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

  • Meta Product Manager interviewMeta · Product Manager · Technical Screen · Jul 2026

    After the recruiter stage, I had two timed, structured parts: product sense and product analytics. Product sense required a clear framework, while analytics tested how I interpreted and used data. The interviews resembled common mock formats, where I had to walk through an approach rather than have a free-form discussion. I used the framework I had prepared, but the analytics bar did not match wh…

  • Meta Software Engineer Interview Experience: A fast coding loop with system design and values checksMeta · Software Engineer · Technical Screen · Jul 2026

    The process began with a recruiter call, then continued through several rounds that mixed fast coding, system design, and behavioral checks. The coding loop was intense. I had two data-structure and algorithm problems in a tight window and had to keep moving even when the clock made every step feel consequential. I remember needing to solve problems quickly while also justifying my approach. Syst…

  • Meta Software Engineer Interview Experience: Easy and medium LeetCode with time-space trade-offsMeta · Software Engineer · Online Assessment · Jul 2026
    Offer

    After a recruiter reached out, I started with an online assessment. Then I moved into the technical loop. The first coding sequence had two LeetCode problems, one easy and one medium. I had to explain my approach thoroughly, including why I chose certain data structures and what the time and space trade-offs were. The next rounds continued in the same coding-focused style through virtual meetings…

  • Meta UX/UI Designer interview: full loop canceled before scheduleMeta · UX/UI Designer · Other · Jul 2026

    I began with a recruiter phone screen and then met the hiring manager. The hiring manager told me to prepare for the full loop, so I organized around completing the rest of the process. The full-loop interview was canceled one day before it was scheduled because the role no longer existed. I never reached the later rounds. Having completed the early steps and prepared for more, I felt disappointe…

  • Meta UX/UI Designer interview: peer rounds followed by a bench waitMeta · UX/UI 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…

  • Micro1 Software Engineer interview experience: AI-guided questionsMicro1 · Software Engineer · Jul 2026

    I began with an assessment, then completed a fully AI-guided interview. The virtual interviewer asked about my programming experience, software engineering fundamentals, and earlier projects. No live person spoke with me. The format was direct. The bot parsed what I said and used that to choose the next question, either confirming my understanding or asking for more detail. That made it feel less…

  • Micro1 Software Engineer interview: a hostile AI screen with no dialogueMicro1 · Software Engineer · HR Screen · Jul 2026

    My first Micro1 screen used AI and felt genuinely hostile. The bot rushed through prompts, skipped ahead when I paused, and mispronounced terms in technical questions. It felt less like an interview and more like an automated quiz. What bothered me most was the lack of room for a back-and-forth. I could not really ask questions or clarify anything. Instead, the interaction narrowed into rapid-fir…

  • Micro1 Software Engineer interview: AI assessment instabilityMicro1 · Software Engineer · Other · Jul 2026

    My interview opened with an AI-driven conversational segment before moving into technical tasks. It felt more like an assessment than a human conversation. The sections tested whether I could reason clearly, explain tradeoffs, write code, and debug under time pressure. I worked through live coding and debugging, code-optimization tasks, and API questions. The questions were not vague in the way s…

  • Micro1 Software Engineer interview: backend and database depthMicro1 · Software Engineer · Technical Screen · Jul 2026

    The Micro1 interview began with React and Node.js fundamentals, then quickly moved into practical backend topics: worker threads, task processing, queues and message services, and using idempotency to make operations safe and repeatable. The discussion continued into distributed systems and PostgreSQL internals, including transactions, isolation levels, concurrency control, query optimization, an…

  • Micro1 Software Engineer interview: fast Zara AI technical sequenceMicro1 · Software Engineer · Technical Screen · Jul 2026

    My first interaction with Micro1 was a Zara AI interview that ramped up quickly. The technical questions became difficult fast, and the flow was so tight that I had little time to pause before the bot advanced. If I did not answer in time, it moved to the next item. It felt as though I had to go through every section. In a stack-related set of questions, I could not effectively skip ahead and had…

  • Micro1 Software Engineer Zara AI interview with rapid technical questionsMicro1 · Software Engineer · Other · Jul 2026

    My first interaction with Micro1 felt like a pure Zara AI interview, and it ramped up quickly. I faced technical questions whose difficulty increased fast. The pace was so tight that I barely had time to pause and think before the bot moved on. If I didn't respond in time, it went straight to the next question. What caught me off guard was having to go through every section. When a topic didn't c…

  • Micron Memory Malaysia Sdn Bhd Software Engineer interview: a short critical-thinking screenMicron Memory Malaysia Sdn Bhd · Software Engineer · Jul 2026

    The interviewer spent about twenty minutes on my background, then used the rest of the short conversation for critical-thinking questions. There was very little technical material, although I did have to explain a simple circuit with a voltage supply, resistance, and a capacitor. The logic-focused portion threw me off because it did not feel very engineering-specific. The staged, high-volume form…

  • Micron Memory Malaysia Sdn Bhd Software Engineer interview: projects, troubleshooting, and shift expectationsMicron Memory Malaysia Sdn Bhd · Software Engineer · Onsite · Jul 2026
    Offer

    The process was organized and centered on my resume and how I worked. I began with a recruiter screen, then met engineering interviewers and later the hiring manager. I also had a hands-on onsite discussion lasting from half an hour to about an hour. The atmosphere was fairly casual, and the interviewer explained what the job would actually involve before asking about past projects and problem so…

  • Micron Technology Software Engineer interview: concise answers in a fast-moving processMicron Technology · Software Engineer · HR Screen · Jul 2026

    After a recruiter call, I quickly moved to a short live interview. I spent about twenty minutes explaining my experience, then answered critical-thinking questions. The technical material was simple, but I still needed to explain the fundamentals clearly: a circuit involving a voltage supply, resistance and a capacitor, plus at least one probability-style question. The high-volume hiring format f…

  • Microsoft Applied Scientist interview with a last-minute virtual cancellation and long HR waitMicrosoft · Applied Scientist · Jul 2026

    The interview itself seemed technically normal at first, but the communication around it became the hardest part. I was called for a virtual interview, then received an email minutes before it was due to start saying it was canceled. They said they would reschedule, but I never received a new time. Later, I did manage to complete an interview, but it still did not feel like there was closure. HR…

  • Microsoft Data Scientist interview: modeling and experiment designMicrosoft · Data Scientist · Technical Screen · Jul 2026
    Offer

    The loop was intense and technically demanding, with work that felt closer to real modeling than trivia. After a recruiter-style step, I discussed an ML project and the trade-offs in evaluating it. We focused on classification with asymmetric costs, and I explained SHAP in the context of what I'd built. I was surprised to get a precision-and-recall question very close to one I'd practiced. Later…

  • Microsoft Data Scientist interview: timed HackerRank assessmentMicrosoft · Data Scientist · Online Assessment · Jul 2026

    Most of my process was a timed online technical assessment. It had several HackerRank-style questions and a predefined window of around an hour to finish everything. There was little conversational interviewing beyond that. It felt like a fast evaluation of technical problem solving, with very little room to recover from a missed question. I did not receive an offer. The straightforward but tough…

  • Microsoft Software Engineer Interview Experience: Binary search first, then graph problemsMicrosoft · Software Engineer · Online Assessment · Jul 2026

    I had an online assessment first, followed by two live coding interviews. The experience was pretty middle-of-the-road for me: not relaxed, but not chaotic either. The first coding interview had a medium LeetCode-style binary-search problem, while the second shifted to graphs. I also discussed general software-development principles and problem-solving. The interviewers were professional and easy…

  • Microsoft Software Engineer interview: correct solutions that still timed outMicrosoft · Software Engineer · Technical Screen · Jul 2026

    My technical rounds were mostly classic DSA questions, but efficiency mattered most. I could tell they were judging more than whether my logic worked. My approach also had to be optimized enough to pass the last few tests. Time limits were part of the challenge, and if I wrote something too slow, the end of the test suite failed. The process stayed focused on performance. The stressful part was n…

  • Microsoft Software Engineer interview: dynamic programming and scheduling algorithmsMicrosoft · Software Engineer · Technical Screen · Jul 2026

    This was an on-campus process with two rounds on the same schedule. First I got a simple dynamic-programming question about counting ways to reach a target count. The second round shifted to scheduling algorithms: FCFS, SJF, and round-robin. They were not presented as trick questions. I felt reasonably comfortable with both the DP logic and the scheduler implementations. I did not get an offer. M…

  • Microsoft Software Engineer interview: HackerRank queue with two stacksMicrosoft · Software Engineer · Online Assessment · Jul 2026

    My Microsoft process began with a HackerRank online assessment. After that came three live coding rounds on HackerRank, each with some behavioral questions mixed in. The behavioral questions were direct: why Microsoft, a time I failed, and how I learn a new skill. For coding, I had problems such as building a queue with two stacks and filtering an array efficiently. They also asked about data str…

  • Microsoft Software Engineer interview: nerves on an easy opening questionMicrosoft · Software Engineer · Technical Screen · Jul 2026

    My experience began with an initial screening round that felt generally easy. I got nervous early and bottled up on the first easy question, which caught me off guard because the overall vibe did not match how tense I felt inside. The process stayed consistent with that: the first stage was meant to be approachable and did not seem designed to trick me. Still, I learned that an easy question can…

  • Microsoft Software Engineer interview: quick take-home follow-up and manager interviewsMicrosoft · Software Engineer · Jul 2026

    I heard back quickly after applying and again after the take-home step. Then I went straight into three interviews, all with managers. The overall vibe was professional and easy to talk to. The conversations felt thoughtful instead of stressful. It seemed they wanted to understand my work and how I communicated, and I left each session feeling that I had covered the points they were listening for…

  • Microsoft Software Engineer interview: respectful manager and technical roundsMicrosoft · Software Engineer · Technical Screen · Jul 2026

    I had two Microsoft interviews: one with the hiring manager and one technical interview. Both were respectful and kind, which made the process less stressful than the usual hiring loop. The recruiter was responsive, so the wait did not drag on. The manager conversation was professional and supportive, and the technical interview had the same tone. It felt like a discussion rather than a harsh cro…

  • Microsoft Software Engineer interview: story-based medium-hard roundsMicrosoft · Software Engineer · Online Assessment · Jul 2026

    After clearing the OA, I had three technical rounds. The questions were story-based and ranged from medium to hard. Not every interviewer required me to fully execute code; some were more interested in whether I could explain an approach clearly. The interviews were demanding because I had to stay precise about both the algorithm and my reasoning while the conversation moved quickly. I was trying…

  • Microsoft Software Engineer interview: three 90-minute loop interviewsMicrosoft · Software Engineer · HR Screen · Jul 2026

    An HR call set up a packed loop day with three interviews, each 90 minutes long. The first two were live coding rounds with LeetCode-medium problems and a strong emphasis on clean code. The third was a behavioral interview with the department manager. The 90-minute blocks made the day longer than a typical loop and required sustained focus across coding clarity and later communication. I did not…

  • Microsoft Software Engineer long interview timeline experienceMicrosoft · Software Engineer · Jul 2026

    The most surprising part of my Microsoft process was its length. It took at least two months from beginning to end: about one month of interviews, then another month waiting for the decision. There were multiple rounds assessing different skills. Interviewers gave hints, and I had to keep track of them and adjust my approach while time was running. I did not receive an offer. The month of uncerta…

  • MicroStrategy Software Engineer interview: office start and virtual roundsMicroStrategy · Software Engineer · Online Assessment · Jul 2026
    Rejected

    The first round was face to face in the office, which gave it a different feel from the later virtual interviews. The technical questions stayed moderately difficult, leaning on solid foundations and scenario-based reasoning instead of obscure edge cases. I had a timed assessment before the technical discussions, then technical conversations, more meetings with a leadership and management perspec…

  • Mirakl Account Executive interview: peer behavioral rounds and case studyMirakl · Account Executive · Other · Jul 2026
    Offer

    I made contact through LinkedIn, then had an initial conversation with the recruiter and a meeting with my potential manager. The process moved into peer interviews focused heavily on behavioral STAR-style questions about how I had handled situations in the past. Those rounds felt structured and values-oriented. I left each peer interview thinking the panel was trying to understand both my experi…

  • MITRE Software Engineer interview: recruiter alignment, presentation, and panel questionsMITRE · Software Engineer · Technical Screen · Jul 2026

    I started with a short recruiter screen that confirmed my resume matched what I said I had done. It was a straightforward conversation about my background and what I wanted, rather than a highly formal step. Once that alignment was clear, I moved to the next stage fairly quickly. The next round combined a panel-style technical interview with a presentation. I organized my thoughts for the present…