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…
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…
Facebook senior software engineer interview
221–230 of 524 posts
Re: Facebook senior software engineer interview
#222Re: Facebook senior software engineer interview
#223Earlier 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.
Re: Facebook senior software engineer interview
#224Earlier quoted context omitted.
I feel the same. It's also much more meritocratic. People from no-name schools and no-name companies study leetcode and get into FAANG all the time. Do people really think it would be better to base it on resume and YOE?
It's not an "either/or" choice... These companies treat it as though if you can't recite a leetcode answer line for line then you're no good. A software developer skillset is a lot more varied than reciting 5 leetcode answers for algorithms you won't ever use in production code 99% of the time. And that 1% of the time you do? You're just going to Google the algorithm again anyway. It's an almost pointless interview e…
In my experience the leetcode questions were quite easy from an algorithm standpoint: string operations and traversals and things like that. You are judged not just on correctness but also your communication, requirements gathering, ability to catch edge cases and bugs, and general code quality. In other words, things that are absolutely relevant to the actual job.
Re: Facebook senior software engineer interview
#225Last spring after COVID hit I was reached out to by a Facebook recruiter with the conversation morphing after a few months (and two other individuals on their end) until having a really exciting conversation with a recruiter in early August that was just refreshing since it actually seemed like Facebook's hiring process wasn't that bad and that they might actually value me and my existing experience.
Part of my challenge is that my current role is not completely coding focused so I really don't have that "true" software engineering background and find it hard to figure out where I'd fit in a typical tech company's role structure. Instead, I have experience coding my own projects for my organization and taking them from concept to production in weeks and maintenance over timespans of years, along with management and tech leadership experience within my own organization.
Since coding isn't a daily focus all the time, my programming skills tend to need to be dusted off each time I take on a new project, and I know I'm not the best algorithmic expert, etc. but I'm reasonably intelligent (in my own humble opinion) and able to learn from others when I have that opportunity available (learning about extreme scaling techniques and certain advanced topics that might only be encountered within a tech-focused organization is unfortunately something I can't easily do within my current organization, and team-wise I'm the primary person interested in these sorts of topics so don't have others to really discuss the ideas with, which leads to that interest in potentially moving to a tech-focused company). I feel like my existing experience and ability to work with others and learn quickly would have some value (especially when you consider that new graduates don't necessarily have a lot of these experiences under their belt, but they are still considered for hiring...their algorithm knowledge might just be a bit fresher/recent).
Switching back to the interview...I spent a bit of time studying for the initial coding interview and felt like I had done decently well, but still received the "thanks but no thanks" email a few weeks later.
After that rejection (along with others over the last several years from companies I saw on the monthly "Who's Hiring" threads that intrigued me) I'm kind of done with trying to apply for tech jobs at the moment.
I'd love to earn more and work remotely from my current location (now that the pandemic has made this a little more possible) and be able to contribute my working days to contributing to the success of a tech-focused company, but it's not easy to be accepted by a tech company when you don't have the right background or exact skills upfront, so at least for the time being I need to be happy with my current work situation (even if it isn't always the most glamorous, tech-wise, and doesn't pay the same as a large tech company might).
This is just one personal anecdote of course, but I do wish there was a different hiring process for folks wanting to break into a tech company with existing experience that would be valuable, albeit non-traditional to typical hires.
Re: Facebook senior software engineer interview
#226Earlier quoted context omitted.
I interviewed at FB and Amazon last summer and I asked how long people stay once they are hired. At both companies I was told the average tenure is about 1.5 - 2 years. That was a big yiiiiikes moment for me. People don't stick around long enough to get promoted.
RSUs from your signing bonus vest fully at 2 years (atleast at Amazon). A lot of people bail as soon as that vesting happens.
Re: Facebook senior software engineer interview
#227Earlier quoted context omitted.
While I have sympathy for the idea that some of these interviews can be ridiculous, however it doesn't seem like the interviewer was in the wrong here. As an interviewee you should have known what interview process is like, I worked at Amazon and I know the recruiters brief the candidates on what to expect in the interview, so you should have known going in that you'd be expected to write code, you could have said no…
They didn't brief me to expect that. Or, to be fair, maybe they did and I missed it. I didn't mention above that he refused to answer a couple of basic questions (what type of work is it? what language? where will the job be? can I be remote?) until he got through the script. It was like talking to a machine. And he was rude. I got a negative impression. I know, sometimes recruits are expected to put up with some rud…
Some were doing it because they had to (last-second substitute) and it showed as they were rude about it or highly disorganized.
You don’t have to take it and it’s okay to cut interviews short as the interviewer (I’ve done it before), but it’s a mistake to be unprofessional about how it’s cut short.
Re: Facebook senior software engineer interview
#228I also hate the new trend of "take home" tests. That just seems disrespectful of the candidate's time.
Re: Facebook senior software engineer interview
#229Re: Facebook senior software engineer interview
#230There 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…
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't really done since the early days of my career. Aside from that, the only real challenge was a system design interview with a VERY junior engineer where I had a really hard time keeping things at a level they'd understand while not coming across as patronizing.