I've looked at a lot of developer portfolios over the past year, and the ones that actually convert — the ones that get someone to hit the contact button — all share the same bones. Meanwhile, the ones that don't work are usually missing something obvious, or drowning in stuff nobody asked for.
One thing that's shifted recently: the bar has moved. In 2026, with vibe coding tools everywhere and AI-assisted development basically mainstream, everyone can ship something fast. The question your portfolio now needs to answer isn't just "can you build?" — it's "how do you think, and what do you specifically bring to the table?"
Here's the honest breakdown: what to include, what to skip, and why.
The Non-Negotiables#
These are the things that have to be there. If any of them are missing, you're losing opportunities.
1. A Clear "Who I Am" Statement#
Not a novel. Not a list of buzzwords. A single sentence that tells a visitor what you do and who you do it for.
Bad: "Passionate full-stack developer with a love for clean code and innovative solutions."
Good: "I build fast, accessible web apps for early-stage startups — mostly in React and Node, with AI-assisted workflows throughout."
The second version tells me your stack, your niche, and that you work the way modern teams actually work. Lead with that.
2. Your Best 3–5 Projects#
Notice I said best, not most. A portfolio with three excellent projects beats one with twelve mediocre ones every time. Recruiters and clients don't dig deep — they look at the first two or three things and form a judgment fast.
For each project, you want:
- A sharp, descriptive title (not "Project 1")
- A one or two-line summary of what it does and why it exists
- The tech stack you used
- A link to the live site and/or the GitHub repo
- A screenshot or short screen recording
That's it. You don't need a 500-word case study for every project unless you're going for senior UX or product roles.
3. A Way to Contact You#
This sounds obvious. And yet — I've visited portfolios where I genuinely could not find an email address. Don't make someone hunt for this. Put it in your nav, put it at the bottom of every page, put it on a dedicated contact page.
Email is fine. A simple form is better. Both is ideal.
4. Your Name and a Photo#
People hire people, not websites. A clear, well-lit photo builds trust in a way no amount of clever design can replace. It doesn't need to be taken by a photographer. A good phone photo with natural light works perfectly.
What to Include If You Have It#
These aren't mandatory, but they add real signal.
How You Work With AI#
This is new, but it's becoming expected. If you use tools like Cursor, Claude Code, or GitHub Copilot as genuine parts of your workflow — not just autocomplete but actual agentic development — briefly mentioning this signals that you work the way modern engineering teams actually work. Developers who combine strong fundamentals with AI tool fluency are commanding a noticeable premium right now.
This doesn't mean listing every AI product you've ever opened. It means showing you understand the current landscape.
Testimonials or References#
Even one genuine quote from a past client, colleague, or manager does real work. "Alex shipped our onboarding flow in two weeks and the code was clean — we've barely touched it since." That's more convincing than any bullet point.
If you're early in your career, ask a professor, bootcamp instructor, or someone you've collaborated with on a project.
A Skills or Tech Stack Section#
Useful for recruiter scanning. Keep it honest and current — don't list technologies you touched once in a tutorial. A focused list of eight real skills beats a wall of logos you barely know.
What to Leave Out#
Every Project You've Ever Built#
Your college assignments, the to-do app you built while learning React, the half-finished side project from two years ago — none of it belongs here unless it's genuinely impressive. Curate ruthlessly.
A Resume Embedded as a PDF#
Link to a downloadable resume — yes, absolutely. But don't embed a PDF into the page. It looks clunky, doesn't render well on mobile, and the information should already be on your about/skills page.
Walls of Text#
Nobody is reading your 400-word project descriptions. Write a sharp two-line summary, then use bullet points for the relevant details. Brevity is a feature.
Outdated Work#
If your portfolio still leads with a project that reflects skills you had three years ago, that's what people will remember. Remove anything that no longer represents your current level.
A Simple Structure That Works#
If you're building from scratch, this layout consistently converts well:
- Hero — Name, role, one-liner, CTA ("See my work" or "Get in touch")
- Projects — 3–5 featured projects with visuals
- About — Short paragraph + photo + skills/stack + how you work
- Contact — Email or form
That's a complete portfolio. Everything else is optional.
If you want to get something live without building the infrastructure yourself, FastFolio handles the structure, SEO, and mobile layout so you can focus entirely on the content. The free plan gets you from blank page to published in an afternoon.
The 30-Second Test#
After someone spends 30 seconds on your portfolio, can they answer these three questions?
- What do you do?
- What have you built?
- How do I reach you?
If the answer to any of those is "not sure," fix that first. Everything else is polish.