Let the dual-loop candidate pick her team - then stop the other loop rather than finish it

September 7, 2026 at 5:00 PMpeoplemedium

Situation

Kristin Cox was interviewing for open roles in both Justin Haynes org and Chris Wolford org. Bree wanted her steered toward Wolford req on the grounds that it had been harder to find strong candidates for. Peter overrode that without debating it. His instruction: have Bree ask the candidate directly which role she is most interested in; if she picks Justin, stop the Wolford process immediately and get an offer out as fast as possible; if she picks Wolford, let that loop finish. He told Justin to be selfish about it and said he would write to Bree himself. He also stated plainly that all else equal his thumb is on Justin side of the scale, because he is far more worried about delivery on the Linux side of the house than on the Fuzzball side.

Reasoning

The candidate own preference is the decisive input, and Bree req-difficulty argument is a recruiting-throughput consideration being applied to a placement question - the wrong owner for that call. Peter routed the question to the candidate rather than arbitrating between two orgs. The urgency is loop latency: two other candidates, Derek Heeren and Jesse, were already a week stale after their loops and Justin could not move on them until the Kristin branch resolved, so asking her collapses a branching wait into a single answer. Peter was explicit that his preference for Justin org should not weigh the decision and that he would apply it anyway - an honest statement of bias rather than an org-design rationale.

Additional Context

Peter noted Apple would not have permitted a candidate to run two internal loops simultaneously in the first place, and that this is precisely the mess it exists to prevent. Both of Justin open roles were live at the time, which raised the stakes on resolving Kristin quickly.

Observed Evidence

Peter: Let us just bias towards not wasting anybody time. Interviewing for the sake of interviewing is not, it does not help anybody. / Peter: Well, you should be selfish. And I do not care what Bree wants. I can write to Bree. That is fine. / Peter: I am way more worried about our delivery on the Linux side of the house under me than I am about our delivery on the Fuzzball side. So if she is interested in your role, I would rather see her go to you. Also, if I am being selfish. And that is a pretty strong preference for me. Not that that should weigh things.

Matching Patterns

60%
Reclassify to Route - Decide Who Owns It, Then Give a Criterion Not a Verdict(names the owner of the question - the candidate herself, supplies a criterion rather than a verdict, declines to argue the original framing)

Confidence Breakdown

33/35
Evidence
15/30
Pattern
19/20
Source
9/15
Corroboration

Reasoning Depth Analysis

Org Signal:Candidate time and interviewer time are both real costs, and recruiting convenience does not get to allocate engineers between engineering orgs.
Who Affected:Chris Wolford, whose loop gets cut short mid-flight; Bree, overruled - though Peter took writing to her onto himself; Derek Heeren and Jesse, unblocked once the branch resolves.
Precedent:When a candidate is in two internal loops, ask them. Recruiting does not get to arbitrage the answer against req difficulty.
Consequences:Real - the Wolford process stops before completion if she picks Justin.
Timing:Now because two other candidates are going stale and Wolford loop finishes mid-next-week, so the branch had to collapse before both decayed.

Source

reflection

AI Confidence

76%

Related Context

🎥
Justin <> Peter Weekly 1:1

fathom

I would ask that we ask Kristen which role she is most interested in. And if she thinks it is Wolford, then yeah, let her finish that process. If she thinks it is yours, then I would stop the Wolford process and get her an offer ASAP.

Outcome

No outcome recorded yet.

Decision ID: c1d413e6-80d1-4b05-ac76-422bdfa64985