Raken Interview Questions
& Process

The interview process was straightforward and respected. It was a quick process with standard steps, and hybrid options were available. I enjoyed getting to know the team and what they offer. It felt like my time was valued. I was also able to be flexible with my different time slots.

The interview process involved three separate 30-minute interviews, which honestly felt like a complete waste of my time. They kept asking the same old questions over and over. The first person I spoke to seemed pretty checked out but still passed me along. The last interviewer wasn't prepared at all and rushed through everything. It was unprofessional and frankly unacceptable that they didn't know what we'd already covered in earlier stages. The whole thing lacked any real structure and felt like it was put together last minute. It even gave the impression that the role itself wasn't really that important to them.

This interview process took a whole month and had 4 parts, which felt like a let down. It was a red flag that it took so long just to string me and other candidates along. They even had me give references, but never checked them. They made it seem like the reference check was done before moving to the final part. I get that they're a smaller team, so I was patient, but the role was open for weeks and they seemed to be interviewing just to pass time. The questions were repetitive and the process felt disorganized. I wasn't into the "Bro" culture. The first three interviews were fine, the people seemed cool and down-to-earth. The last interview felt rushed and like the interviewer had already decided. Just be aware of your time investment. Good luck, hopefully, others don't have this experience. Every "no" gets you closer to your "yes"!

I have interviewed and been interviewed a lot in my career, so I am very familiar with the software engineer interview process. The interview at Raken for a Senior Software Engineer was definitely the worst I have seen. Most questions asked were not relevant to software engineering, and then the questions that were about software covered very obscure language features in an attempt to show that the interviewer could google and find the most unused and arcane parts of the language. I did leave the interview early because it was like playing a game of trivial pursuit, and I could tell this was likely not a place I would want to work at.