iClassPro Software Engineer Interview Questions
& Process

The interview process was unique. It started with a one-way interview, followed by personality type quizzes that seemed more suited for retail than tech. The recruiter wasn't very familiar with the role or the mobile platform's tech stack. The technical challenge involved React Native and Swift, and it concluded with a LeetCode-style problem.

The hiring process was pretty smooth and everyone was nice. I first chatted with the hiring manager, then did a timed skills test that was recorded. After that, I had a final video interview with some of the team. The technical parts felt relevant and fair for a senior PHP/Laravel job. I was upfront about my salary expectations, but the offer was way lower than I discussed and also below market rate. So, while the interviews themselves were professional, the big difference in the offer after being open about pay was a concern. It made me wonder if they really understand the value of experienced engineers.

The HR hiring process seems poorly thought out. I was asked to complete a test that included three parts: a set of Laravel questions, a series of middle school level word problems, and a LeetCode style coding challenge. About half of the Laravel questions were relevant and practical. The rest focused on obscure function names rather than core concepts like facades, Eloquent, the service container, or dependency injection. Trivia like this is not a good measure of real Laravel skills. We use documentation for a reason. The word problem section is not difficult, but I fail to see the value. Be sure to bring a pencil and paper, there is no warning about the format, and once you start, you’re locked in with your camera on. The final part required writing a sorting algorithm from scratch without using PHP’s built in functions. Most senior level engineers have not hand coded a sorting algorithm since college. Really bizarre way to assess senior talent when you provide them an exercise that a college student would probably score higher in. If the goal is to hire strong engineers, consider a real technical conversation where you go over core Laravel features. Then if necessary follow up with a relevant take home task to show their skills. This test doesn’t reflect real world development skills and was a complete a waste of time.