There was an initial call from the recruiter where we discussed some basic aspects of the role. This was followed by a one to one call and later a meeting with the manager of the team. In these calls/meetings we discussed what I had done, how I had overcome challenges, successes, how I prioritised my workload etc. I then had a 45 min technical interview where I had to answer a range of questions related to integration and other technologies (REST, SOAP, containers, Cloud etc). These were fairly detailed and scripted, but they were not designed to catch you out, just to make sure you had a good understanding of these technologies and modern architectures. Finally there was a demonstration and presentation to a small panel (2 people in my case). For this I had to build a demo based on a use case and pitch it using the key messaging behind the Mulesoft platform. This took a fair amount of time to prepare and although there is a lot of collateral online to help you, my advice is give yourself plenty of time, practice beforehand and make sure you time it. In my case I had 45 min to present, which meant that excluding time for questions - and you get a lot - you will only have 15-20 min to present and 10 min to do your demo. Being credible, articulating the key benefits of the Mulesoft API-led connectivity approach and handling objections well ,seemed to be key here.

2 interviews one with HR, one with manager and then panel interview. Then salary discussion and then a very excellent onboarding trajectory. Last step when you get hired is a full background check.