Kairos hiring kit

Hiring in the age of AI

What good looks like has changed. Pick the kind of role you're hiring and get the job ad changes, the interview questions and a scorecard to use in the room. It takes about five minutes.

What we're seeing

The people doing best in startups right now have changed how they work in the last year, and they can tell you exactly how. AI has made a strong generalist far more capable, so the things most job ads still screen for, like years in a particular tool, a specific degree or a big-company logo, tell you less than they used to.

At early stage, hire generalists who believe in what you're building. Move to specialists when the outcome you need changes and you need real depth in one area to keep growing. Headcount alone is a poor trigger.

The most expensive mistake we see is hiring from large corporates on large salaries for early roles. People bring the playbook they know, and the startup loses the speed that was its advantage.

If you're hiring into a function you don't know well yourself, brief on the outcomes you need in the first year and use the interviews to see how strong candidates would get there. The best of them will help you shape the role.

Step 1: choose the role

Step 2: rewrite the job ad

Cut

  • "X+ years of experience in [tool]"
  • "Degree required" where the role doesn't need one
  • "Experience at a large or well-known company"
  • "Must have done this exact role before"

Add

  • What they'll own and achieve in their first year
  • How AI is part of the way your team works
  • That you want people who unblock themselves and make calls with incomplete information
  • Why someone should join you now, in your own words

Copy-ready opening

We're a small team building [product] for [customer]. In your first year you'll own [outcome]. We care more about how you think and how you've adapted than how long you've spent in a particular tool. If the way you work has changed in the last year and you can show us how, let's talk.

Copy text

Step 3: ask these questions

"Walk me through how your day-to-day work has actually changed in the last 12 months because of AI. What do you do now that you didn't before, and what have you stopped doing?"

Shows whether they've genuinely adapted or just know the vocabulary.

Listen for

  • Specific changes to how they work
  • Something they've stopped doing
  • Judgment about when AI helps and when it doesn't

Watch out for

  • "I use ChatGPT for emails sometimes"
  • Talking about AI in the abstract
  • Nothing has changed

"Tell me about a time you were completely blocked and there was no one senior to help. What did you do, and how did it resolve?"

Shows self-direction and whether they'll make a call under uncertainty.

Listen for

  • What they tried first, second and third
  • A decision they made and owned
  • What they changed once they saw the outcome

Watch out for

  • "I raised it in stand-up and waited"
  • Escalating as the first move
  • No specific example

"What's something you believed about your craft 18 months ago that you've changed your mind about? What changed it?"

Shows a pattern of evolving. People who can't name anything usually haven't.

Listen for

  • A specific belief and what replaced it
  • The evidence that changed their mind

Watch out for

  • "I've grown a lot" with no detail
  • A tiny change described as a big one

"If you had ten times more access to AI tools than you have now, what would you do differently in this role? Be specific."

Shows whether they've thought about what AI makes possible for the team and the business.

Listen for

  • A clear change in how they'd operate
  • Impact on the team or company as well as themselves

Watch out for

  • "I'd probably be faster"
  • Describing what they already do

Step 2: rewrite the job ad

Cut

  • "5+ years of experience in [language or framework]"
  • "Computer Science degree or equivalent"
  • "Deep expertise in [specific technology]"
  • "Strong algorithms and data structures knowledge"
  • "Experience in enterprise-scale engineering teams"

Add

  • You ship end-to-end and own features from problem to production
  • You've worked across the stack or can show you can
  • You frame the problem before writing code, and push back when the brief is wrong
  • AI is built into how you work every day
  • You monitor and stay accountable after something ships

Copy-ready opening

We're hiring engineers who ship. You'll own features from problem definition through to production, with AI built into how you work. We care more about the systems you've shipped and what you learned running them than the languages on your CV. If you frame problems well, work across the stack and use AI every day, let's talk.

Copy text

Step 3: ask these questions

Use the four questions under Any role, plus this one.

"You've just shipped a feature built mostly with AI. It works, but you're not fully confident you understand every part of it. What do you do?"

Shows ownership and how they balance speed with accountability. There's no single right answer.

Listen for

  • Reviewing the output critically before owning it
  • Setting up monitoring to catch problems fast
  • A clear view on how much understanding is enough

Watch out for

  • "If it works, it works"
  • "I'd never ship code I don't fully understand"
  • No mention of what happens after merge

Step 2: rewrite the job ad

Cut

  • "10 years in SaaS or B2B sales"
  • "Proven Rolodex in [sector]"
  • "Deep Salesforce or HubSpot expertise required"
  • "Business or Marketing degree required"
  • "Track record of closing $Xm ARR" as the headline bar

Add

  • You build the revenue system and redesign it when you spot gaps
  • You use AI for research, prospecting, outreach and automation as standard
  • You read your own numbers and spot your own problems
  • You're deep in one GTM function and fluent across the rest of the funnel
  • You can show how your approach has changed over time

Copy-ready opening

We're looking for GTM people who build the system they work in. You'll read your own data, design your own playbooks and use AI tools as a natural part of how you operate. If you've got strong opinions about how revenue teams should work, and evidence your views have evolved, let's talk.

Copy text

Step 3: ask these questions

Use the four questions under Any role, plus this one.

"Tell me about a gap you spotted in your company's revenue process that wasn't technically your responsibility. What did you do about it?"

Shows whether they understand the whole funnel and take ownership beyond their own lane.

Listen for

  • How the full funnel fits together
  • Action, or escalation with a proposed fix
  • The outcome, even if imperfect

Watch out for

  • "That wasn't my area"
  • Raised it once and moved on
  • Can't describe the wider revenue system

Step 2: rewrite the job ad

Cut

  • "Expert in Figma" as a headline must-have
  • "Portfolio of high-fidelity polished work"
  • "Strong UX research background leading discovery sprints"
  • "Design review as a gate before any feature ships"

Add

  • You make the call on what gets built and defend it
  • You give feedback in real time while engineers build
  • You use AI to test directions cheaply before refining
  • You run customer discovery in days and bring back specific insights
  • You own what ships

Copy-ready opening

We're hiring designers with taste, judgment and pace. You'll work alongside engineers who ship fast, giving directional feedback in real time. You use AI to explore directions quickly, you make the call on what gets built, and you own what ships. If you've spent the last year evolving how you work, we want to hear how.

Copy text

Step 3: ask these questions

Use the four questions under Any role, plus this one.

"An engineer has used AI to build a feature overnight that would have taken two weeks before. It works, but the UX is rough. How do you approach it?"

Shows whether the designer helps work ship or holds it up.

Listen for

  • Fast, specific guidance
  • Separating "rough but right direction" from "rough and wrong direction"
  • Asking what problem the feature solves first

Watch out for

  • "It needs to go through design review first"
  • "I'd need to write proper specs"
  • Focus on polish over direction

Step 4: score in the room

Candidate scorecard

Tap a score from 1 to 5 for each dimension during or straight after the interview. Once someone clears the basics of the role, these are what separate a solid hire from an outstanding one.

Candidate: ______________________ Role: ______________________ Date: __________

AI fluency

Has genuinely changed how they work because of AI, with specific examples.

1
2
3
4
5

Autonomy

Unblocks themselves and makes calls under uncertainty.

1
2
3
4
5

Adaptability

What they do today is meaningfully different from 18 months ago, by design.

1
2
3
4
5

Role craft

The core skill for the role, shown with evidence.

1
2
3
4
5

Whole-business thinking

Understands the wider system and takes ownership beyond their own lane.

1
2
3
4
5

Total 0 / 25

Print scorecard
Clear

The research behind it

  • Hiring for skills is five times more predictive of job performance than hiring for education. McKinsey, 2022
  • In Australia, a skills-first approach makes the available talent pool 10.2 times larger. LinkedIn Economic Graph, 2023
  • 78% of employers have hired someone with strong technical skills who failed because of poor soft skills or weak motivational fit. TestGorilla, 2025
  • Organisations with a skills-based approach are 98% more likely to retain high performers. Deloitte, 2022

Hiring for one of these now?

Book a 20-minute hiring reset call and we'll pressure-test the brief, the job ad and how you'll assess candidates. Kairos is a Melbourne-based recruitment agency for Australian startups and scaleups.

Book a hiring reset call

Megan Luttrell, Founder, Kairos · LinkedIn