Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

11 stories

Likes earn the author +10 XP for the first 3 likes each day

GrammarlySoftware Engineer
Reported May 2026

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…

Offer0
GrammarlySoftware Engineer
Reported May 2026

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…

OfferHR Screen0
GrammarlySoftware Engineer
Reported May 2026

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

Online Assessment0
GrammarlyAccount Executive
Reported May 2026

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…

RejectedOther0
GrammarlySoftware Engineer
Apr 2026

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…

Onsite0
GrammarlyAccount Executive
Reported Apr 2026

Account Executive interview at Grammarly: Competitive offer and fair negotiation

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…

Offer0
GrammarlySolutions Engineer
Reported Apr 2026

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…

Other0
GrammarlySoftware Engineer
Reported Apr 2026

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…

Technical Screen0
GrammarlySoftware Engineer
Reported Mar 2026

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…

OfferHR Screen0
GrammarlySoftware Engineer
Reported Mar 2026

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…

OfferOnline Assessment0
GrammarlySoftware Engineer
Feb 2026

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…

RejectedOnsite0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP