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

  • ServiceTitan Software Engineer interview: difficult technical loops and inattentive evaluationServiceTitan · Software Engineer · Technical Screen · Jul 2026

    The process began with recruiter coordination and became a set of deep technical conversations that I found genuinely hard. One version included several coding interviews and a system design discussion. The people were pleasant and my impression of the culture was positive, but I was at the end of a hiring cycle, and that affected the result. In a different technical loop, the difficulty was not…

  • SharkNinja Software Engineer interview: two calls and no responseSharkNinja · Software Engineer · Technical Screen · Jul 2026

    I had two interviews, first with a hiring manager and then a team member. Each was about half an hour. The conversations felt natural, and I left both believing I had explained my background clearly and that the fit was there. Even so, I never heard back. After completing both conversations, the process seemed to lose momentum, leaving me feeling sidelined and wondering whether I had missed a fin…

  • After an initial HR conversation, I received instructions and completed online assessments. The logic section used GMAT-style questions under time limits, followed by a SQL test. The process was direct and assessed precision under time pressure and consistency of my answers. Later interviews with users or the business area moved away from the exam format and toward fit with the day-to-day work. I…

  • My experience began badly with inconsistent communication. I completed the first stage in early July and was told I would hear back in two days, but the response did not arrive until the end of the month. An automated WhatsApp message said I had advanced and asked whether I wanted to continue. I confirmed, waited another two days for a form, and then heard nothing for a week. When they eventually…

  • Shopee Data Analyst interview: three respectful conversationsShopee · Data Analyst · Other · Jul 2026
    Offer

    My Shopee process was calm from the beginning. The people I spoke with were easy to talk to, and the interviewers seemed consistent in being professional and respectful. At each step, I felt I could discuss my background without the conversation becoming tense. I had three interviews in all and signed the contract within a month. The difficulty was medium, but what I remember is how smoothly it m…

  • Shopify Data Scientist interview: guided SQL and Python screeningShopify · Data Scientist · Technical Screen · Jul 2026

    About a week after I applied, HR contacted me. The first interview lasted 30 minutes and covered behavior, background, experience, and fit. Soon after, I had a one-hour technical screen with a team member split between SQL and Python. Before each round, Shopify sent a detailed PDF guide. That made preparation feel less like guessing because I knew what they were measuring. The recruiter also expl…

  • Shopify Software Engineer interview with pair programming, AI use, and a life-story roundShopify · Software Engineer · Online Assessment · Jul 2026

    I started with a resume submission. Once my application passed, I moved into an online assessment. The format varied, but it consistently combined several coding problems with a cognitive or IQ-style component and a culture-fit questionnaire. After that, the process moved toward the technical interview stage. My technical round was a pair-programming exercise with an OOP-flavored prompt. I had to…

  • Shopping Cart Versioning, Then Rejected on Tic-Tac-ToeDecagon · Software Engineer · Technical Screen · Jul 2026
    Rejected

    Round 1 was the shopping cart problem that other interview reports have also mentioned, but part 2 seemed a bit different. You're building a shopping cart for a cooking app. Users can add recipes to their cart. Each recipe has a list of ingredients (e.g., Chicken, Garlic). When the same ingredient appears across multiple recipes, the total count qualifies for bulk discounts. Part 1 was the same a…

  • Siemens Energy Software Engineer interview: Python, SQL, and asyncSiemens Energy · Software Engineer · Technical Screen · Jul 2026

    A recruiter scheduled my interview, and I soon had a technical screen focused on software fundamentals rather than anything unusual. It lasted about half an hour and covered Python, SQL, and data structures. I was asked about asynchronous programming, what happens behind the scenes, how data-structure evolution affects performance, and why some approaches are considered deprecated. The tone was t…

  • Siemens Software Engineer interview: two rounds and a hiring-manager discussionSiemens · Software Engineer · HR Screen · Jul 2026

    In the recruiter call, we agreed on availability and I was told to expect two rounds focused on AI/ML. The HR step was straightforward, with basic questions related to the role. I also sent some details by email and booked a Microsoft Teams slot. A short time later, I met the hiring manager online for the main discussion. We focused on my background and how it connected with the role's needs. The…

  • Sigmoid Analytics Software Engineer Interview Experience: two incompatible reported accountsSigmoid Analytics · Software Engineer · Technical Screen · Jul 2026
    Offer

    This source describes two different experiences and does not present them as one combined story. One reportedly ended badly during culture fit, with negative HR feedback and unclear hiring status. The other was a four-round process involving Java, Spring Boot, multithreading, and managerial project discussion. The source expressly says the feel and content are too different to synthesize into a s…

  • Sii Group Italy Software Engineer interview: client preparationSii Group Italy · Software Engineer · HR Screen · Jul 2026
    Offer

    A recruiter contacted me on LinkedIn, and the first steps moved quickly. After an HR interview, I spoke with several business managers who handled group work for different clients. The conversations helped me understand the assignments and what they expected. I then had a client-side technical interview after preparing with a business manager who knew the client's way of working. That preparation…

  • Sii Netherlands Software Engineer interview: prepared client discussionSii Netherlands · Software Engineer · HR Screen · Jul 2026
    Offer

    A LinkedIn recruiter contacted me, and the first conversations moved quickly. After the HR interview, I met several business managers who each covered SII activity with different clients. The technical conversation happened on the client side. A business manager who knew the environment and client prepared me for it, which took away the feeling that I would have to improvise and let me feel comfo…

  • Silicon Labs Software Engineer interview: unstable connection and scheduling breakdownsSilicon Labs · Software Engineer · Technical Screen · Jul 2026

    My experience started with a scheduling mess and became an uncomfortable call. I told HR in advance that I would be overseas and might have an unstable connection because I would need a VPN. The first part of the interview was choppy, although it eventually stabilized. I could not shake how the hiring manager reacted. They seemed visibly impatient and annoyed throughout, and when I asked question…

  • Site Reliability Engineer interview at Nutanix: interview experienceNutanix · Site Reliability Engineer · Jul 2026

    The technical interview was grounded in SRE essentials. I was asked about Linux commands, virtualization, operating-system and computer-network concepts, as well as my resume and projects. The questions kept returning to core computing knowledge rather than anything flashy. The overall difficulty felt average, but it still tested whether my knowledge was solid. I made some mistakes because I was…

  • Six OA Questions Buried in Walls of TextUpstart · Software Engineer · Online Assessment · Jul 2026

    Very easy, 6 questions. The biggest challenge was that most of the questions were way too long — it took more than 2 minutes just to read and understand each one, and if you didn't pass on the first try, debugging got really stressful. For example, the first question (8 minute time limit) opened with a long paragraph about someone in medieval times who wrote a manuscript... two minutes later... t…

  • Six Rounds Including a Code Review, Director Wanted More SeniorityMongoDB · Software Engineer · Senior+ · Onsite · Jul 2026
    In progress

    For DSA I just did LeetCode, steadily, over the past few months. For system design (both low-level and high-level) I went with an online design course without thinking twice, and I also watched a couple of YouTube channels on the topic. Here is how the loop went: Technical Screening: I had to build a rate limiter that lets through n requests within the last k seconds. We talked through the API an…

  • Six-Stage Onsite Loop from Brain Teasers to Bar RaiserOracle · Software Engineer · Onsite · Jul 2026

    Stage 1 Coding Question Max profit using a single buy and sell (best time to buy and sell stock, limited to one transaction). Technical Question Bottom view of a binary tree — explain the implementation approach and the reasoning behind it. Technical Question Find the minimum number of processes allocated. System Design Given a series of webpage URLs (including schemaName, host, port), design a v…

  • SIXT Software Engineer interview: campus DSA cutoffSIXT · Software Engineer · Online Assessment · Jul 2026
    Rejected

    The campus drive began with an online assessment containing two medium LeetCode-style coding questions. About 20 of roughly 150 students were shortlisted for interviews. My first technical round covered time and space complexity and a medium dynamic-programming LeetCode problem. I did not make it past that first technical interview. Candidates who did move on had a second interview, and a smaller…

  • Skechers Account Executive interview: pen pitch and shoe role-playSkechers · Account Executive · Other · Jul 2026
    Offer

    The online group interview was about sales and presentation. We took turns answering questions about the company and product, and I had to sell a product in front of the group. One prompt asked for a quick pitch, about half a minute, to sell a pen. I also did a role-play as a customer and sales associate to sell a shoe, plus a sheet of situation questions. The content was not hard, but being put…

  • Skechers USA Account Executive interview: group product discussionSkechers USA · Account Executive · Other · Jul 2026
    Offer

    My interview was online and uncomplicated. I was in a group with four other people, and we talked about the company and how to sell a product. It was practical and did not feel technical. The only preparation that seemed useful was getting a quick sense of the company background before the conversation. Everyone followed the same general format, which made it easy to understand. I did not find it…

  • My first conversation with Slalom came through a friend connection, so it started informally and felt friendly. They were flexible about my availability, and that tone carried into scheduling. It took less than a week to move from outreach to a real meeting, and the recruiter followed up at the exact time we had agreed on. The interviews were conversational rather than interrogation-style. They m…

  • Slalom Consultant interview: respectful salary mismatchSlalom · Consultant · Other · Jul 2026

    After the recruiter contact, I had a technical and consulting-oriented screen about my prior work, difficulties I had faced, and how I handled them. The questions were standard for consulting, but the recruiter clearly connected them to the role's technical side and to how candidates fit different pay bands. The process respected my time. After the technical conversation, it became clear that the…

  • Slalom Software Engineer interview: senior role, design and in-person behavioral roundSlalom · Software Engineer · Senior+ · HR Screen · Jul 2026

    I started with a 30-minute Microsoft Teams recruiter call about my background and fit for a Senior Software Engineer role. It was straightforward and warm. The technical interview then covered my experience, projects, and technical decisions. The next stage was system design, where I designed a solution, did hands-on coding and modeling, and discussed trade-offs. The final stage was an in-person…

  • SLB Full Stack Engineer interview: puzzle, project discussion, DSA, and designSLB · Full Stack Engineer · Technical Screen · Jul 2026
    Offer

    My process opened with a general HR-style introduction and then moved into technical rounds. The first technical round was light, with a basic puzzle that felt more like a check on how I think than a demand for deep mastery. A project discussion followed and became a standard conversation about explaining my work clearly. The next technical round shifted to medium-level DSA with basic system desi…

  • The process opened with an English exam and a basic logic and math check on a platform. Everything in the test was in English. Passing it was a clear gate, after which the process became an interview rather than another assessment. I then had about a half-hour interview with an engineer. I only learned whether I would move to the second round after that conversation, so there was little room to r…

  • Offer

    After a recruiter-style conversation, I met with HR and then a manager or mentor. The process felt friendly and focused on the material I had already shared against the job description, especially whether my experience fit what they needed. I also completed an English evaluation through a portal, so it did not really test speaking. The role was in Digital and Integration, which was described as a…

  • SLB Software Engineer interview: Java concepts and linked listsSLB · Software Engineer · Technical Screen · Jul 2026

    The technical interview focused on Java concepts and data-structures fundamentals. I was asked about OOP, including the idea behind an "oops" concept and what variables to declare when creating an object. There were also linked-list questions. The questions were not presented as tricks. They tested whether my everyday Java knowledge and core data-structures understanding were really there. The qu…

  • Recruiter outreach led to a drawn-out process with three interviews over about a month and a half. The overall mood stayed relaxed, which helped because the process still involved several stages. I first had an HR-related screening call, then two live coding sessions. Those coding sessions were the main technical hurdle before I could move forward. After I cleared them, I was invited to a loop in…

  • Snap Software Engineer interview: snapfest coding day with supportive interviewersSnap · Software Engineer · Technical Screen · Jul 2026

    After the recruiter process, I went to a concentrated coding day called snapfest. It consisted of two back-to-back rounds, each about an hour, so it felt like one block of interviews rather than separate stages over several days. Both rounds used LeetCode-style medium problems. The interviewer tone stood out. The engineers were not cold or combative. When I got stuck, they offered guidance and ke…