Little more about the team:

Honeycomb’s Site Reliability Engineering (SRE) team works at the intersection of infrastructure, developer experience, and organizational enablement. We lead technically complex, cross-team projects that improve reliability, scale systems, and make life easier for engineering teams. We’re trusted across the company to set direction, solve ambiguous problems, and build processes that run smoothly. Our work spans AWS infrastructure, Kubernetes, Helm, Terraform, Kafka, and other tools, aligned with the sociotechnical needs of scaling a fast-growing company. We’re a collaborative, diverse team that values experimentation, data-driven decisions, and maintaining a safe environment for healthy debate and innovation.

What you’ll do in the role:

• Help Honeycomb scale our backend systems to support our highest-volume customers.
• Build organizational trust through transparent communication, giving and receiving direct and kind feedback.
• Work with other backend teams to dive deep into our stack to make sure we’re getting the most out of our infrastructure.
• Be trained, become, and then train others as an Incident Commander.
• Help SRE and Honeycomb develop a healthy cross-Atlantic engineering culture.
• Participate in the team’s on-call rotation as the EU side of a new follow-the-sun rotation.
• Help the organization navigate tradeoffs between reliability and its other goals and priorities.
• Optional: act as an external ambassador through blog posts, conference talks, and presentations with support from our DevRel team.

What You’ll Bring:

• Strong experience in AWS and Kubernetes.
• Experience performing cost analysis and reduction.
• Solid Helm, Terraform, and CI/CD experience.
• Project management skills.
• Software engineering experience (Golang is a plus, and so is performance engineering).
• Experience with Kafka or another high-volume distributed system.
• Excellent written and spoken communication skills, with the ability to tailor your communication for your audience and give direct feedback when you notice something wrong.
• A curiosity to learn how people and systems work, and the willingness to make them partners in your initiatives.
• Familiarity with observability concepts (SLOs, instrumentation) and data-driven decision making.
• Comfort operating in ambiguity, with a bias for action and experimentation.
• Interest in both the technical and human sides of reliability engineering.
• Experience working in geographically distributed teams.