Rethinking Your Engineering Hiring Process & Signals for the AI Era

Abstract

AI has distorted the signals we rely on to hire engineers. CVs are increasingly tailored, screening can be rehearsed, tech tests can look “perfect,” and even system design and behavioural answers can be polished in ways that don’t reflect real on-the-job judgement. The result: many teams feel less confident in hiring decisions, even as they add more process.

This talk reframes hiring as a measurement problem. We’ll walk the funnel end-to-end and use a simple set of questions at each stage: what are you trying to measure, how does AI change the signal, what does “good” AI use look like here, and what trade-offs are you making? I won’t claim that this is solved, but you’ll leave with a practical decision model and patterns you can adapt and apply to your constraints and culture.

Key takeaways

  • Where signals break (and why “just ban it” usually isn’t the answer)
  • A lightweight way to choose your stance on AI per stage
  • Trade-offs: speed vs rigour, fairness vs control, remote vs in-person

Speaker

Reece Nunn

Software Engineering Manager @BBC

Reece is a Software Engineering Manager at the BBC, where he’s led platform and enablement teams - most recently through a major reorganisation. He began his career as a Software Engineer, building and running experiences and platform services spanning risk, identity, and account/authentication. Today he works with large-scale web and mobile platform capabilities, with a focus on reliability, developer experience, and evolving systems through change. He’s owned hiring processes and run assessment days for engineers at all levels, and is particularly interested in making hiring fair, practical, and predictive of real on-the-job judgement.

Reach out to him on LinkedIn

Read more
Find Reece Nunn at:

Date

Tuesday Mar 17 / 02:45PM GMT ( 50 minutes )

Location

Whittle (3rd Fl.)

Share

From the same track

Session AI/ML

The Ladder Is Missing Rungs: Engineering Progression When AI Ate the Middle

Tuesday Mar 17 / 01:35PM GMT

Career progression in engineering has traditionally followed a predictable path: junior tasks teach fundamentals, mid-level work builds judgment, senior roles require synthesis across systems.

Speaker image - Alasdair Allan

Alasdair Allan

Scientist, Author, Hacker, Maker, Journalist, and Head of Documentation, CTO @Negroni Venture Studios, Interim CTO @Evaro

Session organization

Team Topologies as the 'Infrastructure for Agency' with AI

Tuesday Mar 17 / 10:35AM GMT

The book Team Topologies Second Edition (2025) demonstrates convincingly that organizing business and technology for fast flow of value via empowered teams produces outsized results for enterprises worldwide.

Speaker image - Matthew Skelton

Matthew Skelton

CEO & Principal @Conflux, Co-Author of "Team Topologies", Leader in Modern Organizational Dynamics for Fast Flow

Session AI

From Copilots to Orchestrators: A Three-Month Playbook for Training AI-Native Engineering Teams

Tuesday Mar 17 / 05:05PM GMT

Most engineering teams are stuck treating AI as autocomplete. Engineers have GitHub Copilot installed (or Claude or Cursor or whatever), they're generating snippets faster, but leaders can't connect usage to business outcomes—and developers are shipping code they don't fully understand.

Speaker image - Krystal Flores

Krystal Flores

Staff Software Engineer @Crunchyroll, Previously @Carta, @Lob, @Simple Habit, and @Nordstromrack.com|HauteLook

Session

Blurring the Lines: Engineering & Data Teams in the Age of AI

Tuesday Mar 17 / 11:45AM GMT

Every senior engineer knows the feeling: a model makes a bad decision, a customer complains, and suddenly you're debugging a system that spans three teams, two pipelines, and a machine learning model nobody fully owns. Where do you even start?

Speaker image - Priscilla Nagashima

Priscilla Nagashima

VP of Data and AI @Pleo

Session

Unconference: Building Engineering Teams

Tuesday Mar 17 / 03:55PM GMT