# Principal Engineer at Wagmo > Remote · United States · Principal · Software engineering · open. Source: https://alderhq.app/jobs/ashby%3Awagmo%3Ab98348bc-2d3e-4fff-8714-37627cd44e58 (read 2026-11-12). ## Facts (observed) - Company: [Wagmo](https://alderhq.app/companies/wagmo) - Location text: New York (Preferred) or Remote - Where it can be done from (inferred): Remote · United States (evidence: "Location: New York (Preferred) or Remote") - Posted: 2026-10-01 (42 days ago) - First seen by alder: 2026-11-07 · last verified: 2026-11-07 - Reposted: 0 times · edited: 0 times - Apply on the employer's site: https://jobs.ashbyhq.com/wagmo/b98348bc-2d3e-4fff-8714-37627cd44e58 - Skills listed (inferred): TypeScript, JavaScript, React, Next.js, Node.js, Python, Django, React Native, Flutter, Kubernetes ## Pay and sponsorship - Posted pay: $200k–$250k per year (from the listing's pay field) - Market band for similar posted roles (New York, n 36): p25 $219k, median $247k, p75 $275k ## Description (the employer's text) ### What We Do Wagmo is a modern pet healthcare company built around how pet parents actually care for their pets. We partner with employers to provide a complete approach to pet and pet-parent wellbeing, from preventive wellness plans and emergency coverage to 24/7 pet telehealth guidance. Our purpose is to unlock every pet parent's potential to provide extraordinary care, and we do it by bringing the same intentionality to pet benefits that the best employers bring to human healthcare. Founded in 2017 and female-founded, Wagmo is headquartered in New York City and trusted by leading employers nationwide. ### What’s Important To Us Our mission shapes everything we build and how we work together. We take fearless ownership of outcomes, collaborate with radical candor, and are always driven by the customers and pet parents who trust us. We think critically, follow through relentlessly, and find the extra 10% that turns good work into exceptional work. We keep it weird because the obvious answer is rarely the most interesting one. Our values aren't aspirational. We interview for them and hold each other accountable to them. If what you've read so far resonates with you and you want to be part of a team where every person makes the company meaningfully better, we'd love to hear from you.. ### About The Role As Principal Engineer at Wagmo, you will be the named owner of our application architecture. Wagmo sells pet wellness and insurance directly to consumers and through employers, brokers, and benefits administrators. Over the past two years we moved our insurance program to a new carrier partner and built a provider-agnostic interface to make that possible. It works, and it is not finished: two generations of models still coexist behind feature flags, and the legacy path has to be supported for years. On the partner side, each new benefits administrator we onboard currently arrives as its own build, with its own file format, renewal cadence, and eligibility rules. Our growth depends on that stopping. Architecture has been owned by the CTO to date. This role takes it over. You will set technical direction across insurance, claims, partner integration, and our AI systems, decide what we will not build, and leave designs that two squads can execute without escalating. You will do this with no direct reports, real influence, and your hands in the codebase. The scope here is wide for our team, which is the appeal and also the challenge. There is no platform organization beneath you and no architecture review process to inherit beyond the one we started this year. Our Tech Stack: React · Python · TypeScript · React Native · Kubernetes · Django · Next.js · Node.js · Flutter (legacy) · builder.io · GitHub · Slack · Notion · Claude ### Core Responsibilities Own the end state of Wagmo's insurance provider interface, including a documented retirement path for legacy provider models and the decision about when dual-write paths come out. Design partner and carrier onboarding so that adding a new benefits administrator is a configuration exercise rather than an application build. File format, renewal cadence, group structure, and product eligibility should be configured, not coded. Own architecture review: run it, hold decision rights in it, and maintain a decision log that the team can rely on. Success is squads unblocked without escalation. Define a single identity architecture spanning enterprise SSO tenants, our partner portal, and consumer authentication, with per-tenant onboarding reduced to a documented, repeatable process that stands up to enterprise security diligence. Own the architecture of our AI systems across claims adjudication, customer support, and internal engineering tooling: versioned prompts and strategies with a promotion path, controls that match their documentation, and a measured cost per automated decision. Mentor squad tech leads and raise the standard of technical design across the team, without taking on people management. ### What You’ll Need To Be Successful --- Data: alder (https://alderhq.app). Cite https://alderhq.app/jobs/ashby%3Awagmo%3Ab98348bc-2d3e-4fff-8714-37627cd44e58 and the date you read it. Observed facts come from the employer's own listing; location reach, level, family and skills are inferences.