Student & Career
How to Write a Resume That Actually Gets Interviews
Recruiters spend an average of 7 seconds on a first-pass resume review. That's your entire window. Here's how to make those seconds count.
The 7-second scan test
Print your resume. Show it to a friend for 7 seconds. Cover it. Ask: "What role am I applying for, and why should they interview me?" If they can't answer, the resume needs work — no matter how much time you spent on formatting.
The modern one-page rule
Unless you have 10+ years of highly specialized experience, keep it to one page. Recruiters don't read page 2 for entry- and mid-level roles. Cut ruthlessly.
The structure that works
```
[Name] · [Email] · [Phone] · [LinkedIn] · [Location]
Professional Summary (2–3 lines, tailored to role)
Experience
Role — Company (dates)
- Impact bullet (metric)
- Impact bullet (metric)
- Impact bullet (metric)
Projects (if early career or career-switching)
Education
Skills (short, relevant, honest)
```
Skip: photos (in most countries), objective statements, "references available upon request," hobbies unless directly relevant.
The impact bullet formula
Bad: "Responsible for social media management."
Good: "Grew Instagram from 2k to 25k followers in 8 months, driving 15% of Q3 signups."
Every bullet: verb + what you did + measurable result. Use numbers wherever possible. Percentages, counts, dollars, time saved.
Words to cut
- "Passionate," "results-driven," "team player," "hard worker" — everyone says these; they mean nothing
- "Assisted with," "helped with" — either you did it or you didn't
- "Various," "multiple" — be specific
Tailoring per role
Don't send the same resume to 50 jobs. Instead:
1. Read the JD carefully
2. Highlight 5 keywords they use
3. Adjust your summary and top 3 bullets to mirror those keywords
4. Reorder skills so the most relevant come first
Takes 5 minutes per application, doubles callback rates.
ATS (Applicant Tracking System) tips
Most large companies scan resumes with software before humans see them.
- Use standard section headers (Experience, Education, Skills)
- No tables, columns, text boxes, or images with text
- .docx or PDF (both usually work, PDF is safer)
- Match keywords from the JD without keyword-stuffing
Format details
- Font: Inter, Calibri, Helvetica, or Georgia, 10–12pt
- Margins: 0.5–1 inch
- One column
- Bold for role titles, italic for company details
Portfolio / GitHub / LinkedIn
For tech, design, writing: link to work. A resume that says "check my GitHub" beats one that doesn't have proof.
Final check
- No typos (read aloud, or paste into Grammarly)
- Consistent tense (past tense for past jobs, present for current)
- All dates make sense — no gaps unexplained
- File saved as: FirstName_LastName_Resume.pdf
Resumes get you the interview. The interview gets you the job. Optimize the resume for one thing: the callback.
6 min read
More Student & Career guides
How to Crack Your First Tech Interview (Without a CS Degree)
The 90-day prep plan self-taught devs use to land their first developer role.
Study Smarter, Not Harder: 6 Evidence-Based Techniques
Active recall, spaced repetition, interleaving — what the research says actually beats re-reading.
How to Learn a New Skill in 30 Days (The Sprint Method)
A repeatable 30-day sprint framework for picking up a skill fast, from a language to a framework.