GridSchool Residency
A route built around your goal, and a working engineer who reviews every step with you until a company hires you.
20-minute call. We finish your map on it.
Not ready for a call? Take the free 2-minute check
AI made code cheap to write. Teams now hire the engineers they can trust with what it writes.
A reviewed change and a public case study say more than a certificate or a list of tools.
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.
Tutorials are free. An engineer reading your work every week and sending it back is not.
01 · New to the field
Hundreds of applications and no team that has seen you own a change. You need work that is yours, inside a system that existed before you did, reviewed by someone who reads code for a living.
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 cannot yet build something that runs end to end, you want a job-or-refund promise, or you will not have your work reviewed by another engineer.
What you leave with
What your map builds toward. Shown here as empty specimens, because nobody can buy them filled in.
A pull request with the review thread, the check that catches the defect, and your explanation of why.
for (let attempt = 0; ; attempt++) {- await sleep(500)+ if (attempt >= MAX_ATTEMPTS) throw new RetryExhausted(job)+ await sleep(backoff(attempt))
Filled in live at your defense, on the recording. The first thing worth sending a hiring manager.
On your own domain, in your own design. The problem, the baseline, what changed, and what the numbers cannot prove.
You explain your strongest work, then handle a change you did not see coming, in front of an engineer who did not help you. The recording is yours to send.
How a week runs
Eight weeks of teaching and review, 10 to 15 hours a week. After week 8 the 1:1 keeps going until a company hires you.
Your code, your plan, your blockers. Same slot every week.
On real work. Accepted, or sent back with the one thing to change first.
Up to five people. What shipped, what broke, who went quiet.
Stuck for thirty honest minutes, you ask. I answer that day.
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.
Founding terms
Two ways to work with me
Both start from where you stand. In the Residency I review every step with you. In Complete you get your map and the first week's work prepared, and you run it yourself.
Founding rate quoted on the callUp to five residents with me at a time.
Book a call$349 for 12 months, or 4 payments of $9914-day refund, no questions.
Take the free 2-minute checkStraight answers
I make you the candidate a team can evaluate and trust: reviewed work on real systems, a public case study, an outside engineer's verdict, and my reference. I prepare every interview from your own work and keep working with you until you land. A company's yes is still theirs.
Your map starts where you are. For working engineers it usually skips the practice codebase and goes straight to turning past work into public proof, a project aimed at the role you want, and rehearsing 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. On the call we finish it from your resume, your target companies, and where your last interviews stopped. Every step ends in something a stranger can open.
You can, and the draft is yours to keep. What a list cannot do is read your work and send it back, change the plan when an interview goes sideways, or sign a verdict as someone who did not help you. Most steps on your map end in a written review from me, and the defense is judged by an outside engineer. That part is what you pay for.
No. A bootcamp teaches a stack to beginners. This starts from software you can already write and works on what gets you hired next, planned around you and reviewed every week.
The first five get me at full attention while the method is tuned on them, at the lowest rate anyone will pay. Week 2 is the exit.
Bring your resume and the last interview that didn't go your way. You leave the call with the route either way.
Book a call to walk this map