Meta

I had a phone interview for an IC4 role at Meta in London. I was asked two specific data structures and algorithms questions, and received positive feedback, indicating that I will schedule a full loop soon.

I recently went through an online assessment for Meta on CodeSignal. The assessment involved implementing a task management system with multiple levels of functionality. The first level focused on basic task operations, while subsequent levels added more complexity, such as user management and task assignment. The final level had some unclear requirements, but the overall experience was challenging and provided a good understanding of system design concepts.

Had a Meta onsite E5 interview which included coding, AI, and system design rounds. The AI round was particularly challenging and had a negative impact on the overall experience.

I recently had a 45-minute phone screen interview with Meta for an SDE-2 role, which involved solving two Data Structures and Algorithms problems. I was selected for onsites.

I interviewed for an E6 ML-SWE role at Meta, encompassing multiple coding, system design, and behavioral rounds. Although I received a downleveled offer for E5, I ultimately declined it due to other compelling opportunities.

I interviewed for an E4 Software Engineer role at Meta in Bangalore. After successfully clearing the screening rounds, I progressed to the main interview phase which included coding, an AI-assisted coding challenge, a behavioral assessment, and a product design round. Regrettably, I did not receive an offer.

I recently completed my full interview loop with Meta for a full-stack role but was unfortunately rejected. Despite what I felt was a strong performance across coding, system design, and a new AI-enabled round, I did not receive an offer.

I recently interviewed with Meta for an E4 Product role, navigating through a phone screen and multiple onsite rounds, where I successfully tackled various coding, system design, and behavioral challenges.

I interviewed for a SWE Product role at Meta in the USA, facing two coding problems: a binary tree column traversal and a complex problem involving friend request logic for centaurs. I couldn't fully solve the second problem but explained my approach.

I interviewed for a SWE Product role at Meta, participating in an AI coding round. This unique experience involved debugging existing utility functions and implementing a solution for an NP-Complete problem involving word subsets, which I solved but struggled to optimize.

I recently completed my first technical phone screen at Meta for a Mid-level Software Engineer role, where I was tested on two data structure and algorithm problems.

Applied for the Senior Security Engineer role at Meta in London. The screening process included a few questions related to IAM concepts and a coding problem. The outcome of the interview is pending.

I interviewed for a Software Engineer position at Meta in Bengaluru and was rejected after the phone screen, despite solving both technical questions asked.

I interviewed with Meta, navigating through a phone screen and two onsite coding rounds, including a custom BFS problem, and culminating in a system design discussion about an online chess game.

I recently interviewed for an E5 role at Meta in London, which consisted of a comprehensive loop including a screening round, two data structures and algorithms rounds, a behavioral round, and a system design round. I encountered a variety of challenging problems ranging from merging sorted arrays to designing a messaging service like WhatsApp.

I had a tech screen at Meta where the interviewer guided me through two coding problems. While I initially struggled with the problems, I was able to suggest the correct approach for the first one. I'm currently unsure about the outcome due to the significant help I received.

My Meta onsite interview experience in Bangalore, India, involved four rounds: AI-enabled coding, DSA, behavioral, and product architecture design. A key takeaway was the importance of clarifying ambiguous problem statements throughout the process.

I had my first round interview for a SWE II, Product role at Meta, which was a 45-minute session involving two coding problems. I managed to achieve an optimal solution for the first question and a working solution for the second, and I'm currently awaiting feedback.

I recently interviewed with Meta for an E6/E5 role. After a successful phone screen and strong performance in most onsite rounds, I received a downlevel offer for an E5 position and am currently in the team matching phase.

I recently completed my Meta E5 interview, which included a screening round, two coding rounds, a system design round focused on infrastructure, and a behavioral round. Despite solving most problems and thoroughly discussing the system design, I have a mixed feeling about the overall outcome.

I recently interviewed onsite at Meta for an unspecified role, going through four rounds covering data structures, algorithms, system design, and behavioral questions. I believe I performed well, coding and dry running all problems, and am now awaiting the results.

I recently interviewed with Meta for a Software Engineer position. Despite successfully solving two coding problems during the technical screen, I later realized a critical error in one of my solutions, which ultimately led to a rejection.

I interviewed for an E5 (Prod) Engineer role at Meta in the U.S. After navigating through both phone and onsite rounds, I unfortunately received a rejection, which left me feeling quite exhausted.

I recently interviewed for a Production Engineer role at Meta, encountering both a coding challenge involving file processing and a system troubleshooting scenario. Despite my efforts, I was ultimately rejected.

I successfully cleared the technical screen at Meta for an E4 level position after progressing through an online assessment. The interview primarily focused on two data structures and algorithms problems, and I'm now scheduled for the full onsite loop.

I interviewed for an E4 position at Meta in London, completing a behavioral round and two coding rounds. My system design interview is scheduled for next week. I felt demotivated after the first coding round due to a challenging question I didn't fully solve optimally.

I recently completed my Meta E4 interview in London, which included a behavioral round and two coding rounds, with a system design round pending. I felt somewhat discouraged after encountering an unfamiliar problem in the first coding round, despite performing well in other areas.

I recently completed the full interview loop with Meta, which included a technical screening, two coding rounds, a system design discussion on Netflix API, and behavioral questions. My preparation involved focusing on Meta's top 100 questions.

I recently interviewed at Meta for an E5 Software Engineer position and, despite some initial doubts, I successfully passed all rounds and received an offer for an IC5 role.

I successfully passed my phone screen at Meta, solving two LeetCode problems: Minimum Remove to Make Valid Parentheses and Range Sum of BST, even though I had a brief moment of struggle on the second question.

I had a screening round at Meta for an E5 position in the USA, where I tackled two coding problems. Despite a slight delay at the start, I was able to discuss my solutions and correct a mistake with a hint from the interviewer.

I recently interviewed at Meta for an IC4 position in London and successfully advanced to the team matching phase after completing a phone screen, two coding rounds, system design, and a behavioral interview.

I recently completed a screening round interview at Meta, which included two coding challenges: Range Sum of BST and Expression Add Operators. It was an interesting experience covering different algorithm types.

I had a phone screen interview for an E5 role at Meta in the US, where I was tested on two specific LeetCode problems: Lowest Common Ancestor of a Binary Tree III and Group Shifted Strings.

Successfully navigated the Meta E6 interview process in London, but received mixed feedback on system design. Focused on coding for 3 weeks and minimal system design prep, leading to a potentially negative feedback outcome.

Interviewed at Meta for E4 role. Passed coding rounds and system design, but outcome not specified.

I cleared the E5 interview at Meta in India. The interview process was challenging, with a mix of coding and design questions. I received an offer after a successful interview experience.

Recently completed the Meta Screening round for the Application Engineer role. The 45-minute interview included 25 minutes of Role specialization questions followed by a DSA problem, LeetCode 443: String Compression.

Successfully navigated through Meta's IC5 interview process, covering coding challenges, system design, and behavioral rounds. Demonstrated strong problem-solving skills and technical knowledge, with positive feedback from the interviewer.

I had a phone interview at Meta where I successfully solved two data structure and algorithm problems, and I am currently awaiting a reply.

Shared a solution for a Meta-related problem, LeetCode 2265, and discussed a variant where the task is to determine if every node in a binary tree is the average of its subtree. The problem involves understanding postorder traversal and optimizing it within a short time frame.

Meta Phone Screening Interview Experience

I interviewed for an E5 role at Meta, going through a full loop that included two coding rounds, a product architecture round, and a behavioral round.

I passed the phone screen interview at Meta for the E5 role in the US, where I was asked two LeetCode problems for which I provided optimal solutions.

I participated in a Meta Online Assessment which featured a complex system design problem to implement a banking system with various functionalities including account management, transactions, and a cashback mechanism.

I am sharing an anonymous phone screen interview experience with Meta, where three specific LeetCode variant problems were discussed. The candidate passed the interview and heard back after 6 business days.

I had an interview experience for an E4 role at Meta in London, covering multiple coding rounds and a system design interview. I am currently awaiting the results.

I interviewed for an E5 Infrastructure Engineer role at Meta and regrettably received a rejection. The interview process spanned a screening round and a full onsite loop, assessing my skills in coding, system design, and behavioral aspects.

I completed coding, system design, and behavioral rounds for an E5 position at Meta.

I had a Meta screening for an MLE L5 role in the US. The interview included two coding questions: one specifically linked to a LeetCode problem, and another involving merging two sorted lists of intervals. Although I didn't fully complete the second problem, my focus on communication and the interviewer's guidance helped me advance to the full-loop interview.

I shared my recent system design interview experience at Meta for a Senior Product Engineer (E5) role, detailing two rounds that tested for E5 and E4 levels. The interviews included a complex combined design problem and a more straightforward one.

I interviewed for an E5 position at Meta, completing multiple rounds of DSA, System Design, and Behavioral questions. Unfortunately, I was rejected, partly due to not leaving enough time for the system design deep dive.

This post details a Meta Software Engineer - Machine Learning interview experience, focusing on two specific algorithm questions.

My interview with Meta approximately two weeks ago resulted in not being selected, covering coding and network topics.

I went through a full-loop interview at Meta for an E5 role. Despite some preparation, I felt it was insufficient due to personal commitments, leading to a difficult experience where I struggled with several coding problems and ultimately do not expect an offer.

I interviewed for an E6 MLE position at Meta, which was later downgraded to E5. The interview process included a phone screen, two data structures and algorithms rounds, a behavioral round, and a system design round focused on Instagram reel recommendations. My third round, involving a Merge K Sorted Lists variant, did not go well.

This post details an anonymous candidate's phone screen experience at Meta, where they successfully passed after solving two variant LeetCode problems.

I recently went through the full Meta interview loop for an E5 role, which included a screening round, two coding interviews, a product architecture system design round, and a behavioral interview. Despite performing well on some technical aspects, I was ultimately rejected with feedback to strengthen technical skills across the board.

This post describes a variant of LeetCode 691, 'Stickers to Spell Word,' often encountered in Meta interviews. The specific twist involves using only a single sticker to recreate a target poster, which the author notes simplifies the original problem.

I conducted a mock phone screen interview covering Meta variants of LeetCode Hard problems LC76 (Minimum Window Substring) and LC317 (Shortest Distance From All Buildings).

I shared my Meta E5 Infra interview experience in London, detailing phone screen, DSA, System Design, and Behavioral rounds, ultimately receiving an E4 offer.

I am sharing the full-loop interview questions I encountered at Meta, covering system design, behavioral, and two coding rounds.

I shared a recent interview experience at Meta on behalf of an anonymous candidate, covering multiple LeetCode problems, behavioral questions, and a system design problem.

I had a phone interview with Meta in London where I was asked two questions. I successfully solved the first question but ran out of time for the second, and unfortunately, did not advance to the next round.

I recently completed my full loop interview rounds with Meta for an E4/E5 role. Despite positive feedback on my system design and behavioral rounds, I was rejected primarily due to my performance in the coding rounds.

I had a phone interview with Meta, where I was asked two medium-difficulty questions: Diameter of Binary Tree and a problem similar to Kth Smallest Element in a Sorted Matrix. I moved to the onsite round.

I had a phone screening with Meta for an ML/AI role in London. The interview included two Data Structures & Algorithms questions: one on making parentheses valid by removing minimum characters, and another on finding the Lowest Common Ancestor of two nodes in a binary tree, perceived as similar to finding an intersection of linked lists due to the input format. I successfully moved to the full loop after this interview.

I successfully cleared my phone screen interview at Meta, answering two specific LeetCode problems and their follow-ups, and have been selected for on-site.

I interviewed for an E5 role at Meta in London and was assessed on Data Structures & Algorithms, System Design, and Behavioral aspects through various rounds.

I successfully interviewed for an E4 SWE role at Meta in the US, securing an offer after completing a phone screen and a 5-round onsite, which included coding, system design, and behavioral questions.

I completed a phone screen with Meta, where I was given two LeetCode questions. I fumbled on the first one due to an off-by-one error in my binary search logic, but performed well on the second, only needing an edge case and a minor optimization pointed out. I am hoping for a 3/4 score to advance to the next round.

I completed a full-loop interview for an L5 Infrastructure Engineer / DevOps Engineer role at Meta (Facebook) in USA in April 2025, which consisted of 4 rounds focusing on DSA, Behavioral, and System Design.

This is an anonymous phone screen interview experience at Meta where the candidate passed. The interview included two main algorithmic questions: a variant of Random Pick with Weight and Valid Palindrome II with a follow-up to Valid Palindrome III.

I had a phone screen with Meta where I was asked two LeetCode questions: Continuous Subarray Sum and Convert Sorted List to Binary Search Tree. I was unable to complete the second question in time and received a rejection.

I completed a screening interview with Meta, successfully solving two technical problems and a follow-up question for the second problem within 35 minutes.

I had a 45-minute phone screen with Meta, where I was asked two specific data structures and algorithms problems.

I underwent a full loop interview for an E5 SWE Product role at Meta, which included two coding rounds and a product architecture round.

I had a phone screen with Meta in London, where I was presented with two algorithm questions, variants of 'Random Pick with Weight' and 'Shortest Path in Binary Matrix'. I performed well on the first and mostly on the second, but I made mistakes in the time and space complexity analysis for the second question. I am currently awaiting an update on my application.

I had a full loop interview for a Meta E4 infrastructure position in Seattle, which included a phone screen and a virtual on-site with coding, system design, and behavioral rounds. I was able to solve most coding problems optimally, but I believe I messed up the system design round, leading to a rejection. Despite the outcome, it was a good learning experience.

I had a phone screening interview with Meta where I was asked two algorithmic questions.

I attended a Meta London E5 interview in May 2025, which included coding, behavioral, and system design rounds. I am currently waiting for the results.

I had a Meta screening interview for a Senior Software Engineer role in Bangalore, where I was asked two specific coding problems from LeetCode.

I interviewed for a Specialist AI role (research engineer) at Meta's Menlo Park office and was ultimately rejected after an onsite experience that included coding, AI-specific coding, AI design, and behavioral rounds.

I interviewed at Meta 3 months ago, received an offer, and successfully matched with a team last week. The experience involved coding, system design, and behavioral interviews, featuring specific LeetCode problems, design scenarios like Dropbox, and challenging behavioral questions.

I had a phone screen and onsite interview for an E5 role at Meta in the US and was rejected. I am sharing my experience and learnings, including specific phone screen questions and hints for onsite questions, while honoring an NDA.

I successfully interviewed with Meta for a SWE E4 role, a process that took 6 months from recruitment to offer. Despite challenges like a tough team matching process for NYC and not achieving an E5 due to help on system design, I secured an offer with improved compensation compared to my previous role at Amazon, motivated by changes in company culture and seeking better treatment.

I'm sharing behavioral questions asked during my Meta E5 interview, building on my previous posts about phone screen and loop questions.

I successfully passed my E5 Production Engineer interview loop at Meta in London, UK, after a fast interview process and a total of three weeks of preparation.

I passed the Meta full loop interview for an E4 role in the US, which included a phone screen, two technical rounds focusing on Data Structures & Algorithms, and a system design interview.

I had my screening interview at Meta, during which I was asked two specific LeetCode problems: Kth Largest Element in an Array and a variation of Binary Tree Vertical Order Traversal.

I recently passed a Meta MLE phone screen, which included a variant of 'Shortest Path in a Binary Matrix' and 'Remove Duplicates from Sorted Array'.

I had a phone screen for a Meta SWE ML E4 position and was asked two coding problems. I received positive feedback and am now preparing for the full loop.

I received an offer from Meta for an E4 Software Engineer role after completing phone screen and onsite rounds, which included coding, system design, and behavioral interviews.

I interviewed for a Production Engineer role at Meta in Dublin and was ultimately hired with an overall rating of 3/5. I performed well in Leadership and Troubleshooting rounds but struggled with System Design and one of the Data Structures & Algorithms rounds.

I completed a phone screen with Meta USA for an E4/E5 role, which included two specific LeetCode questions (Range Sum of BST and LRU Cache with variants), and I have advanced to the onsite rounds.

I recently had an interview experience at Meta for an E4 Infra role, where I navigated through screening and onsite rounds, encountering various LeetCode problem variants and a System Design question.

I interviewed for an E5 role at Meta in the US in March 2025 and received a rejection. My coding and behavioral rounds were strong, but I felt less confident about the system design interview.

I had a phone screen for an E5 role at Meta in the USA, where I was asked to solve two LeetCode problems: Binary Tree Vertical Order Traversal and K Closest Points to Origin. I passed this round and am now scheduled for a full loop interview.

I passed the Meta E4 Software Engineer interview loop for an Infra role in the USA and am currently in the team matching stage after clearing Hiring Committee.

I recently went through the Meta E5/E6 interview process in London, covering screening, coding, product architecture, and behavioral rounds, and was ultimately approved for an E5 role. Although I had hoped for E6, I believe my performance in the system design round might have contributed to the E5 outcome.

I had a phone screen interview with Meta in the US, where I was asked two specific data structure and algorithm questions. I successfully passed this round.

I successfully completed my Meta E4 product screen and onsite interviews a few months ago, and I am sharing the specific questions I encountered during the process.

I experienced a coding round for a Meta E5 SWE Infra position in the US, which included two specific LeetCode problems.

I'm sharing the interview questions encountered during my Meta interview process, across multiple rounds.

I had a phone screen with Meta in Bangalore where I was asked two data structure and algorithm questions. One involved counting occurrences of 1s in a given range using an API, and the other was about finding the most frequent number in a set of overlapping ranges.

I underwent a full-loop interview at Meta for an E4 level position. While I performed well in the behavioral and system design rounds, I struggled to deliver bug-free code for the data structure and algorithm problems due to nerves.

I had a screening interview with Meta today. I was asked one behavioral question and two coding questions, one being a variant of Random Pick with Weight and the other Lowest Common Ancestor of a Binary Tree. I'm unsure about the outcome as I ran out of time on one coding question.

I recently went through a phone screen for Meta, which included behavioral questions and two coding challenges: one on stack operations for directory changes and another on string modification to form a palindrome.

I cleared a Meta phone screen where I solved two data structure and algorithm problems, including implementing a custom data structure and 'Copy List with Random Pointer'.

I had an E6 loop at Meta, comprising two coding rounds, two system design rounds (Ticketmaster and Ad impressions aggregator), and a behavioral round. I performed well in coding and behavioral, but felt time management in system design could be improved. I am currently awaiting the results and feeling nervous.

I solved all the coding questions, and the behavioral and product design rounds went well, but I was ultimately rejected without specific feedback from the recruiter. The difficulty with one particular coding question, even though I solved it with hints, might have contributed to the rejection.

I had a phone screen interview at Meta for a frontend role, where I was asked to implement two JavaScript functions from scratch: Memoize and Classnames.

My interview experience for an Infra E4 role at Meta included a phone screen with two algorithm questions and an onsite round featuring five technical problems, including both data structures & algorithms and a system design challenge.

I had a recent phone screen interview with Meta where I solved one coding problem perfectly and struggled with another.

I recently cleared my Meta SWE E4 phone screen and received an invitation for an onsite interview.

I interviewed for an E4 role at Meta, going through a phone screen and virtual onsite that included coding, system design, and behavioral rounds. Unfortunately, I did not receive an offer, attributing it to insufficient preparation for problem variants.

I underwent an additional screen for a SWE ML E4 position at Meta in London. I was asked two specific LeetCode problems: a Meta variant of Subarray Sum Equals K and Subsets. I successfully solved both, despite Subsets being a new problem for me.

I had a phone screen follow-up at Meta, which involved two data structures and algorithms questions.

I had a phone screen with Meta where I was asked two coding problems: an adaptation of Merge K Sorted Lists and Clone Graph. I successfully solved both problems and am awaiting the results.

I recently completed my loop interview with Meta for a Bangalore location, covering coding, ML design, and behavioral questions. While I was ultimately rejected, I am sharing the process and specific questions to help others prepare.

I recently had a phone screen round for Meta in the US, where I was asked two algorithmic questions: a random city generator based on population probability and a string matching problem involving alphanumeric abbreviations.

I had an interview at Meta in London for a SWE, ML E4 role where I was asked two specific LeetCode problems: Add Strings and Least Common Ancestor III.

I went through the Meta full loop interview process, which included a phone screen, two coding rounds, a system design round, and a behavioral round.

I completed a full-loop interview at Meta for a SWE Infra E4 role, which included a phone screen, two coding, two system design, and one behavioral round. I detailed the specific questions asked in each round, along with my approaches and follow-up discussions, and am currently awaiting results.

I had my first ever phone screen with Meta, where I was rejected after solving one coding question and struggling with a follow-up. I did not receive any specific feedback for improvement.

I experienced a phone screening with Meta, where I was presented with two variant LeetCode problems: Basic Calculator II and Valid Parentheses.

I had a phone screen with Meta where I was asked two coding questions, including a LeetCode problem and a variant of another. Despite my approach, I was rejected a few days later.

I went through a Meta interview process, detailing my friend's experience which included several rounds of coding, system design, and behavioral questions. Despite receiving positive feedback across all rounds, I was not extended an offer, which I believe was due to my limited 1.5-2 years of experience.

I had a phone screen interview at Meta for an E4 Infra role, which included a LeetCode problem and a custom problem about finding the minimum cost for a round trip between two cities with time-sequenced flight costs.

I recently completed a full loop interview at Meta for a Product SWE (E4/E5) role and successfully moved to the team matching phase. I was downleveled from E4/E5 largely due to mismanaging time in the Product Architecture round.

I had a phone screen and an onsite loop with Meta for a role requiring 2 years of experience. After preparing for about two months, I was ultimately rejected due to my performance in Coding 2 and System Design rounds, but found it a positive learning experience.

I successfully passed a Meta E5/E6 phone screen in London, despite making critical mistakes on one of the two coding questions, emphasizing the importance of strong communication and adaptability during the interview process.

I interviewed for an E5 position at Meta in London, completing a screening round and an on-site consisting of coding, design, and behavioral rounds, but ultimately received a rejection.

I went through a comprehensive E5 onsite interview loop at Meta in Bangalore, which included a phone screen, two data structures and algorithms rounds, a product architecture design round, and a critical behavioral round.

I recently interviewed with Meta and encountered a novel experience during a coding interview where new requirements were presented mid-implementation for a problem involving balancing parentheses while preserving the meaning of an arithmetic expression.

I completed my full loop onsite interview for the Meta E4 SDE role in London. Despite one round resulting in a 'Lean Hire', I received 'Hire' and 'Strong Hire' ratings in the other rounds including Phone Screen, System Design, DSA Round 1, and Behavioral, and I am hoping for a positive outcome.

I had a screening interview at Meta for an E5 role where I was asked two specific data structures and algorithms questions.

I had a phone screen with Meta for an E6 level position. The interview included behavioral questions and two LeetCode-style coding problems.

I had a phone screen with Meta for an E4 role and received a reject. I successfully solved a standard LeetCode problem, Longest Substring Without Repeating Characters, but ran out of time while attempting a challenging variant of Accounts Merge.

I interviewed for an E5 Senior Software Engineer position at Meta in Bangalore. The full loop consisted of five rounds covering coding, system design, and behavioral questions. Unfortunately, I was rejected due to my performance in the Product Architecture and Behavioral rounds.

I interviewed for an E4 SWE-ML position at Meta in Menlo Park, which included a phone screen and a full loop with coding, behavioral, and ML system design rounds. Despite my efforts, I received a rejection email just 15 minutes after my last interview, with vague feedback about strengthening my experience.

I successfully navigated Meta's interview process, which included an OA, two technical rounds, and a behavioral round, ultimately leading to an offer for a Software Engineer E3 New Grad position.

I successfully navigated a rigorous E4 interview process at Meta in the USA, which initially included five rounds and later extended to seven. Despite initial skepticism about a system design round, I ultimately received an offer for an E4 role after a follow-up interview and team matching.

I successfully passed my Meta E4 On-Site interview for an Infra role in the USA. The process involved a phone screen, system design, two coding rounds, and behavioral interviews, with one behavioral round requiring a redo before I received the offer.

I had a 45-minute screening interview at Meta for a Software Engineer role. I was asked two LeetCode questions, but I couldn't complete the second one, so I'm not expecting a positive outcome.

I've shared my insights into Meta's interview style, specifically regarding the 'Custom Sort String' problem (LC791), its common variant, and a crucial optimization follow-up question.

I had a phone screen with Meta where I was asked two coding problems: LeetCode 88 (Merge Sorted Array) and LeetCode 973 (K Closest Points to Origin). Despite solving both within the allotted time, I was rejected due to insufficient signal.

I had a Meta phone screen where I was asked to solve 'K+1th Largest Element' and 'Valid Palindrome'. Despite providing correct solutions and detailed explanations, the interview was frustrating due to vague feedback and ultimately resulted in a rejection.

I recently completed my phone screen and technical onsite rounds for a Software Engineer - ML position at Meta. I encountered several LeetCode-style coding problems and an ML system design question, and I'm currently awaiting my behavioral interview.

I completed a screening interview for an E4 position at Meta, successfully solving two coding problems, though I needed to correct a minor error on one. I am currently awaiting feedback.

I successfully navigated the interview process for an E5 Machine Learning Engineer position at Meta in Menlo Park. After two months of dedicated preparation, I received an offer following a phone screen and a full onsite loop.

I successfully navigated the Meta London SWE E4 recruitment process, which included a mock interview, phone screening, full-loop interviews, and a follow-up, ultimately securing a hire decision.

I interviewed for a Staff Software Engineer, Product (E6/E5) role at Meta in Singapore. Despite strong coding performance, mixed results in product design and a lack of detailed behavioral answers ultimately led to a rejection, though I found the overall interview experience to be uniquely positive.

I recently completed a technical phone screen for an E5 position at Meta in the USA, where I tackled two specific coding challenges after some initial behavioral questions.

I applied to Meta in January 2024 for an E4 Software Engineer role in London and successfully received an offer after completing multiple technical and behavioral rounds, including a follow-up system design interview.

I had a phone screen with Meta for an E6 Software Engineer role where I was asked two LeetCode style questions. Despite providing optimal solutions and clearly explaining my thought process, I was ultimately rejected due to a minor code duplication in the second question, which I had offered to refactor given more time.

I interviewed at Meta for an L4 position, going through multiple rounds covering coding, behavioral, and system design. Despite solving all technical problems optimally and feeling positive about my performance, I was ultimately rejected for not meeting the L4 expectations.

I interviewed for an E4 position at Meta and was ultimately rejected. The interview process included a phone screen, two coding rounds, a behavioral round, and a system design round, where I struggled with a mobile-focused design problem.

I interviewed for an E4 role at Meta, going through phone screen and multiple onsite rounds. Despite performing well in coding and behavioral rounds, I was ultimately rejected due to my performance in the system design round, which unexpectedly focused on mobile system design.

I interviewed for an E4 position at Meta and was ultimately rejected, primarily due to struggles in the mobile system design round, despite performing well in coding and behavioral interviews.

I interviewed for an E4 position at Meta and was ultimately rejected. While I performed well in the coding and behavioral rounds, my lack of preparation for mobile system design questions led to a struggle in that crucial round.

I successfully navigated the Meta E4 phone screen and onsite interviews, ultimately receiving an offer after a two-month intensive LeetCode preparation period. The whole process took about three months due to holiday delays.

I recently interviewed at Meta for an onsite role and received a rejection, primarily due to my struggle with a mobile system design question during the final round, despite performing well in the coding and behavioral interviews.

I recently completed an onsite interview at Meta for an E4/E5 role in the USA, which involved two coding rounds, one behavioral round, and one system design round. I felt confident about my performance in most rounds, particularly the coding challenges, and am currently awaiting the final feedback.

I recently interviewed virtually with Meta for the E4 Research Scientist ML role, undergoing a two-day process that included ML design, behavioral assessment, and multiple coding rounds.

I interviewed at Meta for an E4 position in Seattle in December 2021 and successfully received an offer. The interview process included a phone screen and several onsite rounds covering coding, machine learning design, and behavioral aspects.