Technical Career Path Evaluator

Self-scoring framework to triangulate your best-fit role based on cognition, energy, and satisfaction.

Identity Snapshot

Your name

What type of problem gives you energy rather than drains it?

When you’re in flow, what are you usually doing?

Which parts of engineering work feel like chores vs crafts?

What kind of compliments from others actually feel accurate?

Which types of failure frustrate you most (bugs, miscommunication, unclear goals, missed opportunity)?

Apply identity insights to your score

Use the optional LLM-assisted review when you want your narrative answers to influence the overall cluster scores.

A short summary of your inputs is sent to the identity analysis backend you control.
The service returns cluster weight deltas (−3 to +3), notable traits, and a brief justification.
Accepted insights are applied immediately to the evaluation; you can undo them anytime.

We do not persist data in the browser after the request completes.

Tip: Results are directional. Prioritize the work that reliably puts you in flow and produces measurable impact.

Cognitive Style Inventory

1 = Never3 = Sometimes5 = Always

Statement

Score

I visualize systems as diagrams before I code.

Cluster: Solution/Systems Architect

I prefer refining interfaces and interaction patterns to optimizing runtime.

Cluster: Design Technologist / Product Engineer

I care more about how users feel than what the stack looks like.

Cluster: Design Technologist / Product Engineer

I like abstracting messy systems into coherent models or contracts.

Cluster: Solution/Systems Architect

I enjoy debugging complex state more than brainstorming product ideas.

Cluster: Engineer / Specialist

I instinctively consider scalability and maintainability in every decision.

Cluster: Solution/Systems Architect

I get restless if there’s no visual or tangible output from my work.

Cluster: Design Technologist / Product Engineer

I often mediate between designers, engineers, and PMs to align language.

Cluster: Design Technologist / Product Engineer

I find joy in creating frameworks or templates that others use.

Cluster: Platform / Framework Builder

I’d rather improve reliability and performance than add new features.

Cluster: Engineer / Specialist

Tip: Results are directional. Prioritize the work that reliably puts you in flow and produces measurable impact.

Capability Reality Check

I can explain systems to non-engineers in plain language. (Solution/Systems Architect)

I refactor code I didn’t write with confidence. (Engineer / Specialist)

I define measurable outcomes for a design or product concept. (Design Technologist / Product Engineer)

I’ve built tools that other teams adopted. (Platform / Framework Builder)

I mentor others on architecture, design systems, or automation. (Solution/Systems Architect)

Tip: Results are directional. Prioritize the work that reliably puts you in flow and produces measurable impact.

Role Excitement (Gut Check)

Slide 1–5 based on how excited you feel making this your core identity.

Frontend / UI Engineer

Full-Stack Engineer

Solution / Systems Architect

Design Technologist

Product Engineer / Creative Technologist

ML / AI Engineer

Results & Interpretation

Solution/Systems ArchitectDesign Technologist / Product EngineerEngineer / SpecialistPlatform / Framework Builder

Alignment by cluster

Solution/Systems Architect11.0 pts

Design Technologist / Product Engineer17.0 pts

Engineer / Specialist8.0 pts

Platform / Framework Builder5.0 pts

Top alignment:

Design Technologist / Product Engineer • 17.0 ptsRunner-up: Solution/Systems Architect • 11.0 pts

What this suggests

Signature strength: Translating between design, product, and engineering; rapid prototyping.

Common pitfall: Feeling like a generalist without a home when rigor or scale dominates.

Try this next: Ship a coded prototype with usability metrics; document the decision trail succinctly.

Your secondary alignment hints at a hybrid niche. Consider roles/projects blending these patterns.

Suggested Next Actions (1-week experiments)

Prototype a micro-interaction or Figma-to-code bridge and capture usability metrics.
Ship a coded demo that communicates a product bet; document tradeoffs in plain language.
Pair with a designer and a PM to validate a workflow with 5 users; summarize insights.

Built for rapid self-reflection. Adjust items to your context; repeat quarterly and track deltas.