Backend & AI Engineer
for B2B SaaS
I design and build scalable APIs, backend systems, and AI-powered workflows that help SaaS companies ship faster.
Don't take my word for it — try my work
Ask this assistant anything about my projects, stack, or process.
Three ways I help SaaS teams ship
Backend Engineering
APIs and services designed for scale — clean architecture, observability, and the failure cases handled before they happen.
AI Integration & Workflows
RAG pipelines, tool-using agents, and LLM workflows that are grounded, guarded, and cheap enough to run in production.
Mobile Engineering
Cross-platform apps that talk to well-built backends — one codebase, native feel, real offline behavior.
Systems that survived production
TransferXO
Cross-border payments backend moving 7-figure monthly volume with zero-downtime deploys.
TM Tinglemore
Mobile learning platform serving 40k+ students with offline-first sync.
Panotour WebXR
Browser-based VR tour engine streaming 8K panoramas on mid-range phones.
What clients say when the system holds
“Simon rebuilt our API layer while we kept shipping. Response times dropped 70% and we haven't had a production incident since.”
“I'm very happy to work with you, Thank you. I highly recommend hiring him. He has a clean code structure. He's a great developer. He's very thorough and flexible in communication. This won't be our last job, we'll work together again and again.”
“He shipped our AI feature in five weeks — properly, with evals and guardrails. Our investors thought we'd hired a whole team.”
Simon Ituen
I'm a backend and AI engineer with 8 years of production experience across fintech, eLearning, civic tech, and immersive platforms. I work with B2B SaaS teams who've outgrown their prototype and need systems that hold up under real users and real load.
My focus right now is AI integration done properly — retrieval pipelines that cite their sources, agents with guardrails, and APIs designed for the failure cases, not just the happy path.
I take ownership of the whole problem: architecture, implementation, load-testing, and handoff. If it ships with my name on it, it works in production.
Ready to build something that
works in production?
Three ways to start. All of them end with working software.