You are looking at a developer's portfolio. There are screenshots of attractive websites. There are logos of companies they have worked with. There is a list of technologies they know. It looks professional.
But you have no idea whether they can actually deliver what you need.
Developer portfolios are the worst tool for evaluating developers. And they are the only tool most people use. Here is how to look past the screenshots and evaluate what actually matters.
What a Portfolio Does Not Tell You
It does not tell you if the project was delivered on time. A beautiful website could have been delivered six months late, over budget, and with a client who swore never to work with that developer again.
It does not tell you if the code works well. A screenshot shows the front end. It says nothing about database design, security, performance, error handling, or code quality. The most impressive-looking website in a portfolio could be running on terrible code that crashes under load.
It does not tell you if the developer did the work. Agencies often show team projects attributed to the agency. The developer you are evaluating may have done a small part of a large project. Or they may have worked there when the project was done but were not involved.
It does not tell you if the project is still running. A portfolio item from 2023 might have been rebuilt by a different developer in 2024 because it was unmaintainable. Check if the link still works. Check if the current site matches the portfolio screenshots.
It does not tell you how the developer handles problems. Every project has problems. What matters is how the developer responds. Portfolios show the happy ending, never the complications along the way.
What Actually Matters
1. Working Software You Can Test
Ask the developer to show you something that is live and working. Not a screenshot. A URL you can visit, interact with, and test on your phone.
Look at:
- Does it load quickly?
- Does it work on mobile?
- Is the user experience logical?
- Does it look maintained (recent dates, current content, no broken links)?
A developer who can point you to working software that is still in production today is showing more than a portfolio piece. They are showing that their work survives contact with real users and real operations.
2. Similar Work
The best predictor of success is whether the developer has done something similar to what you need before. Not identical. Similar.
If you need a WooCommerce store with custom payment integration, a developer who has built five WooCommerce stores with payment integrations is a better bet than a developer who has built fifty beautiful brochure sites.
Ask: "Have you built something like this before? What were the challenges? What would you do differently?"
The answers tell you more than the portfolio.
3. Technical Decisions, Not Just Outcomes
Ask the developer to explain the technical choices they made on a project. Why did they choose WordPress over a custom application? Why did they use this payment gateway instead of that one? How did they handle performance when the store hit 10,000 products?
A developer who can explain their decisions clearly and acknowledge tradeoffs is demonstrating real experience. A developer who says "it is built with the latest technologies" without explaining why is reciting a brochure.
4. Client References You Can Contact
Reviews on a platform (Google Reviews, Clutch, Upwork) are useful for volume and overall pattern. But the most valuable reference is a conversation with a past client.
Ask the developer: "Can I talk to someone you have worked with on a project similar to mine?"
If they say yes, ask the client:
- Did the developer deliver what was promised?
- Was the project on time and on budget?
- How did they handle unexpected problems?
- Would you work with them again?
- Are they still available for support?
If the developer hesitates to connect you with past clients, treat that as a signal.
5. How They Handle Your Questions
Before you hire anyone, you will have a discovery conversation. Pay attention to how the developer handles it.
Good signs:
- They ask you questions about your business, not just your feature list
- They push back on requirements that do not make sense
- They suggest simpler alternatives where appropriate
- They are honest about what they do not know or have not done before
- They explain things in terms you understand
Warning signs:
- They agree with everything you say without questioning it
- They jump to a solution before understanding the problem
- They cannot explain their approach in plain language
- They focus on technologies rather than outcomes
- They promise everything with no tradeoffs
6. Code Quality (If You Can Check)
If you have a technical person who can evaluate code, ask for a code sample or access to a repository.
Look for:
- Consistent coding style
- Clear naming (variables and functions that describe what they do)
- Version control history (regular commits with meaningful messages)
- Tests (any tests at all are a good sign)
- Documentation (comments where the logic is not obvious)
If you do not have a technical person, skip this. The other five signals are strong enough on their own.
Red Flags in Portfolios
Only screenshots, no live links. The project may not exist anymore, or it may look different from the screenshots because it was rebuilt by someone else.
Logos without context. "Worked with Microsoft" could mean they built a major system. It could also mean they once attended a Microsoft event. Ask what they actually did.
Technology-heavy, outcome-light. "Built with React, Node.js, PostgreSQL, Docker, Kubernetes, Redis, GraphQL" is a technology stack, not a result. What did the software do? What problem did it solve? How is the client doing with it?
No projects in the last year. If the most recent portfolio item is from 2023, what have they been doing since then? This does not automatically mean something is wrong, but it is worth asking.
Too many technologies listed with no depth behind them. A developer who claims expertise in 15+ technologies but cannot point to production work in each one is listing everything they have ever touched. Breadth backed by real projects is valuable. Breadth without proof is a warning sign.
The Short Version
A portfolio shows you what a developer wants you to see. To evaluate what matters, look at working software you can test, similar work they have done, their ability to explain technical decisions, client references you can actually contact, and how they handle your questions.
The developer who shows you an impressive portfolio is showing you marketing. The developer who connects you with a happy client is showing you proof.
If you are evaluating developers and want to see working projects, talk to past clients, and understand how I approach building software, start here. You can also see a real project example at /projects/recycle-point-of-sale-app.