Backend Engineer (Platform, Stacks)

Role overview

Backend Engineer focused on Grafana Cloud platform operations and lifecycle reliability. You’ll build and improve backend systems for reconciliation/desire-state management that support business operations like billing, provisioning, and the user portal.

Key missions

• Design, develop, and operate reconciliation systems (including a backend SSS) to track the desired state of the stack.
• Collaborate with SSS, grafana.com, and deployment configurations to keep stack lifecycle workflows reliable.
• Improve operational efficiency by reducing deployment complexity and contributing to stack configuration reconciliation.

Responsibilities

• Build production-grade, correct, scalable backend systems with strong operational clarity.
• Translate ambiguous lifecycle requirements into explicit, modular solutions.
• Break complex problems into safe, iterative increments and communicate technical tradeoffs.
• Write clean, well-tested software that others can operate and maintain.
• Contribute from brainstorming through delivery and customer shipping.
• Participate in blameless incident response and post-incident reviews.

Requirements

• Professional experience with Golang; comfortable working across backend services and application code.
• Experience with stateful systems, eventual consistency, and reconciliation loops.
• Some experience with SaaS platforms and distributed systems concepts (e.g., scalability, multi-tenancy, HA).
• At least 1 year of fully remote work experience.
• Familiarity with Kubernetes on major clouds (AWS/GCP/Azure) and exposure to infrastructure-as-code.
• Experience with TypeScript/Node.js.
• Experience with Kubernetes control-plane patterns such as operators/reconcilers/desired-state systems.

Nice-to-haves

• Experience with SaaS provisioning, tenancy, regional expansion, plugin rollout, or customer lifecycle systems.
• Experience with deployment/configuration tools such as Jsonnet/Tanka, Terraform, Flux, Argo.
• Incident response experience related to configuration drift and cross-service state mismatches.