Work type
The Builder
You're happiest when something exists at the end of the day that didn't exist in the morning. You learn by making, and abstract debate without a prototype drains you.
What this work type really means
Builders think with their hands. You understand a problem properly only once you've tried a crude version of the solution, which is why reading three more articles about a framework feels worse to you than simply installing it and breaking something.
The trap for Builders early in a career is joining an organisation that mistakes documentation for progress. Look for teams where a graduate is expected to have committed, shipped or fixed something in the first fortnight — that expectation is the clearest signal you'll be able to learn at your natural pace.
The strongest Builders eventually pair their making with one other strength: analysis, design taste, or coordination. If your quiz runner-up was the Analyst you'll drift towards systems and infrastructure; if it was the Maker, towards product engineering where craft is visible to users.
Where you'll do your best work
- Small teams that ship often rather than plan for a quarter
- Clear ownership of a component or system
- Mentors who review your work honestly
What tends to drain you
- Long planning cycles where nothing gets made
- Approval chains between you and a working version
- Roles measured on meetings attended rather than output
Graduate roles and internships to explore
Common European entry points for this work type. Titles vary by country — search the shape of the work, not the exact wording.
- Software engineering internship / graduate programme
- Junior full-stack or backend developer
- Hardware, robotics or embedded engineering trainee
- Technical support engineer (as a route into engineering)
The other four work types
Not sure this is you?
The free 12-question quiz takes three minutes and no sign-up. Pathfinder's deeper discovery interview then matches you against live listings instead of generic job titles.