Tell me about yourself.

"There was a long wait between the time I submitted my application and when I was contacted by HR. I received an automatic reply following the submission and then noting for about 2 months, I actually thought that I hadn't got past the CV screening but then I was contacted and was able to schedule interview through their platform around 2 weeks after. The pace of the interviews seems measured overall."

"Interviews went smoothly. They expect you to be able to deeply unpack your responsibilities in your current/former roles and expect you to elaborate in great detail as well about how your organization functions, different teams interact with each other, etc."

"Interviews went smoothly. They expect you to be able to deeply unpack your responsibilities in your current/former roles and expect you to elaborate in great detail as well about how your organization functions, different teams interact with each other, etc."

"The interview process in very well organised and it will take long to complete all rounds. You would be judged on your past work, your background and how well you present your self."

"The screen was normal behavioral questions with the only technical one being how would I improve a product of my choosing."

"The process on start is very easy ( online assessment , phone screen) but coding is very difficult - LEETCODE MEDIUM"

"The screening process was pretty straightforward. It started with a few basic questions about my prior experience, relevant background, and the technical projects I had worked on. From there, the conversation focused on the projects I had mentioned, with questions about my specific contributions, the technologies I used, the challenges I encountered, and how I approached solving technical problems. Overall, the screening was fairly conversational and served mainly to assess my technical foundation, hands-on experience, and ability to clearly explain the work I had done."

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

"The interview was a standard FAANG type of interview, where the recruiter screen talked about resume and behavioral questions, and the first coding round was a non-AI traditional leetcode question."

"Overall, it followed Meta's typical PM loop and most questions came from the Meta question bank. What didn't go well is the time recruiter takes to schedule and team match time it takes."

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

"OA was relatively easy, phone screen was similar, lots of behavioral questions. Overall it was a good process, not very difficult but they do value technical coding skill."

"The process was well-defined but the goals of each round were quite vague and ambiguous. The recruiter was unable to provide detailed insight on how to prep and what to expect in each interview"

"It was a mix of behavioral and hypthetical questions. The behaviroal part I was good at I think, but the hypothetical part it took me too long to answer and I was probably not confident enough, also some answer I gave was not clear and straightforward"

"The initial round with recruiter was good. Along with experience he asked some data platform related questions."

"This was first technical round of interview, I went through typical System design videos but it needs in depth knowledge of system design rather knowing on high level. I kind of assumed it is going to be tough based on Linkedin profile of interviewer. He caught me off guard on few concepts. Interview can go in any direction so prepare deep on concepts. He asked me to write Pseudo code as well. AI Round was good where I was able to answer all questions."

"The recruiter was quite discouraging, as he mentioned that I should apply for entry-level roles after 7 years of experience. I understand it is in a different country but my experience is with US MNC only. Moreover, he explicitly stated that we hire only MBAs from top B-schools only. I could have performed better if I knew what would be asked, there was hardly any information available on the internet. Moreover, I learnt that PMs don't really choose to interact with customers/clients and are asked to work on features that they get from the sales team. Something to keep in mind if you are looking for a role that requires ownership."

"Interviews are aligned with what mentioned in the Job description. Expect some system design questions as well."

"Prepared a concise self-introduction and walked through a major project from my experience that is highly relevant to the role. For the questions what are you most excited currently? my answer is too general and can be more specific."

"didn't go well: (1) missing image data handling was not a good answer. i realized a better solution right after (2) hierarchical classification, how to do level by level? (3) overall infrastructure design including model training infra and streaming data serving"

"the technical round was that difficult but the behavioral round would need more focus on, especially the star methods"

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

"I got the recruiter screen round call scheduled within a few days of applying for the role. The recruiter was professional and explained the role, compensation & benefits details and that the role is hybrid. They seemed to be pleased with all of my answers however I only got a rejection email a day later without any feedback."

"It was Initial Technical Round to verify the Experience and projects mentioned on the Resume. It also had certain basic fundamental questions"

"The recruiter round was for 30mins. Recruiter explained about the role and asked questions regarding my background"

"The first round was recruiter screening via phone call, it went well. Then a zoom call with the principal software engineer, that went well too. Then came the 4 round loop. I messed up during the system design, as the structure for that round was completely different from what was described. The rest went well. But yeah didn make it"

"The process was more slow than expected. The recruiter was very attentive and helpful. Interviewers were happy to share about culture and open up about the less "shiny" aspects."

"- Good coding round - Good overall experience - Interviewer was supportive Cons: - it went for 2 months"

"The recruiter did a good job of giving me an idea of what to expect. Honestly, I didn't practice enough mocks by the time the interview came around. I liked that they had a portal for viewing the application process but I got no notification at all about my rejection."

"Overall experience was average, for last round interviewer was not friendly and he was not helping instead of I ask something they go deep into it"

"So far straightforward phone screen. Prepped background and interests well and tried to speak to the role in a bit of detail."

"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 first round was recruiter screening via phone call, it went well. Then a zoom call with the principal software engineer, that went well too. Then came the 4 round loop. I messed up during the system design, as the structure for that round was completely different from what was described. The rest went well. But yeah didn make it"

"Very smooth and clear, the recruiter laid down what the expectations are, and the coding interview was mostly leetcode medium level."

"It was very conversational. The recruiter call was pretty easy and direct. The next round was with two interviewers and I was given 45 minutes to dive deep into a technical challenge or program I solved or drove. It was very very conversational and while they probed it was not very adversarial"

"Technical being able to use Generic types and useEffect cleanup in a live coding environment without any references"

"The process was well-organized and moved at a reasonable pace. Communication from the recruiter was clear, and each round had a defined focus, so I always knew what to expect. The interviewers were professional and gave me space to walk through my thinking. What went well was the technical discussion , it felt like a genuine conversation rather than a checklist, and the questions were relevant to the role. What could have been smoother was the scheduling between rounds, which took a bit longer than expected, and I would have appreciated slightly more feedback along the way."

"Communication was very smooth with the recruiting team. The online assessment was relatively easier. The technical interview was pretty conversational rather than case heavy."

"Overall, I had a positive interview experience. The conversation felt engaging and gave me a better understanding of the role, the team, and the types of challenges they are working to solve. I especially appreciated the opportunity to discuss my experience and think through questions that reflected the work of the position. One area I could have improved personally was being more concise in a few of my responses. There were moments where I could have communicated my thought process more directly. Overall, though, I enjoyed the conversation and appreciated the interviewer's time, transparency, and insights into the team and TikTok."

"Smooth process with very nice people. Take home took some time but was fun to think about their product area. A lot of emphasis on AI fluency both in product and how you work"

"The interview process was challenging but very informative. The recruiter guided me well about preparation."

"The recruiter was very responsive, Very standard questions if your experience is well aligned. Lot of interviewers who were less than 6 months into the company."

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

"Very smooth interview process. Interviewing in-person enabled for a more conversational style. Got to meet pretty much everyone on the team."

"The process started with a recruiter reaching out on LinkedIn, followed by a 30-minute phone screen focused on my background, motivation, and logistics. It was conversational and low-pressure — the recruiter walked me through what the role involved and what the loop would look like, which helped me prepare. From there it moved to a hiring manager conversation and then a virtual loop covering behavioral questions, analytical skills (SQL, data visualization, requirements gathering), and a case-style discussion on turning data into business recommendations. What went well: The recruiter was personable, transparent, and responsive early on, and set clear expectations. The interviewers were engaged and the questions were fair — grounded in real business-analyst work rather than trick questions. The behavioral portion gave me room to show impact using concrete, quantified examples. What didn't go well: The pace between stages was uneven — there were noticeable gaps of silence (a couple of weeks at one point) with little proactive follow-up, which made it hard to gauge where I stood. Scheduling the loop took longer than expected, and communication was less consistent once it moved past the initial recruiter screen. A bit more visibility into timeline and next steps would have improved the experience."

"The interview lasted about four hours and was divided into several sections. One section focused on behavioral questions, where I was asked about my past experiences, how I handle different situations, and examples of teamwork, leadership, and problem-solving. Another section assessed my math skills through quantitative and analytical questions. The final section was technical and conceptual, testing my understanding of fundamental technical concepts, my reasoning process, and how I approached solving technical problems rather than simply recalling facts."

"Professional but the HM round is so pushy. I dont think my background is the candidate that HM is looking for, so I am confused that why they interviewed me"

"HR is amazing. The first company in Australia I encountered that arrange a time for phone screen and confirmation beforehand but not random call candidates at any time."

"The process was quick with all interview rounds initially scheduled in the same week. The technical interviews were adapted to real world code implementations and didn't directly relate to Leetcode style problems. The system design round was very open-ended with no definite question and highly ambiguous requirements."

"The process was quick with all interview rounds initially scheduled in the same week. The technical interviews were adapted to real world code implementations and didn't directly relate to Leetcode style problems. The system design round was very open-ended with no definite question and highly ambiguous requirements."

"The process was more rigorous than anything I'd done at other big tech companies, but the recruiter was actually accurate and helpful on what to prepare, which is rare, and I really appreciated that. A few things caught me off guard: one round included a coding test unlike anything I’d seen before. They asked me to create a voice agent with sub-500ms latency."

"I'm able to communicate while solving problem but unable to code the problem interviwers are very supportive and friendly they give hints when i stuck at last i was only able to provide pseudo code."

"The interview process went well. The recruiter was very responsive and supportive throughout the process. Had a recruiter screening call and an HM call. I am pretty sure that the HM did not like my profile, or there was no fit for the role."

"Interview process went well. It was an internal job posting. Recruiter screen went well and then I spoke with the hiring manager. He then wanted to talk to my current manager at the time to ensure I would be a good fit."

"The interviewer was nice, however kept interrupting me and push to the next step while I was answering the question. I felt the interviewer was in a rush and wanted to get certain signals by asking specific questions which threw me off a bit as I felt they kinda guiding the interview while i was doing it on my own pace."

"So far so good. Yet to complete, so cannot answer this one fully, but the HR asked me what salary you are expecting, which was slightly off-putting. I did not want to give a figure and box myself."

"The interview process was well-structured and included both technical and client interviews. The technical discussions focused on my experience with Power BI, data modeling, SQL, and real project scenarios. Overall, the interviewers were professional and gave me enough time to explain my approach. The only downside was that the feedback process took longer than expected, and communication between interview stages could have been more consistent."

"First was a recruiter screen, which went in a lot more deeper into experience than normal. Be prepared to share why shopify, deep dive in project Second was tech screen, which was sql & python. interviewer helped a lot, and it was more conversational. i think it's important to clarify a ton before writing query"

"Behavioral and Technical rounds were very friendly and relaxed. The last round was very intense and a technical deep dive into software engineering fundamentals like design patterns, code quality evaluation, etc."

"So far so good. Yet to complete, so cannot answer this one fully, but the HR asked me what salary you are expecting, which was slightly off-putting. I did not want to give a figure and box myself."

"I got into the loop through a backdoor-ish hiring manager route instead of a cold apply, and for L4+ I had to have a soft match with a team before the loop even started. My process was a recruiter alignment call, the GHA questionnaire, one phone screen, two onsite technicals, and a standard Googliness behavioral. What stood out was how collaborative and non-LeetCodey it felt, especially the phone screen, which was basically a live algorithms conversation that pushed on first principles instead of rehearsed patterns. I also learned that Google is doing more team matching before hiring committee now, because a hiring manager's statement of support can strengthen your packet if one round is only lean hire. I ended up accepting because the interview experience was consistently positive and honestly much better than how Google interviews are usually portrayed online."

"Recruiter was extremely unclear about what the rounds would entail. Thought it went fine but was hard to prepare because there wasn't really any set structure."

"It's a typical interview process with an HR screening, a LeetCode round, and a system design round. I could have done better in the system design round especially when discussing design tradeoffs."

"The hiring manager provided an overview of the team's structure, mission, and the open PM role. I shared my background and drew relevant connections to the team's focus area. The conversation included a brief informal problem-solving discussion around product success metrics and go-to-market strategy for an open-source developer platform. The call concluded with alignment on next steps, including onsites."

"What went well was that I was professional, and I’m pretty sure I communicated clearly. What didn’t go well was I wasn’t able to explain the impact."

"It was really fast, about 2 weeks total, I felt like I answered the qeustions perfectly but I didn't make it to the full loop round."

"It didn't go as expected. I did not have as many interviews as expected, and overall, the process wasn't great as the recruiter changed midway."

"Went well overall - The recruiter was really responsive and helpful. Everyone i talked to was really nice"

"It was a smooth experience and gave an overview at the phone interview round of what would be expected at the onsite interview."

"Hiring manager asked about AB testing and measurement and campaign through different channel, how to attribute."

"The process was quick with all interview rounds initially scheduled in the same week. The technical interviews were adapted to real world code implementations and didn't directly relate to Leetcode style problems. The system design round was very open-ended with no definite question and highly ambiguous requirements."

"The process was quick with all interview rounds initially scheduled in the same week. The technical interviews were adapted to real world code implementations and didn't directly relate to Leetcode style problems. The system design round was very open-ended with no definite question and highly ambiguous requirements."

"The process was technically almost trivial. They focused a lot on your communication, and how you would work with clients less on pure technical skills. The 3 rounds were all pretty easy, outside of the initial conversation they all took 2+ hours each."

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

"Went harsh and the interviewer was rude while asking the questions it was 45 mins but they extended it beyond 1 hr"

"More difficult than I had expected. The questions were new, and there was a lot more counter questioning than expected. Especially in the product design round."

"So far, the recruiter has been super helpful in terms of telling me exactly what to expect in each round."

"My interview process was thorough and gave me a good sense of both the technical and operational expectations of the role. What went well was the opportunity to discuss large-scale program delivery, stakeholder management, and how I have led complex cross-functional initiatives. In my current and previous roles, I've managed programs involving technology teams, business stakeholders, risk partners, and vendors, so I was comfortable discussing governance, prioritization, execution planning, and driving outcomes across multiple groups. I also enjoyed discussing how AI can be applied to solve business problems rather than focusing solely on the technology itself. One area that challenged me was some of the deeper AI and machine learning discussions. While I have successfully led AI-enabled initiatives and proof-of-concepts, my strength is program leadership and business value realization rather than building ML models myself. There were a few moments where I had to think carefully about technical trade-offs and model-related considerations. However, I approached those questions by focusing on how I would partner with data scientists and engineers, ask the right questions, manage risks, and ensure alignment with business objectives. Overall, I felt the process validated my strengths in delivery leadership, stakeholder management, strategic planning, and operational execution. It also highlighted areas where I can continue strengthening my AI technical depth. I left the process with an even greater appreciation for the importance of combining strong program management with a practical understanding of AI capabilities and limitations."

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

"overall smooth. Learned that they really care about full line by line understanding not just throwing things at the wall and what sticks."

"Easy normal behavioral questions and case study round was also easy cover every topics possible dont rely on AI tools"

"I went through a very Amazon-style process for a Senior Product Manager L6 role: recruiter screen, hiring manager, then several additional rounds. The whole loop was heavily centered on leadership principles and past work examples, and honestly every round felt pretty consistent in structure. The biggest thing that felt newer was the AI layer on top, where they asked how I had used AI at work and how I integrated it into product development to drive innovation or simplification. I did not find it especially tricky in the sense of on-the-spot problem solving, but they absolutely expected crisp storytelling and strong follow-through on metrics. The toughest part was being ready for sharp follow-ups on why I made certain decisions and how I arrived at the numbers I used."

"Easy normal behavioral questions and case study round was also easy cover every topics possible dont rely on AI tools"

"The screening process was pretty straightforward. It started with a few basic questions about my prior experience, relevant background, and the technical projects I had worked on. From there, the conversation focused on the projects I had mentioned, with questions about my specific contributions, the technologies I used, the challenges I encountered, and how I approached solving technical problems. Overall, the screening was fairly conversational and served mainly to assess my technical foundation, hands-on experience, and ability to clearly explain the work I had done."

"The interview was very quick. The system design is tricky but if you break down the problem into smaller parts it become feasible. The second technical conversation requires speaking out your thought process and reacting to the interviewer suggestions / conversation."

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

"Long process and no direct interactions with recruiter. Rejected despite solving R2 in several different ways."

"I did the first round interview, which was surprisingly not with a recruiter it was with a PM. He deep dived on my resume and asked detailed questions from each experience."

"They care about their leadership principles. Focus on behavioral around these core tenets. I think that Amazon is adding more AI in their OA process, so would prepare for that."

"I interviewed for an entry-level Software Engineer role after applying through my university, and the whole process was fully virtual. I did not have any OA or HackerRank up front. My loop was two technical coding rounds, then a recruiter conversation, then a hiring manager final, although I heard some people get parts of that bundled into more of a superday depending on availability. The coding rounds were standard LeetCode-style questions and felt collaborative, but the hiring manager round surprised me because it was more technical than I expected and included system design and language tradeoff questions. The process moved pretty fast overall, and I made it through the final round but did not get the offer."

"The process felt pretty unstructured and luck-based because interviewers seemed to make questions up in real time off my answers. I went through an HR screen, then a hiring manager round, then a final loop with three TPM peers from the same group. What stood out was that the final panel was not a cross-functional loop at all. It was basically the team itself, and the three peers were also managers under the hiring manager. The interviews were heavily behavioral, but they kept weaving in product knowledge, customer scenarios, ambiguity, and some light technical troubleshooting around Nvidia's domain. I did not get the offer, and one weird part was that after about a month of ghosting, recruiting came back just to add an extra peer round, then disappeared again."

"I got pulled into the process pretty quickly after a recruiter conversation, and they moved me forward without a lot of setup. The loop was recruiter, then an unusually early technical filter round on designing an agentic AI support system, then a take-home prioritization case, then three final-style interviews: case presentation plus a live metrics case, a stakeholder-management round that was really product sense, and a fit deep dive. The whole thing felt very practical and very tied to the real job of helping big customers get Sierra working, which I liked. At the same time, it felt half-hazardly put together because a lot of interviewers seemed new to the process, made mistakes in the case flow, and I basically had no reliable prep material going in."

"I got into the process through a referral and started with a recruiter call that was actually very informative. The process was five rounds for me: recruiter, a 60-minute technical screen with 30 minutes SQL and 30 minutes Python, a 30-minute behavioral, and then three loop rounds. The loop was a little different from other data engineer interviews I have done because each round combined product sense, data modeling, SQL, and Python rather than testing them in isolation. The interviewers were super helpful if I spoke out loud and asked clarifying questions, and the recruiters gave me a lot of prep material up front."

"I got into the process through a referral and started with a recruiter call that was actually very informative. The process was five rounds for me: recruiter, a 60-minute technical screen with 30 minutes SQL and 30 minutes Python, a 30-minute behavioral, and then three loop rounds. The loop was a little different from other data engineer interviews I have done because each round combined product sense, data modeling, SQL, and Python rather than testing them in isolation. The interviewers were super helpful if I spoke out loud and asked clarifying questions, and the recruiters gave me a lot of prep material up front."

"Overall, the interview process was well organized and the interviewers were professional and engaged. The questions focused heavily on product thinking, execution, stakeholder management, and communication rather than memorizing frameworks. I appreciated that the conversations felt collaborative and interviewers often built on previous answers instead of jumping to unrelated questions. The most challenging aspect was the depth of follow-up questions—they continuously probed assumptions and wanted increasingly specific examples, so it's important to have detailed stories prepared rather than high-level answers."

"The recruiter felt like there were casting a wide net when reaching out to me and only loosely checked if my background was aligned. When getting on the phone, they seemed like they were checking the box for basic requirements and I could see that it was not a good team fit when I actually met the hiring manager."

"The process was pretty standard, focused on Amazon leadership principles. Look up Exponent videos on how to answer behavioral questions."

"I thought I did pretty well for all interviews, but I think they were looking for someone with more experience in insurance and audit."

"Clear, some interviews are chiller than others. Just need to put in the work and you'll be okay. Should know all of the Meta products well enough to do an interview on them."

"The process had 4 rounds + the resume screening. First was with PM 1, second with PM 2 and the third was with the head of the product. They were asking RCA, design, situational and how independently you can work if you would be the company."

"It was ok, the interviewer was barely able to speak english well. I couldn't understand what she was saying and had to ask her to repeat many times. I even offered: "We can speak in Mandarin if needed" and the interviewer insisted in speaking in English."

"It was overall good experience. Except you have 4 rounds continuously. What went well? Asking them solid questions and being able to come up with a working solution. What didn’t go well? Not preparing enough for system design as a DevOps Engineer."

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

"The process is basically easy, the idea of interview is to check your expirences alligning to there requirements. as my role, was kept on hold led me to get ghosted on my profile."

"The interview process was straightforward not focused on any particular tech stack mostly DSA and projects."

"The overall interview process was straightforward and well organized. Communication was clear, and the interviewers were professional and respectful throughout. I had a positive experience overall, but I ultimately decided to move forward with a different offer that was a better fit for my current goals."

"Process was quick, about 3 weeks end to end but they were looking to fill quickly. Most interviews were behavioral or focused on P&L subject matter expertise. Take home project was to build a P&L and supporting deck to then present to 2 interviewers."

"Overall pretty straightforward, their interviews are pretty standard and are not there to surprise you. Recruiter and interviewers were professional."

"Pretty tough, long, and drawn out."

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

"The interview was highly rigorous but followed a format: four interviews and then five rounds of on-site. The preparation material provided by the recruiter did really help. It's always better to understand from the recruiter what is expected and then prepare accordingly."

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

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

"It was a great experience and good working with the recruiter. I would say it was mostly behavioral talking about my experience and typical PM scenarios based around that."

"Overall, the interview process was well structured and professional. I appreciated that the interviewers were friendly, engaged, and created a comfortable atmosphere, which made the conversations feel natural rather than overly formal. The questions also gave me a good opportunity to discuss my experience, problem-solving approach, and motivation."

"The recruiter was helpful. The team itself is focused on supporting data management initiatives. But the questions were not all related to it. One of the questions was to code a palindrome- coding is not something I have done for decades. I have handled massive initiatives, reporting out to CIO and CFO of a large telecom, I understand technology , but to expect coding - IMHO a bit much."

"Interviewer were all really nice. Technical portion requires to be thorough in explaining thought process"

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

"It was smooth and well-coordinated. Emphasis on your life story and how you got to where you are now, and why you are seeking out this role. Execution/product sense interview went well - it was specific to Shopify's business line, so I had to understand their user segments."

"It was quite a lengthy process. The TAT was quite long and slow as well. Didn't receive a lot of feedback to prepare better for the next rounds, but overall was a great learning experience."

"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 took almost 2 months, and all the interviews were online. I didn't have to prepare much as the questions were very relevant to the job role and not complex"

"A recruiter reached out to me on LinkedIn, and the process started with a very basic recruiter screen that was mostly just a resume walkthrough and interest in DoorDash. Round one was a two-part screen: 30 minutes of SQL and a case on cold food arriving at customers. The SQL interviewer was extremely blunt, stating that he only cared about whether I got the right answer. After that, they team matched me before the final, which I hadn't really seen before, and I got matched to the new verticals area. The final loop was four interviews across two days with one business partner and three data scientists, and most of it was product analytics case work on metrics, segmentation, funnels, and A/B testing rather than deep theory. The most difficult part for me was the hiring manager round because she started at such a high level that it was hard to know where to anchor the answer."

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

"It was quick but unclear at start what the expectations were. They were not clear on the role or what sort of candidate they wanted in the recruiter phase. Did not really know role expectations until hiring manager conversation."

"Answered effectively, they were looking more for an international experience (Asia) and the job description didn't mention"

"The process was pretty straightforward. Interviews were primarily focused on behavioural types of questions and my past work experience. I had a list of STAR stories prepared."

"It went pretty well. The interviewers were very nice, so it was easy to talk through my behavioral stories without putting on a super professional act. Coding challenges were mostly medium leetcode questions."

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

"The process was very rigorous, more than 12 rounds, met with CRO and CEO. I thought it was overly involved for an L5 role and offer was lower than expected."

"The process was very straightforward. The recruiter will help guide you and give you tips on how to prepare for the interview. They are hyper focused on their Amazon Principles and all questions will stem from that."

"The process was clear and transparent. I knew who I needed to speak with next and what the process was going to be like"

"Overall super well. First OA (LeetCode medium DP problem). Then recruiter called me. Then HM called me. Then 2 coding interviews (LeetCode Easy.)"

"Overall super well. First OA (LeetCode medium DP problem). Then recruiter called me. Then HM called me. Then 2 coding interviews (LeetCode Easy.)"

"The process was structured and fairly rigorous, with a good mix of behavioral questions and case-based problem solving. The recruiter was clear about what to expect and provided helpful guidance on how to prepare. I appreciated that the interviewers were engaged and gave me room to explain my thinking rather than focusing only on the final answer. The main challenge was the pace of some of the case discussions, where there was limited time to structure the problem and work through the analysis. Overall, though, the process felt organized and relevant to the work of a management consultant."

"Overall process was good. I had two interviews scheduled in parallel after the assessment. Interviewers were ex-googlers and helping me out where I stumbled."

"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 process was simple but slow, friendly environment, supportive panel. I got stuck during resume follow-ups"