6 ms·
Have you actually worked at a FAANG?
by mangosteenjuice 4y ago
Have you actually worked at a FAANG?
- novok 4y agoYes for many years, and I have many other friends that do so too. Just recently left to work even harder at a small place and I got promoted past sr eng. The hardest part about FAANG is the fucking leetcode when you change jobs. IMO working at a FAANG is the most optimal place to be if you want to put on the slippers, have a good work life balance and get paid the most.
- fnordpiglet 4y agoHence the layoffs
- jacurtis 4y agoYeah I never understood the whole leetcode between positions, even lateral moves that you choose for culture or personal interest reason required another leetcode. I swear it was just there as a dis-incentive to keep people from moving. Do all FAANGs do this? Or did we just happen to work at the same one?
- zem 4y agogoogle doesn't, as far as I know; changing teams has just required talking to the manager and a couple of engineers from the new team to make a case for them taking me on. so interviewing of a sort, but not the leetcode rituals that getting hired in the first place needed.
- ornornor 4y agoWait what? You’re saying for people who already went through the leetcode hazing to join the company, they have to do it all over again for internal promotions? That’s absurd, I had no idea. Isn’t the “rationale” for leetcode that they dont know you and as far as they can tell, you copy pasted all your open source code from SO, so there is no other way to prove that you can actually write code than to take a leetcode? But if you’re already working there, couldn’t you (bear with me because this is a little crazy) just point in the general direction of the code you’ve worked on at said org and ask your colleagues or manager for their opinion on how much of that was copy pasted from the internet?
- novok 4y agoNo when you change jobs externally lol. Internal moves are pretty easy.
- ornornor 4y agoThat’s a little less absurd even though leetcode is a waste of time. FWIW, I typically decline code challenges. I have ample open source code that’s commented, publicly visible, and tested. I’ll sometimes humor them if I like the team and it really takes an hour or less to complete (note that when they say an hour it really means 4–8h, so I assess it myself). But otherwise, I point at my open source code, offer to pair on a feature/bug on these OSS projects, or drop out of the pipeline if it’s not acceptable to them. Same with quoting a salary number or salary history: if they ask I decline to answer and if “the software won’t let me continue without” I offer to fix their software and drop out of the pipeline if “tbd” or “1” won’t work.
- UncleMeat 4y agoI work at Google. I work fully remote. I rarely work past 5pm. I have worked on a weekend I think one time in 10 years. I have had one "urgent problem, VP on the phone" situation in 10 years. I happily take off time in the middle of the day to handle various errands (vet appointments, etc). "I will have the time and energy to make dinner for my family every single day" was one of the first things I mentioned to my manager upon joining. All this despite managing a team and being the final escalation point for a fairly critical system.