Ask HN: What is one learnable skill you wish was more common in job applicants?
HN, what is ONE learnable skillset you wish was more common in applicants to jobs at your company?
We all take for granted the various views we have about skills versus demand, and hiring ads always show the “bucket list” but never say “We want more applicants with a focus on skill XYZ this time around”. So, for those of you that have hired or are hiring in the past year, what is the one skill you wish more applicants had experience with, over all other skills that they could learn?
- Please choose one skill; no ties, no top three, no shopping lists. Picking one is hard, but it’s worth it.
- I’d especially enjoy hearing from YC startups that posted hiring ads on HN this past year.
- Sample answers: C# operations, git rebase, resolving differences through compromise, understanding EDR/XDR
29 comments
[ 3.4 ms ] story [ 73.7 ms ] threadgdb/lldb/windbg
multi-thread programming
Why do you need all candidates to know this?
“Why do you desire that more candidates know Rust?”.
(I don’t need to know personally, but duly noted anyways.)
Outlining clearly that you disagree with this approach, the risks involved and suggest an alternative but in the end you’re happy to build it as they suggest.
Code is very easy, people are 'hard'.
He was, from my perspective, very sharp. He said that his manager at a previous job stated that the most valuable skill was getting along with others. The manager stated that he could train any human monkey to code, but the interpersonal relationships skills were tops in his view.
Very few people can code.
Almost everyone is capable of getting along with other people.
Why did they get hired in the first place?
We all use frameworks and libraries that are maintained outside of the company we work for. Those frameworks and libraries help us to do our job faster and it's fantastic that they are available to us. However, sometimes those external codebases cause a problem for us. The abstraction breaks or falls down. There's a bug in that external codebase. If no one at the company is capable of debugging and understanding that codebase then when the abstraction fails us a lot of time is wasted.
It's also really good for a company to be able to contribute fixes to an open source codebase back. It's healthy for the open source project and in turn makes that project better for the company.
Too many co-workers type very slowly, and I have to shamefully admit, I avoid helping them at times because to much time is wasted on simply watching then type.
It reminds me when I sometimes ask younger developers for advice, and I can feel their frustration when I don’t do things at the speed they would like.
But, for me that is missing the point. I generally ask advice to spark conversation and learn from each other. The speed of carrying out the act is irrelevant.