Build backend infrastructure for wallets, identity, and onchain systems at Privy (Stripe)

Privy (acquired by Stripe) is hiring a backend engineer with 8+ years of experience to build the wallet, identity, and onchain infrastructure that powers crypto products for customers like Ramp, Klarna, and Kraken. The interview focuses on platform/API design at scale, a security-first mindset, and comfort leading complex technical initiatives with high product ownership in a small, fast-moving team.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Designing platform primitives/APIs used by other engineering teams
Security-first design for wallets, identity, and onchain infrastructure
Balancing high-velocity iteration with production-scale reliability
Acting as de facto PM for developer-facing API decisions
Leading complex, ambiguous technical initiatives independently

Common question themes

Design an API/platform primitive for wallet or identity infrastructure that other teams would build on

How do you bring a security mindset into a design from the start, not as an afterthought?

Tell me about a time you had to make a product decision without a PM in the room

How do you balance shipping small iterations fast against long-term platform scalability?

Walk me through a distributed systems or data model challenge you led end to end

What's your experience with blockchain protocols or smart contract integration, if any?

How candidates describe it

Real Backend Engineer interview stories — retold from candidates' public write-ups, with sources.

Google · Backend Software EngineerNo offer

Google Backend Engineer Interview Experience: Bangalore Onsite (Rejected)

A rejected Google Backend Engineer candidate in Bangalore recounts a recruiter screen, a gating elimination round, and a three-round onsite loop covering trees, tries, scheduling, and graph problems.

Interviewed April 2021 · Bangalore, India

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

View the original posting

All Stripe Backend Engineer interviews

All Stripe interviews