Superhuman Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 9 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Superhuman.
Superhuman
Software Engineer
Mid Average Positive experience No offer 7 rounds
Interview process
Recruiter call Technical screen Onsite Panel Presentation
Interview formats
Coding System Design Technical Presentation
Great interview process! Candidates are guided through the whole process. Although the company has a lot of interviews and you meet a lot of people, which has upsides and downsides. You can learn a lot about the company on one hand, but on the other hand, feedback from people might be biased, and you need to impress around 7 people to get through.
Confirmed questions2 questions
- Answered LeetCode tasks
- Discussed in-depth system design
Superhuman
Software Engineer
Entry Average Positive experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical
I had a great experience with the interview process. It was clear what they were looking for, and everyone was kind. I'm excited about the role and think it would be a good place to work.
Confirmed questions2 questions
- Can you discuss your previous work experience?
- Tell me about your experience with system architecture.
Superhuman
Software Engineer
Senior Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Take home Presentation
Interview formats
Technical Coding Presentation
The interview process started typically with a recruiter call, followed by an hour-long video chat with the hiring manager. The next step was a take-home assignment where I had to build two API endpoints and set up data storage in a database. As I'm actively interviewing, I aimed to complete this within 2-3 hours, given my experience in software development and having conducted numerous interviews myself. I believe I completed the APIs successfully and they were functional. During the 30-minute presentation, I missed an edge case and noted the absence of basic mutexes, though I explained they'd be included in production code. I also discussed concurrency and built the API from scratch without any frameworks. My understanding was that this was a test of my thinking and coding abilities, which I'd rate as an 'A', not 'A+' due to a few oversights. I asked for feedback and received it, but I don't think it justified a rejection. I felt my effort and time invested should have at least earned me a chance for the next stage, likely system design or more technical interviews. A heads-up for future candidates: be prepared for a perfectionist interviewer or potential bias, and consider dedicating more than 2-3 hours, perhaps 4-6, to the take-home to include extensive testing, concurrency, mutexes, etc. It seems experience, skills, or time constraints are less important than submitting flawless production-ready code, which I find unusual for an initial interview.
Confirmed questions1 question
- Build two APIs and implement data storage in a database
Superhuman Software Engineer Interview Questions
Quoted word for word from Superhuman interview reports.
“Build two APIs and implement data storage in a database”
Read reports →“Can you explain the technical details behind how Google Docs enables multiple users to edit a document simultaneously?”
Read reports →“What are some ways to improve performance issues in a React application?”
Read reports →“How would you go about building a Google Doc?”
Read reports →“Could you explain async await?”
Read report →“Given a UI, how would you break it down into components?”
Read report →“How would you go about verifying performance issues in a React application?”
Read report →“Tell me about system architecture.”
Read report →“Tell me about your experience with system architecture.”
Read report →Formats, difficulty and experience
Across all 9 Superhuman interview reports.