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
- Zoho Software Engineer Interview Experience: a full day of tests and virtual interviews at the officeZoho · Software Engineer · Onsite · Jul 2026
I spent a full day at the office, from late morning until early evening. The setup was strange: I had to bring my own earpiece and take virtual interviews while sitting at their workplace. I'd also brought a printed resume, although it didn't seem likely to be useful. The first round was a one-hour pen-and-paper test with 20 questions: 10 about coding and 10 IQ-style questions. Next came several…
- Zoho Software Engineer Interview Experience: Aptitude, voice, technical, and HR stagesZoho · Software Engineer · Technical Screen · Jul 2026
After a recruiter call, I completed a general aptitude test to assess how I approached problems. That led to a voice assessment focused on communication, then a technical interview meant to measure my domain knowledge. The process finished with an HR round about cultural fit and my overall suitability for the role. It felt like a structured sequence in which each stage checked a different skill a…
- Zoho Software Engineer Interview Experience: delayed presentation and no updateZoho · Software Engineer · Other · Jul 2026
The process had four stages. I applied without receiving a confirmation email, completed a one-way video questionnaire, gave a presentation, and then interviewed with the India team. The presentation was scheduled for 3:30pm, but I was not admitted until 4pm. During it, the interviewer appeared distracted and kept chatting, despite the preparation I had put in. The India team interview felt more…
- Zoho Software Engineer interview: Java paper round and longer coding roundZoho · Software Engineer · Technical Screen · Jul 2026
The first round was on paper. It covered aptitude and Java output-prediction questions, with an exam-like feel. I sat with the questions in front of me, and the emphasis seemed to be fundamentals rather than tricks. The second round was a short coding segment with easy problems. It felt like a quick check of core logic, not a deep algorithms session. The third round lasted longer and asked more o…
- Zoho Software Engineer interview: written C, Java, and coding roundsZoho · Software Engineer · Jul 2026
My process started with a written, pen-and-paper round that mixed aptitude with C and some Java. It had a 10-question coding and output section, another 10 questions on IQ-style reasoning, and a full hour to complete everything. A short coding round followed with a handful of problems that felt more straightforward than the later work. The questions used common patterns such as arrays and pointer…
- Zomato Software Engineer interview with paper codingZomato · Software Engineer · Technical Screen · Jul 2026
The Zomato process began with resume shortlisting and moved straight to technical interviews. The first technical round mixed DSA, CS fundamentals, puzzle-style questions, resume details, and basic web development. That combination initially threw me because it was not a pure coding interview. The next technical round made the DSA work more intense, and I had to write code on paper rather than on…
- Zomato Software Engineer interview: a second recruiting chanceZomato · Software Engineer · HR Screen · Jul 2026
My Zomato experience was a rollercoaster. I was initially rejected, apparently because I did not have the years of experience they wanted, but a recruiter contacted me again a few weeks later with another opportunity from a different team. A team lead later became involved. The second path felt like a fresh chance that followed a similar recruiting rhythm, rather than a completely unrelated proce…
- Zoom Communications Account Executive interview: clear and timely processZoom Communications · Account Executive · HR Screen · Jul 2026
After the HR conversation, every step was explained and scheduled clearly. I was never left in limbo, and communication stayed professional and responsive. The people in the process gave clear instructions, started meetings on time, and seemed to know exactly which stage they were running. I always knew what was next, without the awkward silence that can follow a recruiter step. I did not get the…
- Zoom Communications Software Engineer interview: three months without closureZoom Communications · Software Engineer · HR Screen · Jul 2026No response
The process lasted roughly three months and began to feel inconsiderate of my time. After the recruiter touchpoint, I went through several steps that kept being moved ahead, including a presentation that required real preparation and a VP interview. The conversations felt positive, but the gaps grew harder to tolerate and recruiters became difficult to reach. I had a strong VP call. They told me…
- Zoom Communications Software Engineer interview: WebRTC gapZoom Communications · Software Engineer · Technical Screen · Jul 2026Rejected
My recruiter arranged time with the hiring manager and five engineers, so I met a lot of people in a short, back-to-back stretch. Most conversations were fine. One engineer, though, seemed to have decided what he thought before we had really started. He used less than the allotted time and did not seem interested in my background. It felt as though he had not reviewed my resume. The loop eventual…
- Zoom Video Communications Account Executive interview: clear steps, delayed decisionZoom Video Communications · Account Executive · HR Screen · Jul 2026
The multi-round process moved quickly without becoming chaotic. After an HR touchpoint, the scheduling and next steps were clear, and I was not left wondering where I stood. Everyone I spoke with was professional, and the communication felt constructive. The process kept momentum even though it was described as "length" at one point, and I felt I had handled each round well. The frustrating part…
- Zoom Video Communications Software Engineer interview: delays after a VP callZoom Video Communications · Software Engineer · HR Screen · Jul 2026No response
I was drawn into a long hiring loop that took most of three months. After the recruiter stage, I prepared a presentation and then had a VP interview, with long delays between steps. I kept getting positive signals and being told I was advancing, but I also had to chase updates, and the recruiter and hiring manager were hard to reach when I needed clarity. The VP call gave me the most confidence.…
- Zoom Video Communications Software Engineer interview: WebRTC and CodeSignalZoom Video Communications · Software Engineer · Technical Screen · Jul 2026
A recruiter scheduled a hiring-manager conversation and four additional interviews. Most of those conversations went fine, but one engineer seemed to have decided what the interaction would be before it began. He used barely any of the expected time and did not appear interested in learning about my background. That conversation came down to WebRTC protocols. I covered SIP, RTP, the ICE framework…
- ZoomInfo Software Engineer interview on projects, debugging, and codingZoomInfo · Software Engineer · Technical Screen · Jul 2026
After a recruiter call involving the hiring manager, I had a technical screen that mostly covered my projects, the role, and resume alignment. A couple more technical conversations followed, mixing coding-style problem-solving and debugging with JavaScript, Java, and SQL. The feeling was practical: they were testing reasoning, not memorization. My background stayed central throughout. I repeatedl…
- ZoomInfo Technologies Software Engineer interview with VP conversationZoomInfo Technologies · Software Engineer · Technical Screen · Jul 2026
After a recruiter call, I had a technical screen with the hiring manager. A few days later I interviewed with the SWE manager on a coding question, then shifted to resume questions about how my experience fit what they needed. The process felt structured and standard. I could feel the difference between solving the coding problem and explaining background alignment. At a later stage, I had a casu…
- Zoox Robotics Engineer interview: validation-testing problem solvingZoox · Robotics Engineer · HR Screen · Jul 2026
About a week after a recruiter conversation, I had a virtual interview with the hiring manager. I first walked through my background, then we discussed how I handle problems during validation testing: what I do when behavior is unexpected, how I debug, and how I decide which check to run next. It was a focused conversation rather than a puzzle marathon. The questions stayed close to my day-to-day…
- Zoox Software Engineer interview: a written assignment and unclear evaluationZoox · Software Engineer · Take-home Project · Jul 2026Rejected
The interview loop felt long and demanding. After a recruiter contacted me, I spoke with several hiring managers and moved into more technical work. The biggest commitment was an extensive assignment with a detailed written report and, if selected, a presentation to a panel. I felt the workload was disproportionate, especially when I couldn't see clearly how the work would be assessed. After fini…
- Zscaler Software Engineer interview: networking to system designZscaler · Software Engineer · Technical Screen · Jul 2026
After a recruiter touchpoint, I had a focused first technical round. It opened with networking questions, moved to two coding problems, and then shifted to an open-ended system-design prompt. The system-design part was the hardest to get my head around. The interviewer did not feel encouraging or helpful while I was trying to organize an approach. Compared with that, the coding portion was manage…
- A 30-Slide Case Round in One HourPinterest · Data Scientist · Senior+ · Onsite · Jun 2026
Overall, Pinterest's interviews really emphasize solid technical fundamentals. Stats, case, and coding all felt like final exams — the questions were dense and numerous, and they went really deep and got into a lot of detail. Most important thing is you could tell they had a specific correct answer in mind — even if you got most of the way there but didn't land on the exact right answer, the inte…
- A Long Python OA and Live Data ExerciseDave · Machine Learning Engineer · Technical Screen · Jun 2026
After I spoke with the recruiter, I received a fairly long online assessment. It had multiple-choice questions about the language used for the role, which in this case was Python, along with syntax questions. It also had two longer CoderPad questions. The first involved data manipulation. The second was a very long debugging problem with multiple steps. Retakes were allowed, so I could contact th…
- A Sliding Window String Question in Tech ScreeningDatabricks · Software Engineer · Technical Screen · Jun 2026
I recently interviewed for a tech screening at Databricks — a string-related question that comes up a lot on the forum. The question itself was fairly simple, and I hope it helps whoever interviews after me. The question was roughly: given a longer string and a shorter pattern, find the earliest contiguous substring in the long string such that the substring contains exactly the same characters a…
- ABC Family Software Engineer Interview Experience: Testing and validation backgroundABC Family · Software Engineer · Technical Screen · Jun 2026Offer
The interview centered on my testing background and real validation work. In discussing my projects, I covered automation and API validation, then moved into SQL and integration testing. I liked that the conversation remained connected to the work involved in the role. It did not feel as though I was being tested with random trivia. Instead, the focus was on whether I could explain my process and…
- Accenture España Consultant Interview Experience: assessment, group case, and final interviewAccenture España · Consultant · Other · Jun 2026
The selection process had several distinct stages: an individual assessment, a group discussion, a first round case interview, and a final interview. The group discussion was a consulting exercise, and the discussion itself was part of the evaluation. During that session, a staff member introduced a consulting case study and I worked through it in the group conversation. Later I had to present th…
- Accenture España Software Engineer Python frameworks and multiple coding exercisesAccenture España · Software Engineer · Technical Screen · Jun 2026
I expected a mix of discussion and hands-on evaluation, and that was what I got. I first discussed my project experience, then moved into technical questions about Python and related frameworks and concepts. We covered Django, FastAPI, Pandas, object-oriented programming, and APIs. The coding portion involved multiple Python exercises designed to test problem solving. The pace made me slow down a…
- Accenture in India Full Stack Engineer Interview: Three phone interview roundsAccenture in India · Full Stack Engineer · HR Screen · Jun 2026Offer
My process had three rounds, mostly by phone. It began with a recruiter screen lasting about 30 to 45 minutes. Next came a technical conversation with someone from a developer background, also about 30 to 45 minutes. The final round was behavioral and used the same call format. The pacing felt consistent: each call was focused and did not drag. The recruiter screen covered my background, while th…
- Accenture in India Software Engineer Interview Experience: Python and SQLAccenture in India · Software Engineer · Technical Screen · Jun 2026
The technical interview followed a familiar sequence of question sets. It opened with basic Python, including decorators and generators, then moved to the difference between lists and tuples. From there, the discussion turned to SQL ranking functions such as rank and dense rank, before ending with a flatten-list type problem. It felt more like a check of common knowledge than an attempt to probe…
- Accenture in India Software Engineer Interview: A group interview with five studentsAccenture in India · Software Engineer · Other · Jun 2026Offer
My process was straightforward. It started with a group round of five students, where the questions were basic and mostly behavioral. There was little technical probing, and it felt easier than I had expected. Because it was a group format and stayed on fundamental and behavioral questions, it did not feel like an interview that required deep specialization. The experience was low stress, and all…
- Accenture Software Engineer interview: JavaScript, React, and architectureAccenture · Software Engineer · Technical Screen · Jun 2026Offer
I started with a recruiter screen covering my experience, skills, current role, notice period, salary expectations, the position, and the project it would support. Then came two technical conversations. The first focused on JavaScript and React fundamentals, problem solving, scenario questions, and the projects I had worked on. The second went deeper into architecture and design: scalability, per…
- Accenture Software Engineer interview: Python, Django, FastAPI, Pandas, and coding exercisesAccenture · Software Engineer · Technical Screen · Jun 2026
I had a role-specific technical interview that opened with my project experience. The interviewer then went into Python and its ecosystem: Python itself, Django, FastAPI, and Pandas. They also checked my understanding of OOP and API concepts. The technical discussion quickly became practical. I had multiple Python coding exercises focused on problem solving, where the point was to see how I reaso…
- Accenture Software Engineer interview: resume discussion followed by a take-home assessmentAccenture · Software Engineer · Take-home Project · Jun 2026
I began with a structured early conversation. I introduced myself and went through my resume in detail, especially volunteer work and an internship. We discussed the programming languages and tools I had used, why I was interested in Accenture, and the company's different job levels and what comes with them. That made the call feel more like orientation than a rapid-fire screen. Afterward, I rece…
