Guide

Questions to ask before hiring a freelance developer (or agency)

By Fahad Tariq, founder of Zirah Tech · Published November 3, 2026

A developer who quotes a fixed price from a two-sentence brief is guessing, and you will pay for the guess later. These are the questions to ask before hiring a freelance developer, with what a good answer sounds like and when to walk away.

Judge the questions they ask you before you judge their answers

Start with how they handle your brief. One freelancer-written guide puts it directly: a developer who reads your brief and sends a price right away is guessing, while one who asks about stack, timeline and expected users is thinking about the real problem (CodeYug).

Then ask:

• "Tell me about a past project: what was hardest, and what would you do differently?" You want the story behind the work, including trade-offs (CodeYug).
• "Describe your most unhappy client and what happened." A team that cannot answer is just trying to win you over, one agency author argues. Listen for what went wrong and what was learned (Keene Systems).
• "Can I talk to a client from that project?" The same author suggests asking for the reference from the project that went wrong.
• "Who will actually write my code?" With an agency, ask for the names, seniority and whether any work is subcontracted (Selleo). One list warns that some firms show local offices but outsource the work (TopDevelopers).
• "What part of this are you not the right person for?" Good developers push back on bad ideas. Agreeing to everything is a flag (CodeYug).

Get a scope and a price that follow each other

Most vendors offer some mix of hourly, fixed-fee and retainer pricing (Grover Web Design). Fixed suits clear scope, hourly suits unclear scope. A confident fixed price on a vague brief means they are underquoting and will ask for more mid-project, or plan to deliver the minimum (CodeYug).

Ask:

• "What is included, and what costs extra?" Hosting, third-party services and post-launch changes are the usual surprises. Ask for an itemized estimate.
• "What happens when I change my mind?" Keene Systems makes the point that an estimate covers only the work in the agreed design, so any change comes with a cost. Ask to see the cost before change work starts (Keene Systems).
• "How are payments tied to progress?" One source describes 30% upfront, 40% midway and 30% at launch as typical (Grover Web Design). Splits vary; money should follow delivered milestones.
• "Will I get a written proposal?" Deliverables, milestones, timeline, price. Scope that lives only in chat gets remembered differently by each side.

Get ownership of code, accounts and data in writing

Do not assume that paying makes you the owner. In US copyright law, the source of ownership is the author of the work, and a transfer of ownership is valid only if it is in writing and signed by the owner (17 U.S.C. 201 notes; 17 U.S.C. 204 notes). Commissioned "work made for hire" is limited to specific statutory categories and needs a written agreement; a Copyright Office result states the written-agreement requirement (Copyright Office, Circular 30). So the safe route is a written assignment of the code to you. This is general information, not legal advice; have a lawyer review the contract.

Ask:

1. "Will the contract assign all code and deliverables to me?" One agency author calls this a one-answer question: the client owns it (Keene Systems).
2. "Will the code live in my repository from day one?" Losing access to your codebase and project assets is on the standard red-flag list (Security Boulevard).
3. "Whose accounts is this on?" Hosting, domains, app stores and payment tools should be in your name. Selleo separates legal ownership from practical control of repositories, cloud accounts, documentation and knowledge (Selleo).
4. "Will you sign a mutual NDA?" Settle this before sharing sensitive details.

Make progress visible, and test the relationship with a small paid task

A team that is not open about process and progress is a major concern (Security Boulevard). Ask how often you will see working software, not slides, who your single contact is and how work is tracked. Selleo describes weekly demos, clear estimates and early risk flags as the kind of evidence worth asking for (Selleo).

Then reduce the risk before you commit. CodeYug calls a paid test task the most useful thing you can do: pay for 4 to 8 hours on a small, real piece of your project, and you learn whether they can do the work, communicate during it and deliver on time (CodeYug). Selleo makes a similar case for a bounded pilot before a larger commitment (Selleo).

Ask what happens after launch and if the developer disappears

• "What support is included, for how long, and how fast do you reply to an outage?" Get numbers and a channel. Support usually means bug fixes, small updates and monitoring (Grover Web Design).
• "What if you are unavailable for two weeks?" A solo freelancer is a single point of failure. That is not disqualifying, but ask for a plan.
• "What do I get at the end?" Deployed code, documentation and a handover that lets another team continue. Selleo's test: ownership without usable access and knowledge can still create dependency (Selleo).

Walk away when you hear these answers

• Yes to everything, no questions back.
• A fixed price from a vague brief.
• No story behind past work, or no reference.
• Your code, hosting or domains in their accounts.
• No demos until the end, slow replies before you pay.
• Resistance to a written scope or contract.

One red flag is a reason to ask a follow-up. Three is a reason to move on.

Score every candidate the same way

A scorecard makes interviews comparable. Score each area 0 (evasive), 1 (vague) or 2 (specific and checkable).

How Zirah Tech answers these. Zirah Tech works on fixed-scope projects, monthly retainers or advisory hours, starting with a free 30-minute call and a written proposal with milestones. Code goes in your repo from day one, you own the code, accounts and docs, and there is no lock-in. Hold every candidate, including us, to the same list. See the approach or book an intro call.

FAQ

What questions should I ask my web developer or agency? Start with their questions to you, a past project and its problems, and a reference. Then cover scope, price and changes, ownership, progress visibility and support. For an agency, add who does the work and whether any is subcontracted.

How do I vet a freelance developer if I am not technical? Judge evidence, not code: their questions, the story behind past work, a reference who answers, written scope and ownership terms, and a small paid task.

Who owns the code when I hire a freelancer? Under the US sources above, ownership starts with the author and a transfer must be in writing and signed. Ask for a written assignment to you, and have a lawyer check it. This is general information, not legal advice.

What are the biggest red flags when hiring a freelance developer? Agreeing to everything, a confident fixed price on a vague brief, no story behind past work, no reference, holding your code or accounts, and going quiet between updates.