It’s hard to properly assess someone’s intellect, overall skills and, ability to adapt & learn in a few hours of interviews. Much easier to pass candidates through a sieve and pick from the remaining few.
Unfortunately, no. People can be really good at covering up for massive inadequacies, and it can take weeks or months to really start figuring them out.
It’s a long tail problem.
Two things you can do that will help is to make your hiring process much more data driven, and to put your people who would be working with them on the team of people that will be doing the interviews, and give them extensive training on how to properly perform those interview panels.
You could also follow that up with take-home example work, for some cases.
But the real trial is those first few weeks and months, where they have to know that they are being carefully evaluated, and where if things don’t work out then you can make sure that you can easily let them go.
I recently joined a new employer in October, so I am acutely aware of this situation.
This attitude has always struck me as a bit weird. I read it as "the whole industry is wrong and I am right" somehow. Everyone else has learned how to play the game, why haven't you?
Many companies I’ve worked for are pretty open-minded in terms of having a broad range of technical experience and I don’t think I’ve ever met every single requirement in a description for a job that I’ve accepted. You should never ignore an interesting job posting that doesn’t fit your background 100%, especially in this job market.
I’d encourage you to figure out what YOU want to work on and find companies that give you the opportunity to do those things. That said, this is a difficult question to answer because I’ve always looked at those requirements as what I’ll wind up doing for that particular company. I wouldn’t want to take a role that didn’t clearly define what I would be working on, and most companies are going to expect you to work on some platform/product/whatever consistently.
And at McKinsey we're hiring! Lots of mentorship for early-career engineers, support and encouragement to try on lots of hats, and your work is 99% code not PowerPoint pages :)
Look for companies that don't do the Computer Science Trivial Pursuit hiring process. Then probably filter to companies where you are building something core to the business and the job isn't stuck in the IT department which is usually treated as a cost center.
Smaller tech companies usually will have more of a need for broad experience and aptitude because they don't have departments of XYZ specialists like large companies often do.
Then filter by stuff that interests you in some way. It doesn't have to be a passion, in my opinion, since you are working on someone else's product/passion. It would help but just being excited about whatever it is they build helps.
It would be cool if you could put postings out there like "Hey do you like coding? like working with others? like __some_domain__? We do __some_domain__ using XYZ tech, come talk to us." I believe the HR folks like to put requirements down because it gives them something to filter on that is easily defensible should employment law get in the mix.
You might have to define broad experience and aptitude. Most people have it, it comes with years.
But generally startups require them. The early stage ones especially, but plenty of established ones do too. Research also benefit a lot from breadth.
I noticed American companies are much more likely to specialise, because the market rewards the best. Developing countries are likely to have lots of markets that are poorly addressed, so they get into research more.
16 comments
[ 2.8 ms ] story [ 50.5 ms ] threadGood luck in your search.
It’s a long tail problem.
Two things you can do that will help is to make your hiring process much more data driven, and to put your people who would be working with them on the team of people that will be doing the interviews, and give them extensive training on how to properly perform those interview panels.
You could also follow that up with take-home example work, for some cases.
But the real trial is those first few weeks and months, where they have to know that they are being carefully evaluated, and where if things don’t work out then you can make sure that you can easily let them go.
I recently joined a new employer in October, so I am acutely aware of this situation.
I’d encourage you to figure out what YOU want to work on and find companies that give you the opportunity to do those things. That said, this is a difficult question to answer because I’ve always looked at those requirements as what I’ll wind up doing for that particular company. I wouldn’t want to take a role that didn’t clearly define what I would be working on, and most companies are going to expect you to work on some platform/product/whatever consistently.
What location? What company? Please could you provide some details?
https://www.mckinsey.com/careers/search-jobs#?query=software
Smaller tech companies usually will have more of a need for broad experience and aptitude because they don't have departments of XYZ specialists like large companies often do.
Then filter by stuff that interests you in some way. It doesn't have to be a passion, in my opinion, since you are working on someone else's product/passion. It would help but just being excited about whatever it is they build helps.
It would be cool if you could put postings out there like "Hey do you like coding? like working with others? like __some_domain__? We do __some_domain__ using XYZ tech, come talk to us." I believe the HR folks like to put requirements down because it gives them something to filter on that is easily defensible should employment law get in the mix.
If you have a better anagram for FAANG -> MAANG, I’d love to see it.
But generally startups require them. The early stage ones especially, but plenty of established ones do too. Research also benefit a lot from breadth.
I noticed American companies are much more likely to specialise, because the market rewards the best. Developing countries are likely to have lots of markets that are poorly addressed, so they get into research more.