Finding a developer when you're not technical is hard. You can't evaluate their code. You don't know the right questions to ask. And bad developers are really good at sounding impressive. Here's how to tell the difference.
Green Flags: Signs of a Good Developer
- They ask about your business, not just features. A good developer wants to understand why you're building this, who it's for, and how you'll make money. If they just ask for a feature list, they're treating you like a ticket, not a partner.
- They show you real work. Not mockups or designs. Real apps you can download or visit. Ask for 2 to 3 projects and actually check them.
- They explain things in plain English. If they hide behind jargon, they either can't communicate well or they're trying to impress you instead of help you.
- They give you a clear price range early. Not after weeks of "scoping calls." A good developer can give you a ballpark on the first call.
- They tell you what NOT to build. Great developers push back on features that won't help your business. They save you money, not just take it.
Red Flags: Run Away If You See These
- No portfolio or "NDA'd projects." Every developer should have at least a few projects they can show. If everything is under NDA, that's suspicious.
- "It depends" with no follow-up. If they won't give you any price range until you pay for a scoping phase, they're either hiding something or don't know their own pricing.
- They want to start coding immediately. No plan, no blueprint, just "let's get started." This almost always leads to budget overruns.
- Slow communication early on. If they're slow to respond before they have your money, imagine how they'll be after.
- They say yes to everything. No pushback, no questions, no "are you sure you need that?" They're agreeing to get the contract, not to help you succeed.
Questions to Ask on the First Call
- "Can you show me 3 apps you've built that I can actually use?"
- "What would a rough price range be for something like this?"
- "How often will I see progress and give feedback?"
- "Do I own the code when it's done?"
- "What happens after launch? Do you offer support?"
The Best Test
After your first call, ask yourself: "Did I understand everything they said?" If yes, that's a good sign. If you left the call confused and nodding along, that developer is not right for you.