For face to face interview, I met with 3 people in person and over video conference, with 2 other engineers, QA manager and director. One of the HW engineers asked me what “DHCP” stood for, “how to look up DNS on Linux”. Each interview was about an hour, through lunch. The eighth person was the HR, she had questions she had already asked but I was completely beaten up by this time.
Afterwards I thought this was NOT an effective way to evaluate any talent: I was extremely disappointed because the recruiter had told me I was their prime candidate, then kept me waiting for almost 4 weeks while they searched for a better candidate. At the end the recruiter told me they chose another candidate. Apparently that candidate was a more effective in defending themselves in meetings and a better negotiator. Ironic, my network and QA engineering knowledge got trumped.
What is your approach to creating a test plan?
What does DHCP stand for?
How do you attain DNS information on Linux?
The following metrics were computed from 1 interview experience for the Sonos QA Engineer role in Cambridge, Massachusetts.
Sonos's interview process for their QA Engineer roles in Cambridge, Massachusetts is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Sonos's QA Engineer interview process in Cambridge, Massachusetts.