Skip to main content

Hire Fast, Fire Fast? Not so Fast.

Silicon Valley is full of advice and it frequently comes from people who have little experience on the subject matter.  A popular topic surrounds hiring and terminations with the king catch phrase being: “Hire Fast, Fire Fast.”  To me, what that usually means is lack of diligence, thought, communication and courage.

When hiring people love going with their gut feel, often with disastrous results.  There is an obvious subject of diversity of thought, appearance and background.  When thinking “fast” you are probably hiring people like yourself because humans quickly react to people who they believe are in their tribe.

A startup that lacks the resources of a big company often becomes so desperate to get technical staff that when a decent candidate comes along, excitement ensues and the employer doesn't slow down to put them through a more rigorous hiring process.

I highly encourage technical founders and engineering executives to write out their precise hiring process.  Of course, you can skip parts of it when appropriate, but you should skip parts of it consciously.  Here are some things to ponder:
Do you give people a coding exercise?
Do you review their public code?
Do you check references?
My hiring process document is 5 pages - I’ve been refining it for a long time and it’s continuously evolving.

In my opinion the bar is even higher for terminations. It should never come as a surprise to an individual getting terminated. The “performance improvement process” has a bad rap because it’s used by big company management to avoid making tough decisions. Still it benefits you to have a formal process outlined and follow it.

Obvious cases for firing fast include; crime, harassment and offensive behavior. Other issues like speed of work, hitting quota, not delivering the right kind of solutions definitely deserves several conversations prior to actually terminating the employee.  Chances are, if you hired a smart person who has been learning and achieving things in the past you can probably get them to improve their performance with appropriate feedback.

To start up executives, I recommend getting very comfortable with the following phrase: “we need X, you are producing Y, we need this corrected in Z time or we’ll need to start looking for someone else to do this job”.  Being able to have an honest, direct conversation is what separates the tough but fair leaders from those who avoid the subject all together and suddenly decide to “fire fast”.

Lastly, one of the best pieces of advice I can give is to outline your process and calibrate it with your Board of Directors, people you respect in the industry and your team.  It will help you balance Thinking Fast and Slow.

Here are some articles that were a source of material and inspiration:
https://www.entrepreneur.com/article/233022
https://techcrunch.com/2011/05/26/startup-mantra-hire-fast-fire-fast/ 
https://www.fastcompany.com/3005967/why-hire-slow-fire-fast-bunch-bs 
https://hbr.org/2014/03/hire-slow-fire-fast 
https://www.linkedin.com/pulse/20140915174239-5946358-why-hire-slow-fire-fast-may-not-be-the-best-advice/ 
https://www.thehartford.com/business-playbook/employee-termination 

If you like this article you might also consider my writing on Highly Effective Software Teams and Win Forever review
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!

Pull Requests and Code Reviews

Software development involves a great deal of collaboration.  One of the most basic blocks of collaboration on a software development team is a code review.  There have been many different ways of doing code reviews over time, some of this has been dictated by the tools available.  Git and online source collaboration tools created a set of best practices that are worthwhile of adopting on any team.

About a month ago I have looked at various articles about how to best create a Pull Request (PR) and do a code review and the attached presentation is the result of this research.  The presentation can help you guide your team and develop a set of collaboration practices that works for your particular situation.

It’s good to start out with why to seek a code review.  Having clarity about your intentions helps you guide the person helping you with code reviews and also to manage your expectations about you can get out of the code review.  The reasons for seeking a code review are generally …

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…