READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 106 of 153
Interview experiences · Prime Video
Prime Video Software Engineer Interview Experience: broad fundamentals and leadership themes
The process had a looping structure. It began with an online assessment, then moved through data structures and algorithms, basic OOP and DBMS concepts, and Amazon leadership principles. There was also an HR interview and a low-level design component, so the process covered a broad mix rather than one narrow subject. I learned about the steps as things progressed. The leadership-principle part st…
Interview experiences · Prime Video
Prime Video Software Engineer Interview Experience: high-pressure coding and design rounds
I began with a LeetCode-style coding round and solved two DSA problems, one medium and one hard. I had to explain my thinking, cover edge cases, and give time and space complexity. The interviewer kept asking about alternative approaches and the trade-offs behind them. Next came system design. I worked through a problem resembling a scaled Amazon-style service and discussed API design, data model…
Interview experiences · Prime Video
Prime Video Software Engineer Interview Experience: leadership, coding, and system design
After applying, I completed an online assessment and then spoke with a recruiter. About a week later, I entered an onsite loop. From the assessment through the final decision, the process took roughly a few months. The loop had multiple back-to-back rounds in one day, mixing technical and behavioral evaluation. Early on, the bar raiser focused on Amazon-style leadership principles. I used STAR-st…
Interview experiences · Prime Video
Prime Video Software Engineer interview: four difficult global rounds
I had four one-hour interviews with people in different countries, and it was the hardest interview experience I had done. Even so, nobody was disrespectful. Everyone stayed attentive and respectful. The mix was technical and behavioral. One round covered troubleshooting, leadership-principle questions such as Bias for Action, and GenAI fluency. Another used coding problem solving tied to Deliver…
Interview experiences · Prime Video
Prime Video Software Engineer interview: four in-person rounds
After I finished the online assessment, I eventually heard back and was invited to an in-person set of interviews. The process was smooth, professional, and friendly. I had four rounds with a lunch break in the middle. One was purely behavioral, while the other three blended behavioral discussion with technical evaluation. The technical topics I remember were topological graph sorting, cycle dete…
Interview experiences · Prime Video
Prime Video Software Engineer interview: LRU cache and eviction
My first real screen ran longer than expected and went deep into implementation. I was asked to design an LRU cache using a hashmap and doubly linked list while keeping eviction correct. The interviewer was direct and kept probing my approach, especially the eviction behavior and the reasoning behind it. The rest of the process added more technical depth along with behavioral interviews connected…
Interview experiences · Prime Video
Prime Video Software Engineer interview: online assignment and medium coding question
My process began with a straightforward online assignment. After a wait, I was invited to one additional round. That round combined a LeetCode-style medium coding question with a short behavioral section. It felt balanced: I had to solve the problem and talk through my experience and behavioral instincts in the same session. Location: Culver City, CA. Overall feedback: positive. Offer status: got…
Interview experiences · Prime Video
Prime Video Software Engineer interview: prior Python services and module ownership
A recruiter brought me into what felt like a screen focused on experience. Rather than starting with deep technical questions, the conversation was about my previous company and what I had been doing day to day. I described my work on Python services and a module system I built, stressing how critical it was to the broader setup. That focus on my actual work history shaped the interview and did n…
Interview experiences · Prime Video
Prime Video Software Engineer interview: recruiter screen and shared-editor live coding
I first had a brief recruiter phone screen of about 30 minutes, focused on my background and résumé. I was then invited to a technical video interview with a senior engineer. That video round took around 60 minutes. After introductions, I completed a live coding challenge in a shared editor. The rest shifted to system-design basics and my past projects. It was a mix of building, explaining, and c…
Interview experiences · Prime Video
Prime Video Software Engineer interview: sliding window and debugging
The interviews started simply enough with a behavioral component and a LeetCode-style coding problem. I found the behavioral part harder than expected because it was situation based and open ended. They cared about how I would approach a scenario and what my thinking looked like. In the phone-style flow, I also had a medium-difficulty coding question that used something like a sliding-window appr…
Interview experiences · Prime Video
Prime Video Software Engineer interview: STAR stories and networking depth
The recruiter-style phone screen started with my background and became more probing as it went on. I described my current experience and projects, and each answer brought questions about why I'd made particular choices. Using STAR helped organize my stories, though the follow-ups became increasingly technical. I also answered networking questions about TCP/IP, OSPF and BGP. More structured interv…
Interview experiences · Prime Video
Prime Video Software Engineer interview: take-home and AI tool
I began with a HackerRank take-home and did not solve everything perfectly. A second task used 'AI assistance,' but the tool felt unusable to me, so it was more of a distraction than help. I still advanced to an interview with LeetCode-style questions and questions about my experience. It came too soon for me to recover from the earlier work, and I was rejected the next day. The earlier gaps felt…
Interview experiences · Prime Video
Prime Video Software Engineer interview: timed DSA and leadership loop
I had four one-hour interviews: three coding rounds and one system-design round. Each included about 25 minutes of Leadership Principles questions, so I had to manage technical work and leadership discussion within the same schedule. The DSA questions were medium to hard and involved graphs, DP, edge cases, and explaining my reasoning. My past projects came up often enough that I needed to connec…
Interview experiences · Prime Video
Prime Video Software Engineer interview: two DSA questions, leadership scenarios and waitlist
My online assessment had two DSA questions as well as multiple-choice scenario questions about leadership quality. After I was shortlisted, I had a technical online interview with two more DSA problems, and I solved them. The interviews felt organized and consistent. They were not only about abstract coding; leadership expectations and structured thinking also showed up in the questions. Even aft…
Interview experiences · Prime Video
Prime Video Software Engineer interview: two practical programming problems
My assessment was practical and a little different from standard LeetCode. I got two programming questions that increased in difficulty. The first was fairly trivial math, while the second was more interactive and open ended about what they wanted. For the second problem, I had to work out the intended requirements and then implement several functions to make the solution work. It felt as though…
Interview experiences · Procter & Gamble
Procter & Gamble Financial Analyst interview: structured examples
After a recruiter conversation, I had two more rounds. The first covered why I wanted the role and company, how I found it, my background, and follow-ups that made me be specific about what I had done and learned. The second was more CV-driven. I walked through parts of my resume and answered questions about my reasoning and experience. I needed clear examples with context, my actions, and the re…
Interview experiences · Prodapt
Prodapt Software Engineer Interview Experience: OA focused on aptitude
My process began with an online assessment meant to filter many people quickly. It was mostly MCQs on attitude and reasoning, including data interpretation, numerical reasoning, and verbal-style questions, plus one medium-to-hard coding problem. The mix felt balanced to me: the aptitude portion could be tricky if I rushed, and the coding problem could easily decide the outcome. I felt reasonably…
Interview experiences · Prodapt
Prodapt Software Engineer Interview Experience: prompt-writing assessment and prototype hackathon
After applying, I went through a structured process that began with an aptitude-style test. It combined quantitative questions, prompt writing, logical reasoning, coding at a medium-to-hard level, and chart-based data interpretation. For the prompt-writing part, I had to describe a scenario and then write an effective prompt for it. After I was shortlisted, I moved to a hackathon-style round wher…
Interview experiences · Capital One
Product Manager interview at Capital One
I started with a phone screen, then a Virtual Job Tryout, a mini case around a Capital One product, and finally Power Day. Recruiter communication and the materials made the sequence somewhat predictable, but there were enough checkpoints that mistakes still felt costly. Power Day meant four back-to-back one-hour interviews. I worked through a case tied to a product I had worked on, product round…
Interview experiences · LinkedIn
Product Manager interview at LinkedIn: compressed virtual loop
My virtual loop had five rounds with senior-director or director-level product people. Each was about 30 minutes, so the pace felt rushed and there was a lot to get through quickly. Most of the conversations were behavioral, followed by two product questions that served as a quick sense check. People were engaged, but the format left little room to explore nuance. I had expected more time to show…
Interview experiences · Revolut
Product Manager interview at Revolut
I began with a short recruiter screen where the process, next steps, and some basics about motivation were explained. Then I moved into a practical evaluation and product-focused questions. In the problem-solving round, I worked on a trading-related prompt about improving gross profit for a trading feature. I asked clarifying questions and structured the problem myself while the interviewer staye…
Interview experiences · Profound
Profound Software Engineer Interview Experience — A Recruiter Screen and an AI-Assisted Coding Exercise
This place is pretty interesting, they do AI marketing. It's kind of like doing SEO for AI's answers. There were two rounds. The first was with a recruiter, and after chatting for about 15 minutes they asked me to do a coding exercise, and I was allowed to use AI. The problem was roughly: they give you some API endpoints, with docs telling you what each API does, and in the end you pick a few of…
Interview experiences · Epic
Project Manager at Epic: four-hour collaboration and communication session
I went into Epic expecting a fairly normal interview, but the main experience was a four-hour online session centered on collaboration and communication. It started with an information component, especially since I was being considered for multiple roles. There was a separate overview for each role, so I spent time learning the scope before the interactive parts. The core activities began with a…
Interview experiences · Migso-Pcubed
Project Manager interview at Migso-Pcubed: discourteous process
The HR conversation started well and felt calm and fluid, but the manager interview was frustrating. I had the impression that the manager was discovering my CV during the call even though it seemed it should already have been reviewed. I felt spoken down to, and the meeting ended quickly when I said where I lived, which made the evaluation feel rushed. In a related part of the process, an HR mee…