I recently went through an extensive interview process for a position. It started with an initial call from a recruiter, followed by a take-home HackerRank assessment. The assessment included three multiple-choice questions focused on AWS, a simple SQL query, and a medium-level C# coding assignment.
Next, I had a technical interview where I was asked to solve a coding problem involving finding repeating numbers in an array without using collections. This round also included discussions on the pros and cons of microservices and some straightforward C# questions.
The final round involved interviews with a manager and a tech lead. We discussed my previous team's perspectives, the technologies I have used, and the methodologies we followed. They also asked about API performance testing, Kafka, and Agile practices.
After completing all rounds over a span of three weeks, I received a message stating that I was one of the strongest candidates. However, due to the high level of competition, they decided to select another candidate for the position. This experience reminded me that sometimes, no matter how well you perform, a bit of luck is also needed.
Pros and cons of microservices.
API performance testing.
C# coding assessment on finding a repeated number in an array without using collections.
The following metrics were computed from 1 interview experience for the McDonald's Software Engineer II role in Dallas, Texas.
McDonald's's interview process for their Software Engineer II roles in Dallas, Texas is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for McDonald's's Software Engineer II interview process in Dallas, Texas.