The path to success is frequently a winding one, and as a series A tech startup, m3ter is no exception. In just three and a half years, the company has undergone significant changes in its product and internal structure, adapting to shifting priorities and circumstances.

In this session, we'll look back at the different team topologies that m3ter has experienced, how it recognized signs of the need for organizational change, and how it responded to its own mistakes. While we'll mainly focus on the perspective of the Software Engineering teams, we'll also zoom out and consider how these changes affected m3ter's overall organizational structure.

The company has taken lessons from its Product side and applied them across other teams, streamlining processes and refining goals. In doing so, we’ve managed to cover a lot of ground with a very low headcount. 

These lessons are specific to m3ter's journey, but they offer insights into growing a company and developing teams. While they may not apply universally, there are certainly common principles that can be helpful across industries. Come see how we've handled it!