About the role
About the role
This is a hands-on backend role on a small team. You’ll be working on the parts of the system that
need to stay stable as usage grows, enterprise customers come on board, and deployments get more
demanding.
We’re looking for someone who has done more than ship backend features. You should be
comfortable owning systems in production, thinking through failure modes, and making practical
tradeoffs around reliability, speed, and cost.
What you’ll do
● Build and improve backend systems that are reliable, easy to maintain, and ready to scale.
● Own cloud infrastructure and deployments across AWS, including the tradeoffs that come
with them.
● Set up and improve observability, so we catch issues early and understand what’s happening
in production.
● Strengthen testing and CI/CD so we can move quickly without breaking things.
● Improve database performance, data flows, and system behavior under load.
● Work on background jobs, queues, retries, and the kinds of operational details that matter in
real systems.
● Help us prepare for stronger security and compliance requirements as we grow.
● Support on-premise deployment needs for enterprise customers.
What we’re looking for
● Roughly 3–4 years of backend experience working on production systems.
● Real infrastructure experience in AWS or another cloud environment.
● Strong Python backend skills and good judgment about writing clean, maintainable code.
● Comfort with distributed systems, containers, queues, and the practical side of scaling
software.
● A strong production mindset — you naturally think about monitoring, failure cases, reliability,
and cost.
● Ownership — if something needs fixing, you lean in and fix it.
Skills that will be useful
● Scaling applications across services and infrastructure
● PostgreSQL tuning, query optimization, and connection management
● Queues, Redis, Celery, pub/sub systems, and API design
● Authentication, networking, private infrastructure, and security basics
● Unit, integration, and API testing
● Monitoring, logging, alerting, and debugging in production
● CI/CD with tools like GitHub Actions, CodePipeline, or CodeDeploy
This may not be the right fit if
● You only want to work on greenfield builds and not on improving real production systems.
● You’re not comfortable owning uptime or responding when things go wrong.
● You need everything to be perfectly planned before getting started.
● You prefer staying strictly inside a narrow role boundary.
Tech stack
● Python (FastAPI)
● PostgreSQL
● Celery
● AWS (RDS, EC2, Lambda, CloudWatch, CodePipeline)
● Docker, Redis, Sentry, Supabase, GitHub Actions, Next.js
This page is fully interactive when JavaScript is enabled. Please enable JavaScript to apply or browse related roles.
_1548133325694.png){kind=logo}
