Software Engineer - Frontend

About FACEIT

As one of the core pillars of EFG, FACEIT is the beating heart of competitive online gaming. With over 34 million registered users playing 30 million matches each month, we are the industry leader in competitive play. Our platform is where gamers of all levels come together to test their skills, climb the ranks, and forge communities.

At FACEIT, we’re relentless in our pursuit of excellence. We push the limits of technology, deliver cutting-edge features, and provide an unparalleled competitive gaming experience. Our vision is simple: to empower every player to reach their full potential, while keeping competition fair, engaging, and thrilling.

The Problem You Will Solve

Every month, millions of players decide whether FACEIT is worth paying for — and your code is where that decision happens.

Subscriptions is the primary revenue engine behind the FACEIT platform. It's a Stripe- and Xsolla-powered checkout, a Subscriber Portal managing the full lifecycle (upgrade, pause, resume, cancel, gift), and a Loyalty programme where tiers, streaks, XP and payment-anchored benefits turn one-off buyers into long-term members. It's a surface where a 1% conversion lift is measurable in weeks, a race condition costs real money, and complex financial state has to feel obvious at 2 a.m. on a phone, mid-queue.

We're looking for a Frontend Engineer who wants to be the person writing that code. You'll work in a modern stack — React 19, Next.js 16, TypeScript, TanStack Query, an in-house design system, Storybook + Chromatic + MSW — inside a monorepo of ~14 Subscription-owned packages. You'll ship alongside Product, Design and Backend, on features and experiments that move numbers the whole company watches.

The Team

You'll ship alongside a senior Frontend Engineer — your closest technical partner — plus two Backend Engineers, a Product Designer, a Product Manager and an Engineering Manager. Product and Design own the flows; you and the senior FE own how they land in production.

What You'll Own

• The paid conversion path, end-to-end.  Conversion points across the app, the plan landing page, Stripe & Xsolla checkout (including gifting and upgrades), and the immediate post-purchase experience — you'll own the code, the experiments, and the conversion numbers they produce;
• The subscriber lifecycle. Pause, resume, cancel, renewal and the Subscriber Portal — where retention is won or lost. You'll build the flows that reduce voluntary churn without dark patterns and recover involuntary churn cleanly;
• The Loyalty programme UI. Tiers, streaks, XP, payment-anchored benefits, shop token allocation, badges. You'll turn our Loyalty service into an experience players actually understand, care about, and come back for;
• Experimentation velocity. Feature-flagged rollouts, A/B tests on pricing, bundling, activation and cancel-flow interventions, wired to analytics with the rigour to trust the results;
• The technical health of a revenue-critical surface. Testing culture (Vitest + Storybook + Chromatic + MSW), observability, and the safe-rollout discipline that lets us ship confidently to code that processes real transactions every minute.

What We Are Looking For

• Solid production experience with React 19, TypeScript, and Next.js (App Router);
• Fluent with modern data-layer patterns — TanStack Query (or equivalent) and Redux Toolkit — and a clear point of view on when to reach for each;
• Comfortable in a large monorepo: package boundaries, dependency hygiene, incremental migrations, working across many consumers of your code;
• Track record of owning a high-traffic, business-critical surface — checkout, billing, payments or another revenue/retention path — and understanding the operational demands (idempotency, error recovery, race conditions, safe rollout, observability, and the uptime discipline that treats every minute of downtime as lost revenue);
• Strong eye for details of complex state in production: proration, entitlements, expirations, currency and tax, localisation, accessibility. You know the common pitfalls and handle them in code, not in post-mortems;
• Familiarity with experimentation tooling and mechanics: feature flags, segmentation, A/B tracking, and the instrumentation that makes results trustworthy;
• Solid on testing culture — unit, component and visual regression. You don't ship revenue code without a safety net;
• Collaborative by default: fluent code review, clear writing, low-ego debates, comfortable partnering with Product, Design and Backend as equals;
• Fluent with modern AI coding tools (Copilot, Cursor, Claude Code or similar) as part of your daily practice — and clear-eyed about when to lean on them and when not to, especially on revenue-critical code.

Bonus skills

• Passionate about learning new, cutting-edge technologies and finding applicable business cases as needed;
• A passion for video games and esports is a plus.