Live data from Hacker News

Don’t hire top talent; hire for weaknesses

benjiweber.co.uk

111–120 of 168 posts

Re: Don’t hire top talent; hire for weaknesses

#111

>Instead of “how can we find the smartest people?” think about “how can we find people who will make our team stronger?” I would have thought that was obvious? Why would you hire someone unless you had a need for their talents? I guess I'm probably thinking small-business. At the biggest companies, they probably just hire and hope to fit them in because hiring for exact needs doesn't really scale.

> that was obvious? Why would you hire someone unless you had a need for their talents?

To me, that sounds like you think of weakness in terms of "Oh, our UI sucks, let's hire a javascript developer." But is that really what the article means? Could weaknesses be more abstract things like "low trust", "failure to speak up", "inability to change according to market needs"? Do you know many teams that really know their core problems and actually try to solve them?

Re: Don’t hire top talent; hire for weaknesses

#112
How about just fire your whole HR department, and let team leads do the work of finding qualified engineers for their needs?

HR is the bane of the technology world. As a cultural phenomenon, the class of "HR" specialists are massive drag on the progress of the species. We would be better off without this role in our technological cultures.

So much technical debt accrues because the HR person doesn't have a single, frickin', clue what they are doing. If you don't know what "firmware" means, don't try to hire firmware developers, yo.

Re: Don’t hire top talent; hire for weaknesses

#113
post #96
post #89

Earlier quoted context omitted.

Btw, I've heard fb is moving away from leetcode BS stuff for interviews. Can you confirm that?

What are they replacing it with? Back to prestigious university?

With the stuff related to the actual day job. I've heard this about their London office.

Re: Don’t hire top talent; hire for weaknesses

#114
post #109

> “We hire top talent” These phrases are mainly intended to flatter the employees, to make them grateful for being "chosen", and maybe to increase trust and confidence among them. Choosing who to hire (once basic requirements are met), is much less important than the morale and attitudes among employees. Much better to say "top talent" than "randomly picked". But, the hiring process is a huge factor in the perception…

HR people should be required to demonstrate the basics of the technology they are hiring for .. if they can't do that, they're not qualified to gatekeep the technology teams.

Too often, HR is used to repress technological advances, out of fear of loss of control. That is a good thing: HR should lose control over technology groups.

Re: Don’t hire top talent; hire for weaknesses

#115
The article assumes that most teams know and openly talk about what their weaknesses are. But is that actually a common thing? Don't we have a natural drive to ignore our weaknesses and blame them on others?

It's a little funny, because the alternative phrasing also includes that already.

One hires the best of the best without specifying the best of .

"The best people will solve all the problems!" without any inclination about what the problems are.

Doesn't that imply that one doesn't actually know one's own problems and hopes that if one can just hire a people smarter than oneself, they will figure it out for you?

Re: Don’t hire top talent; hire for weaknesses

#116
post #109

> “We hire top talent” These phrases are mainly intended to flatter the employees, to make them grateful for being "chosen", and maybe to increase trust and confidence among them. Choosing who to hire (once basic requirements are met), is much less important than the morale and attitudes among employees. Much better to say "top talent" than "randomly picked". But, the hiring process is a huge factor in the perception…

To me, much more important in that phrase is expectation who will you be working with. It's fantastic to be surrounded by smarter* people and keep learning, but at some level it's hard and if you like what you do, then this seems to be the most important thing about the job.

You have your basic financial needs covered when you're a decent coder, even boring projects can have great and interesting implementations, it all drops down to people who you are working with.

Also, not just in IT, true masters tend to be interesting people in my experience. More often than not, they have humility and curiosity that allowed them to get that far.

But of course it often tends to be an empty phrase. If they do hire top talent you are more likely to hear specific names rather than this phrase.

1. smarter / more experienced / more knowledgeable / sometimes even having your level of expertise but coming from a different background

Re: Don’t hire top talent; hire for weaknesses

#117

Talent is everything. Without Elon Musk, or Von Braun there are no key rocket program break throughs. Not that I know much about rockets, just that there are key talented people that push the world forward. You need the worker bees. But someone at the top has to be the visionary genius. If was the manager of a soccer team that came in last in the League. One way of improving would be to replace my weakest players. An…

This is a valid argument for the discussion. I don't agree with it, but thanks for sharing.

What do you think are Elon Musks talents that push his SpaceX program forward?

In which area do you think that you could make a valuable contribution to the world?

Re: Don’t hire top talent; hire for weaknesses

#118
The article spends most of its words trying to convince the reader to do it, and only a few paragraphs on how to do it. I was convinced in the first paragraph.

My own experience shows that hiring for your team's weaknesses can make it more effective. In 2013, I went from an operations-heavy role to a new team with little operations experience. Our TL designed and coded a new service. He was not happy with the feedback I gave through the design & code review process. Before deploying the new service to production, we met with one of the company's top engineers (Sanjay Ghemawat) for a "production readiness review". The reviewer was impressed and found only a couple of minor issues. He said that it was rare for him to review a service and find no major issues. Many of the questions he asked during the review were things that I had brought up earlier and convinced our TL to fix. Although I had not written any code on the service, I contributed operational knowledge and filled a weakness of the team.

Our TL did not acknowledge my contribution and even gave me a bad review, costing me about $80k in compensation. Now, years later, I believe that he did that to get me to leave the team. I had often pushed to fix the major problems in our project. I think he wanted to keep control and continue working on fun things and ignore the problems. Our manager went along with him, building his own empire. I left and the person who took my place had the same problem and left as soon as they could. Honesty and respectfulness are important qualities of teams and team members because they develop trust. Trust makes teams more productive. An internal study at Google concluded that teams with members who trust each other are much more productive than teams with high technical ability and low trust [0]. Lack of trust is a team weakness that we can hire to improve. We can also intentionally train and practice skills that improve team trust.

I want a systematic way to identify the strengths and weaknesses of myself, my teammates, and potential teammates. I want a questionnaire like the one in Essential Enneagram which was tested in a study with 1,000 participants [1].

I wish the large tech companies would invest in this kind of work and publish it.

[0] https://rework.withgoogle.com/print/guides/5721312655835136/

[1] https://drdaviddaniels.com/enneagram-test/

Re: Don’t hire top talent; hire for weaknesses

#120

Earlier quoted context omitted.

Not sure why you think FAANG is getting the cream of the crop. Looking at stuff like Rob Pike's comments about Go's use for the general Google employee base [0], I think there is quite a lot of misalignment between the aura of mystique from the outside and the situation as seen from the inside. [0]“The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out…

> Not sure why you think FAANG is getting the cream of the crop. The best coders can demand the highest salary. If you can afford to pay the highest salary you are in an advanced position position to get the best coders. FAANG can afford to pay the highest salary. Anecdotal evidence to the contrary does not cancel this mechanism.

Sure a big salary is nice but especially Google hasn't done much in the last decade to make it look there is exciting, or even just satisfying, engineering happening there.
Post reply on HN