Full Stack Engineer

Roles and Responsibilities

• Build features across the stack — Implement product features that span the React frontend, the GraphQL federation, the Node.js microservices, and the underlying Postgres and ClickHouse stores.
• GraphQL federation work — Add types, resolvers, and subgraph capabilities to the federated Platform API. Keep subgraph boundaries clean. Respect RBAC enforcement at the federation layer.
• Developer experience surfaces — Lift NPS through intuitive UI/UX, fast onboarding, in-browser testing, clear error states, code-snippet generation, and fast time-to-first-successful-call.
• Billing and commerce features — Ship subscription, plan, invoice, payout, and overage features that touch Stripe / PayPal webhooks, the billing state machine, and the usage ledger.
• API catalog and discovery — Improve marketplace search and the API listing experience, including the ranking signals that flow in from the analytics and search stack.
• Observability and quality — Instrument every feature you ship — logs, traces, and metrics are part of the definition of done, not a follow-up ticket. Write the alerts that page you, not someone else.
• Testing discipline — Own unit and integration tests for everything you ship; contribute to the end-to-end and contract test suites that protect the federation and the billing path. A feature without tests is not done.
• On-call and incident response — Take part in on-call rotations; investigate proxy errors, GraphQL federation timeouts, and billing webhook anomalies. You build it, you run it.
• LLM-assisted engineering — Use LLM-based coding and agentic tooling to evolve how features are shipped, reviewed, and tested.

What Success Looks Like

• Features you ship measurably improve activation, time-to-first-successful-call, and developer NPS quarter over quarter.
• The GraphQL federation surface you touch stays fast, well-typed, and intuitive for the next engineer.
• Billing, subscription, and overage flows you build are accurate, auditable, and replayable — providers and consumers trust the numbers.
• ou ship at a confident cadence — PRs land daily, deploys are routine and boring, regressions are rare.
• You leave the code, the docs, and the tests in better shape than you found them.

What You Bring

• 4–7 years of full-stack product engineering experience, with non-trivial work on production systems used by real customers.
• Strong TypeScript/Node.js; comfort writing both frontend (React) and backend services.
• Hands-on GraphQL experience — ideally federation (Apollo Federation / Mercurius / similar), schema design, subgraph composition, persisted queries, performance tuning.
• Solid SQL and comfort with MySQL or Postgres in production; bonus for ClickHouse or Redis experience.
• Familiarity with AWS (EKS, Lambda, Aurora) and containerised deployment on Kubernetes.
• Comfortable with modern observability, feature flags, and CI/CD pipelines.
• Care for developer experience — APIs you would want to consume, docs you would want to read, errors you would want to debug.
• Bonus: experience with billing/commerce systems (Stripe / PayPal), API gateways, rate-limiting, agent protocols (MCP, A2A, x402), or LLM-based developer tooling.
• You are pragmatic, ship-oriented, and comfortable in a system big enough that no one person knows all of it.