← Back to Directory

Grammarly interview notes, page 4 of 5

Mid-sized

Most of these Grammarly write-ups come from Software Engineers (39), then Product Managers (3). The most reported rounds are the technical phone screen (17), the system design round (16), the behavioral / leadership round (3) and the product sense round (2).

42 interview notes · updated Jul 2026

Grammarly·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Grammarly PM interview with a product marketing question about GitHub Copilot's inline citation feature. Pretty niche prompt for a writing-focused company but I guess they want to see how you think about developer tools adjacent to their space.
  • How would you go about marketing GitHub Copilot's inline citation feature?

“Spent the first minute just trying to figure out who actually cares about this feature.”

View Post

Grammarly·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Coding round at Grammarly for a software engineer role. One algorithm question, interval scheduling flavor, pretty standard if you've seen it before.
  • Given an array of intervals, what is the minimum number of intervals you must remove so that no two remaining intervals overlap?

“I knew the greedy approach here: sort by end time, walk through and count removals whenever the current start is before the last recorded end.”

View Post

Grammarly·Software Engineer·Technical Phone Screen

Jun 2026
Phone screen for a Software Engineer role at Grammarly. Three coding questions back to back, all string or interval manipulation. Nothing too exotic but the third one had some edge cases I wasn't fully prepared for.
  • Given a list of intervals, merge all overlapping ones and return a sorted list of non-overlapping intervals covering the same ranges.
  • Repeatedly remove adjacent pairs of identical characters from a string until no more pairs remain. What is the final string?
  • Given a string and an integer k, repeatedly remove any k consecutive identical characters until no such group exists. Return the final string.

“Sort by start, then walk through and merge if the current interval overlaps the last one in your result list.”

View Post

Grammarly·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a software engineer role at Grammarly and got a binary search question, which sounds easy until you're actually in the room second-guessing your index math.
  • Given a sorted integer array and a target value, return the index of the target if it exists, otherwise return -1. Then discuss variants like finding the leftmost or rightmost insertion point.

“I knew binary search cold, or thought I did.”

View Post

Grammarly·Software Engineer·Technical Phone Screen

Jun 2026
Grammarly SWE interview with a coding round focused on building a transactional key-value store from scratch. Not the hardest problem conceptually, but the details pile up fast and I underestimated how much the nested transaction bookkeeping would slow me down.
  • Design and implement an in-memory key-value store that supports set, delete, and count operations, along with nested transactions using begin, commit, and rollback.

“I got the basic set/delete/count part down quickly.”

View Post

Grammarly·Software Engineer·Technical Phone Screen

Jun 2026
Grammarly SWE interview that had a twist on a classic tree problem. Instead of just solving it, you had to build the tree first from serialized input, which added a layer I wasn't fully expecting.
  • You're given a serialized sequence of numbers representing a binary tree (level-order with nulls, or similar). Build the tree from that input, then compute its maximum depth.

“I knew the depth part cold, that's just a standard recursion problem.”

View Post

Grammarly·Software Engineer·Technical Phone Screen

Jun 2026
Grammarly software engineer interview, got a linked list problem that I thought I knew cold but the follow-up tripped me up a bit.
  • Given the head of a singly linked list, detect whether it contains a cycle in O(n) time and O(1) space. Follow-up: if a cycle exists, find the exact node where it begins.

“The basic cycle detection part went fine, slow and fast pointer, they meet inside the cycle and you return true.”

View Post

Grammarly·Software Engineer·Technical Phone Screen

Jun 2026
Grammarly SWE interview, technical phone screen focused on data structures. One question, pretty clean problem but the optimal path requires you to actually know binary search cold.
  • Design a time-based key-value store that supports storing multiple values per key at different timestamps, and retrieving the most recent value at or before a given timestamp.

“I got a working solution going with a linear scan first, which they accepted but you could tell they wanted more.”

View Post

Grammarly·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Director-level behavioral round at Grammarly where you're expected to walk through two of your past projects in serious depth. Not a casual chat, they want specifics on what you built, why, and what it actually changed.
  • Walk me through one of your significant projects end-to-end, including the problem you were solving, your approach, your specific role, and the outcome.
  • Why did you make the key decisions you made during this project, and what alternatives did you consider?
  • What was the measurable impact of the project, and how did you know it was successful?

“The part that got me was 'your specific role.' I kept sliding into 'we did this, we decided that' and the interviewer kept pulling me back.”

View Post

Grammarly·Software Engineer·Onsite - System Design / Architecture

Jul 2026
System design round at Grammarly for a software engineer role. The whole thing was one big question about building a real-time collaborative editor, Figma-style. Dense problem with a lot of moving parts.
  • Design the backend and key client interactions for a real-time collaborative design editor, similar to Figma, supporting concurrent edits, presence, and persistence across network failures.

“This one ate up the entire session.”

View Post