1. IQ Test

The IQ test was the weirdest part of this whole process. I've never seen a company send out IQ tests before. It felt like a red flag from the start, but whatever.

1. Take-Home Assignment

This wasn't too difficult. The task was to create an API to provide some data with filters and then dockerize it.

1. Three-Part Onsite Interview

This consisted of system design, coding, and behavioral components.

• System Design: The system design portion was fairly straightforward, but I didn't particularly like how the interviewer handled it.
• Coding: This was one of the easier coding interviews I have done, about average medium difficulty.
• Behavioral: The behavioral interview was odd, as it was with the CTO. He is quite the character; it seems to me he tries hard to appear cool but generally comes off as unprofessional. I appreciated the transparency from the CTO, but it didn't feel like an actual interview.

1. "Bar Raiser" Interview

This was a behavioral interview with an executive outside of the engineering department. They seemed disinterested and weren't very clear about what they were looking for.

Honestly, there were many red flags with Rokt:

• The IQ test.
• Even asking about work-life balance (WLB) is frowned upon. The CTO was straightforward about the fact that if WLB is a priority for you, you shouldn't work at Rokt.
• The role definition was very unclear, and nobody could clarify it for me.
• The company put off a "work hard, play hard" vibe, which just comes across as "work hard."
• The engineering team is distributed across Sydney and New York, meaning late nights and long hours.

Honestly, I would just avoid Rokt. The money is very tempting, especially since their options package is generous in theory, but I am curious to see how those options actually materialize if/when they IPO.

Nothing crazy. I wouldn't worry about the technical interviews too much. If you're passing other technical interviews, you'll probably pass this one.