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
- Google Business Analyst data interview with DSA and modeling pressureGoogle · Business Analyst · Technical Screen · Jun 2026Rejected
My first substantial technical step was data-heavy and more intense than I expected. The data interview included DSA and modeling questions, and the bar was reasoning under pressure, not just getting a final answer. One example looked like a simple arithmetic statement at first but was actually wrong, so I had to deal with that confusion while staying accurate. The interviewer continued with inte…
- Google Software Engineer interview: language-library technical roundGoogle · Software Engineer · Technical Screen · Jun 2026
A recruiter first reached out, then I had a scheduled technical round. Early on, the interviewer focused on a very specific library connected to the language I had chosen. I could not fully remember the details on the spot, and that threw me off. The process then expanded into several technical rounds: DSA interviews, a high-level design discussion, and a Googliness-style behavioral interview. Th…
- Guidewire Software Software Engineer interview experienceGuidewire Software · Software Engineer · Online Assessment · Jun 2026
The process started with an initial online-assessment screening and had four rounds in total. After the screening, the remaining interviews were face to face and felt like a sequence rather than unrelated one-offs. In the middle technical rounds, they wanted clear thinking and trade-off explanations, not just working code. I had a system-design-style discussion where I reacted to a scenario and i…
- Hexaware Software Engineer Interview Experience: an uncomfortable virtual interviewHexaware · Software Engineer · Jun 2026Rejected
My first impression of the Hexaware virtual interview was not good at all. I joined the online interview with my screen shared, and I was thrown off when the interviewer did not turn on their own camera. That small thing quickly set the tone for the rest of the session. When I got stuck trying to understand a question, the interviewer showed little patience and would not really walk through it wh…
- Hit Counter Question, Rejected Over an Edge CaseDatabricks · Software Engineer · Technical Screen · Jun 2026Rejected
The question was hit counter. This question isn't very clearly documented on the boards in terms of the exact requirements and follow-ups, so let me share what I remember as a reference. They started by giving 3 APIs and said I could ask clarifying questions: put(key, value) get(key) get_load() # this gets the QPS for get and put separately — I actually wrote two separate ones for each The requir…
- Hit With a Brand-New Question, Failed on BQInstacart · Software Engineer · Onsite · Jun 2026Rejected
A totally new question I'd never seen before, and I was the one who got hit with it. I feel like every question in this loop had a pretty large amount of code, so everyone should practice a lot. I think I failed because of the new question and the BQ — I prepared for BQ the Amazon way, but in practice it felt more like a casual conversation, and I wasn't quite ready for that. Coding round: the cl…
- HM Accused Me of Using AICommure · Software Engineer · Technical Screen · Jun 2026Rejected
I applied online, and about a week later a recruiter reached out and set up a 30-minute meeting. It was pretty standard stuff — they just introduced the role. A bit more than a week after that, they reached out again: the next step was the HM interview. The HM's camera and mic both seemed to be having issues. The video was really blurry and the audio kept cutting in and out. He started by introdu…
- Honeywell Technologies Software Engineer interview experienceHoneywell Technologies · Software Engineer · Online Assessment · Jun 2026
I started with an online assessment, then had a technical interview that covered coding, my projects, and core subjects. After the technical part, I went through a managerial and HR round that focused more on how I work with people: teamwork, communication, and my career goals. What made the process feel different was the balance. It did not feel like a purely technical elimination round. It felt…
- Hyland Customer Success Engineer Interview Experience: Three rounds and an unclear decisionHyland · Customer Success Engineer · Technical Screen · Jun 2026
I completed three interview rounds, and the format stayed fairly consistent throughout. Each technical round lasted somewhere between around 30 minutes and nearly two hours. After all three, it looked as though the process would continue with a larger shortlist. What happened next threw me off. They selected a group of interns, then abruptly changed course and chose a smaller subset, specifically…
- Imperial College London Research Analyst interview: presentation and competency discussionImperial College London · Research Analyst · Other · Jun 2026Offer
The process felt rigorous but friendly. After the initial steps, I had a round with a presentation and a competency-style discussion led by two interviewers. They were personable and the mood was positive, even though the questions were clearly testing whether my background matched the role. The interview lasted about forty-five minutes. They asked a mix of competency and knowledge questions tied…
- Infosys Finacle Software Engineer Interview Experience: AI-led first roundInfosys Finacle · Software Engineer · Other · Jun 2026
My earliest round was led by an AI interviewer, and the structure was obvious from the start. Instead of a free-form conversation, the system asked a main question and then chose a follow-up based on my earlier answer. It seemed to be testing both technical grounding and my ability to reason and respond in real time. Those follow-ups made it more than a questionnaire. The AI used what I had said…
- Infosys Finacle Software Engineer Interview Experience: Deep technical questions and delaysInfosys Finacle · Software Engineer · Technical Screen · Jun 2026Offer
The process was more intense than I expected. The early indication was that the technical rounds would go deep into my resume, and they did. I was asked about OOP principles, DBMS, core OS concepts, DSA, and SQL. DSA and SQL kept coming up, and the questions built on one another instead of ending after a single prompt. I went through a couple of interview levels. First came LeetCode-style medium…
- Infosys Finacle Software Engineer interview: Salesforce trigger exerciseInfosys Finacle · Software Engineer · Technical Screen · Jun 2026
I went through a short virtual interview that was still fairly technical and focused on Salesforce development. It moved from basic concepts into harder areas around Apex, LWC, and how the pieces fit together. I had to reason through integration scenarios, triggers, and related admin and runtime concerns instead of just defining terms. The session lasted about half an hour, and I had to write a t…
- Infosys Finacle Systems Engineer Interview Experience: Coding then managerial roundInfosys Finacle · Systems Engineer · Technical Screen · Jun 2026
The process was simple and felt more like a filter than a string of endless rounds. I had two main interviews: a coding round followed by a managerial round. I heard that a test can sometimes be included, but my own process stayed with that coding-then-managerial sequence. The overall difficulty felt manageable. I kept hearing internally that referrals mattered, which made the experience feel par…
- Intuit Management Consultancy Frontend Engineer interview experience: AI workflow and take-home reviewIntuit Management Consultancy · Frontend Engineer · Online Assessment · Jun 2026
After I applied, the Uptime Crew process felt structured. It began with a proctored online assessment with three parts: a LeetCode-style DSA problem, SQL, and Bash. The Bash section was harder than I expected, and the DSA question was around the difficult end of medium to hard. I had a limited window to start, somewhere around a week/90-minute timing, and the proctoring made it feel high stakes.…
- IQVIA Consultant Interview Experience: interview content overshadowed by inconsistent follow-throughIQVIA · Consultant · Online Assessment · Jun 2026
What I remember most is the chaos around the process rather than the questions. After recruiter contact, scheduling took weeks of chasing, and the call eventually ran late. It ended positively, with an indication that I would move forward once the team returned from vacation. After that came a long run of generic follow-ups that did not explain what was happening. The process included recruiter a…
- Jane Street Quantitative Analyst interview experience: probability progressionJane Street · Quantitative Analyst · Jun 2026
I went through math-focused interviews that started with easier questions and became harder. The rounds centered on probability. Early questions established the fundamentals, then the difficulty increased. Each round also began with a behavioral check-in, which set expectations before the technical work. In a similar run, I had three phone interviews along the same probability track. The first co…
- JFrog Customer Success Engineer interview experience: Docker and Linux background discussionJFrog · Customer Success Engineer · Technical Screen · Jun 2026
After a recruiter conversation of about 30 minutes, I met with a hiring manager for roughly 40 minutes. We talked through company policy and what the day-to-day job would involve, including shifts and the kinds of work that came up regularly. It was structured, and I left with a clearer sense of the expectations. The first technical round was a detailed conversation about my background and projec…
- Jones Lang LaSalle Financial Analyst Interview Experience: a one-hour fit-focused meetingJones Lang LaSalle · Financial Analyst · Onsite · Jun 2026
After applying through the company portal, I was shortlisted and heard from HR fairly quickly. The face-to-face stage moved fast after that. HR scheduled an in-person interview with a finance manager and director. It took about an hour and felt straightforward rather than especially technical. Most questions were behavioral and tied to my past experiences. They wanted to understand how I had hand…
- Josh Technology Group Software Engineer interview: unstable internet during an on-site OAJosh Technology Group · Software Engineer · Online Assessment · Jun 2026Rejected
The process began with a standard online assessment, but the setting changed how it felt. I had to take the OA at a college venue, where the facilities were limited and the internet fluctuated enough to distract me. The test itself followed a typical structure of programming fundamentals and code-related questions, but those logistics made it harder to concentrate. After clearing that stage, I ha…
- Karat Software Engineer interview with live DS&A and platform feedbackKarat · Software Engineer · Technical Screen · Jun 2026
After I received the initial email with the process details, I was invited to a technical interview. It felt straightforward. I joined a live video call and worked through a live data structures and algorithms test. Once the time was up, I received feedback on my performance. Overall, it was a good, well-run experience. I also liked that the setup felt modern and smooth, so I could focus on the w…
- Kiewit Corporation Software Engineer recruiter, superintendent, and double in-person interviewKiewit Corporation · Software Engineer · Jun 2026Offer
This process was more intense and segmented than easier conversational screens I had experienced elsewhere. It began with a recruiter call, then a Zoom conversation with a local higher-up superintendent. From there, I had a double in-person interview with a project manager and a project sponsor, who was a senior, high-impact person. The people were wonderful, and the process was organized and pro…
- Klaviyo Account Executive: Mock Discovery Call and In-Person PanelKlaviyo · Account Executive · HR Screen · Jun 2026
My process began with a recruiter screen and then moved to a hiring manager interview. Most of the questions focused on my experience, along with situational prompts such as walking through a time I handled a specific situation. The recruiter and hiring manager conversations had a similar structure, although the recruiter also explained what to expect and how success would be measured. The next s…
- Koch Financial Analyst Interview Experience: values, behavioral examples, and EnglishKoch · Financial Analyst · Technical Screen · Jun 2026
The process began with a recruiter touchpoint, followed soon by a technical screen that surprised me because it did not focus much on hard technical questions. Most of it was behavioral. It felt as though the interviewers were looking for something very specific, although I could not tell exactly what they were targeting. Later conversations included many questions about company values. The conve…
- Koch Minerals & Trading Financial Analyst Interview Experience: fit and communication over technical depthKoch Minerals & Trading · Financial Analyst · Jun 2026
The rounds felt designed to test fit and how I expressed myself more than raw technical knowledge. The office was very professional, and the interviewers were respectful and welcoming. Still, the questions made me feel they were looking for something specific in the kind of analyst I would be. Behavioral prompts were a large part of the process. I described situations I had handled in ways that a…
- Konrad Group UX/UI Designer Interview Experience: Portfolio and design challengeKonrad Group · UX/UI Designer · HR Screen · Jun 2026
I began with a short, easygoing HR or recruiter chat. We discussed why I was interested in design and the company, my salary expectations, and what I did outside work. It was friendly and conversational rather than an interrogation; it felt as though they wanted to understand me. Next, I presented my portfolio in person and answered behavioral questions as I walked through it. That was followed b…
- L'Oréal Marketing Analytics Specialist Interview Experience: Initial fit screenL'Oréal · Marketing Analytics Specialist · HR Screen · Jun 2026Rejected
The process began with an HR interview framed as an energy check. HR would decide whether they liked my vibe before taking me further. I would have met the rest of the team afterward, but I did not get past the first conversation. This was more about whether the discussion landed well than about role-heavy content. It was clear that the first round was intended to filter for interpersonal fit. Th…
- Lazard Business Analyst Interview Experience: two short alignment conversationsLazard · Business Analyst · Other · Jun 2026
I started with a short recruiter chat, about half an hour, about my background and why I was interested in the firm. The recruiter also asked whether I intended to relocate. It felt like a quick alignment conversation rather than a deep technical screen. About a week later, I had another half-hour discussion with a portfolio manager. We again covered my background and motivation, then moved into…
- LeetCode Rounds Then a RAG System DesignMicrosoft · Machine Learning Engineer · Onsite · Jun 2026
Round 1 The first round was a classic array-processing problem: LeetCode 56 (Merge Intervals). Overall it wasn't too hard — mostly testing fundamentals. The core idea is to sort by interval start, then walk through and merge the overlapping ranges. What actually separates candidates is how "Pythonic" the code is and how you handle edge cases — things like sorting elegantly with a lambda, or handl…
- Lenovo Account Executive Interview: Recruiter call and two-person team interviewLenovo · Account Executive · HR Screen · Jun 2026Offer
After I applied, I had an easygoing recruiter conversation that moved quickly, with clear next steps. It helped me understand the broader company and role while they assessed whether the fit worked from both sides. Later, I had an online interview with two team members. The discussion centered on my match for the position, but the feedback was not specific. It threw me off that they seemed not to…
