The six pillars of AI-first talent
Architect, Entrepreneur, Operator, Auditor, Explorer, Multiplier — the six competencies we screen for when hiring AI-first talent, and the questions that reveal each one.
"AI proficiency" is not a skill you can screen for with a tool list. Tools change every quarter; the underlying behaviours don't. We assess six pillars, each with its own evidence and its own failure mode.
1. The Architect
Designs the workflow before touching the task. Thinks in systems, inputs and outputs.
Ask: "Walk me through a repetitive process you inherited. What did it look like after six months?"
Failure mode: over-engineering — building systems nobody else uses.
2. The Entrepreneur
Owns the outcome, not the ticket. Finds the highest-value problem without being assigned to it.
Ask: "Tell me about work you started that nobody asked for. What happened to it?"
Failure mode: starting more than they finish.
3. The Operator
Ships. Turns the designed system into something that runs reliably, with the boring details handled.
Ask: "What broke after you launched something, and how did you find out?"
Failure mode: heads-down execution with no strategic lift.
4. The Auditor
Verifies output rather than trusting it. Knows where models hallucinate and where data goes stale.
Ask: "When did an AI tool give you a confident, wrong answer? How did you catch it?"
Failure mode: so much verification that the speed advantage disappears.
5. The Explorer
Keeps a live map of what's newly possible, and evaluates it with judgment rather than hype.
Ask: "What did you adopt in the last six months, and what did you drop?"
Failure mode: chasing novelty over stability.
6. The Multiplier
Raises the capability of everyone around them. Their improvements become team defaults.
Ask: "What are colleagues doing differently because of you?"
Failure mode: teaching instead of delivering.
Scoring the pillars
Don't average the six into a single number — that hides the shape of the candidate. Score each 1-4 with evidence, then read the profile against the role. A first ops hire needs Architect and Operator high. A team lead needs Multiplier and Auditor high. Nobody scores 4 across all six, and a candidate who appears to is usually being assessed on charm.
Want the full assessment structure, including the five-stage process we install around it? Read the AI-first hiring framework.
Want this installed in your hiring process?
We run a 30-minute intro call to map your roles against the AI-first framework.
Book a 30-min intro callRelated reading
How to spot AI scripts in interviews
Candidates now arrive with AI-assisted answers. Here is how to tell rehearsed output from real thinking — the signals, the follow-up questions, and the live-work alternative that makes scripting pointless.
AI Engineering: How to Land Your Dream Job (Using the Skills Map)
A practical playbook for landing an AI engineering job — built on Andrew Ng's four-skill map, with the portfolio, interview answers and signals hiring teams actually reward.
AI-First vs. AI-Native vs. Digital-First: What's the Difference?
AI-first, AI-native and digital-first are often used interchangeably — they are not. Clear definitions of each term, and why the difference matters for hiring.