Senior SRE - Dot

Persevio

Persevio is an AI-powered recruitment platform. We focus on making high-quality recruitment efficient through AI, combining innovative technology with recruitment expertise to support businesses in identifying and hiring top talent.

Job Description

**Location:** Fully remote, with work location and collaboration schedule agreed individually.

**Company Overview**
Persevio is an AI-powered recruitment platform. We focus on making high-quality recruitment efficient through AI, combining innovative technology with recruitment expertise to support businesses in identifying and hiring top talent.

**Role Overview**
Join Persevio as a senior individual contributor focused on production reliability, observability, and operability. You will partner with engineering to understand the current environment, prioritize reliability risks, and deliver practical improvements through hands-on engineering, evidence, and collaboration.

**How You’ll Make an Impact**
* **Establish Reliability Standards:** Design user-facing SLIs/SLOs and error-budget practices with service owners. Partner with the Engineering Lead on priorities, escalation, and release-risk decisions.
* **Lead Incident Management:** Own incident coordination, technical investigation, and clear communication; lead blameless reviews and follow through on preventive actions.
* **Build & Automate:** Develop safe, maintainable infrastructure and deployment automation using Python or Go, infrastructure as code, and CI/CD to reduce repetitive operational toil.
* **Advanced Troubleshooting:** Resolve complex issues across Linux, networking, cloud services, and Kubernetes/container workloads using metrics, logs, and traces.
* **Optimize Resilience:** Improve actionable alerting, runbooks, capacity planning, and recovery readiness. Collaborate on resilience, access controls, and cloud cost efficiency.
* **On-Call Support:** Participate in a planned shared on-call rotation with documented escalation. Coverage, cadence, and arrangements will be discussed before offer.

**What You’ll Bring to the Team**
* **Minimum/Core Requirements:**
* Demonstrated senior-level expertise in software, platform, or production engineering, including substantial hands-on reliability work (equivalent demonstrated expertise is welcome, and there is no maximum-experience limit).
* Production experience with at least one major cloud platform, Kubernetes/containers, infrastructure as code, CI/CD, and observability. (Equivalent tools are welcome; no particular cloud vendor is required).
* Strong automation skills in Python or Go, including testing, safe rollout, and rollback.
* Proven track record in incident participation with clear personal decisions, communication, and preventive follow-through. A formal incident-commander title is not required.
* Ability to independently design a sensible SLI/SLO and explain error-budget tradeoffs. Material contribution is sufficient; sole ownership of an entire SLO programme is not required.
* Proficiency in Business English is required for incident coordination, technical documentation, and cross-team collaboration.
* Sound judgment and the ability to provide constructive influence across engineering teams. No specific degree, employer, or industry background is required.
* **Preferred/Bonus Requirements:**
* Experience in database reliability, distributed systems, security collaboration, or AI/ML-service operations.

**What We Offer**
* **Flexible Working Arrangements:** This role is fully remote. Work location, a practical collaboration schedule, and lawful engagement feasibility are agreed individually before offer. Start date is negotiable.
* **Meaningful Early Outcomes:** In your first 90 days, you will map critical services and reliability risks, agree on ownership with engineering, and deliver a prioritized reliability roadmap alongside measurable automation improvements.
* **Transparent Interview Process:** Our process includes a 30-minute role conversation, a 60-minute practical engineering discussion covering incidents/SLOs/automation, and a final 45-minute discussion with the Engineering Lead on ownership and collaboration.