Principal Data Engineer

Responsibilities

• Hims & Hers is the leading health and wellness platform, on a mission to help the world feel great through the power of better health. We are redefining healthcare by putting the customer first and delivering access to care that is affordable, accessible, and personal, from diagnosis to treatment to delivery. No two people are the same, so we provide access to personalized care designed for results. By normalizing health & wellness challenges and innovating on their solutions, we’re making better health outcomes easier to achieve.
• We're hiring a Principal Data Engineer to set the technical direction for data at Hims & Hers. This is the most senior individual contributor role in Data Platform Engineering (DPE), and the scope is deliberately larger than DPE: the architecture you define determines how Software Engineering, Analytics Engineering, and Data Science build on data for millions of patients across our Telehealth, prescription, and wellness products.
• The multi-year platform architecture. Ingestion, streaming, orchestration, transformation, and serving as one system rather than five. You decide what we build, what we buy, what we deprecate, and in what order.
• What "trustworthy data" means here, and who is on the hook for it. You define the quality and freshness guarantees the platform makes, the tiering that determines which datasets get them, and the accountability model when they're missed. Staff engineers build the detection, validation, and alerting systems. You decide what we promise, to whom, and at what cost.
• The economics of the platform. The design decisions that determine what data costs us at scale (storage and compute strategy, reservation model, orchestration footprint) and the accountability framework that keeps consumption honest as more teams build on it. You set the framework. You don't tune every query.
• The written record. ADRs, design docs, and RFCs that other teams cite as the reference. If a decision only exists in your head, you haven't finished making it.
• The technical ceiling of the org. Mentorship, design review, and hands-on pairing that makes Staff and Senior engineers better. Part of how you'll measure your impact is the volume of decisions you no longer have to make yourself.
• 15+ years building and owning data platform architecture, with a record of decisions whose consequences you stayed to live with, ideally across multiple companies or multiple platform generations
• Evidence you've set technical direction for organizations you didn't manage, and got adoption through credibility rather than reporting lines
• Event streaming in production at scale, including Schema Registry, data contracts, consumer lag management, and delivery semantics along with what they actually cost. Bonus if you've personally made the analytics versus production streaming call

Languages