I applied through an employee referral. I interviewed at Meta in Mar 2026
Interview
I recently interviewed for a Software Engineer role. While the technical interviewers were professional, the recruiting process was one of the most inefficient and deceptive experiences I’ve encountered in the industry.
1. Misleading and "Ghost-Rejection" Emailing Style:
Two days after the full loop interview, the recruiter sent an email titled "Thank You for Your Time Today!" filled with overly enthusiastic language ("huge thank you," "enthusiasm," "here for you every step of the way"). For any experienced candidate, this reads like a "soft" rejection template, yet it was served to tell me to wait for their result. It felt like a deliberate attempt to manipulate the candidate’s expectations rather than providing a clear, professional status update.
2. Pointless Sync Call for a 30-Second Rejection:
Despite having the result ready by Friday, the recruiter insisted on scheduling a formal "sync call" on the following Tuesday morning. I had to adjust my own work schedule and book a private room at my current office, only for the recruiter to spend 30 seconds reading a standard rejection script.
When I provided feedback that this information could—and should—have been handled via email to respect everyone's time, the recruiter doubled down, claiming they wanted to "show gratitude." There is no gratitude in wasting a candidate’s productive working hours for an update that fits in two sentences.
3. The Outcome:
After all this "high-touch" (read: high-friction) communication, it ended in a standard 12-month cool-off period.
Advice to Management
Efficiency is a core value at Meta, but it is clearly missing in the recruiting department. Stop forcing "sync calls" for rejections. It is not "personal"; it is disruptive. If you have a decision on Friday, send the email on Friday. Respect the candidates’ working hours and their professional time.
Interview questions [1]
Question 1
Standard leetcode style question, with AI available in one interview
Took about a month from start to finish, which felt longer than I expected. After a couple of initial phone screenings, I faced a challenging technical round focused on system design. It was during this round that I was asked to describe overcoming a major career challenge. Interestingly, I had just reviewed a similar framework on PracHub, which helped me articulate my thoughts clearly. Overall, I appreciated the depth of the process and ended up accepting the offer.
Interview questions [1]
Question 1
Describe Overcoming a Major Challenge in Your Career
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.
