What separates a top 1% developer from the rest? A guide to vetting freelance portfolios, technical skills, and communication standards in Nepal.
There's a developer in Boudha right now charging NPR 15,000 for a website. There's another one, also in Kathmandu, charging NPR 150,000 for the same type of website. Both call themselves "Full Stack Web Developers." The first one will deliver a cloned WordPress theme. The second one might build you a custom Next.js application that ranks on Google and doesn't crash when 500 people visit at once.
How do you tell the difference before you pay? That's exactly what this guide covers — having been on both sides of this conversation, both as a developer selling my work and as someone evaluating other developers.
The Core Problem
Web development has no licensing requirement. Anyone can call themselves a developer. This means the marketplace is flooded with people who finished a 30-day YouTube bootcamp and are now charging professional rates. Knowing how to evaluate a developer is more valuable than knowing how to code yourself.
1. Look Beyond Screenshots — Demand Live Evidence
Screenshots are meaningless. They could be from someone else's project, a template, or heavily edited in Photoshop. A top 1% developer is proud of their live work. Here's the framework I use:
Red Flags
- "NDA prevents me from sharing live projects" (for all projects)
- Portfolio is only Behance/Dribbble images, no live URLs
- Every project uses the same template structure
- Can't explain what they personally built vs. what was existing
Green Flags
- Shares live URLs you can click through and test yourself
- Can explain specific technical decisions they made
- Portfolio site itself performs well on mobile and PageSpeed
- Has public GitHub repos showing real, recent code
2. The 3-Minute Technical Tests You Can Do Without Coding
You don't need to know JavaScript to run these checks on any developer's portfolio:
Google PageSpeed Insights Test
Go to pagespeed.web.dev, paste their portfolio URL, run the test.
Hire them
Ask why
Walk away
The Mobile Test
Open their site on your phone. Try to navigate it with one thumb. If anything is broken, tiny, or hard to tap — they're not practicing what they'll preach on your project.
The Google-Yourself Test
Google their name + "developer". Does their own portfolio appear in the results? If a developer can't rank their own personal site, they do not understand SEO. Your business site will suffer the same fate.
View Source Check
Right-click their site → "View Page Source." If you see wp-content or theme-, it's WordPress. Not necessarily bad, but if they're claiming to be a "custom developer" — that's misleading.
3. Communication Quality — The Often-Ignored Dealbreaker
I've worked alongside developers who wrote beautiful code but were a nightmare to work with — unresponsive for days, vague about progress, defensive about feedback. Development is 30% coding and 70% communication, collaboration, and problem-solving.
Test this before you hire with a simple message: "I'm considering working with you on a project. Can you give me a rough timeline and process overview?"
Responds within 24 hours with a thoughtful, structured answer
Asks clarifying questions about the project scope
Proposes milestones and checkpoints, not just a final delivery date
Says "I'd need to know more before giving an accurate estimate" — honest and professional
Responds 4 days later with "Yeah I can do it, how much is your budget?"
Gives a fixed price quote without asking a single question
Says yes to everything without pushback — they're telling you what you want to hear
4. Verifying the "Full Stack" Claim
"Full Stack" is the most abused term in software development. Many people claiming it are strong in one area (usually frontend) and barely competent in the other. Here's how to verify:
Ask: "Why did you choose MongoDB over PostgreSQL for that project?"
✅ Good answer:
They explain the tradeoffs: document vs. relational model, schema flexibility vs. data integrity, the specific query patterns that influenced the decision.
❌ Warning answer:
"I just use MongoDB, it's what I know."
Ask: "How do you handle authentication in your backend?"
✅ Good answer:
They discuss JWT vs. sessions, refresh token rotation, secure HttpOnly cookies, and when to use a third-party auth provider.
❌ Warning answer:
"I store the user ID in localStorage."
Ask: "Walk me through your deployment process."
✅ Good answer:
CI/CD pipeline, environment variables, rollback strategy, monitoring setup.
❌ Warning answer:
"I FTP the files to the server."
The cheapest developer is almost never the cheapest outcome. A NRP 15,000 project that needs to be rebuilt in 6 months costs more than a NPR 80,000 project done right the first time. The real question isn't "how much does this cost?" — it's "what's the cost of doing this badly?"
Looking for a Vetted Professional?
My portfolio has live URLs, PageSpeed scores, and case studies — not just screenshots. Come and verify me using every test in this guide.