Grammarly Software Engineer candidates describe a recruiter screen, LeetCode-style coding, system design, and in-depth conversations about past projects and values. One candidate reported about a month from first call to decision.
$159K
Avg. Base Comp
$335K
Avg. Total Comp
5-8 rounds
Typical Rounds
1 month
Process Length
Candidates who interviewed for Grammarly Software Engineer roles describe a loop that pairs standard technical rounds with unusually serious conversation about their own work. The usual shape is a recruiter screen, coding, system design, and one or more interviews on past projects, followed by a hiring manager or values discussion. Round counts differ: one candidate reports five rounds, another six to eight.
On the technical side, reports mention LeetCode-style problems, including two string problems and a rate limiter that allows no more than n requests per time unit. A backend-leaning candidate was asked about concurrency and refactoring code to be thread-safe, and another described a backend round built on practical patterns used on the job. Some described system design as standard, while another candidate was asked to design a new feature for existing infrastructure. Expect to explain complexity and tradeoffs out loud rather than just produce a working solution.
The most consistent theme is project and career depth. Several candidates walked through one or two major projects, defended their tradeoffs, and said what they would change. Another was asked about their best and worst experiences at a previous company and what they would have done differently. Prepare those stories as carefully as the algorithms.
One candidate was asked about relocation and noted that the "remote first" role expected at least two days in the office, so ask about location early. One candidate reported about a month from first recruiter call to final decision. Several describe responsive recruiters and prep materials or an interview guide shared up front.
Synthesized from 14 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Grammarly process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Grammarly
How would you differentiate between scrapers and real people given a person's browsing history on your site?
| Question | |
|---|---|
| Length Of Longest Palindrome | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Random SQL Sample | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Top 3 Users | |
| Find Bigrams | |
| Raining in Seattle | |
| String Shift | |
| Bagging vs Boosting | |
| Size of Joins | |
| Upsell Transactions | |
| Longest Streak Users | |
| Last Transaction | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Minimum Change | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Comments Histogram | |
| Job Recommendation | |
| Google Maps Improvement | |
| Get Top N Frequent Words | |
| P-value to a Layman | |
| Find the First Non-Repeating Character in a String |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe an opening call with a recruiter about the role and process. One was asked about relocation and learned the role expected at least two days a week in the office. Another candidate's screen included one LeetCode-style problem and an open-ended question.
Reported prompts include a rate limiter that allows no more than n requests per time unit, two string problems, and two easy-to-medium LeetCode-style questions. Candidates mention explaining complexity and tradeoffs out loud. One candidate had a second coding interview that was a bit harder than the first.
Candidates report a system design round that some call standard. Another was asked to design a new feature for existing infrastructure. Backend-focused rounds were also reported. One covered concurrency and refactoring code to be thread-safe, and another covered practical on-the-job patterns. One candidate was asked about distributed systems.
Several candidates were asked to walk through one or two major projects, including the decisions behind them, the tradeoffs, the impact, and what they would do differently. One candidate presented two past projects during the onsite. Another was asked about their best and worst experiences at a previous company.
Depending on the candidate, the loop included a hiring manager conversation that dug into a project, a bar raiser interview, a final conversation with a top manager, and a separate values or culture-focused round. Not every candidate describes all of these. One candidate spoke to about seven people across the process.
One candidate reports about a month from first recruiter call to final decision. Several describe fast recruiter feedback and few waits between rounds. One noted a short wait after the final round before the offer came through.
