How I’d prep for Stripe’s Backend Engineer role in 30 days

What this team actually does

The posting says: design, build, and maintain large-scale, low-latency services and data pipelines, with “watertight” accuracy across trillions of dollars.

From my research, this is most likely Stripe’s Regulatory and Compliance Engineering team. They run Stripe’s ledger, the record of every dollar that moves through Stripe. They calculate tax on Stripe’s fees and produce tax and regulatory reports.

How I found this (do this for any job)

1. Search for older postings with the same title. Google "<exact job title>" <company>. Job aggregators keep closed postings. Look for one with the same responsibilities. Older versions often name the team and list more tools.
2. Find people on the team. Google site:linkedin.com/in <company> "<team name>", then open the profiles yourself and read the skills listed for their current role. Here, a team member’s profile lists Spark and Airflow.
3. Check what repeats. If a tool shows up in the posting and on the profiles, study it.

System design questions

• Design a ledger that records every money movement at Stripe. How do you guarantee balances are always correct?
• Design a daily pipeline that calculates tax owed for millions of merchants. What happens if it fails halfway?
• Two systems disagree on yesterday’s total by $3. How do you find out why?

Concepts they’ll probe

• How do idempotency keys work, and where do you store them?
• Snapshot isolation vs serializable: when does write skew corrupt a balance?
• How do you change an API without breaking existing clients?
• Spark: what triggers a shuffle, and why is it expensive?
• Airflow: what happens when a task fails, and how do backfills work?