Engineering Manager

Roles and responsibilities

Architecture & Design Leadership

• Lead, coach, and grow a backend engineering team: 1:1s, performance, hiring, and career growth.
• Own delivery: scope, sequencing, risk, and shipping against the roadmap.
• Unblock the team — priorities, dependencies, design decisions, and operational load.

Customers & Communication

• Communicate clearly with customers, support, product, and engineering — no jargon hiding the actual status.
• Unblock customers from a technical perspective: reproduce, triage, explain impact, and drive a fix or workaround.
• Own customer escalations: join the call, set expectations, coordinate the engineering response, and close the loop.

Technical Leadership

• Hold the bar on architecture, reviews, testing, and production readiness for backend systems.
• Make or facilitate calls across services, data stores, and messaging — without becoming the bottleneck.
• Partner with SDE-3s and tech leads on RFCs, incidents, and the technical roadmap.

Production

• Ensure the team can deploy, roll back, and debug services on GCP and DigitalOcean.
• Drive incident response and post-incident follow-through when production or a customer is hurting.

Engineering Practices

• Install simple habits: design reviews, on-call, observability, documentation.
• Use AI tools for coding, review, tests, and docs; keep accountability with the engineer who ships.

Technologies We Use

• Languages / runtime: Go, Node.js (JavaScript / TypeScript).
• Data: MongoDB, ClickHouse, Redis, Memcached.
• APIs & messaging: REST, gRPC, Kafka, Google Pub/Sub.
• Cloud & delivery: GCP, DigitalOcean, Docker, Kubernetes, Jenkins / GitHub Actions, Argo.
• Observability: Grafana.