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
- LinkedIn Software Engineer Interview: Notification-service design and an accepted offerLinkedIn · Software Engineer · Technical Screen · Jun 2026Offer
About a week after a recruiter call, I had a technical screen that surprised me with its intensity. It ran about 45 minutes and combined behavioral and technical questions. The technical work leaned toward system design: I had to reason through a notification-delivery service, including reliability and scaling, rather than just draw a high-level picture. The later interviews stayed rigorous, with…
- Lockheed Martin Software Engineer interview: four-person behavioral panel and a quick offerLockheed Martin · Software Engineer · Other · Jun 2026Offer
The process was slow to start. My application took about three weeks to move forward, but once it did, the interview part was fairly compact and organized. I had a behavioral-focused interview with a panel of four. They did not expect me to know everything. Instead, they used scenario questions to see how I thought when I did not have certainty. It felt less about finding a single right answer an…
- Lovisa Account Executive Interview Experience: a group format without enough substanceLovisa · Account Executive · Onsite · Jun 2026Rejected
The interview was designed to be social, but I left feeling unable to show what I could do. The group format began with an icebreaker and quick introductions to the interviewers. By the time it was my turn, my background had been reduced to a couple of lines. I worried that the hiring managers did not have enough detail to understand my strengths for an account executive type role. The larger set…
- Lovisa Account Executive Interview Experience: A quick retail interviewLovisa · Account Executive · Onsite · Jun 2026
The first step was quick and low pressure. I received an email shortly before the interview, and the move from application to meeting felt fast. The conversation covered who I was, why I wanted to work at Lovisa, my availability, customer-facing work, and how I would handle different situations. The manager conversation was relaxed too, with standard retail questions, sometimes only a handful of…
- Ltimindtree Software Engineer Interview Experience: a hands-on Java coding sessionLtimindtree · Software Engineer · Technical Screen · Jun 2026
The interview began directly with technical questions. I shared my screen and wrote code in a simple editor during a session that lasted about half an hour. The pressure came from having to work hands-on rather than only talk through theory. The focus was Java fundamentals in a deeper, practical form. I covered Java concurrency and transaction handling, then OOP and core Java. There were under-th…
- LTM Software Engineer Interview Experience: Aptitude test to HRLTM · Software Engineer · Online Assessment · Jun 2026Offer
The first stage was an online assessment on AMCAT. It was mostly aptitude based and entirely multiple choice, with some analytical reasoning and no traditional coding. Clearing that gate led to a technical interview. The technical conversation focused much more on my resume, background, and how I would work in the role. The interviewer led the discussion, seemed to know the work well, and was dir…
- Lyft Software Engineer Interview Experience: A transactional recruiter screenLyft · Software Engineer · HR Screen · Jun 2026
The recruiter screen set a rough tone immediately. I came in for a backend engineering role, but the conversation felt overly transactional, as though boxes were being checked instead of discussing the technical impact I had delivered. I shared concrete examples from past work, including architecture decisions, optimizations, and engineering scenarios. I expected the conversation to connect those…
- Manpower Belgium Frontend Engineer interview experience: technical and IQ assessmentsManpower Belgium · Frontend Engineer · HR Screen · Jun 2026
My process was fast and smooth. It started with an HR interview that included a few technical questions. After that I completed two online assessments, one technical and one IQ-focused. Then I had a technical interview followed by a manager interview. I passed the earlier steps, and the manager round was the final stage. There was no offer at the end, but the process was organized and easy to fol…
- Manpower Belgium Software Engineer Interview Experience: broad fundamentals amid poor schedulingManpower Belgium · Software Engineer · Technical Screen · Jun 2026Offer
The interviews focused on fundamentals, although the process quality did not feel great. The technical rounds began with detailed questions from my resume about projects, internships, and technical contributions. From there, the discussion expanded into OOP, data structures and algorithms, and language-specific concepts. On the backend, I was asked about APIs, databases, server-side architecture,…
- Marks & Spencer Account Executive Interview: Shop-floor exercise and role playMarks & Spencer · Account Executive · Onsite · Jun 2026
I arrived early and was first sent to the shop floor to identify a few things that could be improved. Afterwards I went upstairs for a more formal interview. The setting felt welcoming, and the conversation moved quickly from who I was to what I could bring to the role. They asked about my background, what I knew about the brand, customer service, teamwork, and how my previous experience related…
- Matching Queries Against a Log StreamDatadog · Software Engineer · Technical Screen · Jun 2026
The first-round problem was query and log stream matching. I was given a stream containing two message types: Q: xxx was a query. Each query needed a unique ID, and I had to output an acknowledgment. L: xxx was a log. For each log, I had to output the IDs of all queries that it completely matched. The example input was: The expected output was: My approach was to use a HashMap
- Maybank Singapore Software Engineer interview experience: restructuring delayMaybank Singapore · Software Engineer · Senior+ · Technical Screen · Jun 2026
The process began with a lack of clarity that never got resolved. I never received a proper job description. Although I was scheduled for a senior software engineer track, the interviews felt pitched more at a lead level. I completed two technical rounds, and an HR round was confirmed. Then the process was abruptly put on hold because of internal management restructuring. Long gaps stretched to a…
- Medtronic Software Engineer interview experience: project architecture and DSAMedtronic · Software Engineer · Online Assessment · Jun 2026Offer
The process began with an online assessment, then a technical round that covered systems thinking and data structures. I was asked to describe the architecture diagram for one of my projects, so it felt less like pure coding and more like explaining how the parts worked together. The technical questions then shifted to DSA. The interviewers cared a lot about how I reasoned through problems and wh…
- Meesho Software Engineer interview: SDE-1 problem solvingMeesho · Software Engineer · Technical Screen · Jun 2026
I interviewed for an SDE-1 full-stack role at Meesho after applying through the career portal and being shortlisted. The first round focused on problem solving and felt like a standard technical screen. One detail I kept being reminded about was logistics: I needed a backup internet connection for the interviews. It did not change the technical content, but it affected how I prepared and how I ma…
- Mercor Software Engineer interview with concurrency and RedisMercor · Software Engineer · Jun 2026
My interview was brief, around 30 minutes. The interviewer gave me some code and asked me to make it more robust. He nudged me toward concurrency and distributed-systems thinking, including how to process CSV data and coordinate synchronization with Redis. I felt behind because I was still early in graduate school and didn't have deep experience with that specific concurrency and distributed-syst…
- Mercor Software Engineer interview: fast sorting questions and code reviewMercor · Software Engineer · Technical Screen · Jun 2026
One interview felt unusually fast and almost dismissive. I spoke with an engineer who asked quick, random questions, including the slowest sorting algorithm and its time complexity. I then did a quick code review of two functions. The whole decision seemed to happen within about five minutes, and the engineer appeared eager to wrap up after roughly ten. Another round was also very straightforward…
- Meta Data Scientist interview: SQL, product sense, and the full loopMeta · Data Scientist · Technical Screen · Jun 2026Rejected
A recruiter contacted me first, and I then went through what felt like a standard path from screening to the loop. The initial technical screen covered SQL and product sense. The questions were very much about connecting data work to business decisions. A couple of weeks later, I moved into the full loop. That loop had four rounds: analytical execution, analytical reasoning, technical skills, and…
- Meta Software Engineer interview: 45-minute coding and leaderboard designMeta · Software Engineer · Technical Screen · Jun 2026
After I was scheduled, I had a coding round built around speed and follow-through. I worked through two LeetCode-style problems in 45 minutes and focused on optimization. At least one had a follow-up that required improving the solution instead of stopping once it worked. The onsite loop added coding, behavioral discussion, and system design. The design question involved a leaderboard-style compo…
- Micro1 Software Engineer fifty-minute Zara AI interviewMicro1 · Software Engineer · Other · Jun 2026Offer
My process was quick and centered on a Zara AI interview. The question difficulty felt easy to moderate, and the whole interview took about fifty minutes. It started with a short mock interview and then moved into the technical round. The AI's pacing felt straightforward compared with more intense stress-test interviews. It handled the mock portion first, followed by technical problems that didn'…
- Micro1 Software Engineer interview with the Zara AIMicro1 · Software Engineer · Other · Jun 2026Offer
I interviewed in a live meeting-style setup with the Zara AI, and the process felt time-boxed from the start. I had to answer questions within a limited window, knowing that I was being recorded and that the recording would be shared with recruiters. I had to stay focused throughout because the AI could miss parts of what I said. When the questions came, the interaction seemed responsive to impor…
- Microsoft Product Manager recruiter screen, hiring manager, and big-data silenceMicrosoft · Product Manager · Jun 2026No response
After I applied, I was contacted for an initial screen. The recruiter part felt a little unstructured but not off-putting, more conversational than scripted. I was told that multiple candidates were being interviewed for the role, which made the process feel uphill from the start. I reached a hiring-manager round and focused mostly on big-data topics. Additional rounds were supposed to follow, bu…
- Microsoft Software Engineer interview experienceMicrosoft · Software Engineer · Online Assessment · Jun 2026
I took a LeetCode-style test with three problems, then went through three interviews with different managers. Each manager interview ran for about an hour and combined a coding problem with behavioral questions. The format made it clear they were weighing both problem solving and how I described my thinking and experience. The test came first, and each manager conversation added a human layer tha…
- Microsoft Software Engineer Interview Experience: A demanding opening testMicrosoft · Software Engineer · Technical Screen · Jun 2026
Before I could speak with a recruiter, I had to clear a technical test. It was challenging enough to feel like a real filter and about what I expected from Microsoft. Once I passed that hurdle, the rest of the process moved forward, but I did not receive an offer. The test set the tone immediately, and the bar felt consistent with Microsoft's reputation. My main takeaway was that proving I could…
- Microsoft Software Engineer Interview Experience: LRU cache and C++ vector implementationMicrosoft · Software Engineer · Take-home Project · Jun 2026
My take home coding work and later interviews were more system oriented than quick algorithm exercises. I worked on two DSA problems: an LRU cache with a higher level design angle, and a vector related implementation using arrays, pointer arithmetic, and heap allocation in C++. The interviewers were friendly and fun to talk with, which made it easier to think out loud during implementation. The s…
- Microsoft Software Engineer interview: passed OA then declineMicrosoft · Software Engineer · Online Assessment · Jun 2026Rejected
My process started with an OA for a role that had the same title but a different job code. I fully passed both OA questions, but there were still more rounds afterward. The first interview was 45 minutes, followed by a loop with three separate 45-minute rounds on different days. Even though I felt prepared and thought I had done well, the process ended without an offer. I waited for several month…
- Microsoft Software Engineer Interview: Two SDE2 online assessment problemsMicrosoft · Software Engineer · Online Assessment · Jun 2026
I started with an online assessment for a Software Development Engineer 2 role. It had two DSA questions, one medium and one harder. I got full marks on every test case for the medium problem. I came close on the hard one, but it was not perfect. After the OA, I waited and tried to work out whether I might get a callback. I had no further detail from the process; the assessment result was the onl…
- Milwaukee Tool Software Engineer Interview Experience: one manager conversation and no follow-upMilwaukee Tool · Software Engineer · Other · Jun 2026No response
I had one interview, a conversation with an engineering manager about the role and where I would fit. It went well enough that they said they would reach out to continue the process, but I never heard anything after that. I did not follow up because I had already decided I was not very interested in continuing. The experience felt unfinished, as if I had been left mid-stream instead of formally r…
- Mirakl Account Executive Interview Experience: AI video, HR, manager, and team fitMirakl · Account Executive · HR Screen · Jun 2026Offer
The process began in an unexpected way: my first step was a video interview with an AI. It served as an early check on whether my motivations made sense and whether my story was coherent. I then had a more traditional HR qualification conversation about my profile and skills. Next I spoke with my future manager in a more strategic discussion. We covered my ability to build automation systems and…
- MongoDB Customer Success Engineer interview: customer-meeting presentationMongoDB · Customer Success Engineer · HR Screen · Jun 2026
My process took a couple of months. It began with an HR screen, followed by a hiring-manager interview on the role and typical customer-success questions, then a peer interview covering databases and cloud-native infrastructure. The last stage was a presentation challenge framed as a customer meeting. I had a prep call before presenting to a fictitious customer panel, with interviewers playing di…
- Morgan Stanley Software Engineer interview: difficult introductory questionsMorgan Stanley · Software Engineer · Jun 2026
My first introductory round was rough from the beginning. The questions felt difficult right away. What unsettled me was the interviewers' response: my answers did not satisfy them, and it seemed as though they wanted very specific responses instead of exploring my reasoning or allowing the discussion to develop. I could not make sense of the intent. The questioning felt as if it was constructing…
