Meta IT Software Engineer Interview Questions
& Process

So, to kick things off, the interviewer wanted me to just chat about my background and what I've done before. Then, they hit me with one big technical question. The whole thing was broken down into parts, you know? They started with a pretty simple version of the problem, and then just kept adding more difficulty as we went. Each part needed a bit more thinking, so it felt like they were purposefully making it harder step-by-step. Honestly, it felt like a pretty standard technical interview. Nothing too crazy or unexpected, just seeing how I'd tackle a problem, break it down, and then adjust when they threw in new rules.

it felt like preparing for a university midterm or final exam, where you memorize stuff to pass and then forget it. this approach seems better suited for recent graduates rather than experienced staff engineers. i was hoping to discuss strategic decision-making and its application in work, which is more appealing to me than rote memorization of algorithms like quicksort or merge sort.

Your onsite interview has a few parts. There are two coding sessions, each about 45 minutes, which are like the initial tech screen but maybe a bit harder. Doing well here really depends on how much you prep! Then there's the Design Interview, which might be 1 or 2 sessions, also 45 minutes each. This checks if you can tackle a tough engineering design problem. It could be systems design or product design. They'll give you a broad question and see how you solve it. Not all jobs need this, so your recruiter will tell you if it applies to you. Lastly, there's a 'Getting to Know You' session, about 45 minutes. They'll want to chat about your background, what gets you excited in tech, why you're looking to move, and what kind of impact you want to make. This is your chance to share stories and examples from your past work to show them what it's like working with you and how you handle tough situations.