We use technical cookies and visit statistics: Yandex Metrica and Zorky's own de-identified visit log (cookie zk_aid). We never collect form contents, search text or full IP addresses, and never sell data. Opt out with the button below, or with Global Privacy Control or Do Not Track in your browser. More about cookies and statistics.
Zorky CRMZorky CRM
EN|RU
@termdocs
← All jobs

Senior Site Reliability Engineer

seniorhybrid2,000 USD · period not specifiedWarsaw, PLScore 75/1001w ago
Stack
Site Reliability EngineeringAzureTerraformAzure Kubernetes ServiceBicepCI/CDPythonAI ObservabilityBashFinOpsagileaws
Show company and link
Free. Sign in with email.
Apply
Upload your CV — we will connect you with the employer directly through our pool.
Send your CV →
Description
We are seeking a Senior Site Reliability Engineer to own the reliability, observability, and operational health of production AI systems, bridging the gap between deployment and long-term operability while embedding cost, security, and quality discipline into every solution's lifecycle. Responsibilities Own deployment end-to-end, including infrastructure as code, CI/CD pipelines, and environment management on Azure, ensuring every environment is rebuildable from source Build LLM-aware observability with traces on every model call, production quality signals such as eval sampling, drift detection, and guardrail-trigger rates, plus cost and latency dashboards Define and defend SLOs covering availability, latency, and quality objectives per solution, balancing delivery speed against stability with data-driven error budgets Run incident management, including on-call models, runbooks written before incidents occur, and blameless postmortems afterward Manage the cost of intelligence by monitoring token economics per solution, wiring in budgets and alerts, and conducting capacity planning proactively Keep the security posture current through patching, secret rotation, access reviews, and audit readiness across the solution's entire lifecycle Shape operability requirements before handover, ensuring they land in the pod's definition of done, and run hypercare jointly with sign-off on what will be operated Feed operational patterns, failure modes, and cost learnings back to the pods an
Full description, company and the link to apply — after you sign in. Sign in
Employer contacts (email/phone/telegram) are hidden from the public preview — send your CV, and we will connect you directly.
Urgent question? Message @termdocs