Skip to main content

Deals You Can't Miss

1 Year Subscription

My thoughts on hiring and retention

A question to motivate : 

Which of the below candidate do you prefer? 

  1. A candidate who stayed in a company for good deal of years but has left it leaving a gaping hole in the knowledge. 
  2. A candidate who made it a point to share his/her knowledge by way of brilliant documentation making him/her irrelevant to the company before leaving.
If your choice is option 1, then I would love to learn your though process around that decision of yours and what is your take on mine that I have put forth in this blog post. If your choice is option 2, I am go glad about your choice and would ask what did you do to ensure that your company as well embraces it in its hiring process.

How I approach the hiring side of things?
One of the key things I do working with the Talent Acquisition team is to set the basic value system is set right and that we are all aligned to it, so that we can spot the right candidates that others miss. Having said that, I admit this is not an easy thing to do. One thing that worked for me is to have frequent conversations with stakeholders concerned around the following questions (I often trigger the conversation asking one/some of them):
  • Do you look for an individual's stickiness (duration of his stay) to a company in his career?
  • What is your metric of measuring stability?
  • How do you measure productivity and professionalism of an individual against his/her stickiness to a company?
  • How do you measure experience -- number is experience or experience in number?
  • What specific positive/negative traits do you look for in a candidate? 
During my conversation (aka interview) with the potential hires, I ensure that not only are the candidates treated as people (instead of resources) but are well respected as a courtesy. This sets the stage for me understand the candidate better and that the candidate as well gets a fair insight in the job, the workplace, the company and me as a person. Two things I really care for in any candidate, irrespective of their experience or role are their teaching-ability and learning-ability. I do my homework to ensure I get a decent hunch on these attributes during my time with the candidate.

How I approach the retention side of things?

Retention is yet another hard-ball game. I would bet any day in making the workplace atmosphere more transparent, safe, productive, and guaranteed learnings from solving problems as a team. With this in mind, I start looking out for opportunities for improvement and go about executing them. This is multi-dimensional requiring help from many stakeholders in solving the problem and unfortunately this is often over-looked; take for instance if an outgoing employee cites any of the following reasons for leaving the company in your personal 1-to-1 conversation, what can you do about it:
  • pay-scale disparity (you can't drill down on this one in your conversation)
  • concerns of discriminations (you really got to win the trust of the person to hear this one out but often isn't something within your control)
  • lack of opportunities to pick up better work (you must tactfully drill down on this one to get a hang of ground-zero reality) when they see some of their peers get to work on niche areas
  • lack of learning opportunities (you got to drill down to the specifics) when they end up taking too much of support work or see some of their peers getting special privileges of say, certification reimbursements and they feel so left out.
  • work-life balance going for a toss because of recurrent production issues, time-crunched deadlines, unplanned works etc. hurting their weekends and holidays. 
Not all the above problems might be in your direct control to bring about change. Not all the above problems can be tackled directly or immediately. Some of the measures that I have taken to improve the workplace atmosphere are below:
  • Encourage the habits of documenting key knowledge in business, technology and practices. 
  • Encourage more and more work related conversations to happen. It is important that there are conflicting opinions for the teams to get better in what they do. Unfortunately, conflicting opinions are discouraged in most workplaces.
  • Encourage brownbag or lunch-hour sessions within teams, within horizontals and slowly stretching it to the outside world as talks in meetups and conferences.
  • Encourage pairing not just within roles but across roles.
  • Make it a point to reach out to individual team members to understand their aspirations and look for opportunities to accommodate and nurture it as part of their goals. 
  • Encourage team work by breaking silos.
  • Discourage gossip against person by encouraging open discussions on work subject.
Measure what matters. Loyalty trumps stability; for in my world, retention is not just about how long one stays in a company, but how safe and productive (s)he is at work. Measure an individual's contribution at work and in developing other team members. I look not for how long one stayed in a company but how one helped the company, and the team grow during their tenure. 

My Popular Posts

Ten Commandments of Egoless Programming

We are nothing but the values we carry. All through my life thus far, I tried to influence people around me with the virtues I value. Thanks to some good reading habits I had inculcated, and the fortune of being in good community of peers and mentors alike, I managed to have read some real good books. This post is about the 10 commands of egoless programming in Weinberg's book. I shall explain the commandments based on my experience here. So very many decades ago, Gerald M. Weinberg authored  The Psychology of Computer Programming . In it, he listed The Ten Commandments of  Egoless Programming , which remains relevant even today for us as not just programmers but as team-members. Weinberg is regarded as a pioneer in taking a people-centric approach to computing, and his work endures as a good guide to intelligence, skill, teamwork, and problem-solving power of a developer. When they appear to inspire and instruct, we find that they can apply to just about every business area, and e

Should I buy refurbished laptop from Amazon?

This post is based on my experience with and guess it to be true on all other platforms as well. At least you can check out and verify for these pointers before you make that decision to buy renewed/refurbished laptop on Amazon with your hard earned money. I see this question propping up in several forums and on many different occasions. In the recent past, I had my 5 year old dell laptop that gave up because its motherboard failed. One of the options that I had in my mind was to re-use the HDD and the 16GB DDR4 RAM of that old laptop in the one that I purchase next as secondary.  I had come to a conclusion that it is not worth buying a refurbished/renewed laptop at all. Why? For the following reasons, most of which I see as BIG #RedFlags: You got to remember that Amazon provides a platform for 3rd party sellers to sell their products as well. So in your search for refurbished laptops you wouldn’t want to choose some random 3rd party seller who Amazon doesn’t endorse. You cou

Multi-tenant Architectures

  Multi-tenancy Application Deployment Architecture could be modeled in 4 broad ways: Separate Apps & Separate Databases Shared Apps & Shared Databases Separate Apps & Shared Databases Shared Apps & Separate Databases There is no right or wrong here. It's about choice and consequence that you should consider taking into your business context and constraints. In this post I intend to jot down a some key points to keep in mind for each of these multi-tenant architecture. These are more of quick notes for my quick reference, a cheat-sheet of sorts when I have to make choices. And I guess this can come handy to you too in your wise decision making. Separate Apps & Separate Databases Easiest to implement from development and deployment stand-point. Just automate the deployment infrastructure for every tenant for quick set-up. Most expensive of all the models from infrastructure cost stand-point. Relatively longer deployment t