That's why I am genuinely curious what they plan to do once they hire teams. Let's say you hire a team of a designer and a developer. It's not like they will be always working together and with no one else in the company. Chances are you won't be working as the tag team forever. That would be stupid both for the company and for these people because you are being too closed minded and won't learn much by only interacting with the other person when there are so many other talented people in the company. I presume that isn't what they plan to do. Then that leaves us with the option of just hiring them "as a team" but once they're in, there's no guarantee that they will work as the same team, just like how most acquisitions work--when they acquire a company they say stuff like "Company A's expertise will be helpful in us developing our such and such core features", but after the acquisition they all disperse and get assigned to different teams after a while.
So... what's the point? Well that's why I think it's a gimmicky way to attract attention and get more people to apply. Any counter argument?