READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 107 of 153
Interview experiences · TransPerfect
Project Manager interview at TransPerfect: no feedback after a good first round
In my first interview, I discussed my background, skills, motivation for the role, and interest. I felt I explained myself clearly and that the discussion went well. I was not selected to proceed after that round and was not given a reason. The lack of feedback made it difficult to know whether the issue was improvement, timing, or fit. I did not receive an offer; the conversation itself was posi…
Interview experiences · Providence India
Providence India Software Engineer interview: three rounds and delayed rejection
The process felt a little unstructured from the start. I completed three rounds: two virtual interviews on Teams, then an in-person interview at the office. I got feedback fairly quickly after the first two rounds, so while things were moving I had some sense of where I stood. After the third, in-person interview, communication went quiet. I waited a long time without updates and eventually recei…
Interview experiences · Providence
Providence Software Engineer interview: three rounds and silence after onsite
My Providence process felt somewhat unstructured. There were three rounds: two virtual interviews on Teams, followed by an in-person interview at the office. The first two moved quickly, and I received feedback promptly after each one, so I had a sense of where I stood while the process was active. After the final in-person round, communication stopped. I waited a long time without hearing back,…
Interview experiences · Prudential Ins Co Of America In
Prudential Ins Co Of America In Financial Analyst interview: reserves and SQL
After a recruiter touchpoint, I had four interviews in total: an initial screen and three follow-ups. The process was much harder than I expected, and the interviewers wanted answers on the spot. The questions included actuarial-adjacent Financial Analyst material such as reserves and coding-style concepts. There was also a SQL segment about joins and how they are used. The technical questioning…
Interview experiences · Publicis Sapient
Publicis Sapient Software Engineer interview: technical questions and an uncomfortable tone
The first round was a face-to-face technical interview. I could answer the questions, which were fairly straightforward. What bothered me was that the interviewer kept giggling while I spoke. It made the setting feel disrespectful and uncomfortable. I tried to stay focused and finish my answers, but the repeated reactions left me feeling I wasn't being taken seriously. The technical content itsel…
Interview experiences · PwC India
PwC India Consultant interview: calm behavioral and case flow
After a recruiter conversation, I had a normal flow combining behavioral questions with a case about how I thought. The behavioral discussion was familiar: who I was, my motivations, and how I might fit the role. There were no major surprises. The case was less about arriving at a single right answer than showing my reasoning. The people I met were calm, and I did not feel grilled or blindsided b…
Interview experiences · PwC
PwC Software Engineer interview experience
Poor communication defined my PwC process. I had to confirm the technical-interview time by email several times. After the office visit, there was no clear next-step timeline, and weeks of waiting brought no meaningful status update. When I asked talent acquisition, the reply was vague and amounted to a promise that someone would get back to me soon. After a long pause, I received an email saying…
Interview experiences · Qualcomm
Qualcomm Software Engineer interview: 30-question screen and DSA threshold
My process began with a multiple-choice screen of 30 questions. I needed at least 50% correct to move on, so the threshold was clear from the start. The next step was a technical screen on algorithms and data structures. I worked through classic sorting-style material, including moving all zeros to the end of an array, along with other DSA questions based on common algorithm patterns. It felt str…
Interview experiences · Qualcomm
Qualcomm Software Engineer interview: friendly but unexpected technical scope
After the recruiter interaction, I had two technical interviews that mixed behavioral questions about my past experience with coding and other technical prompts. The interviewers were nice, which helped. Still, some questions went beyond the scope I thought had been set ahead of time. The coding was meant to probe how I reason under constraints, not random trivia, but the mismatch meant I had to…
Interview experiences · Qualified Health
Qualified Health Software Engineer Interview Experience — A Dismissive Interviewer and Workflow System Design
I generally don't like judging interviewers or companies, but this company was pretty disgusting. Right from the start, they said that if I didn't interview well, I'd be kicked out early, in the middle of the interview. The person who came in was a technical team lead, looking arrogant. HR was out of their mind and scheduled him for two rounds in a row, one behavioral and one system design. He wa…
Interview experiences · Qualified Health
Qualified Health Software Engineer Interview Experience — An Agent/RAG System for 200 Documents per Session
System design interview question: An Agent / RAG chat system supporting uploads of 200 documents 📌 Core Problem > Design an enterprise LLM agent question-answering system that lets users upload external documents in batches within one session, up to 200 documents, and have real-time streaming question-and-answer exchanges and multi-turn interactions about their contents. 🎯 System Requirements and…
Interview experiences · Quality CARE India
Quality CARE India Account Executive interview: assignments and shadowing
The process felt excessive and stressful. Before the final interview, I completed many materials, study and training items, and hours of job shadowing. The assignments and tests later seemed disconnected from the interviews, as though the work was never referenced or acknowledged. The recruiter stayed in contact, but there was little follow-through afterward. I did not receive an offer. The main…
Interview experiences · Quality CARE India
Quality CARE India Account Executive Interview Experience: a welcoming phone screen and resume discussion
My initial interaction was relaxed. I spoke with the team by phone, answered a couple of questions, and they scheduled a more detailed interview within about a week. That next conversation was meant to cover my resume, job history, and career path. The team came across as welcoming in the way they explained the role and its responsibilities. Location: United States. Overall feedback: positive. Of…
Interview experiences · QualityKiosk
QualityKiosk QA Engineer interview: role mismatch at weekend interview
HR called to say my profile had been selected for a Lead Performance Test Engineer position. At a weekend interview, I was asked to introduce myself and then quickly told they were looking for something else. It felt sloppy because my resume and fit did not seem to have been reviewed properly. I left thinking the whole interaction could have been handled more professionally. Location: Mumbai. Ove…
Interview experiences · Quantiphi
Quantiphi Machine Learning Engineer Interview Experience: two theoretical modeling rounds
I had two rounds, and both were theoretical rather than hands-on coding. The first covered time-series and classification concepts, including deeper ML topics. I spent most of the time explaining my understanding and reasoning through how ideas applied instead of simply defining terms. The second round stayed in that same territory but felt more architectural. The questions explored how I think a…
Interview experiences · Quantiphi
Quantiphi Machine Learning Engineer interview: unexpected computer-vision focus
My first interaction focused heavily on computer vision, even though the role description had seemed more about text and agentic work. After introductions and questions about my projects, the interviewer moved into vision situations, including how to improve a model’s accuracy, plus a coding-style question involving decorators and dictionary use. The vision focus continued through questions about…
Interview experiences · Quantiphi
Quantiphi Software Engineer interview: Unstop assessment and shortlist
The process felt Unstop-driven from the start, especially for campus hiring. The online assessment had roughly 80 questions, including MCQs and a few coding tasks. I solved three coding questions in a language of my choice, and that portion felt medium to hard. Selection then moved forward according to my performance. I faced another assessment before reaching interviews. Those conversations repe…
Interview experiences
Quantitative Researcher Interview Experience — Stopping Rules and an Adversarial Card Game
A STEM postdoctoral researcher on the West Coast reports receiving a phone-interview invitation two days after applying broadly. The author found the interviewer unfriendly and describes only a brief background discussion before the technical questions. The first problem concerned when to stop accumulating rewards from repeated die rolls, with a losing outcome that erased the accumulated amount.…
Interview experiences · Quantium
Quantium Data Analyst interview: technical assessment and behavioral video interview
After applying, I received a technical assessment that took about an hour. It covered Python, SQL, R, and statistics, and felt like a focused basics check rather than an overly tricky test. A little later, I completed a behavioral video interview. It began with introductions and moved into behavioral questions where I had to support my examples, including examples of initiative. Toward the end, I…
Interview experiences · Quest Global
Quest Global Software Engineer interview: recruiter call through HR round
I started with a recruiter call and, about a week later, had a technical screen. The early conversations were mostly technical, followed by an HR round by phone. Everything was professionally organized, and updates were communicated clearly instead of leaving me guessing. The difficulty felt average: serious enough to matter, but not chaotic. I left feeling that my answers had been understood and…
Interview experiences · Quest Global
Quest Global Software Engineer interview: walk-in exam, Bengaluru rounds, and virtual HR
The process began with walk-in registration and an online written exam. I was then shortlisted for face-to-face rounds in Bengaluru and traveled there for the interviews. It felt like a sequence of filters: I cleared an initial technical round, then the next one, and eventually reached HR. The HR part was virtual, and the whole process was driven by timing. Once I was shortlisted, scheduling move…
Interview experiences · Rakuten
Rakuten Full Stack Engineer interview experience: two-problem HackerRank test
About a week after I applied, I received a HackerRank programming-test invitation. It contained two programming problems, and passing the supplied test cases was the central requirement. It felt like a simple gateway rather than a long exchange with interviewers. The question was whether I could implement the answers correctly under the test conditions. I did not receive an offer, but the process…
Interview experiences · Rakuten Payment
Rakuten Payment Full Stack Engineer interview: a two-problem HackerRank test
About a week after I applied, I received an invitation to a HackerRank programming test. It had two problems, and I needed to pass the supplied test cases to advance. The format was straightforward, but the work still felt demanding. It seemed focused entirely on coding rather than team fit or thinking about systems. I didn't receive an offer. At least the expectations were clear from the start:…
Interview experiences · Rakuten Payment
Rakuten Payment Software Engineer interview: late, unstructured role discussion
The meeting felt off from the first few minutes. The interviewer arrived several minutes late, did not acknowledge it, and gave no apology or proper greeting. They only started talking when I asked something relevant. There was little discussion of the job scope or what the role involved. The only concrete reference was a short video and a vague comment about wanting to do something similar. I ha…