🎯 Tech Dimensions
Evaluate technical engineers across 7 key dimensions
👤 Engineer Information
Junior Engineer
Needs code review to catch issues. Focuses on local scope.
Mid-Level Engineer
Writes clean, efficient code with few bugs. Thinks about edge cases.
Senior Engineer
Writes resilient, extensible code. Refactors systems proactively.
Junior Engineer
Can follow a design and build components.
Mid-Level Engineer
Designs new features within existing systems. Understands trade-offs.
Senior Engineer
Designs systems from scratch. Balances long-term needs.
Junior Engineer
Communicates basic blockers, asks for help.
Mid-Level Engineer
Gives thoughtful code reviews. Communicates clearly.
Senior Engineer
Builds consensus, defuses conflict, improves team dynamics.
Junior Engineer
Owns small tasks. May need reminders to follow up.
Mid-Level Engineer
Owns features end-to-end. Takes responsibility for quality.
Senior Engineer
Owns complex systems. Makes hard calls, handles ambiguity.
Junior Engineer
Focuses on building what's asked. Limited product context.
Mid-Level Engineer
Understands user needs. Suggests small UX improvements.
Senior Engineer
Anticipates product risks. Balances technical and business goals.
Junior Engineer
Learns from others, receives feedback well.
Mid-Level Engineer
Shares knowledge. Mentors juniors informally.
Senior Engineer
Coaches others consistently. Creates learning opportunities.
Junior Engineer
Completes defined tasks reliably. Limited wider impact.
Mid-Level Engineer
Unblocks teammates. Improves team performance or process.
Senior Engineer
Multiplies team output. Influences roadmaps and strategy.