MoT recently asked to hear about some unique interview experiences
And I also hear stories about interviews that aren’t as inclusive as they should be. Or even if they try they struggle to cater for the needs of the interviewee.
I’m curious to hear more, what would be a nightmare testing interview and what steps can we take to make interviews more inclusive?
3 Likes
I had a nightmare interview once, at least in terms of “bad fit”, although at least they interviewers were polite enough about it, so it wasn’t too nightmareish.
But, how about this:
- Questions were ALL based around ISTQB
- The team they were building was an additional layer of extra gatekeeping, to add on after the fact, and despite the fact the teams already had their own testers
- Despite the fact I had made it clear I wanted to work mostly remote to the recruiter, the job required 100% office time and couldn’t even be done remote
This was the only time I said no, in person, at the end of the interview. As not to waste their time having to let me know I didn’t get it. I was not interested, at, all!
4 Likes
Recruiter - list 3 tools that you’ve worked with.
Me - there are more than 3 important tools that I’ve worked with that are relevant to this position (back then, I already had 10+ years of experience).
R - doesn’t matter. I only have 3 empty fields here.
M - ok? I’ll think about that. What’s next?
R - how many certificates do you have, up to 5.
M - I have more than 5. Should I list them?
R - no, just the number. Doesn’t matter what they are.
That was a hard pass on my side ofc
4 Likes
A few things that could make interviews more inclusive;
- Ask the candidate their preferred method and setting
- Ensure all language used is inclusive
- Provide questions before hand in an accessible format (not a PDF without proper markup etc.) and where possible make them open questions
- Allow time for candidates to consider their answers (if not provided before)
- Ask if any accommodations are required for the individual and grant them without bias or complaint
There are probably many more
3 Likes
Yes, yes and yes. I strongly dislike phone calls in general (I will walk 2 miles to ask a question over phoning) and so many job interview processes start by putting me in a weak position.
On this, my nightmare interview was 8 hours of travel only to flunk the C++ technical test (having aced the SQL one). It broke me and over a decade on, I still run a mile when C++ tasks come my way.
I’ve since been on the other side of the table when its clear someone’s technical knowledge/skillset isn’t a right fit for the role. I’d much rather be able to know what level is expected in advance rather than on the day, in person.
4 Likes