An application made for this job — a tailored resume and cover letter that speak straight to the posting.
Fingerprint is seeking a dedicated Site Reliability Engineer to shape platform reliability across eight engineering groups. You will define SLIs/SLOs, drive incident response improvements, and coach teams to design for failure.
This role reports to the VP of Engineering and requires partnering with Cloud Platform for shared tooling. You will influence how reliability is prioritized against features, raise the bar on postmortems, alerting, and change safety, and help the organization treat
Fingerprint empowers enterprises to detect and stop online fraud with the world’s most accurate device intelligence. We lead our industry with bleeding-edge identification capabilities and work on turning new ideas and discoveries in the fraud detection space into reality. Our customers range from innovative startups to leading enterprise companies, including Plaid, Dropbox, and Booking.com.
Fingerprint is a globally dispersed, 100% remote company. We were named on on the 2026 Forbes Best Startup Employers list and ranked #803 on the 2026 Inc. 5000 list of America’s fastest-growing private companies.
We have raised $77M and are backed by Craft Ventures (Tesla, Facebook, Airbnb ), Nexus Venture Partners ( Postman, Apollo.io, MinIO, Druva) and Uncorrelated Ventures ( Redis, Rollbar, Gradle).
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
Raise the operational bar