I gave an AI my job hunt. Here's the system that kept it honest.

Backend engineer Odinaka Nnamani built an AI agent that submitted 12 job applications autonomously, with a verification layer that forced every claim to trace back to his resume, GitHub, or personal site. The system caught 8 dead listings before submission and flagged 3 broken forms rather than fabricating data, with the agent explicitly disclosing gaps such as "No production LLM-API experience" instead of inventing credentials. Nnamani argues the engineers who succeed with AI will be those who build verification into the loop, not those who prompt hardest.

Yesterday I applied to 12 engineering jobs. I didn't open a single application form. My AI chief of staff did it — research, verification, form-filling, submission, audit trail. I woke up to 12 submitted applications, 8 dead listings caught before I wasted a click, and 3 forms flagged as broken instead of faked. This isn't a "10x your job hunt with ChatGPT" post. It's about the verification layer that makes delegating to an AI actually work — because an AI that applies to jobs wrong is worse than no AI at all. The system has four stages, and the important thing is what happens between them: Here's the part that surprised me. Asked about production LLM-API experience, the AI wrote: "No production LLM-API experience." Asked about shipped autonomous agents: "None." Asked about production Go: "No production Go." It disclosed what I haven't done instead of inventing it. That's not a limitation of the system — it IS the system. A fabricated application that gets you an interview you can't survive is negative value. An honest application to the right role is the whole game. The rule I gave it: only those you record are true. Every claim in every application had to trace back to a verified fact — my resume, my GitHub, my site. No invented years of experience, no inflated metrics, no phantom credentials. The verification stage needs to run before research finishes ranking — I burned research effort on roles that died at verification. And the broken-form problem needs a human-in-the-loop escape hatch earlier: three fully-filled forms sitting in Drafting is a queue, not a result. The bottleneck was never my ability. It was my bandwidth. Twenty applications in a day is a data-entry problem, and data entry is exactly what machines are for — as long as the verification layer is ruthless. The engineers who thrive with AI won't be the ones who prompt hardest. They'll be the ones who build verification into the loop. I'm Odinaka Nnamani — backend engineer TypeScript, Node.js, PostgreSQL, AWS and founder of Rootmail https://rootmail.io , email infrastructure that tells you what happened to every email. Open to remote backend/infrastructure roles: heypascal.me https://heypascal.me