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
- Wood Software Engineer interview: Teams competency discussionWood · Software Engineer · Jul 2026
After a recruiter conversation, I moved quickly to a Teams video interview with one interviewer. It lasted about 30 to 45 minutes and began as a competency and HR-heavy discussion, with some job-related technical questions. We talked mainly about my background, motivation, and how my experience fit their work. The tone was conversational. Technical discussion was manageable and centered on what I…
- Workday Account Executive interview: deal review and leadership interviewWorkday · Account Executive · Jul 2026
After a casual recruiter-to-hiring-manager conversation, I did a deal review with a panel. I walked through my sales experience and execution, turning my background into a clear account of what I had done and how I would drive outcomes. The next step was an interview with hiring leadership, which focused more on judgment and fit than on repeating those sales stories. The process followed a standa…
- Workday Software Engineer interview experience: REST APIs and internship leadershipWorkday · Software Engineer · Technical Screen · Jul 2026
The first step was meant to be a recruiter screen, but a technical staff member conducted it. I began with the usual behavioral introduction, and the conversation soon shifted into technical territory. They asked about my resume, REST APIs, and leadership examples from my most recent internship. Although the opening sounded as if it would be light, the later questions checked both how I communica…
- WorldQuant Quantitative Analyst interview: probability, math, and light codingWorldQuant · Quantitative Analyst · Online Assessment · Jul 2026Rejected
After recruiter outreach, I entered a straightforward early loop. I discussed previous work and what I would do in scenarios. The technical prompt was a live-coding-style question that felt fairly easy compared with what came later. Soon afterward, I completed an online round with math-focused, probability-style questions and some light coding. It was clearly about math and probability, but it di…
- Worley Software Engineer interview: standard questions, poor deliveryWorley · Software Engineer · Technical Screen · Jul 2026
The interview itself was fairly standard. It leaned on behavioral questions about what motivated me to join and how well I understood the company. I would rate the difficulty around average, but the logistics changed the tone. The interviewer arrived late. Once we started, the questions were delivered so mechanically that it never became a natural back-and-forth. That made it harder to connect th…
- WSP Software Engineer interview with CV-based technical discussion and an in-person second stageWSP · Software Engineer · Onsite · Jul 2026
After a recruiter touchpoint, I had a direct technical interview that began with a quick look at my background. There were a few behavioral questions, but most of the session became a technical discussion based on the projects on my CV. I also talked about the work they were doing and what I might handle at the beginning. The process had an initial online discussion and then a second stage in per…
- WSP Software Engineer interview: timed video assessmentsWSP · Software Engineer · Online Assessment · Jul 2026
My process began with a video interview and quickly moved to assessments. In a HireVue-style format, I recorded webcam responses to prerecorded questions. Each prompt allowed a short preparation window before a timed answer. The questions covered behavioral experience, motivation for the role, and interest in the energy sector. There was also a test-like cognitive component with timed numerical,…
- xAI Software Engineer interview: final-stage silencexAI · Software Engineer · Other · Jul 2026No response
The process ended strangely. I felt that I had done well and reached a final interview stage. Nobody promised me anything, but the momentum seemed positive. About a week and a half later, I followed up and never heard back. That lack of closure stayed with me more than anything that happened during the interviews. Even after a smooth process and a final-stage appearance, the silence left me frust…
- xAI Software Engineer interview: power-systems questions and an onsite presentationxAI · Software Engineer · Technical Screen · Jul 2026
My interview journey was compact but all over the place in what I was expected to handle. I began with a general manager conversation about the company and team, starting with my resume. That lasted about half an hour. Then I had a technical discussion on electrical-engineering power-systems topics that also lasted about half an hour. It was a crossover rather than a purely software-oriented conv…
- Xccelerated Software Engineer interview on Java, Kafka, and DSAXccelerated · Software Engineer · Technical Screen · Jul 2026
The process was pleasantly straightforward and not overly stressful. I completed roughly three to four rounds, with a positive overall tone and average difficulty. It never felt as if they were trying to trip me up. The discussions drew on software fundamentals: arrays, data structures, DSA, and my previous experience. We also covered Java and high-level Kafka design. I completed a medium-level c…
- Xebia Software Engineer interview on DSA, Java, and KafkaXebia · Software Engineer · Technical Screen · Jul 2026
The process was straightforward and not especially stressful. I had about three to four rounds, with early conversations on my background, fit, and core engineering fundamentals. Technical rounds covered arrays, algorithms and DSA, including a medium-level live coding problem. There was also a Java discussion and a higher-level Kafka conversation about system design and data flow. I gave a quick…
- Xero Product Manager interview: recruiter, manager, and team fit conversationsXero · Product Manager · Other · Jul 2026
I began with a recruiter conversation that felt like a general culture-fit screen. Shortly afterward, I met the hiring manager, where the focus shifted to whether I fit the Product Manager role itself. I then spoke with a broader group from the team. That final stage also centered on fit, both whether I could do the work and whether I would work well with the team. The process felt structured and…
- Xero Software Engineer interview: live coding and a role closed after later roundsXero · Software Engineer · HR Screen · Jul 2026
After an HR screen, most of the process involved hands-on work and live interviews. I solved a typical algorithms question in a live HackerRank round, then laid out a high-level system design and explained my decisions. A hiring-manager discussion covered behavior and team fit, particularly how I handled conflict and resolved problems. At times, I felt they were testing my collaboration as closel…
- Xylem Software Engineer interview: fundamentals under pressureXylem · Software Engineer · Jul 2026
The interview was hard and highly conceptual. I had to think deeply instead of reciting facts, and vague answers were not enough. They wanted precise answers grounded in fundamentals. I do not remember a long, step-by-step sequence of stages. What I do remember is that the difficulty stayed consistent: conceptual depth mattered more than quick problem-solving tricks. I did not receive an offer. L…
- Yardi Systems Engineering Manager interview: six-week behavioral processYardi Systems · Engineering Manager · Online Assessment · Jul 2026Offer
After the initial phone-interview outreach, I moved through a compact sequence over about six weeks: a recruiter phone call and two follow-up interviews with different team leads. Right after the first call, I received an online assessment on critical thinking and basic arithmetic, separate from the conversations. The questions were mostly behavioral. The first call focused on why Yardi and a wal…
- YASH Technologies Consultant interview: SAP MM process flowYASH Technologies · Consultant · Other · Jul 2026Offer
The interview was calm, and the main thing I remember was one significant technical question about business processes and the SAP MM module. The interviewer wanted me to explain the business process first, then connect that understanding to the relevant T-codes. It was a focused conversation rather than a broad grilling. The structure of the question made me feel that they were checking whether I…
- YASH Technologies Software Engineer interview: SAP, ABAP and database fundamentalsYASH Technologies · Software Engineer · Technical Screen · Jul 2026
The interview was difficult and closely tied to SAP work, with ABAP as the main skill. Most questions covered database concepts and SQL, and I needed to explain how those fundamentals connected with the domain. SQL came up repeatedly, along with RICEF questions. It felt much more specific than a general software interview. I was able to handle the questions, so in that sense the conversation went…
- YipitData Account Executive interview: a 15-minute screen and a sales presentationYipitData · Account Executive · HR Screen · Jul 2026
After a recruiter screen of about 15 minutes, I moved to a hiring-manager conversation and continued round by round. The process was organized, but about a week between each step made it stretch longer than I expected. The first real round was with the hiring manager. The second was a separate sales presentation, followed by a director conversation. The structure seemed intended to check fit and…
- Yochana Software Engineer Interview Experience: JavaScript, React, Node.js, and RESTYochana · Software Engineer · HR Screen · Jul 2026
After an HR screen, I had two technical rounds and then a managerial discussion. The process was smooth, with average difficulty. Nothing blindsided me, but it still called for solid problem-solving. During the technical rounds, I discussed project experience and answered questions about JavaScript, React, Node.js, REST API concepts, and database fundamentals. The interviewers focused on how I ap…
- Yochana Software Engineer Interview Experience: resume fundamentals and easy codingYochana · Software Engineer · Technical Screen · Jul 2026
The discussion began with my projects, experience, and the technologies listed on my resume. It then moved through basic programming and OOP, including an explicit OOPS question, along with SQL. There was a coding component, but it stayed easy and tested whether I could implement fundamentals. The same technical discussion included straightforward DSA prompts aimed at basic problem solving rather…
- Yochana Software Engineer interview: late Teams interviewer and tense toneYochana · Software Engineer · Jul 2026
My interview call was on Teams, and the tone felt off from the start. The interviewer joined late and then asked questions in an abrupt, almost machine-like way. I felt they were more interested in showing their own knowledge than evaluating how I solved the problem. When I could not answer one question immediately, the impatience was obvious. The interaction became colder, with an arrogant respo…
- Zalando Software Engineer Interview Experience: Mismatch on level and payZalando · Software Engineer · Jul 2026Rejected
The process soured quickly. I went through complex rounds and was rejected for a mid-level role. To me, the expectations did not match what had been communicated: they seemed to want more experience while offering less pay. The interviewer interactions felt rude and unfriendly, which made it hard to stay motivated. I left upset, with the sense that the company was not acting in good faith about f…
- Zalando Software Engineer interview: technical depth, system design, and manager debriefZalando · Software Engineer · Jul 2026
After a recruiter screen, I had an HR call about my experience, salary expectations, and a detailed explanation of the process and interviewers. I then had several technical rounds in a structured but flexible sequence: general technical depth, system design, and behavioral or managerial evaluation. Each technical round lasted about an hour. The questions tied closely to work I had described, inc…
- Zemoso Technologies Software Engineer interview: backend-heavy technical roundsZemoso Technologies · Software Engineer · Technical Screen · Jul 2026
I went through two technical rounds and an HR discussion, and things moved quickly. In one experience, an offer letter was already arriving in about ten days. The interviews were practical, covering backend work along with some frontend work. About seventy percent of the technical questions were backend-focused. I discussed Node.js middleware, REST APIs, JWT authentication, and asynchronous progr…
- Zensar Software Engineer interview: an unexpected technical evaluation during HRZensar · Software Engineer · Technical Screen · Jul 2026
The first round was a fairly straightforward technical discussion of fundamentals and object-oriented programming. Afterward, I expected a general HR conversation. Instead, that discussion became a full technical evaluation with little warning. I wasn't ready for the sudden change. The interviewer seemed impatient and unprofessional, asking questions rapidly without making much effort to understa…
- Zensar Technologies Software Engineer interview: campus assessment, interview, and HRZensar Technologies · Software Engineer · Online Assessment · Jul 2026Offer
The process began on campus and had two parts: an online assessment, followed by an interview and an HR round. It felt straightforward to moderately challenging. Nothing was especially punishing, but it was not completely trivial either. The interview followed the assessment, and the HR conversation was the final step. My impression was that the process was structured and kept moving. I did not f…
- ZF Group Software Engineer Interview Experience: An easy Teams round followed by deeper resume questionsZF Group · Software Engineer · Technical Screen · Jul 2026Offer
My process had two structured rounds. The first was a Teams interview that felt relatively easy and stayed close to C programming fundamentals and Autosar concepts. I remember answering everything correctly, which helped me relax into the conversation. The second round went deeper into the skills on my resume. The questions were no longer surface-level; they asked about the reasoning behind what…
- Zipline Software Engineer interview: project discussions and an onsite panelZipline · Software Engineer · Technical Screen · Jul 2026
My first step after applying was a short Talent Acquisition screen about my background and current work schedule. Later, I spoke with a team member in a technical session. We stayed close to my resume, discussing the thinking behind my projects and working through a technical question. The broader sequence moved from the recruiter to technical and behavioral conversations, then a scenario-based r…
- Zoetis Account Executive Interview Experience: Polite interviews followed by delayed rejection messagesZoetis · Account Executive · HR Screen · Jul 2026Rejected
I kept running into the same frustrating theme: the process began politely, but communication failed when it mattered. I had an initial recruiter call and then a hiring-manager screen. After that, I waited. I followed up and got no real acknowledgement or clear next step, only silence. In separate moments, I was told I would hear back after a resume review or another stage, but the updates never…
- Zoho Software Engineer interviewZoho · Software Engineer · Technical Screen · Jul 2026
The first stage was a screening-style test with basic MCQs, aptitude questions, and code snippets. The next stage was gated: failing to finish one section ended the process, so finishing mattered as much as solving perfectly. I then had an LLD round where I did not write code. Instead, I explained what I would build, how I would structure it, and the cases and components I would consider. The tec…
