When it comes to a successful career in tech, it's not just about technical skills. Non-technical skills are just as important, if not more so! Some examples of non-technical skills that can help you succeed in tech include:
- Time management
- Critical thinking
What other, maybe less obvious. non-technical skills do you think are important for a career in tech? Share your thoughts in the comments below!
Top comments (21)
Does English count as a non-technical skill? It definitely aids in the furtherment ov one's career.
Linguistics, as a whole set ov concept and terminology, is vastly important and can help bridge gaps in communication, but that is more than technical, so it doesn't count.
I think it definitely counts. It's important in several ways.
Coming from a non-English speaking country I think it's very important to learn to search for information in English. There is much more information available, and often much better sources of information. Just take wikipedia as an example. Any article in English will have way more information than the same article in my native language (unless the article is specifically about something related to my country/language, but most technical articles aren't).
I see programming as an English-first job. There may be exceptions, but it certainly helps.
Well, support u.
When i started, it was difficult to communicate with colleagues. I had to upgrade english from the "speaking" one to professional. There are always many apps to improve the language. For example, Grammarly.
Btw, my friends developed an extension for Google Chrome (i don
t know if i can post here links, but lets try) Natively.ai. It can rephrase and correct your texts online. They are searching for first users (it`s definetely free) for tests
That's why I wanna diversify the languages programming can be accessible in.
Specifically, I've been practicing Swedish, which I will make programming articles in. (You can see a, not yet implemented, preview of that on my GitHub profile.)
Thank you for your engaging response,
May I not sound rude when I ask this, Do you know English?
Yes. Of course I do, I'm an English (US) native.
May I ask why you ask or what prompted you to ask?
For various reasons: frustration tolerance
Some things will be hard to understand and require you to try it multiple times until you get it.
Documentation will be bad or even non-existent.
Higher ups will want you to do things you think are a bad idea.
For communication some people think it is "How to speak" but the first part is listening: even people we don't agree with / even people who attack you. You have to stay calm, extract primary idea from oral sentence, put it in your memory-queue and wait your turn (silence is a requirement to a respectful communication). Being impulsive is something to fix.
I love to see diagram in documentation (UML or not), I think it's a good tools to explain something: tracing a HTTP call inside network, explain a debug process. So the ability to resume complex idea into a simple thing is very helpful for communication
Estimating the amount of time a task will take (I am terrible at this). I feel like I always say "a day or two most likely" and never anticipate weird things that make tasks take longer than expected.
Listening and paying attention to what others do an say will help you boost many soft skills at once. I talked about it on this article (Sorry for the self promotion)
Writing emails, or in general, communication.
Curiosity: Be curious about your users.
Try to understand how they do their job. What are the challenges they face with the current approach?
What would an ideal solution look like from their point of view?
Sometimes, you get the chance to sit down with your (potential) users and ask them all these questions.
But even if you're not in contact with them, try to make the effort, for instance by reading support emails or ask to work on the support team once a week to have these conversations.
Gathering this first-hand knowledge opens doors. First of all, you get to see the problem from the user's point of view.
Additionally, your users might lead you to a solution you haven't thought about before.
Time management is huge. One of the things I have to do so I don't get bogged down in constant meetings is block out time on my calendar every day specifically for work -- at least two hours. I do this on the first or second day of a new job, and I defend that time viciously. I'll outright reject meetings during that time, unless it's my boss, in which case, I'll propose a new time. But I don't back down from it. During that time, my headphones are on, my IDE is open, and I'm pounding out work. I find that when I'm interruption-free, I can get more done in those two hours than I can all week when trying to squeeze in time around meetings. (Also, definitely don't go to a place that has a meeting-heavy culture.)
Thanks for your sharing. Add life-long learning skill here 👉How to Boost Learning Efficiency-9 Tips You Should Know
2) communication; and
All the rest (including collaboration) follows from that.
is personality development important as a non-technical skill for a career in tech?
imo, patience and listening... and the humility to question my own assumptions...
Something that isn't noted here but i think it is important.
I am surprised I missed this discussion! PATIENCE! Patience, patience.
Discipline, and being open-minded for my taste :)