Hello, I'm Edgar Pérez
Frontend Design Engineer
Your frontend is slowing you down. You just can't name why yet. I diagnose the structural problems your team feels but can't articulate.
The Problem
Frontend complexity rarely announces itself. It accumulates quietly.
Features take longer than they should
Every new feature requires touching more files than expected. Simple changes become multi-day efforts.
New engineers take months to contribute
Knowledge lives in people's heads. Conventions are undocumented. Onboarding is ad-hoc.
Design and engineering are misaligned
No shared language, no design system governance, constant rework and miscommunication.
Performance degrades with every release
No budget, no monitoring, no accountability. The site gets slower and no one knows why.
If any of this sounds familiar, the root cause is usually structural. I help teams diagnose and fix these problems at the source.
I see this everywhere. Here's how I learned to fix it.
Who I Am
I build the conditions for frontend teams to ship confidently. Architecture, process, culture — the structural work that makes speed sustainable.
I started in Venezuela, where resource constraints taught me to solve problems pragmatically. Over 9 years, I've led teams, presented to C-level executives, and shipped products used by thousands.
My focus is on the intersection of architecture, team dynamics, and business outcomes. I operate as a bridge between engineering, design, and leadership.
More about me →Over 9 years, I've developed three ways to help.
How I Help
Three engagement models for different stages of frontend maturity.
High-End Frontend Consulting
Diagnose structural problems, design systems that scale, make the implicit explicit.
Custom Web Development
Production-grade websites your team can manage. WordPress, WooCommerce, and beyond.
Long-Term Frontend Advisory
Ongoing access to senior frontend thinking without a full-time hire.
But not everyone needs what I offer.
Who This Is For
Good fit
- + Founders who sense frontend chaos but cannot clearly articulate it
- + CTOs responsible for technical direction and long-term scalability
- + Engineering managers overwhelmed by frontend complexity
- + Teams about to make expensive architectural decisions
Not the right fit
- - Teams looking for an extra pair of hands to ship features
- - Projects that need tutorial-style guidance
- - Organizations not ready to invest in structural change
- - Early-stage startups still searching for product-market fit
For those who do, here's what I've been thinking about.
Latest Thinking
Why I Choose BEM Over CSS Modules (Most of the Time)
CSS architecture is a decision with long-term consequences. Here is why I often reach for BEM methodology over CSS Modules, and when I do not.
Oct 7, 2024Why I Build Design Tokens Before Components
Most teams start with components and add tokens later. I do the opposite. Here is why the sequence matters and what it looks like in practice.
Featured Work
Two problems I solved. The full story inside.
MapVX
A 15-year-old fintech codebase with 8-second load times. I rebuilt the architecture from the ground up — sub-second loads, 99% component reuse.
View case study →
Puppertino
No macOS-style CSS framework existed. So I built one. 1,000+ GitHub stars, active community, zero JavaScript required.
View case study →Don't take my word for it.
What Others Say
Edgar is a very enthusiastic developer with a proactive attitude and eagerness to learn new technologies. He was able to work within the team to achieve amazing websites...
I am extremely grateful for the work Edgar did for my hostel. The website has enabled clients to make reservations directly, helping us avoid high fees from booking companies and offering a more personal experience.
Start a Conversation
I take on a limited number of clients per year. If your team is facing frontend complexity, let's see if we're a fit.
Limited availability — accepting select projects for Q1 2026 Start a Conversation