Shaped Interview Panel with Veto Condition for Performance Engineering Hire
Situation
When Greg wanted to add Cedric to the interview panel and reduce from 5 to 4 interviewers, agreed Bjorn could be dropped but set a condition: a NO from Max or Peter must count as a veto.
Reasoning
This is a performance engineering hire for the 'performant' space — directly connected to the lab boundary decision. Getting the right person matters or Greg may point to a bad hire as proof Engineering can't execute. Dropping Bjorn preserves the technical evaluation — Max brings Chief of Staff perspective and Peter brings CTO judgment. Bjorn's Product lens is less critical for a performance engineering role. The veto condition ensures the engineering leadership team retains a hard stop on candidates who don't meet the bar, even with a reduced panel.
Additional Context
Bjorn proposed the interview panel: himself, Max, Peter. Greg wanted to add Cedric (performance engineering domain expertise) but 5 interviews is too many. Peter's response was to drop Bjorn if needed but retain veto power. This hire is likely for the 'performant' initiative Greg is driving through his lab.
Observed Evidence
Direct quote from Peter in #distinguished-leaders setting the veto condition. Greg's message provides the context of wanting Cedric added and needing to drop someone. Bjorn's original message proposed the panel: 'Me, max, Peter.' Peter's response received a +1 reaction.
Matching Patterns
Confidence Breakdown
Reasoning Depth Analysis
Related Context
slack
If you have to drop one person from that list - the only one you can drop is Bjorn. But... my strong ask then would be that a NO from Max or myself counts as a No....
slack
I'd like to include Cedric or someone else who knows something about performance engineering in the lineup. Five interviews is too much. Who should we swap out?
Outcome
No outcome recorded yet.
Decision ID: 575e2cce-02e4-4d9e-be4a-7c38814bc3bb