Sultan
Dec 24, 2025 - Aug 13, 2026
5
Decisions
0
Active Todos
6
Patterns
Categories
Decisions (5)
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.
Approve a single-seat ChatGPT CVE-model trial for Sultan, narrowing Steves small-group ask to one named person
In the 7/23 Steve Wallace 1:1 Steve relayed Sultans request to trial a ChatGPT model he believes will help with CVEs and may outperform Anthropics tooling against them. Steve recommended approval on a small basis and flagged the exposure himself - AI spend is running 60 to 80 thousand a month, and opening the floodgates likely means people run tools in parallel rather than switching, compounding cost. Peter narrowed the grant to exactly one seat: I am happy to have one person test it out, I would not open it up to the entire company, giving it to Sultan is fine, totally fine. Moody will handle the program application and setup.
OPA precedent — three-in-a-row water-carrier tap, not single-event hero pay
In 5/14 Nathan 1:1, with Nathan in middle of CVE response (third consecutive: dirty frag → copy-fail → current embargo), Peter declined to set the precedent of OPA/bonus payouts for single-event heroics. Maple — who carried water across all three events via consistent handoffs and status updates — is THE OPA candidate. David (took over secure-boot kernel build during Tate's absence) is growing into the role you'd want him to grow into normally → no OPA. Sultan (great dirty-frag work, up-late nights) → no OPA this round despite the effort. Nathan retained decision authority (Peter: I'm going to support whatever you decide. But, be cautious.) but the framework was set explicitly.
Proactive Retention Check-ins After Ian's Departure
Initiated proactive 1:1 check-ins with key staff to gauge morale and prevent surprise resignations after Ian's departure. In the Sultan check-in, clarified Michael Young's departure was performance-based, explained no company-wide announcement (no teachable moment), and affirmed Sultan's role is safe. Goal: replace underperformers with A players.
Bonus Criteria - Strategic Alignment Required
Established bonus criteria: bonuses should be for accomplishments aligned with strategic goals that help scale or deliver faster, not just for being an awesome developer.
Related Patterns (6)
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.
Lead by Example with New Tools
When championing new tools or processes, personally use them and share results rather than just advocating. Learning by doing and demonstrating value through example is more effective than mandates.
Protect Engineering Focus Through Process
When faced with requests that would disrupt engineering focus (from sales, governance, product, or other stakeholders), establish processes that protect engineering ability to innovate while still satisfying legitimate concerns. Prefer systematic solutions over ad-hoc responses.
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.
Strategic Alignment for Rewards
Compensation and bonuses should reward outcomes aligned with company strategy, not just individual talent or performance in isolation.