Backend developer

Roles and Responsibilities

• Build and operate services — Design, ship, and run Node.js/TypeScript services behind the GraphQL federation, including the analytics and quota services that front ClickHouse and Snowflake. Own a slice of the service estate end-to-end: API design, schema, persistence, tests, deployment, on-call.
• GraphQL federation subgraphs — Add types, resolvers, and capabilities to the federated Platform API. Keep subgraph boundaries clean; respect RBAC at the federation enforcement layer.
• Commerce backbone — Build the subscription, invoicing, overage, dispute, and payout flows that integrate with Stripe and PayPal webhooks and the billing state machine. Make sure metering, billing, and payouts stay accurate, auditable, and replayable.
• Proxy control plane — Build the management APIs and background workers that configure the runtime proxy: API keys, plans, rate-limit policies, quota caches, abuse signals.
• Event-driven systems — Produce and consume Kafka events safely: schema evolution, idempotency, retries, dead-letter handling. Operate streaming consumers where they are the right tool.
• Performance, scalability & on-call — Diagnose hot paths, tune queries, and own how your services scale: caching, connection pooling, back-pressure, and autoscaling for traffic spikes and agent-scale call patterns. Write the SLOs and alerts that defend them, instrument what you ship, and take the on-call rotation — you build it, you run it.
• Testing discipline — Own unit and integration tests for your services; contribute to the contract and end-to-end suites that protect the federation and the money path. The billing path gets the highest testing bar.
• Security isolation — Implement OAuth2 / JWT / mTLS where they belong; respect least-privilege; design APIs that fail closed.

What You Bring

• 5–8 years of backend engineering experience, with non-trivial work on production services that real customers depended on.
• Strong TypeScript / Node.js in a production service environment; comfort with async patterns, streams, and back-pressure.
• Solid API design — REST and GraphQL (ideally federation: Apollo Federation, Mercurius, or similar). Schema design, persisted queries, performance tuning.
• Production fluency with SQL — MySQL and/or Postgres. Bonus for Redis or ClickHouse.
• Experience with event-driven systems — Kafka or similar. You understand idempotency, exactly-once myths, and consumer lag.
• Hands-on AWS (EKS, MSK, Kinesis, DynamoDB, Lambda, DMS) and Kubernetes. Comfortable reading and writing Terraform.
• Modern engineering practice: observability, feature flags, CI/CD, and safe rollouts.
• Care for correctness on the money path — you have shipped billing, metering, or payment code before and have the scars to show for it.
• Bonus: experience with API gateways, rate limiting, quota enforcement, usage metering, agent protocols (MCP, A2A, x402), or LLM-based developer tooling.
• You write small, reviewable PRs. You add the test before you fix the bug. You would rather ship a smaller thing well than a bigger thing badly.