Stripe is hiring a Infrastructure Engineer, Privy in 9001 Privy - R&D — New York. The overview below is synthesized from the employer posting on stripe.com: factual requirements and scope are preserved, but prose is rewritten with editorial context. Verify details and apply via the employer link.
Who we are
About Privy
Company context from the listing:
Our mission is to make privacy and user ownership the default online. To do so, we build simple, flexible APIs and tools for developers that make it easy to build new products on crypto rails.
Privy owns the abstractions and infrastructure layer above wallets, integrating across chains, third-party providers, and Stripe products like Treasury and Link. We get to solve hard technical problems while leveraging Stripe's distribution to reach customers like Ramp, Klarna, Deel, Kraken, Hyperliquid, and Fomo — powering experiences for both mainstream users and crypto natives.
Learn more about Privy: Privy and Stripe: Bringing crypto to everyone
About the team
Company context from the listing:
Engineering at Privy is distinguished by:
- High urgency: Shipping very small iterations, very fast, to learn very quickly.
- Product taste: Our customers are developers, and to build effective products for them requires technical knowledge - you will often be "the PM".
- Security mindset: A great portion of our product is trust. While we have a dedicated security team, every engineer brings security to their designs from the start.
In practice, we use boring technology like Node, React, and AWS so we can focus our engineering energy entirely on pushing the boundaries of Privy's core product, e.g. through hardware enclaves, multi-region low latency APIs, and blockchain abstractions that are accessible to mainstream developers.
What you’ll do
Day-to-day scope for the Infrastructure Engineer, Privy as described in the posting:
- Manage and architect multi-tenant infrastructure that serves billions of requests every month
- Design our build and deploy systems across the stack, from SDKs to apps to high-traffic APIs to complex secure enclaves, and more – all for a team that ships daily
- Drive observability across our product and help keep our systems up and performant in our role in the most critical parts of our customers' stacks
- Advocate for making the right technical investments at the right time in a company with ever-evolving technical needs
Who you are
Experience and skills the team lists as required:
Minimum requirements
Experience and skills the team lists as required:
- 8+ years of experience in building highly available production systems
- Knowledge of Typescript or Python, Terraform or similar, Cloudflare, and AWS infrastructure
- An understanding of modern web and API development best practices
- Experience building delightfully simple developer experiences
Preferred qualifications
Experience and skills the team lists as required:
- An ability to quickly learn new skills and take on new challenges
- Experience at rapidly growing startups and the flexibility it requires
- Excitement about authentication, security, or in web3
- An understanding of EC2 Nitro Enclaves and ASGs/Kubernetes
Build a standout application
For the Infrastructure Engineer, Privy at Stripe, reviewers look for concise evidence over buzzwords. Mirror the language of the posting sparingly, quantify support or delivery outcomes, and show how you handled ambiguity, time-zone collaboration and user empathy. Keep your resume to impact, keep your cover note to one page, and link to artifacts — tickets resolved, docs shipped, dashboards owned — that prove you can operate in a fast-moving Web3 team. Prepare to discuss a time you turned a confusing user report into a clear fix and how you measure quality in support and operations.
Web3 hiring values reliability: on-time follow-through, clear writing, and a track record of improving runbooks and tooling. Treat the application as a work sample. For interviews, be ready to walk through how you prioritize across time zones, handle a difficult user, and decide when to escalate versus resolve directly. Show how you document decisions so the next teammate benefits.
In a distributed Web3 org, trust builds through written clarity. Use the cover note to demonstrate it.