Your Soft Skills Are Part of the Job, Not a Side Quest
Knowing when to escalate, how to speak up, and how to explain your work to non-engineers can matter as much as your code, and you have to build those skills on purpose.
Most engineers I know got good at code first and figured the rest would sort itself out. It doesn't. Past a certain point, what holds you back is rarely your technical ability. It's how you work with people.
Here's the idea I keep coming back to: personal growth and engineering growth are the same project. You can't be the solid engineer who solves everything alone, because you work on a team, and that team works with other teams. Every project runs through a web of handoffs, disagreements, and decisions made in real time.
Technical skill gets you in the room. Interpersonal skill keeps you there.
Think about the moments that actually shape your work:
- Knowing when to escalate a problem and when to handle it yourself
- Speaking up when a plan has a hole in it, even if the room is quiet
- Raising a concern without making it sound like an accusation
- Explaining a tradeoff to a product manager or an executive who doesn't read code
- Staying steady when something breaks at 4 p.m. on a Friday
None of these show up in a tutorial. Nobody teaches them in a sprint planning meeting, either. You pick them up by paying attention, by making mistakes, or by learning from someone who's already good at them.
Know yourself and the people you work with
The common thread is self-awareness plus an understanding of the people around you. Ask yourself:
- What am I good at outside of the code?
- Where do I freeze, dodge, or over-explain?
- Who on my team do I need to build trust with, and what do they care about?
- How does my day-to-day work connect to what the team is trying to achieve?
That last question is the subtle one. When you can draw a straight line from your task to the team's goal, you start making better calls about what to escalate, what to push back on, and what to drop.
Make the skills visible
Doing good work quietly isn't enough. Write it down. Keep a running doc of problems you pushed through, concerns you raised and how they were resolved, and results you delivered under pressure. You're not doing this to brag. You're doing it so you and your team can see that you're capable and reliable, and so you have real evidence when it's time for a review, a promotion, or a new role.
Build a system, then keep refining it
Once you know your strengths and gaps, you can work on them deliberately. Pick one area to grow this month, such as writing clearer status updates or asking for feedback after design reviews. Then set up a small routine to practice it and check how it's going. Adjust as you learn more. This turns growth from something that happens to you into something you run on purpose.
The more you grow in one area, the easier it gets to grow in the others. Technical skill, communication, and self-awareness feed each other.
The takeaway
If you're early in your career, don't wait until you feel "ready" to work on the non-technical side. Start with one concrete habit this week: raise one concern in a meeting, explain one of your decisions to someone outside engineering, or write down one thing you solved under pressure. These skills don't stop mattering as you get more senior. They're part of what makes you valuable at any stage.