Interview Experience: Meta | Software Development Engineer (SDE-1) | E3
📌 Job Role: SDE 1
🎯 Job Level: E3
🔢 Number of Rounds: 4
📜 Offer Status: Rejected
📍 Location: London
👤 Candidate Name: Not disclosing due to signed NDAPreparation Strategy
For preparation, I focused on:
LeetCode (Medium & Hard problems), particularly topics like stacks, trees, and linked lists.
Behavioral Questions, using the STAR method to structure responses.
Mock Interviews, practicing under timed conditions to improve speed and accuracy.
Despite having some coding experience (approximately six months), the unexpected difficulty level in the final round was a challenge.
Interview Process
The process consisted of four rounds:
Phone Screen – Coding round
Behavioral Interview – Soft skills and problem-solving mindset
Coding Round 1 – Medium-difficulty coding questions
Coding Round 2 – Hard-difficulty coding questions
One of the biggest surprises was that the recruiter mentioned I would only face medium-difficulty questions, but the final round had two hard questions, making it significantly tougher.
Interview Rounds
Round 1 : Phone Screen (Coding Round)
Difficulty: Medium
Experience
This round consisted of two coding questions:
Given an array of integers, determine how many monotonic sequences the array is built of.
Merge K Sorted Lists (Simplified) – Problem Link
I was able to solve both questions with time left for explanation, which helped me proceed to the next round.
Learnings
Clearly explain the thought process behind solutions.
Practice array manipulation and merging problems.
Round 2 : Behavioral Interview
Difficulty: Medium
Experience
This round focused on soft skills and problem-solving mindset. Some of the questions included:
Describe a time when you worked with a challenging person.
Tell me about a time when you received negative feedback.
Describe a situation when you had little time to finish a job.
Tell me about a time when you had a conflict with a colleague.
I performed well in this round as I had prepared specific examples for each question.
Learnings
Use the STAR method to structure responses.
Show strong communication skills and adaptability in handling workplace challenges.
Round 3 : Coding
Difficulty: Medium
Experience
This round included two medium-level coding problems:
Minimum Add to Make Parentheses Valid – Problem Link
Simplify Path – Problem Link
I was able to solve both problems but received some unexpected follow-up questions. The interviewer repeatedly asked about the contents of the stack I used, which caught me off guard.
Learnings
Be prepared to explain the data structures used in solutions.
Practice stack-based problems and string manipulations.
Round 4 : Coding
Difficulty: Hard
Experience
This was the most challenging round. Although I was told to expect medium-level questions, both were hard:
Convert Binary Search Tree to Sorted Doubly Linked List – Problem Link
Design Skiplist (Search Function Only) – Problem Link
I had not encountered the BST-to-Doubly-Linked-List problem before, and despite hints from the interviewer, I could not solve it. The Skiplist problem was also unexpected, and I only managed to partially complete the solution.
This round was likely the reason I did not receive the offer. Additionally, all my interviewers had an infrastructure background, while my interests were in web and app development, which may have contributed to a mismatch.
Learnings
Develop a strong understanding of advanced data structures like BSTs and Skiplists.
Prepare for harder problems even if the recruiter states otherwise.
Ask clarifying questions early if hints seem repetitive or unclear.
Key Takeaways
Although I did not receive the offer, this interview process helped me identify areas for improvement. My key takeaways:
Strengthen knowledge of hard-level data structures.
Clarify expectations with the recruiter regarding difficulty levels.
Improve behavioral responses with well-structured examples.
Advice for Aspirants:
For those preparing for Meta interviews:
Focus on LeetCode Medium-Hard problems.
Be prepared for unexpected difficulty levels.
Clearly communicate thought processes during problem-solving.
With better preparation, I believe I can perform better in future attempts.


