READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 65 of 153
Interview experiences · Grammarly
Grammarly Account Executive interview: mock qualification call and AE debrief
My process was shorter and felt focused on getting to a clear signal early. I started with a recruiter interaction where I talked through my background and interest. Then I had a second conversation that went deeper in a similar style, followed by a mock qualification and discovery call and an AE debrief. What surprised me was how quickly the mock call fed into the decision. I expected more conve…
Interview experiences · Grammarly
Grammarly Software Engineer four-question coding assessment
My interview process started before I spoke with any engineers. I submitted an application and completed coding assessments with four questions, followed by an HR phone screen. After that, the process focused heavily on live, timed problem solving. I had two live coding rounds. One used LeetCode-style questions, and the other involved solving an actual problem from beginning to end. After the cod…
Interview experiences · Grammarly
Grammarly Software Engineer interview: backend coding and team match
I started with a recruiter screen, then moved into CS fundamentals and a backend coding interview. I also presented my projects before going through team-match conversations. The process felt well organized and clearly communicated. My recruiter kept me grounded by proactively sharing detailed information about each stage. The technical interviews were challenging but fair. I could tell they care…
Interview experiences · Grammarly
Grammarly Software Engineer Interview Experience — An AI-Chat Spreadsheet Design Question and a Brutal 45-Minute Merge Problem
Overall people were pretty nice, and the recruiter was attentive — maybe the company just isn't that big yet and is still hiring. The bar for the questions didn't feel well calibrated, honestly a bit exaggerated. At this level, I think only people from the top, currently-hot AI star companies could really handle it. Why bother stressing over this one? Here are the two rounds of technical intervie…
Interview experiences · Grammarly
Grammarly Software Engineer Interview Experience — An Onsite Interviewer Who Kept Turning His Camera On and Off
Coding: Design an in-memory key-value store that supports set, set, count(value) (how many keys currently hold this value), begin, commit, and rollback. This interviewer would easily rank as one of the worst interviewers I've ever had. He didn't communicate with me at all the whole time. Here's how it went: he said he was turning his camera off and I should spend a few minutes reading the problem…
Interview experiences · Grammarly
Grammarly Software Engineer interview: supportive technical assessment
After the recruiter call, the process moved quickly and felt professionally run. The recruiter was very responsive and easy to work with, and the interviewers were supportive and engaged. Instead of feeling interrogated, it felt like a real conversation in which they were genuinely interested in my background. The technical portion was calmer than I expected. I completed a technical assessment, f…
Interview experiences · Grammarly
Grammarly Software Engineer interview with a smooth recruiter experience
Everything was handled smoothly from the beginning, and the recruiter experience really stood out. Communication was responsive, so I never had that awkward waiting period that can drag out a process. The schedule was predictable, and the interviewer conversations were engaging rather than intimidating. Once I moved into the rounds, the interviewers were knowledgeable and supportive, and the tone…
Interview experiences · Grammarly
Grammarly Software Engineer interview with HackerRank and technical coding
My process started with a HackerRank coding assessment. After that, I had an HR screening round that felt more like a checkpoint than a detailed conversation. The main work came next in a technical coding interview, followed by additional rounds that combined engineering depth with questions about cultural fit. The process felt difficult mainly because the technical portion required real problem-…
Interview experiences · Grammarly
Grammarly Software Engineer: technical screen, CS fundamentals, backend, and project walkthrough
The process was structured and moved at a steady pace. Before my application was submitted, I completed an initial technical screen. Once the application moved forward, I had a recruiter screening. After that, I met with an interviewer for a computer science fundamentals assessment that lasted about an hour. I then had a backend engineering round that lasted another hour. The final part of that p…
Interview experiences · Grammarly
Grammarly Solutions Engineer interview with a presentation and live demo
I went through an organized hiring process that lasted several rounds and felt professional from start to finish. Communication stayed consistent. The recruiter and hiring team set expectations early, followed up on timelines and next steps, and kept me informed after each stage. Each conversation had a clear purpose. There were about five to six rounds overall, and the team explained what they w…
Interview experiences · GreyOrange
GreyOrange Software Engineer interview experience
After the recruiter stage, I completed a take-home assessment that was the hardest part of the loop. It was not one problem. It covered five system-design scenarios, each aimed at a different principle, and I had to create the data models and workflows for them. This was more than drawing an architecture. I had to explain how the designs would scale and what would happen in failure cases, includi…
Interview experiences · GreyOrange
GreyOrange Software Engineer interview: Java output and two-pointer questions
The virtual interview opened with an introduction, then moved quickly into Java. I answered two questions about working out the output, followed by two basic DSA questions, including a two-pointer problem. It was a straightforward technical screen. The focus was clear reasoning and getting the output right, not a long, complicated algorithm under pressure. I did not progress, and it left me feeli…
Interview experiences · GSA
GSA Data Scientist Interview Experience — A CNN Adversarial-Example Question on Bridge Collapse Prediction
We talked about research. Explain why this approach would fail: collect bridges and their design drawings from Wikipedia. Train a CNN on these drawings to predict whether a bridge will collapse (or whether it will collapse within the first X years after being built). Then, starting from random noise, use gradient descent to "construct" a drawing plan that makes the model predict a 99.9% probabili…
Interview experiences · Guidewire Software
Guidewire Software Customer Success Engineer interview: Java, SQL, and director loop
After the usual application step, HR contacted me for my current and expected salary. I then completed Codility work with three Java tests and one SQL test. The next step was a live Java technical interview about OOP, lasting about an hour. After that, I had a behavioral manager interview for another hour, followed by an on-site director interview that also lasted about an hour. The process did n…
Interview experiences · Guidewire Software
Guidewire Software Software Engineer interview: Codility, OOP, manager, and director
After the usual application step, HR contacted me for my current and expected salary. I then completed Codility work with three Java tests and one SQL test. The next step was a live Java technical interview about OOP, lasting about an hour. After that, I had a behavioral manager interview for another hour, followed by an on-site director interview that also lasted about an hour. The process did n…
Interview experiences · Guidewire Software
Guidewire Software Software Engineer interview experience
The process started with an initial online-assessment screening and had four rounds in total. After the screening, the remaining interviews were face to face and felt like a sequence rather than unrelated one-offs. In the middle technical rounds, they wanted clear thinking and trade-off explanations, not just working code. I had a system-design-style discussion where I reacted to a scenario and i…
Interview experiences · Guidewire Software
Guidewire Software Software Engineer Interview Experience: Onsite scheduling broke down
After a recruiter call, I took an online assessment with two LeetCode-style questions, one easy and one medium. They felt straightforward. I then spoke with an engineering manager and, near the end, solved a simple coding problem and wrote tests. The feedback was immediately positive, and the manager said they wanted to see me onsite. The onsite scheduling was where it fell apart. I contacted the…
Interview experiences · Guitar Center
Guitar Center Account Executive interview: relaxed store role-play with managers
I started with a recruiter-style setup that felt fast and straightforward. After an initial conversation to line things up, I had a phone screen and then an in-person interview. At the store, I met with multiple managers. They asked about my background, how I worked with people, my fit for the role and store culture. Most questions stayed close to my CV: sales experience, how I approached custome…
Interview experiences · Gusto
Gusto Software Engineer coding round: hard LeetCode problem and sponsorship constraint
I started with the recruiter and first stage, then moved on to a coding round. The problem felt closer to the hard end of LeetCode than to an easy exercise. I first solved it with a brute-force approach, and after I showed that I understood the core logic, the interviewer pushed me toward an optimal method. I reached an efficient solution and passed the relevant test coverage, so I left feeling t…
Interview experiences · Gusto
Gusto Software Engineer interview, take-home and pair session
My process felt rigorous and time-heavy. It stood out because it involved more than a single technical screen, with multiple signals being collected. I was surprised by how much effort the interview required overall, including a take-home component, follow-up work, and extended technical work that didn't feel proportional to the compensation. The questions were framed as "real work," but they wer…
Interview experiences · Gusto
Gusto Software Engineer interview with a Codesignal GCA-style assessment
After I applied, I moved forward only after completing a Codesignal GCA-style assessment that wasn’t automatic. Once I passed, I had two technical rounds with LeetCode-style questions drawn from the company’s tagged topics. The rounds felt sequential and fairly structured. I solved each problem, reviewed my approach, and moved to the next step after clearing the previous one. After the technical…
Interview experiences · Gusto
Gusto Software Engineer interview with repeated scheduling and communication issues
My biggest problem wasn't the technical difficulty. It was the process itself, especially how scheduling and communication kept falling apart. I had several recruiter interactions go sideways: calls where nobody joined, last-minute reschedules where I was stood up again, and follow-ups that never produced a clear answer. At one point, I even received a generic rejection email without any meaningf…
Interview experiences · Gusto
Gusto Software Engineer interview with timed LeetCode medium assessment
The process felt straightforward and predictable. After applying, I completed an online assessment, followed by a technical interview focused on a LeetCode medium problem. The process then moved toward an offer decision. The online assessment was the difficult part. One question was relatively easy, but after that I essentially had to produce a perfect coding solution without debugging, all withi…
Interview experiences · HackerRank
HackerRank Backend Engineer API assessment, AI-assisted test fixes, and silence
I began with a HackerRank assessment that felt more like backend work than a puzzle. I had to build backend API functionality across multiple files, then fix failing tests with help from an AI assistant. After I completed both parts successfully, I was invited to an automated screening interview, which felt straightforward. Then the process stalled. I received no recruiter contact, status update,…