Do you actually need a full-time hire?

Before you post that job listing, think about what you actually need done. If it’s a specific project with a clear end date, a contractor might be the better move. If it’s ongoing maintenance and feature work then yes, hire someone.

The worst outcome is hiring a full-time engineer for what turns out to be three months of work. Now you have a $150K per year commitment for a role that doesn’t have enough to do.

Can you actually evaluate this person?

If you’re a non-technical founder hiring your first developer, you probably can’t tell the difference between a solid mid-level engineer and someone who interviews well but can’t ship.

Get help. Pay a technical advisor for two hours to sit in on the final interview. It’s the cheapest insurance you’ll ever buy.

What does success look like in 90 days?

If you can’t answer this question clearly, you’re not ready to hire. “Build stuff” is not a success metric. “Ship the new checkout flow and reduce cart abandonment by 15%” is.

Define the win before you write the job posting. It’ll make every other decision easier. Who to hire, how to evaluate them, and when to course-correct if things aren’t working.