Zeb Evans

Yep.

And then you have engineers.

So depending on the feature, maybe it's more backend heavy.

So you'll have four just backend engineers.

If it's front end, you'll have a mixture between those.

And then you'll have a designer that's kind of tied to that team, which we don't actually count as part of that team.

So that'd be a plus one in addition to that because designers have multiple themes.

And so that's what has allowed us to scale EPD engineering product and design is really

building these hyper-focused teams that are focused on very, very specialized pieces of our product.

And product growth is one of those teams.

Yeah.

So our Docs product is actually one of our larger ones.

I think it's 12 people.

So it's kind of an abnormality there, but it is a big piece of our product.

And so we have a real-time collaboration.

There's two people working on real-time collaboration.

So if you picture any doc where you can see somebody's cursor and typing, that stuff is very complicated to make great.

And so we have two people that are fully focused on that.

And then within that, the rest of that team got five or so front-end engineers and three or four back-end engineers.

And then you, of course, got our PM, a product manager, and you got an engineering manager there as well.