The 2-Pager
A new format for your portfolio
Last week yet another LinkedIn coach was talking about a “2-pager” for executives: not a CV, not a pitch deck, but a simple document that makes introductions and networking much easier: the 2-Pager.
Most Software Engineers will ignore this advice because it looks “too business-y”.
That’s exactly why you should steal it.
If you hate the idea of “selling yourself”, the 2-pager is one of the cleanest hacks you can adopt: no cringe, no storytelling theater, just a clear spec of who you are and where you fit.
Let’s port it into our world.
What a 2-pager really is
Forget the coach-speak.
A 2-pager is a lightweight personal doc, usually 1–2 pages, that answers five brutal questions:
Who are you.
What you’ve actually built.
What you’re scary-good at.
What proof you have.
What you want next.
No fluff, no “driven, passionate, highly motivated” nonsense.
Think of it as:
Your README.md as a senior engineer, formatted for humans instead of GitHub.
Not an application.
A conversation starter.
Why engineers need one even when not job searching
Right now, most devs show up to networking calls naked.
Best case: random small talk, a couple of generic questions.
Worst case: “So… if you hear about something, let me know.”
And then silence.
A 2-pager fixes three classic bugs:
It makes you easier to forward.
When someone wants to introduce you, they need something clear to attach.It makes your value legible.
Non-engineers do not understand “I work on backend stuff in Go”. They understand “I helped reduce checkout failures by 30%”.It makes you remembered.
A clean 2-pager is 100x more memorable than “Senior Engineer at Company X, working on internal tools”.
You are basically reducing friction in the “referral pipeline”.
How a 2-pager looks for a Software Engineer
Let’s make it concrete.
Page 1 and (maybe) page 2.
Plain text, simple layout. No design degree needed.
You can structure it like this:
Header
Name, role, location.
One line: “Senior Backend Engineer focused on B2B SaaS, payments, and platform reliability.”
Who I am (short intro)
3–4 lines, max.
What kind of problems you like.
What type of teams you thrive in.
1 sentence about your edge (e.g. “I sit between engineering and product and speak both languages”).
What I’ve built
3–6 bullets, each one like a mini case study.
Context → Action → Result.
“Led migration from legacy monolith to modular services for payments, cutting checkout latency by 40% and incidents by 25%.”
(→ FYI I have already written an article about how to write this type of sentences)
Avoid tech-dump bullets like “Kubernetes, Docker, Terraform, Kafka, Redis…”.
Lead with impact, not tools.
Superpowers
3–5 bullets that describe how you work when you are at your best.
Examples:
“Turn vague product ideas into technical plans that non-tech stakeholders understand”
“Take over messy legacy systems without complaining and gradually refactor them”
“Calm in production incidents, fast at isolating root causes”
Proof points
Links only:
GitHub (if not empty).
1–3 talks, posts, or PRs you’re proud of.
Open-source contributions, side projects, conference appearances.
No links? Start small: a single post where you break down a bug you fixed.
What I’m looking for
Even if you are not “looking”, give direction.
“Types of problems I’m excited about in the next 2–3 years.”
“Ideal environment” (stage, domain, team shape).
You can keep it broad:
“Product engineering roles where I own a problem end-to-end and work close to business impact.”
When to actually use it
Engineers think documents live in folders.
This one lives in conversations.
You use a 2-pager when:
A friend says, “I can introduce you to our Head of Eng”
You reply, “Perfect, here’s a short 2-pager that explains what I do. Feel free to forward it”You have a coffee with someone from your dream company.
After the call: “Thanks for your time; here’s a concise overview of my background in case it’s useful to share internally”You speak at a meetup.
On follow-up: “If you ever need someone with this profile, here is a 2-pager that sums up my work”
Notice what you are doing.
You are not begging.
You are making it easy for other people to sell you when you are not in the room.
How to write yours without cringing
If you are a dev, the main blocker is not Canva.
It’s shame.
You feel you are “bragging”.
So here’s the trick: write it like you write post-mortems.
Be specific.
Stick to facts.
Attach numbers when you can.
Remove hype.
You are not saying, “I am a 10x engineer”.
You are saying, “Here is the diff I have made to real systems”.
If it helps, open a doc and literally start from this prompt:
“If a friend wanted to pitch me for a role tomorrow, what 2 pages would I want them to have in front of them?”
Write in your natural voice.
Then refactor:
Kill adverbs (“very”, “highly”, “extremely”).
Remove any sentence that doesn’t increase clarity.
Cut it until a busy VP could scan it in 45 seconds.
Save as PDF.
Put a short link in your email signature or LinkedIn contact info.
And then, next time someone says, “Sure, send me something about you”, you won’t send yet another lifeless resume.
You’ll send a 2-pager that actually represents how you think and what you build.