Recruiter Screening Round:
Initial conversation with the recruiter to discuss the role, team expectations, and to align on experience and compensation range.
Online Coding Round (CoderPad):
One LeetCode-style live coding round conducted via CoderPad. Focused on problem-solving, coding efficiency, and edge cases.
Onsite/Loop Interviews (5 Rounds):
2 System Design Rounds: Covered both high-level architecture and low-level component design. Assessed scalability, trade-offs, and communication.
2 Data Structures & Algorithms Rounds: Focused on LeetCode-style problems. Emphasized problem-solving, clean code, and optimal solutions.
1 Behavioral Round: Assessed cultural fit, communication skills, and past experiences using STAR format.
Interview questions [1]
Question 1
Standard meta tagged DSA questions, for system design it was design leetcode, design i18n
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.
The interview felt more straightforward than I anticipated for a well-known tech giant. After a recruiter screen, I faced a technical round that included a DSA question about finding the lowest common ancestor in a binary tree. I was pleasantly surprised when I realized the exact problem had popped up in the algorithm practice section on PracHub during my prep. Ultimately, the experience was decent, but I chose to decline the offer as it didn’t align with my current goals.
Interview questions [1]
Question 1
Given a binary tree, find the lowest common ancestor of two given nodes in the tree.
