Common Pitfalls on the Path to Senior Engineer and How to Avoid Them

After working with and observing dozens of engineers making the transition to senior, certain patterns emerge. Here are the most common pitfalls — and how to avoid them.

Pitfall 1: Waiting to Be Told What to Do

The problem: You excel at executing assigned tasks, but you never initiate. You wait for tickets, for your manager to assign work, for someone else to identify the problem. This is the opposite of senior-level behaviour.

Why it happens: You’re comfortable being a reliable executor. You’ve been praised for it. It feels safe to work on clearly defined tasks.

The fix: Start identifying problems yourself. Look at your team’s backlog, the production dashboards, the onboarding experience. Find something that’s broken, slow, or confusing — and propose a fix. You don’t need permission to improve things.

Pitfall 2: Optimising for Code Quality Over Impact

The problem: You spend weeks refactoring a module that works fine because “the code isn’t clean.” Meanwhile, a critical feature that would unblock your team is delayed.

Why it happens: Code quality is tangible. You can see the improvement. Impact is messier and requires understanding business context.

The fix: Ask yourself: “If I spend this week on X instead of Y, what changes for the user or the team?” Not everything that matters is clean code. Sometimes the right thing to do is ship something imperfect that delivers value — and make it cleaner later.

Pitfall 3: Going Deep But Not Wide

The problem: You’re an expert in one area — your team’s service, a specific framework, a particular domain. But you have no idea how the rest of the system works, how deployment happens, or how the product makes money.

Why it happens: Deep expertise is easier to develop and more immediately rewarded. Breadth takes deliberate effort.

The fix: Spend time outside your area. Read design docs from other teams. Shadow the on-call rotation for a service you don’t own. Attend product reviews. The senior engineer who only knows their own service is not yet senior.

Pitfall 4: Avoiding Hard Conversations

The problem: You see a design that’s fundamentally flawed, a timeline that’s unrealistic, or a team dynamic that’s broken — but you don’t say anything. You assume someone else will raise it, or you don’t want to be difficult.

Why it happens: Conflict is uncomfortable. Speaking up feels risky, especially if you’re the most junior person in the room.

The fix: Frame hard conversations as shared problem-solving. “I’m concerned about this approach because X. Can we talk through it?” Most people will thank you for raising the concern. The ones who don’t are probably missing important context — which is another sign you should speak up.

Pitfall 5: Doing the Work of Two People Instead of Teaching

The problem: You’re fast. When a junior engineer is struggling, it’s faster to do it yourself than to explain it. When the team needs something done quickly, you volunteer because you know you can deliver.

Why it happens: It feels productive. You’re shipping, you’re helping, you’re being a team player.

The fix: This is a trap. Every time you do someone else’s work, you lose an opportunity to teach. In the short term, you deliver faster. In the long term, you’re a bottleneck. Teach instead. Spend the extra hour walking through the solution. Write the documentation. Create the pattern that others can follow. Your leverage comes from multiplying, not doing.

Pitfall 6: Neglecting Visibility

The problem: You do great work, but nobody outside your team knows about it. When promotion time comes, your manager struggles to build a compelling case because your impact isn’t visible to the committee.

Why it happens: You believe good work speaks for itself. It doesn’t — especially at larger companies where the promotion committee doesn’t work with you directly.

The fix: Visibility is not self-promotion — it’s part of your job. Present your work. Write design docs that others reference. Share learnings in Slack channels. The best work that nobody knows about has less impact than good work that everyone understands.

Pitfall 7: Burning Out on the Path

The problem: You’re working nights and weekends. You’re taking on every project. You’re stressing about the promotion timeline. You’re comparing yourself to peers who got promoted faster.

Why it happens: The path to senior can feel urgent. You want it, you’ve been working toward it, and every month that passes without it feels like failure.

The fix: Sustainable pace beats sprinting every time. Block out time for rest, learning, and thinking. The promotion will come when you’re ready — and running yourself ragged doesn’t make you ready faster. It just makes the journey miserable.

The Common Thread

Almost every pitfall comes down to the same root cause: acting like an individual contributor who wants to be senior, rather than acting like a senior engineer from today.

You don’t earn the title first and then start behaving differently. You start behaving differently, and eventually the title catches up.

Key Takeaways

• Don’t wait for direction — find problems and fix them
• Optimise for impact, not just code quality
• Build breadth alongside depth
• Speak up, even when it’s uncomfortable
• Teach instead of doing
• Make your impact visible
• Maintain a sustainable pace