<aside> 💡 We expect S&O Team Members to take ownership of problems. These problems range from sets of underperforming markets to leading functional teams or building new lines of business. Our S&O team sits within the product team, and our proximity to the product team allows us to understand and solve problems locally before deploying productized solutions globally.
These solutions can be delivered by working with an ops team, working with a PM, or grabbing an engineering team and acting as a PM. S&O team members stay flexible, because no matter what form our path forward takes, it’s the S&O team’s responsibility to do what’s necessary to solve problems.
</aside>
Strategy and Operations team members typically interact across several cross-functional teams. Most problems that the team handles fall into these buckets:
No matter what a member of the team is tasked with, everyone is expected to dive into the numbers and speak directly with our customers to implement solutions that will improve our marketplace. By design, the S&O team has a lot of freedom to move and is focused on the most important customer problems; members of the team are encouraged to pick up threads all over the business rather than in one specific focus area.
<aside> ✏️ Read the full doc on our group organization here
</aside>
Our product/engineering/strategy teams are structured into various groups oriented around a set of customer problems (“missions”). Those missions are not fixed or even exclusive; there might be times when multiple Groups are attacking the same problem. That’s both acceptable and (on the margin) expected.
A group is a cross-functional unit led by a Group Product Manager alongside one or more Engineering Managers and strategy team members.
These missions are not a collectively exhaustive list of what could be worked on, but simply what we’ve deemed to be the most important missions at this moment in time.
The product team and strategy & operations team work very closely together; we included writing from our product team as well because it provides valuable context regarding the kind of work you’d be doing here.