Poly Interview Questions
& Process

The interview process was professional and well-structured. It started with a recruiter phone screen, then a technical assessment, and finally 2-3 rounds with team members and leadership. They communicated well and were approachable.

The interview process starts with an application/resume screening to filter candidates based on qualifications like experience, education, and keywords. Next, there's a phone/initial screening interview to check basic qualifications, communication skills, resume overview, availability, salary expectations, and some basic role-related questions. After that, a technical/skill-based assessment is given, followed by an offer.

We started with a 15-minute phone screening. A few days later, they set up a 30-minute video call for a technical background check. Then, they sent over a 2-hour coding challenge through Coderbyte. Finally, they scheduled a 90-minute final technical interview where we discussed Node.js and React.js.

I found the job on LinkedIn and the whole process took about a month and a half. It started off pretty well, with a recruiter reaching out and doing a basic phone screen. They asked about my career change motivations and why I applied to Poly. After that, the recruiter quickly connected me with hiring managers at the Westminster office, and I had a Skype interview with three of them the following week. This hour-long interview focused on why I wanted to leave my current job and if my background made me a fit for a Test Engineer role too. They also asked a few small technical questions related to my studies, and I got to ask them my questions at the end. If everything went well, the managers would pass my info back to the recruiter, and I'd set up an onsite interview. I was happy to get to the onsite, but that's where things got messy. The recruiter asked for my availability, and I told her which day worked best and that other days wouldn't work. She passed this to the coordinator, and I waited. A few days later, the coordinator contacted me about scheduling my interviews, which I needed to confirm. I noticed one of the proposed days didn't work for me, so I asked the coordinator if we could move it to the same day as the other interview to do a full day of interviews. The coordinator replied within a few hours, saying it wasn't possible because most of the team would be out on Friday, so Thursday was better for them and asked if that suited me. Just 10 minutes later, I got another email from the recruiter confirming both interviews, even though I hadn't confirmed the Thursday one yet. On the scheduled Thursday, I couldn't make it because of work obligations, but I was set for Friday. Friday morning, I drove to the office and arrived on time to check in with security. The instructions weren't clear; they said to go to the office and check in but didn't specify which building or provide signs for the main entrance. After checking in, I waited. 10 minutes. . .20 minutes. . .45 minutes. . .no one came to get me. I received a personal call and stepped outside. While I was on the call, the person I was supposed to meet walked across the courtyard to the security desk, then came back out and gestured for me to end my call. I couldn't do that, so he went back to his office. After my call, the recruiter contacted me, apologizing profusely, saying the interview time I was given was incorrect and that the interview was actually scheduled 90 minutes later than when I arrived. This was the first I was hearing about the time change. I decided not to proceed with the onsite interview since they had already wasted my time once, and I didn't want to risk it again, even though they offered to reschedule to fit my schedule. My initial gut feeling about Poly turned out to be right.