← Career path / skill treeA-2 · artifact
Engineer Skill Map
A taxonomy of software engineering skills, organized by category. Supporting evidence for “There is a finite set of skills relative to Engineering Careers.”
Craft§01
Micro hard skills — day-to-day execution at the keyboard.
MVPing
Knowing how to scope and deliver a minimum viable product — resisting the urge to over-engineer and shipping something real that can be learned from.
Time Management
Managing your own time across competing priorities — knowing when to focus, when to context-switch, and when to block off deep work.
Knowing What's Important
Cutting through noise to identify the work that actually moves the needle. The ability to say this matters and that doesn't with clarity.
Knowledge Boundaries
Understanding the edges of what you know — and being honest about them. The skill of knowing when to dig in vs. when to ask.
Knowing Your Limits
Self-awareness about cognitive, emotional, and technical capacity. Not burning out, not over-committing, not pretending you're fine when you're not.
Deep Diver
The ability to go very deep on a problem — to follow threads until you truly understand the root cause or the full system behavior.
Closer
Finishing what you started. Bringing things across the finish line even when momentum drops or the hard 20% remains after the fun 80% is done.
Save the Day
Stepping up in a crisis — debugging a production incident, unblocking a team, or doing the unglamorous thing that needs doing right now.
Knowledge Battery
Actively building and maintaining a personal store of knowledge — reading, experimenting, staying curious — so you have something to draw from.
Depth vs Breadth
Consciously deciding when to go deep on a domain vs. when to stay broad. Knowing your own shape as an engineer and building it intentionally.
Value of Maintenance & DX
Understanding that the real cost of software is in maintaining it. Valuing clean code, good tooling, and great developer experience as first-class concerns.
Architecture§02
Macro hard skills — system-level thinking and big-picture decisions.
Making Decisions Well
Gathering the right information, weighing tradeoffs clearly, and committing decisively. Avoiding both analysis paralysis and reckless speed.
Forest and the Trees
Holding both the high-level architecture and the low-level details in mind at once. Knowing when to zoom in and when to zoom out.
Orchestration
Coordinating multiple systems, services, or people to work together toward a coherent outcome. Getting things to move in formation.
Pre-Crime
Anticipating problems before they happen. The experienced engineer's ability to see the failure mode in the design before any code is written.
Letting People Learn & Make Mistakes
Knowing when to step in and when to let someone struggle productively. Balancing team growth against project risk with wisdom and patience.
Teamwork§03
Micro soft skills — pod-level collaboration and communication.
Playing Strengths
Identifying what each person on your team is genuinely great at, and structuring work so those strengths shine rather than get buried.
Pod Collaboration
Working well in a small, tight unit. Shared context, rapid feedback loops, covering for each other, and building team trust at close range.
Good Cop / Bad Cop
Understanding the dynamics of how teams negotiate and push back. Knowing when to be the one who says the hard thing and when to soften it.
Letting Go / Delegating
Releasing control of work you could do yourself so others can grow into it. Trusting people with real responsibility rather than just tasks.
Orchestration
At the team level: getting people moving together, aligned on goals, with clear ownership and no gaps falling between the cracks.
Leadership§04
Macro soft skills — org navigation and influence at scale.
Controlling the Narrative
Shaping how your work, your team, and your decisions are perceived across the organization. Proactive communication rather than reactive damage control.
Guiding the Narrative
Influencing how a story unfolds without forcing it — building consensus, bringing people along, making the right outcome feel inevitable.
Herding Cats
Getting opinionated, autonomous people to move in a shared direction. Requires patience, humor, and knowing which battles are worth fighting.
Strong Opinions Weakly Held
Having a clear point of view — and being genuinely willing to change it when better information arrives. Not wishy-washy but not rigid either.
Culture Battery
Knowing how much of your own energy a company's culture charges vs. drains. Reading the culture clearly and deciding consciously whether it's a fit.
Leveraging Network
Building and using a professional network with intention — not just collecting contacts but creating real mutual value and knowing who to call.
War-Time General
Leading when things are broken, urgent, or on fire. Decisiveness, clarity, and calm under pressure. Moving fast without creating more chaos.
Peace-Time General
Leading when things are stable — building systems, developing people, setting vision, and preparing the organization for the next war before it comes.
Changing the Flow of a Raging River
The hardest leadership skill: shifting organizational momentum, entrenched processes, or broken culture. Gradual, persistent, and strategic.
Champion
Actively advocating for people, ideas, or initiatives that deserve more support. Being the one who uses their credibility to amplify others.
Defender
Protecting your team, your decisions, or your people when they're under pressure or unfair criticism from outside forces.
Managing Expectations
Setting clear, honest expectations with stakeholders about what will be done, when, and why — before they have to ask.
Know Your Audience
Reading the room. Adapting your communication — technical depth, tone, framing — to the specific people in front of you.
Professionalism§05
Hard-soft blend — ownership, judgment, doing what needs doing.
Researching Before Saying Yes or No
Never giving a gut answer to an important question. Taking time to actually investigate before committing — and setting that expectation with stakeholders.
Tech Comms for Non-Tech
Translating complex technical concepts into language that non-engineers can understand and act on — without dumbing it down or losing the nuance.
Aligning Technical Vocab with Business Vocab
Finding the words that mean something to both engineers and business stakeholders. The translator role between two languages.
Doing What No One Else Will Do
Picking up the unglamorous, avoided, thankless work that has to happen for everything else to work. Ownership over not my job mentality.
Doing What Makes Things Better
The proactive impulse to improve things — processes, code, culture, documentation — even when no one asked and there's no ticket for it.