Why I Ditched Terminal UIs for Recruiters
Source: Dev.to
Background
I built a terminal‑style portfolio: a black screen with commands and ASCII vibes. It felt very me.
The Recruiter Feedback
Almost everyone said the same thing:
“This is cool… but recruiters won’t get it.”
They were right.
- Terminal portfolios are fun for developers.
- They showcase technical skill, confidence, and a willingness to bend conventions.
But recruiters don’t explore; they skim. They need to know:
- Who are you?
- What do you build?
- Can I understand this in 10 seconds?
A blinking cursor asking them to type help already lost half the room. The UI wasn’t failing because it was bad—it required participation, which recruiters aren’t inclined to give.
The Pivot
When it clicked, I treated the portfolio as a signal amplifier and rebuilt it with these principles:
- UI‑first design
- Motion‑driven elements for visual interest
- Immediately readable content
- Big typography for quick scanning
The personality stayed the same; only the delivery changed.
Outcome
The irony is that after simplifying the experience, the cool ideas still shone through. A portfolio is not for you—it’s for your audience. You can be creative without being cryptic.
I didn’t abandon the terminal UI concept; I just made it more responsible and recruiter‑friendly.
See the pivot in action
👉
Fair warning: I still overengineered it, just more responsibly this time.