Resume Writing Tips — What Hiring Managers Actually Read
Recruiters Don't Read Resumes — They Scan Them
The oft-repeated industry rule is that recruiters spend 6–10 seconds on the first pass, and perhaps a minute on the ones that survive it. Unfair? Maybe. But when a single job posting pulls in hundreds of applicants, every recruiter becomes a scanner. A good resume is a document designed for a scan, not a read. This post covers the patterns that consistently convert to interviews in IT and general office roles.
What a Recruiter Looks at First
Watch any experienced recruiter work and the eye movement is nearly the same:
- Name, title, years of experience — 0.5 seconds at the top
- Most recent company and role
- Bullets from that most recent role — 3–5 seconds
- Tech stack / tools — especially for IT and design
- Education — last, and briefly
Don't try to re-order this. Your document should flow top to bottom in the order above.
The Non-Negotiable Structure
- A one-line profile at the top: "Backend engineer · 6 years · payments systems" beats any creative summary paragraph.
- Experience in reverse chronological order, above education (unless you're a new graduate).
- Results, not tasks: "Developed payment API" is weak. "Reduced payment failure rate from 3% to 0.5%" is strong.
- A dedicated tech stack section so keywords hit the recruiter's eye quickly.
Weak Bullets vs. Strong Bullets
| Weak | Strong |
|---|---|
| "Worked on payment system" | "Refactored payment service; cut p95 latency by 40%" |
| "Performed data analysis" | "Identified drop-off in onboarding; proposed changes raising retention 12%" |
| "Participated in team project" | "Led frontend for a 3-person team, shipped MVP in 3 months" |
The formula is verb + object + result/number. If you genuinely don't have a number, describe the scale: "service with 100k monthly users," "owned code review for 80% of team PRs." Scale builds credibility almost as well as a specific metric.
Mistakes People Repeat
- Exceeding three pages. 1 page for juniors; 2 pages as an upper limit even for 10+ years of experience.
- One resume for every job. Reorder your stack and rewrite the top-line profile to match the posting.
- Listing responsibilities, not outcomes. Your title already tells the recruiter your responsibility — sell your output.
- Formatting slips. Inconsistent date formats, mixed fonts, typos in company names. These details matter more than you think.
- Dead links. If you include GitHub or a portfolio, click every link before submitting.
- PDF-only or DOCX-only. Have both ready. Many systems handle one better than the other.
Resume vs. Cover Letter
If your target market expects a cover letter as well, keep the roles separate:
- Resume: Evidence — what you've done, with facts and numbers. Objective tone.
- Cover letter: Motivation — why this company, why now. Personal tone.
Bleeding cover-letter phrasing into the resume ("I'm a passionate problem-solver…") usually weakens the resume's credibility. Keep the resume factual.
Pre-Submit Checklist
A one-minute pass before hitting submit catches most common issues:
- Is there a one-line profile at the very top?
- Does every bullet follow verb + object + result?
- Are there at least three numbers or scale indicators?
- Are the role-matching keywords near the top of the skills section?
- Consistent date format, no typos?
- Does the PDF render correctly on a different device?
Final Thought
A great resume doesn't try to summarize your whole career. It proves the specific skill a specific posting requires, within a minute. Replacing a list of "things I was responsible for" with a list of "outcomes I produced" is often the single biggest improvement you can make to your interview callback rate.