Bolu Ajayi

I'm a full-stack engineer who designs backend first. I started out writing frontend interfaces, first at Black Copper, then at Falcon Aerospace, where I grew into full-stack engineering: building the backend APIs and admin tooling behind the products I was shipping, not just the screens on top of them. Somewhere in that stretch, the part I found most interesting stopped being the UI and became what was happening underneath it. How services talk to each other. How state stays consistent when three things can fail independently. How a system behaves at 2am when nobody's watching. I never stopped shipping the frontend — I just stopped treating it as the whole job.

Most of my recent work is Python. At CGLS I was lead engineer on SmartSustain, a FastAPI platform with a geospatial data model, ETL pipelines over millions of government records and a four-pillar scoring engine — and I built the map-driven React frontend on top of it. My MSc dissertation, TD Agent, is a Python analysis pipeline benchmarking LLM technical-debt detection against SonarQube. In Fetch, my distributed-systems build, the payments and driver-matching services are FastAPI, deliberately polyglot alongside the Node side so the service boundaries have to be real contracts. Before that, at Auqli, I owned the backend architecture of a live-shopping marketplace running at up to 50,000 concurrent users.

These days my focus sits at the intersection of Python backends, distributed systems, cloud infrastructure and AI-powered software — with enough frontend range that "who builds the UI?" has never been a blocker on anything I've owned. I'm doing an MSc in Software Engineering, building Wevna — a local-first runtime dashboard that shows you what your Node.js backend is actually doing — and sending fixes upstream to the projects I depend on, including the AWS CDK.