Platform Engineer

Finds the Right Path Different teams often have legitimate but competing needs. You help teams make decisions that hold up as Yuzu grows. Sometimes the right answer is to help one team solve an immediate problem; other times it is to step back and build a shared solution. You can gather input from the right people, make tradeoffs visible, and take responsibility for setting a direction where there is no existing playbook. When you establish a standard, you make it easy to follow without creating friction. Multiplies Other Engineers Platform should give other engineering teams more leverage. You care about safe defaults, clear interfaces and documentation, and meaningful observability. You create simple, understandable systems that other engineering teams can extend. Builds Practical Systems You start from a real bottleneck, build the smallest useful solution, and use evidence to improve it. You avoid both one-off work and premature abstraction., Curious > Experienced Many parts of Yuzu are a niche within a niche (e.g., Cash Pay ). We don’t expect prior experience in our industry or tech stack, and you do not need to have worked on a platform team before. We do care that you are excited to learn about unfamiliar systems, can identify opportunities for impact, and share what you learn with others. AI-Native You use AI to accelerate your own work and are excited to help us discover what high-leverage software engineering looks like today. You care about maintaining consistency and quality as AI increases the pace of change, and you are excited to build CI systems that keep up. Self-Directed We are a small team and we don’t have a dedicated PM. You can comfortably find problems on your own, investigate and solve them, and deliver without persistent external direction. You judge when something should be soloed, escalated, collaborated on, or delegated to a more appropriate owner. Example Projects Make High-Quality, Prod-Like Data Accessible How can engineers debug issues in production without accessing PHI? You might work on systems to scrub, synthesize, restore, and develop with that data, finding the right balance of speed and fidelity. Authentication/Authorization Yuzu’s is a flexible platform that plan designers use to build highly-customizable health plans. It takes a village to administer a health plan, so how do we make sure everyone gets exactly the right level of permissions? How do you enforce access controls across complex entity relationships, ensure privacy and audit-ability, and let users self-service team permissions, all while guaranteeing excellent performance for checks that are performed on literally every request? Unify Public API Each product team owns only a subset of external-facing API endpoints. How do we guarantee a consistent experience for customers and a consistent development experience for engineers? Brownie Points You’ve been on-call or otherwise responsible for a significant system in production. You’ve scaled a system from small to large and lived to tell the tale. You’ve worked on systems with meaningful reliability, security, privacy, payments, or compliance requirements. You’ve worked at a large organization with cross-team coordination challenges. You’ve worked at startup where the engineering team grew far beyond the founders. Our Commitment to You You will have significant ownership. Both equity and autonomy. We will invest in your learning and forgive your mistakes along the way. We will trust you and tell you everything you want to know about the business.

Compensation $160k to $240k annual salary, plus a meaningful equity component commensurate with the level of role at a Series A company in NY/SF. Process If we interview you, you can expect the following process Initial 30 minute conversation A take-home assignment designed to be similar to on-the-job work A 45 minute fit interview An onsite super-day We may speak with 1-2 references you provide #J-18808-Ljbffr