Scantron Interview Questions
& Process

The interview process wasn't too difficult, and the managers were really nice. The company is midsize and undergoing a lot of changes due to mergers and acquisitions, so I'm not sure about their revenue or growth yet. The HR and onboarding process was very thorough, including a background check and drug testing.

After applying, I got an email from a Help Desk Operations Manager about a 30-minute Teams interview, about a week after applying. When I joined the interview, another manager joined who said they were from Secur-Serv, then the primary manager joined. The initial email from the Ops Mgr was suspicious because it lacked a signature, making me consider checking with Scantron HR. During the Teams interview, neither manager's video was on. When I asked about it, there was no response, and the conversation moved on. This was also suspicious. I couldn't find any info about these managers online or on LinkedIn.

I had two rounds of phone interview then 3 rounds of in person interview. Phone interview was about datastructure and algorithm skills. They gave problems, I had to solve them and code. Finally, I communicated the code over the phone and they gave me the result immediately. In the face to face interview, the process was the same. They expect the candidate to code... code... and code without any hesitation.

The initial contact with the company was good, the recruiter kept me updated throughout the process and informed me about the number of interview rounds. The organization of the interviews was also well-planned, with clear communication about the interviewers' names and their roles. I had 3 telephonic discussions and 4 rounds of face-to-face interviews, each lasting an hour. Round 1 was a telephonic call with the SVP, discussing my current role and technical aspects of model-based testing and automation. Round 2 was a telephonic chat with the Program Manager about my responsibilities and handling complex releases. Round 3 was a telephonic call with the Development Director, focusing on planning, envisioning, handling production issues, and working under tight deadlines. This was followed by salary negotiation with the HR manager, which felt pressured. Round 4 was a face-to-face with the Senior DEV manager, discussing my hiring experience, role, ability to stretch, and a technical question on self-join. Round 5 was a face-to-face with the Sr. Program Manager, who seemed unprepared and discussed planning rhythm, process overlap, and SCRUM. Round 6 was a face-to-face with a Sr. QA Manager who appeared stressed, unprofessional, and unprepared, asking questions more suited for a QA Engineer role, like testing scenarios for Gmail & Google Talk Integration. I noticed a lack of role clarity and grey areas within the organization. Round 7 was a face-to-face with the SVP, who discussed company goals and vision. I then asked about the role, team size, reporting structure, performance metrics, rewards, and growth opportunities, receiving satisfactory answers. I concluded that the company lacks clear structure for career paths, performance measurement, and rewards, with a strong focus on US operations and delivery from India. The work culture has high pressure due to process and delivery gaps, but it could be exciting for someone looking to drive change in a startup-like environment.