Live data from Hacker News

Facebook senior software engineer interview

daqo.medium.com

521–524 of 524 posts

Re: Facebook senior software engineer interview

#521

Earlier quoted context omitted.

Funny how humans were somehow able to reproduce just fine for millions of years before surgical deliveries. https://www.youtube.com/watch?v=_YruT2ROEUc

Many women died giving birth.

Oddly enough, the US has the same pregnancy mortality rate as places like Latvia, Moldova, Romania, and the Ukraine. Tied for 56th out of 186 (there are lots of ties)

Re: Facebook senior software engineer interview

#522

Earlier quoted context omitted.

Senior software engineer is specific?

Yes! When a Senior SWE gets promoted the next title is Staff SWE. See also E5 and E6 at http://levels.fyi .

Ah, I see, exactly the way an plastic surgeon gets promoted to pediatrician.

Re: Facebook senior software engineer interview

#523

Earlier quoted context omitted.

There is this weird meme that using Python is beneficial during interviewing -- you mention it, the OP mentions it, I have experienced it myself and seen friends mention it. I don't know how or why this meme infects people; in my interview experience (MSFT, Google, Oracle, FB, Amazon, other smaller places) nobody ever batted an eyelid on me using C#. My advice would be to only use a language you know best, as long as…

It took me 1 second to think that Python has divmod built-in whereas you must import Math in C# to use DivRem. It's just little things like that - as well as boilerplate - that really makes a difference in these interviews. How many of these interviews resulted in a job offer? I disagree with eyelid-batting being the new success metric.

I feel that you think of the interviews as if they were a competitive programming contest.

If I needed a DivRem function I'd just write it in, `import Math` optional. In fact I probably wouldn't remember the exact name of the function and would've just 'created' a new one: `Tuple DivideWithRemainder(int dividend, int divisor)`. You can just write signatures for functions like that on a separate side of the whiteboard and invite your interviewer to tell you if they want to see any of them implemented.

I would advice this as a general approach -- split things into (reasonable) parts and implement them in order of importance. In one interview (Amazon) I ended up implementing every small thing I parceled out. In others my interviewers seemed to appreciate that we both care a lot about the `solution flow` and the `technically hard` parts and not at all about `DivideWithRemainder` or `import Math`.

I got offers from most of the places that I interviewed at.

Re: Facebook senior software engineer interview

#524

Earlier quoted context omitted.

>Secondly, the author believes that senior developers, who likely have 10+ years under their belt if they're senior, need to spend a solid month revising in order to be successful landing a role there. FWIW, I joined FB at 20 YOE and spent about 3 hours on Leetcode problems just to get my mind back to being able to handle "stupid computer" tricks. Array manipulation, algorithm cleverness, etc. are things that I hadn'…

I had the same experience. They only asked about things I haven't focused on or cared about in over 20 years. The person on the other side of the design interview also seemed very inexperienced and wasn't able to follow things that would be obvious and simple to anyone who has actually done system architecture.

>...things that would be obvious and simple to anyone who has actually done system architecture

Load balancing web servers was one of those that almost got me in trouble. I just assumed that any sane web infra would balance load.

Post reply on HN