Skip to main content
10 years · 21 projects

Hello, I'm Edgar Pérez

Frontend Design Engineer

Your team feels stuck. Features drag, releases break things, and nobody can explain why. I find the structural problems and organize the way forward.

Edgar Pérez, Frontend Design Engineer

The Problem

It usually starts small. A component gets copied instead of reused, a fix ships without anyone writing it down, and a year later every release feels like a fight.

  1. [01]

    Features take longer than they should

    Change one thing, five other places break. What should be a half-day task turns into a multi-day ordeal, and nobody can explain why.

  2. [02]

    New engineers take months to contribute

    Knowledge lives in people's heads. Conventions are undocumented. Onboarding is ad-hoc.

  3. [03]

    Design and engineering are misaligned

    No shared language, no design system governance, constant rework and miscommunication.

  4. [04]

    Performance degrades with every release

    The app gets heavier with every deploy. Pages that loaded in 2 seconds now take 5. Your users noticed before your team did.

Most teams try to fix this by pushing harder. At one company, PRs sat open for up to two weeks, so the CTO started tagging everyone in the dev channel himself. Nobody liked that. I set up a rotating PR champion instead, and every PR got reviewed the same week it was opened.

Who I Am

I started in Venezuela, led teams across startups and agencies, and shipped products used by thousands. A client once called me "the organizer." There's more if you're curious.

More about me
8s → 0.8s
MapVX app load time. Most of it came from dropping 16 icon packs we never used
6 engineers
The frontend team I led at MapVX
1,200+ stars
Puppertino, the CSS framework I built on the side

Let's Talk

I take on two clients at a time so I can give each one real focus.

Limited availability, accepting select projects for 2027 Tell Me What's Broken