The rounds that are not about code

Two parts of a hiring loop contain no code and still decide outcomes: a values round about how you actually think about AI risk, and the question of whether you may use an AI assistant in a given round. This section covers both. The first cannot be rehearsed, because what is assessed is whether the position is yours and holds up over three exchanges of pushback, and a borrowed one does not. The second is not something to infer from the room: the rules differ by company and by round, so you ask the recruiter beforehand, in writing.

Two underprepared rounds#

Both of these are non-technical in the sense that no code is written, and both decide outcomes. Candidates prepare for neither, because neither looks like an interview.

Mission and values#

At least one frontier lab runs a standalone non-technical round on ethical reasoning and a candidate's actual relationship to AI risk, and it is reported as a round where technically strong engineers fail. Big tech runs a structurally similar thing against a published set of principles, sometimes with an interviewer who can veto the loop on their own.

What is being assessed is not a conclusion. It is whether you have thought about the question at all, and whether the position you hold stays the same when it is pushed on. Two answers fail equally: performed doom, which is a position adopted for the room, and dismissiveness, which reads as not having engaged with why the organisation exists.

So the preparation is real work rather than rehearsal. Read what the organisation has published about why it does what it does, and form an actual response to it: which parts you find convincing, which you do not, and what would change your mind. That last one is the question most people have no answer to, and it is asked.

Where you disagree is a real question#

When you are asked where you disagree with the organisation, it is not a trap and it is not a modesty prompt. The expected answer is a disagreement. A candidate who says they agree with everything has either not read anything or is managing the room, and both are visible.

Weak      "I agree with the whole approach, that's why I applied."
Weak      "I think this technology could end humanity and that
           terrifies me."       (if you do not in fact think this)
Weak      "I don't really buy the risk stuff, I just want to build."

Stronger  A specific position, held for stated reasons, that you
          can defend for three follow-ups and revise if the
          interviewer supplies something you had not considered.

Being pushed on is the point. Expect the interviewer to argue the other side, including a side they may not hold, and to keep going for two or three exchanges. Holding a position is not refusing to move: conceding a specific point while keeping the position is a strong answer, and abandoning the whole position under mild pressure is not.

Consistency across the loop#

The values round is not the only place this is checked. What you say about why you want the job in the recruiter screen, what you say about a trade-off in a design round, and what you say in the values round are compared afterwards, particularly where hiring decisions go through a committee or a debrief rather than one manager.

A candidate who describes careful deployment as their central concern and then, in a design round, proposes shipping a model to users with no evaluation gate has answered inconsistently, and the debrief will notice. Say the thing you actually think, in every room, and this problem does not arise.

The AI-assisted round#

The rules on using an assistant genuinely differ by company and by round within one company. Some AI-native companies now require you to use one and judge how well you direct it. At least one frontier lab publishes candidate guidance on where assistants are and are not permitted in its process. Some organisations ban them in the first screen and allow them later, and some ban them in live rounds while explicitly allowing them on a take-home.

None of that is stable enough to assume, in either direction. The only safe move is to ask beforehand, of the recruiter, in writing, for each round.

To the recruiter, before the loop:

"Can you confirm the policy on AI assistants for each round?
I want to make sure I am set up the way you expect, including
whether it differs between the screen, the live rounds and
any take-home."

Being watched while you direct an assistant#

Where use is expected, what is assessed is direction rather than output. The interviewer is watching how you frame the request, whether you read what came back, and what you do when it is wrong.

• State the intent before prompting: what you are asking for and why this part rather than another.
• Ask for the piece you have decided on, not for the problem. Handing over the whole question is the clearest signal of not having a design.
• Read the output aloud and say what you are checking: the edge case, the type, the assumption it made silently.
• Catch the wrong answer. An assistant that produced a plausible bug and a candidate who noticed is the best possible version of this round.
• Say when you are not using it, and why. 'This part is twenty lines and I know exactly what I want, so I will type it' is a decision, not a refusal.

The failure that reads worst is accepting output you have not read, particularly when it is subtly wrong and the interviewer can see it. The second worst is silence: pasting a prompt, waiting, pasting the result, and never saying what you expected. That is the same silence problem as any other round, with a second participant.

Being unable to work without an assistant is as visible as being unable to work with one. Both are tested, sometimes in the same loop: a screen with tools banned followed by a take-home where they are allowed measures exactly these two things, and a candidate weak at either end shows it.