Questions to ask before hiring a developer
Ask about three things: what the developer has built that is like your project, how they work and communicate, and what you receive at the end. Good answers are specific, include an example and are easy to follow even if you are not technical.
Last updated:
How to use this list
Pick the five or six questions that matter most for your project and ask them in a first call or in writing. You are not testing the developer. You are looking for clarity, honesty and a way of working that suits you.
Tip: send your project brief first. Then the answers will be about your project, not general talk.
Experience
- Which projects of yours are closest to this one? Can I try them? Look for a live link or a repository you can see.
- What was your part in those projects, and what was done by others?
- Which tools would you use here, and why? A good answer connects the choice to your goals, not to habit.
- What is the hardest part of my project? Honest developers name a risk early.
Process
- How would you split the work into steps? Expect small steps you can check, as in milestones.
- How will I see progress during a step? Weekly demos or a test link are good signs.
- How do you handle changes once work has started?
- How do you test your work before showing it to me?
Communication
- Which time zone and hours do you work in, and how fast do you usually reply?
- How do you prefer to stay in touch: messages, calls, video?
- Who will work on my project? If others join, how are they introduced?
- How do you share bad news, such as a delay?
Handover and ownership
- Will the code live in an account that I control?
- Which open source parts or reusable components will you use? See who owns the code.
- Will you document how to run and update the product?
- Who sets up hosting and app store accounts, and in whose name?
Money and risk
- What exactly is included in the price, and what would count as extra?
- What do you need from me, such as content, logins or decisions, and by when?
- How is each step paid, and when? Compare with the options in fixed price vs hourly.
- What happens if we disagree about a result? Clear, fair steps for this are a good sign.
What good answers sound like
| Topic | Helpful sign | Worth a follow-up |
|---|---|---|
| Detail | Gives examples and names trade-offs. | Only says it is easy or no problem. |
| Questions | Asks about your users and goals. | Does not ask anything about your project. |
| Plan | Offers small steps with clear results. | Offers one big step with a vague finish. |
| Pace | Shares a realistic timeline with assumptions. | Promises an exact date without questions. |
Detail
- Helpful sign
- Gives examples and names trade-offs.
- Worth a follow-up
- Only says it is easy or no problem.
Questions
- Helpful sign
- Asks about your users and goals.
- Worth a follow-up
- Does not ask anything about your project.
Plan
- Helpful sign
- Offers small steps with clear results.
- Worth a follow-up
- Offers one big step with a vague finish.
Pace
- Helpful sign
- Shares a realistic timeline with assumptions.
- Worth a follow-up
- Promises an exact date without questions.
On ErdiBuilds, Verified means an ErdiBuilds admin has reviewed the developer and approved the profile by hand. Developers are independent professionals, not our employees. You still choose who to work with, so the questions above remain useful. More on safe steps is in how to hire a developer safely.
What to do with the answers
Write the answers down and compare them after each call. Rate each answer on three simple points: was it clear, was it specific to my project, and did it make me more confident? A short table in a notes app is enough.
Then pick the developer whose answers you understood best, even if another sounded more impressive. Easy communication in the first week usually continues for the whole project.
Frequently asked questions
How many questions should I ask?
Five or six well-chosen questions beat twenty rushed ones. Pick those that match your biggest worries, such as experience, timeline or handover.
Link to this answerWhat if I am not technical and cannot judge the answers?
Listen for clear language, examples and honest limits. Ask the developer to explain in simple words. If you still feel unsure, an advice and review session can give a second opinion.
Link to this answerIs it fine to ask for examples of past work?
Yes, it is normal. Look for a live link or code you can see, and ask what the developer personally did.
Link to this answerShould I ask for references?
You can. Past clients can tell you about communication and reliability. Not every developer can share names, so also look at the work itself.
Link to this answerWhat are signs that a conversation is going well?
The developer asks about your goal, offers a small first step, explains trade-offs and is open about what they do not know.
Link to this answerRelated pages
- How to Hire a Developer SafelyHire a developer with confidence: pay per milestone, fund before work starts, keep payments on one platform, and get access to your code as you go.
- Who Owns the Code When You Hire a Developer?Learn who owns the code, design and data when a freelancer builds your software, what usually stays with the developer, and how to agree on it in writing.
- How to Write a Project Brief for a DeveloperA good project brief fits on one page: goal, users, must-have features, examples and limits. Here is what to include and a free tool to draft it.
- How to Hire an App Developer, Step by StepA clear process for hiring an app developer: define the job, choose where to look, compare proposals, check fit and start with a small milestone.
- How it worksFrom idea to finished project, step by step.