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
- Luxoft India Software Engineer interview: engineering stack and incident handlingLuxoft India · Software Engineer · HR Screen · Jul 2026Offer
After a recruiter introduction, I spoke with HR about my background, motivations, what I had done, and what I wanted to change. A little later, I had a technical discussion with the team lead that went deeper into software development, application and infrastructure monitoring, incident handling, and technologies from prior projects. The technical conversation was about day-to-day engineering kno…
- Luxoft Software Engineer interview: tense client-style callLuxoft · Software Engineer · Other · Jul 2026
The round felt tense and difficult immediately. The interviewer came across as abrasive and one-sided, spending time explaining their own points without really listening to what I said. I got through the client-style call, but it was hard to navigate. By the end, I did not feel the difficulty was simply about my performance. The communication style made the interaction harder than it needed to be…
- Lyft Data Scientist interview: probability to causal modelingLyft · Data Scientist · HR Screen · Jul 2026
I began with a recruiter screen of about 30 minutes. It was structured: they checked the basic boxes and explained what would happen next. The process then moved through a general data-science screen on probability, A/B testing, and business sense, followed by four deeper technical rounds. Those covered coding and algorithms, optimization, causal modeling, and business acumen tied back to product…
- Macquarie Group Software Engineer interview with a rushed whiteboard discussionMacquarie Group · Software Engineer · Technical Screen · Jul 2026
The process opened with a screening step and then a technical interview. The recruiter and interviewers were professional and friendly, but the logistics got muddled. My discussion started late, then felt rushed once it began, which threw off the timing. The technical part relied heavily on whiteboarding. It was not only about writing code. I was asked to reason about engineering and architecture…
- Management Solutions Data Analyst case and partner interview experienceManagement Solutions · Data Analyst · Technical Screen · Jul 2026
The process began with a group practical-case exercise. We were given a scenario and had to solve it as a team by agreeing on and refining a proposal. After that I had an HR interview about my background, how I thought during school, subjects I liked, and how I organized myself. Then came a technical interview and, finally, a meeting with a partner. The partner stage was the most intense. It dug…
- Manpower Belgium Business Analyst interview: requirements, SQL, and OSManpower Belgium · Business Analyst · HR Screen · Jul 2026
The interviews centered on business analysis and stayed more functional than purely technical. After the recruiter step, I had a short technical screen of around twenty minutes that moved quickly through business-analysis topics. I discussed requirement gathering and BRD-style documentation, then shifted to capital-markets fundamentals and SQL queries. The interviewer seemed to want evidence that…
- Manpower Belgium Consultant interview: a verbal offer later rescindedManpower Belgium · Consultant · Jul 2026Rejected
Things moved quickly at first. Once I received a verbal offer, I expected the next steps to follow, but instead I was left waiting and felt ignored. I later learned that the offer had been withdrawn. The explanation was that my salary expectations didn't match what another candidate would accept. That was discouraging after the early progress. I came away feeling I couldn't rely on the process, e…
- Manpower Belgium Consultant interview: changing final rounds and poor follow-upManpower Belgium · Consultant · Other · Jul 2026
I thought the first interview was the final one. The interviewers discussed my experience, told me I was doing well, and said not to worry. I was then unexpectedly invited to a second interview, a one-person conversation still focused on my background. What was described as the final stage with a partner and hiring manager felt uncomfortable. The questions seemed designed to make things harder ra…
- Manpower Belgium Consultant interview: guided start and disturbing director interviewManpower Belgium · Consultant · Onsite · Jul 2026
The process began in a structured, guided way. HR clearly explained what each step was meant to assess. I had an on-site HR conversation, a team-setting evaluation, and a cybersecurity test. Having one consistent HR contact helped reduce uncertainty about expectations. The tone changed sharply in a follow-up interview with a team director. He raised his voice, behaved in a visibly outburst-like w…
- Manpower Belgium Consultant interview: recruiter, director cases and partner discussionManpower Belgium · Consultant · Other · Jul 2026Offer
There were three clear stages. I first spoke with a recruiter, then met a director and worked through case prompts. The final conversation was with a partner. The format was manageable because each meeting had a defined purpose. The early discussion was mainly about fit, the middle stage concentrated on cases, and the partner conversation seemed to bring those parts together. I knew what each ste…
- Manpower Belgium Consultant interview: rescheduled manager round and three-month waitManpower Belgium · Consultant · Other · Jul 2026Offer
My interviews were spread across several rounds, but the waiting became the difficult part. I completed the first two rounds in the same week, and a third round with the hiring manager was set for a few days later. It was rescheduled just hours before the interview, but I attended and it went fine. Afterward, I spent a long time without much clarity. I followed up regularly, yet it took roughly t…
- Manpower Belgium Consultant interview: robot lawnmower market caseManpower Belgium · Consultant · HR Screen · Jul 2026
After my first recruiter conversation, I went straight to a group business-case day. Our case concerned a robot lawnmower and what it would take to enter and win a new market. I had to work through it with others in the room and arrive at a clear approach. There was also a structured team evaluation and a cybersecurity-related test. An HR contact guided me through the whole process and clearly ex…
- Manpower Belgium Consultant interview: three online interviews and case presentationManpower Belgium · Consultant · Other · Jul 2026Offer
After applying online, I entered an assessment session that ran as one tightly scheduled block. The first meeting contained three 30-minute online interviews back to back. One was a case interview, one behavioral, and one a more technical case. Everything happened in the same Zoom session, so there was little time to reset. What stood out to me was the effort to simulate the actual work environme…
- Manpower Belgium Consultant Oracle HCM and consulting motivation interviewManpower Belgium · Consultant · Technical Screen · Jul 2026
The interview felt professional and relevant to the role. I began by discussing my background, then answered questions about Oracle HCM, my project experience, and my functional knowledge. Scenario questions tested whether I could reason through real-time situations rather than simply recite theory. The tone was relaxed and easy to follow. I was treated openly, and the conversation switched quick…
- Manpower Belgium Frontend Engineer interview: segmented process and missing follow-upManpower Belgium · Frontend Engineer · Technical Screen · Jul 2026No response
The process took about 20 days and felt unusually segmented. It began with HR calls: an initial phone screen, then a Teams call with algorithmic exercises. I then switched platforms for additional JavaScript exercises that lasted quite a while. More HR coordination followed, and the role details shifted during the process. I eventually reached a technical interview that went very well. The manage…
- Manpower Belgium Full Stack Engineer interview with React and Node.js roundsManpower Belgium · Full Stack Engineer · Online Assessment · Jul 2026Offer
I began with one online assessment and then completed three technical interview rounds. React and Node.js were central throughout, and each technical conversation involved problem-solving rather than a purely introductory discussion. The final step was an HR phone conversation. We covered compensation, availability, and general questions. The technical work called for practical thinking, but the…
- Manpower Belgium Full Stack Engineer interview: early silenceManpower Belgium · Full Stack Engineer · HR Screen · Jul 2026
An initial call went well, and I was told I would receive information about the next phase. I waited through the week, but nothing arrived. My messages went unanswered and there was no follow-up. Around the same time, I received an email about an AI-bot screening test of non-technical questions. I had completed it about ten days earlier and still had no response. The uncertainty began to wear on…
- Manpower Belgium Software Engineer interview experience: hashmap and Spring BootManpower Belgium · Software Engineer · Technical Screen · Jul 2026
The first round felt strong and deeply technical. I was asked how a hashmap works internally, how I would handle a race condition, what rehashing means, and why Spring Boot differs from the broader Spring framework. Another stage went further into Java and backend work: Java, Spring Boot, microservices, REST APIs, SQL, and system design. We also discussed my projects, problem-solving approach, an…
- Manpower Belgium Software Engineer interview: four virtual scenario roundsManpower Belgium · Software Engineer · Online Assessment · Jul 2026
My process started with a recruiter call and continued through four virtual rounds. The first was an online test. Then I spoke with someone on the team in a technical interview, followed by two rounds that were driven by scenarios rather than theory alone. In the final step, I had to handle several skills at once while two interviewers were involved at the same time. The setup felt structured and…
- Manpower Belgium Software Engineer interview: fundamentals over project historyManpower Belgium · Software Engineer · Jul 2026Rejected
I applied for a full-stack C# and Angular role, but the interview ended sooner than I expected. The first-round questions felt fairly simple, and I would call the difficulty easy. What caught me unprepared was the emphasis on core concepts rather than the projects I had built. I did not clear the interview, and my sense was that fundamentals mattered more here than demonstrating prior work. Locat…
- Manpower Belgium Software Engineer interview: HR screen, video and face-to-face roundsManpower Belgium · Software Engineer · HR Screen · Jul 2026Offer
I began with an HR screening call about my experience, notice period, and availability. HR then sent the job description, the details of where the rest of the process would take place, and what to expect next. After a few further stages, I had a technical interview by video and then three face-to-face interviews that mixed technical and business topics. One memorable question was whether I wanted…
- Manpower Belgium Software Engineer interview: junior-role mismatch and harsh toneManpower Belgium · Software Engineer · Technical Screen · Jul 2026
The technical round was what stayed with me. The questions felt far beyond what I expected for a junior role and included code concepts I did not know. When I struggled to answer, the interviewer's tone became harsh. At one point, they essentially indicated that I was wasting their time. I had expected the interview to be challenging, but their frustration made it feel both difficult and uncomfor…
- MANTECH Network Engineer referral and offer interview experienceMANTECH · Network Engineer · Technical Screen · Jul 2026Offer
Recruiter outreach was low-friction after a quick introduction. I discussed what I would do day to day and what the team expected. A strong referral in the background made the start feel easy and familiar. The technical conversation was not brutal, but it was substantive. Questions tracked the job description and tested my prior programming work, including lower-level and assembly-related experie…
- Mastercard Software Engineer interview: a bad technical round and a warm behavioral oneMastercard · Software Engineer · Technical Screen · Jul 2026
The technical interview was bad enough to overshadow the rest. The interviewer had not read my CV, gave little guidance, and either did not listen to my answers or could not understand them. It felt as though my responses were not landing. The behavioral interview was the opposite. At least one interviewer was friendly with the hiring manager, and that part had a good tone. I did not get an offer…
- Mastercard Software Engineer interview: a rushed EV design and BFS coding roundMastercard · Software Engineer · Technical Screen · Jul 2026
My Karat round was fast, high pressure, and oddly disorganized. The interviewer had a list of questions to get through, so there was little room for a natural conversation. I got a system-design question about an EV charging scenario, and they covered multiple items in a way that made it hard to go deep on the design choices. Then I had a LeetCode-style coding problem with under 20 minutes. It wa…
- Mastercard Software Engineer interview: eliminatory coding and same day later roundsMastercard · Software Engineer · Technical Screen · Jul 2026
I entered through a college placement style process. The first call was for a coding round, and that round was explicitly eliminatory. After I completed it, I finished the remaining rounds a couple of days later, all on the same day. The sequence began with the coding interview and continued with manager level and bar raiser style evaluation. Those later rounds seemed to be about more than coding…
- Mastercard Software Engineer interview: inflexible schedule and Hangman OOD taskMastercard · Software Engineer · Technical Screen · Jul 2026
The process began with scheduling friction and a rigid structure. I received about 10 days' notice and could not change the interview date. There was also a preparation session that suggested the process would be more organized than it eventually felt. In the interview, I had to implement object-oriented design for a Hangman game. The interviewer was rigid and seemed to expect particular answers,…
- Mastercard Software Engineer interview: scenario based screening rejectionMastercard · Software Engineer · Other · Jul 2026Rejected
My screening was built around hypothetical situations. It was not a friendly chat. The interviewer walked through scenarios and tested how I would think about them, with a clear focus on decision making rather than coding. The interviewer was professional and kept a positive attitude, but I was rejected in that screening round. The quick outcome surprised me because the tone had been good, and I…
- Matrix Missions Marketing Analytics Specialist interview: background fitMatrix Missions · Marketing Analytics Specialist · Other · Jul 2026
My interview was scheduled about a month after I applied. The interviewer was nice and the process felt smooth. Most of the discussion centered on my previous work experience, and nothing about the conversation was especially surprising. I did not get an offer, but it felt mainly like a background-based fit evaluation: more comfortable and conversational than stressful. Location: Hong Kong. Overa…
- Maybank Singapore Software Engineer interview with a Git technical assessmentMaybank Singapore · Software Engineer · Take-home Project · Jul 2026Offer
I started with a technical assessment that required me to build something small and upload the result to Git. After it was reviewed, I was invited to a career discussion, where I connected my previous work to the role they were hiring for. The timeline became strange after I passed the first round. I waited about three months before the next round and had to follow up with the recruiter repeatedl…
