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
- Full Stack Engineer interview at Act Digital: quick start and no closureAct Digital · Full Stack Engineer · Jul 2026No response
The process began with a relaxed HR conversation about my background and resume. Since the role was tied to a client through a third party, the early focus was fit and logistics rather than deep technical questions. The technical stage covered a framework and my experience. Scheduling from recruiter to client moved quickly, but after the client interview I received no meaningful feedback despite…
- Garrett Advancing Motion Software Engineer interview: demanding and supportiveGarrett Advancing Motion · Software Engineer · Technical Screen · Jul 2026Offer
The process felt professional and candidate-friendly. It combined technical and HR conversations, and the interviewers stayed supportive and open even when questions were difficult. I could explain my thinking without feeling rushed or shut down. The technical discussions assessed mechanical-engineering fundamentals, problem-solving, communication, and general aptitude. I felt tested on both know…
- GHD Software Engineer Interview Experience: a graduate group project and short individual interviewGHD · Software Engineer · New Grad · Other · Jul 2026Offer
I found the graduate interview engaging. It began with a group project about Engineering Consultancies, followed by an individual interview. The project helped me understand how they assessed collaboration and shared thinking before learning more about each candidate. My individual interview lasted about ten minutes. It was brief but still connected to the group project, and I had a positive impr…
- GHD Software Engineer interview: technical and STAR questionsGHD · Software Engineer · HR Screen · Jul 2026Rejected
After applying, I had an organized and professional early process. I began with a recruiter conversation about my background and role fit. My final conversation was with two interviewers, who started with a brief overview of the company and what they wanted. The interview mixed technical and competency questions but felt welcoming rather than combative. I explained my experience and problem-solvi…
- GlobalFoundries Software Engineer interview: conversational department panelGlobalFoundries · Software Engineer · Technical Screen · Jul 2026
My interview began with a behavioral conversation with two people from the department. The focus was on day-to-day fit and how I would work, and it never became a technical grilling. What I liked was having time at the end for many questions. I planned ahead to ask about things that mattered to me, including employee resource groups. That exchange made the interview feel more like a conversation…
- GlobalFoundries Software Engineer recruiter and interview experienceGlobalFoundries · Software Engineer · Technical Screen · Jul 2026
After a recruiter step, I had a short set of interviews with several people. The conversations balanced technical and behavioral questions, and everyone stayed respectful and professional. Things moved quickly with little back-and-forth, and I heard back soon after the interviews. It was a smooth process without much stress or delay. My impression was that they were assessing fit efficiently. Loc…
- Globallogic Software Engineer interview experience: college projects and timingGloballogic · Software Engineer · Technical Screen · Jul 2026Offer
I started with a recruiter-style conversation, then went through three rounds that balanced fit and technical background. HR aligned expectations with my earlier work and discussed the role and timing. Technical and managerial interviewers asked about my college projects and general understanding of what I had done. The process was lighter than I expected, more conversation and fit than a barrage…
- Goldman Sachs Asset & Wealth Management Software Engineer interview: DSA and project trade-offsGoldman Sachs Asset & Wealth Management · Software Engineer · Technical Screen · Jul 2026
A recruiter contacted me, and the early technical screen felt easy compared with the later rounds. The superday raised the difficulty with multiple DSA problems, including medium-to-hard LeetCode questions. During the loop, I had a hiring-manager-style discussion mixing technical and nontechnical questions, plus a DSA pair-programming round. The final interview stood out. It felt partly like a ch…
- Goldman Sachs Asset & Wealth Management Software Engineer superdayGoldman Sachs Asset & Wealth Management · Software Engineer · HR Screen · Jul 2026Rejected
After applying online, I went through the usual recruitment loop. HR contacted me and arranged the interviews. My first call was a roughly 30-minute phone screen with a team lead, followed shortly by a CoderPad round that moved quickly and felt like the early technical checkpoint. After clearing it, I attended a superday about a month later. It had four rounds: DSA, SDLC, system design, and a hir…
- Google Business Analyst interview: technical screening and product communicationGoogle · Business Analyst · Technical Screen · Jul 2026Rejected
The interview loop felt fairly standard for Google, but I needed confidence at every stage. After speaking with a recruiter, I had a technical screen. The interviewer asked me to introduce myself, explain what I knew about the company and say why I wanted the role. We then moved to coding questions. The interviewer stayed relaxed as I worked. My impression was that they wanted me to keep steady a…
- Google Product Manager interview: cold early interview and silenceGoogle · Product Manager · HR Screen · Jul 2026Rejected
After an initial suitability call, I waited a couple of weeks for a first knowledge-based interview. Recruiter communication beforehand was supportive, but the interviewer came across as cold and professional, and I did not make it past that stage. In a separate early round, I had to drive the problem myself in a tight 30-minute window: identify constraints, explain an approach, propose solutions…
- Google Product Manager interview: practical-depth barGoogle · Product Manager · Jul 2026
The process felt long and hard from the outset. After the initial stages, the technical questions required real hands-on product experience. I could not have relied on generic product language to answer them confidently or accurately. The challenge was also organizing my thinking under pressure while remaining precise. Follow-up questions kept probing until I connected my reasoning to real-world…
- Google Software Engineer interviewGoogle · Software Engineer · Technical Screen · Jul 2026
The process began with a background questionnaire and an online interview with DSA and behavioral rounds. The DSA question was practical rather than a typical LeetCode problem, and I handled it well. Later, the onsite questions were closer to LeetCode, a shift I had not studied enough for. A system-design mock also felt mismatched because its problem did not resemble what I saw later. Scheduling…
- Google Software Engineer Interview Experience: A one-hour two-problem OA and eliminatory DSA roundsGoogle · Software Engineer · Online Assessment · Jul 2026
This was a fast onsite-style process centered heavily on DSA. I started with an OA containing two data-structures-and-algorithms problems to solve in about an hour. The time pressure made it intense, and I noticed there was no audio or video proctoring. Then I went into the interview portion for the onsite opportunity. The interviews focused only on DSA, with medium-to-hard LeetCode-style problem…
- Google Software Engineer Interview Experience: Median of two sorted arrays and autocomplete designGoogle · Software Engineer · Technical Screen · Jul 2026Offer
I expected the technical rounds to be tougher, but the interview felt much easier than I thought it would. The first main question was finding the median of two sorted arrays, and I got through it fairly quickly. Then the conversation moved to a system-design problem about building autocomplete for a search engine. The coding questions were written in a shared document rather than an editor where…
- Google Software Engineer interview for a PhD ML-focused role with spam-classifier designGoogle · Software Engineer · Jul 2026Rejected
I interviewed for a PhD SWE, ML-focused role, and the first real test came in the first interview round. It combined an ML domain section with behavioral questions. In the ML part, I was asked to design a spam classifier and write pseudocode for a bi-gram model. My recruiter had told me the domain round would connect to my projects, but the questions were more design-focused than I expected. When…
- Google Software Engineer interview with four final-loop sessionsGoogle · Software Engineer · Technical Screen · Jul 2026
My first step was a relaxed recruiter conversation of about half an hour. We discussed my background, school or earlier experience, and what was ahead. Then I completed a 45-minute technical screening coding challenge where how I organized and explained my reasoning mattered as much as reaching an answer. The final loop had four 45-minute interviews, usually spread across one or two days so it wo…
- Google Software Engineer interview with four rounds and onsite C++ implementationGoogle · Software Engineer · Technical Screen · Jul 2026
The process felt steady and not especially punishing. I started with a recruiter phone call and, about a week later, a technical screen. There were four interview rounds in total: two coding rounds, a behavioral round, and a system-design round. The coding was LeetCode-style medium algorithm and data-structure work, with the usual need to communicate clearly, get the code right, and think through…
- Google Software Engineer interview: algorithm rounds and delayed feedbackGoogle · Software Engineer · Technical Screen · Jul 2026Rejected
The process felt complicated and drawn out. After the early steps, I had a couple of algorithm-focused meetings with technical reviewers and an HR personal questionnaire. There were long gaps without updates, and I received no constructive feedback once it was over. Some early steps seemed smooth, but after submitting my materials I couldn't tell when they'd be reviewed or how long the decision w…
- Google Software Engineer interview: compact developer algorithm loopGoogle · Software Engineer · Online Assessment · Jul 2026
I went through a full-loop format with an online assessment and a recruiter call before the technical rounds. Once I reached the developer loop, I had to solve medium-to-hard LeetCode-style problems, and it felt designed to test real problem solving from start to finish. The structure became intense and compact after the earlier screening steps. The interview was essentially developers only, with…
- Google Software Engineer interview: detailed feedback on same-day codingGoogle · Software Engineer · HR Screen · Jul 2026
After a recruiter pre-screen, I had a tightly scheduled interview day with limited breaks. It combined a structured technical conversation with a behavioral STAR-style interview, leaving enough time to reset but not enough for the day to feel casual. I then had two LeetCode-like coding interviews on the same day with another short gap. In each, I was expected to think through an approach, align o…
- Google Software Engineer interview: four scenario-heavy technical roundsGoogle · Software Engineer · Technical Screen · Jul 2026
I expected a standard coding and behavioral loop, but Google put me through four technical deep dives that were much more scenario heavy. I presented a real customer issue, then completed a cognitive-analysis-style round that asked how I would begin thinking about large-scale infrastructure. The next technical discussions covered infrastructure or platform and AI-related problem solving. I was ex…
- Google Software Engineer interview: hardware panel and uneven technical difficultyGoogle · Software Engineer · Jul 2026
The interview focused on technical depth rather than only classic software problem solving. The panel was made up of hardware engineers, and the topics ranged across VLSI, analog work, and design engineering. It felt like a real technical discussion, and the interviewers seemed to engage with my answers instead of waiting for a memorized response. One question genuinely threw me off because it fe…
- Google Software Engineer interview: online coding and team matchingGoogle · Software Engineer · HR Screen · Jul 2026
After a recruiter chat, I completed the process online. The phone screen mixed behavioral discussion with a technical component, then a separate technical round asked me to solve two LeetCode-style questions in a language I chose from Python, C++, or Java. Behavioral questions also appeared alongside coding. Two later calls became somewhat harder but retained the same live DSA problem-solving for…
- Google Software Engineer interview: recruiter screen and four linear roundsGoogle · Software Engineer · HR Screen · Jul 2026
The process began with recruiter screening, where we covered my background, the role, and what the interview path would look like. After that, there were four rounds in a clear sequence. The first mixed a Googliness-style discussion with coding. The following rounds added two more coding interviews. Team matching only came into the picture after the coding rounds were done. The route felt linear:…
- Google Software Engineer interview: referral, six coding questions, and supportGoogle · Software Engineer · Technical Screen · Jul 2026
A referral started my loop and moved me to a recruiter call sooner than I expected. The process then had three coding rounds, each with two LeetCode-style questions, a system-design interview, and a behavioral interview. The overall vibe sat in the middle: challenging but not cruel. In the coding rounds, I needed to solve cleanly, communicate clearly, and handle follow-ups instead of treating the…
- Google Software Engineer interview: unclear live DSA communicationGoogle · Software Engineer · Technical Screen · Jul 2026
This interview was hard in a particular way. It was not only the complexity of the DSA questions, but also the interaction with the interviewer. I got directional array questions involving dynamic programming, though I could not clearly recall the full second part of the problem afterward. The interviewer did not speak clearly enough for me to ask clarifying questions effectively. I spent extra m…
- Google Software Engineer interview: varying difficulty and interviewer toneGoogle · Software Engineer · Online Assessment · Jul 2026
One Google path started with an online assessment and then an interview if accepted. My question was LeetCode medium to hard, although I had heard that others received easier ones. My first interviewer was somewhat rude, which made it harder to stay comfortable and confident while working through the problem. I also encountered a recruiter-led path with a pre-interview stage followed by two short…
- GPU Search Engine Team Phone Screen on Counting Distinct StringsNVIDIA · Software Engineer · Technical Screen · Jul 2026
This is for a team at Nvidia that is turning an open-source search engine into a GPU implementation. I personally have no hardware or GPU experience at all. They replied the day after I applied and said they wanted a phone screen, and I found out early on, after looking into the background of the interviewer, that the interviewer was a hardware engineer. I assumed they cared about my search engin…
- Grab Software Engineer interview with next-day HR screeningGrab · Software Engineer · HR Screen · Jul 2026
A recruiter reached out through LinkedIn, and things moved quickly. I scheduled the HR conversation and interviewed the following day. It was friendly and focused on my background, the engineering role I wanted, my resume, and a short self-introduction. A day or so later, I had a user-related round. The interviewer was accommodating and professional, asked clear questions, and kept a warm tone. T…
