Skip to main content

Two Critical Questions for Your Next Interview

I’ve interviewed probably over 500 engineering and management candidates over the last several years.  There have been a lot of really smart people who have applied at DocuSign, Microsoft and Tempo Automation. A surprising number of them didn’t have a clear answer to these two essential questions:

  1. Why are you interested in joining our team?
  2. Why should we be interested in you? 

If you are an applicant, having a prepared answer for these questions is critical.  If you are a hiring manager, you should ask them and have a clear answer to these questions at the end of the first interaction with your future team mate.

In a field where work is somewhat predictable and static, those questions are less critical, but in software development perseverance, ingenuity and focus make all the difference. These are the two main questions that will separate a subpar and a superb hire.

When I discuss those two questions with an applicant I try to go below the surface.  Generic answers like “it says you are looking for a Python programmer and I know Python” are not good enough.  That type of an answer shows the lack of research and behind that could be a lack of interest.  Don’t bring in disinterested people onto your engineering team.  Low energy is contagious and firing is worse than never hiring someone in the first place.

For applicants: don’t take a job that you are not absolutely interested in.  Software is hard work, often involving a lot of hours.  Do you really want to be doing something you are not a good fit for?  One of the ways you can figure out whether you will be interested in the field is to pay attention to what it is that you are doing in your free time.  Before taking on my current job where we are using software to automate hardware manufacturing I started playing around with Raspberry Pi and looking into connected devices.  The software engineers that succeed on my current team have been playing with machine automation, robotics, hardware design.

If you are applying for a job where you can’t answer those questions, then maybe it is not the job for you.  Before getting too far into the process review the company website, the mission, press releases and blog posts.  Second, study the job description and ask clarifying questions over e-mail.  No matter what - do not sign up for a technical or an onsite interview until you gain clarity.  It could be a giant waste of time for everyone involved.  Be aware of companies that don’t ask those questions, organizations that think they can take any engineer, pay a decent salary and get requirement docs translated into code aren’t looking for ideas and innovation.

The good news is that if you do get these answers the job is likely to be fun and rewarding.  There is a good chance the team will be comprised of people who driven, energetic and have an interest in this field.  How fun would it be to get paid for the things you were exploring on your own, and to be surrounded with folks who have innovative ideas?


Popular posts from this blog

Quality of Code is Quality of Life

About 20 years ago when I started working in technology companies I remember “the best” engineers had similar patterns:
-They worked crazy hours
-They knew the systems no one else knew
-They could react and deliver something faster than anyone else
You could always hear other employees say: “Bob is really smart, no one knows how to get anything done in system X besides him!”

This reinforced optimization around being the only person who knew how to do something in some part of the code.  That in turn reinforced job security and bargaining for those engineers, but also chained them to a particular system.  We had big code bases of C++ or Java code where some “Bob” hacked up features as soon as he possibly could.  “Bob” would have occasional nuclear disasters where he’d sleep in the office or through the weekend and then everyone would thank him for how he “saved the day.”  “Bob” sacrificed his quality of life to get praise when he hacked stuff up quickly and then the second time when n…

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!

Why you should take the software job in San Francisco (or not).

Silicon Valley is an iconic place for technology.  Many people say this is the place for the “best and the brightest.”. Apple, Google, Facebook, Salesforce, Twitter and other top companies draw a lot of talent form all over the world and the largest chunk of VC capital goes to companies in the Bay Area, so it seems like moving here is a no brainer!

The real situation is actually not that simple, I believe there are three scenarios where it makes sense, but in many cases living in the Bay yields disappointing results.  The cost of living, housing situation, homeless catastrophe make places like San Francisco a lot less appealing to a lot of people.  So in what situations does it make sense to move to SF?

Startup founder raising millions There are many places to be a startup founder, but if you are looking to raise capital the largest pool of VC money is in the Bay Area.  There is an established network, events and conferences which give founders an opportunity to pitch more people th…