An autonomous multi-agent system
Designed and built an always-on AI engineering system from scratch, as the sole engineer.
Specs before prompts, evals before launch, and an owner after it ships. For three years I've been a core engineer at Content Camel, a US B2B sales-enablement SaaS, shipping its first AI features.

Designed and built an always-on AI engineering system from scratch, as the sole engineer.
Researches, writes and opens publish-ready pull requests, gated by a human-approved brief, and feeds sales a ranked list of signals.
An LLM pipeline over reps' real HubSpot deal conversations that surfaces which content actually closes deals, with confidence scores and evidence.
The prospect-facing microsite product reps share with buyers. Every layer owned solo, then launched to 100% of users.
Content Camel's serverless backbone, built piece by piece: event services, data pipelines and integrations.
Ground-up rebuilds, an 18-service migration, and leading a team before Content Camel.
I don't query someone else's CRM live every time I need to think. I ingest, then operate on my own copy.
Useful, occasionally wrong, and best wrapped in the same guardrails you'd give any external call.
You're not pretending the AI is certain. You're showing your work.
Match behaviour exactly, ship, then improve from a stable base.
A queue between producers and workers turns a spike into a steady drip.
Write down the manual steps a person repeats more than twice a week. Not the interesting work: the glue.
Why the interesting engineering in an AI feature sits downstream of the model.
The repetitive work is a hidden tax on every team. Here is how I stop paying it.
Extraction, not magic. Treat the model like an unreliable function and wrap it accordingly.
SQS, Lambda, DynamoDB: a mental model that scales without babysitting.
What I'd tell myself before starting a ground-up extension rebuild.
"Hasan goes beyond merely implementing what's designed; his high-level execution and problem-solving skills lead him to explore the 'whys' and focus on the end-user experience."