Senior Software Engineer

About Carrot: Carrot is the leading global fertility and family care platform, built on intelligent care orchestration: the right clinical guidance, at the right moment, in the context of each member’s life. More than a thousand multinational employers, health plans, and health systems trust Carrot to support millions of members across 195 countries – from pre-pregnancy through menopause and major life moments in between. Carrot's comprehensive clinical program delivers industry-leading cost savings for plan sponsors and award-winning experiences and improved outcomes for millions of people worldwide. Carrot is widely regarded as a defining force in healthcare innovation as a recipient of several top-tier awards, including Fast Company's 'Most Innovative Companies' and CNBC's '100 Barrier Breaking Startups'. The company is regularly cited by leading global outlets — including The Economist, Bloomberg, The Wall Street Journal, NPR, ABC News, and Harvard Business Review — as a leading voice on digital health, the future of work, and family health. Learn more at get-carrot.com . The Opportunity  🚀 We’re hiring a Senior Software Engineer who thrives in high-autonomy environments and wants to own meaningful product and platform outcomes from end to end. This is a role for engineers who enjoy operating with urgency, navigating ambiguity, and delivering production-ready solutions without waiting for perfect conditions. You’ll work closely with product, design, and engineering peers to solve complex problems that directly impact Carrot members, customers, and business performance. You’ll also help shape how our organization leverages AI-assisted development to increase speed, quality, and leverage across the engineering function. What You’ll Own 💼 Own high-stakes work as the DRI. Take hard or ill-defined problems in your domain, like a product 1-pager, a member pain point, a partner integration, and own them end-to-end. Design, build, ship, monitor, fix, iterate. Design for flexibility.  Carrot aims to be flexible to the needs of the market, our customers, and our members. Our engineering practices should reflect this. When you are breaking down a body of work or sequencing changes, you should aim to deliver value incrementally, so that each small change unlocks value for the business and users. Make the technical calls. Make speed-vs-durability tradeoffs and live with the consequences. On contested calls, you drive to a decision rather than waiting for one. Operate what you build. You're on the hook for reliability, observability, and incident response in your domain. Use AI as leverage. You have strong, specific opinions about AI tools and how they best accelerate work. You know when to trust the model and how to push back when you’re unsure. You raise the bar for how the rest of the org uses these tools. Be a rising tide. You mentor directly through your work: pairing, reviews, helping less-experienced engineers become DRIs on their own work. You also raise the level of everyone around you indirectly: through the bar you set for yourself, the standards you hold in collaboration, and the way you make hard problems look tractable. Drive measurable outcomes. Every initiative ties back to a member metric, a cost line, a reliability target, or a revenue lever. You can articulate why what you're building matters and what success looks like before you start, and you push back when an initiative can't answer that question. How Engineering works at Carrot  Carrot's engineering org is oriented around a few simple ideas: AI has changed what a small team can ship.   Have a bias for action. Own your outcomes. What used to take a team of engineers a quarter can now be done by a smaller group of engineers in a week or two, if those engineers know how to wield the tools and make decisions based on product context. We are organized around that reality not as an experiment, but as the operating mode. Concretely, that means: Small pods, clear DRIs. We operate in small, focused pods. On any given initiative, one PM or engineer is the directly responsible individual. This person owns the outcome, drives the decisions, and is accountable when it ships and when it breaks. As a senior engineer, you'll be a DRI where appropriate, and when not, you’ll be expected to hold product and others accountable to their responsibilities, including bringing the right context, not blocking progress, and ensuring outcomes are achieved. Push the pace. You are expected to set the tempo, not match it. If a review is sitting, you nudge it. If a decision is stalled, you force it. If the team is moving slower than the problem demands, you name it and figure out why. Protect focus. Disciplined focus is an asset. When something interrupts you or your pod, be it a flaky alert, a recurring question from another team, a manual step that lives in someone's head, a Slack ping that should have been a doc, you fix it at the source so it stops happening.  AI is in the critical path. We are not "exploring" AI tooling. Agentic workflows are the default. You are building leverage with these tools week over week. Accountable to outcomes. "Done" is measured in production behavior, member impact, and ultimately business results. We trust engineers to make local decisions, and we hold them accountable for the results. About You ✨ This is the disposition we're hiring for, and this is the part that determines whether you'll enjoy yourself and thrive. High agency. You are undeterred by imperfect conditions. Missing context, ambiguous ownership, and half-built tooling. Here, you get real autonomy to go fast and make progress, and the rest of the org is held accountable for not being a blocker. Optimize for delivery. Perfect isn't the target. Good enough, shipped, and ready to iterate is the stance. We hold quality in line with speed, because without both, we will not go far. We don't wait for ce