Real, anonymous reports from people who interviewed for Frontend Engineer at Grammarly, newest first and distilled into what to expect across the loop.
Get your personalized Grammarly Frontend Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My first impression of the process was that it could be rough. In one of the rounds, I had front-end technical interviewers who felt toxic and arrogant, and I was asked to sign an NDA before the interview. The feedback I received ended up being extremely minimal, with almost no concrete guidance on what landed well or what didn’t.
Separately, the overall coordination around soft skills also left a bad taste. I went through a long set of steps that included recruiter screening, hiring manager discussions, and multiple interviews covering culture/values and technical topics. I ended up spending over five hours in the interview loop before it was suddenly interrupted—there was an email telling me they needed to re-evaluate the position. After that, a recruiter promised a follow-up to review feedback, but I was ghosted repeatedly and never got a real reschedule for the remaining parts.
> 1 year
Difficult Negative New York, NY
I started with a fairly relational recruiter-to-hiring-manager screen that left a good impression—warm and genuinely empathetic, which honestly felt rare. After that, I moved into a technical interview with another frontend engineer. The questions bounced around React and browser-native features, then shifted into a live coding segment where I worked through a simple algorithm plus some basic HTML/CSS/JS rendering. It felt relevant and, for once, the bar seemed aligned with the role.
A week or so later I hit the virtual onsite, and that’s where everything changed. The schedule felt tightly packed and stressful, like it was designed as a stress test rather than a real assessment of my skills. I also experienced a lack of consideration from the recruiter—arriving late without acknowledging it, and being dismissive when I raised concerns that the process didn’t feel equitable. The onsite was split into multiple parts: fundamentals, system design, frontend plus behavioral, and even a short “coffee chat” with current employees.
> 1 year
Average Negative San Francisco, CA
The first real touchpoint came when the head of engineering reached out and convinced me to talk with the technical recruiter. The screening moved qui…
Unlock every Frontend Engineer interview experience
