What is the project you are most proud of?

"Overall, the interview process was structured and covered a good mix of DSA, software engineering practices, system design, and behavioral/team-fit discussions. I went through five rounds, and the difficulty was reasonable but the questions were varied and required adapting quickly between problem-solving and design-oriented discussions. The DSA rounds went well, particularly because the problems tested both fundamentals and the ability to reason through domain-specific constraints. The system design round was the highlight for me. I enjoyed discussing the bottlenecks in the initial design, reasoning about the 50,000 RPS traffic spike and limited inventory, and iterating toward a scalable solution. The hiring manager round was also a good experience because it went beyond standard behavioral questions and involved a detailed discussion of my past work, architecture decisions, database migration considerations, and how I would use AI tools while solving engineering problems. One thing I found challenging was that the software engineering practices round was more DSA-focused than I had expected, so there was less emphasis on software design/practices than I had anticipated. Overall, though, the process was positive and I received encouraging feedback throughout."

"This was an online phychometry test so not real depth tested. More of behavioral traits and you have to choose and say which of the 2 options you more closely associate with."

"The process focus on your project experience a lot and interviewer will dig into your project. It also have many behavior questions."

"It was a PMT role. Nothing really exciting just went thru resume and some BQs. And maybe was not a good fit as they are looking for b2b pm experience or with Saas"

"It was a PMT role. Nothing really exciting just went thru resume and some BQs. And maybe was not a good fit as they are looking for b2b pm experience or with Saas"

"Everything you find online about the interview structure is exactly how it is run. I split the interviews over 4 consecutive days. I could have asked more questions and done a lot more mock interview practice. When an interviewer interjects - you are off track, take a moment to catch your breath and come back."

"The role is a TPM under Alexa, but seems really like a project manager role- review privacy features. HM round was very basic, one PM loop asked a product design question, however the interviewer always cutting off the answer after 2-3 sentences; the most strange part was the tech lead round- a pure system design question which didn't mentioned in prep call at all. Wend very deep around 45 mins."

"The process was rigorous. The recruiter wasn't much help or accurate. Although the scheduling was very easy."

"It was straight forward. Medium level difficulty for all the questions. Prepare good stories for all your experiences."

"i think i definitely underprepared so i am preparing a lot leading up to my nexxt interview it was a good experience"

"I interviewed for a Senior Software Engineer role on the apps side, and the process was a short recruiter call, one standard coding screen, and then a five-round onsite. The biggest thing that stood out was that every interview had two people in it, usually one leading and one shadowing, so it felt like they were calibrating in real time. The onsite mixed normal coding and backend system design with an AI coding round in HackerRank where I had to use their built-in assistant to debug and build out a maze problem. The technical communication round was much more casual than I expected and ended after about 30 minutes because the interviewer said he had what he needed. I finished the full loop but didn't get an offer."

"I got this interview after applying to Google a ridiculous number of times over the years, with and without referrals, so when I finally got traction it honestly felt partly like timing. My process was recruiter, then a hiring manager technical screen, then three video interviews across leadership, GCA, and RK, but the themes blurred a lot more than I expected. The biggest thing I noticed was how team-specific TPM hiring felt, so I had to make my experience sound directly usable for that team instead of giving broad Google answers. I originally interviewed for a device-side TPM role, passed the loop, and then went through team match and landed in a different org. I got the offer and accepted it, and my main takeaway was that you really have to spoon-feed the fit and show how you would hit the ground running."

"The process was first a phone screen followed by a virtual loop with four rounds. The phone screen was a single tree traversal coding problem, and the onsite had two coding rounds, one system design round, and one behavioral round. The most interesting part was a new AI coding section that I hadn't seen before. It sounded new enough that even the format felt a little flexible, but the expectation was still that I do the actual coding myself and only use AI in a limited way. Overall it was pretty challenging, and if I did it again I would spend more time on behavioral prep because that was my weakest part."

"This was my second time going through the same Meta MLE process, and compared to the prior year the big changes were a written portal pre-screen and the new AI-enabled coding round. A sourcer reached out by email, I filled out the questionnaire, then I did a 45-minute coding screen with two LeetCode-style questions before getting the full loop. I split the loop across four days, one round per day: coding, AI-enabled debugging/coding, behavioral, and an ML design round on a TikTok-style recommendation system. The coding felt very standard Meta to me, but the AI round was the distinctive one because I had to debug an unfamiliar codebase, run tests intelligently, and use an LLM without blindly trusting it."

"A recruiter cold-reached out to me for an E5 software engineer role, and the whole process felt very standard Meta. I had a short recruiter call, then a coding screen with two common problems in one session, and I actually did poorly on the easy one but still barely made it through. After that I got the full loop spread across multiple days, and they gave me a few weeks to prepare. The final coding rounds were mostly standard too, but I felt weak in behavioral because I did not have the right work stories ready, especially for conflict, and I think I mishandled system design by not controlling time and not setting scale assumptions myself. I got the rejection after the final round."

"I got into ElevenLabs through a connection and the whole process moved pretty fast, about two weeks end to end. My loop was recruiter screen, a timed coding assessment, a live coding interview in a Google Doc, a customer-style case study, and then a CTO/founder interview. The consistent theme was that they wanted strong individuals, not people who hide behind team language, and they mixed behavioral questions into basically every round. The coding and case rounds were on the harder, more signal-driven side, while the founder round felt a bit off-topic and oddly fuzzy about the actual role definition. I passed the interviews and got a verbal yes, but I ended up not getting the final offer."

"It was a long process, took ages to schedule interviews. Did not receive feedback after being rejected in the final round."

"I applied online and the process started with a 30-minute engineer screen instead of a recruiter screen. After that, they scheduled what I was told were the final rounds: two coding interviews on one day and a design round the next day. The first coding round was a standard LRU cache interview and felt fair, but the second one was rough because the interviewer gave me a big LLM-related codebase, refused to clarify inputs or outputs, and just kept telling me to read the code. That same evening, they canceled my last design round and then ghosted me when I asked for an explanation. Overall it felt very inconsistent: one interviewer was reasonable, the next was not, and the process ended without any real closure."

"The process was straightforward. Recruiter set the expectations of each round early in the process. The interviewers were very candid and professional, with straight focus on case solving using MECE and structured thinking"

"The interview process was fairly structured, starting with an initial screening followed by technical and/or managerial rounds. What went well was the clarity of questions and the opportunity to explain my thought process. One area that could have been better was the time allocated for certain discussions, which felt slightly rushed."

"The interview went very well, the interviewers were very nice. They don't ask questions out of the scope, they were very helpful and supportive. The communication was key in taking the interview, there was an area I have been asked about, showing eagerness to learn was enough for the interviewer. But, of course, I had to show solid skills in other areas. I learned from this interview that it isn't over until it's over, do not give up mid interview, just carry on answering to the best of your ability."

"Comparatively easy, but took a lot of time to complete the process. Keep your calm and you should be good."