Interviewing requires a lot of time and energy. Maybe you need to study some technical topics ahead of time. You probably already have commitments that require a lot of your focus—like another job or children. That's why it's important to be selective where you can about companies you want to interview with.
Here are the ten questions I'm using to decide whether or not I'm interested in interviewing with a company:
- How large is the engineering team?
- What is the make-up of the engineering team? Such as, how many managers are there, who do they manage, etc.
- How often are one-on-ones?
- Who are the one-on-ones with?
- Is there career coaching?
- Are there performance reviews?
- How have you handled performance reviews with the pandemic?
- What's the development process like? For example, do you work in sprints?
- How tasks are estimated and assigned?
- Are there regular team retrospectives?
Did you know I have a newsletter? 📬
If you want to get notified when I publish new blog posts or make major project announcements, head over to https://ashleemboyer.com/newsletter.
Top comments (41)
Good list Ashlee!
10+ interviewee questions I think are wise to ask:
Who are your customers?
How do you communicate with them?
How do you like working here?
What would you like the company to invest more time in?
What is a typical work day like here?
How do you approach testing?
How do your sprints work?
How do you, as a company/team, make sure you're working on the right things?
What is your tech stack?
What are the biggest concerns about your codebase?
If you were starting over fresh, what technologies would you choose that are different from what you are currently using?
What are your long-term plans?
Excellent questions!
I've used some of these before and they helped me to determine that certain companies weren't a good fit for me. I also asked things like this, relating to the career coach:
How do you promote growth for your employees?
I use this question to figure out if they provide study materials, conference tickets, etc etc.
Who do I talk to if I want to get a book about [programming topic]?
Do they have an interest in your personal and professional growth?
And most recently:
What are your views on remote work?
Great list. A lot of folks are totally lost here.
you can ask these of the initial screener but they probably wont have the answers. After they pass your resume on to the hiring manager and they call you there is no reason not to ask these questions. they will or should ask you if have any questions and that is the opportunity to ask. I think you will impress the interviewer with these questions and they in my experience they will answer as best as possible and their answers will allow you to honestly assess the opportunity for its appropriateness to you
Good question! I never asked about if there are any one on one meetings or performance reviews before. This are good questions to add to my list! Tnx!
Awesome list. I also ask about code quality and how it is maintained etc.
I wish I had thought about this before joining my current project, because knowing what I know now, it may have changed my destination.
Now don't get me wrong I love my current job but the politics at the moment. Our Engineering team is less than 15 people myself included if you had told me that I would have passed on the job, I know what happens in small teams it ends up being a handful of talented people doing the job while others do the bare basics. Due to the fact its a small team it can sometimes get a little heated, when it comes to the feedback. I have found that larger teams of more than 20 people its more sustainable.
Also if I new our development process I would have never joined, what is is that no testing lets keep pushing into production and fix the bugs as we go.... Real makes for fun times, being on the phone to the customer explaining the latest patch broke the system, and they will need to wait a few hours while we debug the system.
Try being on a team building the software calculating loads to go on rockets to and from the International Space Station, without testing. No, seriously. And, of course, they did Friday commits (cuz why not?) The sad thing is, it was the most capable team of devs I've ever worked with; they were just ridiculously overworked and management insisted that new features were always more important than testing.
I joined as a front end lead and, after kicking and screaming each retrospective about testing, finally stepped on toes and created my own team to create our own testing framework. Within a month we were at 90% test coverage.
I got fired and replaced with unpaid interns, but I'll take that any day over killing astronauts or answering to a Congressional investigation over it.
Omg that's wild. I just can't understand the logic of that! How do they sleep at night, really?? Is it a total lack of empathy, inability to think of others, or what.
When it comes to government prime contractors, you'd have about the same level of effectiveness by just setting piles of cash on fire.
How many bugs would you said you guys were able to catch with the introduction of testing with a project like that, which was previously completely untested?
OMFG so many. I knew I was on borrowed time for calling out management, but even some of the other teams were probably gunning for me when they started getting test failures and test coverage alarms on commit (which is stupid, because they had both the authoring app and the test runner on their local). Like, hearing dozens of grumbles of "God damn it" from nearby cubicles each day, for the first week especially. The devs I commandeered to work on it would IM our group "DRINK!" (we made it into a mock drinking game) every time it happened.
I really wish I had the foresight to open source it before giving it to them. I'm sure it was quickly abandoned after I left.
I'll definitely be asking about testing next time I'm job hunting. Once you've lived with automated testing, you don't want to go without!
Great post! Interviews are just as much about asking them questions to see if they are a good fit for you. Also- love the 🤟🏼! I have several family members that are HOH & deaf. :)
These are all good questions to ask at some point during the interview process, but be careful with asking too many questions prior to the first interview. You want to show interest, but don't want to sound like you're questioning the company's practices. Give them a chance to introduce you to what they do, and slowly reveal the truth over several interviews.
But that's the thing. I am questioning the company's practices. I don't want to find out three interviews in that I don't want to work for a company because their practices don't align with my needs. That's a waste of my time and also a waste of theirs. These questions show interest in the things that matter in the long term and if a company is offended by them, that's on them, not me.
I'm sorry, I don't understand why this would be necessary. Do you have an example you can provide me with to understand? I don't see how this approach could be negative.
Asking questions that point out failings of a company (and they all have failings) can be seen as criticism. Criticism from the outside is often viewed negatively, as you don't have the background to understand why the company does things the way they do. To many people this give the impression of arrogance.
It sets the perception of your expectations high early in the process. This may scare of recruiters.
I'm not saying any of these are not relevant questions, but the manner in which they are asked is important.And unfortunately, human nature and defense of one's own failings can cause a negative impression.
Interesting. Thanks for clarifying!
My expectations are very high and there's no problem with that. I don't want to work for a company that can't handle high expectations for a supportive environment. So, if they drop interest after these questions because I asked them "too early", good for us both then. Neither of us would be happy down the line.
That’s absolutely right. I’m not sure if you are sending them via mail? If the company has multiple interviews, I would ask them in a first phone interview or so because then I could also ask again to clarify things.
I did a lot of interviews as an interviewer and I always liked it to get such questions because it shows that the candidate knows what’s important. So if you’re not getting further interviewed because of those questions, it was probably not the right company to work for.
It does matter how you ask a question, for sure. For example, I'd really rather not work for a company with no automated testing ever again. Instead of asking, "You people do automated testing?" you can ask, "Can you tell me about your process to ensure a quality product?" People like talking about how clever their processes are, and if they have a good one, they'll probably be happy to answer, and you'll get useful insights. If the answer is "We're a bunch of geniuses who never make mistakes," I can run screaming.
I also ask
1). I assume Developers are a valuable resource for your organization. How do you show them they are valued? (Do they provide acceptable hardware, or is it from 5 years ago? Do they pay for training or is the 3 month pluralsight that comes with your MSDN it?)
2). When I start a job I want to bring value to the company as quickly as possible. What is your onboarding process like? (Basically will you be paying me to install ssms, or visual Studio? Any decent company should have you hit the ground running)