Senior Backend Engineer (LATAM)

You'd be writing code in our Django backend, which powers both the consumer dashboard and the B2B platform. Expect a mix of:

• New features for the APIs that power our consumer dashboard and customer reporting
• Performance and reliability work in our Celery and RabbitMQ pipelines
• Integrations with third-party services like payment providers and identity providers (Stripe, WorkOS SSO)
• Code review, both giving and receiving, on a small backend team of other Senior Engineers

We don't have a rigid roadmap of "first 30 days, first 60 days" because that's never how it actually plays out. You'd pick up real work in your first week.

• 10+ years building production web applications
• 6+ years with Python and Django
• Working knowledge of CS fundamentals: data structures, concurrency, SQL, system design
• Strong written communication; comfortable working async across time zones
• Self-direction and follow-through

Strong plus

• DRF and/or django-ninja
• Celery, RabbitMQ, Redis in production
• Postgres tuning and query analysis
• Kubernetes and AWS
• Stripe, identity providers, or other third-party API integrations
• HTMX, React, or both
• Background in consumer privacy or adjacent industries

We expect engineers here to use AI coding assistants like Claude Code as part of normal day-to-day work. If you've spent time figuring out how to actually get value out of these tools, that's a real plus.

This role is open to candidates based in Latin America. We strongly prefer working hours that overlap with US Eastern, Central, Mountain, or Pacific time zones, because we do a fair amount of real-time collaboration.

• $78K - $114K
• Paid time off policy

Two things matter more than any specific skill.

• The first is ownership. If your feature ships and breaks in production, you're the one who investigates. If a spec is ambiguous, you ask. If you see something off in a teammate's PR, you flag it instead of waiting for someone else to.
• The second is writing. Async-first work means most of our coordination happens in PR descriptions, Slack threads, and Jira tickets. We care about people who can write clearly, and who also know when it's time to give up on writing and just hop on a 15-minute call.