Quick answer
How do you interview a freelance developer before hiring?
To interview a freelance developer, first share a short brief, then hold a call with practical questions about your project, ask them to walk you through a real code sample, give a small paid task, check how clearly they communicate, and score every candidate on the same sheet. Compare scores, not feelings, before you decide.
Key takeaways
- Send the same short brief to every developer.
- Ask about your project, not textbook theory.
- Ask them to explain real code they wrote.
- Give one small paid task with a deadline.
- Check how clearly they write and reply.
- Score everyone on the same simple sheet.
Why does a proper developer interview matter?
A proper interview matters because a developer's profile shows skills they claim, not how they think or work. A planned interview shows both in about an hour.
This guide is about the interview itself: what to ask, what to look at and how to score. For wider checks like references and trial tasks across all roles, see our guide on how to test a freelancer before hiring. It works whether you plan to hire a web developer, an app developer or a full team.
What should you prepare before the interview?
Prepare a one-page brief, a list of fixed questions and a scoring sheet. Using the same set for every developer makes the comparison fair.
- A short brief: what you want built or fixed, and why
- Your current tools: WordPress, Shopify, Laravel, React, a mobile app or other
- Your deadline and how many hours a week you need
- One or two example sites or apps you like
- Your list of fixed interview questions
- A blank scoring sheet for each candidate
- A small paid task, ready to send after the call
Send the brief a day before the call. A good developer will read it and come with questions. If someone has clearly not opened it, that tells you something already.
If you are not sure how to write the brief, our guide on how to write a project brief for a freelancer shows a simple format.
Which questions should you ask a freelance developer?
Ask practical questions about your project, their past work and how they handle problems. Good answers are specific and simple, not full of jargon.
Questions about your project
- After reading my brief, what questions do you have?
- How would you break this work into smaller parts?
- Which part looks hardest to you, and why?
- What would you need from me to start?
- How long would the first working version take?
Questions about how they work
- How do you test your work before you hand it over?
- Where will the code live? Will I own the Git repository?
- How do you take backups before you change a live site?
- How often will you send updates, and in what form?
- What happens if you fall sick or go on leave?
- How many other projects are you working on now?
Listen for honesty. A developer who says "I have not used that tool, but here is how I would learn it" is often safer than one who says yes to everything.
Which technical questions fit each type of developer?
Ask two or three questions linked to the tools your project uses. You do not need to judge the deep detail, only whether the answer is clear, confident and practical.
| Developer type | Good questions to ask | What a good answer includes |
|---|---|---|
| WordPress developer | How do you choose plugins? How do you keep a site fast? | Few, trusted plugins, child themes, caching, image sizes, updates on a staging copy |
| Shopify developer | How do you edit a theme without breaking updates? How do you add a custom feature? | Duplicate theme for testing, clean sections, apps only where needed |
| PHP or Laravel developer | How do you keep a login form safe? How do you handle database changes? | Input checks, password hashing, migrations, separate test data |
| React or Next.js developer | How do you keep a large app easy to change? How do you handle page speed? | Reusable components, clear folder structure, loading only what is needed |
| Mobile app developer | How do you test on different phones? How do you publish app updates? | Testing on low and high-end Android phones, store review process, version notes |
If your project uses a specific stack, our pages on how to hire a PHP developer, hire a Laravel developer and hire a React developer list the skills that matter for each.
How do you review a developer's code samples?
Ask the developer to share their screen and walk you through code they wrote. Watch whether they can explain it simply and whether the code looks tidy and organised.
Many developers cannot share client code because of privacy. That is fine. They can show a personal project, a public Git repository or a part of past work with private details removed.
What to look for, even if you do not code
- Files and folders have clear, sensible names
- The code has short comments where something is not obvious
- They can explain what each part does in plain words
- They wrote the code themselves, or say clearly which parts they did
- They mention how they tested it
- There is a README or setup note for the next developer
Good questions during the walkthrough
- If you had more time, what would you improve here?
- How would another developer set this up on their laptop?
- What would break first if traffic grew a lot?
If they cannot explain their own code, or get defensive when you ask simple questions, mark it down. You will need them to explain their work many times during the project.
Need help with your project?
Talk to the SI Experts team. Free first call, simple advice, clear quote.
What small paid task should you give after the interview?
Give a small, real task that takes a few hours and pay for it. Use a copy of your site or a test setup, never your live site or main logins.
- 1
Pick a real but small piece of work
For example, fix one bug, build one page section, or connect one form to your email or CRM.
- 2
Write a clear task note
Say what done looks like, the deadline and how they should hand it over, such as a Git branch or a zip file.
- 3
Give limited access
Share a staging copy or a separate user account with only the rights needed for the task.
- 4
Agree the payment first
Fix the fee for the task in writing and pay by bank transfer or UPI when it is delivered.
- 5
Review the result together
Ask them to show you the work on a short call and explain what they did and how they tested it.
Give the same task to two or three shortlisted developers. Comparing their work side by side makes the choice much easier.
Watch the process, not just the result. Did they ask questions when the note was unclear? Did they deliver on time, or tell you early about a delay? Did they test on mobile? Our guide on how to check freelancer work quality explains how to review the delivered work.
How do you check a developer's communication?
Check communication across the whole process: their first reply, the interview call, the paid task and their written updates. Clear communication matters as much as coding skill for remote work.
Most freelance work happens over email, WhatsApp, Slack or a project tool. So written replies matter a lot. A developer who writes short, clear updates will save you many hours.
Good communication signs
- Replies within the time they promised
- Asks questions before starting, not after
- Explains technical points in simple words
- Tells you early about delays or problems
- Sums up the call in writing afterwards
Weak communication signs
- Long gaps with no update
- Uses jargon and gets annoyed when asked to explain
- Says yes to everything without questions
- Hides delays until the deadline
- Different answers on call and in writing
What red flags should you watch for in a developer interview?
Watch for vague answers, no testing process, refusal to share any code, requests for your main passwords and pressure to pay fully upfront. Any one of these is a reason to slow down.
- They want to keep the code on their own account and not give you the repository
- They cannot explain how they test or take backups
- They promise a very short timeline without asking questions
- They ask for your main hosting or admin password instead of a separate user
- They want full payment before any work is delivered
- Their code sample does not match the skills they claimed
You should always own your domain, hosting, code repository and app store accounts. The developer should work inside your accounts with their own user. When the work ends, you remove their access in one click.
For payment, a fair setup is a small first milestone, then payments as parts are delivered. If the developer is GST registered, ask for proper GST invoices. Our post on what to include in a freelancer contract covers ownership and payment terms.
How do you use a scoring sheet to pick the right developer?
Score each developer from 1 to 5 on the same six points right after each stage. Add the scores and compare. This stops you choosing on mood or a single good moment.
| Area | What you judge | Score (1 to 5) |
|---|---|---|
| Understanding of your brief | Did they read it and ask useful questions? | __ |
| Technical answers | Were answers clear, practical and linked to your project? | __ |
| Code walkthrough | Was the code tidy and could they explain it simply? | __ |
| Paid task result | Did it work, on time, and was it tested? | __ |
| Communication | Were replies quick, clear and honest? | __ |
| Work habits | Backups, Git, access, updates and leave cover | __ |
Give extra weight to the paid task and communication. These two show how the real project will feel. A developer with slightly weaker theory but great habits is often the better choice.
Should you interview a solo freelancer or a dedicated developer from a team?
You can interview both the same way. A solo freelancer suits small one-off work. A dedicated developer from a team suits ongoing work, because the team adds code review and leave cover.
| Point | Solo freelancer | Dedicated developer from a team |
|---|---|---|
| Interview and code walkthrough | Yes | Yes |
| Paid task | Common | Common, or a short first phase |
| Code review | Self-checked | Team lead can review key work |
| Cover during leave | Usually none | Team cover |
| Best for | Small, clear tasks | Ongoing builds and support |
If you need several people, see how to hire a dedicated team in India. For apps, see our page to hire a mobile app developer.
SI Experts is powered by Shivah Web Tech, with 11+ years of work, a 25+ member in-house team and 500+ projects. You can interview our developers and start with a small task. Cost depends on the skill, hours and scope. You get a clear quote after a free call. Contact us to set up an interview.
Frequently Asked Questions
How long should a freelance developer interview take?
Plan about 45 to 60 minutes for the main call. Spend around 15 minutes on your project, 15 on their past work and habits, and 20 on a code walkthrough. Keep the rest for their questions. The paid task comes after the call and usually takes a few hours of their time over two or three days.
How can I interview a developer if I am not technical?
Focus on things you can judge. Did they read your brief? Can they explain their own code in simple words? Do they test, take backups and use Git? Did the paid task work on your phone and laptop? If possible, ask a friend who codes to join for the code walkthrough. Clear thinking and honest answers are easy to spot even without coding skill.
Should I give a developer a coding test during the interview?
A live coding test under pressure often shows nerves more than skill. A better option is a small paid task done in their own time, followed by a short call where they explain it. This is closer to real work. Keep the task to a few hours and use a copy of your site, not the live one.
What is the most important question to ask a freelance developer?
One of the most useful questions is, after reading my brief, what questions do you have? A good developer always has questions about scope, users, tools or edge cases. If they have none, they may not have read the brief or may not think ahead. Their questions also show how well they understand your business.
How many developers should I interview?
Interview three to five developers after a quick check of their profiles and samples. Then give the paid task to your top two or three. This is usually enough to make a clear choice without spending weeks. Use the same brief, questions, task and scoring sheet for everyone so the comparison stays fair.
Is it okay if a developer cannot share client code?
Yes. Many developers sign agreements that stop them from sharing client code. Ask for a personal project, a public repository or a part of past work with private details removed. You can also rely more on the paid task. What matters is that they can show and explain some real code they wrote themselves.
What access should I give a developer for the paid task?
Give the least access needed. Use a staging copy of your website, a test store or a separate user account. Do not share your main hosting, admin or email password. For code, add them to your own Git repository with limited rights. When the task ends, you can remove their access quickly if you do not hire them.
