> 30-50% of engineers on core teams have been forcefully reassigned to data labeling and RLHF, upsetting folks even more. This really doesn't sound believable to me, but who knows with all the craziness going on. Software developers in the US are seriously expensive, using them for data labeling would be a waste of resources. And the percentage sounds very high, unless "core teams" is only a small subset of the total…
Is Meta destroying its engineering organization?
431–440 of 655 posts
Re: Is Meta destroying its engineering organization?
#432> I talked with several engineers in infra orgs, who had 30-50% of their teams drafted into the ADO org. And in some cases, it was the best engineers who left.
> On Tuesday, Meta’s Chief Information and Security Officer (CISO), Guy Rosen, announced his departure.
This Guy was here since 2013, after his mobile tracking app Onavo was acquired, VP of Trust & Safety / Integrity during the high-stakes times of the Cambridge Analytica scandal, handling platform abuse and election interference during a very "yuge" election cycle.
With that goes the accumulated ethics, philosophy, and tribal knowledge that drives organizational cybersecurity and risk, 3 very important factors that can't be automated away or even openly spoken about. This sounds like a massive change to decision making that is larger than engineering.
Re: Is Meta destroying its engineering organization?
#433This sounds bad to say, but it's difficult to feel bad for any meta engineers who lost their jobs. You undoubtedly had other options, yet you chose to work for one of the most well-documented do-bad-for-the-world organizations on the planet. Former employees will deflect and make the comparison to United Fruit workers, despite the obvious difference in employee-optionality and influence. You made your bed. I hope you…
Id honestly wager that at you and most of the people who are agreeing with you in the comments don't make the meta SDE salary, and if offered the 300k/year positions at Meta, even for a limited time, you would absolutely take it And you would be stupid not to. One one hand, you can be that guy that says you declined a Meta job, and be stuck at your current salary level, watching people make more money around you, and…
Re: Is Meta destroying its engineering organization?
#434Earlier quoted context omitted.
I had a similar experience at Google, they were so convinced they were the only good engineering company in the world and had to protect themselves from all the wrong-thinkers outside and yet the only progress they made was via acquisitions.
You'd say that Google Maps hasn't improved much in the last 20 years?
I had a Keyhole account long before Google was in the business, and it worked about like Google Earth does now.
Re: Is Meta destroying its engineering organization?
#435Having worked at meta, something I noticed is that the orgs that were well run were ones that were bought. WhatsApp, reality, insta, etc. I worked in an org that was not associated with those products and was purely homegrown and it was awful. Things got done but horribly inefficiently due to over hiring and extreme requirement and schedule shifts. I believe that the cultures that were developed outside of Meta are u…
WhatsApp was a textbook example of how not to do an acquisition. The story I heard was when it was acquired, a spreadsheet went around and everyone basically decided what level they were in the (then) FB job ladder and all the engineers said they were E7s (Senior Staff SWE). The way PSC worked, WhatsApp at the time was only ever calibrated against themselves (from what I heard). It had become a fiefdom and, as someone who was on a team that tried to get them to do anything, the experience was awful.
IG was handled better but it was also an almost nonexistent team when acquired, which might well explain it. They stuck with their Django/Python codebase and (IMHO) that was a mistake. The amount of duplication that we had to do for IG specifically was embarrasing. The framework and tooling FB had on the product side was light years ahead of what IG had. IG used to have a very good product focus but I think that's long dead now. It was good because IG had a clear vision for their app and ultimately (IMHO) management had a different view to "grow". They briefly tried to launch another app (IGTV) that flopped, hard. There were a bunch of UI/UX changes that clearly showed the focus had become simply following celebrities instead of sharing updates (eg where the post/compose buttons moved to).
I mention Google because I saw the same things happen at Google.
Youtube was (and my guess is, still is) its own entity. Culturally, Youtubers don't see themselves as Googlers. They didn't (AFAIK) use Google3 or any of the other stuff most of the rest of Google did. But Youtube itself was perceived very positively, technically, particularly in relation just general encoding/decoding infrastructure as well as Bandaid (where racks are shipped to ISPs to cache videos).
Android was another acquisition that prided itself in not being Google. This was very much fostered by Andy Rubin while he was still there. Obviously Google needed to write Android apps but I got the sense that it was always Google engineers who solved all the problems whereas Android just didn't care. They cared only about shipping Android. Fuchsia was an Android offshoot.
Docs and Maps were both acquisitions but they went fully Google3 and were different orgs but weren't seen as separate. The engineering director of Docs (Fuzzy) had, from what I can recall, a very positive reputation beyond Docs (now Drive).
Doubleclick was also an acqusition but went fully Google and you'll find a lot of people who don't even know it was an acquisition.
I don't know what org you worked in but they all vary. My own experience was that Infra orgs in comparison to Google were primitive and barely above just running random Docker-like (Tupperware) instances with a godawful variant of C++, probably started by someone who had done C++ at Google and had decided they really wanted mutable function parameters and exceptions for no particular reason.
The thing I really respected about FB product orgs generally was that really did ship things quickly. I used to joke that the smallest unit of time at Google was a quarter. God help you if you eneded another team (under a different VP) to do something. You'd have to spend a quarter arguing with them to get them to add it to their OKRs for the following quarter.
At FB the timeline for launching a new thing to a limited audience was measured in weeks. The biggest barrier usually was the weekly build cycle for the blue app. The release cycle for Web was S-tier and (IMHO) the people who worked on the infra for Web were generally god tier. This was another reason why IG doggedly sticking with Python just created problems.
There are many thigns you can criticize Meta for (eg the stupid crypto, the billions wasted on VR) but the Web Foundation and Ent teams were god tier and I'll die on that hill.
Anyway, even back then the ML teams and infra, not to put too fine a point on it, sucked (IMHO). Newsfeed was OK but the recommendations for a lot of things like videos just sucked. All of this was mainly because it all relied on daily offline jobs. And then Tiktok came along and showed everybody (including Youtube) just what a bad job they were doing at recommendations. And don't get me started on the IG Reels dumpster fire.
Oh ok, I thought of another one: Messenger. I knew some smart people on Messenger but overall the product and the infra were, again, a dumpster fire.
Re: Is Meta destroying its engineering organization?
#436Earlier quoted context omitted.
Where do you draw the line? You're a TVC in the kitchen at Meta? All you do is give girls depression? You work at a business that buys ads on Meta? Is all you do is give girls depression? Even if you work in a non-profit branch specifically to do out-reach for kids or something?? How far separated from Meta do you have to be to not be reduced to doing nothing but giving girls depression?
It requires discernment, to be sure. The Principle of Double Effect[0] is essential in such cases, because it helps determine when cooperation with evil is remote or proximate, and when such cooperation with evil is morally permissible. [0] https://plato.stanford.edu/entries/double-effect/
It's interesting how easy it is to define exactly how evil Facebook is and categorize each worker on an evil spectrum based on job title alone.
Who would have thought life was that simple!
Re: Is Meta destroying its engineering organization?
#437Earlier quoted context omitted.
It seems really dumb to tell them that. I assume they’re all feeding garbage to the models now.
They’ve largely filtered their employees for people who have a mental breakdown if they don’t get 110% on a 100% scale or get the top of the top rating because they’ve done that their whole life until they got their first job at the tender age of 25-28 after getting their masters or PhD. I’ve met too many meta members who have stories about their direct reports or peers who had a crashout because they got Exceeds Exp…
Seems like a side effect of the k shaped economy... our society increasingly doesn't have rewards for normal hardworking people. Given tech has been disrupting blue collar jobs for decades I have a hard time feeling sorry for them. Working at Meta already meant you were chasing a bag knowing the product was more or less social poison anyway. It doesn't seem to me that Zuck is uniquely culpable... maybe he's just the best one at the game they're all playing...
The fact he still cares so much about Meta when he is a billionaire is just like those crashouts. Again, it's the same type of person. He's just better at it than they are.
Re: Is Meta destroying its engineering organization?
#438Earlier quoted context omitted.
As I learned while burning through all my savings in the 2023-2024 timeframe: You are free to have principles, but principles aren't free. I am ashamed I worked there.
If you worked at Meta and couldn't find a job for a year, its not because of Meta.
Re: Is Meta destroying its engineering organization?
#439Earlier quoted context omitted.
As I learned while burning through all my savings in the 2023-2024 timeframe: You are free to have principles, but principles aren't free. I am ashamed I worked there.
That’s a choice. This isn’t a story about someone poor who needs to work at McDonalds to make ends meet to feed their family. We are talking about the top earners in the world who made a decision to make more money than working at a competitor (Google/Apple/Microsoft/etc) where they would still be in the top 1% of earners.