The document
A resume the parser and the person can both read
What goes wrong when a resume is designed for the screen and parsed as junk, and how Resume Studio keeps one reading order from the profile you already wrote.
The file looks finished. The parse does not.
The usual failure is not a missing section. It is a file that looks expensive on a laptop and arrives in an applicant-tracking system as a pile of out-of-order lines: a skill chip sitting where the dates should be, a two-column skill cloud that the parser reads top-to-bottom as if it were a sentence, a headshot that eats the first 400 pixels of a one-page screen.
The other failure is quieter. You export from Word, the fonts substitute, and a hiring manager prints a page where the dates have slipped onto the next line. You cannot see that from the original file. You only see that the callback never comes, which is not evidence of anything except that you cannot inspect the artifact they actually received.
Neither of those is a writing problem. They are a layout-and-export problem sitting on top of writing you may already have done.
One profile, a single-column canvas, a score against the posting
Studio does not start from a blank decorative page. It dresses the profile you already built in intake or import: name, roles, dates, bullets, skills. You pick a public template. The canvas keeps a single reading order so a parser that walks top to bottom meets the same sequence a person does.
Paste the posting you are actually applying to. Studio scores the document against that text and flags bullets that still read as duties ("responsible for the backlog") rather than as work with a number. You rewrite those lines on the canvas. Export is a PDF of that version, not of a parallel Word file you forgot to update.
- Open the profile that intake or import already filled.
- Pick a public template. The body stays one column.
- Paste the job. Read the score and the flagged lines.
- Edit the flags. Export that version.
What Saskia Vellam gets on the canvas
This is a fictional example CV, written to show the template. It is not a real person.
Saskia Vellam is a fictional software engineer in Edinburgh. Her profile already has the charge-endpoint line: p95 latency from 820ms to 210ms by moving two joins behind a cache. Studio's job is to keep that sentence intact through template and PDF, not to invent a second one.
Against a backend posting that asks for latency work and tests, the canvas can show the 820ms-to-210ms bullet and the coverage bullet (41% to 78%) as evidence. It cannot show a Kubernetes line she did not write. The score is a match against the pasted ad, not a claim about a hire.
When Studio will not help
If the profile is thin, Studio will export a thin PDF. A template will not add a year of work. If you have not pasted a job, the score has nothing to score against. And Studio will not submit the file for you — it stops at export.
Questions
- Does Resume Studio write the resume for me?
- No. It lays out the profile you already wrote, flags duty-style bullets, and exports a PDF. The sentences still have to come from your work.
- Why not a two-column infographic layout?
- Many parsers walk the page top to bottom. A second column of skill chips is often read as if it were part of the story. Jobtiv's public templates stay on one reading order for that reason.
- Do I need an account?
- Yes. Studio sits behind an account because it is editing your profile, not a public demo page.