Technical Interview - Coding
Duration: 60 minutes
Location: HackerRank
For this interview, you'll work through a series of algorithmic programming problems that build on each other in complexity. We use HackerRank as our coding environment, so we encourage you to familiarize yourself with it in your preferred language beforehand.
To prepare, we recommend you:
Review core data structures (arrays, linked lists, trees, graphs, hash maps) and common algorithmic techniques (recursion, sorting, searching, dynamic programming) Practice writing clean, working code — problems will progress in difficulty, so strong fundamentals matter more than memorizing specific solutions Get comfortable evaluating the time and space complexity of your code and explaining your trade-offs
We're evaluating your problem-solving approach, coding fluency, and ability to communicate your thinking — not memorization of specific problems. Resources like And "Cracking the Coding Interview" is a good starting point for practice.
Note: AI tools (e.g., Copilot, ChatGPT) are not permitted during this interview.
System Design & Service Architecture
Duration: 60 minutes
Location: HackerRank
Engineering Managers at Grammarly need to have a solid understanding of system design and to think critically about architecture. However, their role should focus on high-level planning rather than detailed design or implementation. They should use problem-solving skills effectively and avoid getting too caught up in technical details, instead emphasizing leadership and strategic oversight.
In this interview, we will ask you to build a system with multiple components. The question may cover the following topics:
Client-server communication Data structures and flows Be prepared to lead the discussion with your interviewer, ask questions where needed, and state your assumptions. Additionally, ensure you clarify with your interviewer whether to create a diagram or code based on your discussion.
We will use HackerRank’s for this interview. Use either tool as a whiteboard to help document and communicate your design to the interviewer. You are free to add as much as you like—it doesn’t need to be structured.