You'll work with some very smart engineers. It's not a bad stepping stone if you don't mind the stress and enjoy learning on your own.
Your experience will be based 100% on the department and team. Little to no formal mentoring occurs; you'll have to seek it out.
Beware the legacy systems. They are poorly documented, and most likely the person that built them rage-quit six months ago.
If you ask for a walkthrough, you'll be pointed toward the tech handbook, which is poorly maintained. If an answer is there, it's likely outdated.
Most teams have on-call rotations, and things go down frequently due to poor communication. This is probably because the typical product person is split between three to four different teams.
Steer clear of tech debt teams.
Most of the problems at Tempus stem from the CEO and his insufferable Steve Jobs complex. Your entire tenure could be spent on a vanity project.
Don't hold your breath for the IPO.
The interview process was straightforward. There was a recruiter call, a chat with the EM/PM, a technical assignment that felt pretty realistic, and a final round which included a chat with the Director of Engineering, Tony, who was especially nice.
The recruiter contacted me minutes after I submitted my application. I had a phone chat with him. Then he sent me a 2-hour technical challenge that has 2 coding and 10 multiple-choice questions. I nailed it. The second day, I got the email arranging
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 wi
The interview process was straightforward. There was a recruiter call, a chat with the EM/PM, a technical assignment that felt pretty realistic, and a final round which included a chat with the Director of Engineering, Tony, who was especially nice.
The recruiter contacted me minutes after I submitted my application. I had a phone chat with him. Then he sent me a 2-hour technical challenge that has 2 coding and 10 multiple-choice questions. I nailed it. The second day, I got the email arranging
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 wi