For further actions, you may consider blocking this person and/or reporting abuse
For further actions, you may consider blocking this person and/or reporting abuse
Luciano Jung -
Jorjis Hasan -
Michael Tharrington -
OLUWAPELUMI -
Top comments (40)
Someone who learns fast and wants to learn. I can teach skills to anyone, but if they don't have the drive to learn then the lessons are not going anywhere.
Also, I look for humility and lack of embarrassment re: their code. I think a lot of devs suffer bc they're to afraid to show other people their code till it is "perfect". Code is never ever ever going to be perfect and in the mean time those that are embarrassed are missing the opportunity to learn and teach their code and perspective. There is plenty to be learned from reviewing in progress code and if the person can't get over their fear of sharing code (and really, understanding that everyone writes"bad code" at points) they're missing out.
Yeah, and in general to all devs: with code I find that the end isn't nearly as valuable as the journey there. If you work w a team of devs, share and review each other's code and talk to each other about it. It's one of the most valuable resourcs you have access to.
The first question I always do is to ask them to explain what they working on recently. What was the overall project, what has been their contribution, what was the benefit to the customer, what has been the biggest challenge and how did they succeed. Tells you about communication skills, strategic understanding, empathy and customer focus.
Plus patience, curiosity, and a sense of humor.
The first question I always do is to ask them to explain what they working on recently. What was the overall project, what has been their contribution, what was the benefit to the customer, what has been the biggest challenge and how did they succeed. Tells you about communication skills, strategic understanding, empathy and customer focus.
Plus patience, curiosity, and a sense of humor helps a lot.
In less senior developers I look for curiosity, the willingness to learn, the ability to listen, the ability to admit when they're stuck and the confidence to disagree with others in a constructive way.
In more senior developers I look for the willingness to teach, the ability to admit they are wrong and the absence of condescension & arrogance to less senior devs or non technical folk (in addition to all of the attributes I look for in less senior devs). Being able to deliver a decent presentation is also up there for senior devs.
Very well said. I feel as though hiring managers often look simply for the best skillset on paper, backed up by memorable definitions that you can come up with. Instead, taking the time to talk about what excites you as a developer and what you want to achieve can go a lot further.
I agree with you. Communication is really important on a team. Learning new things and adapt to the implemented work. Teaching and share information is also good for new developers or new teammates.
After reading about "makers vs menders", I have started looking for developers whose favorite things to do compliment the current makeup of the team. We need makers and menders. This is sort of a technical skill, but it's more of a personality type. We need both types of people.
I really appreciate good old fashion hustle. If I get the idea that you're going to pour yourself into something and really care about it, I will probably want to hire you. If you're very smart and technically skilled, but picky about how you contribute or "too good" for certain kinds of work, I'm going to have a hard time with you.
Ultimately I want to give you work you like, but you can't be too good for what needs to get done right now.
Exactly. Way too many people out there who think they are too good to do the dirty work. Guess what? That's where you show your real skills. Anyone can look good on green field projects. Few can take a piece of crap codebase and improve it. I take pride in being able to do so.
Curiosity. Love for the craft. Positive communication.
I very much agree!
The ability to express themselves clearly and efficiently in writing. This includes hitting the right tone in terms of their emotions, and taking into consideration the needs and emotions of their counterparts, without being too deferential or condescending.
That's a great call. Do you have any thoughts about approaching someone who is (unintentionally) bad at this and helping them improve without making them feel too guilty?
I once worked with a lady who helped me level up in this area by showing me how to do it and providing templates. I quickly learned without my ego taking a hit. I really owe her a lot of my following success.
Communication skills are key. If they can't communicate their ideas clearly, they probably can't code clearly, either. Code is communication.
Most of what I look for falls under the umbrella of emotional intelligence, which includes the ability to recognize and manage one's own emotions and to be considerate of the emotions of others. Empathy is a big part of that. Humility is also important, and on a related note, open-mindedness to new ideas and suggestions from others. Embracing a growth mindset, as opposed to a fixed mindset, when it comes to the developer's own abilities and the abilities of coworkers and interview candidates is also key. I actually teach workshops and mentor engineers on developing these human skills, so feel free to reach out if you want to discuss further!
Unbridled enthusiasm is great, it really distinguishes those who have passion for programming and see the magic, and those who do it because they can and it pays well.
The ability to explain topics clearly and concisely as well - I think that's a big indicator of a solid understanding of a topic.
I've blogged about what I look for in interviews here
Humility
What & how many books do you read? This helps me separate the "Grower" from the "Shower". Voracious readers inevitably have the following qualities:
Someone who knows programming at the hardware level as their platform and the ability to reason about costs incurred by their code whilst transforming data upon it. Understanding that code is not what a programmer does, it the tool she uses to do it. Resistance to popular dogmas in technology, willingness to put her ideas to the test and eagerly replace her methods once it has been established that another one is the better solution.
A desire to share, teach and mentor.
Inductive reasoning (to indicate the ability to dive into and solve complex problems). I call it the Sherlock Holmes ability. I think this is a great developer ability, especially for debugging. 💩 will hit the fan and when it does, inductive reasoning increases the probability that you look for the reason in the right place.
Put simply, you need the guy who rolls up his sleeves and says, "Right, let's go and de-💩 the fan. Who's with me?"