Table of Contents
- Who this roadmap is for
- Week 1-2: Pick one target lane
- Week 3-5: Build 2 portfolio projects with real-world signals
- Week 6-7: Resume and LinkedIn optimization
- Week 8-9: Start applications with a system
- Week 10-11: Interview preparation (practical)
- Week 12: Offer readiness and negotiation basics
- Common mistakes that delay first offers
- Weekly scorecard template
- What a “good week” looks like
- FAQ
- Final checklist
- Related guides in this series
If you’re in university (or just finished) and trying to land your first developer job, this university-to-first-developer-job roadmap gives you a clear week-by-week plan.
Who this roadmap is for
- Computer science students
- Bootcamp graduates
- Self-taught developers with less than 1 year of practical experience
Week 1-2: Pick one target lane
Choose one lane so your portfolio and resume are coherent:
- Backend (Go/Node/Java)
- Frontend (React/TypeScript)
- Full-stack (React + API + database)
Reliable resources:
Week 3-5: Build 2 portfolio projects with real-world signals
Your projects 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:
Week 6-7: Resume and LinkedIn optimization
Focus on outcomes, not tasks.
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:
Week 8-9: Start applications with a system
Track applications in a spreadsheet or Notion with:
- Company
- Role URL
- Date applied
- Resume version used
- Referral status
- Outcome
Target:
- 40-60 high-quality applications
- 10-15 referral asks
- 3-5 mock interviews
Reliable resources:
Week 10-11: Interview preparation (practical)
Prepare 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: Offer readiness and negotiation basics
Before accepting:
- Understand role expectations for first 90 days
- Confirm mentorship and onboarding support
- Clarify salary, benefits, and growth path
Reliable resources:
Common 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
Weekly scorecard template
Use this simple scorecard every Sunday:
- 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 weekly. If you’re below 7 for two weeks, reduce scope and focus on fewer priorities.
What a “good week” looks like
- 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
This cadence compounds quickly and turns uncertain effort into predictable progress.
FAQ
What if I can only study 8-10 hours per week?
Use a 24-week version of this plan, but keep the same sequence. Progress speed changes, but the strategy does not.
Should I wait until my portfolio is perfect before applying?
No. Start applying once one project is decent and keep improving in parallel.
How many rejections are normal?
Many. Rejection is part of the process, not evidence that you’re not fit for software engineering.
Final checklist
- One clear role target
- Two production-style portfolio projects
- Resume with measurable outcomes
- Structured applications tracker
- Weekly networking and referral outreach
Consistency beats intensity. A focused 12-week sprint can move you from uncertain to interview-ready.