Posted by: Jeff Timmins | October 8, 2013

More Release Manager interview questions

More Release Management interview questions

Because of the popularity of my previous post on this subject and because I’ve had some practice lately I’m sharing a few more questions that could be used during an interview for a Release Management position. Also note that asking questions is important in an interview because by doing so you will come across interested in the role!RaisingHandForQuestions

Before I start I want to share some general principles that are important to remember related to asking questions during an interview:

  • Always listen for the answer so you can formulate a follow-up question if appropriate.
  • Only ask the questions that really matter – sometimes you want to look smart by asking a certain question but the answer doesn’t really matter and only wastes time.
  • When preparing questions, think about harvesting information for the next round of interviews – it is important to think ahead and ask questions that will help your research effort for the next set of interviews.
  • It is very possible that after you are done asking a question you will be requested to answer the same question so make sure to only ask a question you can answer yourself.
  • Ask a leading question in order to be strategic – if want to share with the interviewer how great you are at XYZ AND you know from your research that they have a problem with XYZ, ask them a question about it and then say “Oh that is interesting, I solved that problem by …”
  • When in the last round of interviews, and if possible, ask all the questions you need answered in order to accept or decline a job offer. This doesn’t apply HR type of questions related to time-off or insurance.
  • Know as much as the person/people that will be interviewing you as possible and use that information to connect with them as appropriate.
  • Know as much about the company you are interviewing with as possible.

Here are the additional questions:

  1. Are there any particular problems or “pain points” in the organization that you are trying to solve or resolve with the Release Management process at your company?
    This is one of my favorites because everyone has problems they need to solve and this will allow you to share an example of how you have solved problems in the past.
  2. Would you consider your Release Management process something that is evolving or something that is fairly mature?
    I like this question because it helps me understand if they need help creating an RM process or are simply looking for someone to follow the process that has already been created. Some are happy creating process and others are happy following. 
  3. How do you track your Releases at your company (i.e. which customers have which version or which version is deployed to the Hosted Servers)?
    This is a good example of a question that you can use strategically if you happen to know a good way to track Release information.
  4. Is your company working on any other type of applications in the future?
    If interviewing at Google or Microsoft you can skip this question but if interviewing with a smaller company it is good to know if the need for Releases will expand. 
  5. Is this a new position or a replacement position and what does the Org structure look like for this role?
    Personally I like to know if the company is growing or if they had a problem with the previous employee (why he/she failed could be a good follow-up so you can say “I’d never do that!”) + I like to know how far away I am from the C-level roles. 
Image credit from Bloomberg Businessweek

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s


%d bloggers like this: