The chaos of the interwebs has once again washed me up on a bunch of exposés by young techies blowing the lid off soft skills. Once again, it turns out they're a global conspiracy by managers to distract creators from the sacred rite of writing code to the gentle clack of custom mechanical keyboard switches.
I was about to drop a link to a decent article on the subject, but it turns out 100% of the Google results are articles from sites selling some kind of “educational course,” where copywriters ramble incoherently about how important “communication skills,” “creativity,” and “emotional intelligence” will be in your future job.

Jesus. No wonder beginners are so confused. Lavender-scented life coaches and managers who learned everything from books have shat all over the concept of “soft skills” to the point where nobody has a clue what it means anymore.
I want to explain it the way I explain it. And yes, I don't give a shit how “unorthodox” or “not by the book” it is. It fucking works.
Here's the one definition you need to read five times and remember:
Soft skills are everything that isn't a hard skill but that you still need at work to keep shit moving
The real world isn't a scripted game where you win by pressing the right combination of buttons. It's complicated and it keeps changing. Figuring out how to adapt is the challenge.
The term “soft skills” wasn't dreamed up by wannabe scrum masters. It was coined by some hard-ass guys in the US Army in the '60s.
Right there in the middle of the Cold War, when humanity's biggest problems weren't “oh dear, how do I write a tweet without offending anyone?” so much as “OK, fuck, we need to stick those guys in a giant rocket and fire the fucking thing straight at the Moon so they're there by lunchtime.”
Back in those ancient times, some hard-ass Army officers were reading through a bunch of reports and got to thinking:
— OK, we've taught our brave young lads to shoot a pigeon in the eye with an M16 from 100 meters away and tear around the desert in a Hummer. But when the first group charged in like Rambo, they got wiped out in no time. The second group, who somehow coordinated with each other, reached their objective and lived.
Even tough leaders and secret tactics didn't help. There was some unexplained difference even between equally well-trained teams.
And since US military types are pretty straightforward people, orders were issued to study and classify the phenomenon in question so they could put out a new manual.
Those military manuals gave us the very first vague definition of soft skills: skills that had nothing to do with how well you could operate equipment or handle a weapon, but that you still needed on the battlefield for the operation to succeed.
No “emotional intelligence” or “ability to crack jokes on Zoom calls” on that list, as you can see.
In fact, most leadership and project management practices today, even in tech, come from US Army manuals. ADP 6-22 alone (yes, that's its actual name) is worth ten “New York Times bestsellers” on managing teams. But since reading those manuals really is a feat of physical endurance that only 0.001% of the world's population can pull off, the “bestsellers” are safe for now :)
Hard skills are easy: if they teach it at university (or in courses) in your field and test you on it in exams, it's a hard skill.
For a programmer, that's writing code, architecture, quality assurance, maintenance, debugging, and a bunch of other stuff you don't need me to tell you about.
For a product manager, hard skills include identifying stakeholders, writing user stories, figuring out priorities, estimating timelines, gathering feedback, and so on.
For any profession, you can put together a list of “base unit abilities” you just can't do without.
So how do you tell a real soft skill from “some bullshit nobody needs”?
Ask yourself three questions:
1️⃣ Do I do this on the clock?
2️⃣ Is it something other than one of my hard skills?
3️⃣ If I stop doing it, will my team (or project) slow down significantly, fail, or lose its way?
If you answered “YES” to all three, congratulations, you've found a soft skill.
What you do with it now is up to you. You can level it up and grow into a T-shaped senior engineer or a team lead. Or you can decide you hate it, chuck it out, and focus on specific hard skills in the hope of waking up one day as the genius Linus Torvalds. Depends on your goals.
Let's take a specific example. Oleg is your typical mid-level programmer at a product company.

It's a simplified list. Even a run-of-the-mill programmer would have more than ten things on there, but it'll do for trying out our three questions to see what kind of “skill” we're dealing with.
☝️ “Writing code,” “testing,” and “reviewing code” are definitely hard skills. They teach you those at university or in courses, and nobody will hire you as a programmer without them (in an ideal world, anyway. Maybe some people do get hired 🐺).
☝️ “Making coffee” and “doing 10 pull-ups” are definitely not hard skills for a programmer. But if Oleg stops making coffee or doing pull-ups, will it slow his team down? It'll slow Oleg down, sure, he likes that stuff, but his team probably won't give a shit.
So those aren't soft skills. They're just things you can do outside of work, or hobbies.
☝️ “Going to syncs” and “discussing features with the lead” are more interesting. They're a “yes” on all three questions, so they pass our soft skills test.
If morning syncs are how Oleg's team works and he stops showing up, the team will be missing information and will, obviously, slow down. People will start redoing the same things over and over and getting into fights. I've seen it plenty of times. You'll probably have to fire that Oleg for the team to survive, and as you can see, it won't be for lack of hard skills.
At his next job he might turn out to be a brilliant, indispensable programmer.
☝️ “Discussing features with the team lead” also suggests Oleg is good at planning, even if he hasn't figured it out himself yet. Credit to the lead: he's realized he can sit down with Oleg and quickly groom the backlog for the next sprint, and that he's got a potential senior on his hands. So he's taken to inviting Oleg out for “a chat over a smoke.”
When it dawns on Oleg that this (along with a couple of other things he does) isn't “a waste of time” but a real skill, even if it's a soft one, he'll be a senior at heart. Maybe then he'll even read a few books, level up, and become one for real.
You can run the same thought experiment yourself. Write down everything you do over the course of a workweek and run each item through those three questions to figure out where your soft skills come from.
Now you've got an actual list of them, and I bet there's no bullshit like “communication skills” and “emotional intelligence” on it, is there?
The more observant among you probably saw the second hot take coming back when we were making coffee. It kind of follows from the first.
Hard and soft skills are always relative to the role.
Which is why it's kind of adorable when young techies have a meltdown in the comments: “Just give me the official list of all these soft skills of yours and I'll fucking learn them all, and if you can't even give me a list then ur lying.”
You've got it all ahead of you, my friend! Just look at that spark in your eyes!
Take the coffee again. For Oleg the programmer, making coffee isn't a work skill at all, as we've established. For a barista, on the other hand, making coffee is the single most important hard skill.

We can even try to imagine someone for whom “making coffee” is a soft skill.
Say you're an American sales rep. You're famous the world over for the amazing coffee you roast at home, and after you serve it to clients, you close 20% more deals. Coffee is now one of your soft skills. Even if you didn't plan it that way.

Our programmer Oleg can write code of exactly the same quality for exactly the same REST API, but the soft skills he'll need to turn that code into a finished product will depend on the team.
Shocking.
Let me give you two examples from actual teams I've worked on.
The first is your classic synchronous team, doing Scrum in a beautiful office on the 48th floor of a megacorp. Important soft skills on a team like that include “sharing and getting information effectively at morning standups” or “not losing it when someone asks you the same stupid question for the hundredth time and you're fucking sick of explaining something this obvious to all these shitheads.”
The second team is scattered all over the world and communicates exclusively async. No daily syncs, no story points on every task, because it just isn't feasible: when the US devs are waking up, the guys in Australia are going to bed.
On a team like that, other soft skills come first: “planning your own to-do list for the day so you don't sit around with your thumb up your ass waiting” and “actually sorting things out in an async chat.”
And I've seen people do well in one environment and absolutely fail to survive in the other. Covid, by the way, made it painfully obvious how often things ground to a halt at traditional companies when they went remote, because even their leads had no idea how to work async.
They kept worshipping at the altar of the “morning standup” on Zoom, without even grasping the concept of time zones: by the time US headquarters wakes up, Europe's already having a beer and Australia's on its third dream of the night.
Meanwhile, I'd strategically post five numbered questions in the chat ahead of time, and in the morning I'd get “oh hey, it's late where you are, let's talk about it at standup tomorrow.” Fuuuck)0))
That's a perfect example of someone who gets an A+ in “emotional intelligence” but completely lacks the soft skill of working async.
That manager did get fired eventually, by the way. But I'd already left.
So when I say “soft skills,” I mean specific skills without which you're screwed on a specific team. Not some abstract crap like “stress tolerance” or “communication skills.”
🤓 For extra credit, here's something to think about: could writing code be a soft skill under this definition?
Every interview is a soft skills test, at least in part. Not many teams need a genius programmer who can't work with other people. Maybe as a mascot.
But sometimes, for some reason, interviewers specifically want to “test your soft skills” separately. That usually means one of two things:
As you can see, either way it's a bit of a lottery.
Figuring out who's sitting across from you and answering accordingly is a skill that comes with experience. Interviews are a game. Knowing how to play it is a soft skill too :)
Again, it all depends on your goals.
At those coveted FAANG companies, you'll most likely get the first kind, so get ready to do the whole “look how friendly and communicative I am” song and dance for a bored Indian guy on the other end of the call. Well, that's why they pay $300 million a second. You want the cash, be ready to dance.

At startups it's the other way around: give them a bunch of hesitant “well, it depends” answers and they'll definitely get back to you. Say “that's bullshit, fuck that” and they'll send you an offer.
As a team lead who interviews close to 50 people a year, I've personally hired both kinds. It always depended on the team. I don't see this in black and white. There are different projects and different people, and they either work well together or they don't.
So stop beating yourself up if you didn't get the job.
I can guarantee you, if they'd hired you, chances are you'd have burned to a crisp within a few months because the project wasn't a fit, and turned into one of those disgruntled techies on Twitter with a thousand followers.
So it's all for the best!