Overview

The problem you’d own Imunify360 is a multi-layer Linux server security suite — WAF, IDS/IPS, malware scanning and cleanup, proactive defence, patch management, reputation — running as an agent on hundreds of thousands of customer servers, backed by a cloud estate of scanning, correlation and signature-delivery services on our own bare metal.

Responsibilities:
  • Run SLI definition with squad leads and senior engineers. You facilitate and hold the standard; the owning squad signs the SLI
  • Build the taxonomy this product actually needs, which is broader than availability and latency
  • Enforce one non-negotiable design rule: an SLI must be measurable from outside the gate of the thing it measures
  • Attach an SLO, an error budget and an owning squad to each. Tiering is expected — not every component earns a 99.9% target or a pager
  • Design and build the pipeline that gets these indicators off the fleet and into a queryable store: push-based, sampled, privacy-constrained, and with a cardinality budget you set and defend
  • Extend agent-side and service-side instrumentation where the signal does not exist yet, in Python, Go and Rust, working with the owning squads
  • Consolidate the current sprawl of dashboards, ad-hoc queries and reporting paths into a defensible set of instruments, and retire what does not earn its keep
  • Symptom-based, SLO-anchored alerting with multi-window burn-rate semantics. Not threshold soup
  • A three-tier taxonomy — page / ticket / dashboard — with an explicit rule for what is allowed to page a human at 03:00
  • Every alert ships with an owner, a runbook and a documented failure mode, or it does not ship
  • Alert hygiene as a standing practice: quarterly review, deletion counted as a win, actionable-rate tracked. A persistent inability to perform a security-relevant refresh should page. It currently logs a warning
  • Component → owning squad ownership map, kept current, machine-readable, and wired into routing so an alert reaches the right seven people rather than a shared channel
  • Severity matrix, acknowledgement SLAs, follow-the-sun rota design across UTC−5 … UTC+8, and clean handoff protocol
  • Incident command practice and blameless postmortems within 24 hours
  • Design the escalation system so that squads carry their own pagers. You build and operate the platform and coach on the practice; you are not the buffer that absorbs everyone else's alerts
Required Qualifications:
  • Substantial production-engineering or SRE experience, including at least one environment where you defined the SLO framework rather than inherited it. We will ask you to walk through SLIs you personally wrote and how you negotiated them with resistant teams
  • Strong Python. Comfortable reading and modifying Go or Rust — our agents are written in them and instrumentation lands there
  • Deep practical grip on time-series and event telemetry at scale: Prometheus/OpenMetrics, Grafana, an Alertmanager-class routing layer, and a columnar store for high-cardinality fleet data (ClickHouse or equivalent)
  • Distributed systems debugging on bare metal and long-lived hosts. Most of this estate is not Kubernetes, and the reflexes that assume an orchestrator will not transfer cleanly
  • Configuration management and CI at production scale — Ansible, GitLab CI, Jenkins or close equivalents
  • The judgement to design measurement for machines you do not own and cannot scrape: push telemetry, sampling, clock skew, partial reporting, and the privacy constraints that come with running on a customer's server
  • Written communication that holds up async. This role is 40% telemetry engineering and 40% getting sixty engineers to agree on what "healthy" means; the remaining 20% is refusing to let the answer be a dashboard nobody reads
Benefits:
  • A strong focus on professional development with opportunities for learning and growth
  • Interesting and challenging projects
  • Mentor and other knowledge-exchange programs
  • Fully remote work with flexible working hours, that allows you to schedule your day and work from any location worldwide
  • Paid 24 days of vacation per year, 10 days of national holidays, and unlimited sick leaves to ensure you maintain a healthy work-life balance
  • Compensation for private medical insurance
  • Co-working and gym/sports reimbursement
  • The opportunity to receive a reward for the most innovative idea that the company can patent, fostering a culture of creativity and innovation
Nice To Have:
  • Security product background — WAF, EDR, AV, vulnerability management — and the instinct that a security control's SLI is about enforcement, not uptime
  • Monitoring under audit: SOC 2 CC7.x, ISO 27001 A.8.16, NIST SP 800-137 continuous monitoring. Some of this work is audit evidence and it helps if you have written for that audience
  • OpenTelemetry, eBPF, Sentry
  • Cost- and cardinality-aware telemetry design
  • Fluency with agentic development tooling — we run a Cursor/Claude-first SDLC with internal and third-party MCP servers, and engineers here are assessed on how well they work with it
  • Kubernetes, for the one workload that is on it
  • Python
  • Go
  • Rust
  • Prometheus/OpenMetrics
  • Grafana
  • Alertmanager
  • ClickHouse
  • Ansible
  • GitLab CI
  • Jenkins
Technologies:
  • Python
  • Go
  • Rust
  • Prometheus
  • OpenMetrics
  • Grafana
  • Alertmanager
  • ClickHouse
  • Ansible
  • GitLab CI
  • Jenkins
Note:

✨ Our intelligent job search engine discovered this job and republished it for your convenience.
Please be aware that the job information may be incorrect or incomplete. The job announcement remains the property of its original publisher. To view the original job and its full details, please visit the job's URL on the owner’s page.

Please clearly mention that you have heard of this job opportunity on https://ijob.am.