Technical Interviews: Ask Relevant Questions


Having sat on both sides of the table, I'm always surprised to see Technical Interviewers ask questions that are not relevant to the role or skill level for which they are hiring.

These questions can be useful, and I definitely understand why they're asked - but in today's world, the approach can be a dated. Once upon a time, Software Engineers needed a wider breadth of knowledge because technology was less mature. But as languages have matured, and as hardware's become more stable and powerful, it's allowed developers to focus and specialize around an area of expertise. Thus, the classical questions of yester-year are less relevant.

For example, if your role is mostly front-end focused - your questions should be around UI development, events, accessibility, data collection, validation, filtering, presenting. If that's not your skillset, have someone else sit in and ask questions. Or, have the candidate talk through their GitHub projects, or portfolio.

But what if your application actually deals with tree-structures? This becomes less a question of role and more a question of skill level. If you've budgeted for a Jr developer, the question you should focus on is whether they can learn such concepts and grow in their role.

I've seen similar challenges with Technical Interviews for Architects, Engineering Managers, and other Sr titles. Especially when the role can vary widely from one company to another, it's really important to that hiring managers have a clear sense of what they need, set clear expectations around the capabilities.

  • Will your Architect/EM still be writing code?
  • Do you need your Architect/EM to be skilled in Application or Infrastructure Architect, (or both?)
  • Will your EM be a part of application design?
  • Do they need to be experts in Agile?
  • Are you looking for experts in Cloud?

Whenever it's unclear, candidates should always feel comfortable asking interviewer about the expectations for the role. Even if it's a simply asking: "In what areas does this role needed to be an expert, mid, and novice?"

If you're asked a question that doesn't seem relevant to your role, you should certainly start by responding: "I've not typically encountered this kind of question when interviewing for this kind of role. I'm happy to answer it - but before starting, are you gauging my general knowledge or does this question reflect the expectations for this specific role?"

This points to the importance of being conversational in interviews and having a dialog. It allows both parties to better assess fit.

At the end of the day it's impossible for both the hiring manager, or the candidate, to be successful when expectations are ambiguous.

Popular

Let's Clear Up The Ambiguity!

Image
Job seeking is hard - especially when you factor the ambiguity around expectations, the lack of transparency and consistency around process. It's frustrating dealing with the sheer subjectivity of everyone's opinions. Just think of even the basics: How long should your resume really be? Traditional black and white, or modern? Should you include a headshot? Oh - and cover letters - are those needed? Is anyone actually reading the cover letter? What are they looking for? Is there a bias for people with a more traditional background? Worst of all: The dreaded typo  that you catch only after applying to your dream job.  Are typos really going to cost you the opportunity??? To help bring some clarity to the process, I surveyed a bunch of hiring managers. The results were really interesting, and very illuminating.     If you're on the job hunt, I hope this information helps out! One final note: My recent post,  7 Steps to Writing an Amazing Resume , factors a lot of this feedba
Read more

FAQs for a Software Engineering Hiring Manager

Image
Technical Interviews have evolved a lot since the early I transitioned from being a Software Engineer to an Engineering Manager. Particularly in the post-Covid era, there's been a greater emphasis on the person, which I think is an important and welcome change. Over the decade of interviewing hundreds of coders, I've also had the pleasure of working with various bootcamps, colleges, and hundreds of individual job seekers on LinkedIn. Across all the changes over the past years, across the various locations and mediums, something remained consistent throughout: The questions I get asked.  With that in mind, I thought - why not make a FAQ from my perspective as a hiring manager? While this is my perspective, it's based off years of observation and supporting data. But that being said, advice is not fact. You may disagree with certain points, and that's OK. Opinions we disagree with allow us to better understand our own views. At best, I hope these responses help you
Read more

7 Steps to Writing an Amazing Resume

Image
  Since sharing my resume template  I've received plenty of feedback from job seekers, HR and hiring managers - all of whom value its purpose. Two (now former!) jobseekers even shared that as soon as they used my template, they were getting calls. Something about this template works, and given the traction it's getting others, I wanted to share - in more detail - why  this approach works so well.  Before continuing, let me give an important disclaimer: This resume isn't a miracle cure that's going to land anyone their dream job. Unless they're filled with lies, resumes are only as good as the candidate themselves. But they can also be a whole lot worse. This template and approach are all about maximizing the potential candidates have by highlighting and summarizing key areas.  Last point before beginning: If you don't know me, it's worth stating this advice comes from more than a decade of having hiring a broad range of coders: straight out of college, high
Read more

7 Steps to Building your Portfolio MVP

Image
Often when I suggest to coders that they build a portfolio, I'll hear back: "I don't need one..." "With all the effort it takes to apply, where will I find the time?" Simply put, having a portfolio's never going to hurt your chances at landing a job - it can only help. That second question is where a lot of struggle - because applying to jobs can be time consuming. Especially if you're wrapping up a bootcamp, or having to manually type in your resume info after uploading your resume. That's why I made these 7 steps which, when done correctly, can really help you stand out with a hiring manager. And, the best part is, it should only take you 2 days. Being the Agile-Obsessive that I am, it's all about maximizing value while minimizing effort. Fix links to your Resume, GitHub, LinkedIn, etc. at the top where they're always accessible. Link to everything here - and then remove all other links on your Resume except your Portfolio link . It sa
Read more

Work Experience vs Professional Experience

Image
In reviewing a bunch of resumes this week, I noticed quite a lot of resumes with a  "Work Experience"  section. In each of those resumes, people had de-valuing some very valuable  experience - and I write that with no exaggeration. The problem is people were looking at their experience purely through the "Job Title/Relevancy" lens and had reduced their experience down to a list of discrete, random, disconnected jobs. No interconnectedness, no narrative thread weaving through it all. As much as you may feel some jobs have no way of being connected, the reality is  you   are always the connection . To not connect them on your resume is to lose all that growth, knowledge, skills, impact, value, and trajectory. In other words - you lose the " You " in the resume. I recommended they start with a small change. Reword "Work Experience" to "Professional Experience" because, ultimately, every single job they had was in service of building their
Read more