Meta E6 Phone Screen [Rejection after providing Optimal Solutions]

During my Meta E6 phone screen, I was given 40 minutes to optimally solve two LeetCode-style questions. I started by asking clarifying questions and establishing good test cases, including edge cases, to ensure I fully understood the problems. For both questions, I first presented a brute-force approach, then moved on to optimal solutions, complete with time and space complexity analysis. I verified later that my solutions were indeed optimal and my complexity analysis was accurate, all achieved with minimal to no hints from the interviewer. Once we agreed on the optimal approaches, I proceeded to code both questions, completing them within the 40-minute window. Throughout the interview, I clearly explained my thought process, performed dry runs, and even demonstrated edge-case dry runs to illustrate how my solutions handled various scenarios. After the interview, I ran my code on LeetCode, and it was accepted for all test cases with optimal time and space complexity.

The only minor imperfection in my performance was a small code duplication (about three lines) in the second question. I proactively mentioned this to the interviewer, stating that I could make those lines more elegant if I had a couple more minutes, as I prioritized delivering a working solution first. The interviewer agreed but didn't offer me time at the end to demonstrate the improvement, so I didn't think it would be a significant issue. No behavioral or other types of questions were asked; after 40 minutes of coding, the interviewer asked if I had any questions for them, which we discussed for five minutes, concluding the 45-minute screen.

To my surprise, I received a rejection email a few days later. The feedback stated that while I did an excellent job on the first question, the code duplication in the second question (those same three lines I had mentioned) was cited as the reason for rejection. With 14 years of rich experience building large-scale systems and leading engineering teams for Fortune 50 companies, I found it hard to fathom a rejection based on such a minor point, especially after my rigorous preparation. I feel like Meta prioritizes two 'perfect' coding solutions over extensive real-world experience. I've had a tough time with Asian interviewers historically, and despite my strong performance against significant personal challenges leading up to the interview—including my child being in the ER, my wife's car issues, and school cancellations—I was ultimately gutted by this outcome. I genuinely hope my experience helps others, even though I felt particularly unlucky in this instance.