Building a Personal + Confidential Operating System

Senior operators who work on high-stakes problems where every detail counts. Chiefs of staff, founding team members, heads of product, strategic advisors, account executives and sales engineers — anyone on a small team where the interpersonal dynamics are the strategy.

You already do this work in your head. You already have mental models of who responds to what, who needs to be moved first before the group will follow, which channel someone is brave in versus which one they hedge in. You already know that meetings are processing sessions, not decision sessions… and that the real move happens in the DM 48 hours later.

You want outsized influence in your IC role to:

• Ship a product feature
• Prevent a feature from being built or shipped
• Fundamentally change GTM strategy/tactics (ex: POV length, which part of the sales cycle is worth focusing on, investments to prevent churn)
• Drive product marketing strategy/tactics
• Be leadership’s shadow trusted advisor (this is more common than you think, because leaders trust strong ICs in the trenches)

Operators who build and use a personal OS become captains of their domain. They enter workplace situations with a surgical plan, update their assumptions as new information arrives, and shape the world toward how they’d like it to be.

What starts as building simple, personal software extends to crafting the interpersonal dynamics you want to inhabit.

You’ll vibe code a personal OS that doesn’t just track meeting notes — it’ll track how good you are at predicting and influencing behaviors and outcomes.

Along the way you’ll learn the fundamentals of using a database (Supabase), Raycast and its SDK, git, and how to build software with Claude Code. Being able to read TypeScript is a nice-to-have, not a requirement. All the development happens through Claude Code.