Skip to jobs
Unlisted
All jobs

Wagmo · Engineering

Principal Engineer

Where
New York (Preferred) or RemoteRemote · one country only
Experience
8+ yrsguessed from the title
Pay
$200K–$250Kbase, as stated on the posting
Posted
Already listed when Unlisted started watching this board (6 Oct 2026)
Apply on AshbyOpens the employer's own posting

Checking Ashby for this posting…

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

What You’ll Need To Be Successful

Why Consider This Role?

Key Benefits