Skip to content
Client-server communicationSeparation of concernsData structures and flowsSystem extendabilitySystem scalability
We consider communication critical and evaluate it in the interview process. Consider the audience and the level of information requested. For example, did we request an overview or a detailed technical explanation of a project?Check with the interviewer if you want to share more or are unsure if the key idea was understood.Look out for visual or auditory cues that we are trying to interrupt. We may need clarification on something you said or to move the conversation along to cover all the required information. We are doing this to help you.Make it clear which parts of a project you worked on specifically and which parts were done by the team. This helps the interviewer. Don’t hesitate to talk about your accomplishments. Mention any significant work you did outside your job description. For example, did you do many interviews, improve a process, or volunteer in an employee group?Please familiarize yourself with our products. You will receive a voucher to try in your interview confirmation email. Feel free also to try
While coding or completing system design problems, use “Enter Minimal View” in the Meeting menu. Or use the shortcut ⌘ ⇧ M. This will create a small video window that remains on top of your collaboration tool.If possible, set yourself up in a well-lit area where you won’t be distracted.Don’t be afraid to ask for a break if you need one.It is OK to arrange interviews over multiple days to work best with your schedule.Sometimes pictures are clearer than words. If you have access to a whiteboard or notebook, it is helpful to have them nearby. There is also a “Whiteboard” option in the “Share Screen” feature of Zoom that you are welcome to use.
Share
Explore
Engineering Manager - Interview Guide
Hello! 👋 We're excited that you’re interviewing with Grammarly for our Engineering Manager role! In this guide, we share tips to help you prepare for and have a successful interview experience. Please don't hesitate to contact your recruiter if you have any questions.
Hiring Manager Call
45 minutes
This is an introductory call with the Hiring Manager who oversees the role. The conversation will build upon what you discussed with your recruiter. During this call, the Hiring Manager will ask you additional questions about your experience and background, and may inquire about your technical expertise and specifics. They will also take the time to answer any questions you have and provide more information about Grammarly, the team, the role, and any other details you might be curious about. Enjoy this chat!
Virtual Onsite Interviews
We may conduct these interviews over multiple days, depending on the availability and schedules of participants.
Software Development Skills
60 minutes
For this interview, you will work through a typical software development flow. You will work with existing code in a language of your choice (TypeScript, JavaScript, Python 3, and Java). You will start by debugging and fixing a known problem in the code, and then you will work on extending that code for a new product requirement.
To prepare for this interview, we recommend that you brush up on your coding skills - you should be comfortable writing code, and looking through, debugging, and updating existing code. Familiarize yourself with reviewing various data structures and algorithms (e.g., recursion, branch and bound) and evaluating your code’s time and space complexity, as well as justifying your decisions. and other similar platforms are great for practice.
System Design & Service Architecture
60 minutes
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 that will have multiple pieces. The question may cover the following topics:
Be prepared to lead the discussion with your interviewer, ask questions where needed, and state your assumptions. Additionally, ensure that you clarify with your interviewer whether to create a diagram or code from your discussion.
We will use
or 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. People Management
60 minutes
This interview will focus on your management style and ability to foster a healthy team environment that supports individual growth. Be ready to discuss your team, its structure, and how you’ve helped team members develop throughout their careers.
Manager Impact
60 minutes
In this interview, we will take an in-depth look at two projects you’ve led or played a significant role in. Be prepared to discuss the overall architecture, complex or innovative problems you solved, and how you drove the projects to completion.
CTO Discussion
60 minutes
As we build exceptional engineering teams, our managers must be able to engage with their people when necessary, requiring strong technical skills and experience. This session will cover technical depth, management abilities, and signals related to execution, growth, and scale.
This is an opportunity to meet , our CTO, and share your story. Come prepared to talk about your engineering journey, the projects you’re most proud of, and their technical complexity. Mark is eager to learn what matters most to you and to hear the highlights of your technical career.
Reference Check
We'll wrap up the interview process with a reference check through HiPeople.
General Tips for All Interviews
and , too!Interviewing Remotely
As a hybrid company, we conduct our interviews remotely via Zoom and use collaboration tools such as Coda, Google Docs, and HackerRank.
Tips for Zoom:
Other Resources
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.