For most of my early career, I believed the technical part was the hard part. The architecture, the migrations, the outages at three in the morning, the decisions with real money and real risk riding on them. Everything else, the meetings, the persuading, the managing of feelings, I quietly filed under soft. Nice to have. Secondary to the real work. I was wrong, and it took me years and a few bruises to admit it.
The technical problems, however painful, mostly had answers. You could reason your way to them, test them, and know when you were done. The problems I now spend most of my time on do not work like that. Getting two senior people who distrust each other to back the same decision. Persuading a team to give up a system they built and love. Telling someone their project is being stopped in a way that keeps them with you rather than against you. None of those has a correct answer you can compile. They are harder than anything in the stack, and nobody thought to warn me.
The label itself is part of the problem. Calling them soft skills implies they are gentle, optional, the pleasant finish on top of the real competence. In practice they are the load-bearing structure. I have watched brilliant technical plans die because the person carrying them could not bring anyone along, and I have watched ordinary plans succeed because someone built the trust to make them happen. The industry has started to notice this out loud. Deloitte’s 2026 study of technology leaders makes the point plainly, that as the stakes rise, success now takes more than technical expertise and depends on the ability to lead people through change. The thing we called soft moved to the center of the job.
I would rename them if I could. Not soft skills but the human skills, or better, the hard skills, because they are the ones that are genuinely hard to do well and hard to fake. Anyone can learn a framework. Very few people can walk into a room where trust has broken down and rebuild it.
When I try to be specific about what these skills look like in my week, they are not abstract.
Listening properly, which means listening to understand rather than listening to reply. It sounds trivial until you count how rarely it happens in a senior meeting where everyone is waiting for their turn.
Reading a room, sensing when a decision has quietly died in people’s faces even though the words are still polite, and knowing to stop pushing before you turn a maybe into a no.
Telling hard truths without making enemies, so that the message lands and the relationship survives. This is the one I got wrong most often when I was younger, mistaking bluntness for honesty.
And building trust in the calm periods so it is there in the crisis. Trust is not something you can summon in the moment you need it. It is banked slowly, in dozens of small moments where you did what you said you would, and then spent all at once when everything is on fire.
Here is the pattern I did not see coming. The higher you go, the less your technical skill is what you are paid for, and the more the human skills become the whole job. As a young engineer, I solved problems with my own hands. Now I almost never touch the problem directly. I work through people, which means my effectiveness is capped not by what I know but by whether I can move others to act.
That is a genuinely uncomfortable transition for anyone who came up on technical excellence, because the thing that made you successful becomes the thing you have to partly let go of. The engineer’s instinct is to go solve it yourself. The leader’s job is to build the people and the trust so it gets solved without you, and often better than you would have. Making peace with that shift is one of the harder pieces of growing into these roles, and I do not think I have it fully finished even now.
If I am honest, I am still working on all of this. I have gotten better at listening, though I still catch myself composing my reply while someone is talking. I have learned to read a room, though not always in time. These are practices, not achievements you complete, and they never fully stop demanding attention.
So my one piece of advice to the technically excellent person climbing into leadership is this. Take the soft skills at least as seriously as you took the technical ones, because they are harder, they matter more the higher you go, and nobody is going to hand you a course that teaches them properly. You learn them the expensive way, in real rooms with real stakes. I just wish someone had told me early that the soft skills were the hard ones, so I could have started paying attention sooner instead of assuming they would sort themselves out while I got on with the real work.
