Head of Product, Systems

About the Role We believe most product organizations are built and managed to chase the wrong signals (confidence in delivery timelines 12+ months away, internal consensus, user engagement vanity metrics, etc.). We use Directed Discovery, which is a human-centered, evidence-driven product methodology that prioritizes managing product-market-fit above everything else. As Head of Product, Systems , this means you will be building and managing a product team and culture which focuses on ensuring our products and user experiences consistently produce these outcomes: Choosers quickly and easily recognize Torus’ value and purchase our products (likelihood to buy) Users feel like our product experiences are simultaneously powerful and simple (customer happiness) Repeat purchases/expansion of our product (length of stay) And most importantly, we need to produce these outcomes especially when product-market conditions change. This means you’ll partner as a peer to the Heads of Software, Embedded Systems, Data, and Testing Tools & Frameworks to ensure that our technology systems are successfully balancing “Speed and Quality Equally.” How We Build Building with Directed Discovery means a lot of things, but if you don’t deeply resonate with the below, you will not be a fit. Product leaders as critical Sales collaborators. Our products exist in a highly sophisticated ecosystem of building owners, utility operators, and regulatory environments. Managing product-market fit means finding the intersection between choosers’ likelihood to buy and users’ happiness as they interact with our products. We believe the only way to great clear chooser signals is being a powerful collaborator in the Sales process. This looks like delivering truly exceptional product demos and supporting the Sales team in overcoming buyer objections as deals are closing. Your own proposals get preference-tested like everything else. Expect evidence to kill some of your ideas. If that sentence reads as relief, keep going. If you would rather run a roadmap on conviction and consensus, this will be a frustrating place to work. Work is routed, not “roadmapped”. Net-new work runs the full sequence; additions to existing experiences run lighter; operational work lighter still - and rigor scales with reversibility. Software iterates after release. Hardware must be right before tooling and certification. Speed and quality, equally, by design. You must be able to match the level of rigor and framework to the moment of time and need. Evidence breaks ties. The user breaks the tie on experience. The purchase order breaks the tie on viability. The instrument breaks the tie on performance. The whole team does discovery. Our engineers help build discussion guides, moderate interviews, and sit in preference tests. You will teach this craft, not gatekeep it. No sprints. Single-piece flow, mile markers, and an org we redesign as we learn. Leaders serve teams from the bottom of the structure; teams own implementation. Who You Are A relator: people feel heard by you before they feel directed by you. You seek context with intention, and you co-create rather than dictate. Deal-credible: you can defend payback economics to a CFO in the morning and observe a facilities operator using the product in the afternoon without leading the witness. You have closed or rescued revenue, and you can name exactly what changed in the product because of it. Falsifiable: you keep score on yourself. You can tell stories about public positions you held that evidence reversed — and you tell them with something close to relish. A strategist with strong tactical intuition: you own our product strategies, and ensure they are aligned with our company mission, vision, and strategy, but at the same time you instinctively build those strategies within our delivery constraints and challenges. An instrument builder: you design the systems that make decisions obvious rather than argued — #J-18808-Ljbffr Socket.dev