Four readers decide whether you get the call, and they want different things. This is how to write one page that survives all four — and how to grade your own before you send it.
Long before a conversation happens, the document is speaking for you — and it is inspected more than once on the way in. Its job is not to record that you survived your last role. It is to argue that you are ready for the next one, in front of four separate readers who each want something different.
A resume that wins one reader can lose the next. The whole craft is satisfying all four at once.
Every choice on the page answers one thing: which of my four readers does this serve, and how fast does it help them say yes?
Treat the page as a pitch for the job ahead of you, not a receipt for the one behind you. To make that case it has to hold up in front of four audiences, each studying it more closely than the one before.
Structure earns you the parser. Speed earns you the recruiter. Evidence earns you the interviewer. Impact earns you the hiring lead. A page tuned for one can quietly fail the next.
Auditing of the major tracking platforms — Workday, Greenhouse, Ashby — shows none of them deploy software to reject AI-written resumes outright, largely because of the liability that would create.
The real filter is the human recruiter who reads it next. So do not spend energy gaming the machine with keyword tricks or hidden white text. Use relevant keywords naturally, keep formatting clean enough to parse, and write for the humans on the other side of it.
Every trick aimed at the parser — stuffed keyword blocks, invisible text, fake headings — is visible the moment a human opens the file. You are optimising for the reader who was never the gate.
The machine decides whether you are readable. The people decide whether you are worth reading.
The parser spends milliseconds. The recruiter gives you seconds. The interviewer gives you minutes — but only because the first two already said yes. You are not writing for the reader with the most time. You are writing for the one with the least.
Read your resume four times, once as each reader. Mark every line that serves only you — the writer — and none of them. That set is your first edit.
The problem is rarely too little on the page. It is too much of the wrong thing. Every throwaway sentence drains the power of the good ones next to it — so subtract before you add.
Because the human recruiter is the filter, and because nearly every application they read was drafted by a chatbot, pristine corporate-speak has flipped from asset to warning sign. Six hundred words of polished, generic prose read as artificial.
Slightly imperfect rhythm and unusual, highly specific vocabulary now read as authentically human — and that earns trust. Strip the words every model reaches for: spearheaded, leveraged, testament to, results-driven, passionate. Replace them with precise vocabulary from your actual field.
The goal is not polish. It is that only you could have written it.
Results-driven professional passionate about leveraging cutting-edge solutions to drive synergy across cross-functional teams.
I build internal tools that ops teams actually keep using after launch. Most of my work is Python and boring reliability problems, which I like.
Search your draft for the five filler verbs above. Delete each and rewrite the sentence using a word someone in your field would say out loud.
Cleverness is not the goal — effortless navigation is. People arrive expecting to find things in a certain place. An inventive layout does not impress them; it makes them work harder to find what they came for.
Experienced. Lead with work experience; push education and projects down. A dense recent history is what a hiring manager wants first.
Fresher or switcher. Do not open with a near-empty Experience heading that announces what you lack. Move projects up, often directly under the summary. A switcher leads with the projects and transferable wins that point at the new field.
Add GitHub or a portfolio only if the work there is strong — an empty profile does more harm than no link. If work authorisation is relevant, state it plainly. City and country is enough; the full street address is a liability, not a credential.
Never pour every keyword into one undifferentiated block. Divide them by category so a manager can spot your capabilities in under three seconds.
Skills: Python, React, SQL, Docker, AWS, Figma, Kafka, Redis, Git, Java, REST, Agile, Jira, Node, MongoDB…
Backend: Python, Node.js, PostgreSQL, Redis · Infra: Docker, AWS, Kafka · Frontend: React, TypeScript
List only what you can discuss under questioning. Everything on that list is fair game for a probe — twenty shallow skills are worse than eight you can defend.
Group your skills into three or four named tiers, then delete any entry you would not want to be asked about for ten minutes.
Two or three sentences, no more: what you do, where you are sharp, and why this role in particular. No section gets read more, or squandered more often.
A recruiter uses the summary to decide in a heartbeat whether the rest is worth their time. The trouble is that AI-generated openers all blur together, and readers have trained themselves to glide straight over them.
Swap the fog for detail only you could have supplied — the field you operate in, the problems you have cracked, the scale you have worked at.
Seasoned engineering leader with 20 years of experience delivering high-impact solutions across diverse industries.
I take payments systems from flaky to boring. Backend engineer, eight years on high-throughput fintech infrastructure, most recently owning a platform moving $2B a month.
Motivated professional looking to transition into product management, bringing transferable skills and a passion for technology.
Six years running retail ops taught me where products break in the real world. Now I build the roadmap instead of absorbing the fallout — most recently shipping the returns flow that cut our support volume by a third.
Enthusiastic and hardworking recent graduate seeking a challenging role to utilise my skills and grow with a reputed organisation.
Final-year CS student who builds and ships small tools rather than following tutorials. Comfortable in Python and React; happiest debugging the thing nobody else wants to touch.
Opening with "20 years of experience" is now a structural liability — screeners and founders read it as rigidity, not authority. Lead with your value thesis instead: the exact business problems you are equipped to solve today.
"Twenty years" is read as a liability. "The person who fixes X" is read as a hire.
Write your summary twice — once naming the problem you solve, once naming the years you have served. Show both to someone in your field and ask which one they would call back.
A recruiter did not ask for your job description back. "Responsible for managing a team" is a phrase a hiring manager's eyes slide off — it says nothing about how good you were. Flip the order on every line: name the result first, then the method, then the scale.
Move past task-based lines and even STAR. The structure that works now is Result + Metric + Context & Scope — but be careful: hiring managers are sceptical of clean, contextless metrics, which read as inflated AI output.
Drove 32% improvement in operational efficiency through cross-functional process optimisation.
Took our regional logistics unit from $40M to $110M while cutting customer churn in half, by migrating legacy data to a serverless platform.
The first line is unfalsifiable. Thirty-two per cent of what, measured how, against what baseline? A hiring manager cannot picture it, cannot probe it, and has read forty like it this week.
The second names a business, a range, a second-order effect, and the mechanism. It invites a follow-up question — which is what a resume line is for.
Owned · rebuilt · migrated · cut · shipped · negotiated · recovered. Each implies you made the call and lived with the result.
Assisted with · involved in · participated in · supported · helped drive. Each implies you were nearby when it happened.
If a bullet could belong to anyone else with your title, it is not a bullet. It is a job description.
Underline every verb on your resume. Any line whose verb only proves presence gets rewritten or cut.
The same rewrite at three career stages. Watch what changes: not the length, but how much of the line only you could have written.
Worked on migrating the legacy system to microservices.
Owned the auth-service extraction during our monolith split — moved 12 endpoints with zero downtime, and wrote the rollback plan we used twice.
Built an e-commerce website using React, Node.js, and MongoDB with cart and payment features.
Built and deployed a billing app for a local shop; three staff use it daily. Rewrote the sync layer after the first version lost sales during power cuts — now queues offline and reconciles on reconnect.
Experienced operations manager transitioning into data analytics, with strong analytical and problem-solving skills.
Ran the returns desk for a 40-store retailer, then built the SQL model that found why 60% of returns came from four SKUs. The fix cut return volume by a third.
The strong fresher example admits something broke. That is not a weakness to edit out — interviewers trust specific, slightly imperfect stories far more than flawless ones, because real work is full of rollbacks, and a candidate who names one has usually done the work.
The switcher rewrite does not hide the old job; it uses it. The operations history is why the analysis was credible. The new-field verbs do the positioning.
A number means nothing without scale. If the reader will not recognise your employer, add a context line under the company name — [B2B SaaS · $15M ARR · 80 employees]. The same achievement reads completely differently at a five-person startup and a global enterprise.
The goal is not the most impressive line. It is the most checkable one.
Every weak version describes a category of work. Every strong version describes one specific instance of it — with the thing that went wrong, the number that moved, or the constraint that made it hard.
That is the entire trick. Categories are cheap and everyone claims them. Instances are expensive, which is exactly why they are believed.
Take your three weakest bullets and rewrite each as Result + Metric + Scope. If you cannot find a metric, turn the page.
"My work isn't measurable" is the most common objection in this whole craft, and it is almost always false. The number exists. You just have not asked the question that produces it.
Pick a bullet with no number. Run it through all five. At least one will fire.
"~15 hours a week" and "roughly 300 records a day" are honest and usable. A precise-looking 32% you cannot reconstruct is neither. If you would not survive the follow-up question, do not write it.
Notice that none of these require a dashboard. They require you to remember the shape of the work and estimate honestly.
"Handled 300 concurrent users during college-fest registration" is a real number. Nobody gave it to you — you counted.
Take every unquantified bullet you have. Run each through volume, time, money, people, quality. Write the number down even if it feels small — small and specific beats large and vague.
Write for where you are going, not where you sit. Someone chasing a director title cannot read like a manager on the page — the resume has to bring strategic thinking, cross-team leadership, and long-range planning to the surface.
Hold your current work against the role you are reaching for. Give more room to the parts that point that direction, and quiet the routine that does not. Nothing here is fabricated — you are choosing which real threads to pull forward.
For a career switcher this is everything. Reframe old-field wins in the language of the new field, and lead with the projects, courses, or freelance work proving you can already do the target job, even if nobody has paid you for it yet.
Skills have a shorter shelf life than ever. Employers care less about what you knew five years ago than how fast you absorb something new today.
Do not bury this in Education — weave it into your history. Point to moments where you were handed an ambiguous problem, learned a new method on the fly, and delivered anyway.
You will not be replaced by AI, but you can be replaced by someone who knows how to use it. Listing "ChatGPT" under skills looks lazy.
Prove fluency through outcomes instead — work shipped faster, scale reached, process automated. Framing AI as a multiplier for your own judgement signals the candidate teams are hunting for.
Skills: ChatGPT, Claude, prompt engineering, AI tools.
Rebuilt weekly client reporting as an AI-assisted pipeline — four analysts' Monday mornings became a 20-minute review, at the same error rate.
Choose which real threads to pull forward. That is positioning, not fiction.
Scope separates the levels, and it is legible in one line. An IC line names what they built. A manager line names what the team shipped. A director line names the system that made shipping repeatable.
Reaching one level up? At least two bullets should already read at that level.
Print the description of the job you actually want. Highlight every line of your resume that speaks to it. If the highlights are all in the bottom half, reorder the page.
Most people over-engineer this. They invent filler roles, stretch dates, or write a paragraph of pre-emptive defence. All three make the thing worse. The resume's job is to survive the scan — not to litigate your history before anyone has asked.
The instinct to conceal is the thing that hurts you. A dated, labelled gap reads as a life. An unexplained hole reads as something being withheld.
Acme Ltd · 5 months
Beta Corp · 7 months
Gamma Inc · 4 months
Independent Consultant · 2023–2025
Data engagements for Acme, Beta, and Gamma — three migrations delivered, each inside a fixed 6-month window.
If you studied, freelanced, volunteered, or shipped anything during the gap, that is experience — put it in the history with a real line. A break spent learning is a stronger signal than a job spent coasting.
Do not pre-answer the question. Make the page survive the scan, and keep the context for the conversation.
Lay your dates end to end. Any unexplained gap over four months gets one labelled line. Any run of three short roles gets grouped under a single heading.
A handful of layout choices, made before anyone reads a word, decide whether they read at all.
Give ninety per cent of the page to the last seven to ten years. Anything older belongs in one un-bulleted line at the bottom titled Earlier Career History. This cuts clutter and reduces age bias in a single move.
Lead with the problems you solve now, not the length of the career. The reader is buying a solution, not a timeline.
Copy all the text out of your finished PDF and paste it into a blank document. That is roughly what the screening software sees. If sections arrive out of order, words merge together, or letter-spaced headings shatter into single characters, fix the formatting before you send it anywhere.
Two-column layouts, contact details inside the header/footer region, and headings typed with spaces between letters. All three look fine to you and shatter on extraction. Test before you trust them.
Run the parse test now, on the file you last sent out. Fix whatever comes back scrambled before you apply to anything else this week.
Nobody reads one without the other. A recruiter who likes your resume opens your profile within the minute — and the first thing they do, without meaning to, is check whether the two agree.
None of this requires the same words. It requires the same facts. Discrepancy is the risk; duplication is not the fix.
The LinkedIn headline does the same job as the resume summary, in a tenth of the space, and it follows you into every search result and comment thread. Make it the problem you solve — not your job title, and not "Aspiring."
Senior Operations Manager at Acme Ltd
I fix the handoffs that make retail ops expensive · Supply chain & returns · 40-store scale
Open to work. The recruiters-only setting is visible to anyone with a hiring seat and invisible to your employer. The green frame is public. Pick deliberately.
Your custom URL. A clean /in/firstnamelastname costs one minute and appears on every resume you send from now on.
Open your resume and your profile side by side. Read only the titles, dates, and company names. Fix every mismatch before you touch a single word of prose.
Firing one identical PDF at a hundred openings stopped working a while ago. A one-size-fits-all application gives itself away immediately — but tailoring is not rebuilding your history for every posting. It is moving the spotlight.
Keep two or three versions, one per role type you target, and send the closest match. Then spend real tailoring effort only on the handful of roles you genuinely want — sharpen the summary, reorder the bullets, lift the most relevant experience to where it is seen first.
Every trick eventually gets detected — hidden text, keyword stuffing, inflated metrics. Skills do not. Fix the resume once, properly, then put your energy into applying early and building work worth writing about.
Treat the resume as a living document and you stop being another applicant on a screen. You become the obvious solution to their problem.
Build your two or three base versions this week. Tailor deeply only for roles you would accept tomorrow.
Twenty-five checks, one point each. Be honest — the version of this that helps you is the one where you score badly the first time.
The score you get today is not the point. The three boxes you cannot honestly tick are.
Your Resume Is a Marketing Tool · A Field Guide, Practitioner Track · AIMasterz Library, aimasterz.com/guides. Companion volumes: Your AI-Driven Career Pivot in 90 Days · Find Your First 10 Clients in 60 Days.
Delete before you add. Result before duty. Specific before polished. Checkable before impressive.
— END · FIELD GUIDE · PRACTITIONER TRACK