The reality of resume screening
At a FAANG-tier company, a recruiter spends 6–10 seconds on the first pass. They’re scanning for:
- Company names they recognize (or tier signals — FAANG, unicorn, funded startup)
- Role titles that match the level they’re hiring for
- Keywords that match the job description (often via ATS — applicant tracking system)
- Education (for some companies, specifically for new grads)
If none of those things are present in the first visual scan, the resume goes in the “no” pile before your best project gets read.
This is not fair. It is the reality.
The one-page rule
One page if you have fewer than 10 years of experience. Two pages maximum if you’re a senior with genuinely distinct, impactful experience across many roles.
If you’re struggling to fit on one page, you’re including the wrong things. The question is never “is this thing I did worth mentioning?” — it’s “is this thing more worth mentioning than the best thing already on the page?”
The XYZ bullet formula
Every bullet point should follow this structure (from Google’s resume advice):
Accomplished [X] as measured by [Y] by doing [Z].
- “Reduced API p95 latency by 40% by introducing a Redis cache layer in front of the primary PostgreSQL read replica.”
- “Increased checkout conversion by 12% by A/B testing and shipping a redesigned payment flow.”
- “Reduced on-call alert volume by 60% by migrating from a polling-based health check to push-based telemetry.”
What makes a weak bullet:
- “Worked on the backend API.” (What? How? Result?)
- “Improved performance.” (By how much? What changed?)
- “Collaborated with cross-functional teams.” (This is noise. Everyone collaborates.)
Rules:
- Every bullet has a verb in past tense and active voice.
- At least 50% of bullets have a quantified result.
- No bullet is longer than two lines.
Skills section: don’t lie, don’t understate
List your actual technical skills. Interviewers will probe anything on your resume.
What to include:
- Languages you can write production code in right now
- Frameworks/libraries you’ve used in real projects
- Databases and infrastructure tools you’ve operated
- Tools relevant to the role (e.g., Kubernetes for a DevOps role)
What to leave out:
- “Familiar with X” (if you’d flounder in a 10-minute deep-dive, drop it)
- Dated/irrelevant tools (Flash, AngularJS from 2014)
- Generic filler (“Microsoft Office”, “Jira”)
Honest tiering (optional but useful): Instead of one flat skills list, some candidates break it into “Proficient” and “Familiar” — this manages interviewer expectations and prevents painful moments.
Experience section: what to emphasize
Order matters: Most recent first. Recruiters scan top to bottom.
For each role, include:
- Company, title, dates (month/year)
- 3–5 bullets for your most impactful role, 2–3 for older roles
- The highest-scope thing you did first
Scope signals:
- Mentions of systems/products that served real users at real scale
- Evidence of ownership (“led”, “designed”, “owned”, “shipped”)
- Cross-team or cross-org impact
- Mentorship or hiring (“grew the team from 3 to 8”)
Avoid:
- Describing your team’s work as your own (interviewers probe this — you’ll be exposed)
- Describing your responsibilities rather than your accomplishments (“responsible for” → cut it)
- Internal project names that mean nothing to an outsider (“Worked on Project Hydra” — what is that?)
ATS optimization
Many companies run resumes through an Applicant Tracking System before a human sees it. If the system doesn’t find the keywords it’s looking for, you’re filtered out automatically.
Practical fixes:
- Mirror language from the job description. If they say “distributed systems,” use that phrase — not “large-scale backend.”
- Use standard section headers: “Experience,” “Education,” “Skills.” Not creative names.
- Submit as PDF. ATS parsers handle PDF well.
- Avoid tables, columns, headers/footers, and text boxes — some parsers can’t extract text from them.
The one thing to do right now
Pick your strongest bullet on your current resume. Ask yourself:
- Does it say what you did, or just what you were responsible for?
- Does it have a number?
- Would a recruiter outside your company understand what it means?
Rewrite it to a clean XYZ format. Then do that for every bullet. This alone will put your resume in the top 10% of what recruiters see.