Hiring in DevOps & Cloud Infrastructure

• SRE

  Site reliability engineers · Senior SREs · Staff SREs · SRE managers

• Platform engineering

  Platform engineers · Developer-experience leads · IDP owners

• Cloud infrastructure

  Cloud engineers (AWS/GCP/Azure) · Networking engineers · Kubernetes specialists

• Security engineering

  Cloud security engineers · AppSec engineers · IAM specialists

• SRE vs platform vs DevOps

  These labels are used interchangeably but mean different things. Rubrics capture the actual remit: reliability, developer experience or ops automation.

• Scale and blast radius

  Running a startup cluster and running a fleet at hyperscale are not comparable. Scale is captured with named metrics.

• Cost fluency

  Cloud cost is now a first-class skill. FinOps discipline is scored explicitly.

• On-call reality

  Rota depth, escalation ownership and incident-commander experience vary hugely between candidates who all list 'on-call' on the CV.

Every candidate is scored against the role's rubric, and every score points back to a specific line in the CV. For devops & cloud infrastructure, these are the signals that carry weight:

• Remit-specific rubric
• Scale and blast radius captured
• FinOps fluency surfaced

1. A ranked set of candidates, each with a score and the evidence behind it.
2. Eligibility checks resolved before the candidate reaches you — right to work, credentials, location model.
3. Salary expectation against your band, stated plainly, before you invest interview time.
4. One decision per candidate: advance, hold or decline, reversible for a short window.

Candidates stay invisible to you until we've reviewed them for your specific role, and contact details are released as a separate step.