The One Thing to Never Say in an Interview
Pitfalls seem endless in the interview world; here’s how our Oxenham team manages one of the most common.
Bashing former employers, even if justified, may cost you that new job.
There's a story for every move and, short of recent layoffs, I've seen a number of individuals looking to make a jump from companies where their values and abilities aren't aligned.
Perception is reality on the side of interviewers, especially in what could be a short 30 minute initial screen, and well-meaning comments on disagreements over technology, leadership, or other decisions in your current or previous role can come across far more negative than intended.
Framing things neutrally, i.e. "I thought Rust would have provided more advantages than C++ for our project because of xyz" is a great way to show your technological acumen without allowing the risk of perception to creep in.
An alternative, too, is focusing on the positive aspects of the prospective employer's tech/people culture you've heard from either their website or recruiter.
If you're asked point blank "why are you leaving your role" it's still acceptable to keep things concise and say "I could see my values and career goals aligning better with a team like yours than my current situation."
You can get across the kind of environment you thrive in or are attracted to without divulging the entire contents of your burn book.
Find a meaningful outlet for catharsis, to be sure, but I've found it's slightly healthier to take a real hike than being told to take one by a prospective employer. Humor aside, the goal of the interview process is to direct focus around positives for the future rather than negatives of the past.
Ask yourself in advance of entering an interview “where could perception could creep in?” and “where do frustrations with my previous experience lie” then be ready to reframe them for good.
Then go make that impact with your new company you’d have liked to see all along.
— Pat Dunford, Recruiter, Technology Services