Your colleagues are happy ticking Jira tickets and clocking out at 5 PM. Nothing wrong with that. Valid choice.
But when your ambition outpaces your environment, the friction gets exhausting unless you have a strategy.
Build Your Own Career Pyramid
Steve McConnell's1 career pyramid idea: define what you're building toward, or your current environment becomes your ceiling.
Know what you want. What skills? What impact? What's the long-term goal? A clear vision provides sustained motivation when the day-to-day feels like a treadmill.
Pick projects that compound. Avoid "lily pad hopping" - jumping between disconnected tasks with no cumulative value. Each project should build on the last.
| Approach | Result After 2 Years |
|---|---|
| Lily pad hopping | Broad but shallow, no clear expertise |
| Pyramid building | Deep capability in 2-3 areas, clear trajectory |
The engineers who advance have clear narratives about depth. The ones who hop have lists. Lists don't get you to senior.
Create Your Own Opportunities
When opportunities aren't handed to you, make them.
Fill the gaps. Look for unresolved problems or places where new tech could help. Step up. The projects nobody wants are often the ones that teach you the most.
Keep learning. Dedicate time to structured learning outside work. Courses, reading, meetups. Expands your value, opens new paths.
Find mentors. Inside and outside your org. Some of the most valuable career conversations happen with people outside your immediate peer group. They see things your colleagues don't.
Creating opportunities looks quieter than the LinkedIn version. It's not about starting a side project that gets 10,000 GitHub stars. It's noticing something broken, fixing it, and making sure the right people see it.
Influence Without Preaching
Your attitude can spark curiosity without direct persuasion.
Ship good work consistently. Share interesting articles. Show genuine enthusiasm. Quiet engineers start asking questions after seeing someone else ship something genuinely useful.
Offer help collaboratively. See a colleague struggling? Spot a process that could improve? Offer support without being judgmental. Builds goodwill, gradually shifts culture.
One person raising their ambition changes the room's energy more than you'd expect. But this only works if the organisation has any appetite for improvement. Sometimes the walls are too thick.
Know When to Leave
Sometimes the culture is fundamentally indifferent to growth. Talented engineers waste years trying to change cultures that were never going to change.
The signals aren't subtle:
- Promotion criteria are opaque and always favour the same people
- Your manager changes every six months and nobody remembers your goals
- "We've always done it this way" - not because the old way is good, but because change is effort
- Senior engineers are coasting and the organisation rewards tenure over impact
Assess honestly. Does leadership care about development? If not, you're fighting uphill. Do people get promoted for impact or for longevity? Are the senior engineers still learning, or are they curators of outdated expertise?
Find compatible culture. In interviews, ask about learning opportunities, career progression, team dynamics. Find somewhere your drive is valued.
Ask hiring managers: "Tell me about the last person on your team who grew into a more senior role. What did that path look like?" The quality of that answer tells you everything.
TIP
The 80/20 Rule for Career Growth Focus on the 20% of activities yielding 80% of your growth. High-impact learning, strategic networking, challenging projects. Not routine tasks.
Summary
- Define your career pyramid. Know what you're building toward.
- Create your own opportunities. Don't wait for growth to be handed to you.
- Avoid lily pad hopping. Choose projects that compound.
- Influence through shipping. Not preaching.
- Know when to leave. Some cultures can't be changed from within.
What's Next
Next time you feel your environment limiting you, ask: am I waiting for permission, or creating my own momentum? That difference determines whether you stagnate or accelerate.
Footnotes
Steve McConnell - author of Code Complete and the career pyramid framing used throughout this post. ↩