Camunda Devops Engineer Interview Questions
& Process

I had a call with a recruiter first, then I was given a technical assignment to create an application (Python or Go) for Prometheus and deploy it on a kubernets cluster. After that, I had a technical interview with the Engineering Manager. I was declined for lacking some technical skills, but the Engineering Manager said that Camunda looks more at personality and attitude than Technical skills, since these can be taught. I find this contradictory because I was denied due to my technical skills lacking, or maybe my personality did not fit and they were not honest on their feedback. I would have appreciated a clearer answer on why I did not get the position so I know how to improve, but it seems companies nowadays don't care to give proper feedback.

I did a bunch of research on the company before applying because I really liked their culture. I even checked out their GitHub and tried out their apps. I found a small issue and told the recruiter. The interview process seemed really well laid out with a Google Doc detailing stages and timelines. We then agreed on a coding challenge, which also came with a detailed document and a feedback timeline of about 2 days. I worked hard on it, switching from admin to DevOps, and finished the task, including writing, packing, and deploying a Python app to Kubernetes. I submitted it early on the 4th day. After 2 days with no word, I followed up on the 4th day. The recruiter responded on the 5th day saying the position was on hold and they were stopping the process, so I never got feedback on my test task. She then suggested another role, which I agreed to discuss, but then there was silence again. Two weeks later, she proposed a call. Despite my bad experience, I gave it another shot, but then there was silence again. The actual recruitment experience was way different from what they initially presented. I at least expected some communication and feedback on my task, as giving tasks creates an obligation. The salary wasn't special, but my goal was a remote DevOps role in a good company, and I achieved that, earning similar money as a senior admin before.

My interview experience started with a good chat with the HR person, which was nice. Then I talked to the hiring manager, and that went well too. The third round was a hack session. I messed up here because I didn't really get what they meant by 'hack session' in the description. I thought it'd be more about managing files or connecting to APIs, like typical DevOps stuff. But it turned out to be about making a game, which wasn't really what I expected for a DevOps role. Because I was unprepared for that kind of task, I couldn't finish it in time and didn't move forward.