Developer portfolios that get replies, not just praise
The four-section structure recruiters skim in 90 seconds, and why most engineer portfolios pitch the wrong thing.
Most developer portfolios are personal museums. A timeline, every project they've ever shipped, technologies listed in alphabetical order. They get compliments from peers and zero replies from people hiring.
The portfolios that get replies pitch a job, not a career. They have four sections. Here's the structure.
1. One-line who-you-are
At the top: name, role, and the kind of work you want. "Senior backend engineer, distributed systems, contracts open for January." Not "full-stack polymath passionate about code."
Specificity is the entire game. Recruiters scan for fit; they don't read for vibes. If your top line is generic, you blend in with every other dev on LinkedIn.
2. Three projects, deeply
Not ten projects with screenshots. Three projects with: what it was, what you did, what changed because of it. Use numbers if you have them, "reduced p99 latency from 480ms to 90ms" beats "optimized backend performance."
If you can show before/after, graphs, code, screenshots, show them. Most developer portfolios skip the proof because the dev doesn't think it's interesting. Recruiters and engineering managers find it the only interesting thing.
3. Writing or talks (if you have them)
Three blog posts, conference talks, or open-source contributions. This is the section where you show how you think, not just what you ship. If you don't have any, skip the section, don't pad it with links to your Twitter likes.
4. Contact, real
Email address visible. Not a contact form. Email. The path from "interested in hiring this person" to "sending them a message" should be one click and one copy.
Add your timezone and preferred response window ("usually replies within 24h"). It sets expectations and signals professionalism.
Visual restraint
Static UI. No hover animations on every card. No floating gradients. Developer portfolios that look like a Squarespace template signal "I picked a theme," not "I can build product." A solid, dense, editorial layout with great typography signals competence faster than any animation.
Build one
The portfolios collection has the patterns above with tuned prompts. Bubble avatar clusters and project case-study cards are the most-used components, start with those, then add the writing section last.
Keep reading