Most developers focus on mastering algorithms, frameworks, and technical problem-solving. But the real difference between a good engineer and a great one? Soft skills.

It’s not just about writing code. Anyone can write code, most developers can write good clean code, but very few can communicate ideas clearly, work with teams, handle conflict, and influence decisions.

Here’s why I think soft skills get ignored in tech:  

– They’re hard to measure. (Spoiler: You can’t put “great communicator” in a pull request)

– They don’t feel urgent. Learning a new framework feels more productive than improving how you give feedback.

– They take time to develop. Unlike coding, where you see results instantly, soft skills require practice and patience.

These soft skills will set you apart:

1. Clear Communication

You can be the smartest engineer in the room, but if you can’t explain your ideas, no one will listen. Whether you’re writing documentation, presenting solutions, or just asking for help, clarity is everything.

• Use simple language. If a non-tech person wouldn’t understand, rewrite it.
• Avoid jargon unless necessary. Clarity beats complexity.
• Practice writing, concise messages prevent confusion.

2. Giving and Receiving Feedback

Good engineers take feedback well. Great engineers seek it out.

• When receiving feedback, listen first. Ask clarifying questions before responding.
• When giving feedback, be direct but constructive. Focus on the work, not the person, and you’ll be just fine 🙂
• Normalize code reviews and retrospectives as learning opportunities.

3. Problem-Solving Under Pressure

It’s easy to think clearly when everything is going well. But when production is down and stakeholders are waiting, your mindset matters as much as your skillset.

• Take a breath before reacting, panic makes things worse.
• Break problems into smaller parts and tackle them logically. Can’t stress this enough.
• Learn to communicate status updates calmly and confidently.

4. Negotiation & Influence

Beyond solving problems, is getting buy-in for your ideas. Whether you’re advocating for a new framework, asking for a raise, or pushing back on an unrealistic deadline, your ability to influence others matters.

• Focus on why something matters, not just what you want.
• Anticipate objections and prepare solid arguments.
• Be willing to compromise. Oh yes! Collaboration beats winning an argument.

5. Adaptability

Tech moves fast. If you’re not adaptable, you’re falling behind. Being skilled isn’t enough, you have to be willing to unlearn and relearn.

• Stay curious and treat every challenge as a learning opportunity.
• Be open to feedback and new perspectives. Be willing to unlearn
• Don’t get too attached to tools or processes. Prioritize outcomes over preferences.

A quick reality check:

These soft skills won’t replace your technical ability.
But they will amplify it.

I’ve seen it in my own journey. The moment I stopped obsessing over being “technically perfect” and started working on how I show up…

Things changed.

I got invited into more strategic conversations.
I led better.
I grew faster.

Adaptability, good communication and being a team player are the 3 key soft skills that’ve been most impactful in my career.

So where do you start?

You don’t need to overhaul your personality.
Start small. Build habits. Here’s a good place:

• Before starting work, ask: What’s the real goal here?
• After meetings, write 1 sentence summarizing what happened
• Give someone specific praise this week. Authentic and factual, not fluff or flattery praises

For example, “Great job” is fine.
But, “Your breakdown helped me understand X faster” is better.

That’s it. Micro-habits > big declarations.

Do this consistently and you’ll:

• Think clearer
• Communicate sharper
• Lead stronger

Caution: You will most likely hit the “I’m not good enough” barrier as you try to develop yourself in these areas, but do not let it stop you. That’s how it always feels in the beginning. You’re not alone. Just do it and it’ll get better eventually.

Remember, repetition is the key.
Practice. Refine. Apply.
That’s how we get better, at code, and everything else.