How to screen engineers when your team isn't technical

Plenty of people who hire engineers cannot evaluate engineering work themselves: founders, office leads, hiring managers in growing teams. That is fine for the first half of a process and a problem for the second half. The trick is knowing exactly where the line is, and not pretending it is somewhere else.

What you can run yourself

A non-technical interviewer can do the early filtering well, because the early filter is mostly about clarity, motivation, and fit, not depth.

• Spend five to ten minutes before each call on the resume, the GitHub or portfolio, and the LinkedIn history. Walk in knowing what to ask about.
• Use structured questions with clear answers for the first pass: scope of past work, team size, what they owned versus what the team owned, why they are leaving.
• Ask people to explain a recent project in plain language. You cannot judge the code, but you can judge whether they can think clearly and communicate, which predicts long-term success better than puzzle performance.

Where you have to stop

The moment the question becomes can this person actually do the work, a non-technical interviewer is guessing. Confident, articulate candidates pass these stages whether or not the depth is real, and quiet ones who are excellent get cut. This is the single most expensive failure in the process, because a wrong technical hire costs months.

If you have not done the work, do not grade the depth. Bring in someone who has, or you are scoring confidence, not competence.

How to cover the gap

You have three honest options for the technical depth check, in rough order of cost.

• Borrow an engineer. A current engineer on your team, or a trusted one in your network, sits in for one focused conversation on the real stack. Cheapest when you have the relationship.
• Use a work sample. A short, paid, realistic task that mirrors the actual job tells you more than a whiteboard puzzle, and a technical reviewer can grade it asynchronously.
• Use a partner who screens with a practicing engineer. For our engineering desk, candidates are screened by a practicing engineer before they reach you, so the depth check happens before you spend a minute on it.

The mistake is not being non-technical. The mistake is letting that fact stay invisible until a bad hire makes it obvious. Run the parts you are good at, name the part you are not, and put a real technical judgment in the loop before anyone signs.