<story><title>Yelp lays off 1000, furloughs 1100</title><url>https://blog.yelp.com/2020/04/planning-for-yelps-future</url></story><parent_chain><item><author>013a</author><text>Yelp&amp;#x27;s engineering isn&amp;#x27;t likely much more than ~150 people (I worked there ~2 years ago, maybe has grown since then but honestly, given their revenue situation even then, likely not by much). The mix there is just like most companies; you&amp;#x27;ve got dedicated teams for each of their apps (which includes Android, iOS, web, business-facing, etc), you&amp;#x27;ve got API teams, back office teams working on moving data around and business analytics, a very secretive abuse management team, IT, etc. Yelp also, given their age, wasn&amp;#x27;t (at some point) running their primary workloads in the cloud; they had (have?) a colo DC in San Francisco that hosted a ton of stuff, so there were people dedicated to that hardware. There was some movement to get rid of this as I remember.&lt;p&gt;Surprisingly, or hopefully not, the vast majority of the company is more directly revenue generating; sales and customer acquisition. Its spread very globally; at least as of a few years ago, the SF HQ didn&amp;#x27;t house any sales people, though I think they had an office in Oakland which did.&lt;p&gt;Point being, I always got the impression that their engineering team was very &amp;quot;right sized&amp;quot; given their revenue and product scope.</text></item><item><author>Waterluvian</author><text>I know this is a very tired topic, but does anyone have any good blog posts or articles about &amp;quot;what exactly is it that you all do?&amp;quot;  Yelp having 6000 employees. I&amp;#x27;m not surprised, I&amp;#x27;m not mad. I just want to understand.</text></item></parent_chain><comment><author>firstfewshells</author><text>I think you&amp;#x27;re way off. I interviewed with them last year and the number I got from them was close to 850 engineers globally.</text></comment>
<story><title>Yelp lays off 1000, furloughs 1100</title><url>https://blog.yelp.com/2020/04/planning-for-yelps-future</url></story><parent_chain><item><author>013a</author><text>Yelp&amp;#x27;s engineering isn&amp;#x27;t likely much more than ~150 people (I worked there ~2 years ago, maybe has grown since then but honestly, given their revenue situation even then, likely not by much). The mix there is just like most companies; you&amp;#x27;ve got dedicated teams for each of their apps (which includes Android, iOS, web, business-facing, etc), you&amp;#x27;ve got API teams, back office teams working on moving data around and business analytics, a very secretive abuse management team, IT, etc. Yelp also, given their age, wasn&amp;#x27;t (at some point) running their primary workloads in the cloud; they had (have?) a colo DC in San Francisco that hosted a ton of stuff, so there were people dedicated to that hardware. There was some movement to get rid of this as I remember.&lt;p&gt;Surprisingly, or hopefully not, the vast majority of the company is more directly revenue generating; sales and customer acquisition. Its spread very globally; at least as of a few years ago, the SF HQ didn&amp;#x27;t house any sales people, though I think they had an office in Oakland which did.&lt;p&gt;Point being, I always got the impression that their engineering team was very &amp;quot;right sized&amp;quot; given their revenue and product scope.</text></item><item><author>Waterluvian</author><text>I know this is a very tired topic, but does anyone have any good blog posts or articles about &amp;quot;what exactly is it that you all do?&amp;quot;  Yelp having 6000 employees. I&amp;#x27;m not surprised, I&amp;#x27;m not mad. I just want to understand.</text></item></parent_chain><comment><author>derwiki</author><text>I think your 150 estimate is very low— we had 80 eng when I left, nine years ago.</text></comment>