Stripe is hiring a Software Engineer, Authorization Infrastructure in 8613 Data Privacy — N/A. 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 Stripe
Company context from the listing:
Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world’s largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities.
About the team
Company context from the listing:
Stripe will succeed at our mission of increasing the GDP of the internet only if we preserve Stripe users’ trust. To achieve their trust, the team is building authorization infrastructure and a platform that ensures proper authorization for users and services.
What you’ll do
Day-to-day scope for the Software Engineer, Authorization Infrastructure as described in the posting:
We’re looking for an engineer who is passionate about addressing tough problems in the authorization space. This role is critical, not only for Stripe, but for the future of the commercial internet.
Responsibilities
Day-to-day scope for the Software Engineer, Authorization Infrastructure as described in the posting:
- Build and maintain reliable, performant and scalable authorization infrastructure (e.g. libraries, frameworks, services).
- Build comprehensive understanding of authorization needs of our users (e.g. product teams and infrastructure teams).
- Build comprehensive, easy-to-use, and policy driven authorization solutions.
- Collaborate with our users to adopt our authorization solutions to protect their resources by providing a great user experience.
- Build access visibility and continuous policy governance to empower resource owners, legal and compliance to put risk of inappropriate access under control.
Who you are
Experience and skills the team lists as required:
We’re looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply.
Minimum requirements
Experience and skills the team lists as required:
- 2-5 years of professional hands-on software development experience
- Has experience in the security domain
- Has a curious and learning mindset, regardless of level or experience
- Has empathy, strong communication skills and a deep respect for the power of collaboration
- Works well cross-functionally and cross-team; and your co-workers at all levels trust you
- Drives clear next steps when encountering ambiguous spaces without clear lines of ownership
- Thinks creatively and holistically when solving problems
- Prefers simple solutions and designs over complex ones, and have a good intuition for what is lasting and scalable.
- High standards for code quality and a constructive attitude to help others raise the bar
Preferred qualifications
Experience and skills the team lists as required:
- Experience in the authorization domain
- Experience with Go, Java or Ruby
Build a standout application
For the Software Engineer, Authorization Infrastructure 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.