The 4 Non-Technical Skills That Actually Made Me Better at My Job

When I started at my company two years ago, I thought leveling up meant grinding LeetCode and learning the latest framework. Turns out, the engineers I actually wanted to be like weren't the smartest coders in the room—they were the ones people wanted to work with and trusted to solve real problems.

I've picked up four concrete skills that changed how I move through my job. None of them are technical. All of them matter more than you'd think.

1. Stop Complaining, Start Learning

Early on, I'd catch myself thinking why is this happening to me? when something went wrong. A deploy failed. A code review was brutal. I got assigned a legacy system nobody wanted to touch.

I realized that mindset was a trap. Now when something sucks, I deliberately reframe it: What can I learn from this? It's not toxic positivity—it's pragmatic. Staying optimistic about a situation doesn't make the problem disappear, but it keeps me functional and pointed forward instead of spiraling.

This matters because you're going to spend months or years at a company. Your attitude determines whether you're miserable the whole time or whether you actually extract value from being there.

2. Be Coachable (Get Out of Your Own Way)

I used to think asking for help meant admitting I wasn't good enough. So I'd stay quiet and try to figure things out alone, which just meant I stayed confused longer.

The shift: when someone teaches me something—whether it's a code review, architecture decision, or how the business actually works—I show up with zero ego. I don't pretend I know things I don't. I listen like I have no prior knowledge.

This unlocked so much. Senior people on my team started actually investing in me because I wasn't defensive or performing competence I didn't have yet.

3. Ask Questions (The Right Kind)

I was scared to ask questions because I thought it made me look weak. The reality is the opposite: not asking questions is how you stay confused and slow down the team.

But the type of question matters. Asking "how do I do this?" is fine. Asking "why are we doing this?" is better. "Why does this matter to the business?" is even better. "Is there room to improve or automate this?" is the kind of question that gets you noticed.

Questions aren't weakness. They're how you understand the full picture instead of just executing tasks.

4. Develop Emotional Intelligence (Read the Room)

This one took me the longest to understand. Emotional intelligence is about knowing how you come across, reading what other people actually need in a moment, and understanding the business context underneath the technical problem.

When a meeting gets tense, some people stay neutral or go negative. Others stay collaborative and optimistic. That difference—that presence—changes outcomes. It's not fake. It's about showing up with the right energy for what the team actually needs.

I picked this up partly from being around people older than me and watching how they handled situations. I'd absorb what worked, notice what didn't, and integrate the habits that felt genuine.

The Pattern

Two years in, I see the real gatekeepers to growth aren't coding skills. They're attitude, humility, curiosity, and presence. Those four things compound.

You can learn any tech stack if you're coachable and ask good questions. You can survive a brutal environment if you stay optimistic and grounded. You can become someone people actually want on their team if you bring good energy and understand context.

The engineers I want to be like aren't running the fastest—they're the ones people trust and want to work with. That's earned through these skills, not GitHub commits.