Staff Site Reliability Engineer, Fingerprint

• 10+ years of engineering experience, with 3+ years as an SRE, production engineer, or reliability-focused Staff engineer operating across multiple teams — you have owned reliability for a platform, not just for a service you built
• Deep experience with SLI/SLO design and error budgets in practice, including the hard part: getting product teams to adopt and act on them
• Strong incident leadership: you have run incident response and postmortems for high-severity, customer-facing incidents and materially improved how an organization learns from them
• Hands-on depth in distributed systems failure modes — cache/database saturation and cascading failure, retry storms, capacity limits, degradation and load shedding — in a high-throughput, low-latency environment. Fluent in Kubernetes, AWS, and modern observability tooling (Datadog or equivalent)
• Comfortable reading and writing production code (Go, TypeScript, or similar) and infrastructure as code. You can ship a fix, not just recommend one
• Track record of leading through influence: you have changed how teams you did not manage operate, and can explain how adoption actually happened
• Teacher's instinct. You have coached engineers into owning reliability and can point to practices that persisted after you stepped back
• Exceptional written communication. You make incidents, risks, and trade-offs legible to engineers and executives alike, and you default to async, documented decision-making
• AI-native by default. You use AI tools as a normal part of how you investigate incidents, analyze telemetry, write runbooks and postmortems, and build tooling — and you have opinions, from experience, about where they accelerate reliability work and where they don't yet
• Operate for an AI-assisted org. You think about how runbooks, alerts, dashboards, and operational data should be structured so that both humans and AI agents can diagnose and act on them safely — legible signals, clear ownership, strong guardrails on automated change
• Pragmatism over purity. You know that reliability competes with delivery, and you can make the case for the right investment at the right time — and say when a risk is acceptable

Desirable

• You will be Fingerprint's first dedicated Site Reliability Engineer. You will work alongside our Architect on the shape of the platform, with Cloud Platform on the infrastructure that runs it, and with every product team on how they operate what they own — without direct reports
• The mandate has three parts. First, make reliability measurable: define SLIs and SLOs for our critical paths, get teams to own them, and make error budgets the shared language for prioritizing reliability against features
• Second, raise the operational bar: strengthen incident response, postmortem quality, alerting, and change safety so that we find out first and repeat incidents stop repeating
• Third, build the mindset: coach teams to design for failure, test for it deliberately, and treat operability as part of done — so the practices outlive your involvement in any single team
• You report directly to the VP of Engineering. That placement is deliberate: reliability standards need to apply evenly across eight engineering groups, and you need the neutrality to hold every team, including infrastructure, to the same bar
• Make reliability measurable:
• Define SLIs and SLOs for Fingerprint's critical request paths (identification, events, server APIs, client agents) with the teams that own them; make them visible, reviewed, and tied to decisions
• Introduce error budgets as the mechanism for balancing reliability investment against feature work, and coach EMs and Staff engineers on using them
• Own the reliability metrics that leadership uses to judge progress; be the No Nonsense voice on whether we are actually getting better
• Raise the operational bar:
• Strengthen the incident lifecycle end to end: detection, response, communication, postmortem quality, and follow-up completion. Make the postmortem the most useful document a team writes
• Close the "customers find out before we do" gap: drive alert quality, correctness anomaly detection, and escalation design across teams, working with Cloud Platform on shared tooling
• Lead reliability reviews for high-risk changes and new services (production readiness, capacity, failure modes, rollback), teaching through review rather than gatekeeping
• Introduce deliberate failure testing (game days, chaos exercises) in staging first, then production, to discover gaps and safe limits before customers do
• Build the SRE mindset in teams:
• Embed with teams for time-boxed engagements: pair on their hardest reliability problems, leave behind better practices and a stronger owner, then move on
• Develop Staff and Lead engineers as reliability leaders in their own groups — the goal is that every team has someone who thinks like an SRE
• Codify practices that stick: production readiness checklists, on-call standards, runbook quality, change safety norms. Make them lightweight enough that teams choose to use them
• Partner with the Architect and tech leads so reliability is designed in, not retrofitted
• Stay hands-on:
• Dig into production during incidents and investigations. Write tooling, dashboards, and reference implementations. Be credible with the engineers you are asking to change how they work
• Lead AI adoption in reliability practice: set norms for AI-assisted incident investigation, postmortem analysis, runbook authoring, and observability tooling across teams, and shape our runbooks, alerts, and operational data so AI agents can safely help diagnose and operate our systems alongside engineers