Senior Engineering Manager – Service Transformation & Platform Capabilities

Join ABC Fitness and become part of a culture that’s as ambitious as it is authentic.

Let’s transform the future of fitness—together!

Our Values Best Life We believe great work begins with great people.

That’s why our culture is built on respect, trust, and belonging.

We create an inclusive environment where every team member can bring their authentic self to work—because diverse perspectives drive innovation and meaningful impact.

Growth Mindset We are doers, thinkers, and dreamers.

At ABC Fitness, your growth is our investment.

Through continuous learning, mentorship, and professional development opportunities, we empower you to reach new heights—personally and professionally.

One Team From day one, you’ll be part of a team that collaborates, celebrates, and cares.

We move fast, support one another, and have fun along the way.

Because when you thrive, we all thrive. 

 What You'll Do Lead the service transformation teams Build and manage small, high-ownership squads responsible for converging duplicated product capabilities into shared, domain-oriented services.

Own the delivery cadence, quality, and predictability of a multi-year transformation executed in steady quarterly increments with clear boundaries, owners, and cutover plans.

Turn architecture into shipped services Partner with principal engineers and staff engineers to translate target architecture, service boundaries, migration seams, and compatibility strategies into sequenced, executable plans your teams can implement safely.

Your job is to make the architecture real: prioritized, staffed, de-risked, and delivered.

Establish the base service tier Drive the standards for how shared services are designed, contracted, versioned, documented, and consumed, so that every ABC application — and the AI agents and partners building on top of them — can rely on one consistent capability layer.

Ensure services are designed for both human and machine consumption from day one, with structured contracts that agents can use reliably.

Protect compatibility and business continuity Convergence only counts if customers never feel it.

Lead teams through incremental strangler-style migrations, staged cutovers, dual-running periods, and post-cutover hypercare.

Existing behavior, reporting, and integrations keep working until each consumer has safely moved.

Modernize the application foundations Guide the movement of business logic out of legacy, database-centric implementations into testable, cloud-native services on our target stack.

Retire duplicated builds, legacy dependencies, and aging infrastructure as consumers cut over.

Raise the bar for engineering quality Build quality in as a system, not a stage.

Establish a software-factory approach where every change moves through automated validation loops — layered validators for scope, contracts, parity, runtime behavior, and user experience — that produce evidence of correctness rather than claims of completion.

Design the pipeline so that failures are detected, diagnosed, and corrected in-loop before work integrates, and so that each converged service ships with a durable, inspectable evidence trail.

The goal is simple: ship quality software, quickly.

Drive AI-native ways of working Enable your engineers to use AI across code comprehension, design exploration, implementation, migration analysis, test generation, and documentation.

Turn promising individual uses into repeatable team practices, so a small squad can credibly take on a portfolio-scale transformation.

Make AI the way your team works: engineers direct agents across code comprehension, design exploration, implementation, migration analysis, test generation, and documentation, and the factory's validation gates — not manual inspection — prove every change correct.

Turn what works into repeatable factory practices, so a small squad can credibly take on a portfolio-scale transformation.

Hire and grow strong engineers Recruit, coach, and develop engineers who are comfortable working across legacy code and modern service design.

Set clear expectations, give honest feedback, and build a culture of ownership, craft, and follow-through.

Partner across the program Work closely with product, program leadership, principal engineering, SRE, security, and data teams to sequence domains by customer impact and technical dependency, surface risk early, and keep cross-team commitments visible and managed.

What This Is Not This is not an architecture-only or people-only role.

You are expected to engage credibly with design and delivery detail, challenge weak technical assumptions, and be accountable for outcomes — while your engineers own the code.

This is not a greenfield platform build.

The value of this work is measured by safely converging live, revenue-critical systems onto shared services, not by producing new frameworks.

Decisions must balance long-term platform quality with migration safety, business value, and the realities of changing production applications.

This is not a big-bang rebuild or a customer migration program.

The transformation is evolutionary: systems stay releasable throughout, and customers experience better capabilities, not disruptive migration events.

What You Bring Proven engineering leadership Substantial experience leading backend or platform teams delivering complex, high-throughput production systems, with direct accountability for delivery, quality, and team health.

Service transformation depth Experience decomposing monoliths, extracting services, and defining domain boundaries, ownership models, and migration strategies within complex existing environments — and delivering those migrations to production.

Credible backend and distributed-systems fluency Enough hands-on depth — in Java and Spring or comparable enterprise backend ecosystems — to review designs, ask the hard questions, spot risk in implementation plans, and unblock your teams.

You don't need to write the code, but you need to earn the room.

Migrat