About
I'm Ahmed Ali, a software architect and engineering lead. After six years in the industry, my work has moved from writing FinTech backends to designing the systems around them and leading the teams that build them.
Most of what I do sits at the point where a product starts outgrowing its original architecture. That is rarely a coding problem. It is usually a boundaries problem, a data-flow problem, or a set of trade-offs nobody wrote down when the first version shipped.
I also founded TrackHRS, which taught me the parts of software that architecture diagrams leave out: pricing, support, deployment on a Sunday, and the difference between a system that works and a product people pay for.
If you want the detail, I've written up how that plays out role by role: architecture, backend, full-stack, AI and leading teams.
Projects delivered
Web, ecommerce, CMS, ERP and AI platforms
Years engineering
FinTech, AI and SaaS at production scale
Events per day
Kafka pipelines running in production
Engineers led
Across AI, ecommerce and CMS product lines
There is no best design, only the one whose costs you have chosen deliberately. I would rather write down why we picked Kafka over a queue than let the reason evaporate in six months.
The happy path is not the one that wakes you at 3am. Retries, circuit breakers and dead-letter queues belong in the first diagram, not the second incident review.
Service boundaries decide who can ship without asking permission. Getting them right cut cross-team integration issues by more than half on my current team.
Clever code is a liability the moment its author moves on. I optimise for the person reading it a year from now, which is often me.
The kinds of systems I've spent the most time inside, and what each one taught me about designing for its particular failure mode.
Personal finance platforms delivered to digital banks, where precision is non-negotiable and downtime is a headline. Multi-database consolidation, encrypted transaction flow, audit trails and bank-grade availability.
Real-time computer vision and alerting, RAG pipelines, advisory chatbots and multi-agent platforms that generate working software. AI built as a service with evaluation and failure paths, not a demo.
Founding and shipping a live SaaS end to end: desktop agent, microservices, billing, admin portal and the deployment pipeline underneath. Plus MVPs taken from nothing to production for other teams.
Hundreds of client platforms across ecommerce, content management and ERP integration, covering high-traffic storefronts, admin systems and the third-party integrations that hold a business together.
Alongside the architecture work, I lead engineering teams, setting standards, drawing service boundaries and mentoring engineers on system design and what it takes to run production well.
Engineers led
Across AI, ecommerce and CMS product lines
Fewer integration issues
From clear service boundaries and ownership
Less deployment effort
Kubernetes and Docker replacing manual releases
Whether it needs designing from scratch or rescuing from its own success, tell me what you’re building and I’ll tell you how I’d architect it.
Open to remote and hybrid work worldwide