Blog
One resume per application is the whole game
Recruiters spend six seconds deciding whether to keep reading. The resumes that survive aren't better written — they're better aimed. Here's the tailoring playbook we built Risume around.
How ATS parsers actually read your resume
We ran 1,100 resumes through the four parsers behind most Fortune 500 career sites. Two-column layouts, icon fonts, and text boxes fail in ways you can't see — here's the autopsy.
Jun 242026Why we typeset resumes like LaTeX
Word processors reflow; typesetting commits. What we learned rebuilding hyphenation, widow control, and optical margins for a one-page document that has to survive print.
Jun 172026What recruiters see in the first six seconds
Eye-tracking studies agree on where the gaze lands: name, current title, current company, dates. Design for the F-pattern scan and the deep read takes care of itself.
Jun 102026Quantify everything: turning duties into outcomes
"Responsible for backend services" tells a reader nothing. A framework for excavating the numbers you forgot you earned — scale, money, time, and people.
Jun 32026Match scores, explained
The number in the corner of your editor isn't magic. How Risume weighs skills, recency, and role language against a job post — and what moves the score honestly.
May 272026Designing an API that renders paper
Most APIs return JSON. Ours returns a typeset document with page breaks that can't be wrong. Notes on building render infrastructure for the Risume API.
May 202026Writing the career gap without flinching
Gaps read as risk only when they read as evasion. Three honest framings that keep the interview on your work — and the one move that always backfires.
May 132026The one-page rule is dead. Long live the one-page rule.
Ten years of hiring-manager surveys say the rule survives every attempt to kill it — but the reasons changed. When a second page earns its keep, and when it costs you the call.