I Built a Developer Personality Test (because why not)

I Built a Developer Personality Test (because why not)

Built a fun psychological assessment that tells you what kind of developer brain you have - not your skills, but your actual personality and work style.

โ€ข By Ehsan Pourhadi โ€ข
Projects Frontend

Soโ€ฆ I built a thing. Itโ€™s called Developer Type Assessment and it tells you what kind of developer brain you have ๐Ÿง ๐Ÿ’ป

Not โ€œare you good at algorithmsโ€ (pls no), but more like:

  • do you ship fast or overthink everything
  • do you love clean code or just want it to work
  • do you debug like a detective or YOLO your way through bugs

๐Ÿ‘‰ You can try it here: https://ehsanpo.github.io/developertype/

I honestly started this as a โ€œfun weekend projectโ€ and then suddenly I was deep into psychology, scoring algorithms, and arguing with myself about color contrast at midnight. Classic.


The Idea (aka: what was I thinking?)

I didnโ€™t want a skills test. No quizzes like โ€œwhat does this JavaScript output?โ€ (trauma ๐Ÿ˜ญ).

I wanted something more psychological. Something that feels like real dev life.

Every question forces a trade-off:

  • ship fast vs build it right
  • explore vs maintain
  • solo grinding vs team collaboration

Your answers slowly pull you toward one of 12 developer archetypes like:

  • The Ship It ๐Ÿš€
  • The Detective ๐Ÿ•ต๏ธ
  • The Craftsman ๐Ÿ› ๏ธ
  • (yes, Architecture Astronaut is there too ๐Ÿ‘€)

No โ€œrightโ€ answers. Just vibes.

๐Ÿ’ก Inspiration

This assessment was inspired by the article The 12 Developer Mindsets Iโ€™ve Seen in My Career by @notadevbuthere. The archetypes and core concepts are based on real developer behaviors and patterns observed in software teams.


The Stack (kept it simple, promise)

I didnโ€™t want backend drama. No auth. No DB. No servers. Just frontend fun.

  • React + Vite โ€“ fast, clean, no pain
  • React Router โ€“ with HashRouter because GitHub Pages ๐Ÿ˜…
  • Pure CSS โ€“ no Tailwind, no frameworks, just vibes and CSS variables
  • html2canvas โ€“ for downloading results as images (this was surprisingly fun)

Thatโ€™s it. No magic. No enterprise nonsense.


Cool Stuff Iโ€™m Proud Of โœจ

๐Ÿง  Smart-ish Scoring

Each answer gives weighted points to multiple archetypes.

So youโ€™re not just โ€œone thingโ€. The algorithm can notice stuff like:

โ€œhuh, this person scores high in Ship It AND Craftsmanโ€ฆ interesting tension ๐Ÿ‘€โ€

It actually felt like teaching the app to understand personalities. Kinda creepy. Kinda cool.


๐Ÿ”— Shareable Results & Download

Results are encoded into the URL using base64. No backend needed โ€“ just pure frontend magic โœจ

Which means:

  • share the link and anyone can see your result
  • no retaking the test
  • no database, no servers, my wallet is happy
  • download your result as a PNG
  • share directly to LinkedIn (yes, devs love this stuff)

Encoding state into the URL turned out to be insanely powerful. Sharing just worksโ„ข and I wanted it to feel like an achievement unlock ๐ŸŽ–๏ธ, not just text on a screen.


The Questions (harder than coding tbh)

20 questions. 4 answers each.

This part took the longest.

Each answer had to:

  • feel real
  • map clearly to personality traits
  • not scream โ€œTHIS IS THE CORRECT ANSWERโ€ ๐Ÿ™ƒ

Example question:

You find a messy file that somehow works. What do you do?

  • Rewrite it from scratch (perfectionist)
  • Ship features and move on (pragmatic)
  • Understand why it works first (detective)
  • Refactor slowly over time (balanced dev)

If you read that and felt personally attackedโ€ฆ good ๐Ÿ˜ˆ


Things I Learned (aka: bugs taught me stuff)

๐Ÿ”‘ React keys REALLY matter

I had a weird bug where answers from one question leaked into another.

Turns out:

key={answer.id}

was NOT enough.

Fix:

key={`${question.id}-${answer.id}`}

React stopped gaslighting me immediately.


โฑ๏ธ Tiny delays = better UX

That 300ms pause after clicking an answer?

Remove it and the app feels broken. Add it and suddenly everything feels intentional.

UX is wild.


Stats (because devs love numbers)

  • 20 questions
  • 12 archetypes
  • ~5 minutes
  • 0 backend servers
  • Hosted on GitHub Pages
  • Built in 2 hours

Try It ๐Ÿ‘‡

๐Ÿ‘‰ Take the test: https://ehsanpo.github.io/developertype/

๐Ÿ‘‰ Open source on GitHub: https://github.com/ehsanpo/developertype

If you try it, tell me what type you got ๐Ÿ‘€ And if you read this farโ€ฆ wow. Youโ€™re definitely not โ€œThe Ship Itโ€ ๐Ÿ˜…

Built for fun. Learned a ton. Highly recommend building weird little projects like this.

Now excuse me while I add one more feature that I definitely donโ€™t need. ๐Ÿš€

Developer Type Assessment Screenshot

Tags: #React #Vite #UX #Side Projects
TreeStone
Running cat