
Superhuman Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 108 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Superhuman.
Software Engineer
I interviewed for a Software Engineer (Early Career) role at Superhuman and enjoyed the process. It included a recruiter screen, CS fundamentals, a backend coding interview, a project presentation, and team match conversations. Every stage was well-organised and clearly communicated. My recruiter was supportive throughout. She proactively shared detailed info about each round and was responsive. The technical interviews were challenging but fair. The team match process was my favourite part. I spoke with a few engineering managers across different teams, and each conversation felt genuine. They pitched their teams honestly and gave me real insights. I got matched with my top choice.
- Leetcode questions
- LLD/SysDesign Type Questions
- Project Presentation
Software Engineer
The interview was a standard 5-round process (CS round, app development, system design, impact round, and a call with the CTO), not counting the initial recruiter and hiring manager calls. The entire process went really smoothly. My recruiter was super nice, and we'd chat about feedback after each call. They even gave me tips for each round, which was pretty helpful. They gave me the Superhuman Go subscription during the interview so I could try out their product.
- Can you tell me about some proactive challenges you faced that led to significant impact?
- Design a system for a popular application.
Software Engineer
The interview started with a recruiter call, then a technical interview. The technical part was all Leetcode questions, with 4 questions in 50 minutes. I did them one by one, optimizing for space and time. It felt good at first, but after 3 questions, I was getting tired and wondered how these related to what Grammarly engineers actually do. They were not tailored to Grammarly's problems, just generic HackerRank questions. I finished the first three, including a DP approach for Climbing Stairs, but they still seemed unhappy with my fourth answer. I know hiring is tough, but this felt lazy and frustrating, making me just recite problems, DP tricks, and complexity. It just shows how much Leetcode you've grinded and how many tricks you know. You guys should really improve this, at least make it relevant to Grammarly's actual work. Based on these questions, I'm not sure you're solving your problems effectively if they aren't on Leetcode. I wouldn't recommend this process.
- Could you solve the Climbing Stairs problem?
- Can you remove all adjacent duplicates in a string?
- How would you remove all adjacent duplicates in a string with a modification to find characters to replace, like in ascending or descending order?
Superhuman Software Engineer Interview Questions
Quoted word for word from Superhuman interview reports.
“Implement a data structure that supports generating a random element in O(1) time.”
Read reports →“Can you determine if a given long string can be entirely segmented into words found in a provided dictionary, and if so, find the minimum set of such words if multiple segmentations are possible?”
Read reports →“How would you remove all adjacent duplicates in a string with a modification to find characters to replace, like in ascending or descending order?”
Read reports →“Could you implement a rate limiter that restricts requests to a maximum of 'n' per time unit?”
Read reports →“Build a React application that takes user input, queries an API, and then displays and styles the retrieved results.”
Read report →“Could you refactor this piece of code to handle concurrency issues and work in a concurrent environment?”
Read report →“Describe how you would design a web server capable of managing multiple clients simultaneously reading and writing the same data.”
Read report →“Can you implement some algorithms and discuss their time and space complexity?”
Read report →“Could you explain how you would profile Java server-side code and troubleshoot issues on a system handling high loads?”
Read report →Formats, difficulty and experience
Across all 108 Superhuman interview reports.