Questions to Ask a Software Developer Before You Hire Them
Short answer: hiring a developer to build something for your business isn’t a job interview. You can’t judge their code, and you don’t need to. Ask about work like yours, who will actually do the work, how the price and changes work, who owns everything, and what happens after launch. Listen for plain answers you can get in writing. If someone can’t explain it simply, that’s your answer.
Last updated 14 November 2026. Written for business owners in Australia, and the questions work anywhere.
Why job-interview questions don’t help here
Most lists online are for hiring a developer onto your team: coding tests, years of experience, favourite programming language. If you’re an owner paying a developer or an agency to build something, you can’t judge any of that.
What you can judge is whether they understand your business, and whether the deal protects you. I spent two years selling offshore development to businesses in Australia and Japan, so I’ve heard most of these answers from the other side of the table.
A made-up example: you run an electrical business and want an app so customers can book and pay online. A developer who asks how you quote today, which job software you use and who answers the phone is thinking about your business. One who only talks about screens and features isn’t.
The questions
A. Have they done this before?
- Can you show me something you built that’s like this, and can I talk to that client?
- What went wrong on that project, and what did you do about it?
- Who will actually do the work? Will any of it be passed to someone else?
Listen for real examples and a client you can call. Be careful if all you get is screenshots, or a story where nothing went wrong.
B. Do they understand the job?
- In your own words, what problem is this solving for my business?
- What would you leave out of the first version?
- Is there software I already pay for, or could buy, that does most of this?
Listen for someone who pushes back and suggests something smaller, or something off the shelf. Be careful if the answer to everything is yes.
C. Money
- Is this a fixed price or hourly? If it’s hourly, what’s the cap?
- How are payments split, and what will I be able to test before each one?
- How do you price changes? Will anything be billed without my written OK?
- What will it cost each month to run once it’s live: hosting, licences, AI usage and support?
D. Ownership
- Will the code, domain, hosting and app store accounts be in my business’s name from day one?
- Do I own the code and designs once each invoice is paid, and will you put that in the contract?
E. After launch
- How long will you fix bugs at no cost?
- What does ongoing support cost, and how fast do you respond?
- If we part ways, what will you hand over so another developer can take it on?
F. AI
- Are you using AI tools to write the code? How do you check what they produce?
- Will any of my customers’ information go into AI tools, and which ones?
Answers that should stop you
- “We’ll sort the contract out later.”
- “We keep the code on our account. It’s easier.”
- “It’s hard to estimate, so let’s just start and see.”
- “You don’t need to worry about the technical side.”
- No mention of running costs, or of what happens after launch.
None of these means the developer is dishonest. It means the risk sits with you, and it’s easier to fix before you sign than after.
After you’ve asked
Get the answers in writing, in the quote itself. Then run the quote through the 12 checks before you sign.
If you’d like the whole process in one place, Before You Pay a Developer has short videos and eight worksheets: the developer brief, the quote check, the ownership list, interview questions and a trial task. It’s A$69 in Australia and US$47 elsewhere.
Not sure you need a developer at all? Take the free check. It gives you one of four answers: build, buy, wait or stop.
FAQ
Do I need to be technical to ask these questions? No. Every question is about your business, your money and what you own. You’re judging the answers, not the code.
How many developers should I talk to? Two or three is usually enough. Give each one the same written brief so you can compare like with like.
Should I ask for a paid trial task? For anything sizeable, yes. A small paid piece of work over a week or two shows how they communicate and deliver before you commit to the whole build.
Should I hire a freelancer or an agency? Either can work. With a freelancer, one person is the whole team, so the handover plan matters even more. With an agency, ask who actually does the work.
Is offshore development a bad idea? Not on its own. The same things protect you either way: ownership in your name, a clear scope, milestones you can test and a handover plan.
Not legal advice. For contracts, talk to a lawyer where you are.
Matt Ainsworth is the founder of The Lean CPTO. He held product and analyst roles at MLC and AMP, spent eight years in Tokyo training teams at McKinsey, BCG, Goldman Sachs and Sony, and has coached founders for more than 10 years. He spent two years selling offshore development to businesses in Australia and Japan.