For new software engineers
Every morning: roles that fit you, the person to reach at each, and a note written for you. You send it in your own words, and every reply is tracked.
Two minutes. You keep your map either way.
Or join the free six-week sprint, from November 4
AI made code cheap to write. Teams now hire the people who find the real problem, define what good looks like, and answer for the result.
A real user, a written spec and its checks, something shipped and measured. A hiring manager can open it in ten minutes.
Agents, evals, and the structure of a codebase are the new fundamentals. Using AI well means being able to check what it did.
Your map is built from your goal and rebuilt from what happens: a rejection, a new target, an interview that went sideways.
Hiring runs on trust. Five honest notes a week to named people, with something they can check, beat a hundred portal applications.
01 · New to the field
Hundreds of applications and mostly silence. You need a resume that is ready, notes to real people instead of portals, and one project for a real user that a hiring manager can check.
route build → proof first, then presence
02 · Working, want better
Your best work sits behind an NDA and a resume line. You need it rewritten as public proof, aimed at the role you want next, and rehearsed until the technical round is the easy part.
route career-first or defense-first
03 · Between roles
You need applications and warm intros moving in week one, while one sharp project runs alongside. Speed without spraying: every application points at something a stranger can check.
route career-first, sprint
Not for you if you want someone to apply for you, you want a job guarantee, or you don't enjoy solving problems for people. The free tools stay free either way.
What you leave with
What your map builds toward. Shown here as empty specimens, because nobody can buy them filled in.
The change, the check that catches the defect, and your explanation of why. The proof that you can review what AI writes.
for (let attempt = 0; ; attempt++) {- await sleep(500)+ if (attempt >= MAX_ATTEMPTS) throw new RetryExhausted(job)+ await sleep(backoff(attempt))
A local business, a club or a nonprofit that gave you an hour. What they needed, written down the way they said it.
On your own domain, in your own design. The problem, the baseline, what changed, and what the numbers cannot prove.
The problem, the spec, the checks and the result, said out loud, then your answer to "how do you use AI?" The recording is yours to send.
How a week runs
Once your resume is ready: 5 sends a week (3 at the least), plus one step a week on your real-user project.
Roles that fit you, the person to reach at each, and the note written. In your inbox and in the app.
You send them yourself, in your own words. Every reply is tracked, and silence gets a follow-up.
A conversation, a spec, a check, or something shipped for your design partner.
In the sprint and the cohort: bring what's stuck, and leave with the next step.
Who you work with
My work is applied AI and agentic graph engineering: systems that map how a codebase fits together, and agents that make changes a team can check before it trusts them. These are problems engineering teams have right now, and they are the problems your map is aimed at.
I learned to build before the AI era, writing systems from scratch and shipping software people depended on before LLMs arrived. When the wave hit, it was clear engineers would need help. The tools changed faster than anyone could explain them, and it got harder for a team to tell who was good.
So this is where my time goes. I automate the busywork of a search with the same kind of systems I build, and I plan a map for each engineer around their own goal, so no week goes to work that does not move you toward the role you want.
How it works with money
Three ways in
Every path starts from the free check, where you stand today.
Prices are in US dollars and include any sales tax or VAT. Checkout shows them in your own currency.
$3,000Or 3 payments of $1,100. Reservations open December 1.
Start with the free check Or the free six-week sprintStraight answers
Nobody honest can promise that. What we do: roles that fit you every morning, notes to real people, a real-user project a hiring manager can check, and every reply tracked. A company's yes is theirs.
Your map starts where you are. For working engineers it usually goes straight to turning past work into proof a stranger can check, the titles that fit now, and the rounds where you stall.
The sentence at the top of this page drafts it from three answers, using the same steps the platform runs. The free check finishes it from your resume and where your search stops. Every step ends in something a person can check.
You can, and the map is yours to keep. What you'd be doing by hand: researching roles and the person to reach every morning, drafting each note, tracking every reply and follow-up, and finding a real user for your project. In the cohort you also get clinics and people at the same stage.
No. A bootcamp teaches a stack to beginners. This starts from software you can already write and works on what gets you hired: a ready resume, sends to real people, and one project for a real user.
Don't take it on trust. The free check runs on your own situation before you pay anything, the sprint is free, and we publish the sprint's numbers at weeks 3 and 6, the weak weeks included. Complete has a 14-day refund on the one-time price, and the founding cohort's refund terms are on its page before anyone pays.
Yes. Parents start with this page: what changed in hiring, what we do, and what we can't promise. The founding cohort starts after a call with the grad on it. A parent can also give the self-serve plan as a gift.
Any time, online, in two clicks. It starts with 7 free days, then $97 a month, and it stops on its own after 12 payments. We email you 3 days before the first charge.
The free check reads where your search stops and builds your map. You keep it either way.
Take the free check