«    »

100 Interview Questions to Ask Employers

The interview process should ideally be an equal, two-way conversation between the interviewers for an employer and a potential employee. However, speaking as someone who has sat on both sides of the table, it has always seemed to me to be imbalanced towards the interviewers. They control the process and ask far more questions than the interviewee. But it is just as important that the interviewee make sure the employer will be a good fit as it is that the interviewers ensure that the interviewee will be a good fit. It does neither side any good to have an unmotivated, unhappy employee looking for the first opportunity to leave, no matter how skilled they may be.

This point was brought to my attention again a few weeks ago when I read the article 100 Interview Questions for Software Developers by Jurgen. I liked the article and have used some of the questions, but it got me thinking that software developers and other I.T. professionals deserve to have the same resource – interview questions to ask of employers. So below I list 100 questions you should look for answers to during the interview process. Some of the questions are specifically for software developers, but many are more broadly applicable to any professional knowledge-worker position.

Warning: Do not simply ask the interviewers these 100 questions in the first interview! Your first priority in an interview process is to convince the interviewers to hire you by selling yourself. The important but secondary priority is to determine that the company is a good fit. It does not matter how good a fit the company is if they will not hire you. (This reminds me of all the blog posts from people who interviewed for Google but did not get in.) So wait until the company is at least seriously interested, and better yet has extended an offer, before doing your due diligence and asking these questions. I would not recommend asking all of these questions directly of the interviewers, especially those from the human resources department, as they likely do not know what the specific working conditions are like and may sugar-coat the facts. I recommend instead talking directly to a few regular employees, preferably in a neutral setting outside of the office.

Without further ado here are the questions organized into categories.


  1. What drives the organization? What do senior executives value? What is important to them?
  2. What are the core values that make up the organization's culture? Has this been consistently supported by senior executives?
  3. Is the organization financially strong and stable? Please provide your annual financial reports for the last three years. (This is available on-line for publicly-traded companies.)
  4. What are the significant strengths, weaknesses, opportunities, and threats facing the organization over the next few years? What are the organization's strategic goals?
  5. How does the department / team I will be joining relate to the overall organization? How does it support the organization's strategic goals? Is the department a cost or profit center? How is the department perceived politically?
  6. Management

  7. How often will my immediate supervisor meet with me one on one?
  8. What is the management style of my immediate supervisor and their superior?
  9. How do you deal with poorly performing employees?
  10. What is your strategy for empowering employees?
  11. How do you ensure you are delegating effectively rather than micro-managing?
  12. How do you help ensure that employees are highly motivated?
  13. How do you ensure that each employee is doing quality work?
  14. How does management ensure that employees feel listened to?
  15. How do you enhance the creativity of developers?
  16. How approachable and receptive is management to suggestions and feedback?
  17. How do you minimize interruptions for developers?
  18. Do you treat people with respect and integrity? Provide an example.
  19. How important is productivity of software developers to the organization? What do you do to maximize productivity?
  20. Do you put as much if not more effort into retaining employees as you do recruiting? What is your retention strategy?
  21. How do you promote a healthy work-life balance?
  22. What metrics do you track and report on? Provide a report showing data from the last few months.
  23. Teams

  24. How are teams assembled? How are team members selected? What are the selection criteria?
  25. How often will the team I am in meet as a group?
  26. What do you expect will be my role on the team?
  27. What are the experience levels (i.e. junior, intermediate, senior) and job roles of the other team members?
  28. What is involved in moving to another team or changing work assignments?
  29. Do teams have a sufficient diversity of skill beyond simply coding? What about ability in gathering requirements, architecture, usability design and testing, database design and administration, functional testing, and technical writing?
  30. What types of team-building activities are done? How frequently?
  31. Are teams empowered and self-organizing? Are teams able to choose and tailor a methodology to suit them and their work?
  32. How much freedom and support is provided to mentor and consult with colleagues, superiors, and customers?
  33. Describe the clients, customers and end users I will be working with or for. How reasonable and pleasant are they?
  34. Work Assignments

  35. What kind of work assignments will I be given? What will be my day-to-day responsibilities?
  36. What opportunities will there be to work with new, interesting technologies?
  37. How do you plan to provide me with challenging work that makes optimal use of my abilities while providing a supportive environment?
  38. Are developers required to do administrative or non-value-add tasks that could be done more cost effectively by others?
  39. Work Environment

  40. Will I be situated in an office with a door?
  41. Is the work environment quiet with no distracting noises like intercoms, call center staff, ventilation systems, or traffic?
  42. Are living, green plants in abundance in the office?
  43. Are high quality chairs provided?
  44. Is the office setting (chair, desk, keyboard, and monitor) ergonomically friendly? Can I adjust the height of everything to fit my needs?
  45. Do you supply at least two large monitors as a standard configuration for software developers?
  46. Are software developers provided with high-powered workstations? How often are they upgraded?
  47. Does the office setting support collaboration with coworkers? This includes at least one extra chair, the ability for two people to sit in front of the computer (i.e. pair programming), and a white board fixed onto a stable surface with room for at least three people to stand in front of it.
  48. Will I be provided with an ergonomic keyboard and mouse to my specifications? Or can I purchase my own and expense it with no questions asked?
  49. Will I have the freedom to install the tools I want on my workstation?
  50. What is the process and lead time to get a new tool, workstation, or server purchased and installed? How much bureaucracy and delay is involved?
  51. Project Management

  52. Do projects have realistic schedules, resources, and scope that are actively managed and adjusted? How much freedom and control does the project manager / team have to change these three factors?
  53. How do you deal with a project that is behind schedule?
  54. How do you manage requests to change the scope or requirements of a project?
  55. What tools and practices are used to manage project schedules?
  56. Who estimates the time or effort required to do development work?
  57. How is the expenditure of effort tracked? What tools are used for time entry and tracking progress?
  58. What is the duration of iterations and releases?
  59. Development Practices

  60. What development methodologies do you use? Describe how they are put into practice.
  61. How closely does development activities align with the philosophy & principles of Agile and Lean?
  62. What languages, libraries, and frameworks are commonly used or mandated?
  63. What developer tools (especially IDE) are provided or mandated?
  64. What do you do for:

  65. Version Control?
  66. Unit Testing?
  67. Code Reviews?
  68. System & Integration Testing?
  69. Client / Customer / End User Collaboration?
  70. Requirements / Design Specifications?
  71. Design Reviews?
  72. Defect Tracking?
  73. Build Automation?
  74. Continuous Integration?
  75. Usability Testing?
  76. Continuous Improvement

  77. What continuous improvement activities are performed on a regular basis?
  78. How often are retrospectives / lessons learned meetings held?
  79. How aggressively do you minimize bureaucracy and non-value-add activities? Can you provide an example of improving in this regard in the last six months?
  80. What is your process for handling suggestions and ideas from employees? How many suggestions per employee on average were received in the last year? How many were acted on?
  81. Professional Development

  82. Do you provide opportunities for developers to receive feedback and learn from having their software running in production?
  83. What opportunities will I get to work with or mentor under expert world class software developers, architects, and managers?
  84. How much paid training do you provide to each employee per year? What kind of training is it? Can employees choose or recommend the training they take?
  85. Performance Evaluation

  86. What kinds of opportunities for growth and advancement are possible? Describe the options for technical career paths that do not involve management.
  87. How do you make decisions regarding promotions?
  88. What approach is used for providing timely, effective feedback on performance? How are performance evaluations carried out?
  89. What do you look for in an ideal employee?
  90. Working Hours

  91. What are the official number of hours worked per week?
  92. How many hours per week on average have your software developers worked over the last three months?
  93. Do you allow or expect mandatory overtime? What do you consider an unacceptable amount of overtime (both mandatory and voluntary)?
  94. Do you provide flexible working hours? What limits are there?
  95. Compensation and Benefits

  96. Do you provide a competitive salary? What is your definition of competitive?
  97. How do you ensure that the salary of long-term employees stays competitive, especially in a hot job market? Do you respect your long-term employees enough to raise their salaries in such situations without waiting for them to ask for raises?
  98. How do you compensate for overtime?
  99. Do you pay your software developers according to their level of productivity? Why or why not?
  100. How many weeks per year of vacation do you offer?
  101. How flexible are you concerning how banked vacation can be used? Can it be saved from year to year? Are there any restrictions on taking vacation?
  102. What is your policy concerning raises? How regularly do you give raises? Do you consider a yearly increase in salary equal to the local inflation rate to be a raise?
  103. How do you reward exceptional performance? What do you consider exceptional performance and how do you identify it?
  104. Do you provide share options, profit sharing, retirement savings contributions, or pension? If so, what are the details of the plan(s)?
  105. What medical benefits do you provide? Do you cover dental work or eyeglasses? Do you cover health preventative measures such as exercise programs, vitamins, or preventative medical exams?
  106. What is your policy regarding sick days?
  107. Do you allow and support people in working from home? Up to what percentage of the time?
  108. Will travel be expected? If so, how frequently, for how long, to where? What is the policy on travel expenses?
  109. What other benefits or perks do you provide?
  110. Contribution to Community

  111. How do you participate in and contribute to the local and global I.T. / software development community?
  112. What open source software do you support? What form does this support take?
  113. Wrap-up Questions

  114. Who are you competing with locally for recruiting software developers? Who are you losing developers to?
  115. Bonus Question: Please provide three references consisting of employees I can talk to. The references should include a senior software developer and a technical lead.

The vast majority of Internet resources for job interviews focus on questions to ask employees, but I did find a few relevant articles that were helpful in producing this list of questions:

If you find this article helpful, please make a donation.

18 Comments on “100 Interview Questions to Ask Employers”

  1. John Nolan says:

    Q: Will I be situated in an office with a door?
    A: No Rapunzel you won’t.

  2. It might be rare, but there are companies that provide offices. I actually interviewed once at a startup that provided offices for all developers, and a number of well-known software companies do so (e.g. Microsoft, Fog Creek).

  3. Ollie Jones says:

    Very interesting writeup.

    I’d be careful with these questions if I were you, though. Some of them may come across sounding like rock star green room demands — “Two cases of Harpoon IPA beer at exactly 40 degrees, a dish of m&ms with no blue ones in it.” That kind of stuff will work fine if your name is Bruce Springsteen, but may work against you otherwise.

    The most interesting places to work are those that are open to new ideas about productivity and their business. So, “would you mind if I brought in a second monitor to use?” is a good followup to “do you provide two monitors?”

  4. @Ollie, I agree completely about being careful to not come across as too demanding. That’s why I included the warning in the article to not just blindly ask these questions in the first interview, but to use them more as a guide to research the company in depth. I really liked your point about companies being open to new ideas. I’d like to think I covered this under the Continuous Improvement section, but you seemed to capture the essence much more directly.

  5. Zen Render says:

    A big part of the interview is usually determining your “fit” for the company, and since these are not the sorts of things employees would normally ask, you’ll seem “odd” or “overly demanding” with many of these questions.

    As someone who works in IT, I’ve heard/seen a lot of horror-stories who arrive on day one and start complaining about needly things like that their LCD monitors are “Not the Ones They Specified During the Interview.” A lot of these are good questions for the interviewEE to find out about a company, but would be seen as overly demanding to ask the interviewer.

    If I was going to be CIO or HR director for a company, I might start asking for some of these more detailed questions, but any system engineer who asks to see the last three years of financials during the interview is showing that they haven’t done their own research at all before the interview.

    Oh, and #101? I think you mean “existing” employees.

    I’d use this list as “things to wonder about the company” BEFORE the interview, and then determine what I can/can’t figure out for myself. Overtime maximums (check your local legal limits, too) and those sorts of things are totally normal to ask, and you SHOULD ask before starting at a company, for sure.

  6. Zen Render says:

    Of course, I’m not trying to say that MOST of the list are too demanding. It is a good list, and a number of these questions are the sorts of things I know I’ve left an interview thinking “Oh, I should have asked about how overtime works,” and things like that.

  7. Eric Brown says:

    We provide offices for almost all of our staff. Every IT staff has his or her own office. Other departments have their own offices as well, with no more than 2 people in some of the larger offices. Managers are mixed right in with their staff in the same office area. It works fantastically.

  8. Son Nguyen says:

    I understand these questions are guidelines to understand an organization and it’s good to choose and ask some selected ones that are of your interest. But if some naive potential interviewee asks this many questions, I’ll show them the door sooner than they would like.

  9. Adrian Hankey says:

    Don’t expect honest answers to these questions. You will be told whatever they feel they need to tell you to get you to sign. Once you’re in the door it will all change and those wonderful ideals, projects and processes will evaporate. I’ve been through it many times before I got wise.

    You can’t determine if a company is any good by asking them directly, this requires more subtle investigation and observation. Also, if the software they build is not directly related to building revenue as opposed to lowering expenses, they will suck. This isn’t because they don’t want to suck, but the economics of the situation will forbid good development.

  10. @Adrian, I do have enough cynicism to know where you are coming from and I have certainly heard / read about situations where this has happened. But if you know (or even strongly suspect) that a company is going to lie to you in the interview, why would you even bother applying at that company? I for one would not want to work at such a place. This of course assumes you can be selective about where you work, but if you have no choice then these questions above won’t really be relevant.

  11. Peter K says:

    As others has indicated, good list of questions and as usual, interviewEEs should choose which of these questions are important to them and NOT blindly ask them just to have something to ask.

    Depending on the employing organization, there is usually a lot of information available for candidates to research and understand the organization. Annual Financial reports are usually available.

    A few questions that I would always ask are “Why was this position vacant? Why can’t it be filled by promoting internal personnel?” and “What are some of the challenges that the manager/supervisor that the position will be reporting to currently see for the position?”. The answers will usually give you an idea of the work environment and team that the position will be involved in.

  12. Shabana says:

    Hi Vandegriend, it is fantastic list of questions you have put up in your http://www.basilv.com/psd/blog/2009/100-interview-questions-to-ask-employers

    There are some questions, I never had courage to ask the questions you have listed though some of them had ever been on my mind………………. Also, Noop’s list of question is quite good and really a breathe of fresh air when interviewer keep on asking definition and oops approach.. And yes a wonderful and insight question asked by Why was this position vacant? by Peter K, though I won’t expect a honest answer but it is worthy question and will tell a lot even if they don’t give honest answer.

  13. hi basil! thanks for your post, it was a lovely read and some really great questions to ask the employer! anyway if you have a moment please also check this list i compiled of the 50 most commonly asked interview questions ASKED by employer!, why they are asked, any hidden motives and exactly how to answer the questions!
    50 most common interview questions and answers

  14. Most people prepare questions to ask. My advice, don’t do it. It sounds so weird then people ask questions they think they have to ask. Instead, ask questions you really care about, even if they are not going to be popular with interviewer such as “Why are you hiring from out side of the company ? Don’t you have senior team members you might want to promote?”
    Also spread the questions through out the cource of the interview it would keep you engaged and keep dialog going rather than a monolog.

    Feel free to follow my advices on Twitter:http://twitter.com/CommonInterview

  15. [...] Now to finish reading this on how to get that job at google (or anywhere else cool) and ask these 100 interview questions to ask employers. Kingdom, Phylum, Class, Order, Family, Genus, [...]

  16. Val says:

    Nguyen, I understand that it’s a huge list of questions and is difficult to answer, but would you have any other reasons for ‘showing the door’ to the interviewee if they asked them? I mean, wanting to know the answers to most of these makes perfect sense to me. Are you utterly unwilling to discuss these things with potential employees? Maybe you don’t feel the interview is the right place to ask these? Would you be willing to get back to a potential employee with the answers to these, say, via email? I mean, I hope your position isn’t “I’m too cool to answer these questions, even if they are valid and the interviewee has a right to know the answers”.

  17. Jared says:

    I am young, out of college and i have done tons and tons of research, through articles and talking to people. etc.. some of these 100 questions should be on the “what not to ask list” – BE CAREFUL!

«    »