The interview process began with a call from a recruiter who asked basic questions to assess fit.

Next, candidates were given a coding problem to solve within 24 hours. If successful, the final stage involved a call with a senior software engineer for the decision.

The final call was decent; it was one of the easiest interview calls one could attend, featuring a simple LeetCode question solvable with two lines of code.

The major drawback was the inclusion of PHP-related questions. As a developer, the focus should be on identifying talent capable of solving real-world problems and thinking big. Instead, the interviewer seemed to prioritize debugging PHP code, which felt like an inefficient use of interview time.

As a graduate, I would definitely prefer more challenging interview questions. The way a company conducts its interviews reflects its standards, and in this case, the process was very poor.

Debug PHP: some random coding question (not challenging)