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

  • Capgemini Consultant interview: SAP TRM and HR practicalitiesCapgemini · Consultant · Technical Screen · Jul 2026

    After a recruiter stage, I had a technical screen followed by HR. The technical discussion focused on SAP TRM, its related business process, and questions about payments and repayments. The interviewer wanted to know whether my prior experience mapped to that module. The next conversation was resume driven and calmer. It included aptitude and logical-reasoning work with many memory-style question…

  • Capgemini Consultant interview: technical, manager, and compensation roundsCapgemini · Consultant · Technical Screen · Jul 2026
    Offer

    I went through a clear three-round process. The first was a technical round where the interviewer asked direct questions to probe my technical knowledge. Then I had a manager round that focused much more on how I worked day to day, including process and work discussion, plus scenario questions about how I would handle real situations. The final step was an HR round covering compensation details,…

  • Capgemini Software Engineer interview: business cases, Excel, and VBACapgemini · Software Engineer · HR Screen · Jul 2026

    The process was concise: a recruiter phone screen, a technical conversation about a Java or React project, and a behavioral final round. Each stage lasted about half an hour, so it felt designed for quick decisions. The technical part relied on business-case questions and knowledge outside typical coding. I discussed basic Excel and Power BI, Excel and VBA, and how I handled business problems thr…

  • Capgemini Software Engineer interview: fast project-based technical roundCapgemini · Software Engineer · HR Screen · Jul 2026

    After a recruiter screen on basic requirements, notice period, and salary expectations, I had a short, fast technical interview. It covered core coding and problem-solving with some system-design concepts, and moved quickly enough that I had to keep my explanations crisp. I discussed a project, then answered design and implementation questions about challenges, technologies, and how the pieces wo…

  • Capgemini Software Engineer interview: policy-based rejectionCapgemini · Software Engineer · HR Screen · Jul 2026
    Rejected

    My process included technical interviews, document verification, background verification, and a final HR discussion. Those verification steps made the journey longer and more formal than ordinary interview back-and-forth. After clearing each stage, I expected a positive decision, but my candidature was rejected under hiring-policy criteria. I felt I had cleared the work in front of me, while the…

  • Capgemini Software Engineer interview: selection without offer letterCapgemini · Software Engineer · Technical Screen · Jul 2026
    Offer

    I cleared technical rounds and then had an HR conversation about salary expectations. One stage was face to face, L1 and L2 were held on the same day, and HR confirmed that I had been selected. I was told to expect an offer letter within a few working days. More than a month passed without an offer letter. I called and messaged, but neither recruiting nor HR responded. The interviews themselves h…

  • Capgemini Software Engineer interview: ServiceNow scenario troubleshootingCapgemini · Software Engineer · Technical Screen · Jul 2026

    This was technical from start to finish, but unlike a generic software-engineer screen. It began on Microsoft Teams and focused on a specific toolset and real scenarios rather than theory. My questions centered on ServiceNow ITSM, scripting, and troubleshooting. Because the prompts were scenario-based, I had to work out the expected behavior rather than recite definitions. Some were long and not…

  • Capital One Business Analyst interview with a mini case and Power DayCapital One · Business Analyst · HR Screen · Jul 2026

    After an initial recruiter call, the process moved quickly to a mini case and then straight into a Power Day. It felt standard for a Business Analyst track: an HR conversation about what to expect, followed by quantitative case-style questions in the mini case. The Power Day was the heavier part, with several back-to-back interviews. During Power Day, I had case interviews and a product-focused r…

  • The hardest part for me was a case interview where I initially struggled to understand the question. The interviewer guided me through calculating the answer across a series of steps, but I could not fully follow what they were asking. I kept clarifying and asking questions. The case was about launching a new game with free and paid visibility in the market. Even with the guidance, it was tense b…

  • Capital One Business Analyst interview: graph and percentage assessmentCapital One · Business Analyst · Online Assessment · Jul 2026
    Rejected

    My process ended at the online assessment. My background leaned toward analytics, but the assessment was much more about business and math than analytics problems. The preparation material I found did not seem to match the format I received. There was a small set of questions on graphs, data interpretation, percentage calculations, and reasoning beyond plugging in numbers. I worked through them,…

  • Capital One Data Analyst interview: Power Day cases after a data challengeCapital One · Data Analyst · HR Screen · Jul 2026
    Offer

    After an HR call, I had a technical screen that combined technical work with business problem solving. There was a coding test focused on SQL and Excel data management, then a data challenge where I analyzed the material and presented what I found. The process took about two months from beginning to end, longer than I expected because I kept waiting for the next step. Power Day had four rounds an…

  • Capital One Data Analyst interview: SQL and final business caseCapital One · Data Analyst · Online Assessment · Jul 2026
    Rejected

    After a recruiter screen, I took an online technical test and then went through rounds that felt much more business heavy than advertised. The test had one basic SQL question and a larger set of data-manipulation multiple-choice items. The first interview mixed business-case work with a very quick SQL component, and a later technical round had easy LeetCode-style questions. The mismatch showed up…

  • After a recruiter screening call, the process quickly moved into a mini case on a Capital One product. I received charts, interpreted the data from an A/B-testing perspective, and then zoomed out to a UX review where I made recommendations from what I saw. About a day later, I had Power Day, a long series of interviews that mixed product skills, product discovery, and heavier case work. One part…

  • My final stage was Power Day: four back-to-back video interviews. Two were consulting-style cases. The other two focused on product work, including a product I'd led and a product-sense case study. The product prompt involved designing an experience related to the DMV. I had to connect the user journey, decisions and trade-offs into a clear plan. The day felt like an assessment of how I framed pr…

  • Capital One Product Manager interview: math and product decisionsCapital One · Product Manager · Technical Screen · Jul 2026

    After an initial one-on-one, I spent a full day in back-to-back meetings, each about an hour long. The split surprised me: two rounds were essentially math problems, while the others assessed how I made product decisions and thought about product work. One interviewer put it this way: if someone is so strong at math that becoming a developer or moving toward technical architecture makes more sens…

  • This was one of the smoother interview experiences I had. The people I spoke with felt genuinely strong, and I liked how they talked about the role and the team I would be working with. The conversations gave me a real sense of the company culture and did not feel rushed past the context. The tone stayed positive, and I left understanding what the job involved. I did not get an offer, but I would…

  • Capital One Product Manager interview: withdrew after recruiter mismatchCapital One · Product Manager · HR Screen · Jul 2026
    Withdrew

    I only reached the early stage because the recruiter call put me off. It felt disconnected from product-manager work and the roles being hired for. I came away thinking the person did not understand what Product teams did, and they discouraged me from taking part in a rigorous full-day process if I did not feel like a strong fit. There was a brief attempt to pull me back into the process, but I h…

  • Capital One Software Engineer interview: CodeSignal OA under time pressureCapital One · Software Engineer · Online Assessment · Jul 2026

    My process was dominated by a CodeSignal OA where time pressure mattered a great deal. I completed the assessment and earned full points on three of the four questions, which was a relief, but the clock was already working against me by the time I reached the last one. The OA had four DSA questions in 70 minutes. I fully solved questions 1, 2, and 4 and got top marks on each. When I reached quest…

  • I interviewed in a standard four-interviews-in-one-day format. After earlier rounds, I had four one-hour sessions that were evaluated together: two technical interviews, one behavioral interview, and one case interview. The technical interviews used LeetCode-style problem solving. The behavioral session focused on my experience and how I described my work. The case interview was about walking thr…

  • I began with a direct recruiter conversation about the role, day-to-day work, and how the company viewed it. Soon after, I had a technical interview for sales support. The questions covered day-to-day work, competing demands, communication with different teams, pressure, and pace. The interviewers were calm and objective, and I felt they wanted to understand my reasoning. I could explain my analy…

  • CATERPILLAR Software Engineer interview: French STAR responseCATERPILLAR · Software Engineer · HR Screen · Jul 2026
    Offer

    After a recruiter step, I had a panel interview with three developers. The atmosphere was friendly, and they were helpful when I got stuck. The format relied heavily on STAR-style behavioral questions, including one that I had to answer in French. There were also a couple of technical questions and questions about my resume and situations from past roles. The technical side was not extreme, but t…

  • Rejected

    SWE VO System design: design ChatGPT. At first the interviewer said not to worry about scale and no need to persist anything. Later they asked why use SSE instead of WebSocket, and also asked how to optimize the frontend so that long conversations can still render well. Coding: all new questions I had never seen. I used Python. Vector Store The problem is to implement a simplified vector store th…

  • Checkout Software Engineer interview with system design and valuesCheckout · Software Engineer · HR Screen · Jul 2026

    I had a smooth sequence of rounds that felt more like conversation than a test. The stages moved quickly, and everyone I met was especially friendly. The route was HR first, then a hiring-manager discussion about my background and experience. After that came a system design interview and a values interview. The overall difficulty felt average, while the tone made it easier to explain my thinking…

  • Chime Product Manager interview: intensive loop and missing recruiter follow-upChime · Product Manager · Technical Screen · Jul 2026
    Rejected

    I started with a recruiter screen that felt fast and responsive. After meeting the hiring manager, the pace stayed high. I was moved into the next round on such a tight timeline that they wanted me to begin the technical interview before I had much chance to prepare. After that second round, the process went quiet. I followed up, got no reply from the recruiter, then received a standard rejection…

  • CIBC Software Engineer interview experienceCIBC · Software Engineer · Onsite · Jul 2026
    Offer

    I first spoke on Microsoft Teams with the recruiter and a senior manager. That conversation felt straightforward. I then had an in-person round in downtown Toronto, including whiteboard work where I used simple if statements to talk through the logic and how I would approach the problems. I was surprised that there was no live coding. The emphasis was on laying out my thinking clearly in front of…

  • Cisco Software Engineer interview: a broad and difficult online assessmentCisco · Software Engineer · Online Assessment · Jul 2026
    Rejected

    The OA was difficult from the beginning and covered far more than I'd expected. It mixed multiple-choice questions, coding and several subjective scenario sections. One section used short passages followed by questions I had to answer in words. Switching from coding to those judgment-based tasks was immediately challenging. The coding was hard too, requiring both speed and correctness. My backgro…

  • Cisco Software Engineer interview: assessment followed by weeks of silenceCisco · Software Engineer · Online Assessment · Jul 2026

    My process began with a Hackerrank-style exam. It included several easy-to-medium LeetCode-style problems and a simple SQL question, so it felt manageable compared with harder online assessments I had heard about. After I finished, I heard nothing for weeks. The silence eventually ended without further progress, so the outcome felt less like the result of an interview conversation and more like a…

  • Cisco Software Engineer interview: fair questions and disputed cheating concernCisco · Software Engineer · Technical Screen · Jul 2026
    Rejected

    I entered the interviews confident because the questions matched my strengths: backend concepts, Java, system design, and coding. The interaction felt positive, and I believed I answered clearly. After the rejection, I spoke with HR to understand what happened. I learned that the interviewer thought I was looking at answers during the interview. That surprised me because I was not using anything…

  • Cisco Software Engineer interview: networking OA cutoffCisco · Software Engineer · Online Assessment · Jul 2026

    The process began with an online assessment, and the later interview path depended on that result. For me, the OA was the gate. I solved some questions, but my overall performance was not strong enough to continue. There was no detailed technical follow-up afterward, only the sense that the feedback did not support moving forward. The assessment covered networking and C fundamentals: subnetting,…

  • Cisco Software Engineer interview: OA programming barrier and design discussionCisco · Software Engineer · Online Assessment · Jul 2026
    Rejected

    My process started with an online assessment and moved quickly into interview rounds, though I did not make it all the way through. The assessment combined many multiple-choice questions with programming tasks, and I could tell early that the programming section would decide things. When I was unsuccessful, the gap was clearly more about solving than simply understanding concepts. The interviews…