Recruiter call, followed by a technical interview.

The technical interview focused purely on LeetCode-style questions. I had 50 minutes to complete 4 questions. I tackled each progressively, optimizing based on space and time complexity.

It initially started off well, with good rapport with the interviewers. After 3 questions, I was getting drained and questioned how any of these questions were relevant to the job at hand.

They weren't customized or changed datasets to represent the type of problems Grammarly engineers face; they were pure copy-paste questions from HackerRank. I got to the fourth question after completing all the test cases from previous problems (I spent time on each, including both top-down and bottom-up DP approaches for the Climbing Stairs problem), however, they still seemed unsatisfied.

I imagine recruiting and hiring is a difficult problem. However, this is just plain lazy and frustrating, having to correctly recite problems, DP optimizations, and discuss time complexity. All this really tests is how well one has "grinded" LeetCode and how many tricks they can avoid during an interview.

Please do better, for your sake. At the very least, cater it towards the problems that Grammarly solves (based on these questions, I'd argue they probably don't solve them well, since they're not on LeetCode).

Would not recommend at all.

If you still wish to grind, here are the problems asked:

#70 Climbing stairs #1047 Remove all adjacent duplicates in string #1209 Remove all adjacent duplicates in string. The last one was a modification of #1209 with a function/predicate to find characters to replace (ascending, descending order).