The Three Roles framework
Give each professional identity its own sentence, then connect them.
The Three Roles framework is a focused variation of the Thematic structure. It assumes the subject occupies three named roles — writer-engineer, doctor-investor, designer-musician — and gives each one a sentence. The role names anchor the reader; the verbs inside each sentence supply the proof. It is the most efficient way to write a bio for a portfolio career without the bio sounding scattered.
When to use it
- Portfolio-career professionals.
- Newsletter writers who also have a day job.
- Operator-investors and angel investors.
- Designers and engineers who also write or teach.
- Academics with industry roles, and vice versa.
When to avoid it
- Single-role professionals — the framework will manufacture roles that do not exist.
- Short bios where three sentences exhaust the space.
- Bios for audiences that distrust portfolio careers (some institutional contexts).
The steps
The 4-step structure
- 1Name the three rolesEach role is a noun, not a verb. Writer, investor, teacher, founder, board member, advisor, parent — the named roles the subject genuinely occupies.
- 2One sentence per roleEach sentence opens with the role and contains one defensible verb. 'As an investor, she has backed seventeen pre-seed companies in marketplaces and fintech.'
- 3Connect the rolesAdd a sentence that names what makes the combination coherent — what the subject would say is the through-line across them.
- 4Land in the presentClose with a sentence that states where the subject lives and what they are currently most focused on.
Worked example
The framework in action
Setup
Sample subject: a portfolio-career creator who codes, writes, and invests.
Bio · 97 words
As an engineer, Jamie Park is a staff infrastructure engineer at Vercel, where she leads the platform's edge compute team. As a writer, she edits The Inner Loop, a weekly newsletter on developer ergonomics that reaches twenty-six thousand engineers. As an investor, she has angel-checked twenty-four developer-tools companies since 2020. The three roles share a single concern — making the path between writing code and shipping it shorter for the people doing the work. Jamie lives in Vancouver and is currently helping her newsletter readers move from Postgres to libSQL at innerloop.dev.
Pitfalls
Common ways this framework fails
- Inventing a role to make three. If there are only two, use a two-role bio.
- Failing to name the through-line, so the reader is left with three disconnected sentences.
- Choosing roles at incompatible scales — 'CEO, hobbyist gardener' reads oddly.
Variants
Useful variants
Same shape with two sentences.
Risky but workable for the rare polymath; requires very tight sentences.
Pairs well with