Superhuman logo

Superhuman Frontend Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 14 interview experiences Β· FREE TO READ

3.4 Rounds average
Average Typical difficulty
71.4% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Superhuman.

Showing 3 of 14
Superhuman logo
Superhuman

Frontend Software Engineer

Engineering Β· more than a year ago

Senior Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Behavioral Coding System Design Behavioral

The interview process had 4 parts. First, a hiring manager chat about your experiences and projects. Then, a technical coding challenge using React, TypeScript/JavaScript. After that, a front-end system design discussion. Finally, a cultural fit interview.

Confirmed questions4 questions
  • Can you share a situation from your past experience or a project you worked on?
  • Your task is to build a React app that searches for and shows GIFs from an API, using Typescript/Javascript.
  • How would you approach designing a front-end system?
Superhuman logo
Superhuman

Front End Engineer

Engineering Β· more than a year ago

Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Technical Coding System Design Behavioral

I applied online through Grammarly's careers page. A recruiter contacted me within a week to talk more about the job and schedule a tech screen. The job posting I applied for was no longer listed, so I checked with the recruiter. They said they took it down to process current applicants, which I liked because it means they're actively hiring for listed roles and you're more likely to hear back. After the tech screen, I had a virtual on-site with front-end coding, system design, and behavioral interviews. I got to ask a lot of questions about working at Grammarly during the interviews. The original team I applied to needed someone more experienced, but they offered me a spot on a different team. I talked with the new hiring manager, and we both thought it would be a good fit. The whole process took about two months from applying to getting an offer, but it could have been faster as I was busy sometimes. The recruiter was flexible with my schedule and kept me updated on everything.

Confirmed questions1 question
  • Standard interview questions focusing on web front end development.
Superhuman logo
Superhuman

Frontend Engineer

Engineering Β· more than a year ago

Mid Difficult Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Panel Group Presentation
Interview formats
Behavioral Technical Coding System Design

Started out positive with an initial 30min screen with the hiring manager, who was great, empathetic and relational, which is often not the norm in engineering. I look for that, especially from managers. I'm fatigued by the countless engineers who lack social skills and empathy, even though they work at companies who list empathy as a core value and essentially bypass those values, get hired because of their non-empathethic left brain. Frustrating. Next was 1 hour technical interview with another Frontend Engineer. Medium difficulty with a range of questions about React, native browser features and a 20min live coding, solving for a simple algorithm as well as some basic HTML, CSS and JS rendering. It was also a positive experience because the questions were relevant to the qualifications listed for the FE role. Next was a 5.5 hr long virtual on-site. This is where things started going downhill with a variety of negative experiences about their recruitment process. The schedule was packed and not considerate of the candidates time or well-being. It felt like a stress test. The recruiter didn't exemplify empathy or compassion, was instead passively dismissive to my concerns about the interview not feeling equitable. The recruiter also arrived late to our initial meeting by about 10mins and never acknowledged their tardiness or expressed consideration of my time. Unusual. Virtual on-site was split into 5 parts. CS fundamentals, system design, frontend and behavioral, along with a virtual 30min coffee chat with two other current employees, one a PM and FE. Virtual chat was a total failure and waste of time and energy. The two people arrived and stood there silent while I facilitated the entire conversation with them. It was awkward and exhausting. I could've used that time to rest instead. Overall, some people on the panel were great and embodied Grammarly's EAGER values. Recruitment process did not. And why are CS fundamentals equally valued for a FE role? πŸ€”

Confirmed questions4 questions
  • Could you animate this element to the right over 1s?
  • How would you determine if something is within the browser's global namespace?
  • Can you explain the inner workings of Redux?

Superhuman Frontend Engineer Interview Questions

Quoted word for word from Superhuman interview reports.

β€œHow would you determine if something is within the browser's global namespace?”

Read reports β†’

β€œHow would you write your own version of the `myBind` function in JavaScript?”

Read report β†’

β€œGiven a problem, find the most optimal solution in terms of time complexity.”

Read report β†’

β€œCould you create a basic React component to show a list, with functionality to add or remove items?”

Read report β†’

Formats, difficulty and experience

Across all 14 Superhuman interview reports.

Interview formats

Behavioral 31%
Coding 26.2%
Technical 23.8%
System Design 14.3%
Presentation 4.8%

Interview difficulty

Easy 0%
Average 85.7%
Difficult 14.3%

Candidate experience

Positive 71.4%
Neutral 7.1%
Negative 21.4%