J'ai postulé via un recruteur. Le processus a pris 5 jours. J'ai passé un entretien chez Meta
Entretien
I was contacted by a recruiter about a possible position. While I was not immediately looking, I was intrigued enough to continue with the process.
I had a quick phone call with my recruiter to go over my background and experience. She concluded the phone call by determining my availability for a technical phone screen and followed up with some research materials to better prepare for the phone screen.
The technical phone screen was set up using collabedit as the platform for sharing code between myself and the interviewer. I was asked a few simple technical questions, and a few harder programming problems dealing with algorithms and data structures. The interviewer was patient and helpful.
The recruiter emailed me the same evening to let me know that I would not be moving further in the process, as my initial hesitations on the early data structure questions signalled poor understanding of basic concepts.
Questions d'entretien [1]
Question 1
You are given a string with each english character translated to its alphabetical position (e.g., the string "ABC" --> "123"). Provide a function that, when provided the string as an argument, will return the maximum number of strings the encoded string could represent (for example, "123" could represent "ABC", "LC", or "AW").
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.
Questions d'entretien [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.
Questions d'entretien [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.
Questions d'entretien [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.
