We’re looking for a mid-level SRE to own observability and alerting across our platform. Right now our monitoring lives primarily in New Relic, and while we’ve built solid foundations (Kafka consumer lag tracking, infrastructure health dashboards, custom NRQL alert policies), we know there’s a lot more to do. You’ll be the person driving this forward.

This isn’t a pure ops role. You’ll write code, design alerting architectures, and work closely with the engineers shipping the platform. When something is on fire, you’ll be one of the people who actually understands why.

What you’ll do

Own and mature our observability stack: alerting policies, dashboards, on-call runbooks, and incident response workflows
Design and tune alert conditions in New Relic (NRQL, baseline and anomaly detection, composite conditions) to minimize noise and maximize signal
Identify gaps in our monitoring coverage across services, message queues, infrastructure, and network links
Build and maintain tooling that helps the team understand system behavior, not just when things break, but before they do
Automate, glue systems together, and write a useful tool in Python when one doesn’t exist
Collaborate with platform engineers on SLIs, SLOs, and error budgets
Participate in the on-call rotation and drive post-incident improvements
Contribute to infrastructure work when needed

What we’re looking for

Must-have

3 to 5 years of experience in SRE, platform engineering, or a strong DevOps role
Hands-on experience building and maintaining observability systems (alerting, dashboards, tracing, logging) with New Relic, Datadog, Grafana, or similar
Solid Linux fundamentals and comfort operating in cloud-hosted VM environments
Experience with containerised workloads (Docker, Docker Compose)
A systematic approach to debugging: you form hypotheses, isolate variables, and document what you find
Good written communication. We write things down

Nice-to-have

Experience with Kafka or other message streaming systems
Experience with Redis or other caching technologies
Familiarity with network-level infrastructure (VPNs, firewall rules, routing)
Exposure to telecom or IoT connectivity domains
Experience with NRQL or another query language for observability platforms
Infrastructure as code experience (Terraform, Ansible, or similar)
Familiarity with Kubernetes. We’re not there yet, but directionally heading that way

What we offer

A technically honest environment. We’ll tell you what’s messy and where improvement is needed
Meaningful ownership from day one, with no layers of process between you and the problem
An experienced team
Competitive salary based on experience
Flexible hours and autonomy over how you work, within an on-site team culture
The chance to shape the reliability culture of a growing IoT and connectivity platform

How to apply

Send a short note about yourself and why this role interests you, along with your CV, to careers@cobira.co. You don’t need a formal cover letter. Just tell us something real about what you’ve worked on and what kind of problems you like solving. Questions before applying are welcome, just ask in the same email.