J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Superhuman (San Francisco, CA) en oct. 2018
Entretien
The head of the engineering org reached out to me and convinced me to take a call with the technical recruiter. I was then screened over virtual hangout and then brought in for an onsite interview. In general, these engineers typified what you might expect from an engineer: cold, lifeless, uninteresting, purely technical. Conversation with these developers was akin to speaking to a brick wall. They offer lots of IQ (i.e very strong technical prowess), but are ages behind where they need to be from an EQ standpoint.
The head of engineering and the engineering manager with whom I spoke were very lovely and seemed to have actual personalities - something that was very hard to find among the individual contributor engineers.
Basically, the interviews felt very one-sided conversationally and, if you intend to have even a remotely fun time at work, I would highly suggest you avoid Grammarly like the plague.
2
Candidature
J'ai postulé en ligne. J'ai passé un entretien chez Superhuman en juin 2024
Entretien
- A 1-hour technical assessment conducted through HackerRank code-pairing: practical coding and problem-solving.
- The interview will focus on domain-specific knowledge in your preferred language (React, JavaScript, Angular, or any other FE technology).
- Please be able to explain and talk through your approach, solutions, and ideas to optimize the code.
J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien chez Superhuman (Toronto, ON) en oct. 2022
Entretien
Pretty good experience overall. I didn't make it to the "virtual onsite", but had a good experience otherwise. Interviewers were very friendly and accommodating. The process was a little slow, but other than that it was really good.
J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez Superhuman (Austin, TX) en oct. 2021
Entretien
30 min screening.
1 hour technical. 20 minutes of pair programming. 20 minutes of answering React questions. Some of the interview questions were very poorly written with little to no input/output examples. Interviewers wouldn't describe question in further detail.