How to Hire a Developer When You’re Not Technical
Most founders will hire a developer the same way they hire anyone else. They look at price, portfolio, and personality, but these are the wrong filters.
Hiring a developer without a technical background does not mean you are flying blind. Instead it means your evaluation will have different criteria than developers are accustomed to. This is how you can evaluate a developer you can’t technically assess yourself.
1. Know what you are hiring for before you talk to anyone
Before evaluating a developer you need to know what you’re building, what done looks like, what features the application needs, and your budget and timeline. These elements, defined clearly, are what a developer needs to know to write a proposal. If you cannot clearly articulate what you want built and what success will look like, then you are not ready to talk to developers yet.
2. Choose the right model first
There are several models founders can choose from for their development needs: Freelancer, Agency, Offshore, or In-House. Each model has different tradeoffs and costs associated with it. Freelancers are best for contained, well-defined projects. Agencies make sense when the project is complex. Offshore reduces costs but requires a lot more oversight. In-house makes sense for on-going work. Choosing the right model before you start talking to developers is as important as choosing the right developer. Choosing the wrong model will be more expensive than choosing the wrong person in the right model.
3. Evaluate the work not the resume
With a clearly defined definition of done and model chosen, you can then begin evaluating developer options. Each developer should be able to point you to a launched product. A portfolio of projects is not enough. Instead, ask to see finished products that actually shipped and ask what their contribution was.
4. Ask the right questions
Founders need to understand who is building the software, how their developer handles scope changes, how they estimate work, the processes if timelines go over planned, and who owns the code when the work is done. Knowing the non-technical questions to ask will avoid spending money on a developer who will not give you what you are asking for. I previously wrote about the five questions that founders should ask when evaluating developers. Worth reading before your first developer conversation.
5. Run a technical screen
No matter what, your developer should demonstrate their skillset to you, but you don’t have to run the screening yourself. An advisor, trusted technical contact, or developer friend can conduct a simple practical exercise. You should never hire a developer without seeing evidence of their actual work.
6. Start small before committing big
If possible, the first paid engagement should be small and specific. This allows you to evaluate your development team without committing to the full cost of your project. By creating a bite-sized project you will learn how the developer communicates, whether they deliver on their commitments, and whether the relationship is one you want to continue without getting locked into long-term contracts.
Getting clarity on what you are building is the single most important thing you can do to protect yourself before talking to developers. Hiring the developer can be done without a technical background – you just need to be specific during the hiring process.
If you are considering hiring a developer, book a free45-minute call. No pitch – just a real conversation.
