Don't ask "Can you do AI?" Ask questions that force them to reveal their process.
1. "How do you handle data privacy and GDPR compliance during model training?"
Why: If they hesitate, run. You cannot afford a lawsuit because they trained a model on user data without consent.
2. "Can you walk me through your false-positive reduction strategy?"
Why: Accuracy metrics are easy to fake. Reducing false positives is where the real engineering work happens.
3. "What is your approach to WCAG accessibility standards in AI-generated interfaces?"
Why: AI interfaces must be usable by everyone. This separates the amateurs from the pros.
4. "Do you fine-tune existing models or build from scratch?"
Why: This determines the budget. You don't need a scratch-built model for a simple customer service bot.
5. "How do you handle model drift after deployment?"
Why: AI models degrade over time as data changes. If they don't have a maintenance plan, the product will fail in six months.
6. "Can you integrate PCI DSS if we process payments via the AI agent?"
Why: Critical for fintech. Security compliance is not an add-on; it’s a foundation.
7. "What specific AI in marketing tools have you built previously?"
Why: Context matters. A firm good at healthcare AI might be terrible at marketing algorithms.
8. "Which AI agent platforms do you prefer for orchestration?"
Why: Tests if they are modern. Agentic workflows are the new standard; static models are the old guard.
Why: Autonomous agents are the next wave. You want a team that understands this shift.
10. "How do you view Artificial General Intelligence impacting your current codebases?"
Why: A bit philosophical, but it tests if they are future-proofing their architecture or just coding for today.