Location
Remote - Global
Job Type
full-time
Work Format
🌍 Remote LATAM
Salary
$137K – $170K
Posted
November 17, 2026

Job Description

We have been using a disciplined approach to compensation since the start.

We believe this is the only way to create a consistent, strategic, and equitable compensation structure. That in turn unlocks healthy growth for our organization.

We build our range with benchmarking data for the particular role from Pave.com - because Pave hooks into HRIS, they have the most accurate data for early-stage companies.

We decide any given hire's offer based on three factors:

  1. first among them, expected performance in the role (based on performance in the interview process and proximity of experience);

  2. as well as seniority (amount of relevant experience);

  3. and location (different cost of living).

Overview Application

At Moxie, we empower ambitious aesthetic entrepreneurs to build profitable, independent practices—without burnout, overwhelm, or guesswork. In just a few years, we've grown from an idea to a global, remote-first team now supporting 700+ practices nationwide.

Our purpose is simple: to unlock sustainable success for aesthetic entrepreneurs, at every stage of their journey.

Staff Product Engineer (Frontend)

We're looking for a Staff Product Engineer to be one of Moxie's leading frontend individual contributors, driving the highest-leverage frontend initiatives across the org in Q4 2026 and Q1 2027. The center of gravity here is horizontal: how every Moxie team builds, ships, and maintains UI. You'll be a leading contributor to our Design System and the entire frontend toolchain and CI. You’ll also play a key role as we rethink and redesign our architecture, tooling, and SDLC for the agentic eraYou'll most likely sit on the Financial Operations (FinOps) team and stay hands-on in product delivery there, so your standards stay grounded in real feature work. Day to day, you'll partner with Design, Product, engineering managers of UI-heavy domains, and other staff engineers across our frontend stack ( Next.js , MUI, Apollo, GraphQL, Storybook, and more). stack of Next.js, MUI, Apollo, GraphQL codegen, and Storybook.

Our Objectives for the Role

  • Ramp through real product work. Within three months you're shipping FinOps UI improvements that raise performance, consistency, or developer experience, such as consolidating a repeatedly forked pattern (such as confirm dialogs) or perhaps refactoring un-performant queries on a slow page.

  • Shape architecture across the company. Within three months you're ramped up to Moxie's system design and architecture, and opinionated on what we can do better, and what we should build next. You're comfortable developing technical proposals, and taking them from draft to review, approval, and final implementation.

  • Own non-project technical initiatives and engineering culture. Start owning at least one org-level initiative in your first three months (for example redesigning our frontend development SDLC for the agentic era), and by month nine own one or two initiatives with measurable gains in quality or velocity, while shipping v1 of one or more key initiatives.

We're Looking For

  • Design system or frontend platform experience. You've built a design system or led a large React and GraphQL migration, including design tokens, theming, component API design, and a promotion path for canonical components, and you've seen it adopted rather than decay.

  • Data layer depth. You know GraphQL client caching and fragment colocation well enough to move a complex route to one primary query with component-owned fragments, and to make that the default pattern.

  • A record of leading adoption without formal authority. You ship in slices, pilots, and migration guides instead of big-bang rewrites, and you earn adoption through clear docs and by making the right path the easy path for teams that don't report to you.

  • Hands-on product delivery. You stay in feature work, ramp quickly in a large codebase you didn't design, and can tell canonical patterns from forks.

  • Toolchain and performance sense. You've improved CI time, type-checking, or page performance with measurable results, and you can reason about where install, caching, and build time go.

  • Fluency with AI tooling in daily work. You use AI tools in how you build and have a point of view on how AI can improve the software development lifecycle. Bonus points if you’re opinionated about harnesses, tooling (Ghosty, Herdr, Pi, Plannotator, etc), and multi-agent workflows and processes.

  • Technical leadership and influence. You partner with Design, Product, and engineering managers, communicate tradeoffs and status clearly, and level up other engineers through reviews and pairing.

This is not a role for someone who wants to work only on horizontal initiatives and step away from shipping product UI.

Why Join Us?

  • Own frontend architecture for a real, multi-domain product, while also helping shape and guide Moxie’s architecture and system design..

  • High-leverage horizontal work (design system, data architecture, tooling) while staying hands-on in product delivery.

  • Build the core that people and agents both use. You'll shape an AI-native frontend where generation in Figma and in code reuses canonical components.

  • Clear accountability at Staff level for decisions that materially affect the company, without needing Principal or org-design scope.

  • Above all, we're in this to empower small business owners to own and grow their businesses. If you succeed, Med Spas will remain the opportunity for independent owner-operators instead of being dominated by a small number of large chains. If that speaks to you, speak to us.

  • Competitive salary and a fully remote setup.

 

At Moxie, we believe in creating a workplace where everyone feels valued, trusted, and included. Our team lives by our values: act as owners, give more than we take, move with speed and care, and simplify and learn every day.

We welcome people of all backgrounds, experiences, and perspectives to apply. If you require any accommodations to fully participate in the interview process, please let us know, we’re happy to assist.

🎯 Who is this job for?

This role is suitable for a Senior/Staff-level frontend engineer with extensive experience leading React and GraphQL platforms, design systems, frontend architecture, and organization-wide technical initiatives.

The candidate should be skilled in Next.js, React, MUI, Apollo, GraphQL, code generation, Storybook, design tokens, theming, component APIs, client caching, CI optimization, performance improvement, and AI-assisted development workflows.

They should be experienced in shipping product features, modernizing large codebases incrementally, driving adoption without formal authority, writing technical proposals, collaborating cross-functionally, and mentoring engineers while remaining hands-on.

💬 Potential Interview Questions

How would you design and evolve a scalable React design system using MUI, design tokens, theming, and Storybook?

I would establish tokens for color, typography, spacing, and motion, then build accessible components with stable, composable APIs. Storybook would document usage and states, while visual regression and adoption metrics would help prevent forks and guide promotion of canonical components.

How would you migrate repeatedly forked UI patterns, such as confirmation dialogs, into a canonical component?

I would first inventory existing variants and identify the smallest API that covers real use cases. I would ship the component behind a pilot, provide migration examples and codemods where practical, then deprecate legacy versions gradually while measuring adoption and defect reduction.

How would you structure a complex Next.js route using GraphQL fragments and Apollo Client?

I would use a route-level query for the primary data boundary and colocate fragments with the components that consume each piece of data. GraphQL Code Generator would provide typed operations, while Apollo cache policies and normalized entities would keep updates predictable and avoid unnecessary refetching.

How would you diagnose and improve a slow page backed by GraphQL?

I would measure frontend rendering, network waterfalls, resolver latency, payload size, and Apollo cache behavior before changing code. Typical improvements might include consolidating requests, removing unused fields, improving fragment boundaries, paginating large collections, and using appropriate cache policies.

What strategies would you use to improve frontend CI, type-checking, and build performance?

I would profile each pipeline stage to distinguish dependency installation, code generation, linting, type-checking, tests, and bundling costs. Then I would apply dependency and build caching, incremental checks, parallelization, affected-project execution, and documented performance budgets, validating every change with measurable before-and-after results.

How would you design an effective frontend development workflow for AI-assisted or agentic engineering?

I would create a workflow with explicit plans, repository conventions, narrow task boundaries, automated validation, and human review checkpoints. Agents should use canonical components and typed APIs by default, with harnesses that run tests, linting, accessibility checks, and visual checks before changes are accepted.

How would you lead adoption of a frontend architecture change without formal authority?

I would start with a representative product problem, ship a small pilot, and demonstrate improvements in developer experience, reliability, or performance. Clear technical proposals, migration guides, office hours, and making the preferred path easier than the legacy path are more effective than requiring a large rewrite.

How would you balance staff-level platform work with hands-on delivery on the FinOps team?

I would reserve capacity for one or two high-leverage initiatives while remaining accountable for meaningful product features. Working directly in FinOps keeps architectural decisions grounded in real customer workflows, delivery constraints, and measurable product outcomes.

How would you ensure canonical frontend components are accessible, usable, and consistent with Design’s intent?

I would define accessibility requirements in the component contract, including keyboard behavior, focus management, semantics, contrast, and screen-reader support. I would collaborate with Design through shared tokens and Storybook states, then verify behavior with automated and manual testing.

How would you communicate and execute a technical proposal that changes frontend architecture across multiple teams?

I would document the problem, goals, constraints, alternatives, risks, migration stages, and success metrics, then seek feedback from engineering, Product, and Design stakeholders. After approval, I would deliver incrementally with clear ownership, status updates, reference implementations, and metrics showing whether the change achieved its intended outcome.

📋 Job Summary

Moxie is a global, remote-first company helping aesthetic entrepreneurs build profitable, independent practices, and it is seeking a Staff Product Engineer to lead high-impact frontend architecture and product delivery. You’ll ship FinOps UI improvements, shape the design system and frontend toolchain, improve performance and CI, and drive adoption of scalable patterns across teams. The stack includes Next.js, React, MUI, Apollo, GraphQL, GraphQL Code Generator, and Storybook, with daily use of AI development tools. This is a fully remote, full-time role across LATAM, offering $97K–$170K depending on location, and it’s worth applying for the chance to influence an AI-native product, lead company-wide frontend initiatives, and remain hands-on with meaningful feature work.

Required Skills

React Next.js GraphQL Storybook TypeScript Apollo Material UI

Never miss a JavaScript opportunity

Subscribe to get similar jobs and weekly insights delivered to your inbox

Hiring JavaScript developers?

Post your job to 10,400+ registered developers. Starting free.

See Pricing

Related jobs

Remote - Global

Software Engineer

Centre for Effective Altruism

Full-time

Is this your listing? Claim or request removal