![]() We had the pleasure of sitting down with Andreas to mine his wisdom: from brass-tacks advice on how and when to build your own tools and how to roll them out, to reflections on the human factors important to a successful incident response program. With this experience at Stripe, Andreas has a uniquely broad view on evolving incident response as a company grows from baby startup to a big player. He later joined as one of the first engineers on the Reliability Tooling team and adapted BRB to serve the entire incident response lifecycle. He helped launch the first version of the main tool (internally nicknamed the “Big Red Button”) and get it successfully adopted. Over the next nine years, he saw the company grow to over 3000 people across the globe and launch numerous new products that would make Stripe a leading online payments provider, handling payments for companies like Amazon, Google, Shopify and Lyft.Īmong the many projects Andreas took on was building Stripe’s internal incident response tools. When Andreas Fuchs joined Stripe as an engineer in 2012, the company was about 25 people located in a former wedding chapel hidden behind a wine bar in Palo Alto, working on one main product, the payments API. The importance of names, the surprising benefits of restricting your product, and other lessons from an engineer who built Stripe’s “Big Red Button”
0 Comments
Leave a Reply. |