Grammarly interview notes, page 3 of 5

“First instinct was to just slap a counter in a database and call it done.” The rest of the author's notes on Software Engineer interview at Grammarly, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The set/get/count part I had no problem with.” The rest of the author's notes on Software Engineer interview at Grammarly, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I had an answer prepared but the follow-ups kind of unraveled it.” The rest of the author's notes on Software Engineer interview at Grammarly, Executive / Final Round round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with the easy part, a map from topic strings to a set of callbacks, and that was fine.” The rest of the author's notes on Software Engineer interview at Grammarly, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is the one that got me.” The rest of the author's notes on Software Engineer interview at Grammarly, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I had a decent story ready but fumbled the engineering-specific part a bit.” The rest of the author's notes on Product Manager interview at Grammarly, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The naive approach of looping and rescanning the string will get you there eventually but it's slow and they'll push back.” The rest of the author's notes on Software Engineer interview at Grammarly, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The stack-based approach clicked for me pretty fast, keeping pairs of character and count.” The rest of the author's notes on Software Engineer interview at Grammarly, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This one got me.” The rest of the author's notes on Software Engineer interview at Grammarly, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This question has a lot of surface area and I think I underestimated it at first.” The rest of the author's notes on Software Engineer interview at Grammarly, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.