Katkat

real interview stories, told over a cup of tea ♡

Grammarly 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

11 results

  • Rejected

    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…

  • 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…

  • Grammarly Software Engineer interview with HackerRank and technical codingGrammarly · Software Engineer · Online Assessment · May 2026

    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-…

  • Grammarly Software Engineer interview: supportive technical assessmentGrammarly · Software Engineer · HR Screen · May 2026
    Offer

    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…

  • From the beginning, the process felt smooth and fair. Follow-ups were scheduled quickly, everyone showed up on time, and the recruiter kept me updated with clear instructions and timely feedback at each stage. That tone continued in my conversations with the team. Even though the process took time, it never felt messy or stressful. I went through a straightforward set of rounds focused on clarity…

  • An Onsite Interviewer Who Kept Turning His Camera On and OffGrammarly · Software Engineer · Onsite · Apr 2026

    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…

  • 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…

  • Grammarly Solutions Engineer interview with a presentation and live demoGrammarly · Solutions Engineer · Other · Apr 2026

    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…

  • Grammarly Software Engineer four-question coding assessmentGrammarly · Software Engineer · Online Assessment · Mar 2026
    Offer

    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…

  • Grammarly Software Engineer interview: backend coding and team matchGrammarly · Software Engineer · HR Screen · Mar 2026
    Offer

    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…

  • An AI-Chat Spreadsheet Design Question and a Brutal 45-Minute Merge ProblemGrammarly · Software Engineer · Onsite · Feb 2026
    Rejected

    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…