The process is quite long and demanding, including a 6-hour technical assignment that must be completed in one sitting. Even after completing and passing this stage, the next step involves a dashboard panel interview with Solution Architect-style questions. While this was for a Technical Support Engineer role, only a few of the questions were directly related to the technical assignment or the role itself—many felt unrelated. Unfortunately, this stage can still be used to reject candidates, even after successfully completing multiple earlier rounds, including the main technical task.

As the first stages were pretty well described, will share the last two. After the "home assignment, you get to a whiteboard session, There, for 1.5 hours, you get to discuss scenarios. They essentially describe how Redis works. (see questions below) +++ The last stage is a mix of tech and behavior questions. Surprisingly it's the longest one and actually may last over 3 hours (supposedly 2). You might get asked for a pretty granular description of things that you might not essentially know.

First HR screen then call with hiring manager. The hiring manager then didn't show up for the interview, Had to reschedule. The call with the Hiring manager was a random sporadic rapid fire round of his favourite linux commands. No situational questions whatsoever just questions about commands, I had to argue with the hiring manager that while the answer he was looking for was right, The way I described was also correct but he didn't seem to understand that theres more than one way to do something in Linux. Next was a tech assignment which was fairly easy, configure redis on two servers and set up replication, write some small code to inject and read data using a data type, I passed this. Next was what I was told a session to discuss this in depth, Except on this call we spent about 5 minutes talking about the assignment then I started getting quizzed on the best way to deploy redis, I was told I could do anything I wanted except when I gave an answer and an explanation I was told I was wrong, even though I have described scenarios that have been deployed before and I had good knowledge of. After this I was rejected, I was relieved, a complete car crash process and nothing in the interview was really on the job description. In my opinion, the interviewers only asked me questions to see if I knew what they knew, this is the wrong way to conduct candidate interviews and if these folks conducted themselves in my current company I would not let them within a mile of a candidate. Avoid this company as it seems very chaotic and stressful to work there.