Live data from Hacker News

Facebook senior software engineer interview

daqo.medium.com

101–110 of 524 posts

Re: Facebook senior software engineer interview

#101
post #30

How can anyone work at Facebooks nowadays and have a clear conscience. Is it just the salary? It is, isn't it? Just money. How depressing.

Turns out you got to pay bills even if you are on a moral high horse. Besides if one has to have a clear conscience to match everyone's standard here, one should stop working at FAANG, stop using FAANG products, maybe stop using big oil products, stop using big pharma products, is it ok to pay taxes to a govt if you don't agree with something they did or should one pick up and move too? what else did I miss?

HN is so much of a echo chamber lately for some topics, there was a recent discussion about FB head of integrity leaving the company and the top comment and thread was a personal attack on the FB CEO's integrity without even understanding what an integrity team/dept does in these companies. I could just as well have been reading youtube comments. I see threads with some topics now and I can pretty much be sure to not expect to learn anything new or get a good discourse. Just people thinking they are better than others.

Re: Facebook senior software engineer interview

#102
post #61

Facebook is pure self-parody at this point. This post is tragic comedy with no practical value besides entertainment. Anyone pursuing job options following advice like this has a severe problem with lack of self-esteem and capacity for independent thought.

100%. There’s an assumption in articles like this that you even want to work for said FAANG company. Additionally, these posts assume a one-way interview process, which is a sure fire way to end up places you don’t want to be. Jump through all the hoops like a good little show pony, then maybe if you’re good enough, you get an offer and... what? Congrats, now you work for a terrible organization at a level where you’…

The comp offers aren’t even that great, even compared to midrange tech companies, especially for senior / staff level engineers.

I worked at a midrange ecommerce and content licensing firm, about 20-25 years old, in a major US city, and my total comp as a senior engineer (6 years of experience then) was in the range of $350k between salary, equity and bonus, and this was over a decade ago.

If you find a company that values you and needs your skills, you can get high comp at lots of places, and many have much better work / life balance, less wanton dysfunction and less political drama in the workplace.

Even a 50% or 100% increase over the $350k isn’t worth debasing myself with “dance monkey dance” whiteboard hazing. You might as well ask Facebook to give you a dunce cap on your first day, or a t-shirt that says, “My lack of self-respect is so severe that I agreed to do Facebook’s interview process.”

The mere fact that I’d actually be valued at the $350k place and wouldn’t be rectally probed to ensure I am fungible with every other assembly line programmer is a big indicator that my total earnings over a long time are likely to be much higher away from a place like Facebook. Generous scheduled equity refreshers are no match for actually rising in responsibility and skill growth to critical new positions in a firm.

Re: Facebook senior software engineer interview

#103
post #66
post #30

How can anyone work at Facebooks nowadays and have a clear conscience. Is it just the salary? It is, isn't it? Just money. How depressing.

I know multiple people that have taken jobs at Facebook in recent years that feel it is a net negative in the world but could not resist the paycheck and justify it by committing to either by work hard as user advocates from the inside, or just finding open source work that doesn't directly exploit users to drain their resources on. I for one have taken interviews at Facebook with 0 intention of working for them just…

So, they didn't make you an offer.

Re: Facebook senior software engineer interview

#104
post #25

CLRS is over 1000 very dense pages. I assume the author just did a fairly casual reading and didn't work through many problems. Even still, this is a full month of study just for the interview process, and little of this sticks unless you practice it. This basically says to me that big companies just want to hire new grads or people who have copious amounts of free time to waste on studying, or perhaps enough wealth…

> CLRS is over 1000 very dense pages.

CLRS is in fact over 1000 pages, but it's not very dense, quite the opposite. It goes in painstaking detail about every single minutia you could possibly be thinking of, often formally proving things that everyone with even a modicum of mathematical education should be able to independently come up with a proof for (white path theorem, anyone?).

All of that is great for beginners (there's a reason it's a standard textbooks), but I remember that even when I was in school I found it a little too verbose and used to prefer the Sedgewick.

With that said, I still agree that the author's timetable is very optimistic.

Re: Facebook senior software engineer interview

#105

Earlier quoted context omitted.

> Why is vaguely recalling an algorithm studied years prior and needing to look it up indicative of a poor candidate in an interview? The article does not imply that it does.

The article doesn’t but I think OP’s point was that relying on knowledge / algorithms designed and provided by others would mean an immediate fail in a FAANG interview, but it’s exactly what successful engineers do when employed at FAANGs.

And the reason is that you have to stand out from other candidates. If enough candidates do know algorithms on the whiteboard, then they can set the bar that high.

Re: Facebook senior software engineer interview

#106

Earlier quoted context omitted.

> I'd argue that points to a massive monoculture problem at Facebook, but I'm massively anti-Facebook so I'm biased. I'm pretty sure that's the point. Massive enterprises like Facebook have no need for creative "outside the box" thinking anymore. They need dependable, solid developers with a standardized skillset that they can plug into a position like lego blocks, easily replaced whenever they burnout or stop toeing…

>plug into a position like lego blocks Every time I hear someone from big tech talk about being a "L"-something (or in this blog they're "E" levels), I wonder if they know they sound exactly like the bureaucracy talk of the US Federal Government employees and their "GS" "E" or "O" levels.

For better or worse, when you get to a certain size you absolutely NEED that level of bureaucracy. You can't get 120,000 full time employees plus probably another 100,000 contractors to work together without establishing a clear hierarchy that everyone inside it understands. A smaller company can have different approaches because they will have a dense network of employee relationships, and can work together off of those relationships. However, at six figure employee scale by necessity you will end up with a very very sparse matrix of employee relationships, so you have to have something else to get results.

Re: Facebook senior software engineer interview

#107

Sad to see that FAANG is so attractive - sure, pay is nice, technical problems are nice - but you are actively working on walled gardens. You become a walled gardener.

I used to believe that when I was younger.

Now that I'm older, I'm understanding of people optimizing pay and intellectual challenges. At the end of the day, people have to optimize for their own interests because the world sure as hell doesn't care about your or my sacrifice. Even my best friend who took a job at a non-for-profit for many years helping those in need eventually joined BigCo to be able to afford things in life.

Re: Facebook senior software engineer interview

#108
The best way to prepare for a fanng interview is to have friends there and get fast tracked on easy mode.

FB rejected me twice and both times I followed a study plan much like the blog and in my case it turned out that I got too complicated with it and spent too much time on cool shit like dynamic programming, tries, all-pairs shortest paths but I should have stuck to drilling the simple data structures like stacks and BSTs cause that is all I ever got asked about.

I also got backchannelled during the behavioral the 2nd time around which I suspect may have been defamation. In the end my fan club did me a favor helping me dodge a bullet because I probably would have accepted an offer until I read about how bad morale at facebook really is (which in hindsight was reflected loud and clear in the conduct of the aforementioned behavioral).

One thing I have noticed about remote interviewing in general but especially with facebook is how disgustingly filthy some of the panelist's backgrounds were. During the portion where the candidate is allowed to ask questions I wanted to ask "Damn, you live like this?"

Re: Facebook senior software engineer interview

#109
post #20

Every time I read these posts I find them very depressing. Crunch through an enormous bunch of algorithm problems in order to perform well on some unrealistic whiteboard programming (I think the system engineering problems are actually more useful though) - as usual we've focused on the easy to measure metric rather than anything actually useful. Maybe these things are meant to be a proxy for how good you are at othe…

This may be an unpopular opinion, but I like how it is very objective, measurable, and somewhat specific. If I get fired and suddenly have my days free, I can simply study algorithms and leetcode and get a job elsewhere. It seems easier than worrying about everything else that could be asked during an interview.

Re: Facebook senior software engineer interview

#110
post #93
post #85

Earlier quoted context omitted.

"But why?" Because most people can't. And they want to make sure you can.

And it proves what exactly? Except that they have lost out on a good hire only because that hire is not familiar with that particular programming language that the interview is.

But that's not how it works. You are almost always free to use why language you want. There are exceptions to this but in those cases it would be clearly indicated in the job description.
Post reply on HN