Camunda Software Engineer Interview Questions
& Process

I was given a technical task to complete, and I submitted what I thought was a strong solution. However, the feedback I received on it was lacking. They scored the 'plus' aspects highly but then provided a set of vague buzzwords for the 'minus' points, which in turn led to an overall 'negative' assessment. This conclusion didn't make sense to me. I followed up with an email asking for more specific feedback on the 'minus' points, as they were generic and unrelated to the actual task. I hoped this was just due to a time constraint and that a more professional review was still possible. My email was ignored, and no clear explanation for the review's illogical outcome was provided. I suspect they are insecure about their review process and avoid giving concrete answers to requests for clarification. They seem to completely mishandle their recruitment, refusing to take accountability. In short, don't bother with this company; their culture appears toxic and irresponsible, and there's no guarantee of respectful treatment even if you get hired. It's deeply unprofessional.

The whole interview process took about a month. It started with an HR screening, then I was given a home assessment that involved working with tree and graph algorithms. After that, I had a chat with the team leader. Later, there was a hacking session focused on Java streams, which was pretty easy. The final step was a whiteboard session where I had to think about graph problems. Overall, I had a really good experience with everything, but unfortunately, I didn't make it past the last stage.

The interview process was quite straightforward. First, there was a phone call where they asked basic questions about my current role and my career aspirations. Next, I had a coding challenge. They mentioned they weren't looking for tests or clean code, which was a bit concerning regarding their assessment quality, but I tried to write clean code with tests anyway. The final part was a hack session. I have to say, this part was with an arrogant and misleading interviewer who seemed to misunderstand everything. It was the same test as the coding challenge, but the interviewer was very conceited. As a side note, their current endpoint architecture is quite basic and doesn't follow any guidelines, so it's not something you'd want to emulate.