Many AI interviews test memorised definitions. But knowing what a transformer is does not tell you whether someone can deliver a working tool to your team. Focus instead on how candidates think about real problems.
Problem-framing questions
- "Here is our problem. What would you build first, and what would you deliberately leave out?"
- "How would you know this project is succeeding after one month?"
- "When would you not use AI for this?"
Good sign: they ask about users, data and success metrics before naming technologies.
Practical engineering questions
- "Walk me through an AI feature you put into production. What broke after launch?"
- "How do you handle slow or failed responses from an AI API?"
- "How do you keep API keys and customer data secure?"
- "How do you test a feature whose output changes every time?"
Quality and evaluation questions
- "How would you measure whether the assistant's answers are correct?"
- "What would you do if users report wrong answers?"
- "How do you reduce made-up (hallucinated) answers?"
Cost and operations questions
- "How would you estimate the monthly running cost?"
- "How would you reduce cost if usage doubled?"
Communication questions
- "Explain this project to our sales manager in two minutes."
- "How would you report progress each week?"
The best predictor: a small paid task
Give a realistic, time-boxed task using sample data — for example, extracting fields from five invoices or answering ten questions from a handful of documents. Review:
| Look at | Why |
|---|---|
| Working result | Can they deliver? |
| Code clarity | Can others maintain it? |
| Notes on limitations | Are they honest about weaknesses? |
| Next-step suggestions | Do they think about the business? |
Prefer pre-vetted developers? You can interview our developers for free before deciding.