Katkat

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

  • MBDA Software Engineer interview: month between HR and recruiter meetingMBDA · Software Engineer · Other · Jul 2026

    I started with an HR phone call. About a month later, I met the recruiter on site at the Plessis-Robinson location. Every exchange I had with the people involved was positive. The meeting was structured but did not feel hostile or overly pressuring. They seemed to be trying to get a clear read on my fit. The month-long gap made the process feel slower than the interactions themselves. Location: L…

  • MBDA Software Engineer interview: several-hour assessment centre processMBDA · Software Engineer · Technical Screen · Jul 2026

    I went through a full assessment-centre process that took several hours. It began with an icebreaker in a small group of applicants, which set a calmer tone. From there I had a personal interview with one person and later a group task. The assessment included looking at a partnership proposal for a new collaboration. They wanted to see how we thought through the situation together. There was also…

  • MBDA Software Engineer interview: values and CV Teams conversationMBDA · Software Engineer · Other · Jul 2026

    I had a friendly MBDA Teams call centered on whether my values aligned with the company. They asked what I could bring to the team and to MBDA, and they also asked about my CV. The tone was more probing than I expected because values and motivation drove the conversation. I left feeling that they took fit seriously, so the call felt more focused than a generic screening. Location: United Kingdom.…

  • Mcdonald'S Global Office In India Software Engineer interview experience: timed codingMcdonald'S Global Office In India · Software Engineer · Online Assessment · Jul 2026
    No response

    I applied online and received an email invitation for a virtual interview. In that session, I solved an easy LeetCode-style problem involving pairs or arrays. It was manageable and did not feel especially long or brutal. There was also a nontechnical behavioral round about my experience and resume. That interviewer looked for critical thinking, communication, and some familiarity with data analys…

  • McGraw Hill Software Engineer interview: verbal engineering discussionMcGraw Hill · Software Engineer · Jul 2026

    After a brief recruiter chat, I had what was scheduled as an engineering-manager discussion, although a senior developer led it. It was a one-hour, verbal technical round with no live coding. We discussed Terraform, CI/CD strategy, GitHub Actions, observability, and day-to-day production support. I also described a simple education-domain schema for teachers, students, classes, and assignments, i…

  • McKinsey & Business Analyst interview: case pace and opaque decisionsMcKinsey & · Business Analyst · Online Assessment · Jul 2026

    I applied online and waited for the Solve-style assessment and next steps. I advanced after the pre-screen, but the connection between the test and interview decisions wasn't clear to me. Even when I asked later, I couldn't fully understand the scoring and matching. At one stage, it seemed that both my assessment and resume affected whether I moved forward. The live interviews paired personal exp…

  • McKinsey & Business Analyst interview: partner-level case jumpMcKinsey & · Business Analyst · Other · Jul 2026

    The process grew harder as it went. I had two relatively easier first-round interviews, often with Business Analysts, on cases such as market entry and profitability. The final partner rounds used much harder strategy cases and less familiar story lines, so I had to adapt quickly. They also asked about my resume and experience before moving into the cases. The schedule felt tight, with cases taki…

  • McKinsey & Business Analyst interview: preparation support, personal experience and casesMcKinsey & · Business Analyst · Other · Jul 2026

    The recruiting team gave me a lot of preparation support. I could access resources, join online sessions and use help groups to understand the stages and expectations. The process was long, but I knew how the interviews would work. The rounds paired a personal experience interview with case work. I could ask about the interview format beforehand, which reduced some of my uncertainty about the cas…

  • McKinsey & Business Analyst interview: Solve score and unexplained rejectionMcKinsey & · Business Analyst · Online Assessment · Jul 2026
    Rejected

    I applied for a Business Analyst role and went straight to the McKinsey Solve online assessment, a gamified problem-solving test of roughly 80 minutes. About two weeks after finishing it, I received a rejection email without reaching a live interview. I asked for my score. A couple of days later, they said I was in the 10th decile with a 537 score. That made the rejection hard for me to understan…

  • McKinsey & Business Analyst interview: supportive case conversationsMcKinsey & · Business Analyst · Other · Jul 2026

    I expected a stressful process, but the case interviews felt tightly run and well supported. The interviewers were professional and seemed genuinely interested in helping me do well. It was intellectually demanding without feeling hostile. The cases and discussions had structure, and the interviewers gave detailed answers when I asked questions. They were unusually open about the realities of the…

  • McKinsey & Consultant interview: case rounds, fit, and respectful offer processMcKinsey & · Consultant · Other · Jul 2026
    Offer

    I had a very good process, beginning with friendly and professional interviewers. It started with a phone screen, then two case-interview rounds with a partner and a senior associate. Near the end, there was a final round covering fit and problem-solving skills. It was a direct way to understand how I thought, how I explained my reasoning, and how my experience related to day-to-day challenges. I…

  • MD Anderson Cancer Center Research Analyst interview: team presentationMD Anderson Cancer Center · Research Analyst · HR Screen · Jul 2026

    I started with a recruiter-style call that covered basic background questions. Then I had a technical-light Zoom interview with the whole team. The format was simple: everyone joined the call, I gave a presentation of about ten minutes, and they asked follow-up questions about my experience instead of pushing into deep technical problem solving. I was surprised by how few technical questions ther…

  • Medpace Research Analyst hybrid-policy mismatch and clinical-trial questionMedpace · Research Analyst · New Grad · HR Screen · Jul 2026

    The process began with a mismatch in expectations. In an earlier phone conversation, I was told about a hybrid policy that did not match what came up later in the in-person part of the process. From my side, the experience felt frazzled. The interviewer seemed disconnected, and I got the impression that they did not have complete answers to my questions. The timeline was roughly three weeks: firs…

  • Meesho Software Engineer interview: structured real-work questionsMeesho · Software Engineer · Other · Jul 2026

    I applied for a Software Developer role at Meesho and went through a well-structured interview sequence, although it did not lead to an offer. The interviewers were professional and grounded, and their questions seemed tied to real engineering work rather than abstract trivia. The flow stayed organized throughout, and it was easy to engage with the team while still being pushed on relevant subjec…

  • Meltwater Account Executive interview: general group stage without sales depthMeltwater · Account Executive · Other · Jul 2026

    I went through an early group stage with several people at once. The conversation stayed general and did not go deeply into sales topics such as running a pipeline, what I would sell, or why Meltwater specifically. It was more about broad communication and fit, and I had to think aloud with others present. The process felt average in difficulty but not tailored to an Account Executive role. I lef…

  • Merck Software Engineer interview: long final campus dayMerck · Software Engineer · HR Screen · Jul 2026

    After I applied online, the early response was quick: an HR phone screen followed by a video interview with the hiring manager. I was then invited to a final-round onsite at the Rahway campus for top candidates. That day included about 6 to 7 interviews and a 45-minute presentation. The manager conversation came roughly 5 to 6 weeks before the onsite, and it took several more weeks to hear back.…

  • Mercor Software Engineer interview canceled before three algorithm prompts could be answeredMercor · Software Engineer · Jul 2026

    The process was chaotic from the start. My first interview was canceled, and when I finally got a second one, it ended extremely quickly, in around five minutes. Before it started, I was given a Google document with three data-structures and algorithms prompts, including BFS and two pointers. I tried to take a couple of minutes to get oriented, but the interviewer canceled before I could write an…

  • Mercor Software Engineer interview with a three-section HackerRank assessmentMercor · Software Engineer · Online Assessment · Jul 2026

    After I applied, the first step was an online HackerRank-style assessment with three sections. It covered data and algorithms, data pipelines, and SQL-style questions, so I had to move between very different problem types one after another. A short time later, I had a 30-minute conversation with the hiring manager. That discussion felt mostly behavioral, with some technical back-and-forth mixed i…

  • Mercor Software Engineer interview with resume-tailored AI questionsMercor · Software Engineer · Other · Jul 2026
    Offer

    I went through an interview flow that was entirely AI-based, and I found it surprisingly efficient. The AI generated questions tailored to my resume and the job description, and the experience felt almost human, more like a real conversation than a cold checklist. The questions covered system design prompts and coding and code-practice topics, and I usually had enough time to think through my ans…

  • Mercor Software Engineer interview: a three-part HackerRank-style OAMercor · Software Engineer · Online Assessment · Jul 2026

    After applying online, I received an online assessment on HackerRank-style tests with three sections. It covered data structures and algorithms, data pipelines, and SQL questions. Not long afterward, I had a 30-minute conversation with the hiring manager. It was mostly behavioral, with a few technical discussions mixed in. It felt like a standard early loop, with the OA setting the tone and the r…

  • Mercor Software Engineer interview: AI-generated resume-tailored questionsMercor · Software Engineer · Jul 2026
    Offer

    My interview was conducted entirely through an AI platform. It generated questions tailored to my resume, and I found the process efficient and positive. Even though it used AI, it did not feel like a cold or mechanical interaction. The questions sounded natural, and the exchange felt more human than I expected. It was comprehensive for the time it took but still moved smoothly. I felt the AI pac…

  • Mercor Software Engineer interview: five-minute interview with BFS and two-pointer questionsMercor · Software Engineer · Jul 2026

    Scheduling went badly from the start. The first interview was canceled after I had already been set up for it, and the second lasted only about five minutes. During that short session, I received a Google Doc with three data structure and algorithm questions, including BFS and a two pointer approach. I needed a couple of minutes to get oriented, but the interviewer canceled before I could write a…

  • Meta Data Engineer interview with timed SQL, Python, modeling, and product scenariosMeta · Data Engineer · Technical Screen · Jul 2026

    After recruiter outreach, I went through a structured set of rounds built around speed and clear problem solving. The recruiter call covered role fit and process details. Then came a technical screen with several SQL and Python tasks under tight time limits. I had to keep working until each task was fully resolved with the expected results, while the interviewers kept returning to my thought proc…

  • Meta Data Scientist interview: timed SQL cases and A/B experiment designMeta · Data Scientist · Technical Screen · Jul 2026

    After a recruiter and screening step, I faced a fast, high-pressure set of SQL and case tasks. The Python and SQL round covered SQL mechanics and quick reasoning, including common data structures, CASE statements, and window functions. The pace stood out because the window closed as soon as it was time for the case study, so accuracy and efficiency both mattered. The case work was more demanding…

  • Meta Logistics Software Engineer interview: screen, loop, and system designMeta Logistics · Software Engineer · Technical Screen · Jul 2026

    After the recruiter conversation, I had a technical screen with two coding questions. The next stage was an onsite-style loop with a behavioral discussion, two more coding questions, and system design. The recruiter was accommodating when scheduling was difficult. The coding prompts were LeetCode-like, with follow-ups that required me to explain and revise my approach. System design was about tra…

  • Meta Machine Learning Engineer interview with a conversational-assistant design and declined offerMeta · Machine Learning Engineer · Onsite · Jul 2026
    Offer

    The process dragged on longer than I expected. It felt drawn out from the early weeks onward. I went through screenings on core ML knowledge, including attention and its variants, before later stages shifted into more high-pressure technical work. Onsite day was intense and tightly structured. In the system-design round, I had to build a conversational assistant and include safety measures. That…

  • Meta Machine Learning Engineer interview: paperwork after technical roundsMeta · Machine Learning Engineer · Technical Screen · Jul 2026

    The technical rounds were not the main issue for me. A friendly, detailed recruiter screen covered the role and its expectations, then I moved into familiar LeetCode-style coding interviews with screen sharing. The coding itself did not feel unfair. I handled the problems and kept the normal pace while explaining my approach. Even so, I did not get an offer, and the reason I heard was paperwork r…

  • Meta Platforms Software Engineer interview: coding and system-design loopMeta Platforms · Software Engineer · Technical Screen · Jul 2026

    After the recruiter call, I had a technical screen with two coding questions, then an onsite-style loop with behavioral, two more coding questions, and system design. It was structured to test both range and depth under time pressure. The coding was LeetCode-style. I needed to explain the approach, write clean code, and handle follow-ups and optimization. The interviewers were not hostile, and so…

  • Meta Platforms Software Engineer interview: screens, loop interviews, and leadership expectationsMeta Platforms · Software Engineer · Technical Screen · Jul 2026
    Rejected

    I started with two screening conversations and then entered a set of loop interviews that matched the company's familiar style. The technical work centered on LeetCode-style problems, and the system design could go deep. I was surprised by how much the interviewers varied, even with a similar format. Some offered hints, while others expected me to keep going independently with very little guidanc…

  • Meta Product Designer interview: peer rounds followed by a bench waitMeta · Product Designer · Technical Screen · Jul 2026

    I went through three peer interview rounds with technical and behavioral parts. The format matched what I had seen for this type of role, and the technical questions lined up with the resources I had found beforehand. After those rounds, I expected a decision to move forward. Instead, I was told to wait while they decided which team or role might fit me. I understood it as something like being he…