About the Company

They run one of the leading ticketing platforms in Latin America, with around 1 million users across Argentina, Chile, and Peru. The engineering team is small by design — 7 people — and the backend is a real production system: NestJS/TypeScript on GCP, MongoDB Atlas at scale, native mobile apps on iOS and Android.

The Role

They're looking for a Senior Backend Engineer to work on a system that already has real discipline: trunk-based development, auto-deploy to staging, DDD in progress, Atlas tuned for production traffic. You won't be managing anyone — you'll be writing code, making technical contributions that matter, and working closely with a small team that takes engineering seriously.

What you'll do

• Build and evolve backend features across the stack — from domain logic to infrastructure

• Contribute to the ongoing DDD migration: bounded contexts, repository pattern, domain/application/infrastructure layering

• Work with MongoDB at production scale: aggregation pipelines, index strategy, Atlas tuning at M50 level

• Participate in code reviews and technical discussions with a team that debates decisions openly

• Collaborate on API contracts with the iOS and Android teams

• Contribute to incident response in production: MongoDB, Cloud Run, cronjobs

• Help keep CI/CD, infra hygiene, and QA discipline running and improving

What we're looking for

• 5+ years in backend with Node.js, ideally 3+ years with NestJS in production

• Advanced TypeScript: decorators, generics, complex types

• Professional-level MongoDB: aggregation pipelines, compound indexes, $lookup, $project, hint, read preferences, real performance tuning on Atlas — not just "I've used Mongo"

• Experience with systems at relevant scale (100k+ MAU) with demand spikes — launches, live events

• Hands-on tactical DDD: bounded contexts, repositories, value objects, layered architecture — applied in a real team, not just read about it

• GCP in production (Cloud Run, IAM, Secret Manager, VPC) or solid equivalent in AWS/Azure

• CI/CD with GitHub Actions or similar

• Comfortable with trunk-based development

Nice to have

• Redis: cache patterns, pub/sub, derived read models

• Atlas Search / Lucene: fuzzy matching, analyzers

• Event-driven architecture: GCP Pub/Sub, Kafka

• Observability: GCP Logging, Datadog, Atlas metrics

• Familiarity with mobile contracts (iOS/Android) — reading them, not writing them

• AI-assisted development: Claude Code, Cursor, Copilot

• English

How they work

• Distributed team, Argentina-based

• Async-first with occasional syncs

• A team that debates technical decisions openly and values strong opinions held loosely