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 Northrop Grumman: behavioral panelNorthrop Grumman · Software Engineer · Jul 2026Offer
A recruiter email laid out the early screen, including standard and role-specific questions. I then met a panel made up of a hiring manager and two tech leads. The process centered on communication and fit: they wanted STAR-style behavioral answers and kept returning to how my experience looked against the role. It was not especially technical and did not require a presentation. I mostly discusse…
- Software Engineer interview at Northrop Grumman: interview experienceNorthrop Grumman · Software Engineer · Jul 2026Offer
A quick recruiter touchpoint confirmed my background and interest, then I moved into a relaxed virtual interview with the team. It was low-pressure even while live. The interviewers seemed more interested in understanding my work than testing me, and I had room to discuss my resume and ask what the job looked like day to day. The questions were mainly behavioral and experience-based. They asked a…
- Software Engineer interview at Ntt Data Europe & Latam: interview experienceNtt Data Europe & Latam · Software Engineer · Jul 2026Offer
After a recruiter call, I went through two technical discussions and then an assessment round. It was professionally run and technically grounded, with interviewers who seemed clear about what they were asking. The process did not feel chaotic or excessively difficult. It felt like a fair test of how my experience matched the role. The tone stood out as much as the content. I felt comfortable fro…
- Software Engineer interview at NTT DATA: interview experienceNTT DATA · Software Engineer · Jul 2026Offer
I went through two technical discussions and one assessment round. The structure seemed meant to confirm that I could do the work rather than repeat buzzwords. The overall atmosphere was professional and calm, and the interviewers came across as technically solid. The technical conversations followed my resume in a natural way, and the assessment did not feel like a gotcha. I felt the interviewer…
- Software Engineer interview at Oscar Insurance: timed unfamiliar patternOscar Insurance · Software Engineer · Jul 2026
A recruiter contacted me a couple of days after I applied and scheduled a technical round about a week later. I had been warned that the questions would be difficult and tightly timed. That proved accurate: I had 30 minutes for a challenging pattern I had never seen before, got partway through it, and could not finish in the time box. The short window made the experience stressful from the beginn…
- Software Engineer interview at Palo Alto Networks: interview experiencePalo Alto Networks · Software Engineer · Online Assessment · Jul 2026
I started with an online assessment and then had three virtual technical rounds. The first was a system-design-and-coding-style prompt where I implemented a solution. It soon turned into debugging existing code to fix a bug, with the focus on making the code work under constraints rather than on theory. In the final round, I had to modify the code again in an object-oriented way, changing both it…
- Software Engineer interview at Perk: interview experiencePerk · Software Engineer · Jul 2026No response
After recruiter outreach, I had a short HR call, but the recruiter moved quickly from question to question without much engagement or follow-up. The technical part was roughly where I expected it to be. After I finished, though, I received no feedback or clear yes-or-no answer, and my follow-ups went nowhere. I had been told to expect an email within a week if I progressed, but weeks passed witho…
- Software Engineer interview at Plangrid: React and system designPlangrid · Software Engineer · Jul 2026
The recruiter first discussed the role, my background, and the process, which put me at ease. The hiring-manager conversation was mostly behavioral: why I chose software engineering, resume projects I was proud of, and how I approach teamwork and communication. It also included a few technical basics, including C++ and DSA. The next steps were a live React interview, system design, and culture fi…
- Software Engineer interview at Prime Video: three coding roundsPrime Video · Software Engineer · Jul 2026
The process was predictable: three medium LeetCode coding rounds, then system design and a cultural-fit conversation. The interviewers were pleasant, and the atmosphere did not feel adversarial. Still, I saw the format as dated. I kept questioning the use of LeetCode tasks as a proxy for real engineering ability and whether the culture-fit conversation added something meaningful to the coding sig…
- Software Engineer interview at Qualys: interview experienceQualys · Software Engineer · Jul 2026
The first technical interview mixed front-end and back-end fundamentals. React and Redux came up with Node.js, along with an output-style coding question, basic DSA, and at least one question about my project experience. The next technical round stayed in that territory with Java coding, SQL queries, design patterns, resume questions, and more React, JavaScript, and Node.js. What made the process…
- Software Engineer interview at Robert SlackRobert Slack · Software Engineer · Jul 2026
After I applied online, I waited a while before the recruiter-led process began. I first completed a HireVue coding-and-video portion, then spoke with a recruiter about the role and next steps. I was later sent a link to schedule a meeting with the hiring manager. The later technical conversations focused more on fit and background knowledge than deep algorithms. I spoke with multiple interviewer…
- Software Engineer interview at Rupeek: DSA and system designRupeek · Software Engineer · Jul 2026
My SDE 3 process took about three weeks and had four rounds covering DSA and design. After an initial coding or assessment stage, I tackled medium problems such as coin change and trapping-rain-water-style questions. Another round covered Java, Spring, REST APIs, fundamentals, and design decisions. The design work included low-level design for a health-app-style scenario and high-level design for…
- Software Engineer interview at SafranSafran · Software Engineer · Jul 2026Offer
The interview was very technical from the start and centered on the fundamentals of elasticity. I had to work through a problem involving stress calculations for a cylindrical structure and, as best I remember, derive a related formula or theorem. My French was assessed alongside the technical material. The interview was clearly challenging, but I found it interesting because the topics were conc…
- Software Engineer interview at Salesforce: Futureforce offerSalesforce · Software Engineer · Jul 2026Offer
I applied to the Futureforce tech accelerator and received a HackerRank OA with two or three LeetCode questions. After about a month, I advanced and attended an online preparation presentation with engineers for the system-design discussions ahead. The interview combined behavioral discussion of projects and AI use with a LeetCode question and follow-ups. A week later, I received and accepted an…
- Software Engineer interview at Schweitzer Engineering Laboratories: in-person multi-part daySchweitzer Engineering Laboratories · Software Engineer · Onsite · Jul 2026
The process had three main stages. I started with a phone screen, then had a technical interview on Zoom, followed by an in-person day with several components rather than a single technical conversation. That in-person sequence included a security interview, a presentation, another technical interview, and a management interview. Moving among coding-style thinking, presentation, and people- and l…
- Software Engineer interview at ServiceTitan: slow coding sequenceServiceTitan · Software Engineer · Jul 2026
After a recruiter call, I went through several straightforward coding rounds. They focused on medium LeetCode-style data structures and algorithms. The interviewers were calm and practical, asked clarifying questions, and stayed interested in how I was thinking. I cleared multiple rounds that kept testing much the same skill set, but the whole process took about a month. Several-day pauses appear…
- Software Engineer interview at Siemens HealthineersSiemens Healthineers · Software Engineer · Jul 2026
After a recruiter call to schedule everything, I went through two virtual rounds. The first technical round covered OOPS, .NET Core, and design patterns, followed by two programming questions. One involved a stack; the other asked me to swap two variables without using a third. I tried to work through them step by step because the round felt geared toward practical engineering. The second round m…
- Software Engineer interview at Siemens: interview experienceSiemens · Software Engineer · Jul 2026
An agency recruiter set up my first interview after an initial chat. It was an online conversation with an engineering manager, and at that point the process seemed to be moving toward something more hands-on. I was told the next stage would have been an onsite, more technical interview, but I never reached it. The manager conversation itself was calm and conversational. I could explain my backgr…
- Software Engineer interview at Sonata Software: interview experienceSonata Software · Software Engineer · Jul 2026Rejected
The process started with a recruiter-managed Risebird setup, but the early technical discussion did not seem connected to the actual project. Both rounds were led by people who did not appear closely tied to the client or role details. The second repeated the same pattern, and the interviewer did not seem to know what had already been discussed. Communication became the larger problem. I made mul…
- Software Engineer interview at Sonata: interview experienceSonata · Software Engineer · Jul 2026No response
After a recruiter call through Risebird, I went through two rounds that felt disconnected from the client and the actual role. Neither interviewer seemed to know much about what the project needed, and the second round repeated the same problem. The interviewer also appeared unaware of what had been covered before, and I could not get a clear explanation of how the interviews related to the clien…
- Software Engineer interview at Spacex: interview experienceSpacex · Software Engineer · Jul 2026
I got far enough to face technically intense screens that seemed built to test end-to-end understanding. Even when a question was posed as a hypothetical, it did not feel like a formula-memory exercise. It felt as though they wanted hands-on reasoning and confidence with fundamentals across the chain. The hardest part was a run of very pointed hypotheticals that seemed only loosely connected to m…
- Software Engineer interview at Starr Companies: interview experienceStarr Companies · Software Engineer · Jul 2026
After I applied, about a month passed before I heard anything. I was then sent a HireVue link for video responses and a coding challenge. After another wait, a technical recruiter scheduled a short 30-minute call to explain the role and next steps. About a week later, I was invited to schedule time with the hiring manager. That conversation mixed behavioral and technical topics, including Spring…
- Software Engineer interview at Steven Douglas Associates: interview experienceSteven Douglas Associates · Software Engineer · Jul 2026
The process felt standard and not especially punishing. After an initial HireVue-style step, I had a couple of live conversations that were more about how I thought than about trick questions. The technical round was framed as a fit check against the team’s stack, so it tested background knowledge without becoming a coding contest. The live rounds were welcoming. I discussed my resume, answered S…
- Software Engineer interview at Super Micro Computer: coding loopSuper Micro Computer · Software Engineer · Jul 2026Rejected
The loop had a predictable shape, even though I was not selected. It began with three medium LeetCode-style coding rounds, continued to system design, and ended with a cultural-fit conversation. The interviewers were pleasant and the atmosphere stayed positive. What bothered me was the format more than any particular prompt. The coding rounds felt dated and close to traditional LeetCode preparati…
- Software Engineer interview at Supermicro: virtual loopSupermicro · Software Engineer · Online Assessment · Jul 2026
I started with a recruiter screen, then completed an online assessment before a virtual loop with several interviewers. Each conversation blended technical material with Amazon Leadership Principles. The coding was DSA-heavy: I had to contrast brute-force and optimal approaches, explain time and space complexity, and work through a sliding-window problem systematically instead of rushing to code.…
- Software Engineer interview at SwiggySwiggy · Software Engineer · Jul 2026No response
My process began with one very quick technical screen. I was asked only the Two Sum problem, which I solved in roughly five minutes, so the interview itself did not feel stressful or complicated. After that, the process went quiet. There were no follow-up rounds and no meaningful updates or timeline. Months passed without closure, which felt unprofessional, especially after such a clean first ste…
- Software Engineer interview at Systems Planning and AnalysisSystems Planning and Analysis · Software Engineer · Jul 2026Rejected
This process was much heavier than I expected. It began with a recruiter phone call, then an HR phone interview, followed by a video meeting with the manager. Later I attended an in-person meeting with both the manager and HR, and completed an English test. The process took time and offered little clarity between steps. It ended in rejection, communicated through automated-looking emails that did…
- Software Engineer interview at Tesla: gasket toleranceTesla · Software Engineer · Take-home Project · Jul 2026
Before the interview, I completed and submitted a take-home test. The interview then opened with a problem that sounded simple, involving a gasket and an L bracket compressing that gasket. The interviewer treated it as straightforward, but I overthought the calculation and missed the correct tolerance limit. The subject itself was not complicated. The precision of the calculation was what mattere…
- Software Engineer interview at ThalesThales · Software Engineer · Jul 2026
A phone conversation led quickly to a one-hour video call. The recruiter mainly checked whether I was still seeking a role and could relocate if necessary. The video call combined motivation questions with technical discussion. It was not a hands-on exercise; it was a conversation about my reasoning and the way I described my background. The difficulty was average for me, neither impossible nor p…
- Software Engineer interview at The Walt DisneyThe Walt Disney · Software Engineer · Jul 2026Offer
The recruiter first discussed my interests and location fit. I understood that some versions of the role might have two rounds, one easy-to-medium LeetCode problem and a hiring-manager round, but my own path was recruiter first and then a technical-and-fit discussion with an engineer or hiring manager. I had a recruiter video screen, a hiring-manager video interview, an in-person office technical…
