Lesson 2 of 6 · 14 min
Resume, LinkedIn & a Job Search System
A one-page resume, a findable profile, and a weekly routine that produces interviews.
The one-page resume
Juniors should use one page. Order:
- Header: name, email, GitHub, LinkedIn, portfolio link, city
- Skills: languages, frameworks and tools you've actually used in projects
- Projects: 2–3, each with a live link and 2–3 impact bullets
- Experience: any jobs, even outside tech. Highlight teamwork, ownership and customers
- Education: degree, bootcamp or self-taught, plus relevant certificates
Bullet formula
Action verb + what you built + technology + result
"Built a REST API in Node.js and PostgreSQL for a recipe app; added caching that cut page load from 2.1s to 0.4s."
Get past the filters
- Match keywords from the job description (if they say "TypeScript" and you know it, write "TypeScript")
- Use a simple layout without tables, columns or images, so applicant tracking systems can read it
- Save as PDF named
Firstname-Lastname-Resume.pdf
LinkedIn & GitHub
- Headline: "Junior Full-Stack Developer · JavaScript, React, Node, SQL"
- Pin your best 3 repositories on GitHub
- Post about what you build. Short posts about a bug you solved get noticed
A weekly system
| Each week | Target |
|---|---|
| Targeted applications with a tailored note | 10–15 |
| Messages to engineers or alumni (ask for advice, not a job) | 5 |
| Interview practice sessions (Interview Prep + a friend or peer) | 3 |
| Commits to a portfolio project | 4+ days |
Track everything in a spreadsheet: company, role, date, contact, status. Job searching is a numbers game you can improve, so measure it.
✅ Check your understanding
Which resume bullet is strongest?
What usually gets a junior developer interviews fastest?
Create a free account to track your progress.