How Do Set Clear Hiring Expectations
9 August, 2021
Problem Hiring in startups is all about setting clear expectations from the start. While managers mainly hire for a specific role, there are things that cannot always be specified in job descriptions or are constantly evolving. If this is not clearly communicated during the interview or in its immediate aftermath, people will at some point leave or be let go.
The fact that there was a disconnect from the start between what you expect new hires to do and what they will do once they join, indicates a lack of clarity. Mismatches of this kind generate a lot of frustration. A new hire is not at ease, you are not at ease, and stakeholders who will notice misalignment will also not be at ease.
To avoid the problem of misaligned expectations, I try to be explicit about the company mission and key objectives for an upcoming period before a new hire joins in. Whether this is communicated during the interview or in its immediate aftermath, it is taking place before their official start date. Many people told me that it is too early to bring up expectations before the person starts working, but in fact, I think it never is too early, and I will seize the earliest opportunity to set expectations right.
One of the first questions I would ask a new hire would be, What does success look like to them in three months. For example, if they join on September 1, what do they expect to achieve by December 1. I would create the document containing my own expectations and their answers and socialize it broadly across the organization. Everyone would get a chance to learn about those expectations and what the new hire will be doing. This is critically important because expectations of all people who would be interacting with the new hire should be aligned.
This document also serves to guide the new person and help them self-evaluate their work. New hires are often overwhelmed by doubt: Am I doing this right? Having a clear path they should follow from day one is a key to their success. For example, the document may state that they should be working on four areas, each of which would have certain milestones. By checking those milestones, they can self-evaluate if they are on track in those four areas and, if yes, not worry too much.
One of the main challenges I face is how to frame what people shouldn’t be working on. Unlike things that one should be working on, things they shouldn’t be, are typically part of unspoken assumptions and unwritten truths. Yet, most misunderstandings are hidden in unwritten truths. Therefore I would always be explicit and have everything in writing: a new person will work on A, B, and C but not on D.
Finally, communication is critical to managing expectations. Sometimes it takes to over-communicate, but over-communication triggers questions and feedback, and if anything was unclear, it would be clarified. Communication is all about repetition and preparation. It doesn’t involve only a new person, but other people who need to share documents, engage in conversation, answer questions, etc. An extra effort put into communication will no doubt be paid off in the long run.
- Be clear on what is expected from a new hire within the first three months. Those expectations should be tangible and verified by someone on your team in terms that those are feasible for one person to achieve. If you have vague or unrealistic expectations, that will leave a lot of room for interpretation. Leave too much room for interpretations, and you will have difficult discussions.
- Involve other people. Expectations are about alignment: a new hire’s, yours, and everyone else who will be interacting with the new person. Make sure that everyone’s on the same page and that everything has a paper trail.
- You can never over-communicate. You need to repeat every single thing at least three times to consider that as communicated. When it comes to expectations, it takes even more repetition.
Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader
Viswa Mani Kiran Peddinti, Sr Engineering Manager at Instacart, walks through his experience scaling a team, product and his skills as a leader.
Viswa Mani Kiran Peddinti
Sr Engineering Manager at Instacart
Vineet Puranik, Senior Engineering Manager at DocuSign, discusses the impact of roadmaps, organization, and proper management for your teams to procure growth.
Senior Engineering Manager at DocuSign
Saikrishna Desaraju, Engineering Manager at Marks & Spencer, draws from his personal experience to advise new managers on thriving in their roles.
Engineering Manager at Marks and Spencer
Josef Starychfojtu, VP of Engineering at Mews, delves into his interviewing tactics for recruiting the best-suited candidates.
VP of Engineering, Platform at Mews
Krishanu Sengupta, Product Lead, AI & ML at Compass, offers insight on how to develop into a role you are passionate about by obtaining experience in roles that build relevant skills.
Product Lead, AI & ML at Compass