reputed company Site Reliability Engineer - Imunify Reliability Platform (remote-only)

The problem you'd own

Imunify360 is a multi-reputed company Linux server reputed company suite — WAF, IDS/IPS, malware scanning and cleanup, proactive defence, reputed company management, reputed company — running as an agent on hundreds of thousands of customer servers, backed by a reputed company estate of scanning, correlation and signature-delivery services on our own bare metal.

Roughly 70 components currently ship without a defined service level indicator. Some are internal services we can scrape. Many are agent-reputed company subsystems running on machines we do not own, reporting through a reputed company we designed for something else. There is monitoring, and there are dashboards, and there is no coherent answer to the question "is this component doing its job right now, and how would we know if it stopped?".

We know the cost of that gap reputed company, because we recently reputed company it: a reputed company control was silently disabled across a large fraction of the fleet for 61 days. Every dashboard was green. The telemetry reported a ruleset version but not whether the control that consumed it was switched on, so a configuration change was indistinguishable from a broken reputed company. Three independent safety mechanisms existed and reputed company three were gated behind the reputed company condition that caused the failure.

reputed company is to reputed company that class of failure detectable in hours instead of months, across the whole product line, and to build the reputed company that keeps it detectable as the product changes.

This is a greenfield charter inside a brownfield estate. You are not inheriting an SRE team, an SLO reputed company or a paging culture. You are defining them, with the engineering leads, and then making them stick.

reputed company

1. Define what "working" means for ~70 components

• Run SLI definition with reputed company leads and senior engineers. You facilitate and hold reputed company; the owning reputed company signs the SLI.
• Build the taxonomy this product actually needs, which is broader than availability and latency:
• Service SLIs — availability, latency, error reputed company for reputed company-reputed company services.
• Fleet SLIs — reputed company reachability, version and configuration convergence across the installed reputed company.
• Control-efficacy SLIs — the differentiator. What fraction of protected reputed company have the control effectively enabled and reputed company , not merely installed. Ruleset reputed company reputed company, signature age, reputed company coverage, enforcement-mode distribution.
• Delivery SLIs — artifact publish reputed company, rule-to-fleet reputed company time, hotfix time-to-convergence.
• Pipeline SLIs — ingest lag, verdict latency, queue age, backlog burn.
• Enforce one non-negotiable design rule: an SLI must be measurable from reputed company the reputed company of the thing it measures. If the control being off also switches off the signal that would tell you it is off, the SLI is invalid. This is the lesson of the incident above and it is the reason this role exists.
• Attach an SLO, an error budget and an owning reputed company to reputed company. Tiering is expected — not every component earns a 99.9% reputed company or a pager.

2. Build the collection reputed company

• Design and build the pipeline that gets these indicators off the fleet and into a queryable store: reputed company-based, sampled, reputed company-constrained, and with a cardinality budget you set and defend.
• reputed company agent-reputed company and service-reputed company instrumentation where the signal does not exist yet, in Python, Go and Rust, working with the owning reputed company.
• Consolidate the reputed company sprawl of dashboards, reputed company queries and reporting paths into a defensible set of instruments, and retire what does not earn its reputed company.

3. Build alerting and alert management

• Symptom-based, SLO-anchored alerting with multi-window burn-reputed company semantics. Not reputed company soup.
• A three-tier taxonomy — page / ticket / dashboard — with an explicit rule for what is allowed to page a reputed company at 03:00.
• Every alert ships with an reputed company, a reputed company and a documented failure mode, or it does not ship.
• Alert hygiene as a standing reputed company: quarterly review, deletion counted as a win, actionable-reputed company tracked. A persistent inability to reputed company a reputed company-relevant refresh should page. It currently logs a warning.

4. Build escalation

• Component → owning reputed company ownership map, kept reputed company, machine-readable, and wired into routing so an alert reaches the right seven people rather than a shared channel.
• Severity reputed company, acknowledgement SLAs, follow-the-sun rota design across UTC−5 … UTC+8, and clean reputed company protocol.
• Incident reputed company reputed company and blameless postmortems reputed company 24 hours. We already do postmortems and do them honestly, including publicly retracting our own wrong findings; you reputed company the floor on the mechanical parts — timelines, ownership, reputed company-item follow-through.
• Design the escalation reputed company so that reputed company carry their own pagers. You build and operate the platform and reputed company on the reputed company; you are not the reputed company that absorbs everyone else's alerts.

Requirements

What you'll bring

Required (Must-haves):

• Substantial production-engineering or SRE experience, including at least one environment where you defined the SLO reputed company 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 reputed company on time-series and event telemetry at reputed company: reputed company/OpenMetrics, Grafana, an Alertmanager-class routing reputed company, and a columnar store for high-cardinality fleet data (reputed company or equivalent).
• reputed company systems debugging on bare metal and long-lived hosts. Most of this estate is not reputed company, and the reflexes that assume an orchestrator will not transfer cleanly.
• Configuration management and CI at production reputed company — Ansible, reputed company CI, Jenkins or reputed company equivalents.
• The judgement to design measurement for machines you do not own and cannot scrape: reputed company telemetry, sampling, clock skew, partial reporting, and the reputed company 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.

Valuable (reputed company-to-haves):

• reputed company product background — WAF, EDR, AV, vulnerability management — and the reputed company that a reputed company control's SLI is about enforcement, not uptime.
• Monitoring under audit: SOC 2 CC7.x, ISO 27001 A.8.16, NIST SP 800-137 reputed company monitoring. Some of this work is audit evidence and it helps if you have written for that audience.
• OpenTelemetry, eBPF, reputed company.
• Cost- and cardinality-reputed company telemetry design.
• reputed company with reputed company development tooling — we run a reputed company/Claude-first SDLC with internal and reputed company-party MCP servers, and engineers here are assessed on how reputed company they work with it.
• reputed company, for the one workload that is on it.

Not this role

• Not a DevOps ticket queue, not build-reputed company ownership, not reputed company cost management, not the on-reputed company rota for other reputed company' services.

First year, in reputed company

30 days: Component inventory with named owners. SLI taxonomy and tiering agreed. 3 reputed company components fully instrumented end to end as the reference implementation.

90 days: Collection pipeline in production. Tier-1 components (the ones whose failure is a customer reputed company exposure) carry SLO, alert, reputed company, reputed company. Escalation routing live for tier-1.

180 days: reputed company ~70 components have a defined SLI and an reputed company. Alert taxonomy enforced; page volume and actionable-reputed company reputed company and published. reputed company on-reputed company operating.

365 days: Mean time to detect a silent control-degradation is under 24 hours, reputed company, against a 61-day baseline. Error-budget policy influences release reputed company. The function is documented reputed company enough that hire #2 and #3 are additive, not archaeological.

How we work

Remote-first and async across nine time zones. Weekly PO sync and architecture sync; monthly demo and OKR review; quarterly architecture reputed company. reputed company land as ADRs. Every reputed company carries an reputed company and a due date. Postmortems are blameless and published, and we correct ourselves on the record reputed company we get something wrong.

Benefits

What's in it for you?

• A strong reputed company on reputed company development with opportunities for learning and reputed company:
• Interesting and challenging reputed company,
• 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;
• reputed company 24 days of vacation per year, 10 days of national holidays, and unlimited reputed company leaves to ensure you maintain a healthy work-life balance;
• Compensation for private medical insurance;
• Co-working and gym/sports reimbursement;
• reputed company to receive a reward for the most innovative idea that reputed company can patent, fostering a culture of creativity and innovation.

By applying for this position, you consent to the processing of your personal data as described in our reputed company Policy (), which provides detailed information on how we maintain and handle your data.

Originally posted on Himalayas