Airbus did everything in the book of how to give a developer a bad interview experience.
1- I applied and I didn't have a call or any contact for 2 weeks after that, I received a behemoth of a coding challenge that requires at least 10 working days (and the challenge also have a deadline after 10 working days)...
2- Without having any call about the job, knowing if they support remote work or the range of the salary and by spending some of my vacation days to work on that challenge, I managed to finish it and send it in time.
3- I didn't receive anything from Airbus afterwards... nothing... not an email saying we received the coding challenge and will look into it, not an email saying you passed or you failed... nothing...
4- After a month of complete silence, I reached out to the department/person, who sent me the challenge asking for any information... and I still haven't received any communication from them (more than a week later)
Build a whole Jenkins server fully automated with Ansible and the configuration as code practices...
The server should work locally and react to webhooks to automatically deploy a fully ELK stack (that is also following configuration as a code practices with immutable configuration)...
Plus functional/performance/state testing... for both the Jenkins server and the deployed ELK stack.
The following metrics were computed from 1 interview experience for the Airbus DevOps Engineer role in Egypt.
Airbus's interview process for their DevOps Engineer roles in Egypt is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Airbus's DevOps Engineer interview process in Egypt.