I applied for the Site Reliability Engineer position through a job platform in June 2022. The recruitment process consists of 4 stages: - HR interview - Technical Challenge...A very interesting one :) - Technical Interview - Executive interview HR interview: I was called for the HR interview a day after applying where I scheduled it within 6 days. I learned more about the company beyond what was on the website along with a discussion about salary, benefits, the general recruitment process, and tips to help me with the next stage. I got the technical challenge 2 hours after this call ended. Technical Challenge: Instructions about the challenge was sent and I had 7 days to complete the challenge. The challenge had 3 tasks: - Task 1: Coding related (with a spice of monitoring). - Task 2: IaC to deploy task 1 (if it was done). - Task 3: CI/CD for task1 and task 2. This stage was very interesting as the success of each task wasn't dependent on the tool but rather on the approach used to solve the problem (I love the flexibility this brings). So, you are free to use and do whatever you feel necessary to both deliver the tasks and impress the engineers as well ;). The challenge duration was 7 days. N/B: After the task has been reviewed, detailed feedback will be sent on each task consisting of: - What you did well, - What you could have done better, - What you didn't do well, - What you didn't do. Technical Interview: This stage was a team interview with all its members. It started out with a light individual introduction with light jokes to make the environment cool (I must say, the engineers here are really experienced and fun). This stage was like a defense of my project. It was focused on: - what I would have done to make the project better, - why I selected the approach/tool/implementation, - what would it be like for production. I would say it was one_ man_at_a_time drilling. For each answer I provided, I was asked further questions on it. I was asked 10 questions (2-2-3-3): - 1st and 2nd sets of questions were conceptually based, - 3rd set was production-focused, - 4th set was team culture fitness. I got the opportunity to learn more about the team requirements and what tblx is doing on a deeper level. After the technical interview, I got detailed feedback about why I won't be moving forward with the process with a major con of seeking someone more experienced (senior) while my profile was a "junior-solid" in their opinion.