Developer Tea

9 Questions You Should Always Ask During An Interview

Episode Summary

Today I talk to you about questions you should always ask a potential employer. Today's episode is sponsored by Hired! If you are a developer or a designer looking for a job, Hired is a fantastic place to begin your journey! The special link for a doubled bonus is https://hired.com/developertea - be sure to use this link when you sign up.

Episode Notes

Today I talk to you about questions you should always ask a potential employer.


Today's episode is sponsored by Hired.com! If you are a developer or a designer looking for a job, Hired is a fantastic place to begin your journey! The special link for a doubled bonus is https://hired.com/developertea.


Mentioned on the show:

A quick note:

I'm aware that I didn't discuss money in this episode. This was partially intentional, as the subject is massive on its own. I will be discussing finances for developers in the future!

And lastly...

Please take a moment and subscribe and rate the show! Click here to open Developer Tea in iTunes.

Episode Transcription

Hey everyone and welcome to Developer Tea. My name is Jonathan Cottrell. Today I'm going to be talking about questions you should be asking the people you are interviewing with. And this is for the programmer who is interviewing for a job, not the person who is looking to hire someone. So the reality is a lot of the time we don't know what questions to ask our future employers. We go through the process of answering all the questions that they have for us. And then so many times the employer asks, well, do you have any questions? And really the only questions you have are, you know, what's for lunch or something like that. And I would recommend that you come a bit more prepared than that. There are a lot of questions you can ask to get an idea of what that company is looking for so that you can become more hireable. There are also questions you can ask that you may end up deciding that you don't want to work for that company. Working for a company for a year or two years of your life, that can be a significant investment. And there are so many things that you can do to kind of learn about that company in the beginning and avoid a lot of problems later. Today's episode, by the way, happens to be sponsored by Hired.com. If you are looking for a job, Hired.com is a great way to get started. We will talk more about the sponsor later on in the show. But I want to jumpstart. Straight in because I have nine questions here. By no means is this comprehensive. There are a ton of questions that you could be asking. In fact, Julia Evans actually wrote a great list of them back in 2013. And of course, that list will be in the show notes on spec.fm. But let's jump straight in to the ones that I have here. Some of these are kind of inspired by those. Some of them are inspired by the Reddit post. But I want to jump straight in. I'm going to go through a couple of these. Then we'll talk about our sponsors. And then I will finish out the rest of the questions. Number one. And these are in no particular order, by the way. I just decided to kind of write out my thoughts both as an employer and as an employee. So number one. What does a typical day, a typical work day, and a typical work week look like? Do people tend to work late or on the weekends? And this question is such a hot topic when you start talking about hiring because people are typically very protective. And so I'm going to start with number two. What is the most important thing that you value the most? And it's important to be protective of the time that they have outside of work. And it's important to be protective of the things that you value the most. And so this is a very important question to ask. Because if you get into a job and you don't know what that internal working culture is like, and you're blindsided by everybody feeling like they need to be at the office until dinner, then you may not enjoy that job. And it could be that you actually do enjoy that kind of environment. And suffice it. To say there is no right answer to this question. This is simply the information that you as a developer need. Because if there is a supposed right answer, then the company that's trying to hire you, they're going to know what you are trying to fish out of them, right? If you are only seeking information, if you frame these questions in order to retrieve information from your potential future employer, they're going to be much more likely, to be honest with you. And so if you talk about the typical work day and typical work week, what do your hours look like? Most people will be honest with you as long as you aren't saying, you know, if you frame the question like this, do you guys overwork your employees? Obviously, very few people think that they overwork their employees. But instead, if you frame it like this, what are your typical office hours? What time do people usually leave the office? Then you have a better chance of getting a job. You have a better idea of how that actually plays out. Some people think that working from 7 o'clock in the morning to 7 o'clock at night is not overworking. And in fact, there are a lot of industries where that is a very normal thing. It doesn't really matter whether or not we think it should be normal. There are a lot of industries where that has become normal. So don't ask questions that have obvious right or wrong answers. Very few employers think that they are doing things wrong when it comes to overworking their employees. So that's the first one. Ask what that typical work week or work day looks like. And number two, this one is kind of a longer trajectory of the working quality and how busy you would be. Do you have a particular part of the year where things get busier than normal? And this is very common for a lot of businesses to go through a three-week or even a six-week period where things are, much busier than normal. A lot of times around the holidays, just about every company ends up being busy towards the end of the year, towards the holidays, whether they're front-loading work because people are going to be off for the holidays or whatever. But you need to know that going in, right? You need to know when the busy parts of the year are. Because if you typically take your vacation during those busy parts, well, it's important for you to weigh that into your decision about whether or not, this company is right for you. And that's really the underlying discussion here is that when you go to interview for a company, certainly the company is the one who is providing the job and it's nobody's place to go in and make demands. But you are providing your time. You are providing your services and you are valuable. They want you to succeed. They want to hire someone to solve their problems. They don't want to keep on interviewing people over and over. So they, see value or potential value in everyone who walks in their door for an interview. You should be asking these questions so that you can make the determination if what they are offering for your life for the next couple of years, perhaps, is something that you actually want, is something that you want to take part in. So that is the reason why number one and two are so important. What does this job look like? What kind of demand will it place on my life? What months of the year will I be, busier than other months? And what parts of the week will I be busier than other parts of the week? These are very important things, kind of fundamental things to know about a job. And this definitely isn't just for developers for number one and two, that's pretty much any job you ever go to in life. So number three kind of moves away from this idea of how much strain does this put on me and moves towards the idea of the values and the enjoyment that the people at that particular job, that particular company get out of their jobs. So number three is what is your favorite part of the job? If you are speaking to the interviewer, ask them what their favorite part of their job actually is. Now, of course, depending on the size of the company, you could be talking to an HR person that's giving you your interview. And if you're going to be a developer for this particular company, their answer may not be relevant to you. If they say something about, you know, the HR field, but it does give you an insight into how the company works. If you're going to be a developer for this particular company, If you're going to be a developer for this particular company, If you're going to be a developer for this particular company, works and into what people enjoy doing at the company. If you're talking to a developer, it's even more insightful, right? Because if they say something like, we just shipped this incredible product together, that's very different than them saying, well, my favorite part of the job is that they provide unlimited vacation. These are two very different value sets that speak a lot to the culture of the company that you're applying to work at. Okay, I think that's a great spot to take a quick break and talk about Hired.com, today's sponsor for this episode. Now we're talking about hiring, we're talking about the interview process, but actually finding a company to interview at is perhaps one of the hardest parts of the hiring process. And Hired.com is fixing this problem. If you are a developer or a designer looking for a job, Hired.com provides a free service to you, 100% free. The folks at Hired have vetted over 2000 companies from all over the world. Just to find offers for you, you get offers upfront that include compensation. A lot of times they include equity. These can be part-time or full-time jobs. You get a bonus upfront too. Now Hired usually makes that bonus $2,000. If you use our special link in the show notes, you can double that bonus up to $4,000. Hired.com, check it out if you are looking for a job. It is a great place to start, a great place to look through offers. You actually get to see the offer before you ever even talk to the company. So go to the show notes, use the link, Hired.com. You can get a $4,000 bonus if you use that special link. Okay, so let's jump back into our questions that you should be asking in those interviews. We've gone through the first three and we have six more. The first three certainly take longer than the other six, because at this point you kind of have an idea of the amount of energy that you're going to be spending at the company. And it's likely that you have an idea of what the company does. And now that you've asked the person that is hiring you what their favorite part of the job is, you have an idea of what you can expect to be kind of the cultural excitement, the things that people get excited about on the job. Okay, number four, what are some things that you and your team have done recently that you are proud of? Now this question gives you two pieces of information. First of all, it gives you kind of an idea of what you're doing. And then you can kind of look at the job and see what you're doing. And then you can look at the job and see what you would be working on, what you and your team would be working on. But secondly, it gives you an idea of the kind of things that make people happy at the company that you're working at, specifically the kind of things that make people proud. Now this is kind of similar to number three, what is your favorite part of the job? But if number three was about, you know, the long term vacation, well, now you want to know a little bit more about the work you're going to be doing. So the things that they've done recently that they are proud of, is probably the stuff that you're going to be putting energy into as well. Number five, in the ideal case, what is the long term trajectory for this role? Will the responsibilities change? Is this a role that is designed for someone to stay in for a long time? You know, what does this role look like in the long term? And the reason you want to ask this question is so you can determine whether or not this role is going to be something you should be depending on for a long time. And also, if you want to be depending on this role for a long time, you should be depending on this role for a long time. And also, if you want to be depending on this role for a long time, you should be depending on this role for a long time. And also, if you want to grow into another role in the future, if the role that you are applying for is one that actually doesn't have any room for upward growth or mobility, then it may be something that you need to consider. Do I want to be in this role for a long term? There's a little bit of a caveat here. You should always take the answer to this question with a grain of salt because people change, companies change, the needs of the company will change, the market will change, everything changes. So you shouldn't take the answer to this question with a grain of salt because people change, companies change, the needs of the company will change, the market will change, everything changes. So you shouldn't take the answer to this question necessarily as the 100% truth forever and always. Instead, look at the answer of this question as the intention of this role. Is the intention for this role to be static or is the intention for somebody to go through this role? For example, a junior level developer position is intended to be something that is transitory, right? If you become a junior developer, you won't stay a junior developer for a very long period of time. The intention is for you to become, you know, whatever that next step is. If you want to call it an associate developer, for example, or maybe the company goes ahead and puts you all the way up to a senior level developer, the intention is not to keep you at that junior level forever. However, a senior level or even an associate level position, those may be roles that are intended to be fulfilled by the same person for as long as that person wants to stay in that role. Okay, let's jump on to number six because we really could talk about any one of these questions for the length of an entire episode, but I want to go ahead and get through them because, you know, this show is supposed to be short. All right, number six. Is remote work a part of your culture? And the reason this question is so important is because for many developers, this is a make or break question. Simply by nature of the type of work that we do, the actual coding that we do, our work is possibly portable. Our work allows us to do it from just about anywhere in the world. However, your company may not be in support of this idea. It may be that your company wants you in the office every single hour that you work. That's unusual. Most companies, most software development companies allow at least a little bit of remote work, especially increasingly into the future. This will be true, but you need to know that going in. Is remote work a part of their culture or not? Number seven. Who would I be working with and who would I be answering to? The truth is, if you don't enjoy the people that you are working around, it doesn't matter how cool the work is, you're eventually going to get burnt out because of who you are working with. If you end up meeting the person that is going to be in direct superiority to you and they seem overbearing or you don't like their personality, you should know this going in. Again, there is no right or wrong answer to this question. It could be that the company says, you know what? You don't really have a person that you answer to directly. You're going to be somewhat autonomous. Well, that's not a right or wrong answer. If you don't like autonomy, that could be something that you don't want. If you do like autonomy, that could be the perfect situation for you. So you just need to know these things going in so you know what to expect and you can weigh all of your options with as much information as you can possibly get. Okay. Number eight. What kind of professional development does your company engage in? Are you involved with a company that is not a company that is a local developer? Do you go to conferences? Do you allow people to speak at conferences? Do you do some kind of networking events? That kind of stuff. Every company engages in this particular piece of the pie differently. Some companies don't go to conferences at all. Some companies have a very strict limited budget and a strict amount of time that they want to put towards that kind of thing. Some companies think that conferences are the ultimate way to develop the company, to develop the presence in the industry. And there's a sliding scale between all of these situations. If you want to develop a speaking career, for example, then you probably shouldn't work at a company that never allows their employees to go to conferences. If you don't want to develop a speaking career, then you probably shouldn't work at a company that encourages and hopes for all of their employees to speak as a major part of their business. If you don't want to develop a speaking career, then you probably shouldn't work at a company that encourages and hopes for all of their employees to speak as a major part of their strategy. And finally, number nine, what can I do as an employee of your company to be the most valuable? What can I do to be the most valuable? This question is something that so few employees remember to ask. How can I be more valuable to this company? This is a question that needs to be answered every single day. If you are working for a company, what is the most value that you can provide to that company? And the way this works is you provide value to a company and they will provide value back to you. Now, of course, you shouldn't be providing more value than they provide to you on a regular basis without eventually being compensated for it. So, for example, if you're working 60 hours a week and you're getting paid an hourly wage for 40 hours a week, then there's a problem there. But if you are trying to provide as much value as possible, then you're going to be providing more value to that company. So, if you are trying to provide as much value as possible to the company that you are working for, the intention will be to compensate you back for the value that you provide. But the way that you provide value to the company may be different than you think it is. In other words, the people who see you as valuable, if you ask them how to be more valuable, you may have a surprising answer. The answer may be, well, we need you to be in meetings. Or the answer could be, well, we need you to be on time to everything. These could be very simple ways to increase the amount of value that you're providing to a company without much effort at all. And answering this question before you even come to a company gives you even more of an idea of how you can be most successful at that company. And if the picture of success at that company doesn't match up with what you want in a job, if it doesn't match up with what you want to do, then maybe that's a something to consider. Maybe that job isn't right for you. But if you are getting this valuable information directly from the people who are in charge of hiring you before you're even at the company, then you come in as a valuable member of the team. You immediately know exactly the path to follow to be the most valuable possible. And that ultimately is a fulfilling job when you can provide value to a company and they compensate you for that value. That is such a fulfilling and satisfying moment to realize that you are actually providing value. You're creating value for the company that is hiring you. I hope you've enjoyed these questions. I hope they provoke some thought and discussion. If you are a manager that hires people, I hope that this has provoked some thought in you as well about what types of things people need to know when they come to your company. What kinds of things should you be telling them? And encouraging them to learn about at your company when you're hiring. If you are looking for a job, if you are the person that's in the interview being interviewed, I hope this gives you some idea of your responsibility in the interview. It's important that you think about these things, that you learn about them in advance before you take an offer from a company. Thank you so much for listening to Developer Tea. Thank you again to Hired.com, our sponsor for today's episode. If you are looking for a job that you want to learn about, please contact us at Hired.com. Check out Hired.com. They can provide you up to five or more job offers in a given week. Designers and developers, check out Hired.com. Use our special link so that you can get that doubled signing bonus. Instead of $2,000, you would get a $4,000 bonus from Hired if you get hired through Hired. Thank you to Hired.com. Thank you so much for listening to the episode. Of course, all the show notes and all the links from today's episode, can be found at spec.fm. Until next time, enjoy your tea.