A few years ago I rebuilt my personal portfolio three times in six months. New design, better color palette, smoother animations. I was obsessed with how it looked. I got zero callbacks from it.
Then I had a conversation with a senior engineering manager at a mid-size fintech. She told me she spends about 90 seconds on a portfolio before deciding whether to forward it. She doesn't care about scroll animations. She's trying to answer one question: can this person actually build things?
That broke something open for me. I'd been designing a portfolio for an imaginary audience. Here's what I learned after that — the hard way, then the right way.
The 90-Second Reality Check
Hiring managers at companies like Cloudflare, Linear, and Vercel are reviewing dozens of applications a day. They're not leisurely scrolling your site with a coffee. They're triaging.
According to a 2024 report from Hired.com, technical recruiters spend an average of 1.5 to 2 minutes on a developer's portfolio before moving on or flagging it for a deeper look. That's not a lot of runway.
So the first thing you need to do is ruthlessly audit your portfolio from a cold-eyes perspective. Open it on a new browser. Pretend you're a tired hiring manager at 4pm on a Friday. What do you actually see in the first ten seconds?
If the answer is "a beautiful hero section with a parallax effect and no actual information" — we've got work to do.
What Should Actually Be on Your Portfolio
A Clear, Confident Introduction
Not "Hey, I'm a passionate developer who loves coding!" That tells me nothing. I've read that sentence probably 400 times.
Instead, try something specific. "I build backend systems in Go and Python. Recently shipped a payment processing API that handles $2M/month in transactions for a logistics startup." Now I'm interested. Now I know what you do and that you've done real things.
Your intro should answer three things immediately: what you build, what stack you use, and what kind of problems you solve. One paragraph. That's it.
Projects — But Only the Right Ones
Here's the deal: three strong projects beat ten mediocre ones every time. I used to pad my portfolio with every side project I'd ever touched. Todo apps, weather widgets, clones of existing apps. Hiring managers have seen all of it.
What actually stands out is a project that solves a real problem, has real users, or demonstrates a non-trivial technical decision. A to-do app built with React doesn't tell me anything I couldn't figure out from a tutorial. But a to-do app where you explain why you built your own conflict resolution for offline sync? Now we're talking.
"I don't care if it's a side project or a startup. I care if you made real decisions under real constraints. Show me the tradeoffs you made." — Engineering Manager, mid-size SaaS company (shared in a dev community Slack, 2024)
For each project, you want four things: what it does, what stack you used, what the hardest part was, and a link to either a live demo or the GitHub repo. That last part is non-negotiable. A project with no link is basically a ghost.
GitHub Activity Matters — But Not How You Think
A lot of developers obsess over having a green GitHub contribution graph. I get it. But that's not really what's being evaluated.
What hiring managers and senior engineers actually look at is your commit quality and your README files. Seriously. I've heard this from engineers at Atlassian, Figma, and HashiCorp — they'll open your most-starred repo and read the README before they look at a single line of code.
A well-written README shows communication skills, documentation habits, and whether you've thought about the people who might use your work. A repo with no README is a yellow flag. A repo with a detailed README including setup instructions, architecture decisions, and known limitations? That's a green flag.
The Technical Writing Section Nobody Adds (But Should)
This one I stumbled onto accidentally. I added a "Writing" section to my portfolio mostly because I had a few dev.to posts I was proud of. Within two weeks of relaunching, I had two hiring managers mention it specifically in intro calls.
Technical writing is a massive signal. It shows you can explain complex things clearly. It shows you think deeply about your work. And honestly, it's rare enough that it makes you stand out immediately.
You don't need a massive blog. Even two or three solid technical posts — something you learned debugging a tricky issue, an architecture decision you made and why — is enough to add a writing section. Post on dev.to, Hashnode, or your own blog. Link them from your portfolio.
How to Show Seniority Even Without Years of Experience
I see this question a lot, especially from developers in markets like Nigeria, India, Brazil, and the Philippines who are building strong technical skills but don't have five years of FAANG on their resume. Here's what I think: seniority signals are about decision-making, not time.
When you describe a project, don't just say what you built. Say why you made the technical choices you made. "I chose PostgreSQL over MongoDB here because the data relationships were complex and I needed ACID compliance" is a senior-sounding sentence. It tells me you evaluated options and made a deliberate call.
Same with explaining what you'd do differently. "If I rebuilt this today, I'd separate the auth service from the main API — I learned that coupling them made testing painful" is the kind of reflection that signals maturity. That's what a senior engineer sounds like. You can demonstrate that voice in how you write about your work.
Certifications That Actually Help
If you're early career and your project list isn't deep yet, relevant certifications can fill the credibility gap. The ones that hiring managers actually recognize and value in 2025-2026:
- AWS SAA-C03 (AWS Solutions Architect Associate) — widely respected, especially for backend and cloud roles. Cost: around $150 USD for the exam.
- Google Professional Cloud Architect — strong signal for GCP-heavy shops, more rigorous than AWS SAA. Exam fee: $200 USD.
- HashiCorp Terraform Associate — increasingly asked for in DevOps and platform engineering roles. $70.50 USD exam fee.
- GitHub Actions / GitHub Advanced Security certifications — newer, but GitHub's own certifications are gaining traction in CI/CD-focused roles.
Don't plaster eight certifications on your portfolio. Pick one or two that are actually relevant to the jobs you're targeting and list them clearly near your skills section.
Portfolio Tech Stack: Don't Overthink It
I spent way too long deciding whether to build my portfolio with Next.js, Astro, or just plain HTML. Here's my actual take: it doesn't matter much, but Astro is a solid choice in 2025-2026 for a static portfolio. It's fast, ships minimal JavaScript, and gets near-perfect Lighthouse scores out of the box.
That said, I've seen great portfolios built on plain HTML/CSS hosted on GitHub Pages that outperform fancy Next.js sites because the content was better. A slow, pretty portfolio with weak content will lose to a fast, simple one with great projects every time.
If you're using your portfolio to show off a specific skill — like if you're a React specialist — then yeah, build it in React. That's a legit flex. Otherwise, pick what you know and move on. Don't let the tech choice be the reason you never launch.
Hosting and Domain Names
Free hosting is completely fine. Vercel and Netlify both offer free tiers that are more than enough for a portfolio. What's not fine is a URL that looks like yourname.vercel.app/projects/page2.
Get a custom domain. Namecheap sells .dev domains for around $10-12/year. yourname.dev looks professional and takes ten minutes to set up. It's one of the cheapest credibility upgrades you can make.
The Soft Stuff That Actually Seals Deals
One thing I've noticed that almost nobody talks about: hiring managers want to feel like they know who you are before they get on a call. Not in a weird way — just a sense of your personality and communication style.
A short, honest "About" section goes a long way. Not a corporate bio. Just something real. What you're working on, what kind of problems get you excited, maybe one thing you're learning right now. It doesn't need to be long. It just needs to sound like an actual person wrote it.
The developers I've seen get callbacks consistently aren't always the most technically impressive ones. They're the ones who communicate clearly and make hiring managers feel confident they won't be painful to work with.
Make Contact Stupid Easy
Your email should be on the homepage. Not buried in a contact page. On the homepage, visible without scrolling.
I know that sounds obvious. But I've reviewed portfolios where I genuinely couldn't find a way to reach the person. That's a portfolio that doesn't get a callback — not because the work was bad, but because it created friction at the worst possible moment.
One Last Thing About Salary Expectations
Your portfolio affects what you get paid. I don't think people talk about this enough.
According to Levels.fyi 2024 data, entry-level software engineers at mid-size tech companies in the US earn between $95,000 and $130,000 total comp. Senior engineers at those same companies are in the $160,000 to $220,000 range. The difference often comes down to how you're perceived — and your portfolio is a huge part of that perception before you ever get on a call.
A portfolio that reads as senior — specific, thoughtful, showing decision-making and communication — can get you into a higher interview tier from the start. That matters, because your starting offer in that tier is meaningfully higher.
If you're job hunting in 2025 or heading into 2026, your portfolio isn't a formality. It's one of the highest-leverage things you can spend a weekend improving. Three focused projects, honest writing about your work, fast load times, your email on the homepage.
That's genuinely most of it. The rest is noise.