Available for freelance & consulting
I'm Akeem Baker — a Quality Engineer. A decade of understanding how systems fail now shapes how I design, build and ship them: deliberate architecture, sharper trade-offs, and far fewer expensive surprises.
10+ years across testing, automation & delivery
Architecture chosen for what it costs to change later
Proven continuously — tests, types & accessibility in CI
Full-stack delivery: Next.js, React & TypeScript
Work
In-depth case studies of selected projects — the problems, the engineering decisions I made, and the outcomes delivered.
A two-sided property management platform for self-managing UK landlords and their tenants — and a look at how I design a product for reliability, security and long-term growth from day one.
A consulting site is easy to fill with claims about engineering standards. I built mine so the claims are checkable — the architecture, the trade-offs, and the automated gates every change has to pass before it ships.
About
I'm Akeem Baker — a Quality Engineer. That understanding is what shapes the architecture I choose, the trade-offs I make, and the software I hand over.
Across functional, regression and UAT testing — and automation built in Playwright, Selenium and TestComplete — I watched the same failures repeat: unclear boundaries, hidden coupling, and decisions made by default rather than on purpose. Those are the patterns I now design against, before anything is written.
Today I pair that with full-stack development in TypeScript, React and Next.js — one person who can shape the architecture, build the feature and prove it works. Fewer handoffs, fewer gaps between what was intended and what ships, and software that stays cheap to change long after handover.
Most of that work starts inside something that already exists. I'm comfortable joining an established codebase, CI pipeline and Agile team, and I follow your conventions rather than importing my own.
Services
Testing, AI-assisted development and full-stack delivery — with quality engineered in from the first decision rather than inspected at the end.
How I work
No black boxes. Here's how a typical engagement runs — and the quality practice built into each stage.
Understanding your goals, your users, and the constraints you're working within.
Quality built in: I ask what could go wrong as early as what should go right. Risks found here cost nothing to fix.
Agreeing scope, approach and a clear plan before any work starts.
Quality built in: Scope is prioritised by risk, so the areas most likely to hurt you get the most attention — not just the loudest features.
Modelling the domain and choosing the structure your software will grow into.
Quality built in: The design makes correct behaviour easy to build and incorrect behaviour hard. The cheapest defect is the one the architecture won't allow.
Development in small, reviewable increments with regular check-ins.
Quality built in: Tests are written alongside the code, so each increment arrives already proven.
Shipping to production with documentation and a clean handover.
Quality built in: Automated checks — tests, types, accessibility — all pass before anything ships. Releasing becomes a decision backed by evidence.
Maintenance, improvements and ongoing support — one-off or on a retainer, as your needs change.
Quality built in: The test suite evolves with the product, so changes stay safe long after launch.
The stack I reach for to build and test modern web applications.
Contact
Send me a short description of what you're working on and we'll scope it on a quick call — whether that's a defined project or just an idea you want to talk through. No obligation, no hard sell.
Currently available for freelance and consulting work.