QCon San Francisco begins tomorrow, and I’m speaking on Wednesday! Preparing for this and my LDX3 talk gave me a rare opportunity to reflect on my own engineering career.
How did I grow from an engineer navigating unfamiliar technologies and inherited systems into someone trusted to make engineering-wide architectural decisions requiring deeper technical judgment?
Two conversations from earlier in my career came to mind.
Accumulating technical experience vs. developing technical intuition
Early in my career, I remember talking with a VP of Engineering while I was learning Ansible and several other technologies at our small startup.
I asked him how I was supposed to learn and remember everything when every technology introduced its own vocabulary, configuration, architecture, and conventions.
He explained that technologies are often cyclical. Once you understand the underlying principles, you begin seeing the same ideas expressed in different ways.
Consider two web application frameworks: Spring Boot in Java and FastAPI in Python. Both address familiar concerns such as API routing, dependency management, configuration, and error handling, even though their implementations differ.
Seeing the patterns beneath the technology
Once you’re familiar with concepts like API routing and dependency management, learning a new framework becomes largely a matter of understanding its specific conventions, capabilities, and tradeoffs.
The ability to recognize underlying patterns and apply that understanding to unfamiliar technologies is what I mean by technical intuition.
The more patterns we recognize across technologies and update our mental map, the less we need to relearn from scratch.
Developing technical intuition is one dimension of engineering growth. Another important dimension is developing technical judgment.
Are we simply accumulating experience through successive projects, or building a deeper understanding of the decisions and tradeoffs that shape them?
Why years of experience don’t automatically translate into growth
Another conversation from my engineering career was much less comfortable.
Frustrated with the pace of my career growth, I pointed out to my manager how many years I’d already spent in software engineering. Surely that experience should count for something when evaluating my readiness for advancement.
She challenged that assumption: The number of years I’d worked wasn’t particularly useful on its own.
At the time, her answer felt dismissive of the effort I’d invested and the challenges I’d navigated.
Looking back, I realize she was challenging my assumption that years of hard work and successful delivery automatically demonstrated readiness for greater responsibility.
What she was looking for was evidence of the judgment I’d developed from that experience.
So how do we develop that judgment in our everyday engineering work?
Learning to zoom out
It’s surprisingly easy to move from one project to the next, focusing on designing, implementing, and shipping, without ever zooming out to see the bigger picture.
We continue to gain hands-on technical experience but may miss the reasoning behind project priorities, important tradeoffs, and decisions that shaped execution. We may never learn how the work ultimately performed or what we could have done differently.
Over time, these missed opportunities limit how much judgment we develop from our experience.
One way to learn more deliberately is to examine each project across three stages: before, during, and after.
Before: Understand why the work exists
Before getting immersed in implementation, become curious about the decisions that brought the project into existence.
Why was this work prioritized now? What changed in the business or technology landscape? What alternatives were considered? And why was your team chosen to own it?
These questions reveal how organizations evaluate opportunities, allocate resources, and navigate competing priorities.
For example, a technically overdue migration may have remained on the backlog for years because its benefits didn’t justify the disruption. Changing customer needs, infrastructure costs, or business priorities might finally make it worthwhile.
Understanding that history teaches you something about prioritization that implementing the migration simply cannot.
During: Study the decisions shaping execution
Once the project is in motion, pause periodically to pay attention to decisions beyond the architecture and code.
Why were milestones sequenced a certain way? Which risks were prioritized or deferred? What shaped decisions about delegation, ownership, and technical tradeoffs?
For example, your tech lead may have prioritized a data backfill before building user-facing features. What looked like a slow start may have been a deliberate effort to uncover data-quality and migration risks before committing to a launch date.
You don’t need to make every decision to learn from it. Ask your tech lead, manager, or other stakeholders about the reasoning behind their choices, especially if you would have approached things differently.
These conversations can reveal constraints you hadn’t considered and deepen your understanding of how technical decisions are shaped by organizational and business needs.
After: Learn what the work actually accomplished
Shipping is an important milestone, but it rarely tells the full story.
Did the project achieve its intended outcomes? Was adoption as expected? What became easier or harder than anticipated?
Perhaps an API you designed was technically robust but difficult for other teams to adopt. Or an infrastructure improvement eliminated one bottleneck while introducing an unexpected maintenance burden.
Revisit your original assumptions. What held up, what surprised you, and what would you approach differently next time?
Most importantly, what lessons will you carry into future projects?
What changes as you grow toward Staff and Principal?
At Staff and Principal, you’re trusted with increasingly ambiguous, consequential problems, often in systems you didn’t build.
This is where technical intuition and technical judgment reinforce each other. Intuition helps us recognize patterns and navigate unfamiliar systems, while judgment enables us to evaluate tradeoffs, anticipate consequences, and make sound decisions under uncertainty.
In my coaching practice, I’ve worked with engineers who progressed from coding bootcamp to Staff Engineer in eight years, and others with twenty years of experience who were still developing some of the judgment required at Staff level.
Of course, career progression also depends on opportunity, sponsorship, timing, and organizational expectations. But across different career trajectories, I’ve noticed one recurring difference in how engineers learn from their experiences.
Ten years of deliberately learning from engineering experience builds judgment that ten years of repeating the same way of working rarely does.
Looking back, I better understand my manager’s point. My years of hard work were valuable, but what would show I was ready for more was how those experiences had strengthened my judgment and ability to navigate increasingly complex decisions involving technology, people, and the business.