Live data from Hacker News

A Senior Engineer’s Guide to FAANG Interviews

interviewing.io

41–50 of 195 posts

Re: A Senior Engineer’s Guide to FAANG Interviews

#42
post #9

I don't know, I've walked into these interviews with zero preparation and succeeded. And I've failed FAANG-ish interviews where no amount of leetcode grinding would have helped me. In my opinion, it's getting rather silly. They're scaring off and filtering out excellent candidates with these excessive processes. None of them even cared about my Github repository that's full of code I write for fun. Software developer…

The Product Manager interviews are even worse. Google was the shittiest experience I had, all the way to the silly hiring Committee. Three months of my life I'll never get back.

Re: A Senior Engineer’s Guide to FAANG Interviews

#44

All of the FAANGs are various levels of unethical, or a net negative for society in my estimation. No more interviewing there for me.

Is the company you are working for using any of the cloud providers? Are you using computers built by low wage workers? Do you use Amazon? Google? Microsoft?

Or does it make you feel better that you aren’t working for them directly?

Re: A Senior Engineer’s Guide to FAANG Interviews

#45
post #15

Just a heads up to anybody super starry-eyed about fang, I worked 10+ years non-fang, and tried fang, and it was absolutely miserable, one of my least favorite jobs of my career. Yes I made a lot, but I also worked and stressed proportionally more. YMMV.

>> Just a heads up to anybody super starry-eyed about fang, I worked 10+ years non-fang, and tried fang, and it was absolutely miserable, one of my least favorite jobs of my career. Most people I know say the same, but they stay. You can be at a non-FAANG and work for half the pay (and often be just as miserable) or you can work at FAANG, own a house, not worry about money, and often do not much work. Misery is part…

> Misery is part of the package.

But isn't that a bug? It's not that hard to find a non-FAANG job that pays well, lets you own a house, and not worry about money without having every working day be a misery.

Re: A Senior Engineer’s Guide to FAANG Interviews

#46
post #20
post #9

I don't know, I've walked into these interviews with zero preparation and succeeded. And I've failed FAANG-ish interviews where no amount of leetcode grinding would have helped me. In my opinion, it's getting rather silly. They're scaring off and filtering out excellent candidates with these excessive processes. None of them even cared about my Github repository that's full of code I write for fun. Software developer…

All jobs I applied for that I interviewed for looked at my GitHub specifically, and my past projects, and that was their main topic of discussion in the interview, apart from usual coding questions and such. Im not victim blaming by saying you may just be applying to the wrong places, am I

Unfortunately this also means you have to be open to a potential 50% cut in TC as well.

Personally, I find enjoying the 8+ hours I spend at work each day more important than raw TC, so have made the tradeoff (and still have a reasonably high TC) which works for me.

That said, I would love a more laid back research programming job in academia, but that requires an additional 50% cut from where I am now.

It's still understandably frustrating that knowing how to write software seems largely irrelevant to getting a job at a FAANG.

Re: A Senior Engineer’s Guide to FAANG Interviews

#47
post #9

I don't know, I've walked into these interviews with zero preparation and succeeded. And I've failed FAANG-ish interviews where no amount of leetcode grinding would have helped me. In my opinion, it's getting rather silly. They're scaring off and filtering out excellent candidates with these excessive processes. None of them even cared about my Github repository that's full of code I write for fun. Software developer…

FAANGs can get literally over a million job applications per year. Any procedure that filters that down to roughly the number of people that they plan to hire (a few 10k) is also going to filter out some excellent candidates, no way around it.

Re: A Senior Engineer’s Guide to FAANG Interviews

#49
post #40

Earlier quoted context omitted.

Not a recruiter, but I imagine there are at least 3 reasons for your repo to be ignored or deprioritized in favor of typical interview: - not everyone contributes to OSS - it’s easy to fake - it’s hard to assess within a short period of time This it seems to be hard to standardize and streamline candidates validation based on their oss repos. Also, afaik the goal of interview is to assess candidates thinking patterns…

Sure, it would take some more effort to dig into than checking boxes. But it would also provide more valuable feedback.

How would you compare candidates that have some code in GitHub and those that don't ?
Post reply on HN