> Unfortunately when it comes to preparing for interview leetcode is pretty much required at all stages.
I have never had a leetcode-style interview in 40 years. (I may have had one such question, maybe - hard to remember for sure.) So, no, it is not required at all stages.
Disclaimer: I'm in embedded systems, which is very different from FAANG.
We normally do minor fizz buzz code screens internally. But that's just a small test to see how much of the tech you know, like if you were switching from say Python Lambdas to Angular front-end. And it's mostly to see about how you approach the problem.
But some of the internal postions do it differently. My favorite was a mock code review on a PR that had intentional flaws. Then you'd call put what was wrong and how to fix it - not just pure code but also requirements, tests, commit messages, etc.
LeetCode is different though. The rating and stuff. Even the interface... I still don't know what it's doing behind the scenes to run the code and feed inputs and what those inputs are. Believe it or not, this LeetCode interview wasn't my worst internal code screen. I once had one that HR said to bring my laptop and use any language I wanted. When I got there, the manager handed me a Mac (which I've never used), told me to use Angular to create a page with a table (hadn't used Angular at that point), and told me to do it in Webstorm (most teams were still using Eclipse at that time, so no experience here either). I managed to Google my way to a working table, but cut the interview short when he wanted me to style it. It's and internal posting. I clearly know the basics and got something working, even in the worst possible interview scenario where I didn't know the tools at all. Surely I can learn the rest (this was a midlevel posting, not even senior).
I'd interpret that as they wanted actual usable work from the interview,
I've had a few of those "technical tests" that boiled down to "if we get enough applicants to add to this code we won't need to hire any of them"
You can be assured that the person who actually got the job worked on a Mac in Angular using Webstorm and that nobody wants to entertain ideas that their methods of interviewing are in any way tipping the scales.
On the opposite side, I usually skip teams for their repo so I can review them. Are there test cases built out? Do they have east to follow code design, or descriptive comments? Do they have a normal level of abstraction, or are there multiple layers of interfaces for not real reason? I recently declined a position because the team was building a UI, didn't have a CMS, didn't have any real rests, and the code looked like a bit of a mess. It didn't help that the languages (Go, React) were completely new to me, so I wouldn't be able to make an impact on improving these issues.
I’ve run into a leetcode once over the course of five job hunts. There’s always some sort of screener that may use a leetcode style interface, but the problem is something like fizzbuzz/write a function to say if a number is prime/etc.
The interview is about finding the obvious resume frauds and seeing if they can communicate their problem solving process, not finding a genius that’ll invent new algorithms
I'm with you and the GP, but I suspect all three of us have pursued a balanced and satisfying career instead of the one with top of market compensation.
Some of the folks here don't see alternative options when FAANG compensation is some integer multiple of what the rest of the industry has been supporting for the last 40+ years, and I don't entirely blame them for that. I'm not surprised when some later find themselves miserable and feel like they're trapped by golden handcuffs and insufferable bureaucracy, but I understand how they got there.
Yes, I’ve been in tech for 30+ years and just recently broke 6 figures in salary. But I live where a nice house is under $300K and I take satisfaction in living frugally.
Webdev in various stacks, database design, programming and administration, linux administration. Mostly in higher ed with a few forays into short-lived startups.
As someone currently in the process of trying to move from a cushy, interesting startup job to a soulless FAANG for that compensation multiple, the ONLY reason I'm doing it is because I have a young kid now. I wish there was another way, but it is genuinely impossible to provide a comfortable level of family life on a startup salary, unless your partner is also in tech and is ok with not being a stay at home parent.
> I wish there was another way, but it is genuinely impossible to provide a comfortable level of family life
It's all a matter of perspective, isn't it? It's basically the top 1% speaking. And you can't tell me that the other 99% have miserable lives.
> unless your partner is also in tech and is ok with not being a stay at home parent.
Stay at home parent is a choice, and a pretty expensive one. One does not have to choose that and can still live a comfortable life. Many women (and let's face it, we're unlikely discussing the man staying at home for the next 7-15 years, eh?) even prefer not to interrupt and/or basically end their careers because of parenthood.
Americans often look to Europe, claiming that these things are so much easier there, which might be true, but at least as much is it a matter of personal choice as well.
Can confirm that the 99% have very comfortable family lives, lower stress jobs, plenty family time... (based on having many lower income friends) Bottom n% is a different story, but a FANG salary is not a necessity unless your lifestyle choices and personal expectations make it so.
I'm guessing those lower income folks either don't live in HCOL locations or were fortunate enough to buy their homes before the pandemic. My family is all in HCOL, so with a young kid it's not really feasible to move away (or to go back in time and get a better deal on the house).
Yes, to some extent the asinine expenses of people like me are a result of various choices we made, but that's assuming those choices had any really realistic alternative at the time. And now I'm stuck.
There are other companies, too. I work at, statistically speaking, Your Phone Company, and they don't pay FAANG money but they certainly pay a lot better than I was doing at startups.
Caveat: I don't live in the Bay Area, though the Boston area isn't exactly cheap.
Thanks! It's an interesting place, and I think the technical quality depends pretty heavily on what org you're in. But the quality-of-life is very high and I'm mostly enjoying myself.
I have never had a leetcode-style interview in 40 years. (I may have had one such question, maybe - hard to remember for sure.) So, no, it is not required at all stages.
Disclaimer: I'm in embedded systems, which is very different from FAANG.