READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 64 of 153
Interview experiences · Geico
Geico Senior+ Software Engineer Interview Experience — Recruiter Downgraded the Level Before the HM Screen Even Started
I saw this on an online job board. The job post was actually for a Distinguished Engineer, and I thought it would be a chance to get a taste of a super high-level IC role, a career jump of sorts, and I was fine taking a pay cut for that, so I applied. The recruiter then told me that their Distinguished level is calibrated against Google/Meta L8 ICs, which is two levels above my current scope, so…
Interview experiences · General Dynamics Information Technology
General Dynamics Information Technology Software Engineer Interview Experience: a 30 minute panel
The process was unusually streamlined. I had a single 30 minute virtual panel with a program manager, a senior architect, and a VP. It was a quick, focused discussion with decision makers rather than a long run of screens. I did not have to wait through multiple rounds. I received an offer shortly after the call, which made the process feel efficient and low drama. It felt as if the team had a cl…
Interview experiences · General Mills
General Mills Software Engineer Interview Experience: intrusive recruiter questions
My first contact was a recruiter call that shifted in an unexpected direction. The recruiter asked intrusive personal questions, including what my spouse and parents do and how many children I have. The conversation then moved to my salary history. What felt especially off was that it became an argument about that history without clear information about the engineering role or the salary range th…
Interview experiences · General Motors
General Motors Senior Software Engineer Interview Experience — Hiring Manager Chat Turned Technical, Then a Codility REST API Phone Screen
Earlier I had a call with the hiring manager. I expected the whole thing to be behavioral, but surprisingly it was almost entirely about technical decisions — things like how you'd go from a monolith to microservices, the tradeoffs between the two, and then how you'd go from microservices to a more modular architecture, and how to make those calls. About a week after that call, a recruiter reache…
Interview experiences · General Motors
General Motors Software Engineer Interview Experience — Open-Ended System Design That Ran Fifteen Minutes Over
The interview was scheduled for 45 minutes. The interviewer gave me a question that was roughly: there is an application that has to call three to five dependency services, and how do you guarantee a specific target for a specific service, for example access latency under 10 seconds and availability above 99%. It didn't feel like a normal design round. It felt like a very open-ended discussion ab…
Interview experiences · GHD
GHD Software Engineer Interview Experience: a graduate group project and short individual interview
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…
Interview experiences · GHD
GHD Software Engineer interview: technical and STAR questions
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…
Interview experiences · Gimlet Labs
Gimlet Labs Machine Learning Systems Interview Experience — Two System Designs and an Unexpected Rejection
This is an inference startup. The basic business is to place different stages of inference on different hardware in a forward-deployed model. For example, a company might have many old accelerator cards that no longer have enough compute for other work and use them for decoding. The role was Member of Technical Staff in machine learning systems. A recruiter approached me. I was already changing j…
Interview experiences · Glean (CA)
Glean (CA) Backend Engineer interview: multiple one-hour DSA rounds
I started with an introductory round with the hiring manager and then met with the head of engineering. After that came multiple coding and DSA rounds, each lasting around an hour. The setup felt condensed but clear. They moved from conversation into hands-on technical evaluation pretty quickly. The process was described as difficult, and the structure reflected that. Instead of one challenge, I…
Interview experiences · Glean (CA)
Glean (CA) Backend Engineer interview: rejection after system design
I interviewed for a backend focused role and was rejected after the system design round. The early stages weren't where the process ended. The later system design evaluation was the point at which I didn't make it through. The overall sequence matched what I'd heard from friends: a fairly consistent process that eventually led to the same system design stage. That round felt high stakes. The earl…
Interview experiences · Glean (CA)
Glean (CA) Software Engineer interview: difficult DSA problem-solving screen
My process started with a recruiter reach-out where we talked through the setup and the overall interview process. After that, I had a technical screen that felt more "in-house" than a generic LeetCode interview. It still relied on DSA knowledge, but the prompt put more emphasis on problem-solving within its structure. The question required me to apply data structures and algorithms. I could tell…
Interview experiences · Glean (CA)
Glean (CA) Software Engineer interview where timing decided the outcome
The interview process felt smooth from start to finish. The recruiter was responsive, and communication during the interviews went well. I stayed engaged and clear while working through the questions. The interview fell in the difficult range. The main issue was timing: I couldn't solve the question within the allotted time. The interview wasn't chaotic or confusing. It felt more like a performan…
Interview experiences · Glean (CA)
Glean (CA) Software Engineer interview with six rounds and a DSA setback
I went through six rounds in total: one hiring manager round, two technical rounds, and three cultural rounds. By the later stages, it was clear they were evaluating more than coding, with a strong focus on overall fit. The technical work was difficult for me. I didn’t get past the first technical DSA round because I got tripped up by library differences and mixed up my C++ and Java knowledge whi…
Interview experiences · Glean (CA)
Glean (CA) Software Engineer: practical coding and system design onsite
A recruiter reached out to me, and the first technical screening round involved a middle-to-hard LeetCode-style problem. After that, I moved into an onsite loop with three rounds: two coding rounds and one system design round. One coding round involved another LeetCode-style problem. The other was more open-ended and practical. I spent most of the time coding while the interviewer checked in only…
Interview experiences · Glean (CA)
Glean (CA) Solutions Engineer hiring manager interview rescheduled
My process started well. The team was responsive early on, and after the initial setup, everything seemed to move smoothly. During the hiring manager portion, though, the interviewer joined about 55 minutes late, which forced a reschedule. I completed the interview after that, but then I never really heard back from the recruiter or hiring manager. I followed up multiple times and received no sta…
Interview experiences · Glean
Glean Data Scientist Interview Experience — Five SQL Questions and a Rehashed User ID Puzzle
I haven't seen an interview post about this company, so let me be the first. There were 5 SQL questions, and the interviewer was a DS. The questions themselves weren't that hard, but a lot of the open discussion was pretty tricky. Two tables: users with user_id, signup_date, and login with user_id, browser, date. A few of the questions stuck with me: Calculate login DAU, and if there are days wit…
Interview experiences · GlobalFoundries
GlobalFoundries Software Engineer interview: conversational department panel
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…
Interview experiences · GlobalFoundries
GlobalFoundries Software Engineer interview with setup and hold questions
After the recruiter conversation, I had two engineering-focused technical rounds. The first was with someone on the design side. We went through my resume and academic projects before discussing C. The second was with someone on the verification side and was noticeably tougher. That verification interview focused on fundamentals: asynchronous design, flip-flop behavior, assertions, and setup-and-…
Interview experiences · GlobalFoundries
GlobalFoundries Software Engineer recruiter and interview experience
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…
Interview experiences · Globallogic
Globallogic Software Engineer interview experience: college projects and timing
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…
Interview experiences · Goldman Sachs Asset & Wealth Management
Goldman Sachs Asset & Wealth Management Software Engineer interview: DSA and project trade-offs
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…
Interview experiences · Goldman Sachs Asset & Wealth Management
Goldman Sachs Asset & Wealth Management Software Engineer superday
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…
Interview experiences · Goldman Sachs
Goldman Sachs Software Engineer Interview Experience — Two-Hour Online Assessment with Two Problems
2 hours to solve two problems: Transaction Segments Given an array transactionValues of length n, where transactionValues[i] is the transaction amount at time i. Count the number of contiguous subarrays that are strictly increasing and have length exactly k. Strictly increasing means: transactionValues[i] < transactionValues[i+1] < ... < transactionValues[i+k-1], i.e., every element must be stric…
Interview experiences · Grab
Grab Software Engineer interview with next-day HR screening
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…