10 questions to ask a freelance developer before you hire them

Most founder-freelancer mismatches happen because the founder asked the wrong things on the first call. Here are the ten questions that actually predict the engagement, and what good answers look like.

1. "Can you walk me through the last project you shipped end-to-end?"

You want a story with a beginning, middle, and end. If they can't name the live URL or the outcome metric, they probably haven't shipped much.

2. "What did you change about the original scope mid-project?"

The best answer is "I cut things." Freelancers who only add features turn into agencies who only add invoices.

3. "What's your current capacity over the next 8 weeks?"

You want a number of hours per week, not a vibe. "I have bandwidth" is not an answer.

4. "Who owns the code, and where does it live?"

Should be: "Your GitHub org from day one." Anything else — a private repo they own, a zip they hand over at the end — is a yellow flag.

5. "What's your weekly update cadence?"

A good freelancer has a default rhythm (Friday email, a Loom, a shared Notion). Someone who says "whenever you need me" is someone who will go quiet.

6. "What does your contract include for the case where I stop the project early?"

A pro freelancer has a kill clause that's fair to both sides. No contract or a one-sided one is a red flag in both directions.

7. "Have you ever told a client their idea was wrong?"

If they say no, they will not push back on you either. You are paying for taste, not just hands.

8. "What's a recent project you turned down, and why?"

Tells you what they think is outside their lane. Someone who has never turned a project down is desperate, undisciplined, or both.

9. "Can I talk to a previous client?"

Always yes. References are biased but the conversation isn't — listen to *how* the previous client describes the work, not whether the recommendation is positive.

10. "What does week one look like if we start Monday?"

You want a specific answer: a kickoff call, an architecture doc by Wednesday, a deployed skeleton by Friday. Vague answers predict vague work.

The two answers that should make you walk away

• "I never miss deadlines." (They will, and they won't tell you.)
• "I can do anything." (No senior developer says this. Specialists know their lane.)

Hire the freelancer who admits a limitation in the first call. They are also the one who will tell you the truth when something is going wrong — which is the only thing that matters once the contract is signed.