DevOpsDays Boston 2022: Gad Salner- How to scale a unicorn-building engineering team (and stay sane)

Channel:
Subscribers:
42,400
Published on ● Video Link: https://www.youtube.com/watch?v=I7bPHxwAGv4



Duration: 23:01
12 views
0


THE most common question I get asked by people familiar with my recent journey is: ״how the hell did you go from a team of 1 to a 25 person engineering group in a year?״

We weren’t short on challenges this past year: lockdowns, remote onboarding for new employees, and hyper-growth struggles. Each of these can break a team on their own. But when you create and instill fundamental habits that grow individual capabilities, expanding the team isn’t just possible, it’s actually quite a natural progression.

Without a solid game plan wouldn’t have made it very far. And moving forward, we’ve laid a roadmap that gradually empowers those 25 engineers to grow and take ownership, paving the way for the next 50.

This is the story behind one of our engineering groups, and how we’re building a kickass, world-class team, which among other things, is changing the conversation around payments.

In this talk, I’ll take a deep dive into our new strategy step-by-step, from planning to execution: my structured game plan for empowering engineers to drive your team’s rapid growth in size, responsibility, and impact.




Other Videos By Confreaks


2023-03-01RubyConf Mini 2022: Splitwise Sponsor Session: Declare Victory with Class Macros by Jess Hottenstein
2023-03-01RubyConf Mini 2022: Weaving and seaming mocks by Vladimir Dementyev
2023-03-01RubyConf Mini 2022: From Start to Published, Create a game with Ruby! by Cameron Gose
2023-03-01RubyConf Mini 2022: Anyone Can Play Guitar (With Ruby) by Kevin Murphy
2023-03-01RubyConf Mini 2022: The Case Of The Vanished Variable - A Ruby Mystery Story by Nadia Odunayo
2023-01-30DevOpsDays Boston 2022: Thomas Stringer - Zero to Secure: Using Open Service Mesh to Easily...
2023-01-30DevOpsDays Boston 2022: Andreas Grabner - DevSecOps by Default: What have, can and must we learn...
2023-01-30DevOpsDays Boston 2022: Kavitha Govindarajulu - Evaluating Your Toolbox
2023-01-30DevOpsDays Boston 2022: Steve McGhee, James Brookbank - Enterprise Roadmap for SRE
2023-01-30DevOpsDays Boston 2022 - We can’t all be Shaq: why it’s time for the SRE hero... by Malcolm Preston
2023-01-30DevOpsDays Boston 2022: Gad Salner- How to scale a unicorn-building engineering team (and stay sane)
2023-01-30DevOpsDays Boston 2022: Daniel Kim - Achieving 99.99% uptime with Open Source Observability
2023-01-30DevOpsDays Boston 2022: Peter Chestna - Feedback: You don't have to be bad to get better
2023-01-30DevOpsDays Boston 2022: Kam Lasater - How to Fail at Serverless (without even trying)
2023-01-30DevOpsDays Boston 2022: Adarsh Shah - From Infrastructure as Code to Environment as Code: ...
2023-01-16RailsConf 2022 - Diversity in Engineering; a community perspective
2023-01-16RailsConf 2022 - Keynote: RailsConf 2022 - It's been a minute! by Aaron Patterson
2023-01-16RailsConf 2022 - Testing legacy code when you dislike tests (and legacy code) by Maeve Revels
2023-01-16RailsConf 2022 - Don't page me! How we limit pager noise at New Relic by Chuck Lauer Vose
2023-01-16RailsConf 2022 - ELI5: A Game Show on Rails by Andy Glass
2023-01-16RailsConf 2022 - Spacecraft! The care and keeping of a legacy ... by Annie Lydens & Jenny Allar



Tags:
DevOps
DevOpsDays