August 4, 2026
An editor, not a generator
Most resume tools start from a blank page. You paste in a job description, answer a few prompts, and a few seconds later you have paragraphs of confident, well-formatted text that reads like a resume. It's fast. It's also not obviously yours, because a tool built to generate text and a tool built to know your history are doing two different jobs, and most resume tools only do the first one.
Margin was built to do the second job.
Two different machines
A generator is built to produce text. Give it a prompt, and it fills the space between your input and a plausible-sounding resume, drawing on patterns learned from other people's resumes, not your work history. Whatever sounds right for the role, it writes down. That's not a flaw specific to one product; it's what generation is built to do. Autocomplete doesn't know what's true about your last five years. It knows what tends to read well.
An editor works differently. It starts from your actual Master Resume and the actual posting you're applying to, and every suggestion it makes points back to one of the two: the line in the posting that asked for it, or the line in your resume it's drawn from. That's the whole mechanism. Not smarter writing: a shorter distance between what it suggests and what you can actually stand behind.
What that looks like in a Tailored Review
Open a Tailored Review and every suggested change comes with three things attached:
- A source. Each edit cites the line in the posting that prompted it ("drives retention," "0→1 ownership," whatever the role is actually asking for), so you're looking at a match, not taking Margin's word for it.
- Reasoning in the margin. Not a silent rewrite. An explanation of why this line moves up, why that phrase gets cut, sitting next to the change itself.
- A hold on your approval. Nothing lands in your resume until you accept it. You go through suggestions individually. The resume on the other side is the one you signed off on, not one a model finished for you while you weren't looking.
That third point is the one that actually separates an editor from a generator. When a suggestion doesn't have a clean match anywhere in your Master Resume, it stays visible in the ledger as an unmatched suggestion: disclosed, not inserted. What fills that gap, if anything, is yours to decide.
A cut line and a buried one
Take a line like "Responsible for various initiatives." A generator might rewrite it into something more impressive-sounding without knowing what those initiatives were. An editor asks a narrower question: is there a number or an outcome for this already sitting a few sentences down, buried where a nine-second skim will never reach it? If there is, that's what moves up. If there isn't, the line gets cut (filler goes first), and the space it leaves is yours to fill, not the model's.
Why the extra step is the point
An edited resume takes longer to produce than a generated one, because you have to read the suggestions and make the calls a generator would make for you. That's not friction Margin is planning to remove. It's the actual mechanism the rest of this depends on: a resume you didn't read isn't one you can defend across a table from someone asking you to walk through it.
That's where a generated line tends to come apart: not on the page, but in the follow-up question, when a sentence that was never built from anything you did has nowhere further to go. An edited line holds up under the same question, because it traces back to something true and something the posting actually asked for. You can defend it, because you're the one who approved it going in.
The truest version, not the most polished
None of this is caution for its own sake. It's the difference between a tool that writes at you and one that reads you first: a second reader on your side of the desk, not a text machine standing in for one. The resume that comes out the other side isn't the most polished one a model could produce from scratch. It's the truest version of the one you already had.