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.
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.
Caveat: I don't live in the Bay Area, though the Boston area isn't exactly cheap.
To my pleasant surprise, the HFT is more rewarding (not just in comp) than the FAANG was. At least for now, or that's what I keep telling myself.
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.
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.
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
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).
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 also have a hunch I've gotten easier coding questions when an existing team member referred me to hiring for their own team.