Phase 01
I do
The curriculum teaches. Twenty-five units across frontend, data, backend, and AI engineering.
Programs/Mentor Corps
Staff the
middle.
The accelerator teaches in a gradual release model. Units are I do. Evidence gates are you do. The Mentor Corps staffs the band in between — we do — which is where veterans stall and where no automated system reaches.
Duty description
- Commitment
- 4–5 hrs / month
- Term
- One cohort · 17 weeks
- Cohort size
- 10–15 troops
- Location
- Remote
01 / Gradual Release
Where you fit.
Your mentee is a working engineer in the making. You are a working engineer already — a Vets Who Code graduate employed in the field, or a veteran engineer from outside the accelerator. Either way, someone who has already done the thing they are trying to do.
Phase 02 · You
We do
The Mentor Corps. Judgment, tradeoffs, and the question a model cannot answer: would this survive code review at a real company.
Phase 03
You do
Evidence gates. The troop proves it alone, against a published rubric, graded by someone who is not you.
02 / Scope of Work
Two tracks.
Track 1
Technical
Pre-gate artifact review, architectural tradeoffs, debugging workflow, git CLI, and the question that matters most: would this survive code review at a real company.
Coverage follows the curriculum — React and TypeScript on the frontend, the data layer including pgvector, FastAPI on the backend, and AI engineering: RAG, agents, production AI APIs.
Track 2
Translation
Turning mission experience into engineering impact statements, mock technical and behavioral screens, portfolio review, and offer negotiation.
It runs light through the accelerator and becomes the main event at graduation.
Mentorship is scoped deliberately above syntax. Troops already have the harness — OpenCode and CodeGemma 2B — and it answers faster than a human can. Your time goes to judgment. It is also not a networking app and not a coffee chat.
03 / Commitment
What you
owe them.
Four to five hours a month, for one cohort. Standing appointments, not availability. At the end of seventeen weeks you decide whether to take another.
- 01
One 45-minute sync every week
On a schedule you and your mentee set.
- 02
One pre-gate artifact read per unit
Returned within 48 hours, against the published rubric.
- 03
Async access in the cohort Discord
Within hours you state up front. Not always-on.
- 04
Six months of Track 2 after graduation
Mock screens, resume, interview loops, offer negotiation.
04 / Timeline
How it runs across
seventeen weeks.
The load is not flat. Weeks three through six are where attrition happens, and that is where you lean in hardest.
Weeks 01–02
Onboarding
Confirm the match, review their weakest units from intake, and agree on when they escalate rather than grind. They bring learning objectives, a working GitHub, and a first gate submission.
Weeks 03–06
Peak load
Frontend
The highest-touch phase. This is where attrition happens, so this is where you lean in hardest — unblocking and confidence, not lectures.
Weeks 07–10
Data layer
Correctness review. Bad schema and query decisions fail quietly, and gates alone will not catch them. They explain their modeling choices out loud.
Weeks 11–14
Backend
Tradeoff conversations, API contracts, CI/CD, and what production actually looks like. They walk you through the system design of their own work.
Weeks 15–17
AI engineering
RAG and agent design judgment, and the difference between production-real and demo-real. Portfolio goes final and the job search opens.
+ Six months
Post-graduation
Track 2 takes over while they apply, interview, and negotiate.
Data structures and algorithms run as a continuous thread across all seventeen weeks, on their own recurring touch, because interviews are shaped differently than the work.
05 / Qualifications
Who we're
looking for.
You don't need to be a veteran to mentor. You need to be good at your job and willing to invest time in someone who's working to get where you are.
- Working software engineers with production experience — frontend, backend, full-stack, DevOps, AI/ML, or cloud infrastructure.
- Engineers who can commit to weekly check-ins and async code reviews for the duration of a 17-week cohort.
- People who give direct, honest feedback. Our troops come from the military — they don't need to be coddled, they need to be coached.
- VWC alumni who want to come back and pay it forward are especially welcome.
06 / Guardrails
You never grade
their gate.
This one is structural, not a courtesy. A veteran will not admit “I don't understand this unit” to the person who decides whether they pass. Grading and mentorship stay in separate hands so the weekly sync is a place they can be honest about what is not landing.
You review against the published rubric for each unit — not personal preference. Before your cohort starts, you are briefed on the three failure modes that make mentorship worse than nothing.
Failure mode 01
Writing the code for them
Failure mode 02
Drifting into life coaching
Failure mode 03
Contradicting the curriculum
07 / Leadership & Impact
It's practice.
It's impact.
Not charity. Engineering leadership practice.
Mentoring a VWC troop is the closest thing to managing a junior engineer without the HR paperwork. You'll practice giving code reviews that teach, running 1-on-1s that develop people, and translating your experience into guidance someone else can act on. Senior engineers and engineering managers consistently tell us that mentoring with VWC made them better at their day job.
Your time has measurable impact.
This isn't a pen-pal program. Our troops ship code, pass technical interviews, and get hired. When your mentee lands a role at a company you respect, you'll know your Thursday evening code reviews had something to do with it. Our alumni are engineering at Microsoft, Accenture, Amazon, Google, GitHub, Booz Allen, and Deloitte. Many of them came back to mentor the next cohort.
Take one cohort.
Seventeen weeks, four to five hours a month, one engineer who will remember your name for the rest of their career.