AI systems engineer · remote · US / UK / EU
AI chatbots and automation. Websites, web apps, and mobile apps. Data pipelines, integrations, SEO, and growth systems. If software can solve it, I design it, build it, and run it — one engineer, end to end, with a real shipped system behind every capability below.
The capability map
Each card is backed by a real system I've built and operated — most of them running in production right now. And the map keeps growing: if your problem is software-shaped and it isn't listed here, ask anyway.
Selected systems
A 196-page site, 1,000+ schema blocks, and a self-built SEO intelligence platform running daily — optimized to be cited by ChatGPT, Perplexity, and AI Overviews, where visitors convert an order of magnitude better than classic search.
Read the case study → Education · full platform + AI ~800 tests · liveSchool site + student portal with server-graded mock exams, anti-cheat proctoring, and an AI pipeline that turns news articles into exam materials — human-approved, schema-validated, injection-tested.
Read the case study → SaaS · RAG chatbot product 66-business eval corpusA multi-tenant AI support chatbot with hybrid retrieval and citations — its answer quality proven the hard way: evaluated against 66 real company help centers with thousands of scored answers.
Read the case study →What I take on
Build
Automate
Operate & grow
Fixed-scope engagements agreed in writing before work starts — no open-ended hourly billing. And this list isn't a boundary: and you'll get an honest answer on scope and fit, whatever it is.
Process
You describe the problem; I tell you honestly whether AI (or I) am the right fix. No deck, no pressure.
Written scope and timeline. What's included, what isn't, and how we'll measure success — before any money moves.
Working software every week, not status reports. You see it run on real data before launch.
Launch with monitoring and docs. I run it on retainer, or your team takes the runbook — your call.
About
I'm Ajay Chaudhary — an engineer with four years of insurance-tech experience (C#/.NET microservices, regulated and data-heavy) and a portfolio of production systems shipped solo: an AI content pipeline running live for an education client, a RAG chatbot SaaS evaluated against 66 real businesses, an SEO intelligence platform driving a live growth program, and an automation stack that ran unattended for months.
Everything I ship comes with the same habits: tests before "done", secrets scanned before commit, claims measured before they're stated.
FAQ
You get the person who writes the code on every call — no account manager relaying messages, no junior doing the work the senior sold. There's no agency overhead in the price, and no hand-offs where context dies. The trade-off is bandwidth: I take on a small number of clients, and I'll tell you if I'm at capacity.
India (IST). That overlaps US East Coast mornings and the full EU/UK afternoon. Async-first: you get working demos and written updates on a fixed cadence, plus scheduled calls in your business hours.
Fixed scope, fixed price, agreed in writing before work starts — never open-ended hourly billing. If scope changes mid-project, the price change is agreed before it's built. Retainers are monthly and cancellable.
All code and IP is yours, in your repositories, from day one. I sign NDAs. My own pipeline enforces secret scanning on every commit, dependency audits, and an append-only log of automated actions — the same discipline goes into client systems.
Every system ships with documentation and a handover runbook written so any competent engineer can operate it — that's a deliverable, not an afterthought. You're never locked in.
Yes, heavily — an agent platform I engineered myself, with human review, tests, and security gates on everything it produces. It's why one engineer can deliver at team speed. You benefit from the speed; the quality bar is enforced by the test suites and audits, not by trust.
Start here
Describe the problem in a few sentences. I'll reply within one business day with an honest take on scope, approach, and whether it's worth doing — even if the answer is "don't hire me for this."
Start a project
A few details and you'll get an honest reply within one business day — scope, approach, and whether it's worth doing.