real interview stories, told over a cup of tea ♡
Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
3935 results
- PwC India Consultant interview: calm behavioral and case flowPwC India · Consultant · HR Screen · Jul 2026Offer
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…
- PwC Software Engineer interview experiencePwC · Software Engineer · Technical Screen · Jul 2026
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…
- Qualcomm Software Engineer interview: 30-question screen and DSA thresholdQualcomm · Software Engineer · Technical Screen · Jul 2026
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…
- Qualcomm Software Engineer interview: friendly but unexpected technical scopeQualcomm · Software Engineer · Technical Screen · Jul 2026
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…
- Quality CARE India Account Executive interview: assignments and shadowingQuality CARE India · Account Executive · Jul 2026
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…
- QualityKiosk QA Engineer interview: role mismatch at weekend interviewQualityKiosk · QA Engineer · Other · Jul 2026
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…
- Quant Developer Second Round, Data Processing and Weather Forecast System DesignEngelhart · Software Engineer · Technical Screen · Jul 2026
I recently interviewed for a Quant Developer role at Engelhart, on the US Power & Gas side. The second round was two hours, split into data processing and system design. The data processing part was done in something like Colab, but it was super annoying: the file the interviewer wanted me to open wouldn't load (404), so I had to quickly download some time series + node data from a website, hourl…
- Quantiphi Machine Learning Engineer interview: unexpected computer-vision focusQuantiphi · Machine Learning Engineer · Jul 2026
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…
- Quantiphi Software Engineer interview: Unstop assessment and shortlistQuantiphi · Software Engineer · Online Assessment · Jul 2026
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…
- Quantium Data Analyst interview: technical assessment and behavioral video interviewQuantium · Data Analyst · Other · Jul 2026
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…
- Quest Global Software Engineer interview: recruiter call through HR roundQuest Global · Software Engineer · Jul 2026Offer
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…
- Quest Global Software Engineer interview: walk-in exam, Bengaluru rounds, and virtual HRQuest Global · Software Engineer · Online Assessment · Jul 2026Offer
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…
- Rakuten Full Stack Engineer interview experience: two-problem HackerRank testRakuten · Full Stack Engineer · Jul 2026
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…
- Rakuten Payment Full Stack Engineer interview: a two-problem HackerRank testRakuten Payment · Full Stack Engineer · Online Assessment · Jul 2026
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:…
- Rakuten Payment Software Engineer interview: late, unstructured role discussionRakuten Payment · Software Engineer · Jul 2026
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…
- Ramp Account Executive interview experience: 45-minute presentationRamp · Account Executive · Jul 2026Rejected
The process was long. The recruiter kept me updated, but the timeline still stretched out to roughly six interviews. The biggest demand was a 45-minute presentation that took about 20 hours to prepare. I received positive feedback during the stages I completed, so I expected a clearer ending. Instead, I got a rejection email with almost no explanation. After putting in that much time, I wished th…
- RAMP Consulting Group Account Executive interview: presentation round and email rejectionRAMP Consulting Group · Account Executive · Other · Jul 2026Rejected
The process dragged on and felt more time-consuming than it needed to be, especially because the hardest parts came near the end. I started with the recruiter and went through several interviews that led to a presentation-heavy round. Although the feedback earlier in the process had been positive, the pressure grew as I prepared the materials. The presentation was the biggest challenge. I spent a…
- Ramp Software Engineer interview: AI-assisted development screenRamp · Software Engineer · HR Screen · Jul 2026
After a recruiter reached out, I had a short screen that was mostly about how I use AI day to day. We discussed what I had built or worked on with coding assistants and answered questions directly about AI-assisted development. The recruiter did not go deeply into much else, so the AI emphasis was clear. The next step was another technical conversation with a practical coding feel. It had two par…
- Ran Out of Time on an Onsite Coding Round, Talked Through the Answer InsteadGoogle · Software Engineer · Onsite · Jul 2026In progress
Just finished my Google onsite. Something came up in one of the coding rounds, and I want to ask the folks and interviewers here on the forum how they'd read this: r2, first question: the piano-finger-movement problem (sliding window, similar to finding a monotonic interval / window coverage). First part: I wrote the code fast, dry-ran the interviewer's three test cases live plus a couple of edge…
- Raytheon Software Engineer interview: resume-depth second roundRaytheon · Software Engineer · Technical Screen · Jul 2026Rejected
The first interview was surprisingly laid-back. We spent a lot of time on OOP, including the classic four pillars, and broader software-engineering fundamentals. I explained how I thought about code, and it did not feel like they were trying to catch me out. The second round was a real step up. Several engineers and the hiring manager joined, and they examined the details behind what I had put on…
- Raytheon Technologies Corporate Headquarters Software Engineer interview: C++ resume deep diveRaytheon Technologies Corporate Headquarters · Software Engineer · HR Screen · Jul 2026Rejected
After speaking with a recruiter, I had two back-to-back rounds. The first was easygoing and focused on how I thought about code, core OOP ideas, and software-engineering fundamentals. I walked through what I had built and how those concepts appeared in practice. The second conversation was tougher. I met the hiring manager and several engineers, and they went deeply into my resume. Surface-level…
- RBC Business Analyst interview: clear behavioral panelsRBC · Business Analyst · HR Screen · Jul 2026Offer
RBC contacted me about two weeks after I applied. Once the interview was booked, the process moved quickly and stayed low stress. The early conversations were efficient, the timeline and expectations were clear, and I had time to ask questions at the end. Most of the interviews were behavioral and situational. I talked through past experience and then responded to scenarios about how I would hand…
- RBC Software Engineer interview: coding assessment and a project-focused final roundRBC · Software Engineer · Technical Screen · Jul 2026
After speaking with a recruiter, I took a technical screen with LeetCode-style problems on a coding assessment. One felt easy and a couple were medium. A little later, I had further rounds combining deeper discussion with technical evaluation. The final part focused on what I'd built and how it worked. I discussed my projects and familiar tech stack, answered targeted technical questions and then…
- React JS and Java Coding RoundsApple · Full Stack Engineer · Technical Screen · Jul 2026
React JS Coding Round In incognito mode, if you open a site like Amazon.com or Flipkart.com, what are some ways to optimize the page's load speed? Is JavaScript single-threaded or multi-threaded? What is the event loop? Does JS execute top to bottom, or the other way around? If you fetch 10M records via an API in JS and render them in a table in the UI, what problems show up in the UI? How would…
- Recalling All 5 Online Assessment QuestionsUpstart · Software Engineer · Online Assessment · Jul 2026
All 5 real questions, fully recalled. Question 1: Sum of multiples of 3, 5, 7 less than a given number For example, if the given number is 12, the multiples of 3 below it are 3, 6, and 9; the multiples of 5 are 5 and 10; and the multiple of 7 is 7 — so sum = 3 + 6 + 9 + 5 + 10 + 7 = 40 (12 itself, although a multiple of 3, is not included). Note: the original post's formatting here was garbled (s…
- Recruiter Screen With Zero Technical QuestionsOpenAI · Software Engineer · Senior+ · HR Screen · Jul 2026In progress
Got pulled in by a recruiter on LinkedIn, scheduled a 30-minute recruiter call. Writing this down right after while it's still fresh. Bottom line: it was pretty light, zero technical questions. Basically I gave my self-intro, and then she asked one question per experience on my resume without digging deep — felt like she was just confirming what's on the resume is real. Then she asked why I want…
- Reddit Machine Learning Engineer interview experience: two DSA roundsReddit · Machine Learning Engineer · Technical Screen · Jul 2026
The interview was straightforward: two data-structures-and-algorithms rounds along with machine-learning knowledge. The interviewers were kind and easygoing, and one of them in particular made the conversation feel comfortable. The format matched what I expected for the role. There were no strange surprises, just a clean sequence with a relaxed tone. I did not receive an offer, but the interview…
- Referral, Team-Specific Loop and a Visible-People Array ProblemGoogle · Software Engineer · Technical Screen · Jul 2026
Google's process looks like it has changed. I got a referral and interviewed for a specific team. The interview process was broken into 2 rounds: Round 1 a standard Leetcode problem on a text editor that doesn't compile behavioral Round 2 solutions design (similar to system design, but less ambiguous) a Leetcode problem The question I got in round 1 had two parts. Part 1: Given an array of height…
- Rejected 2 Days After a 5-Round Virtual OnsiteFigma · Software Engineer · Onsite · Jul 2026Rejected
After the recruiter call, the first round was HM + coding. The VO (final onsite) was 5 rounds — coding + 2 system design rounds + behavioral + a project deep dive. I hadn't seen the AI-flavored system design round anywhere else before. The VO was spread across 3 days, and I got rejected 2 business days after that. The HM round asked about past projects, not much technical. The first coding round…
- Rejected After a Weak System Design RoundAnthropic · Software Engineer · Onsite · Jul 2026Rejected
Phone screen: a file. Onsite: Coding: image processing. System design: prompt playground. This round was probably my weakest performance — I hadn't crammed on enough interview experiences beforehand, and I hadn't written much down in my own doc. On one or two questions I walked right into the interviewer's trap. Pay attention to some low-level details here — that's also something I hadn't taken v…
