Around 1482, a young man from Florence wanted a job in Milan. He wrote to the Duke, Ludovico Sforza, and his letter is still one of my favorite cover letters.
He didn’t open with where he’d trained or who he’d worked for. He opened with the Duke’s problems. Milan was often at war, so he laid out, point by point, what he could build for it: bridges light enough for an army to carry, ways to drain a moat, covered vehicles, cannons, ships. In peacetime, he could design buildings and move water where the city needed it.
Then, near the very end, almost in passing, he mentioned that he could also paint.
The man who would paint the Mona Lisa put painting near the bottom of his list, because it wasn’t what the Duke needed most. And he offered to prove any of it, wherever the Duke liked.
That was Leonardo da Vinci. Before he was Leonardo da Vinci, he had to sell himself on a piece of paper, just like you.
What did Leonardo get right?
Three things, and every one of them still works:
- He wrote about their needs, not his history. The Duke’s problems came first.
- He listed what he could do, not what he’d done. Capabilities, not duties.
- He offered proof. Not “trust me,” but “let me show you.”
What does that look like on a résumé?
It’s tempting to think your résumé is about you. It’s really about what you can do for the person reading it. So:
- Read the company before you write. What are they building? What’s hard about it? What’s this seat for?
- Put the most relevant thing at the top, even if it isn’t the thing you’re proudest of. Leonardo saved the painting for later.
- Write what changed because you were there. “Responsible for the payments service” says where you sat. “Cut failed payments in half” says why they’d want you.
- Point to proof. Work they can see, a write-up, a talk, a project they can look through.
- Keep it short. Leonardo didn’t need ten pages. Neither do you.
Doesn’t that mean a different résumé for every job?
A different top, yes. The rest can mostly stay put.
Spend a few minutes on the summary and the first few lines for each seat you actually want. Name their problem, and say plainly how you’d help with it. It’s the most useful few minutes of any search.
It matters even more now. When every résumé has been polished smooth by the same tools, the one that names the reader’s real problem is the one that gets read twice. (A warm introduction helps even more than a better résumé, though. More on that in Get out of the pile.)
What if I’m not sure what their problems are?
Ask. Read what the company has written about itself. Look at what the engineering team talks about in public. If someone introduced you, ask them what’s keeping the hiring manager up at night.
When I introduce an engineer, that’s one of the first things I want to know about the seat, because it tells me who will fit. It works just as well from your side.
The short version
- Your résumé is a proposal, not a biography.
- Lead with their problems, and what you can do about them.
- Capabilities and results, not duties.
- Offer proof they can see.
- Tailor the top for every seat you really want.
Write yours for the reader, the way Leonardo did. The masterpieces can come later.
Want a second pair of eyes on yours?
I read these myself. Jonathan Soo Hoo, my partner at Mirror, does the first outreach on some searches; if you hear from him, that’s why.