ADDED: I'm sorry, but the people on this thread who are arguing that if you can't get a $200K+ job at Google, you're obviously not even trying have some serious blinders on.
People who have waltzed into a high paying job at Apple or Google by sending them a resume believe exactly this.
It’s one of the many problems with any sort of unsolicited financial/job seeking advice. Actually the problem with advice of any sort. It’s almost 100% wrong.
During the dot-com bubble bursting, my company was having big layoffs and I landed a new job based on an informal lunch meeting with someone I knew that I had literally a couple of days after being laid off. (Some other leads I was investigating in parallel prior to getting an offer produced not so much as a nibble.)
Then, probably only a month of so before that employer shut down (somewhat after but somewhat related to the 2008 downturn), I contacted someone I knew at another company--which resulted in an offer and I'm still there.
But none of that provides much in the way of insights for someone else beyond a generic "have a network that knows you do good work and is in a position to hire you."
Which is an extremely important insight.
In my case, it basically boiled down to working a long time in the industry and having relationships with former co-workers, consultants who did work for us, and clients.
ADDED: Having said that, a lot of people think their resumes are all they need to land whatever job they want. And maybe that's true in some cases. But other than my first job in the tech industry--which I got out of grad school--every other position has been basically through people I knew and my resume was essentially irrelevant.
Seems random to be honest. Some of my interviewers have been older people. Some of the people waiting with me at lobbies prior to interview have been older people. I'm 38 FYI.
Seems your ability to pass the leetcode problems is the most important factor, so long as you don't torpedo yourself with odd behavior during the non-technical portions.
For more experienced candidates like yourself and I, I hear the system design round is also important. But your success in that is more difficult to gauge, whereas you kind of know whether you bombed an leetcode round or not.
Depressing is that your multiple decades of experience might be absolutely worthless as far as passing leetcode rounds go. Your experience may or may not be useful for the system design round. It's useful if your experience with systems matches that with what the company is looking for. It's useless if not. I've noticed the systems at many non-tech enterprise companies don't exactly align with the systems at newer tech companies.
Then again, I'm not entry level (10 yoe), so I might be competing at a higher bar. However, I'd gladly join any of these companies as a junior engineer without hesitation.
I've seen stories of, amongst others, someone who studied while in prison get into GOOG, someone who was a aesthetician get into NFLX, a cab driver who got into UBER, all as SWEs.
I actually wish I wasn't a SWE so I could compete at the entry/junior level. I feel my 10yoe (SWE at investment bank), which gives me a TC only slightly higher than a FAANG junior SWE, is wasted.
A buddy and I provide all kinds of practice interviews to help engineers get into FAANGs. We work on a success based payment model, and help substantially with negotiations, too.
If you're interested send me a note with availability for a chat (email and website in profile). I would love to at least offer some advice for next time even you decide our coaching is not for you.
This is all assuming you can get past the resume filter which is all luck unless you know someone with enough pull within the company already.
Of course, in this case specifically, it might be because they worked for 10 years in an investment bank, and might be used to always speaking about companies in terms of stocks.
- TC trajectory would be significantly higher, even if it means taking a minor temporary paycut.
- Intangibles, which might sound trivial, but stuff like working with smart coworkers, not having to dress up like a businessman to work, etc.
I've got close to 20 years of programming experience, including working at Google for several years and launching some very high-profile projects. I still fail interviews if I haven't studied for them. You could argue that it's a stupid system where they test 20-minute coding exercises with a trick answer, and you'd be right [1]. But it's a system that can be gamed, and can be gamed with relatively little time. Putting in a week full-time, or working a problem a day for 3 months, will put you way ahead of most of the rest of the competition.
[1] But the interview bullshit serves another less-obvious purpose: it tests how much you actually want to work at the organization. It's relatively easy to bullshit enthusiasm in a calm chat with a hiring manager. It's pretty hard to do it when your brain is occupied by solving a hard problem and you're frustrated because you have 5 minutes left to solve a problem and there's still a sticky bug.
Add to that, since last year, my day job got a lot less demanding, so I am actually studying/leetcoding during the afternoon at work too.
One wrench thrown into the loop is that I am a mainly a frontend engineer by trade, and it seems frontend interviews at FAANG and many other top tech companies are focusing less on leetcode/DS&A and more on JavaScript trivia problems. So that has been a context shift, and I am focusing more on getting as many JavaScript tricks and patterns into my repertoire now, and less on leetcode.
Pretty much my #1 personal goal in life at the moment is to get into a FAANG, or at least similar caliber, company. No, it's not a life or death matter, but whereas someone else might be content to watch TV/Netflix, or play games, or go golfing, I'm spending that time leetcoding...
What I feel torpedoes me during the interview is that I can get often get 90%+ of a solution, even if it's a problem I haven't seen before. But some edge case or bug in my code kills me, or I miss some trick or pattern that is the key to getting it right. In a less competitive company, this might mean passing the interview, but for a FAANG or similarly highly competitive company, I feel not getting 100% technical perfection means dead on arrival.
I started as a frontend engineer at Google, 11+ years ago, and you're right that there's a lot of Javascript/DOM/HTML trivia to understand. Google was also one of the few companies that insisted you know vanilla JS cold and don't use frameworks in the interview. It's worth studying up on MDN to make sure you really know JS corner cases. You need to know the leetcode-style problems too - when I applied (and I think this is still true), it was 2 interviews for algorithms & data structures, 2 for frontend, and 1 system design.
It also may not be the right time to apply, since many FAANGs are dramatically slowing down hiring. Your odds get much better in boom times than bust times.
Also got rejected from AMZN back in December. Made the mistake grinding leetcode during the weeks leading up to the interview, when it turned out to be purely JS trivia.
The hardest part of interviewing as FEE seems to be the lack of sample JS interview problems available, versus say, leetcode. I feel I am pretty well versed in using JS and have pretty in-depth knowledge of the arcane workings of the language far beyond a typical developer (certainly more so than my coworkers), but just like how leetcode interviews cover cases you'll never encounter in day to day work, frontend JS interview problems seem to do the same.
That said, I don't know how much JS knowledge a typical FEE at a FAANG or similar company has. But that's one big reason I want to get into one of these companies - I'm assuming, and hoping, the level of knowledge and enthusiasm (I hate to use the word passion) is much higher at SV tech companies than outside. Most of the places I've worked (banks, finance), the JS engineers can barely explain how async stuff works in JS.
I'm kind of in the same boat. I failed all my interviews as well and I have about the same amount of experience as you. I agree that getting into these companies is easier as a junior engineer.
You may want to look at an interview prep course like Outco.io or Interview Kickstart. I haven't attended one yet but will most likely do so once I'm ready to start interviewing again. I think the feedback they offer will be worth it rather than me constantly headscratching after failing another interview.
(The fact that these courses exist just exemplifies the whole problem with software interviewing but I don't fault them for that)
For example, in my failed FB interview above, I quickly and successfully solved two problems in the phone screen - thus I passed. The first onsite (virtual) coding round I struggled on the first problem but got it with about 10 minutes to spare. Main issue was that the optimal solution involved doing something in JavaScript that AFAIK typically considered bad practice. The second problem I waltzed through in 5 minutes. The second coding round I got the first problem, but there was an edge case bug I didn't catch, and fixing that took up the entire 45 minutes so I didn't get to a second problem. I'm guessing that was a big negative signal.
I know communication goes a long way, but considering how competitive these positions are at FAANG level companies, I'm sure there is someone else out there that communicates and vibes just as well as I do in addition to getting the 100% optimal solution quickly.
The one thing I can see a service like IK offering me is networks and referrals, but not sure how much that would be worth, especially since they aren't exactly cheap. That said, I'd pay the tuition without hesitation if they could guarantee me a job (of any level) at a FAANG level company, but that's not the case :). Or at least a 100% refund if I fail to get into such a company after a period following the curriculum - but I feel that's easier promised than done even if they were to offer such.
I have friends at some of these companies who have given me referrals, but ultimately all that does is give me higher odds of getting an interview, and in some cases, a chance to directly chat with the hiring manager prior to the interview. For whatever it's worth I've had managers express great enthusiasm about having someone like me on their team after a conversation, but then I get torpedoed for not being able to find the perfectly optimal solutions to some leetcode medium/hard.
Yeah, referrals at these sized companies only help to get a recruiter to pay attention. It doesn't really help. I've even gotten interviews just by searching LinkedIn for ___ recruiter and messaging them directly.
FWIW, I recently attended the Outco sales pitch and they do have a almost guaranteed payment option. Instead of paying up front you can pay nothing and then pay 10% of your first year's base salary. Obviously that would cost you more than if you had paid up front but that could be an option.
One other thing that did make me hesitate Interview Kickstart though were that they seemed to be for generalist SWE only, not frontend. The person I spoke with said FEE would have the same interview problems/track as any other SWE, but my personal experience over the past two years has shown me this is usually not the case.
Also would be concerned about what IK/Outco considers a "success". I'm only targeting a relatively small subset of companies (FAANG, obviously, plus others at similar level). So my definition of success (aforementioned companies) vs. theirs (any company?) might be different. A question to ask during the info session I suppose.
People who say it's easy are arguing from an optimistic point of view specifically addressed as unhelpful at the start of the article.
Do we seriously believe there are so many FAANG jobs available that "any reasonably good programmer" who wants one can have one, just for the price of a bit of "serious study"? I don't think so. Google et al may be big, but they're not that big or growing that fast.
A great deal of the demand for engineers does not come with anything like FAANG-level prospects.
For every junior FAANG engineer, there are legions of senior or staff level equivalent engineers at companies outside of the Silicon Valley style tech/software sector who will retire with their TC topping out at maybe around what a lower-mid level engineer at a mid-top tech company would make.