8 ms·
It's a classic case of hire engineers first and figure out problems to solve later. This works great if the company already has a massive revenue stream (Google
by paxys 7y ago
It's a classic case of hire engineers first and figure out problems to solve later. This works great if the company already has a massive revenue stream (Google, Facebook etc.) so the engineers can just mess around and once in a while come up with something great. For a company losing $2B+ a year, not so much.
Once WeWork solved its core engineering problems (bookings), engineering job descriptions got more and more abstract - "build the operating system for the workspace", "bridge the gap between physical and digital", "create a sense of community", "humanize through technology" (all copied directly from their engineering website), so it's clear that they are paying thousands of engineers to do nothing.
I know for a fact that they have large data and machine learning teams spread across SF, NYC, Tel Aviv, Shanghai and maybe more that collect and analyze data from all their operations - few hundred offices and few hundred thousand members. At this scale there is zero reason not to use off-the-shelf products (or pay one of the dozens of companies out there that specialize in this), but they decided to custom build all the infra in-house from scratch.
- ethbro 7y ago> I know for a fact that they have large data and machine learning teams spread across SF, NYC, Tel Aviv, Shanghai and maybe more That's going to be an awkward presentation to management when they present their revenue forecasts under different economic scenarios...
- deleted 7y ago[deleted]
- mrgreenfur 7y agoMaybe they are using all those ML teams to build "self driving offices" (a la uber) or Self-greeting receiption? or predictive room bookings