Twelve focused weeks can take you from university to interview-ready for your first developer job. You finish with one role target, two production-style projects, an outcome-based resume and 40-60 tailored applications sent.
The plan is for CS students, bootcamp graduates and self-taught developers with under a year of experience. No internship is required. Each block below says what to do and which resources to use.
Table of Contents
- What you have after 12 weeks
- How the 12 weeks are sequenced
- Weeks 1-2: pick one target lane
- Weeks 3-5: build two portfolio projects with real-world signals
- Weeks 6-7: rewrite your resume and LinkedIn around outcomes
- Weeks 8-9: start applying with a tracking system
- Weeks 10-11: prepare for four kinds of interview questions
- Week 12: check the offer before you accept
- How to tell the plan is working
- Mistakes that delay first offers
- FAQ
- Related guides in this series
What you have after 12 weeks
By week 12 you should be able to tick every item on this checklist:
- One clear role target
- Two production-style portfolio projects
- Resume with measurable outcomes
- Structured applications tracker
- Weekly networking and referral outreach
The application targets for the sprint:
- 40-60 high-quality applications
- 10-15 referral asks
- 3-5 mock interviews
How the 12 weeks are sequenced
Each block builds on the one before it. You pick a lane, build proof for that lane, then describe the proof on your resume. Only then do you apply and practice interviews.
The plan is written for:
- Computer science students
- Bootcamp graduates
- Self-taught developers with less than 1 year of practical experience
Weeks 1-2: pick one target lane
Choose one lane so your portfolio and resume tell the same story:
- Backend (Go/Node/Java)
- Frontend (React/TypeScript)
- Full-stack (React + API + database)
Reliable resources:
Weeks 3-5: build two portfolio projects with real-world signals
Each project should include:
- README with setup instructions
- Clear architecture notes
- Tests and basic CI
- Deployed demo or API endpoint
Project ideas:
- Job application tracker API
- Interview prep flashcard app
- Student budget planner with authentication
Reliable resources:
Weeks 6-7: rewrite your resume and LinkedIn around outcomes
Write each bullet around its outcome. A task on its own is the weaker bullet, as this pair shows.
Bad bullet:
- “Built a backend in Go”
Better bullet:
- “Built a Go REST API with PostgreSQL, reducing query response from 420ms to 120ms through indexing and query refactoring”
Reliable resources:
Weeks 8-9: start applying with a tracking system
Track every application in a spreadsheet or Notion with these columns:
- Company
- Role URL
- Date applied
- Resume version used
- Referral status
- Outcome
Aim for the targets from the first section: 40-60 applications, 10-15 referral asks and 3-5 mock interviews.
Reliable resources:
Weeks 10-11: prepare for four kinds of interview questions
Split your prep across four buckets:
- Coding fundamentals
- API/system design basics
- Behavioral stories (STAR format)
- Debugging and trade-off communication
Reliable resources:
- LeetCode
- NeetCode
- Excalidraw for architecture explanations
Week 12: check the offer before you accept
Before accepting:
- Understand role expectations for the first 90 days
- Confirm mentorship and onboarding support
- Clarify salary, benefits and growth path
Reliable resources:
How to tell the plan is working
Score yourself every Sunday, 0-2 points per line:
- Portfolio progress (0-2)
- Applications submitted (0-2)
- Referral outreach sent (0-2)
- Interview prep sessions done (0-2)
- Lessons documented (0-2)
Target 7+ points a week. If you’re below 7 for two weeks, reduce scope and focus on fewer priorities.
A good week looks like this:
- Shipped one meaningful project improvement
- Submitted 8-12 tailored applications
- Sent 3-5 personalized outreach messages
- Completed 2 mock interviews
- Updated resume with one measurable achievement
Mistakes that delay first offers
- Applying to everything without role focus
- Shipping unfinished portfolio projects
- Waiting too long to ask for referrals
- Over-indexing on coding puzzles only
FAQ
What if I can only study 8-10 hours per week?
Use a 24-week version of this plan and keep the same sequence. The pace changes. The strategy stays the same.
Should I wait until my portfolio is perfect before applying?
No. Start applying once one project is decent. Keep improving it in parallel.
How many applications should I send in 12 weeks?
The plan targets 40-60 high-quality applications. Pair them with 10-15 referral asks and 3-5 mock interviews.
How many rejections are normal?
Many. Rejection is a normal part of the process. It doesn’t mean you’re unfit for software engineering.