1-) 30 min talk with the recruiter This is a regular recruiting interview, going over experience and why you want to work in Camunda. 2-) Coding Challenge This is a coding challenge focused on parsing a BPMN file and getting some information back. 3-) Hack Session This is a pair programming session where you would solve a series of tasks with a Camunda engineer. 4-) Hiring manager This is a freestyle interview with the hiring manager where he would make any type of questions to you. 5-) White Board Session This is a session going over the design of the Camunda engine on the fly and how would you come up with a similar design to what they have done already. 6-) Meet team - Interview This is another freestyle interview where you are supposed to get to know a team member and they ask you whatever questions they want. This process is difficult because it is just way too long. Too many superfluous interviews that don't really add information that the previous interviews did not cover. By the end I was just too exhausted. However, since there were no leetcode puzzles, it was a positive experience because the challenges are closely related to what you do in the day to day.

They have a straight and trivial interview process: - Phone call: Very simple questions about the current job and what is your dream job. - Coding challenge: they said they don't want tests or clean code, this already makes you think about the quality of their assessment. Try to write test and in a clean way anyway. - Hack session: I would like to spend 2 words here. I was interview by an arrogant and misleading person. He was able to misunderstand every question. Same test as the coding challenge but with a very conceited person. Just a note: the current architecture of their endpoint is quite trivial and not following any kind of guidelines, so look at it as something you would not aspire to implement.