Very quick process: a typical initial recruiter screen/call, a couple-hour take-home assessment (not too hard), and then a 3-hour video call including talking to a product manager, a technical coding session, a "system design" session, and meeting with a director.
Most of the technical coding session involved various "quiz-type" questions in JavaScript. The recruiter mentioned I'd be able to choose my language for the technical session between Python and JavaScript, so I was thinking it'd be more of a general programming problem, which was not the case, so I was pretty thrown off.
I did not feel this was a good way to assess general programming skills or abilities, and it felt like a silly way to evaluate someone, to be honest. I got the vibe they just care about knowing JavaScript specifics super well and not much else.
I also got the vibe that the culture only prioritized working quickly to keep up with constantly shifting priorities.
Various JavaScript quiz questions and programming questions related only to specific concepts in JavaScript.
Talk through how you would build some specific type of application, what technologies would you use, etc.
The following metrics were computed from 5 interview experiences for the Tempus Software Engineer role in Chicago, Illinois.
Tempus's interview process for their Software Engineer roles in Chicago, Illinois is very selective, failing most engineers who go through it.
Candidates reported having negative feelings for Tempus's Software Engineer interview process in Chicago, Illinois.