Ahmad Hassan
I design systems and lead engineering teams. Most of my work is building the thing that makes the thing work — architecture, integrations, the parts that have to be right.
Currently at Face44, where I've run ~80 projects and built tooling that changes how the team operates.
Rawalpindi, PK — open to relocation
Now
Building agentic AI workflows into how my team actually operates — custom agents for code review, planning, and architecture decisions. Less “AI features in the product,” more “AI in how we build the product.”
Based in Rawalpindi, thinking about what distributed engineering teams look like when AI handles the repetitive cognitive load.
Updated May 2026
Work
Solutions Architect
I've been at Face44 for six years, defining technical direction across ~80 projects — SaaS platforms, headless CMS builds, integrations. The work is architectural but I stay in the code.
The problems I've liked most: cutting a Laravel dashboard from 25s to under 1s, extracting a CPU-bound microservice that was causing downtime, migrating 800GB off a disk that kept filling up. More recently: building an agentic system of custom AI agents and rules that changes how the team makes decisions.
I also run the engineering function — hiring, pre-sales, sprint planning, being the person the client calls when something has to be owned.
Tech Lead
Seconded by Face44 as sole technical contact for a London-based client. Led a distributed team across the US, UK, and Europe — fully async, Agile. Less about shipping features, more about running a distributed team well.
Full Stack Engineer
Before architecture, I was full stack. Built the HR module of a modular ERP from scratch — AngularJS, PHP, MySQL — integrated with accounting and permissions systems. This is where I learned what "integrated" actually means in production.
Stack
I've built across most major stacks over 10 years — TypeScript, Python, PHP, .NET, various frontend frameworks. No strong religion about languages.
The part I care about: cloud architecture, integration design, and systems that don't fall over. AWS for most things, GCP when there's a reason. PostgreSQL is usually right.
Lately: Claude, agentic workflows, structuring agents to do real engineering work rather than just code completion.