Interview Experience for Quality Engineer – L4 Role at Apollo.io Interview Process: 1. Coderbyte Test – 70-minute online assessment (to be submitted within 48 hours) 2. Technical Interview – 60 minutes 3. Coding Round – 60 minutes 4. Take-home Automation Task – 2–3 hour Cypress assignment (to be submitted within 48 hours) 5. Test Automation Task Evaluation – 60-minute discussion on the submitted task 6. Behavioral Interview – 45 minutes After clearing all the initial rounds, including the take-home Cypress assignment, I was invited to a Test Case Design Round. This final technical discussion focused on three key areas: • Writing comprehensive test cases for given real-world scenarios • Identifying bugs from a UI screenshot • Justifying test case prioritization and coverage strategy Despite successfully completing all rounds, I received a rejection email shortly after this final stage: “Thank you for taking the time to speak with our team and for your interest in the Quality Engineer position at Apollo.io. Unfortunately, the team has decided not to move forward with you in the interview process. We appreciate your enthusiasm and the time you spent meeting with us. If anything changes on our end, or if we open a position more aligned with your background, we’d love to stay in touch.” While I respect their decision, I must share that the entire process—from start to finish—felt overly time-consuming for a single role, with multiple in-depth rounds and take-home tasks that required significant effort. Additionally, I had spoken to a current employee during the process, who mentioned concerning aspects of the work environment: • High pressure and unrealistic expectations in projects • Reports of employees being let go frequently • Poor work-life balance If you’re applying for this role, I strongly recommend evaluating these aspects before moving forward. Sometimes, not getting selected is a blessing in disguise.