Set the Sr. Application Engineer comp anchor on internal team parity, not on the candidate Amazon total comp

Situation

Justin Haynes brought Peter a compensation question on Kristin Cox, a Sr. Application Engineer candidate coming from Amazon, whom Peter had interviewed four days earlier. Peter ruled the Amazon number out entirely - nowhere near that, you are not going to compete with Amazon on TC - and gave Justin the reference class to use instead: look at the rest of your team for the barometer. He named what CIQ is actually selling in place of cash, saying she comes to a startup for the moonshot. He gave Justin the barometer rather than a number, leaving the offer construction with him.

Reasoning

Two claims, and the second carries the decision. The first is that a total-comp contest with Amazon is unwinnable, so bidding on that axis loses regardless of the number. The second and load-bearing one is that the correct reference class is the team the person will join: an external anchor imported for a single hire creates a compression problem that CIQ then pays for across everyone else indefinitely. Naming the moonshot is Peter stating the axis CIQ actually competes on - equity upside and scope - and declining to compete on the one where it cannot win. Consistent with the leveling work in flight, where the job rather than the incumbent sets the band.

Additional Context

Peter had flagged the risk to himself four days earlier in a group DM with Justin and Brianne Clasen - love Kristen, hate that she is from Amazon, but love Kristen - before any comp question was raised. This is the same requisition on which Peter issued a Strong No to a different candidate on 9/7.

Observed Evidence

Direct quote of the ruling in DM, plus Peter own pre-emptive flag of the comp risk four days earlier. Confirmed by Peter in review, including that the 9/7 Strong No was a different candidate for the same requisition.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis