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

  • Software Engineer interview at Tiger AnalyticsTiger Analytics · Software Engineer · Jul 2026

    The technical questions leaned toward data engineering. I had two technical rounds on Python and PySpark coding, moderate-difficulty DSA, and Azure Data Factory, so I had to discuss data workflows as well as algorithms. The questioning sometimes moved quickly and felt argument-driven. I did not feel I had much time to write or iterate on query-like work, which made it harder to show the backend d…

  • Software Engineer interview at TikTokTikTok · Software Engineer · Jul 2026

    The recruiter gave me a broad sense of the role and scheduled the interviews, but I could not get much detail about the topics or how many stages remained. HR replied quickly, yet the process structure stayed unclear. The first technical stage was a LeetCode question. A later combined stage included technical discussion plus another LeetCode problem. Once interviewing started, things moved along,…

  • I began with a self-introduction presentation of about ten minutes. My supervisor asked questions from what I presented and sometimes interrupted, so I had to respond in real time rather than treat the presentation as a formality. The team then explained its work and responsibilities, and I was able to ask questions. The process felt structured and respectful. Its main challenge was handling acti…

  • Software Engineer interview at VisaVisa · Software Engineer · Jul 2026
    Rejected

    Visa began in a standard way with an OA and then technical rounds. In CodeSignal Round 1, I had a medium array problem, a deep resume discussion, Docker and Kubernetes questions, and basic database-query material. Round 2 was more coding-heavy and asked me to implement an LRU cache. I got working LRU-cache code, but the interview ended around the 50-minute mark, leaving expected material uncovere…

  • Software Engineer interview at Volkswagen Group ItaliaVolkswagen Group Italia · Software Engineer · Jul 2026
    Offer

    My Software Engineer process had three rounds: HR first, then an account manager associated with the client, followed by a client-side interview panel. The final panel was the last checkpoint before the process wrapped up. The sequence was smooth and simple. I never found it chaotic or overly complicated, and each step followed naturally from the last. I cannot speak to how other roles work, but…

  • Software Engineer interview at Volkswagen Group Italia: offer timelineVolkswagen Group Italia · Software Engineer · Jul 2026
    Offer

    My process had several stages and moved more slowly than I expected. I went through two technical discussions, then final document verification and a salary conversation. It eventually became an offer-acceptance process, and I received an offer letter. The surprising part was timing. More than three weeks passed before I joined the organization after accepting. The paperwork did move forward, but…

  • Software Engineer interview at Zensar Technologies: unexpected technical roundZensar Technologies · Software Engineer · Jul 2026

    The first technical interview was professional and covered .NET fundamentals and cloud basics. A later round was described as casual and HR-like but arrived as an unannounced technical-heavy interview. The interviewer felt rude and impatient, and the questions seemed limited to that person's own expertise rather than a fair view of what I could contribute. HR later ended communication by saying t…

  • Offer

    I first had a recruiter phone screen focused on my background and whether I was genuinely aligned with the role. It was more about getting to know me than technical grilling. The manager interview used STAR-style behavioral questions, with a couple of light technical trivia questions as a change of pace. The experience was smooth, and I received an offer. The format suited the role because it put…

  • Sogeti Consultant interview: coaching calls and an impersonal panelSogeti · Consultant · HR Screen · Jul 2026

    After I applied, the recruiter contacted me quickly and sounded genuinely excited, almost surprised that no one had hired me already. We covered my MSP background and my mail-migration work, including how I ran projects from kickoff through implementation and the post-implementation survey. A week later I followed up because nothing had arrived, and soon after that a panel interview was scheduled…

  • Withdrew

    I entered through a referral and passed an initial assessment. That led to a recruiter phone screen and then a technical interview, so the process moved forward quickly once I cleared the test. I withdrew after the technical round and did not experience the full multi-round loop. The early funnel felt normal: assessment, recruiter call, then technical screen. Since I chose to step away, I cannot…

  • No response

    After a recruiter screen, I had a quick hiring-manager call and two peer interviews back to back. They were personable conversations about my experience, motivation, understanding of the role, and basic experience-based questions. Both peers spoke positively and pointed me toward the next stage. Then communication stopped. I followed up after about a week and again later, but received only a feed…

  • No response

    At first, the process seemed quick and responsive. After the first stage, though, I ran into complete silence. I followed up and still received no feedback, which made me feel that I had been interviewed simply for the sake of interviewing. I also experienced another version of the same poor follow-through. It dragged on for around two months, and I was ghosted after the interviews despite my rem…

  • Sopra Steria Software Engineer interview: one-day assessment and data tooling roundsSopra Steria · Software Engineer · Online Assessment · Jul 2026

    After the recruiter step, I went through a fast set of assessments. The first covered aptitude, general fit, and English-style screening. The second used coding-oriented multiple choice on basic DSA, SQL, and OOP concepts. It was manageable and finished within one day. In a separate role-specific track, I had two internal interviews, a client round, and a managerial round. Those conversations tes…

  • Southern California Edison Software Engineer interview: STAR panel and electrical conceptsSouthern California Edison · Software Engineer · Technical Screen · Jul 2026

    I started with a talent-acquisition recruiter call. Because I matched the role requirements, I moved to a four-person panel interview. They took turns asking questions, so the conversation was structured but moved quickly as each interviewer joined in. Most questions were behavioral and expected STAR-style answers. I was pressed about past experience and how I handled particular situations, with…

  • Spacex QA Engineer interview: recruiter support and onsite feedbackSpacex · QA Engineer · HR Screen · Jul 2026

    After a recruiter call, I went through a series of phone interviews that felt more structured than anything I had done before. There was another round with an engineer, followed by a hiring-manager call that ran about half an hour longer than I expected. That conversation stayed pretty chill, though they kept asking me to connect my background to their work. Soon after that, I was invited onsite…

  • Spacex Software Engineer interview experienceSpacex · Software Engineer · HR Screen · Jul 2026

    The recruiter-to-technical flow was fairly standard, but it became a full evaluation cycle. It started with HR or cultural fit, followed by technical conversations with team members. In one technical discussion, I spoke directly about prior jobs while several people listened and occasionally joined in. Later rounds demanded deeper understanding and clearer communication. The hiring manager was in…

  • Spacex Software Engineer interview: a surprise half-day panelSpacex · Software Engineer · HR Screen · Jul 2026

    I started with HR, then met a hiring manager and a technical team member before what was described as an onsite. By the time I reached the panel, the process had grown into a full half-day onsite interview. What caught me off guard was the framing. It had been sold as a simple, quick chat, but it was really a technical interview. After I answered, they pushed back with follow-up questions that se…

  • The process started with a short recruiter call about my background, then turned technical almost immediately. The next call lasted about 30 minutes and felt grounded in first principles. I answered quick checks on fundamentals such as the ideal gas law and Bernoulli's equation, then moved into structures-style questions. Even when I did fine on the equations, it seemed they wanted tight, confide…

  • The first round began with a resume dive and moved directly into technical questions. The interviewer focused on one of my projects and pushed on the details instead of accepting the high-level story. I felt they wanted clarity on my decisions and implementation choices, and much of the discussion rested on solid C++ fundamentals. After that, the process shifted to a coding assessment after the e…

  • Speechify Software Engineer interview: proctored AI-assisted coding challengeSpeechify · Software Engineer · Online Assessment · Jul 2026

    After I applied, the process moved almost immediately into an automated, AI-assisted coding challenge. It happened so fast that I felt nobody had reviewed my background first. There was no initial call. Instead, I received the challenge and had to record my screen and camera while working. The assessment lasted 90 minutes and used a company-provided codebase. I was told I could use AI tools, but…

  • The early technical step felt unusually uncomfortable because it was heavily proctored and camera-driven. I had to keep my camera on during a timed assessment, and the recording requirements made it feel more like surveillance than collaboration. It was an independent test, with no live interviewer helping while I worked. The assessment required a screencast. There were rules against AI tools and…

  • Speechify Software Engineer interview: refactoring and realtime AI designSpeechify · Software Engineer · HR Screen · Jul 2026
    Offer

    I began with a recruiter conversation about my resume and the shape of the technical rounds. Soon after, I completed a 90-minute LLM-based refactoring assessment inside a full-stack app. I was given problems to fix, and although AI tools were allowed, I still had to think through the work instead of copying answers. The later formats were live and varied. In a 90-minute vibe-coding session, I rec…

  • Sprinklr Software Engineer interview: running median and LRUSprinklr · Software Engineer · Online Assessment · Jul 2026

    I started with an online coding assessment, then moved into interviews that leaned heavily on classic DSA and competitive-programming-style problems. In the first interview, I was asked about finding the median in a running stream and about an LRU cache. It felt practical, as though they were testing whether I understood the data structures underneath the ideas. That round also included a horses…

  • Ss&C Technologies Holdings Financial Analyst interview: clipped technical screenSs&C Technologies Holdings · Financial Analyst · Technical Screen · Jul 2026

    I did not feel much emotion during the process. It was very businesslike and clipped. They skipped the usual introduction and went straight into technical questions. When I asked questions back, the answers were extremely short, as though they were trying to keep each reply to a few words. Most of the interview was a barrage of technical checks, with perhaps one situational prompt mixed in. The p…

  • Starr Companies Software Engineer interview experienceStarr Companies · Software Engineer · Online Assessment · Jul 2026
    No response

    Within a few business days of applying, I was invited to interview through an AI-style HireVue recording. I logged in, read one prompt at a time, had a short preparation window, and recorded a camera response. The questions were mostly STAR-style behavioral questions, with two attempts per prompt. Using the second attempt submitted it automatically. Near the end, a coding challenge appeared in th…

  • State Farm Software Engineer interview experienceState Farm · Software Engineer · Online Assessment · Jul 2026
    No response

    A few business days after applying, I received an interview invitation. The first step was asynchronous HireVue: I logged in, read each prompt, and recorded answers on camera. The behavioral questions were standard STAR-style questions, but near the end they added a coding task that had to be finished in the same recording window. The coding part was difficult largely because I could not ask clar…

  • Stefanini Brasil Software Engineer interview: client architecture discussionStefanini Brasil · Software Engineer · HR Screen · Jul 2026

    I began with an alignment conversation with HR, then interviewed with technical leadership. After that, I was introduced to a client. The role would be in a financial context, so the conversation stayed close to the kinds of decisions and architecture I had worked on before. The technical part was light but still required clear explanations. I was asked about choices I had made in an earlier hack…

  • Offer

    The interview unfolded in a fairly organic way. There were different moments, a few pauses, relaxed conversations, and varied questions along the way. I answered naturally and did not feel as though I was being interrogated. My impressions became clearer as the discussion moved forward. Overall, the process continued normally to the end, with balanced expectations. I left with the sense that the…

  • Stellantis Financial Services Us Software Engineer interviewStellantis Financial Services Us · Software Engineer · Technical Screen · Jul 2026

    I began with a short phone call about why Stellantis and why the role suited me. It was the usual walk-me-through-yourself and fit discussion. About a week later, I had a Teams interview. It was one behavioral session with a couple of targeted questions, followed mostly by a normal conversation. I used STAR to organize my examples, and the tone stayed easygoing and low-stress. There were no surpr…

  • Stellantis Software Engineer interviewStellantis · Software Engineer · Technical Screen · Jul 2026

    The recruiter first called to ask why I wanted Stellantis and why I thought I fit. Soon after, I had a Teams interview. It was mostly behavioral, and I used STAR to keep my answers organized, but the exchange did not feel like an interrogation. The 30-minute virtual interview was a small panel of engineers, with no HR present. They asked a few pointed questions and talked through examples from my…