Do I need fintech / payments background?
Strongly preferred for direct platform teams (Payments, Connect, Billing, Fraud). Less critical for adjacent teams (developer tools, infrastructure, internal tools). For payments-track applications: signal domain depth — idempotency, webhooks, settlement, reconciliation. Without prior fintech: substantive side projects on payment processing (e.g., implementing a mock payment gateway with proper retry semantics) demonstrate awareness.
What about Ruby/Rails experience?
Helpful but not required. Stripe's primary stack is Ruby with Sorbet (gradual typing) on Rails — this is publicly documented in Stripe engineering blog. For non-Ruby applicants: demonstrate equivalent dynamic-language fluency (Python, JS) + interest in typed Ruby. Sorbet familiarity is a plus signal but not required at screen.
How important is payments domain knowledge?
Very for screening, not absolute for hire. Resume that surfaces payments concepts (idempotency, webhooks, settlement, chargeback, capture/refund flow) signals domain depth that Stripe's screen specifically values. Without prior fintech: read Stripe's docs + engineering blog before applying — surface insights from this in the application.
Does Stripe sponsor visas?
Yes for SWE roles in San Francisco HQ + various US/global locations (Dublin, Singapore, etc.). Strong sponsor. International students with US/UK work eligibility have a clear path. Stripe is well-known for clean visa coordination.
What about Stripe's interview format?
Stripe's onsite has unique rounds: integration round (real GitHub repo + internet access — this is unusual at FAANG-tier companies), debugging round (debug existing codebase). Resume should signal you'd handle these well — bullets showing OSS contribution, debugging methodology, codebase navigation skill.
How long should my Stripe resume be?
1 page strict for <5 YOE. 1-2 pages for senior. Stripe culture values craft + clarity — same density bar as Google/Meta. Cut older roles to 1-line summaries.