Like it or not, this is a must for a developer. If you can’t tell your manager why your solution will miss the deadline, you’re fired anyway.
This is absolutely not related to the job. But if you can use your brainpower and your hands together to create anything from gadgets to furniture (or even a house), you are most possibly a like-minded creature I’d like to work with.
Again, an obvious thing for a developer. Technology stacks come and go. If you are willing to learn, that’s not enough: I don’t want you to learn just because your job. I want you to learn because you want to.
This is the most important one, and I always include something related to interviews. If you can’t fail, you can’t make software. We are all human, and as such we err a lot (even if you don’t admit). If you can fail and learn from your failures, you are one of the best candidates.
Now many of you will argue why I miss team work here. Simply put, teamwork is not everyone’s game. Of course, you must obey some rules (like using spaces, not tabs. Just joking) so the code base won’t fall apart, but even if you are not a team player, I can give you a lot of tasks. It is just a matter of communication. “Hey Designer Guy, I need you to design feature X for me.” Later, I can approach you with something like “Hey, you have to implement feature X, here’s the design”. I know this was a bit unrealistic example, but I hope you get the idea. In a good team, even a non-team player can contribute large to the project.
I agree with what Arpit said. In addition to that, the person should be:
Along with what @mohanarpit mentioned...having a good sense of humour goes along way to fleshing out ideas and challenging the norm.
Arpit Mohan
CTO @ Appsmith
What & how many books do you read? This helps me separate the "Grower" from the "Shower". Voracious readers inevitably have the following qualities: