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 Arch Global Services Philippines: prolonged silenceArch Global Services Philippines · Software Engineer · Jul 2026

    The hardest part was the disorganized communication after I invested time. In one assessment flow I did not advance but at least received a rejection email. In others, I completed interviews or assessments and then heard nothing when I expected scheduling or status updates. Gaps between rounds reached three to four weeks, and after a final round the silence lasted months without feedback or an of…

  • Software Engineer interview at AtosAtos · Software Engineer · Jul 2026
    Offer

    The first conversation covered my background, shift-work availability, and how my experience matched the need. It was direct, with little emphasis on compensation negotiation. The next exchange came the day after I applied through my school job postings and felt more like a conversation than a real technical assessment. Two days later, a manager called to propose the role. The speed made it feel…

  • Software Engineer interview at Avanade: interview experienceAvanade · Software Engineer · Jul 2026

    The first round went smoothly. The interviewer was responsive and the conversation felt good. The second technical round was much more intense, with fast problem-solving questions. In one version of that round, I had to create a function on the fly while answering nearly fifty questions. That technical stage also included case-style scenarios and live testing. It felt like a full hour without muc…

  • Software Engineer interview at Brillio: HR then technical fitBrillio · Software Engineer · Jul 2026

    The process had two stages. First, I had a telephone discussion with HR about my background, experience, and expectations for the role. The next interview assessed problem solving, technical knowledge, past projects, and overall fit. It was a standard, straightforward sequence of context-setting followed by technical evaluation. Location: India. Overall feedback: positive. Offer status: no offer.

  • Software Engineer interview at Burns & McDonnell: full-day onsiteBurns & McDonnell · Software Engineer · Jul 2026
    Offer

    I attended a full-day interview beginning with a short presentation on my background and experience. I then met in panels and individual conversations with engineers and managers, covering several perspectives on my fit. There was also a recruiter touchpoint and time to see the workplace and culture. The day was long but organized, with each part connected to how I thought and would work with the…

  • Software Engineer interview at Finacle: backend fundamentals and poor conductFinacle · Software Engineer · Jul 2026

    My technical round covered JavaScript and Node.js, real-time-style problems, SQL, and React basics. One practical coding task involved transactions and locking. The questions generally connected web and server-side fundamentals back to my resume and the role. The atmosphere was not consistently constructive. In one experience, an interviewer laughed when I struggled, which made the discussion fee…

  • Software Engineer interview at GHD: interview experienceGHD · Software Engineer · Jul 2026

    The interview was welcoming and conversational from the start. The interviewers gave me room to discuss my background, technical knowledge, and career goals. Instead of grilling me, they turned the questions into a conversation about how I solve problems and why I was interested in the company. The questions were connected to the role and encouraged me to explain my reasoning rather than simply n…

  • Software Engineer interview at GlobalFoundries: supervisor to HRGlobalFoundries · Software Engineer · Jul 2026

    The process began with people closest to the role and finished with HR. I spoke separately with a supervisor and a manager. Their questions drew on my experience and knowledge, with behavioral material mixed in, and seemed aimed at understanding how I would think and operate from what I had done before. Later, an assessment-style Q&A tested critical thinking and problem solving rather than memori…

  • Software Engineer interview at Google: long formal loopGoogle · Software Engineer · Jul 2026

    The process took roughly one to two months, then extended further through team matching. It began with CV screening and a technical coding phone interview, followed by an onsite loop with several 45-minute coding interviews, architecture discussions, and Googliness questions. After the interviews came a formal hiring-committee stage and team matching, with a proposal only if a team aligned. The m…

  • Software Engineer interview at HCL TechHCL Tech · Software Engineer · Jul 2026

    This was a short, straightforward interview with about three or four deeper questions about services and APIs. It took place in Hyderabad and felt professional and good in tone. I did not get the offer because I could not answer important parts of the discussion. The questions were not trying to be tricky; they simply required specific knowledge I did not have ready. I kept thinking afterward abo…

  • Software Engineer interview at Honeywell Technologies: low-level designHoneywell Technologies · Software Engineer · Jul 2026

    The first round began with a low-level-design prompt. I had to design a system, then the conversation moved into object-oriented programming and C++ questions. Nothing about the topics was wildly surprising, and the interview itself felt okay. I did not hear back afterward, though, and because the process did not continue, I assumed I had been rejected. Looking back, the expectations seemed clear…

  • Software Engineer interview at HP SCDS: bilingual and multi-person roundsHP SCDS · Software Engineer · Jul 2026

    The first conversation felt personable and dynamic rather than rigid. It was short and split between English and Catalan/Castellano. We discussed my experience, goals, ambitions, and how my story fit the company and role, without the sense that anyone was trying to trap me. Another sequence began with HR, then a peer screen, an in-person peer round, and an in-person manager round. The in-person m…

  • Software Engineer interview at Hyland: technically prepared but not selectedHyland · Software Engineer · Jul 2026
    Rejected

    After a pre-placement talk, I moved into a technical interview that felt normal for the role. I completed most of the work I was given, and the difficulty did not seem unusually high. The process was more competitive than I expected. I had not read the presentation as an immediate rejection, yet I was ultimately rejected. My preparation seemed adequate for the technical portion, which made the ou…

  • Software Engineer interview at IBM: automated rejection and silenceIBM · Software Engineer · Jul 2026
    Rejected

    I completed a HackerRank online assessment under a tight timeline, but much of the rest of the process lacked human contact. I later received an automated-looking rejection notice without having heard from an actual person. In another similar timeline, I completed a HireVue-style interview with standard prompts and then waited more than a month and a half without an update. That long silence felt…

  • Software Engineer interview at Jio Platforms: broad fundamentalsJio Platforms · Software Engineer · Jul 2026

    A single technical discussion covered a broad set of fundamentals. I began with an easy DSA problem, then moved through core CS topics. C++ questions included dangling pointers and memory management; SQL covered basic queries; and the last section went deep into JavaScript hoisting, the event loop, callbacks, promises, and asynchronous execution. The difficulty was average. My impression was that…

  • Software Engineer interview at JOHN LEONARD: interview experienceJOHN LEONARD · Software Engineer · Jul 2026

    I applied online and waited about a month before anything happened. I was then sent a HireVue link for an asynchronous interview with quick behavioral prompts and a small coding component. Later, a technical recruiter scheduled a 30-minute conversation about role details and next steps, followed about a week later by a hiring-manager scheduling link. The later rounds focused on the team’s stack r…

  • Software Engineer interview at Josh Technology GroupJosh Technology Group · Software Engineer · Jul 2026

    The online rounds covered both basics and DSA. The first asked about C/C++ fundamentals and pointers. The second leaned more toward aptitude and DSA, especially trees. The assessment felt medium rather than extremely hard, but it still required solid fundamentals. I also saw material around tree traversal, OOP-style basics, and infix/postfix questions earlier in the process. I was not selected. W…

  • Software Engineer interview at Josh Technology: campus DSA sequenceJosh Technology · Software Engineer · Online Assessment · Jul 2026

    Campus hiring began with three rounds. The first tested OOP and logical reasoning; the second combined aptitude with two DSA problems; the third was entirely DSA with three problems. After I cleared them, I entered an onsite-style sequence of about five technical interviews focused on DSA, problem solving, core CS, and my projects. There was then an in-office follow-up with an online assessment c…

  • Software Engineer interview at Josh Technology: interview experienceJosh Technology · Software Engineer · Online Assessment · Jul 2026

    The OA and early coding stages made this feel grindy. The preassessment was harder than similar practice sets I had seen, especially because it had many graph questions. I had to code strictly in JavaScript, which narrowed the way I could approach the problems. The rounds covered basic concepts and hands-on coding. I was asked about infix and postfix notation, a task to find the least value in a…

  • Software Engineer interview at Josh Technology: three online assessmentsJosh Technology · Software Engineer · Online Assessment · Jul 2026

    My whole process stayed remote because I only reached the online rounds. There were three online assessments, each with medium DSA material. The questions used trees and linked lists, plus one string question. Although the listed difficulty was medium, the OA stage was the hardest part of the process for me. I did not receive an offer and did not advance beyond those online rounds. Location: Gurg…

  • Software Engineer interview at Lam Research: interview experienceLam Research · Software Engineer · Onsite · Jul 2026

    I started with recruiter or HR contact, then met a manager and a peer. At the onsite, I presented slides as part of the process, and there was also a panel interview. Across those conversations, the questions centered on my previous experience and how it might transfer to the role. The structure felt standard: discuss my background with the manager and peers, then use my slide deck to anchor the…

  • Software Engineer interview at Ltimindtree: interview experienceLtimindtree · Software Engineer · Online Assessment · Jul 2026

    The process had three straightforward rounds: an online assessment, a technical interview, and HR. The assessment mixed aptitude, logical reasoning, and coding practice, setting the tone for the rest of the process. The technical conversation focused on Python and problem-solving. It was more about how I approached coding than memorizing tricks, and it stayed interactive. The difficulty was avera…

  • Software Engineer interview at Maersk: frontend machine codingMaersk · Software Engineer · Jul 2026

    I had a frontend-focused process with two technical rounds and a hiring-manager-style discussion. The early technical work covered practical JavaScript and frontend tooling, including core JavaScript, asynchronous behavior, TypeScript, and Vue 3. It was easy to medium in tone and was about writing and reasoning through frontend code rather than theory alone. The second round became a machine-codi…

  • Software Engineer interview at Medtronic: fit and collaborationMedtronic · Software Engineer · Jul 2026

    After an HR call, I spoke with the hiring manager in a process that felt direct and centered on competencies. They asked about my experience, including whether I had worked in medical devices, then discussed my projects and the way I worked on a team. Even the technical questions focused on my reasoning rather than only the final answer. Because I had interned at another company site, I already k…

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

    The technical screen was tightly focused on algorithms. I had two coding questions: one involved traversing an array to count ball collisions based on speed, and the other asked how to maximize a weighted sum by sorting an array strategically. They tested greedy thinking and careful logic. The problems were described as easy to medium, and I could follow how the scoring and sorting decisions conn…

  • Software Engineer interview at Microsoft: respectful recruiter screenMicrosoft · Software Engineer · Jul 2026

    The recruiter screen was prompt and professional. The recruiter explained the role, asked about my background, and clarified expectations, so the conversation did what an early fit check should do. I did not advance or receive an offer. The process felt clear and respectful, but the experience reminded me that an early screen can still be decisive even when the conversation goes well. Location: U…

  • Software Engineer interview at Morgan Stanley: four-hour first in-person interviewMorgan Stanley · Software Engineer · Onsite · Jul 2026

    My first in-person interview was hard mainly because I had never gone through that format before, not because the material felt impossible. I did enjoy learning about the team and the company, and I appreciated the effort the interviewers put into the conversation. The day lasted four hours. By the end, both the interviewers and the team seemed tired, and that fatigue made the experience heavier…

  • Software Engineer interview at NBCUniversal Advertising Products & Solutions: interview experienceNBCUniversal Advertising Products & Solutions · Software Engineer · Jul 2026

    After the exam, I went through a college-placement-style process with three interview rounds and an HR step. The second round felt most like an on-the-spot test because it combined basic programming questions with a few puzzles. The other rounds were more introductory. The flow was straightforward for me, and I felt able to answer what each interviewer asked. Location: Thanjāvūr. Overall feedback…

  • Software Engineer interview at Nevada Staffing: tolerance and heat transferNevada Staffing · Software Engineer · Take-home Project · Jul 2026

    After recruiter contact, I submitted a take-home test and then interviewed. The first question was about a gasket and an L bracket compressing an L gasket. It sounded simple, but I overthought the tolerances and missed the correct limit. In a second pass through the technical loop, the tone itself made things harder. The interviewer pulled specific details from my resume and then abruptly moved t…

  • Software Engineer interview at New Relic: delayed Portland processNew Relic · Software Engineer · Jul 2026
    Rejected

    After the recruiter call, I waited almost two weeks before the hiring manager scheduled the Portland interview. On that call, the manager seemed disengaged and did little to build momentum, so the conversation felt flat and uninterested in my experience. Another couple of weeks passed with no update. The recruiter eventually said the search had narrowed and they were pausing candidates, followed…