How to Interview Engineers When You're Not Technical

The 5 signals, 8 questions, and 1-page scorecard for founders who can't judge the code · by HireSphere AI

You don't need to understand the code to spot a strong engineer — or a risky one. Unlock the guide (5 signals, 8 questions with strong-vs-weak answers, red flags) and use the scorecard below on your next candidate.

Inside: the 5 signals any founder can evaluate · 8 plain-English questions with what strong and weak answers sound like · 5 red flags that need zero technical knowledge · a 1–5 scorecard with a hire / second-opinion / pass band.

Score a candidate (optional) — 1 = weak, 5 = strong

Communication — can explain technical things in business terms

Ownership — takes responsibility for outcomes and failures

Judgment — reasons in trade-offs, not absolutes

Curiosity — keeps learning and applies it

Delivery — estimates honestly and ships reliably

Please complete every item and add a valid email.

We'll email the guide and occasional hiring insights. Unsubscribe anytime.

–
/ 25 candidate score

The 5 signals you CAN evaluate without a CS degree

You can't judge their code. You can judge how they think, communicate, own outcomes, and make trade-offs — and those predict success better than a whiteboard test. Score every engineer on the five competencies below; let a technical interviewer (or ours) handle depth.

  • Communication — can explain technical things in business terms
  • Ownership — takes responsibility for outcomes and failures
  • Judgment — reasons in trade-offs, not absolutes
  • Curiosity — keeps learning and applies it
  • Delivery — estimates honestly and ships reliably

8 plain-English questions — and what strong vs. weak sounds like

1. Walk me through a technical decision you made that you'd make differently now.
Names the trade-off, what they optimised for, the business impact, and what changed their mind.
Blames the team or tooling, or can't think of one — 'it worked out fine.'
2. Explain the hardest technical problem you've solved as if I were a customer.
Plain language, an analogy, and why it mattered to the user or the business.
A wall of jargon; visibly frustrated that you don't follow.
3. Tell me about something you shipped late. What happened and what did you change?
Owns it, names the systemic cause (scope, estimates, dependencies), and describes a specific fix they still use.
Excuses, or claims nothing has ever been late.
4. How would you decide whether to build a component or buy it?
Frames cost, time, risk, maintenance, and how core it is to the product.
'Always build' or 'always buy' — no framework.
5. How do you estimate how long something will take?
Breaks work down, gives ranges, flags unknowns early, communicates when the estimate moves.
Gut numbers with false precision; never revisits an estimate.
6. Tell me about a bug or outage you caused. How did you handle it?
Transparent, fast to communicate, ran a post-mortem, prevented the class of error.
'I've never caused one' or blames whoever merged it.
7. What have you learned in the last six months, and how did you apply it?
Specific topic, specific application, honest about what didn't work.
Vague ('I keep up with things'), nothing applied.
8. If I gave you our codebase tomorrow, what would you do in your first week?
Read, ask questions, find a small safe win, learn how work flows before changing it.
'Rewrite it' before understanding it.

Red flags that need no technical knowledge

  • Can't explain their work simply.
  • The rewrite-everything reflex.
  • No ownership of a single failure.
  • Dismissive of business constraints (deadlines, budget, customers).
  • Vague on specifics when you ask "what did you do?"

Print / save as PDF →

Want the technical depth too?

"How can you evaluate technical candidates if I can't?" That's exactly what we exist for. The scorecard covers what you can see; Interview as a Service runs the structured behavioral and technical interviews — engineering included — and hands you a ranked top 3 with the reasoning written down. You borrow judgment you can verify, and still make the call.

Book an Alignment Call

30 minutes with our founders. If we're not the right fit, we'll say so on the call.

93%+ 90-day retentionPlaced by day 6090-day replacement guaranteeNo 20%+ placement fees

HireSphere AI · Built for scaling businesses doing $1M+ in annual revenue · hiresphere.ai · support@hiresphere.ai
Give the WHAT and WHY; the calibrated technical evaluation is the service. Directional guidance, not a hiring decision.