# taylor-sierra-ai-native-interview-engineering-hiring-2026-04-20

## Veille

AI-native job interview at Sierra — Overhaul of engineering hiring process — Plan/Build/Review — Sierra Blog

## Titre Article

The AI-native interview

## Date

2026-04-20

## URL

https://sierra.ai/blog/the-ai-native-interview

## Keywords

job interview, AI-native hiring, hiring process, software engineering, coding agents, product thinking, plan-build-review, strengths-based evaluation, system design, debugging, onsite, Sierra, Bret Taylor, Codex, Claude Code, engineering culture

## Authors

Bret Taylor

## Ton

**Profile**: Corporate blog post by the co-founder and CEO of Sierra (also chairman of the board of OpenAI), professional-visionary register, intermediate level.

**Description**: Bret Taylor adopts the tone of a convinced and pragmatic tech leader, presenting the hiring process overhaul as a natural response to the deep transformations of the software engineering profession in the age of AI. The style is clear, structured, and accessible, alternating between observation (coding agents are upending software engineering) and concrete proposal (the Plan/Build/Review format). Authority comes from the author's stature — former co-CEO of Salesforce, chairman of OpenAI, co-founder of Sierra — and from the real-world implementation of the process described. The target audience is twofold: prospective engineering candidates (employer branding effect) and tech leaders looking to modernize their own hiring processes.

## Pense-betes

- Sierra has completely dropped classic coding and algorithms interviews — a strong signal that traditional technical evaluation (LeetCode) is losing relevance in a world where coding agents do the bulk of implementation work
- The new process is structured in three phases: Plan (product ideation), Build (2 hours of autonomous building with AI tools of choice), Review (demo, code review, discussion of the path to production)
- Key philosophy: when a single engineer can build across the entire stack, the advantage comes from the combination of technical thinking + product thinking + business context — not from the ability to solve algorithmic puzzles
- The software engineer's role is evolving from "building the machine" to "designing and refining the machine" — coding agents like Codex and Claude Code are the catalyst
- Sierra hires for strengths ("spikes") rather than the absence of weaknesses — which radically changes the evaluation grid
- The classic coding phone screen is replaced by a system design interview — reflecting the growing importance of knowing how to ship code to production at scale versus knowing how to write code
- Sierra is piloting a debugging interview: the candidate receives a mid-sized codebase and a fictional colleague's draft PR, and must review and improve it by iterating with coding agents
- Evaluation criteria are agnostic to what the candidate builds — what is assessed is initiative, judgment, systems understanding, and product thinking
- Interviews are conducted with pairs of evaluators to improve calibration
- Candidate feedback is very positive: "the most fun interview they've ever had" — examples: one candidate built an AI game keeping players in a flow state, another built a headless simulation tool driven by an agent via a markdown file
- The onsite takes place physically at Sierra's offices — the format requires a real working environment, not just a whiteboard or an online editor
- This type of hiring process could become a standard for AI-native companies, but raises the question of accessibility: not all candidates are comfortable with 2 hours of product building under pressure

## RésuméDe400mots

In "The AI-native interview," Bret Taylor, co-founder and CEO of Sierra, describes the complete overhaul of the company's engineering hiring process to adapt it to the realities of AI-native development. The starting observation is clear: coding agents like Codex and Claude Code are upending software engineering. The engineer's role is no longer to "build the machine" but to "design and refine it." When a single engineer can build across the entire stack thanks to AI tools, competitive advantage comes from the combination of technical capability, product thinking, and business context — not from solving algorithmic puzzles.

Sierra's old process was standard: two coding interviews, one algorithms interview, one system design interview, one culture-fit interview, then reference checks. The new process rests on three attributes: being representative of real day-to-day work, producing rich signal on the candidate's strengths and weaknesses, and offering a positive and authentic experience.

The core of the overhaul is the new three-phase AI-native onsite. During the "Plan" phase, the candidate leads an ideation session to define a product to build, while evaluators ask questions to enrich the proposal. The idea is centered on the candidate's area of expertise to observe their product thinking in action. During the "Build" phase, the evaluator leaves the room and the candidate has two hours to bring their idea to life, using the AI tools and frameworks of their choice, with the freedom to pivot or adjust scope. Finally, during the "Review" phase, the candidate presents what they built: evaluators debate the product choices, examine the code to assess technical judgment, discuss the path to production, and explore how AI was used.

Beyond the onsite, Sierra has replaced the coding phone screen with a system design interview, deemed more relevant for assessing the ability to ship code to production at scale. The company is also piloting a debugging interview in which the candidate receives a mid-sized codebase with a colleague's draft PR, and must review and improve it by iterating with coding agents.

Evaluation criteria are agnostic to the product built, and interviews are conducted in evaluator pairs to improve calibration. Sierra explicitly hires for strengths rather than the absence of weaknesses. Candidate feedback has been enthusiastic: several have said it was "the most fun interview they've ever had."

## GrapheDeConnaissance

- Sierra —améliore→ processus de recrutement ingénieurs (METHODOLOGIE, 0.98)
- Bret Taylor —publie→ The AI-native interview (DOCUMENT, 0.95)
- Bret Taylor —affirme_que→ les agents de codage transforment le rôle d'ingénieur de "construire la machine" à "concevoir et affiner la machine" (AFFIRMATION, 0.95)
- Onsite AI-native —remplace→ entretiens codage et algorithmes classiques (METHODOLOGIE, 0.97)
- Onsite AI-native —est_basé_sur→ trois phases Plan/Build/Review (METHODOLOGIE, 0.98)
- Phase Build —est_instance_de→ session de 2 heures avec outils IA au choix (CONCEPT, 0.95)
- Sierra —utilise→ recrutement pour les forces (spikes) plutôt qu'absence de faiblesses (METHODOLOGIE, 0.93)
- Entretien de system design —remplace→ phone screen codage (METHODOLOGIE, 0.95)
- Sierra —utilise→ Entretien de débogage (METHODOLOGIE, 0.9)
- Pensée produit —surpasse→ résolution algorithmique (CONCEPT, 0.9)
- Codex —est_instance_de→ catalyseur de la transformation de l'ingénierie (CONCEPT, 0.88)
- Claude Code —est_instance_de→ catalyseur de la transformation de l'ingénierie (CONCEPT, 0.88)
- Bret Taylor —a_créé→ Sierra (ORGANISATION, 0.98)

---
Canonical: https://www.thekb.eu/en/fiches/taylor-sierra-ai-native-interview-engineering-hiring-2026-04-20/