Engineer Skill Map
Rate your confidence in each skill (1–5). Your archetype fingerprint updates as you go.
Archetype Fingerprint
Depth Charger0%
Irreplaceable domain expert. Goes deeper than anyone else.
Mad Scientist0%
Lateral thinker. Reframes problems and sees ahead.
Operator0%
Makes organizations function. War-time and peace-time leader.
Connector0%
Multiplies people around them. Culture and relationships.
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.