Tell me about your past projects.

"The interview screen was pretty straightforward. The hiring manager screen is mainly behavioral and assessing your product style and fit"

"Friendly interviewers, coding round didn't have enough time for 3rd round but finished explanation. make sure you focus on explaining clearly and moving fast through first and second round to complete third round of coding screen."

"It was good experience overall Went well Recruiter really put efforts in prepping me for HM Didn’t go well HM round was not clear enough There were no direct LP questions asked so they gave another Screening round"

"The HR call was 30 mins. So a proper deep dive into candidate interests and suitability. It was quick and next round was scheduled immediately"

"What went well: The technical evaluation was refreshingly practical and closely mirrored real-world software engineering rather than abstract competitive programming puzzles. The coding sessions focused heavily on clean code architecture, defensive programming, edge-case handling, and reasoning through system performance trade-offs. The interviewers actively engaged as collaborative peers, providing helpful hints when exploring complex design decisions. What didn’t go well: Time management during the system design/ML infrastructure round was tight. Spending too much time in the opening minutes clarifying deep architectural assumptions meant rushing through the observability, rate-limiting, and fault-tolerance sections near the end."

"Its moderate if you have prepared enough. Be ready with introduction and experience on your projects you have worked on process improvement and team management"

"Practical interviews, focussed on the role requirements. System design had unique twists, but nothing too out there."

"overall a good experience with the onsite at harvey's offices, one nit since this role is a founding trust engineer role, the interviewers and the panel did not have real experiences with auditors and bigger security frameworks, so the questions were orthogonal to my experience."

"Practical interviews, focussed on the role requirements. System design had unique twists, but nothing too out there."

"Very streamlined experience. Phone screen and product sense and prioritization questions are all very standard."

"The process was very easy. The questions were not difficult but I didn't have a strong delivery of my answers as I didn't prepare a strong STAR approach."

"The overall interview process was incredibly smooth, straightforward, and well-organized from start to finish. The recruiter was exceptionally friendly, responsive, and did a fantastic job of setting clear expectations for each stage. There weren't any significant downsides, as the scheduling was efficient and the communication remained consistent throughout."

"The process was weird. I thought the interview went well, the interviewer even told me to prepare my leetcode for the next round and then I got rejected."

"Not that hard, pretty easy SQL coding challenge. Have to run the SQL live in a Python NB. The behavioral was also pretty easy and mostly about past projects and failures and probing more on resume."

"The interview focused on my experience with Node.js backend development, including API design, database management, caching, and real-world project implementations. What went well was explaining my production experience and problem-solving approach; areas for improvement include providing more detailed answers on certain concepts and system design scenarios."

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

"The overall interview process consisted of a recruiter screen, a technical call with the hiring manager, a written narrative exercise, and a 5-round virtual loop focusing on System Design, People Management, Operational Excellence, Cross-Functional Leadership, and a Bar Raiser round, with each module heavily testing Amazon’s Leadership Principles using the STAR method. What went well was my ability to deliver structured, data-driven answers that dedicated most of the time to my direct actions as a leader while anchoring results in concrete business metrics. I successfully demonstrated core Leadership Principles like Customer Obsession and Hire and Develop the Best through explicit examples of team growth, performance management, and architecture trade-offs, effectively balancing high-level business strategy with technical depth during system design discussions. What didn’t go as well was my initial tendency to credit the team using "we" instead of "I," which required interviewers to interrupt and probe for my specific individual contributions. Additionally, I mismanaged pacing in one round by spending too much backstory time setting up an operational failure scenario, which left little time for long-term preventative fixes, and I initially got bogged down optimizing a single database schema during system design rather than outlining the full end-to-end architecture first"

"The interview consists of two parts: a 45 min LC style coding and 15 mins conversation on your prior projects. The 45 min question was to build an arithmetic evaluator. For that, you have to use the Shunting Yard algorithm. It was only "+", "-", "(" and ")". I'm not sure if we would have used more operators, maybe some with precedence, if I had gone further. I had a hard time understanding the interviewer. I learned later on from Chat that you should contact your recruiter immediately if this happens."

"The overall interview process went smoothly. My recruiter was friendly and communicative, and flexible with my schedule (I was traveling and had to split up my interviews). I received feedback relatively quickly after each round (within a few days - I often had to wait longer with other companies). No surprises, the recruiter clearly described the type of interview for each round."

"OA is sent automatically to everyone who applies. Resume screening happens after. Questions are generally very difficult. The phone interview is done through AI, and asks you technical questions about your experience, projects, and challenges."

"Very strong interviewers who know what they are looking for and prompt you in the direction needed. The product sense question seemed too narrow in scope and was phrased in a tricky way where traditional structure could not fit in to solve the problem."

"Very strong interviewers who know what they are looking for and prompt you in the direction needed. The product sense question seemed too narrow in scope and was phrased in a tricky way where traditional structure could not fit in to solve the problem."

"The process was relatively short and well defined. I went through a recruiter screen followed by a first round with the director of the portfolio. After passing that the final round was a panel with two group PMs, an eng manager, and a design manager (4 separate interviews over the course of a week) eBay provided 4 "themes" for each panel interview, however both PM rounds asked execution questions when one of the rounds was supposed to be strategic or product design focused."

"2 HLD rounds, 1 LLD round, 1 HM round. Did well in all the technical rounds. HM round - I got rejected because the Hiring Manager thought my scalability experience was not upto the expectations."

"The recruiter was very nice and all the interview went very smoothly. I think I was rejected because some of my answer showed unexperienced."

"The process was fairly easy and not very structured, with a mix of some product sense and behavioral interviews scattered throughout."

"I have 2 technical screens and the bar for EM for system designs is very high. The recruiter communication was very good. However the process took very long."

"It was easy and helped me understand the role better before asking questions. This helped me tailor my responses better"

"I interviewed for an AI Engineer internship, but the process was mostly DSA-heavy. I had an online coding round first, then a technical round with binary tree and DP questions, then another harder DSA round with DP and linked list questions, and finally an HR round. The online round covered arrays and strings, and the later rounds got progressively more difficult. The only non-DSA part was the last round, where they asked about my projects and previous experience. I didn't share the final outcome, but the main thing that stood out to me was how coding-focused the whole process was."

"Well structured and highly professional, consisting of a phone screen followed by deep dives with senior leadership team and cross functional stakeholders"

"Technical interviews were mostly fine. 6 rounds, marathon-style. Did all interviews and was ghosted afterwards, no follow ups, no rejection emails, nothing."

"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."

"My Netflix intern process was four rounds total if I count the OA: two CodeSignal assessments first, then a live coding round, then system design, and then a hiring manager round. I was nervous at every step because Netflix has such a high bar, but the people I met were really free and welcoming, so it felt less like an interview and more like working through things with engineers. The most unusual part to me was the AI-assisted assessment early on and then the longer team-matching wait before the hiring manager round. The earlier rounds usually took about a week to hear back from, but I waited around three weeks for the manager step. Once I got to the manager round, it honestly felt almost definite that I was very close, and I ended up getting the offer."

"The interviews focused mainly on my experience, technical background, and how I approached real problems rather than overly theoretical questions."

"I had a long process with a recruiter screen, then a PM aptitude screen, then a full onsite loop for a PM leadership role managing PMs at roughly an L7-equivalent level. I put more than 100 hours into prep because this is absolutely not a night-before kind of interview, and I actually felt pretty strong across the first several rounds. The loop covered people management, cross-functional influence, execution and metrics, operating, project retro, and product sense, and the interviewer variance was real because some people would lightly guide while others gave me nothing. I got rejected, and I'm pretty sure the miss was the metrics depth in my last execution-style round, plus not going deep enough on secondary metrics in product sense."

"It was a great experience overall. Everyone I met during the process was really kind and invested in the recruiting process. Recruiters were also generally responsive but sometimes it took a couple weeks to schedule the next rounds."

"Process was quick, team was professional, and had a diverse set of interviews. Recommendation to split the loop into two days."

"It was a short process, not very technical, very mission driven. The recruiter screen was all the basic questions. The second round was the with the manager and more about previous experiences and applying them to the role. A lot of questions around data. The final round was more of a teammate vibe check and culture fit round."

"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 process wasn't too difficult. DSA/Leetcode wasn't heavily emphasized. It was a general programming type interview where you go through a code block and show your understanding of data structures"

"The interview process was well structured and covered a good mix of DSA, ML theory, and ML system design. The problem-solving and technical discussions went well, and the questions were relevant to the role. I felt I could have prepared more thoroughly for some of the system design and deeper ML theory questions."

"I enjoyed the whole process and transparency throughout. Though it's a bit dated, I'm sure the general premise is still the same. Recruiter phone screen Online coding assessment 45 mins tech interview Onsite with 3 technical interviews and 2 behavioural (1 of my tech was cancelled) Communication was always clear and it took a bit longer since it was over the Christmas break. Got offer shortly after the final and accepted, super glad!"

"Recruiter was good at communicating throughout and the interviewers seemed really engaged in the process. Excitable about their space. There is a product design portion where, given a prompt and UX snippet, users are asked to design a solution to the prompt. You are given about 30 min and then are grilled on that. There’s a basic analysis portion ensuring you can read basic data and infer decisions."

"The process was smooth , straight to the point . The interview environment also smooth easy and everything was to the point"

"Behaviour heavy. Prepare for typical product manager interview questions, I woulnd't say the questions are too challenging."

"The process was short. Each interview was about 30 minutes. Mostly all questions were behavioral/product sense/product strategy"

"The overall interview process was easy, no product design rounds. They were all mainly behavioral with some general product sense questions baked in."

"I think I did well, prepapring was the best thing I could do, having notes, listening to podcasts, asking questions, doing mock interviews, practice practice practice"

"The recruiter is good , friendly and patient Always briefing about what would the next roles look like"

"The recruiter is good , friendly and patient Always briefing about what would the next roles look like"

"Process was fairly straight forward. Response times can vary so don't stress if you don't hear back in time."

"Overall good. Round interview really intense. 1 hour for each and have to deal with 4 managers one by one."