Live data from Hacker News

Facebook senior software engineer interview

daqo.medium.com

181–190 of 524 posts

Re: Facebook senior software engineer interview

#181
post #146

Earlier quoted context omitted.

An effective way to change a culture is to participate in it.

Changing a company's culture is nearly impossible at a startup, let alone a behemoth like FB.

Google did just vote to unionize, so it's not impossible, but very difficult.

Re: Facebook senior software engineer interview

#182

Besides the usual advice, this observation is very interesting: > Applying for senior engineering positions (>E4) in FANG companies is one of the best ways to get into them. This comment by a veteran senior engineer confirms to me that Facebook, just like most other FANGs, does a poor job of promoting from within. There are multiple comments to the same effect from many other FANG employees: It's much easier to get r…

I think you’re misunderstanding the author. The sentence after the one you quoted is

> Most of these companies have solid internship programs, and almost all E3 (entry-level) positions are offered to returning interns.

The author is saying that getting an entry-level position without an internship is very difficult at these companies and so if you want to work at one, applying as a senior engineer is a much easier route.

FWIW, I work at one of those companies and have found senior roles and promotions to actually be pretty biased toward longtime employees

Re: Facebook senior software engineer interview

#183
post #2

There are two interesting things in this post. The first is that a senior developer at Facebook believes every single senior developer looking for a role at Facebook can revise the same things. Clearly the author believes that Facebook are looking for programmers who fit a very specific mould, to the point that they're willing to go out in public and state exactly that. I'd argue that points to a massive monoculture…

My experience is that the expectation is the same for ALL big tech companies: you need to spend about a month revising problem types that they consider important for an interview. If someone fails on this, it is enough for them to pass on a candidate.

Re: Facebook senior software engineer interview

#184
post #126

Earlier quoted context omitted.

I worked at a company, not a FANG, but had interviews like a FANG. We had a solid team. But some of us believed we wouldn't be able to pass our own interviews.

isn't this what's happening at FANG companies: the gatekeepers (i.e. people giving interviews) have an incentive to not let people in too easily? This limits the pool of employees, and since what's rare is expensive, makes insiders more valuable? Also at FANG companies, interviewing feels (to me) like hazing that is unrelated to what the day-to-day job will be like. Some interviewers I had obviously had a very high o…

Our incentive is not (as you imply) a selfish desire to enrich ourselves though artificial scarcity, but rather the knowledge that a weak team member hurts everyone and is hard to get rid of. At my firm we have the explicit goal of hiring people who are better than half the developers at similar level. A little math will show you that if you do not do this, your average talent level goes down over time.

Re: Facebook senior software engineer interview

#185

Earlier quoted context omitted.

I couldn't disagree more with your post. The author is basically just putting out a detailed study plan for passing an exam. If a doctor posted a plan for passing the medical boards would your first thought be "Wow, look at that massive medical monoculture problem!" That seems like a ridiculous stretch in my opinion. To your second point, I hear this all the time in threads about tech interviewing: "Tech interviews a…

If a doctor posted a plan for passing the medical boards would your first thought be "Wow, look at that massive medical monoculture problem!" That seems like a ridiculous stretch in my opinion. It's more like an oncologist posting that every doctor needs to revise cancer treatments for a month before applying for a role in a hospital without realising that other doctors have spent 10 years specialising in different a…

this is off topic, but medical training (at least in the US) is unfortunately about as dysfunctional as you describe.

there's are years of inefficient labor from students, residents, fellows, and junior doctors on procedures they'll never do again (because they relatively cheap)

Re: Facebook senior software engineer interview

#186

Earlier quoted context omitted.

> That all makes sense for hiring people to work on big existing systems, but many of these large companies are also trying to innovate and build new products with smaller, more agile teams. Which innovation of Facebook are you describing? Instagram, WhatsApp, or the stories?

Not products in the typical sense, but these are some interesting technologies coming out of Facebook that I can list off the top of my head (many of which I have used personally): * https://engineering.fb.com/2014/06/10/web/open-sourcing-haxl... * https://osquery.io/ * https://rocksdb.org/ * https://fbinfer.com/ * https://flow.org/ * https://prepack.io/

I mean you listed several database libraries, static analyzers, and a code optimizer.

Is it your suggestion that those kinds of applications do not require solid knowledge of a variety of different data structures and algorithms?

Re: Facebook senior software engineer interview

#187
post #146

Earlier quoted context omitted.

Changing a company's culture is nearly impossible at a startup, let alone a behemoth like FB.

Google did just vote to unionize, so it's not impossible, but very difficult.

Between 200 and 300 Google employees formed a union. Google didn't vote to unionize.

Re: Facebook senior software engineer interview

#188
post #2

There are two interesting things in this post. The first is that a senior developer at Facebook believes every single senior developer looking for a role at Facebook can revise the same things. Clearly the author believes that Facebook are looking for programmers who fit a very specific mould, to the point that they're willing to go out in public and state exactly that. I'd argue that points to a massive monoculture…

[deleted]

Re: Facebook senior software engineer interview

#189
post #83
post #12

Earlier quoted context omitted.

From the article it would appear that anyone with a computer science background and a decent amount of experience as an engineer should pass the technical test without the need to spend the whole month revising. If you don't have a computer science foundation it's probably a good idea to learn the basics anyway, rather than learning just to pass the interview.

The bar for Facebook is something like being able to solve two medium-difficulty problems in 45 minutes. If you want to test yourself, you could try these, which are popular questions: https://leetcode.com/problems/find-all-anagrams-in-a https://leetcode.com/problems/subarray-sum-equals-k/-string/ Note that it's not enough to present any solution - you need to present a solution that is efficient. Also, you should be…

As someone who interviewed people applying to Facebook (or Oculus anyway), the coding tests were intentionally told to be structured as one easy question (so that the candidate could build some confidence and provide some signal) and one medium/hard coding question (ie can they write more substantial solutions and solve harder problems). That’s for the traditional “CS” coding interview. The other technical part is an open ended design question (whiteboard/hand-waving diagrams/explanations with no code).

Re: Facebook senior software engineer interview

#190
post #85

Earlier quoted context omitted.

After 20 years in software, I had a phone interview with an Amazon guy who sounded half my age (at most). Asked me to write some kind of function to do something, sort some stuff or some such. I described verbally how I would do it, almost line by line, in pseudo-code. He said "I need you to write it out in [some language]". I said "But why? I just told you how I'd do it." But he needed me to literally write the code…

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

We always allow the candidate to use any reasonable language. We're not testing if someone knows Java/Python/Lisp (I wish). We're testing if they know any language. I can confirm seeing people with resumes who nevertheless could not write any code even in the language they professed to be "expert" in.
Post reply on HN