Hiring in Tech: Why We Keep Getting It Wrong
Tech hiring focuses too much on technical skills that can be learnt. The key is finding candidates with a strong work ethic, teamwork abilities, and a growth mindset.
What Is The Difference Between A Code Editor And An IDE Or A Text Editor?
Lorem ipsum dolor sit amet, consectetur adipiscing elit lobortis arcu enim urna adipiscing praesent velit viverra sit semper lorem eu cursus vel hendrerit elementum morbi curabitur etiam nibh justo, lorem aliquet donec sed sit mi dignissim at ante massa mattis.
- Neque sodales ut etiam sit amet nisl purus non tellus orci ac auctor
- Adipiscing elit ut aliquam purus sit amet viverra suspendisse potent i
- Mauris commodo quis imperdiet massa tincidunt nunc pulvinar
- Adipiscing elit ut aliquam purus sit amet viverra suspendisse potenti
Pros and Cons of Using These Editors:
Vitae congue eu consequat ac felis placerat vestibulum lectus mauris ultrices cursus sit amet dictum sit amet justo donec enim diam porttitor lacus luctus accumsan tortor posuere praesent tristique magna sit amet purus gravida quis blandit turpis.
#1 VS Code by Microsoft
At risus viverra adipiscing at in tellus integer feugiat nisl pretium fusce id velit ut tortor sagittis orci a scelerisque purus semper eget at lectus urna duis convallis. Porta nibh venenatis cras sed felis eget neque laoreet suspendisse interdum consectetur libero id faucibus nisl donec pretium vulputate sapien nec sagittis aliquam nunc lobortis mattis aliquam faucibus purus in.
- Neque sodales ut etiam sit amet nisl purus non tellus orci ac auctor
- Adipiscing elit ut aliquam purus sit amet viverra suspendisse potenti
- Mauris commodo quis imperdiet massa tincidunt nunc pulvinar
- Adipiscing elit ut aliquam purus sit amet viverra suspendisse potenti
#2 Sublime Text Editor
Nisi quis eleifend quam adipiscing vitae aliquet bibendum enim facilisis gravida neque. Velit euismod in pellentesque massa placerat volutpat lacus laoreet non curabitur gravida odio aenean sed adipiscing diam donec adipiscing tristique risus. amet est placerat in egestas erat imperdiet sed euismod nisi.
“Nisi quis eleifend quam adipiscing vitae aliquet bibendum enim facilisis gravida neque velit euismod in pellentesque massa placerat”
Wrapping up the article
Eget lorem dolor sed viverra ipsum nunc aliquet bibendum felis donec et odio pellentesque diam volutpat commodo sed egestas aliquam sem fringilla ut morbi tincidunt augue interdum velit euismod eu tincidunt tortor aliquam nulla facilisi aenean sed adipiscing diam donec adipiscing ut lectus arcu bibendum at varius vel pharetra nibh venenatis cras sed felis eget.
Hiring in tech is weird. You set up interviews, ask a bunch of questions, maybe throw in a take-home task, and after all that, what do you know?
That someone prepped well for an interview? That they remember syntax they could easily Google?
Most of what we test for—coding ability, familiarity with certain tools, even system design—can be learnt on the job. Sure, for some roles, you need deep expertise. But for the most part, if someone is smart and willing to learn, they’ll figure it out.
What’s way harder to teach? How to be a decent coworker.
What Really Makes Someone Good at Their Job?
There are things that separate a good hire from a great one, and they have nothing to do with how fast someone can reverse a linked list. The real questions are:
- Do they care about their work? You can’t force someone to take pride in what they do. Either they care about quality, or they don’t.
- Can they work well with others? Nobody wants to deal with a brilliant jerk. Tech is a team sport.
- Are they open to feedback? If they think they already know everything, good luck getting them to grow.
- Do they have grit? When things get hard (and they will), do they step up or check out?
These things are hard to measure in a traditional interview, which is why so many hiring processes focus on the easy stuff—like “does this person know X framework?” instead of “will this person make our team better?”
So, Who Do You Hire?
I’ve worked with engineers who had every credential you could ask for but couldn’t take feedback or work with others. I’ve also worked with people who started out with gaps in their knowledge but had the drive to improve and became some of the strongest folks on the team.
Given the choice, I’ll take the second person every time. Because skills can be learnt. Mindset? Not so much.
So if you’re hiring, ask yourself: Would I want to work with this person every day? If the answer is no, move on—regardless of how good their resume looks.
Views: 10
Chibuzor Obilom
Software Tester. TechPro. Rubber Duck. Futurist. Comprehensivist. 21st Century Theorist
