I applied through a recruiter. I interviewed at Meta in Mar 2023
Interview
My Meta interview experience was intense, fair, and surprisingly well structured. The interviewer set clear expectations, kept the pace tight, and focused heavily on problem solving, tradeoffs, and communication rather than trivia. The coding question was realistic and layered, rewarding a clean first solution and making follow-ups much easier if the foundation was solid. I appreciated the emphasis on explaining decisions, edge cases, and complexity. Feedback cues were subtle but helpful, and the conversation felt collaborative instead of adversarial. Overall, it felt like a strong signal-seeking process that values clarity, adaptability, and engineering judgment more than memorized patterns in practice.
Interview questions [1]
Question 1
Graph question but I forgot how to implement bellman ford
The entire process usually takes 3–8 weeks, depending on scheduling and the specific role. Coding interviews heavily emphasize common DSA topics such as arrays, strings, trees, graphs, BFS/DFS, heaps, hash maps, and dynamic programming. System design becomes increasingly important for E4+ positions.
Interview questions [1]
Question 1
Given an array of integers and a target value, return the indices of two numbers that add up to the target
Unexpectedly, the first question in the technical round felt familiar. It was about finding a subset of strings with unique character concatenation — same problem I had worked through on PracHub a few days earlier. The interview included a recruiter screen followed by a rigorous pair of technical interviews where I tackled data structures and algorithms alongside system design concepts. After successfully answering a few more challenging DSA questions, I received an offer. The entire experience was intense but ultimately rewarding, and I happily accepted the position.
Interview questions [1]
Question 1
Given an array of strings, pick a subset whose concatenation contains no duplicate characters, and return the maximum possible length of that concatenation.
Standard cookie cutter interview with a coding interview, a system design interview and culture interview. The coding part is basically leetcode. The system design is what you can find on many youtube videos. The culture one is more tricky as they want to see that you fit Meta's culture, not that you were doing great at your existing company. So skills like dealing with conflict without calling in managers is sought after.
Interview questions [1]
Question 1
coding: I forgot, sorry
system design: design ticketmaster
culture: talk about past project; when you disagreed with a peer; how I resolved dissagreements, etc.
