GridSchool Residency · 8 weeks · then I stay until you're hired
You have the degree.
Now get the job.
Eight weeks of real systems every day, a senior engineer beside you every week, and a public body of work nobody can fake. If you are not hired when the eight weeks end, I keep working with you until a company hires you.
20-minute call. No pitch deck. If it isn't the right room, I'll say so and point you somewhere better.
Everything on this page is checkable. Start with these three.
Built for the graduate the market skipped
You did the work. You can build software. The apprenticeship rung you were promised got thinner the year you needed it, and AI made every portfolio look the same. This is for three people, and the same room fixes all three.
CS grad, no offers
Hundreds of applications, a handful of screens, no team that has ever seen you own a change. You need work that is yours, in a system that existed before you did.
Bootcamp or self-taught, tutorial portfolio
Your repos run. They also look like everyone else's. You need a product with real users, a graph tool you built, and a reviewer who marked your code up.
0 to 3 years, stuck or laid off
You have shipped, but nobody outside your old team can tell. You need public proof of ownership and the AI-era craft the next role expects.
Not for you if: you can't yet build something that runs end to end (start with a free course and come back), you want a job-or-refund promise, or you won't have your work reviewed in front of other people.
What the eight weeks look like
Eight weeks of the intensive if you work every day. After that I stay with you until a company hires you. The sequence is the same either way: live system, your own product, public proof, a defense, then the search.
-
Weeks 1 to 2
Read and change a live system
A multiplayer world with real users lands on your machine. You make it run, trace a ticket through code you did not write, then ship your first change through review and watch it deploy.
-
Weeks 3 to 5
Your own product, shipped
You model a system, build it with the AI tooling working engineers use, put it in front of real users, and measure the outcome. I sign off on each stage in writing.
-
Weeks 6 to 7
Graph tool, design system, public site
You build a tool that reads source code as a graph and use it to plan your own changes. You and I agree a design system in a 1:1 and you build your site in it, one page per project, and start publishing.
-
Week 8
The defense
Eight recorded minutes defending your strongest change to a working engineer who did not help you. Their written verdict is yours to show a hiring manager.
-
After week 8
Until you land
I keep the weekly 1:1, prepare each interview from your own work, and get eyes on the evidence. A company's yes is still theirs. I do not stop because the eight weeks ended.
Every week: a private 45-minute 1:1, a live cohort call, and up to three written reviews on your real work. Plan for 10 to 15 hours a week. Discord in between.
What you build, and what a hiring manager sees
A merged change to a live multiplayer world
PR, review thread, deploy, and a failure log, on a system that existed before you did.
They see: you can be trusted with code you didn't write.Your own system, with users
Modeled, built, deployed, observed, with a measured outcome and an honest causation note.
They see: you can take something from idea to people using it.A graph tool you wrote
Parses source into a call graph, answers "what breaks if I change this", and packs context for an AI assistant.
They see: you understand systems, and you use AI like an engineer.Your site, in your own design system
One page per project, your posts and research, a profile that reads as a working engineer's.
They see: a stranger finds real work in under a minute.How I work with you
Bootcamps have a curriculum and a cohort. You get a senior engineer who reads your code every week for eight weeks, then until you land, and a room of five who notice when you go quiet.
- Weekly 1:1, 45 minutes. Your code, your plan, your blockers. Same slot every week.
- Three written reviews a week. On real work. Accepted, or sent back with the one thing to change first.
- Sign-offs on every project. Nothing counts as done because you said so.
- A live cohort call. Five people, one hour, what shipped and what broke.
- The defense. An outside engineer, on camera, filling in the form on the right.
- Discord, daily. Stuck for thirty honest minutes, you ask. I answer the same day.
At your defense, a working engineer who did not help you fills this in, live, on the recording. It is the first thing worth showing a hiring manager.
Shown empty on purpose. Nobody can buy this filled in.
Your progress is a map
Every step on it is a thing you can point a stranger at. The tall column is what to do next. Green is done. A shorter amber column is waiting on my written verdict, or came back with changes. Nothing lights without a link, and I see the same board from my side.
Walk the demo board →Founding cohort
The first five residents get me directly through all of it, at a founding rate that is quoted on the call and never printed here, because it will rise once they have defended in front of outside engineers.
- One payment, or a deposit and the balance after week 1. Checkout shows the figure before you pay anything.
- The week-2 exit. If either of us says wrong room by the end of week 2, unused tuition comes back. No forms.
- The one condition. Work every day. Go quiet for three weeks and your spot pauses and I call you.
- After week 8 I stay. Weekly 1:1, interview prep from your own work, and getting eyes on it, until a company hires you. A company's yes is still theirs. Your evidence, your site, your verdict, and my reference are yours.
Apply, a 20-minute call, then a decision on both sides. Score your trust gap first, it costs nothing.
I'm Aden. Check everything on this page.
I'm a working software engineer, not a placement shop. I paid twenty thousand dollars for a bootcamp on my way in and built this because I knew what that money should have bought: a senior engineer who reads your code, real systems to break, and proof you can show. There is no alumni wall yet. The founding five build it, and they can always reach me after.
Straight answers
Will you get me a job?
I make you the candidate a team can evaluate and trust: real ownership on live systems, written review, a public site, an outside engineer's verdict, and my own reference. I prepare every interview from your own work and I keep working with you until you land. A company's yes is still theirs.
Why eight weeks?
That is the intensive: ship the proof if you work every day. Short programs end there. I do not. If you are not hired at week 8 I keep the weekly 1:1, the interview prep, and getting eyes on the work, until a company hires you. Eight weeks is the program. It is not a hire-by date.
Is this a bootcamp?
No. Bootcamps teach beginners a stack. You already write programs. This is a residency: work on real systems with a senior engineer, sign-offs, and proof, for someone who already has the degree or the equivalent.
What if I'm slower or faster than the timeline?
The timeline is a sequence, not a clock. The map opens the next step when you finish the one before it. Work every day and the pace is yours.
I never got hired after the AI wave. Is that me?
If you can't write a working program yet, learn that first; I'll point you at free material. If you can, the missing piece is almost never another tutorial. It is proof someone else can trust, and the craft of using AI in a way you can defend.
Why founding, with no placements yet?
Because 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. Once they have defended in front of outside engineers, the rate rises and the room gets harder to get into.