Bloodcuff
ActiveSite Reliability Engineer
End to End Owner
You’ve applied to Bloodcuff. The hiring team has asked you to take the next step here: an evaluation run by Evidal — a conversation about real work you’ve done, not a form. What you say goes to the hiring team as a structured read of your experience.
This isn’t a resume. It’s a conversation about real work you’ve done — not bullet points, not titles, not buzzwords. Every evaluation runs the same way, for everyone. Nobody is filtered out by keywords. Learn more ↗
Pick a marker, or open a requirement from the list.
What this role needsWhat you’ll be asked about.
Read it before you start, then open a requirement to see why this team asks for it and what kind of story lands.
Required experience
Be ready to discuss a real project for each — one project can cover several.
Every one of these comes up.
01Kubernetes in productionManaging workloads, debugging failures, scaling services, and handling on-call incidents on a Kubernetes-based stack.
Why this team asks for it
The platform runs on Kubernetes; operating it reliably is the role's central task.
Written by the hiring team for this role.
What to bring
A project you personally built.
- What you built yourself.
- What you decided, and why.
- What you would do differently now.
02AWS cloud operationsProvisioning and operating infrastructure, managing IAM, networking, and cost on AWS.
Why this team asks for it
AWS is the stated cloud provider for all production services.
Written by the hiring team for this role.
What to bring
A project you personally built.
- What you built yourself.
- What you decided, and why.
- What you would do differently now.
03Observability toolingImplementing and maintaining Prometheus, Grafana, and OpenTelemetry pipelines; alerting and SLO tracking.
Why this team asks for it
Building observability is an explicit responsibility covering metrics, tracing, and dashboards.
Written by the hiring team for this role.
What to bring
A project you personally built.
- What you built yourself.
- What you decided, and why.
- What you would do differently now.
04Infrastructure as CodeWriting and maintaining Terraform (or equivalent) modules for repeatable, auditable infrastructure changes.
Why this team asks for it
Automating infrastructure with IaC is an explicit responsibility.
Written by the hiring team for this role.
What to bring
A project you personally built.
- What you built yourself.
- What you decided, and why.
- What you would do differently now.
05Scripting language for operations automationWriting runbooks, automation scripts, and lightweight tooling for operational workflows.
Why this team asks for it
Scripting is required for automation and tooling tasks across the role.
Written by the hiring team for this role.
What to bring
A project you personally built.
- What you built yourself.
- What you decided, and why.
- What you would do differently now.
Any of: Python · Go
06Linux and networking fundamentalsDebugging network issues, tuning OS parameters, reasoning about packet paths and DNS in production incidents.
Why this team asks for it
Strong Linux and networking is a stated hard requirement underpinning all reliability work.
Written by the hiring team for this role.
What to bring
A project you personally built.
- What you built yourself.
- What you decided, and why.
- What you would do differently now.
07Incident management and postmortemsLeading incident response, writing blameless postmortems, and driving follow-up action items.
Why this team asks for it
On-call ownership and incident response are central to the role.
Written by the hiring team for this role.
What to bring
A project you personally built.
- What you built yourself.
- What you decided, and why.
- What you would do differently now.
Strongly preferred experience
An example you can talk through is enough.
These come up when there is time — and “not yet” is a real answer.
08SLO definition and ownershipDefining error budgets, surfacing reliability signals to product teams, and negotiating prioritisation of reliability work.
Why this team asks for it
Driving SLOs with the product engineering team is an explicit responsibility.
Written by the hiring team for this role.
What to bring
A situation you were accountable for.
- The situation, in specifics.
- How you handled it.
- Where it ended up.
The same requirements are listed in skill.md so your agent can prepare from them. Open skill.md ↗
Ready to get started?Two ways to apply — pick the one that fits.
With your AI agent
Give your agent this link and ask it to apply for you. It reads the instructions and takes it from there.
https://evidal.ai/api/v1/company/bloodcuff/roles/site-reliability-engineer/skill.mdOr paste this into your agent:
Read https://evidal.ai/api/v1/company/bloodcuff/roles/site-reliability-engineer/skill.md and apply to this role on my behalf. Use what you already know about my work, and ask me for anything you're missing.