#19 – Recruiting Primer – Part 2
from Tech Deciphered
In episode 19, we share detailed advice to recruiters, sharing views on job descriptions, finding talent, interview process, good and difficult interview questions, other hacks, as well as our own “pet peeves”. This is the second episode on recruiting. In episode 18, we framed the discussion and shared our core recruiting principles, including in compensation, and in the design and development of the recruiting organization. Episode 20 will end our trilogy, by focusing on detailed advice to candidates. Navigation: Introduction (01:24) Section 1 - The Job Description (02:00) Section 2 - Hacks & Tools (10:19) Section 3 - Finding Talent (15:04) Section 4 - Interview Process (18:14) Section 5 - Other Hacks (31:52) Section 6 - Pet Peeves and Dislikes (39:17) Conclusion (41:27) Our co-hosts: Bertrand Schmitt, Tech Entrepreneur, business angel, advisor to startups and VC funds, co-founder at App Annie, @bschmitt Nuno Goncalves Pedro, Investor, co-Founder and Managing Partner of Strive Capital, @ngpedro Our show: Tech DECIPHERED brings you the Entrepreneur and Investor views on Big Tech, VC and Start-up news, opinion pieces and research. We decipher their meaning, and add inside knowledge and context. Being nerds, we also discuss the latest gadgets and pop culture news. Subscribe To Our Podcast Intro (01:24)Bertrand: Welcome to episode 19. This is the second episode in a trilogy of episodes on recruiting that started previously, with episode 18. In this new episode, we are going to focus on the recruiter side: writing a job description, the tools and approach to find talent, the interview process, global differences, the evergreen approach to recruiting, closing candidates. And we will conclude on our pet peeves and dislikes.Section 1 - The job description (02:00)Nuno: And maybe switching and going into the weeds a little bit on advice that we would specifically have for recruiters and starting with the job description. The job description is normally this painful thing that someone has to do that involves some copy pasting, hopefully if there's a template or some Googling in the middle, to define what the job looks like.I think this is absolutely the wrong approach, just to be clear. A job description, I think has two sides to it. There should be an external job description, which is manifested to the market. That can be used with external recruiters, that can be used with candidates directly. And that should be sharp and really conveying what hard skills are being looked for, what soft skills are being looked for, what is the value system of the organization, and obviously a brief description of the organization, and finally, a little bit on how that position would fit in terms of roles and responsibilities within the organization. Those four or five things need to at least be there.It should be sharp, it shouldn't be a three page job description. I've seen seven page job descriptions. I'm like, why?Bertrand: No way.Nuno: Is anyone gonna read that? And sharp should be one page, very clear, there should be a lot of attention to the words that you use and the clarity on it.And it should really be appealing. It is a marketing material. I'm not saying it's not, but it should also be clear in filtering people that have certain skills versus others, people that have a certain value system versus others, et cetera. Then there's a little bit the internal job description, which also should be very clear. Which is, who is this person going to report to, what are going to be the day to day of this person, the complexity of it, et cetera.I'm not sure that needs to be manifested in a very formal way. But there should be clear understanding around the table, from the hiring manager all the way, maybe to the CEO early on in the company, to the person that's managing the recruiting process so that there is clarity on what works and what doesn't.If there are some unwritten rules that are not in the job description that is shared externally, it should be there. It should be clear to the team what actually are we looking for here. And so again, for me, the job description is an incredibly important tool of framing to get the right talent, so again a marketing material, to frame that talent against the rest of the market, and also to be used as an internal play on these are the flags that we have in mind. And this is what we're looking for. The final point I would make on job description is, sometimes job descriptions are incredibly prescriptive. I'll give a stupid example. Someone who has a tremendous amount of experience in doing partnerships, for example, in the financial industry or the financial services industry might not have been someone who was in business development for the last 15 years.It might've been someone who was doing something else around that industry for the last 15 years. And so sometimes I feel that if the job description is badly framed, it also frames really badly the type of talent you're looking at, in particular if you're using external recruiters, that's even worse. Because they're looking for a very specific type of profile, and that means you're formatting everyone that you're recruiting in this industry. I remember having a discussion with someone a few years ago, a very large tech company that's well-known was hiring a VP of Corporate Development and someone had reached out to me about that position.And as I was having that discussion, I met someone who used to be the VP of Corporate Development, maybe two cycles before. And that person just shared with me, "they're going to hire someone from Google or Facebook". And I said, "why?" "Because that's what they do". And so again, this cycle of formatting, right? Where you have people that run around with the same playbooks. If you are looking to change fundamental your playbook, you shouldn't go and hire someone who's been doing the same playbook for five years, right? Unless maybe that's the playbook you want to follow, but you should have someone that can recreate a playbook from scratch and maybe the right talent is not on paper getting someone from your direct competitors. Maybe it's getting someone that has that skillset, but has grown through the ranks in a startup or someone who was CEO of a startup that very heavily skewed towards that role. Again, very important job description, but it needs to be used as a tool to frame the hiring, not as a copy paste exercise or a Google exercise.Bertrand: Actually that was actually going to be a discussion for me on my pet peeves. And that's an issue I have seen again and again especially in Silicon Valley, where in some ways, you have so much depth of talent that you end up with, "I want this person who has done this specific experience, has done this MBA, has done this engineering school, and has worked five years at a big corporate, and has done this, and has 20 years' experience in databases".And guess what? Actually, you can find people with all these criteria , they exist, at least, in Silicon Valley. But then, you end up with a situation where you don't bring up-and-comer, you don't bring people with varied experience, you just bring ultra, super-deep expert who actually might not be that interesting, because in some ways, they might have spent too long in big corporates for their own good. And I'm always surprised to see that mindset and approach, where in so many other regions, you simply have no one who has more than 10 years' experience in a specific industry or space. And guess what? It actually works well enough. You might not need that 20 years experience. So I think that's something to be extremely careful. And, yes, a good job description can help you not to go in that direction. And personally, I prefer someone who deeply understand the game, but is also very hungry, to achieve, to succeed, to go to the next level, versus someone who has been there, done that for way too long and is not excited anymore, for whom this is just another job, more or less like the same, versus someone who really want to make a dent in the universe.Nuno: And very, very early on in my career, I applied for this position, I still remember, that required five years of experience as a project manager in an engineering environment, what we would now call engineering manager and five years experience in technical sales. And I literally had been working for three and a half years total, where I'd moved from being a developer to basically an engineering manager and then a product manager.And I'd never done actual sales in my life and I applied for it. And it's very interesting 'cause I went through the whole process. This was a long time ago, so I think I can mention it now. It was back in Europe with HP when HP was really cool some time ago. It's very funny the hiring manager, for some reason, liked me and it's very interesting. They actually made me the offer. I didn't join, which is sad because the salary. It's one of these things you do when you're young. I took some other job that paid much less and didn't have the same responsibility. It's just, I went to after some stupid dream. And that's the one that sort of got away in some ways, but I once asked the guy, "Why did you even look at me?" And he's like, "there was no loss in just at least having one interview with you. And you had an interesting background, you were, you started working very young through college and I was like, there's something about this guy. That's interesting. Let's just check him out. And as we went through the whole interviews, the whole team thought you had all the core capabilities to excel at this play, to excel at the role that is required from you. And you have one third of the experience, literally, but we thought you could excel at it." And those hires normally, again, I didn't join this organization, but those hires normally I think,...
Embed this episode
No transcript yet.