Senior Full-Stack Engineer — CoreApps Platform (AI-native, Encore)

A builder role on the team that powers Groupon's global commerce engine.

CoreApps Platform is the foundational engineering group powering Groupon's global commerce engine — every customer interaction and every transaction, worldwide. This is a builder role: you take features from problem statement to production across backend, frontend, CI/CD, and test automation, using Claude Code as your daily leverage tool. You own the whole slice. You unblock yourself. You ship.

• →Drive features end-to-end. Backend services, frontend surfaces, CI/CD pipelines, test coverage, deploy, monitor — the whole vertical slice. No handoffs, no "that's someone else's team."
• →Ship on legacy and cutting-edge together. Modernize Java / Ruby systems into TypeScript / Node.js on Encore, while keeping services at 100K+ RPM running cleanly.
• →Operate Claude Code natively. Daily agentic workflow with MCPs, skills, hooks, evaluation patterns — AI is not a productivity add-on, it's how you collapse FE + BE + DevOps + QA into a single-engineer scope.
• →Cut through red tape. Find the path. Kill process that doesn't protect anything. Respect process that does. Escalate when you can't, ship when you can.
• →Lift your peers. Share patterns, unblock teammates, leave the codebase cleaner than you found it.

• 5+ years shipping production software, with deep production TypeScript / Node.js as your primary backend stack (NestJS / Fastify / Encore or similar, named and used).
• Full-stack range. You've owned features across backend and frontend, and you're comfortable in CI/CD pipelines, test automation, and production debugging. Specialist-only profiles (backend-only, frontend-only) will not fit this role.
• Claude Code native. Daily use with a demonstrable personal setup — MCPs, skills / agents, hooks, or equivalent automation. You can screen-share it. Autocomplete-only and Cursor-only do not qualify.
• Builder bias. Evidence of projects you drove beginning to end — scoped the problem, designed the approach, shipped it, operated it. No "I contributed to…" answers — we want what you built.
• Distributed systems fundamentals — API design, SLOs, structured observability, on-call ownership.
• High-bandwidth communication — written and verbal, across technical and non-technical audiences.

• Java or Ruby reading fluency (for navigating the source systems being migrated).
• E-commerce / marketplace scale experience.
• Encore, Temporal, or similar workflow frameworks.
• Frontend frameworks used in anger (React, Next.js).

First 30 days: operating in the team's AI workflow on day one — Claude Code setup running, first PR merged, owning a service.

First 90 days: shipped at least one end-to-end feature across the full stack, reduced a real bottleneck, demonstrably faster velocity than traditional backend-IC pace.

First 180 days: the team points to work only you could have driven at that pace — migration cutovers, FE + BE features shipped as single units, tooling peers now depend on.

Builders. Engineers who take scope from "this is a problem" to "this is in production" without waiting for permission. Fluent in Claude Code as the force multiplier that makes one engineer effective across backend, frontend, DevOps, and QA. Deep in TypeScript, comfortable anywhere in the stack, energized by cutting through noise and shipping. If you wait to be told what to do, this role will frustrate you.