The IT Skills Nobody Puts in the Job Description
The job advert lists the tools. It never lists the part that decides whether you are actually good at the job: reading people, knowing when to stop, saying the hard thing early, and checking back.
- Published
- 17 Nov 2026
- Written by
- Md Tayobur Rahman
- Topic
- Developer Job Interview
- Reading time
- 4 min
Article
Read a typical IT job advert and you would think the work is a list of things. Windows, Active Directory, a ticketing system, maybe some PowerShell. The ad describes the tools, but almost never the work. The part that actually decides whether you are good at the job — the part your manager notices within a month — is not on the requirements list at all.
Most of your day is reading people, not systems
A ticket comes in that says "laptop very slow". You walk over expecting a disk problem. The person at the desk has a client call in forty minutes, a deck that takes two minutes to open, and a look on their face that says they have already restarted twice and are close to giving up on you too. The job in that moment is not the disk. It is deciding, in the first ninety seconds, whether they need the fault explained or they need to be on time.
Those are two different jobs, and nothing in the job description tells you to notice the difference. You learn it by getting it wrong a few times — by delivering a beautiful explanation of fragmentation to someone who just wanted the file to open before the call started.
The discipline of stopping early
The printer on the third floor jams every Tuesday. You can spend the afternoon chasing the driver, or you can say: use the one on the second floor today, I will dig into this after four. Neither answer is lazy. What gets people into trouble is doing the impressive fix while eleven tickets pile up behind them, because the interesting problem is more fun than the boring queue.
Judgement about when good enough really is good enough, and the willingness to say that out loud before anyone asks, is a skill no certification covers. New techs tend to think thoroughness is always the right answer. Experienced ones know that thoroughness delivered at the wrong moment is just lateness with extra steps.
Telling people things they do not want to hear
The finance director's laptop has a battery swelling under the trackpad and a hinge that is starting to crack. She has an audit in three weeks. Or the shared drive everyone calls "the real backup" has not actually been backed up since a migration last spring that nobody wrote down.
The technical part of these situations is easy — you already know it is bad. The hard part is walking over, saying it plainly, and giving a date, a number and a consequence without softening it into nothing. Most IT failures I have seen were not technical. They were someone who knew in March and did not want to be the person who raised it.
Following up when nobody is watching
Someone messages you at four on Thursday: it is fine now, thanks. You know it is not fine. The next morning you ask whether the file opened properly for their client, and if it did not, you are already halfway into the fix before they have had to chase you.
That check-in takes ninety seconds. It does more for your reputation than a month of clean ticket closures. Nobody writes "will chase this until it is actually fixed" on a CV, but every manager who has hired for a helpdesk can name the difference between a technician who closes tickets and one who closes problems — and can usually tell you which one they fought to keep.
You can teach someone to image a laptop in a week. The rest — reading the room, knowing when to stop, saying the uncomfortable thing early, caring enough to check back — takes years, and it is the part of the job the advert never mentions.
Share
Contact
Available for Laravel platforms, native Android apps, and the systems that run behind them.