Skip to main content

What to ask during your interview

Most of the literature about interviews is focused on how to give good answers and get an offer letter.
I talk to a lot of candidates that forget that interviewing is a bi-directional process.  In the world of technology companies and startups specifically the candidates are interviewing the company just as much as the company is interviewing them.  Over the years I have collected some questions that I believe could help someone understand if the opportunity is right for them.  Here are some areas that I believe every candidate should touch through the interview process:

Business
  1. Who are the customers?  What happens if they don’t have your product?
  2. What are the revenues right now and what are the means of ramping them up?
  3. What is the financing now and how much runway do you have left?
  4. When delivering your product/service - how much of the process is digital and how much of the process involves people or hard assets?  Are those non-digital parts of your service on your books/payroll?
  5. What is the current team/department budget?  What is included in the budget?
Position Fit
  1. What is the difference between an OK person in this role and a super star?
  2. What in my experience stood out as something that will help you "move the needle?"
  3. What is the technical stack?  What are the biggest legacy code problems?
  4. (For leadership roles) Can you tell me about my direct reports?  What is their career plan and their passion?
  5. Who are the people who failed at this?  Why did they fail? What happened when they did?
  6. What is the expectation for the next 30-90-180 days?
Culture
  1. What do you love about working here?  What keeps you here?  What things annoy you?
  2. How do you evaluate performance?
  3. What are the metrics that the company is tracking?
I am certain that I "stole" these questions from people and articles.  I wish I remembered the sources to give them credit now.  If you have some other questions you believe would be helpful - please comment or send them my way.

Comments

Post a Comment

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team. I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me! SDE/T or QA Engineer interview checklist from Mike Borozdin If you like this checklist you might want to check out these posts: Emotional Intelligence in Software Teams   and  Good-bye manual tester, hello crowdsourcing!
Post a Comment
Read more

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers. Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily acce
Post a Comment
Read more

Intuitive Programming - Comments

Comments are a topic of vibrant discussion.  Ever since programmers could leave some text in the program that was ignored by the machine the debate started: “what’s a good comment, what’s a bad comment, why comment?” There are endless instructions to programmers that say many of the following things: 1) Describe your function! 2) Don’t write in the comment what you wrote in the code. 3) Tell people why you are doing what you are doing. What I think has been missing from this discourse is the audience for comments and through those audiences there is intent.  The code is being read, skimmed or analyzed by people and tools.  So what are the audiences and reading modes? 1) Maintaining and enhancing the code 2) Skimming through the entire module or file to figure out what the overall structure is 3) Reviewing the test files to check out the test coverage and edge cases 4) Seeing the docstrings of functions while being in a separate file altogether 5) Reviewi
Post a Comment
Read more