Inside the Residency

What the eight weeks actually look like.

The senior skills employers now want first, the four sprints that build them, the team you ship with, the bar your work is held to, and the day you defend it.

8 weeks
Four 2-week sprints
~20 hrs
Per week, around your schedule
100% remote
All sessions on Zoom
5–7 people
One cross-functional team

The entry-level job quietly asked for senior skills.

AI took over the routine tasks juniors used to cut their teeth on. So employers raised the bar: judgment, communication, leadership, and the ability to direct AI — skills people used to pick up five years in. The Residency is built to give you them now.

52%
of the new skills now asked for in entry-level, AI-exposed jobs are ones that used to belong to experienced workers. In the least AI-exposed jobs, it’s 7%.
PwC, 2026 AI Jobs Barometer
JudgmentDirect AI — don’t just prompt it
You write the decision record behind every build: the trade-offs you made, what you’d change. The grading bar checks whether your team can explain its decisions, not just ship them.
Stakeholder managementManage someone who isn’t your boss
Weekly stakeholder meetings and Friday check-ins. On employer projects, you answer to the real organization whose problem you’re solving.
LeadershipOwn a piece and run it
Teams elect their own Scrum Master and each person owns a discipline on a 5–7 person team. You run the standup, you call the milestone.
CommunicationExplain your work under questions
Daily standups, peer reviews, and a demo day where you present and defend what you built in front of mentors and stakeholders.
CollaborationShip as a cross-functional team
Backend, frontend, cybersecurity, data, and QA working toward one product — real code reviews, real pull requests, real handoffs. Not a solo repo.
DeliveryShip something real, on a clock
Four 2-week sprints with milestones and a hard final-demo deadline. You leave with a story about shipping under pressure, because you did.

Coached every week A live leadership workshop with Ryan Taylor — CEO of Coding Temple, who built the leadership-development programs at Udemy — works the judgment, leadership, and communication directly.

Every one of these is a skill employers say they can’t find in early-career hires. You leave able to prove all six.

Four agile sprints, the way a real team works

Each two-week sprint mirrors a real engineering team — planning, building, reviewing, and a demo at the end. By week eight you’ve been through the full cycle four times.

Sprint 1 · Weeks 1–2

Foundation

Goal: orientation and setup
  • AllResidency overview, expectations, and team formation
  • AllKanban board, GitHub workflow, and dev environment setup
  • AllTech stack chosen; Scrum Master elected from within
  • AllStakeholder worksheet distributed; first stakeholder meeting scheduled
DeliverablesTeams finalized, repos created, Kanban boards active, stakeholder meeting scheduled.
Sprint 2 · Weeks 3–4

Discovery & Auth

Goal: requirements and system foundation
  • BEData model, schema design, and authentication
  • FEWireframes, auth UI, and dashboard mockups
  • CSThreat model and secure architecture
  • DADefine KPIs and the event-tracking plan
  • QADraft the test plan and auth test cases
DeliverablesRefined product spec, completed data model, approved wireframes, working authentication.
Sprint 3 · Weeks 5–6

Core Features

Goal: build the primary functionality
  • BECore feature APIs and role-based access
  • FECore feature UI and API integrations
  • CSInput validation and authorization review
  • DALogging hooks and the first dashboard data
  • QAIntegration and regression testing
DeliverablesFirst major feature complete, fully integrated and tested end-to-end.
Sprint 4 · Weeks 7–8

Polish & Deploy

Goal: stabilize and prepare for demo
  • BEBug fixes and performance optimization
  • FEUI polish, UX refinements, and the demo flow
  • CSFinal security review and OWASP validation
  • DAKPI validation and dashboard accuracy
  • QAFull regression suite and end-to-end testing
DeliverablesDemo-ready product, final presentation, program retrospective complete.

A cross-functional team, like a real engineering org

Every discipline working toward one shared product. You own your lane and you depend on everyone else’s — the kind of experience a solo project can’t show.

Backend

Backend Engineering

APIs, database, auth, and business logic.

Frontend

Frontend Engineering

UI, integrations, and responsive design.

Security

Cybersecurity

Threat modeling, security reviews, OWASP.

Data

Data Analytics

KPIs, dashboards, and data validation.

QA

Quality Assurance

Test plans, regression, and bug tracking.

Teams of 5–7, formed by compatibility and shared interest · Scrum Master elected from within

~20 hours, built around your schedule

Live sessions are short and on Zoom. The rest is async work on your own time, the way a real remote team runs.

Mon
  • 5–6 PM: Stand-up
  • Team meeting
  • Sprint planning (wk 1)
Tue
  • Async development
  • Code reviews
  • Cross-team collab
Wed
  • 5–6 PM: Stand-up
  • Team meeting
  • Feature integration
Thu
  • Async development
  • QA testing
  • Security reviews
Fri
  • 5–6 PM: Stand-up
  • Stakeholder check-in
  • Sprint retro (wk 2)

What “production-grade” means — no ambiguity

Your work is graded against clear criteria. This is why the proof is worth something: it’s held to a real standard, and not everyone clears it.

Dimension
Pass
Iterate
End-to-end functionality
All core features work without errors
Core idea works; minor bugs
Stability & error handling
Runs consistently; fails gracefully
Minor errors not fully handled
Technical implementation
Code organized; team can explain its decisions
Mostly readable; minor violations
Team collaboration
Clear role ownership; proactive communication
Visible but inconsistent collaboration
Demo readiness
Demo runs smoothly; clear presentation
Demo mostly works; minor issues
Core features work end-to-end without breaking
Code is organized, readable, and follows best practices
Runs consistently in a demo environment
The team can explain its architecture and decisions
Errors are handled properly — no crashes

The day you present and defend your work

The culmination of eight weeks. Your team presents to peers, mentors, and stakeholders — live, with the audience able to try the product themselves.

5 min
Live demo
Full product walkthrough — the audience can interact via a shared link or QR code.
1 min
Problem statement
The real-world problem you’re solving, and why it matters.
1.5 min
Solution overview
What you built, where AI was integrated, and the tech stack.
1.5 min
Learnings & challenges
Each person: what they learned, the hardest part, what they’d do differently.
3 min
Q&A
You answer for the decisions you made — concise, no hand-waving.

~1 hour per team · Recorded demos accepted, live explanation recommended · The recording becomes part of your Proof Pack

The next cohort starts August 10.

Twenty seats, four teams of five. If you can build and you need recent proof of it, this is the most direct way to get it.