Partners

It's expected for the structure of your teams and organization to change as you grow. This is also true for the processes and communication channels you need in place so that everyone remains highly effective. What works well for a team of ten engineers falls short once you have thirty. You adapt and then feel some friction again when you get to a hundred. Rinse and repeat. At Intercom we’ve iterated and been through this process a few times having grown engineering from one team of four engineers sitting together in the same room to 160 people in 30 teams across three countries and two time-zones.

I’ll share how we’ve been successful at empowering engineers to drive organizational change. Their uniquely positioned being the vast majority of the org and at the same time closest to some problems. This allows them to identify, solve and own solutions to the challenges they face. When is it important to iterate? How do you identify when you've outgrown your current setup? How do you set yourself, and the org, up for success? This talk should give you some ideas and answers to these and apply them to existing or future problems your teams might face.

Level up your code reviews
Level up your code reviews
Software estimation - embracing nuance and controlled chaos
Software estimation - embracing nuance and controlled chaos