How I Forced shadcn UI Into Neo-Brutalism in One Night Before a Job Dating

The clock was ticking. With INTELO coming in less than 12 hours in hurry, I took a hard look at my portfolio. It was clean, but it looked exactly like every other modern developer site: sleek, dark mode, and entirely safe. And "safe" is a death sentence when you need to stand out to recruiters.

At 7:00 PM, I decided against a full rewrite. Instead, I did something more aggressive: I hijacked my existing Next.js 16 stack and completely overhauled the design system, forcing shadcn UI out of its default clean aesthetic and into a raw, high-contrast Neo-Brutalist style before sunrise.

Here is how I pulled it off in under 4 hours.

Escaping the "Generic Dev" Trap

Most developer portfolios look identical because we all use the same component libraries out of the box. While shadcn UI is incredible for accessibility and speed, its defaults feature the same smooth roundings, muted colors, and predictable layouts as everyone else's.

When a recruiter scans a hundred profiles a day, generic means invisible.

I needed my site to scream personality and rigorous execution within a three-second glance. I chose Neo-Brutalism because it rejects the polished, oversaturated trends of modern web design in favor of loud, intentional constraints:

Aggressive High Contrast: Swapping out muted grays for stark cream backgrounds paired with thick, raw black borders.
Hard Geometry: Stripping away the default large rounded corners utilities and replacing smooth drop-shadows with strict, 90-degree hard shadows.
High-Impact Information Hierarchy: Making critical achievements—like ranking 13th nationally in a solo Cyber Security CTF—pop off the screen instantly using heavy typography.

The Pivot: Instead of rewriting the backend or routing, I focused 100% of my time on overriding the Tailwind configuration and global styles to completely mask the underlying components.

The 7 PM Architecture: Bending shadcn UI

Speed and stability were the ultimate constraints. Because I didn’t have time to rebuild accessible modals, dropdowns, or buttons from scratch, utilizing my existing shadcn setup was a lifesaver. The goal was simple: keep the robust, accessible BaseUI primitives, but violently change the skin.

The next morning ? Will it stand out ?

As I write this, I haven’t walked into the INTELO yet. The doubts are absolutely there. My portfolio is no longer universally "safe"—it is loud, polarizing, and completely unbothered by mainstream design rules. Some recruiters might find it too chaotic; others might love it.

But with less than 12 hours to go, I’m betting on the risk. In a sea of identical templates, being memorable is better than being invisible. I just hope this raw, high-contrast look is enough to make a recruiter pause, click around, and hopefully help me land the perfect internship.

Final Thoughts: What This 4-Hour Sprint Taught Me

Pulling off a massive design overhaul in a single evening forced me to re-evaluate how I approach building things. When you have a hard stop at 10:00 PM, your perspective shifts instantly.

Here is the biggest takeaway from my night of bending shadcn UI:

Safe is the Riskiest Strategy of All

The biggest lesson? Don't be afraid to take a design risk. Building something that looks like every other site on the internet feels safe, but in a competitive environment like a job dating event, it’s actually a massive gamble. You are gambling that a recruiter will magically notice your generic site out of hundreds. By leaning into Neo-Brutalism, I made a conscious choice to be unforgettable.

Wish me luck tomorrow. If you're stuck overthinking your own project, drop the perfectionism, break a few design rules, and just ship it.