Tom finished a 16-week bootcamp in March. He signed an offer for a backend engineer role 7 months later. Here's month-by-month what he actually did.
Month 1: kept building
Bootcamps end with a portfolio project. Tom's mistake (and almost everyone's) was treating that project as the finish line. The first month after graduation is the highest-leverage one — he was the most "current" he'd ever be on the material.
He kept extending his capstone for four more weeks: added auth, deployed it, wrote a README aimed at recruiters not classmates.
Months 2–3: applied broadly, learned fast
Sent 86 applications. Got two interviews. Both went badly. Reviewed every question afterwards and rebuilt his answer to "tell me about a recent project" three times.
The number of applications wasn't the lever. The quality of the answer to that one question was.
Month 4: narrowed scope
Stopped applying to anything labelled "junior" at companies bigger than 500 people. Those funnels were too crowded for someone with no prior commercial experience.
Targeted early-stage startups specifically. Different bar: they care less about credentials, more about "can you ship by Friday." Tom could.
Months 5–6: referrals started compounding
Three coffee chats per week. Each one ended with the same ask: "if you hear of anything that fits a junior backend hire, would you mind passing my name along?"
Two referrals turned into interviews in month 5. One into an offer in month 6.
Month 7: accepted
The offer was for slightly less than he'd hoped. He negotiated once, got £2k more, and signed.
What to take from it
- The portfolio doesn't end when the bootcamp ends.
- Quantity-of-applications is the wrong metric for a junior role with no commercial experience.
- The fastest narrowing move is company size, not job title.