Backend Engineer

About The Role

The role builds and owns the backend services that power the company's core product — APIs, data models, and infrastructure handling real production traffic at scale. This is a hands-on engineering position where the systems designed here directly shape how millions of requests flow through the product every day.

The team operates with a high degree of ownership: engineers choose their tools, ship their own code to production, and are accountable for reliability, latency, and cost. This is not a ticket-factory — the role involves genuine architectural decisions and close collaboration with frontend and mobile engineers to design clean, durable APIs.

Key Responsibilities

Design, build, and maintain RESTful and event-driven APIs using Go, Python, or Java in a microservices architecture on AWS Own the full lifecycle of backend services — from design docs and schema design to deployment, monitoring, and on-call Model and optimize data storage across PostgreSQL, Redis, and Kafka, tuning queries and schemas for performance at scale Improve system reliability by instrumenting services with Prometheus metrics, structured logging, and distributed tracing, and driving down p99 latencies Lead incident response and postmortems for production issues; build tooling to prevent repeat failures Collaborate directly with frontend and mobile engineers to define API contracts, versioning strategies, and error-handling standards Write thorough tests, participate in code reviews, and raise the engineering bar through documentation and mentoring What We Are Looking For 3–7 years of backend software engineering experience building and operating production services at scale Deep proficiency in at least one of: Go, Python, Java, or Rust Strong SQL and data modeling skills; hands-on experience with PostgreSQL or similar relational databases Production experience with AWS (ECS/EKS, Lambda, RDS, S3) and infrastructure-as-code tooling such as Terraform Experience designing, versioning, and evolving public-facing APIs consumed by multiple client teams Bachelor's degree in Computer Science or equivalent practical experience; comfort with distributed systems fundamentals (idempotency, queuing, caching, consistency)