O pozici
Groupon connects 42 million customers with local experiences - restaurants, events, wellness and travel - and the million-plus merchants who deliver them. Our mission is to get people offline and into the real world at prices that make it possible. We're an AI-native company in the middle of a platform transformation, moving from a deals marketplace to an experience discovery platform that works for customers and merchants at the same time.
Groupon IQ is the internal platform that powers deal creation, QA, and publishing across the company. The 7-person team can't keep up with the backend incidents IQ generates today, and downstream tribes feel every outage. When this role works, IQ stops being a recurring incident and becomes the boring backbone other tribes rely on.
Co budeš dělat
- Owning Groupon IQ's backend reliability hands-on, debugging distributed-system failures, fixing the root cause, and writing the post-mortem that prevents the next one
- Generating most of your own code through AI agents (Claude Code, Cursor, Codex, your choice) while doing the review that catches what the model doesn't see
- Setting and enforcing the code-review bar for AI-assisted output across the team, so silent timeouts and broken migrations get caught before they ship
- Driving technical direction across the shared TypeScript monorepo so a change in one app doesn't quietly break three others downstream
- Mentoring the 7 engineers reporting to you toward the ownership posture Pavel hires for: take the problem, don't wait for it to be assigned
- Partnering with the Encore team and the marketing and BI users downstream of IQ, so platform changes land predictably for everyone who depends on them
Koho hledáme
- Hands-on full-stack (preferred) or backend TypeScript depth in distributed systems. You diagnose timeouts, race conditions, and broken migrations at the source, not just patch the symptoms.
- Daily AI-assisted engineering practice. Most of your code today goes through Claude Code, Cursor, Codex, or equivalent, and you can spot the failures the model misses.
- Monorepo experience at scale (Nx, Turborepo, pnpm workspaces, or similar) where you've personally driven structural decisions about repo layout, build performance, or shared-package boundaries
- A hands-on coding role with people leadership as a secondary responsibility, already lived, not aspired to. You're the lead engineer who happens to manage a few people, not the manager who used to code.
- Ownership instinct outside the corporate norm. You've taken problems that weren't yours and finished them, because they needed finishing.
- E-commerce, marketplace, or high-traffic consumer product context where reliability translates directly to a user or business outcome you can name
Benefity
- Extreme Ownership. Nobody here waits for a ticket. The engineer who finds an incident first owns it end-to-end, regardless of which tribe shipped the original code.
- Impact Obsessed. Every technical call gets justified against the marketing or BI user it affects, not the elegance of the design. A rewrite that doesn't reduce incidents or unblock a downstream user isn't worth shipping.
- Disciplined. AI generates most of the code on this team. Discipline is what stops that velocity from becoming a stability problem: every AI-generated change earns its review like any other, and re
- We encourage candidates to leverage AI tools during the hiring process where it adds value, and we’re always keen to hear how technology improves the way you work. If you’re passionate about AI or curious to explore how it can elevate your role you’ll be right at home here.
