You are a recruiter. Your company needs someone different.
Not someone who checks boxes. Not another candidate with a polished PDF and generic answers about "working well under pressure."
Someone who actually builds things. Someone your team will still be talking about in two years.
You've been sent one unusual portfolio. A single link. No subject line. Just a name: [Your Name].
You click it.
What are you looking for?
Chapter 1 — The Thinker
You remember the last hire who froze when things got complicated.
The sprint that went sideways. The stakeholder who changed their mind on a Friday. The bug that wasn't a bug — it was an assumption nobody questioned.
You need someone who leans in when it gets messy. Someone whose first instinct is curiosity, not panic.
[Your Name]'s portfolio doesn't start with a skills list. It starts with a problem.
Case Study — Problem 01
[Your project title — e.g. "Why was nobody finishing the onboarding flow?"]
[Describe a real problem you noticed. What was broken, confusing, or ignored? 2–3 sentences about what you observed before you did anything.]
[Skill used][Tool used][Outcome]
You scroll further. There's no "About Me" section. Just more problems — and what happened when they got solved.
You want to know more. Do you...
Chapter 2 — Inside The Mind
"I don't start with solutions. I start with questions I'm embarrassed to ask."
That's a quote from [Your Name]'s process notes. Not a portfolio section — actual working notes, made public.
You find a diagram sketched in their notebook and photographed. Not clean. Not polished. Real. The kind of thinking that happens before the pretty slides.
[Describe your real process: Do you map it? Ask "why" five times? Build a rough prototype first? Make it specific and honest — this is what makes you memorable.]
You realise you've been reading for ten minutes. You're not skimming anymore.
Chapter 2 — The Output
There's a working link. You hesitate, then click it.
It loads instantly. Clean. No broken images, no placeholder text, no "coming soon."
This is finished. Not "finished for a student project." Actually finished. The kind of thing you'd be comfortable showing a client.
Project — Live work
[Project name — e.g. "StudyBuddy: a focus timer that adapts to your habits"]
[What did you build, why did it matter, and what would someone notice if they used it for 5 minutes? Keep it specific. Avoid jargon.]
[Tech / tool][Time to build][# of users / impact]
You close the tab and immediately re-open it. You want to show someone.
Chapter 1 — The Eye
Your last campaign felt safe. Competent. Forgettable.
You've seen a thousand portfolios that look exactly the same. The same mockup frames. The same three pastel colors. The same section titled "My Process" with the same four steps.
Then you see [Your Name]'s first piece. And something shifts.
It's not that it's technically perfect. It's that it has a point of view. It makes you feel something you didn't expect to feel looking at a portfolio.
Work — Creative piece 01
[Your most visually striking or emotionally interesting piece]
[What is it? What were you trying to make someone feel? Did it work? Include a sentence about what you were willing to risk by making this choice.]
[Medium][Inspiration][Reaction you got]
You scroll down. There's more. Each piece is different. None of them look like the last one.
What do you want to see next?
Chapter 2 — The Unexpected
You did not expect this.
It's a project that has no obvious category. You can't tell immediately if it's design, writing, code, or all three. You sit with that confusion for a moment — then you realise that's the point.
Project — The rule-breaker
[Your weirdest, most uncategorisable project]
[Describe it honestly. What rules did you break? Why? What did people say when they first saw it — the confused ones and the excited ones?]
You find yourself thinking about it on the commute home. You mention it to a colleague. They ask for the link.
Chapter 2 — The Workshop
The sketchbook section is not what you expected.
There are dead ends. Ideas that didn't work, shown honestly. A version that was "better" on paper but felt wrong in practice, and the decision to scrap it.
[Your Name] doesn't hide the mess. They frame it. This is where ideas come from.
Behind the work — Concept evolution
[A project where the first idea was wrong and you figured out why]
[Tell the story of a creative pivot. What did you believe at first? What made you change direction? What did you learn about yourself as a creator?]
Honesty in a portfolio is rare. This is refreshing in a way you didn't realise you needed.
Chapter 1 — The Adapter
Deadlines don't move. The world does. Your team needs someone who keeps up.
You've seen talented people crumble when the brief changes on a Wednesday. The ones who thrive? They treat every new situation as a puzzle, not a threat.
[Your Name]'s portfolio has a section you've never seen before: "Things I learned last month."
It's updated monthly. The most recent entry is from three weeks ago.
Current learning — What they're building right now
[What are you actively learning? e.g. "Teaching myself motion design in 30 days"]
[Be specific. Why this skill, why now, and what have you made with it so far? Show the work-in-progress honestly — that's the proof of momentum.]
[Days in][Where started][Where now]
You realise most candidates show you where they've been. This one shows you where they're going.
What do you want to see next?
Chapter 2 — Shipped
The list is longer than you expected for someone just starting out.
Not big things. Not viral things. Just a steady trail of finished things — tools built, experiments tried, side projects completed and released into the world.
The pattern you notice: none of them took more than three weeks. They ship, learn, and move.
Shipped — Project log
[List 2–3 small completed projects with a one-line description each]
[e.g. "A browser extension that blocks distracting sites during Pomodoro sessions — 40 users. / A weekly email digest about local events, ran for 3 months. / A Python script that auto-organises downloaded files — saved 20 min/week."]
Small bets. Finished things. That's rarer than it sounds.
Chapter 2 — What's Next
"I'm most useful to teams where I don't know everything yet."
That's how [Your Name] describes themselves. Not out of false modesty — out of self-awareness.
Their "what I want to learn next" section reads like a research proposal. They've thought about why each skill matters, what they'd build with it, and who they'd be able to help.
Vision — What they're aiming for
[What problem in the world do you ultimately want to help solve?]
[This isn't about a job title. It's about a direction. Where does your curiosity keep pulling you? What would you build if you had the skills you're working toward right now?]
Most portfolios tell you who someone is. This one tells you who someone is becoming.
Epilogue — The Decision
You close the tab. Then you open it again.
You've reviewed forty-three portfolios this month. You remember three of them. You will remember this one.
You find the contact section.
[Your Full Name]
[One-line description — e.g. "Designer who codes. Builder who thinks. Student who ships."]
Emailhello@yourname.com
Portfolioyourname.com
GitHubgithub.com/yourname
LinkedInlinkedin.com/in/yourname
Available for internships, freelance work, and full-time roles.
Based in [Your City]. Open to remote.