Persona: Priya, marketing to product
Priya spent five years in B2B growth and content. She is targeting junior/mid product. Her current "portfolio" is a Canva of campaigns plus LinkedIn. A product hiring manager is not looking for a creative moodboard - they want discovery, prioritization, and outcomes.
Scenario: one narrative instead of everything
If Priya puts "marketing + product + design thinking + AI" in the hero, the site says "a bit of everything". Better: one primary role, 2-3 projects rewritten for product (user problem, hypothesis, decision, outcome), then a short bridge from growth.
Role-fit checklist
- Write the audience: recruiter, hiring manager, or client.
- Pick one main proof of competence in that field.
- Order projects closest to the target role first.
- Remove sections that do not support the narrative.
- Rewrite cases in the language of the new role.
- Match CTA: full-time vs freelance.
- Run a 20-second test with someone outside your bubble.
Before you pick template colors:
What sells in design, eng, and marketing
Design: process, constraints, impact on metrics or flow quality. Engineering: stack, trade-offs, reliability, ownership scope. Marketing: campaign results, hypotheses, audience, lessons - not a wall of graphics alone.
PM, data, and sales can have portfolios too; the section weight changes, not the rule: proof first, decoration second.
Common mistakes
- Universal hero "for every job post".
- Cases still written in the old industry voice.
- Too many weak proofs instead of 2-3 strong ones.
- Template chosen for aesthetics, not narrative.
- No bridge story when changing careers.
Limits
A template will not invent a selective story for you. Under NDA-only work or a company product you cannot publish - describe scope without secrets or build a side case. This is portfolio practice, not a hiring guarantee.