Rokt Software Engineer interview questions

Overall, had a great interview process. Like others have mentioned, the recruiting pipeline starts with an IQ test. This was initially a red flag for me, but I had such good experiences during conversations with the team that I was glad I looked over this strange detail. The takehome is pretty straightforward, and so are the algorithms & SDI interview. Everyone I met was super passionate about their work, and they were nice.

1. IQ test - Weirdest part of this whole process. Never seen a company send out IQ tests before. Red flag from the start, but whatever. 2. Take Home - Not too hard, create an API to provide some data with filters and dockerize it. 3. 3 part onsite - Sys design, coding, behavioral. Sys design was fairly straight forward but don't really like how the interviewer handled it. Coding was one of the easier coding interviews I have done, average medium difficulty. Behavioral was odd as it was with CTO and he is quite the character. Seems to me that he tries hard to seem cool, but generally comes off as unprofessional. Appreciated the transparency with the CTO but didn't feel like an actual interview. 4. "Bar Raiser" - Behavioral with an executive outside the engineering department. Seemed disinterested, wasn't very clear what they were looking for. Honestly lots of red flags with Rokt. - IQ test - Even asking them about WLB is frowned upon. CTO was straight forward about the fact that if WLB is a priority for you, you shouldn't work at Rokt. - Role definition was very unclear and nobody could clarify it for me - Put off a "work hard, play hard" vibe which just comes across as work hard. - Engineering team distributed across Sydney and New York meaning late nights and long hours Honestly I would just avoid Rokt. The money is very tempting since their options package is generous in theory, but I am curious to see how those options actually materialize if/when they IPO.