Why Most Resumes Get Buried Before a Human Ever Reads Them
Unlocking Career Velocity The Ultimate Guide To Cv Rrr For Professional Success
I spent about six years running resume screening for a mid-size tech company in London. We'd get 400 applications a week for senior engineering roles. The tool we used couldn't read PDFs well, so we converted everything to plain text first, then ran keyword scoring against the job description. Here's what I noticed after looking at thousands of applications: 90% of the ones that made it past the initial filter had one thing in common. They were boring. Not bad, not poorly written, just safe and generic enough to score well on a system that couldn't tell the difference between relevant and irrelevant keywords.
The RRR framework I'm about to explain is simply Results, Readability, Relevance. That's it. Three principles that actually work together instead of fighting each other like most career advice tells you to do. Most guides tell you to optimize for keywords AND write compellingly AND quantify everything. That's three separate goals that often contradict each other. RRR folds them into one workflow.
Results means every bullet point answers the question "so what?" This is where people mess up most. They list responsibilities instead of outcomes. "Managed a team of five developers" tells me nothing. "Shipped three microservices in six months while reducing incident response time by 40%" tells me you can deliver and you understand metrics. I remember a candidate once — let's call him Daniel — who had 87% on our ATS score despite having a mediocre background. His resume was stuffed with keywords from the job description. But he'd copy-pasted them without context. He listed "Agile," "Scrum," "Jira," and "CI/CD" as standalone skills with no demonstration of actually using them. I flagged his application for manual review out of curiosity and he tanked the interview because he couldn't speak to any of those tools beyond naming them. Keyword stuffing has a half-life of about three years now. Most screening tools weigh contextual usage much higher than simple presence. Readability is the part nobody talks about because it's harder to quantify. A resume needs to be scannable in under eight seconds. That's the average time a recruiter spends on an initial pass. Your formatting should guide their eye to the right information without them having to hunt. Section headers should be consistent. Bullet points should follow a pattern. Dates should align. If a recruiter has to work to find your job title at a company, they've already lost patience. I once saw someone use a two-column layout that the ATS parsed as a single column of garbled text. Their entire resume read like nonsense to the screening tool. They were qualified for half the roles they applied to. The fix was simple — go back to a single-column format with clear headers and standard section ordering. Relevance means every single line earns its place on the page. If it doesn't directly support the role you're applying for, cut it. This is the hardest principle to follow because we all want to show range and versatility. But relevance is a razor. A software engineering role doesn't care about your barista job from four years ago unless it demonstrates something genuinely transferable like handling high-pressure customer interactions during a staff shortage. I've seen senior candidates include their college GPA three positions into their career. It takes up space that could be used for something that actually matters. Age discrimination is real in some industries, and certain details — graduation year, wedding photo, hometown — signal age without meaning to. Keep it to the last ten to fifteen years of experience unless you have a specific reason to go further back.
The Practical Workflow
Start with the job description. Print it out or highlight it digitally. Circle the hard requirements — things like "5+ years Python," "experience with AWS," "managed budgets over $1M." Those are your relevance anchors. Now take your current resume and go through it line by line. Every bullet point that doesn't connect to one of those anchored requirements needs to either be reframed or deleted. Don't just delete — reframe first. Sometimes a responsibility seems unrelated but contains a transferable skill if you describe it differently.
Then test for results. Go through each remaining bullet point and ask whether it states an outcome or just a duty. If it's a duty, rewrite it with numbers, percentages, or concrete deliverables. If you don't have exact numbers, estimate conservatively. "Improved process efficiency" becomes "Reduced deployment time from 3 hours to 45 minutes by automating the build pipeline." Even approximate numbers are better than vague claims because they give the reader something to latch onto.
Finally, test for readability. Hand it to someone who doesn't know your background. Ask them to find three things in under 30 seconds: your current role, your most recent promotion, and a key achievement. If they can't find all three, your formatting is working against you. Common fixes include making job titles slightly larger than company names, using bold for metrics, and keeping bullet points to one line when possible.
Edge Cases That Break the Framework
Academic and research roles work differently. A CV for an academic position is expected to be comprehensive — publications, conferences, grants, teaching experience. The RRR framework still applies but relevance means including everything in your field, not cutting for brevity. The same goes for government and military applications where specific forms and structured experiences are mandatory. Don't try to be clever there. Follow the instructions exactly.
Creative roles also need a different approach. Designers, writers, and artists should be linking to portfolios that demonstrate results rather than describing them on the resume. The resume in those cases is a map, not the territory. Keep it tight and functional, let the portfolio do the heavy lifting.
I encountered one edge case that genuinely surprised me. A candidate applied for a product management role at a fintech company. She had no direct fintech experience, no product management title, and her resume scored 62% on our relevance metric. But her results bullets showed she'd reduced customer churn by 23% at a healthcare startup by redesigning the onboarding flow. That's a product management result even if the title wasn't there. I recommended she apply anyway and the hiring manager agreed. Contextual relevance — showing you can do the actual work — beat keyword relevance every time. The workaround I used in that case was to add a short "Selected Achievements" section at the top of the resume that highlighted transferable results before the chronological experience started. It shifted the recruiter's focus from what she hadn't done to what she had done.
What This Doesn't Fix
A strong resume won't compensate for a genuine employment gap that raises red flags, nor will it help if your track record shows job-hopping across three companies in two years. The RRR framework optimizes what's on the page. It doesn't create substance. If you're early in your career with limited experience, focus on projects, internships, and quantifiable achievements from any context — even academic or volunteer work counts if you frame it properly.
There's also a hard limit on length. For most people with less than ten years of experience, one page is sufficient. More than fifteen years and you're probably justified in going to two pages. Three pages is almost never necessary unless you're in academia or a C-suite role where publications and board positions are expected. Going beyond two pages signals either poor judgment about what's relevant or an inability to edit, which are both negative signals to recruiters.
A Note on ATS Systems
Applicant tracking systems vary wildly in quality. Some companies use cheap, outdated tools that can't parse tables or even standard fonts. Others use modern systems from large vendors that handle complex formatting better. There's no way to know which you're dealing with when you apply. The safest approach is to assume the worst-case parsing scenario and format accordingly. Use standard section headings like "Experience" and "Education." Avoid tables, columns, graphics, or text boxes. Save as PDF unless the application specifically requests DOCX. Stick to common fonts like Arial, Calibri, or Helvetica at 10 to 12 point size. This covers roughly 95% of ATS implementations in the wild.
The remaining 5% will reject perfectly fine resumes due to poor system design. You can't control that. Submitting your application through a referral or reaching out to a hiring manager on LinkedIn directly will bypass the ATS entirely in most cases, which is why networking isn't just corporate advice — it's a practical workaround for a broken system.
