How to Vet a Developer Before You Hire

Hiring a developer is a gamble. The industry is full of smooth talkers who can't actually build anything, template resellers pretending to be custom developers, and genuinely talented people who are terrible at communication.

Here's how to tell the difference before you hand over money.

Step 1: Check Their Portfolio (Properly)

Everyone has a portfolio. But most people check it wrong.

Don't just look at screenshots. Screenshots can be stolen, mocked up, or from templates. Actually visit the live sites.

Check the sites on your phone. Pull out your phone and load their portfolio projects. Do they work on mobile? Are they fast? If a developer's own showcase projects are broken on mobile, imagine what they'll do with yours.

Look for variety. If every project looks the same, they probably use one template for everything.

Ask about their specific role. On team projects, developers often claim credit for work they barely touched. Ask: "What exactly did you build on this project?"

Step 2: Ask the Right Questions

These questions reveal more than any portfolio:

"What would you do if we changed requirements mid-project?"

Good answer: Describes a process for handling changes, mentions scope documentation, talks about how they'd assess impact. Bad answer: "No problem!" (too eager) or gets defensive.

"Tell me about a project that went wrong."

Good answer: Honest about a real failure, explains what they learned. Bad answer: "I've never had a project go wrong." (Either lying or hasn't done enough work to fail.)

"How do you handle communication and updates?"

Good answer: Specific tools and cadence. "I send weekly updates every Friday, we use LINE for quick questions, and I share a Notion doc with progress." Bad answer: Vague promises about "staying in touch."

"What happens after launch?"

Good answer: Clear support terms, maintenance options, documentation handoff. Bad answer: Silence or "we can discuss that later."

Step 3: Red Flags That Should Kill the Deal

• No contract. Any legitimate developer uses contracts. No exceptions. If they resist putting things in writing, run.
• 100% upfront payment. Standard is 30-50% upfront, rest on milestones or completion. Anyone demanding full payment before starting is either desperate or planning to disappear.
• Can't explain tech in plain English. If they hide behind jargon and can't simplify, they either don't understand it themselves or are trying to confuse you.
• Promises everything. "Yes we do AI, blockchain, mobile apps, AR/VR, and enterprise systems!" Real specialists have focus areas. Generalists who claim expertise in everything are usually mediocre at all of it.
• No questions for you. A good developer asks lots of questions about your business, goals, and users. If they jump straight to quoting without understanding the problem, they're just selling hours.
• Unrealistic timelines. "We can build your e-commerce platform in two weeks!" Either they're using garbage templates or they don't understand scope.

Step 4: The Small Test

Before committing to a big project, consider a paid test.

Pay them for a small, defined piece of work. Maybe a single page, a specific feature, or a design mockup. See how they work:

• Do they deliver on time?
• How's the communication?
• Is the code quality decent? (Have a technical friend review if you can't.)
• Do they handle feedback well?

A 10-20k THB test can save you from a 200k THB mistake.

Step 5: Check References (Actually Do It)

Ask for 2-3 past client contacts. Then actually call or message them.

Questions to ask references:

• Did they deliver on time and budget?
• How was communication?
• Were there any surprises or hidden costs?
• Would you hire them again?
• What could they have done better?

If a developer won't provide references, or their references are suspiciously hard to reach, that tells you something.

The Uncomfortable Truth

Good developers are often bad at sales. They might not have the slickest website or the smoothest pitch. Meanwhile, the best salespeople in development are often mediocre at actual development.

Judge by the work, not the pitch. Look at what they've built, how they communicate under pressure, and what their past clients say.

And trust your gut. If something feels off in the sales process, it'll be worse during the project.