How the 12 months actually work
Five phases, one mentor, and a written plan you can see. No part of this is a surprise at month four.
12-14
Months
One mentor throughout
Weekly
1:1 call
45-60 minutes
8-12
Hours/week
Yours to manage
The five phases
Each phase has a defined focus and a defined output, so you always know where you are.
- 01Week 1-2
Orientation
Baseline and goals
Your mentor reads your code, not just your resume. They look at what you have built, how you structure things, and where you are genuinely stuck. You agree a target role and a written 12-month plan with dated milestones, so there is never a vague stretch where nobody knows what comes next.
- Written 12-month plan
- Baseline skill assessment
- Target role and company list
- 02Month 1-3
Foundations
Close the gaps that block interviews
Whatever is missing between where you are and a junior offer gets fixed first: DSA depth, Python quality, system design basics, or the AI fundamentals you have been skimming. You ship one small project per fortnight and get code reviewed on every one.
- Two reviewed projects
- DSA problem set with feedback
- Weekly written retro
- 03Month 4-7
Specialisation
Depth in one direction
You pick a track and go deep: LLM, RAG, agents or MCP. This is where the capstone starts, and where your mentor spends the most time on architecture decisions rather than syntax. You present your design before you build it, which is how you learn to defend it afterwards.
- Capstone design doc
- Architecture review
- Mid-program checkpoint
- 04Month 8-10
Production
Make it deployable
Cloud deployment, observability, cost and failure handling. Most student projects are a notebook. This phase is about the unglamorous work that decides whether you can talk credibly about a system in an interview: it fails, you have seen it fail, and you know what you changed.
- Deployed capstone
- Failure-mode write-up
- Cost estimate
- 05Month 11-14
Placement
Interviews and offers
Mock interviews on the real structure for your target companies, timed the same way. Resume and LinkedIn rewritten around evidence rather than adjectives. Referrals where we have a relationship, and honest advice when we do not.
- 12+ mock interviews
- Rewritten resume
- Referral intros
- Offer negotiation prep
What is included
Everything in the program fee, across all 12-14 months.
Weekly one-on-one call
45-60 minutes, same slot, every week. Your mentor sets the agenda from your written plan, not from a template.
Async code review
You push work and get written feedback within two working days. Reviews are specific to your code, not generic advice.
Roadmap that gets updated
Your 12-month plan is revised as the AI job market moves. If a technology is no longer what companies ask for, it comes out.
Mock interviews
Timed the way the real loop is timed, on the real question sets for your target companies, from month eight onward.
Resume and LinkedIn work
Rewritten around evidence you can defend. We remove the adjectives and keep the numbers.
Referrals where we have them
We introduce you to companies where we have a real relationship. Where we do not, we say so rather than pretending.
Six months of tracking
We keep tracking you for six months after the program ends, because the offer you want sometimes arrives just after it.
Direct line between calls
Questions between calls go to the same mentor who already has context on your work. No ticket queue.
One mentor throughout
The same person for 12-14 months, with a direct line for code review between calls. No re-explaining your context every few weeks.
Free rematch if it does not fit
If the match is wrong, we rematch you at no cost or refund the mentorship portion. We would rather fix it than have you spend a year there.
Curriculum that tracks the market
Your plan is revised as what companies ask for changes. A technology that stops appearing in job descriptions comes out of your roadmap.
Questions students ask first
Why 12-14 months instead of a shorter bootcamp?
Because hiring cycles for AI roles are slow and interview preparation takes months of accumulated practice. A three-month program can teach you the material, but it rarely leaves room for the reviewed work and repeated mock interviews that actually get you through a loop. Twelve months matches the cycle.
Is it really the same mentor the whole time?
Yes. One mentor, start to finish, with one direct line for code review. Switching mentors mid-program means re-explaining your context, which is exactly the overhead this is meant to remove.
What if my mentor is not a good fit?
Tell us and we rematch you at no cost, or refund the mentorship portion. We would rather change the match than have you spend a year talking to someone whose advice does not land.
Can I keep my mentor after the program ends?
Yes, as a separate arrangement with your mentor directly. Several students do this while they are in their first job. It is not part of the program fee, so agree it separately rather than assuming it is included.
How much time does it really take?
Roughly 8-12 hours a week: the weekly call, your module work, and the project you are building. Front-loaded months are lighter than the placement phase, which is heavier because mock interviews are demanding.
Is this suitable if I am in second year?
Yes, and it is the ideal time. The foundations phase covers exactly what your placement season has not taught you yet, and you will be interview-ready by the time companies start recruiting for final-year placements.
Still deciding?
Meet the mentors first. Their expertise, availability and background are all listed, and you can send a request before committing to anything.
Want the curriculum too?
Mentorship pairs with the 12-month program, but it also works on its own if you are already building on your own.
Ready to start
Applications for the next cohort are open. We reply within two working days, and the first call is a free 30-minute conversation about whether this fits.