Artwork

Content provided by David Noël-Romas (@davidnoelromas) and Alex Kessinger (@voidfiles), David Noël-Romas (@davidnoelromas), and Alex Kessinger (@voidfiles). All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by David Noël-Romas (@davidnoelromas) and Alex Kessinger (@voidfiles), David Noël-Romas (@davidnoelromas), and Alex Kessinger (@voidfiles) or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Bryan Berg (Stripe)

50:46
 
Share
 

Manage episode 307282675 series 2897195
Content provided by David Noël-Romas (@davidnoelromas) and Alex Kessinger (@voidfiles), David Noël-Romas (@davidnoelromas), and Alex Kessinger (@voidfiles). All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by David Noël-Romas (@davidnoelromas) and Alex Kessinger (@voidfiles), David Noël-Romas (@davidnoelromas), and Alex Kessinger (@voidfiles) or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Staff engineers may not get much time to code anymore, but this does not mean problem-solving and system design is not an integral part of their day-to-day. Today’s guest is Bryan Berg, Staff Engineer at Stripe, and he joins us to talk about the nuances of his position and his unique approach to the many challenges it entails. As a Staff Engineer, Bryan acts as Tech Lead of the Traffic team, and we begin our conversation by hearing about how he landed in this role. Bryan describes the ambiguous challenges he faced during earlier days at Stripe, and the knack he had for finding and working on processes and systems that were previously underinvested in. We then jump forward to the present and dig into what Bryan’s current role entails, hearing him describe a wide range of tasks from reviewing documentation, communicating between teams, writing vision documents, and ensuring the work he directs falls into the company and stakeholder requirements. We also explore the interesting concept of when to draw on past experience versus keeping an open mind when facing new challenges. On top of all this, our conversation covers how Bryan judges the success of his work, sustains faith in his ideas, pitches to colleagues, debugs difficult pieces of code, and finds inspiration to be a great technical leader.

  continue reading

22 episodes

Artwork

Bryan Berg (Stripe)

StaffEng

32 subscribers

published

iconShare
 
Manage episode 307282675 series 2897195
Content provided by David Noël-Romas (@davidnoelromas) and Alex Kessinger (@voidfiles), David Noël-Romas (@davidnoelromas), and Alex Kessinger (@voidfiles). All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by David Noël-Romas (@davidnoelromas) and Alex Kessinger (@voidfiles), David Noël-Romas (@davidnoelromas), and Alex Kessinger (@voidfiles) or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Staff engineers may not get much time to code anymore, but this does not mean problem-solving and system design is not an integral part of their day-to-day. Today’s guest is Bryan Berg, Staff Engineer at Stripe, and he joins us to talk about the nuances of his position and his unique approach to the many challenges it entails. As a Staff Engineer, Bryan acts as Tech Lead of the Traffic team, and we begin our conversation by hearing about how he landed in this role. Bryan describes the ambiguous challenges he faced during earlier days at Stripe, and the knack he had for finding and working on processes and systems that were previously underinvested in. We then jump forward to the present and dig into what Bryan’s current role entails, hearing him describe a wide range of tasks from reviewing documentation, communicating between teams, writing vision documents, and ensuring the work he directs falls into the company and stakeholder requirements. We also explore the interesting concept of when to draw on past experience versus keeping an open mind when facing new challenges. On top of all this, our conversation covers how Bryan judges the success of his work, sustains faith in his ideas, pitches to colleagues, debugs difficult pieces of code, and finds inspiration to be a great technical leader.

  continue reading

22 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide