Very good and organized process. Standard leetcode type initial round (medium) and then final loop with sys design, another leetcode type question, and behavioral. The recruiter is pretty active at every step.

Recruiter call, followed by technical interview. Technical interview focused purely on Leetcode style questions, had 50 mins to complete 4 questions. Did each progressively and optimized based on space and time complexity. It initially started off well, good rapport with interviewers. After 3 questions, was getting drained and questioned, how are any of these questions relevant to the job at hand? They weren't customized or changed datasets to represent the type of problems Grammarly engineers face, pure copy paste questions on HackerRank. I got to the fourth question after completing all the test cases from previous problems (spent time on each, including both top down and bottom up dp approach for Climbing Stairs problem), however, they still seem unsatisfied. I imagine recruiting and hiring is a difficult problem, however this is just plain lazy and frustrating to having to correctly recite problems, DP optimizations and discuss time complexity. All this really tests is how well have they grinded Leetcode, and how many tricks can they 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 em well, since they're not on Leetcode). Would not recommend at all.

HR round and then phone call. The highlight of phone interview was complex leetcode style questions of which perfect solutions were expected. Not a good way to go to hire a senior engineer.