1. Phone screening (1 hour)
2. Remote programming test (2 hours)
3. Onsite interviews (5 interviews, 5 hours - a whole day process)
   • Interview with Senior Engineer: 3 algorithms on a whiteboard (1 hour)
   • Interview with Hiring Manager: Lunch interview, algorithm on a whiteboard
   • Interview with Performance Engineer: 2 questions for 2 different design scenarios, testing scenarios, background, and current work-related questions.
   • Interview with QA Engineer: This interview was challenging. The engineer seemed focused on a communication error between two computers. After a significant amount of time, the discussion shifted to a code review of the Remote Programming Test (RPT). The code, which was fully functional and written under time pressure, was not reviewed as expected. Minor points were raised, such as the use of a general catch Exception instead of a specific one in certain scenarios, without acknowledging the time constraints.

Algorithms Core Java testing Agile specific topics Distributed caching Spring framework related questions Automatic build processes Jenkins