The MeritSlate blog
Deep dives on the hiring machine.
ATS internals, the real math behind resume scoring, and honest tailoring — written by the team building the deterministic Merit Score Score engine. No recycled listicles.
What actually happens after you hit submit
The real sequence between your application and a response — parsing, screening, disposition codes — and what the timing of a rejection tells you about where you lost.
In this article
- 01The sequence
- 02Reading the timing
- 03Why so many applications get no reply at all
- 04What the recruiter is actually looking at
More articles
Two-column resumes and the ATS: exactly what breaks
Why multi-column resume layouts scramble in parsing, what the extracted text actually looks like, and how to keep the design you like without losing a section.
How to tailor a resume in 20 minutes (without rewriting it)
A repeatable per-application process: build a master resume once, then reorder, retitle and re-word against each posting in under half an hour.
Resume summary vs objective: which to write, and what to put in it
Why the objective statement died, what a modern resume summary actually does, and a three-line formula with worked examples for career changers and new grads.
What to put in a resume's contact section (and what to leave out)
Whether to include your address, photo, LinkedIn URL and pronouns — plus the contact-block mistakes that cause a parser to lose your phone number entirely.
Writing a resume for remote jobs
What actually changes on a resume when the role is remote — location handling, time zones, evidence of distributed work, and the filters remote postings really run.
LinkedIn and your resume: keeping two documents that don't contradict
Recruiters search LinkedIn and read your resume. How to keep titles, dates and skills consistent across both — and why the two documents have different jobs.
How to read a job description before you apply
How to tell a hard requirement from a wish, spot the roles that aren't really open, and decide whether a posting is worth twenty minutes of your time.
How many bullet points per job should a resume have?
How many bullets to write per role, how to order them, how long each should be, and why the oldest job on your resume should have the fewest.
Functional vs chronological resumes: why the functional format fails
The functional (skills-based) resume breaks ATS parsing and reads as concealment to recruiters. What to use instead when your history isn't a straight line.
Writing a resume with no experience (that isn't padding)
What to put on a first resume when you have no professional history — how coursework, projects and unrelated jobs become real evidence, and what to leave off.
Employment gaps on a resume: what to do, and what never to do
How to present a career break so it stops being a question — where to put it, how much to explain, and why adjusting your dates is the one move that turns a non-issue into a fireable one.
Certifications on a resume: where to put them and how to name them
How to list certifications so both a keyword matcher and a human find them — naming, placement, expiry dates, and which ones are worth the line.
The career-change resume: surviving a system built to match your past
Keyword matching scores you against the job you had, not the one you want. How to structure a career-change resume so transferable experience actually counts.
The best fonts for a resume (and the ones that break parsing)
Which resume fonts survive ATS extraction, what point size and margins to use, and why icon fonts and exotic ligatures turn your resume into unicode garbage.
Resume keywords: how an ATS decides which words matter
How to find the ATS keywords a job description actually weights, where to put them, how to handle job titles and soft skills — without keyword stuffing.
Not getting interviews? Run this diagnostic before rewriting anything
Why your resume gets no response: a four-step diagnostic that isolates parse failures, keyword gaps, seniority mismatch, and weak evidence — plus how to read the rejection pattern.
The ATS-friendly resume format, tested against nine parsers
An ATS resume format checklist derived from running real resumes through nine vendor parse simulations — section by section, what breaks, what survives, and which rules are myths.
Quantify your resume: metrics and action verbs are 24% of the score
How to quantify resume accomplishments in any job — including roles that feel unmeasurable — and pick strong action verbs. The two writing axes worth nearly a quarter of your Merit Score.
Do cover letters still matter in 2026?
When a cover letter changes the outcome, when it is ignored, whether an ATS reads it, and how to write one in twenty minutes that is grounded in your actual resume.
PDF vs DOCX: which resume file format should you send?
Whether an ATS can read PDFs, how parsers extract text from PDF and Word files, where each format fails silently, and how to export a resume that survives the trip.
How long should a resume be? One page, two, or who cares?
What resume length actually affects — parsing, keyword coverage, recruiter skim time — plus how far back to go, what to cut, and when CV rules replace resume rules.
Anatomy of a Merit Score
Exactly how our fully deterministic, 9-axis Merit Score is calculated — the real weights, what each axis measures, what counts as a good score, and what the number deliberately can't see.
How an ATS actually reads your resume (2026 edition)
A technical walkthrough of how modern Applicant Tracking Systems ingest, parse, structure and rank resumes — what really filters you out, and which popular advice is folklore.
The line between tailoring your resume and lying
How to rewrite a resume for a specific job without fabricating experience — what background checks actually verify, and how to audit AI-written bullets for invented facts.
Reading about ATS filters is step one. Beating them is step two.
Free account · 2 full scores every day · no credit card.