Brianne Clasen
Dec 31, 2025 - Sep 2, 2026
16
Decisions
0
Active Todos
9
Patterns
Categories
Decisions (16)
Sensitive Decision
Hire Jori Koolstra now - go into the interview intending to sell, then compress the loop to days
Peter had a 10:00 interview with Jori Koolstra for the Linux Kernel Development Engineer role on Aug 30 (a Sunday). Beforehand he asked Nathan Blackham directly whether the slot was an interview or a sell, and said his own plan was already sell: I hope it is sell because that is my plan. I also really hope I like this guy because I LOVE his resume. Immediately after the call he told Nathan Hire him now. That is my take, and in the group DM with Nathan and Brianne Clasen he wrote We should hire Jori. Like... today. In #distinguished-leaders, replying to Bjorn Hovland asking whether anything ever happened with Tim Pepper and saying We need to be better at evangelizing Rocky and We just do not have an active community leader over there, Peter volunteered the same candidate: I also interviewed a kernel engineer candidate that I LOVED today (background in math) who wants to spend a lot of time evangelizing Rocky upstream and building a community. Bjorn replied Get him. Nathan confirmed the next morning that it was a sell, said he would get the roundtable scheduled for today or tomorrow, and added that he might be trying to get him out earlier.
Keep the reference requirement because the failure to produce one is the signal - not because the reference itself is worth reading
On Aug 22, in the hiring group DM, Brianne Clasen asked whether a kernel candidate should still submit references after Nathan Blackham had objected that the ones offered were not from the relevant period of the person work history. Peter kept the requirement and separated it from its stated purpose: he would like to get one, not so much because he cares about the reference itself, but because if someone cannot find one, there is something going on. Brianne confirmed she had read it the same way. Nathan then offered to supply names of people from the relevant team the candidate could approach, which makes the negative result meaningful rather than an artefact of the candidate not knowing who to ask.
Sensitive Decision
Sensitive Decision
Sensitive Decision
Compress the Leandro Dorileo hire into a single week and run his final interview as a sell call rather than an evaluation - on the strength of Nathan like-mind endorsement alone
Nathan told Peter that Leandro (Leo) is one of a very small set of people - alongside Andrew and Dieter - with whom he can sit down and know they understand the in and out of OS engineering, and that he would have offered on the spot. Peter asked what he should cover; Nathan answered sell call. Peter accepted that framing without pushing back, immediately compressed the timeline (I would love to get it handled before the end of the week), asked Brianne to schedule a decision call for Friday morning, and told Nathan to chase Dieter and Jeff for scorecards - proceeding to his own 2pm interview before those scorecards existed. Two hours after the 1:1 he confirmed in Slack: I think I sold him. I am a yes. Lets move.
Hire Hailey Mothershead without reservation, and take John Paul as a qualified yes with a standing instruction not to chase him if he declines
At the Aug 12 kernel round table Peter gave two very different verdicts. On Hailey he was unreserved - I would hire her today, I thought she was smart, I thought she was inquisitive, I think she will work incredibly well with the team - and said that at a smaller company he would have called Brianne right after the interview and not let her leave the building without papers in front of her. He named his one real concern, a complete lack of C experience, and dismissed it as learnable, and flagged that she will find CIQ feedback culture blunt. On John Paul he deferred entirely to the technical panel, said he did not enjoy the interactions, did not believe JP is interested in what CIQ is doing, agreed with Shreeya read that they are getting roughly a year, and said he would not block a consensus yes. He then added the operative instruction: if we make an offer to him and he does not accept, let us not kill ourselves to make it work out. He closed the meeting with I know this team has felt pressured. I do not want this pressure to bring in the wrong person.
Sensitive Decision
Proceed with the Patrick Culp offer as US-only and say absolutely nothing about the future - if we lose him, we lose him
Nathan raised that Patrick Culp intends to relocate to Japan with no firm date, and Brie asked whether to proceed and how to shape the offer. Nathan proposed telling him relocation is not something we would be open to in the short term and would have to be re-evaluated. Peter judged that about 80 percent correct and cut the remaining 20 percent hard: I would not make any future looking statements, even something - I would not make any future looking statements, period. We just do not know what is going to happen. Even in the short term, we do not know what is going to happen. What he authorized instead was a statement of present fact framed against Patricks own Amazon background: unlike Amazon, unlike Apple, unlike Google, we do not have a Japan entity right now, so there is no Japan CIQ to move you to. It is true that we have people working in Japan right now - they do not actually work for CIQ. And I would leave it at that. No more than that. He gave one reason for today - today I would not support moving an engineer to Japan because they do not work for CIQ and because the hiring policies make it prohibitively difficult - and then stopped. He accepted the cost out loud: and if we lose him, we lose him. But also, as long as he is willing to hear this is what is true today, and he is willing to sign on to it, I am happy backing it. Nathan and Brie agreed to have the conversation before writing the offer, with the US number known internally but not presented.
Pass on Patrick Culp for now (no black mark), re-engage in 3-6 months
In the Round Table hiring debrief for candidates Ben Howard and Patrick Culp, Peter decided to pass on Patrick Culp for now - explicitly not a hard rejection - with intent to re-engage him in three to six months. Stated reason: he wants breadth of past experience coming into Nathan org right now. Peter committed to co-drafting the decline and re-engage message with Bree Clasen.
Intent to move Ascender to Zorina with dedicated headcount; stays under Justin for now
Peter decided the direction for Ascender (and Ascender Pro; Ledger Pro pending a Bjorn confirmation): move it under Zorina as a clean, dedicated product home, with headcount Peter has secured for Zorina to hire a team (Bay-Area-first, lightly). For now Ascender remains under Justin — NOT Nathan — and the move to Zorina is directional intent, not yet executed. Larry and Jimmy (original engineers) move to sales-support under Bjorn. Intent is to productize Ascender like any other shippable product rather than leave it an orphan.
Ascender Pro Dev JD scope finalized — application engineer to de-risk Jimmy, pulls Ascender dev into Peter org
Joint Peter/Bjorn/Jimmy/Brianne meeting 5/14: title is application engineer (intentionally NOT Ascender-engineer — allows cross-project use), $180k mid-senior, 6-8 years experience, React + Python primary (50/50 front-end/back-end), Go a plus, go-getter required (must keep pace with Larry and Jimmy who are both super-fast). Interview panel: Brianne, Jimmy, Larry, Chris Wolford. Peter optional final (Bjorn pushed Peter onto panel: I trust Peter's interviewing). Brianne posts JD by weekend / Monday. Will report into Peter's org, location-within-org TBD. Bjorn's framing: pull all Ascender development under [Peter's org] form.
Open Ascender hiring req — start the process now, hire after close
Peter approved opening the Ascender engineer requisition and running the recruiting process immediately, while noting actual hiring against the req cannot happen until the role formally closes. Operational handoff to Nathan to drive.
Andrew Jorgensen Level Flexibility Confirmed
Clarified with Brianne that Andrew does not need to come in as Maxs peer. Happy to slot him into either the more senior or less senior position based on his comfort. Want him coming in feeling happy and excited about what hes signing up for.
Andrew Jorgensen Hiring Approved
Approved hiring Andrew Jorgensen for an IC role reporting to Nathan Blackham. Offered flexibility on level - he can come in at senior or less senior position based on his comfort.
Related Patterns (9)
Proactive Talent Pipeline Investment
Invest in building leadership bench and talent relationships before there is an urgent need. Use proven relationships from past experience to create optionality.
Accountability Follow-Through
When you issue a warning or mandate with stated consequences, you follow through. Warnings are not threats - they are commitments. The credibility of future accountability depends on following through now.
Executive Sponsorship for Strategic Partnerships
Strategic cross-company initiatives and major client partnerships require executive-level accountability to move at the right pace and ensure proper prioritization.
Small Circle for Sensitive Operations
When executing sensitive strategic operations, keep the circle of informed people as small as possible to prevent leaks that could accelerate hostile action or undermine the initiative.
Protect Engineering Capacity
When external demands threaten to overload engineering capacity, protect capacity by either requiring the demand to come with additional resources, or forcing hard prioritization choices upstream.
Three-Lever Talent Management
When pursuing a velocity or performance mandate, simultaneously operate on all three talent levers — upgrade (hire better), retain (protect key people), and exit (remove blockers) — rather than sequentially. This creates compounding momentum: exits free capacity for upgrades, retention preserves institutional knowledge during transitions, and upgrades raise the performance bar that justifies further exits.
Reclassify to Route - Decide Who Owns It, Then Give a Criterion Not a Verdict
When a question arrives at Peter framed in one domain, he often does not answer it in that framing. He reclassifies it into the domain that actually governs the outcome, which relocates ownership to whoever owns that lane, and then hands down a decision criterion rather than a verdict. The reclassification IS the decision - it determines who decides. He does this rather than adjudicating on the merits himself, even when he was explicitly cc-ed and even when a direct report challenges him on the substance.
Decide on the Precedent, Not the Case
When a request arrives framed as a one-off, Peter does not evaluate the one-off. He evaluates the rule that granting it would write, and answers that instead. Peter generalized this himself on 2026-08-11: it is always about understanding precedent - whether it is a comp change or anything that structurally affects the company. It is therefore NOT a compensation pattern; the domain of the presenting request is incidental. The tell that this pattern is live is that the stated reason for the answer refers to future cases rather than to the merits of the present one.
Redesign Conditions Over Policing Symptoms
When a direct report names a vulnerability and proposes surveillance-style verification mechanisms (breathalyzers, daily check-ins, monitoring rituals), Peter accepts the disclosure but pushes back on the surveillance model. Treats the verification proposal as a signal that the underlying environment needs redesign — and offers to change the conditions that produced the vulnerability rather than instrument the symptom. Costs Peter optionality (e.g., committing to broker work-hour expectations directly with the partner/spouse) — the asymmetry signals genuine retention vs transactional.