Daniel Joffe
I've spent 10 years helping startups ship faster, building the frontends, design systems, and developer tooling that let teams move without friction.
I've worked with these companies to build fast, beautiful, and inclusive digital experiences.
10s → 2s Load Time
Reduced mobile load time from 10s to 2s at FightCamp.
80% Fewer Eng Requests
Decreased Content team's developer dependency by 80% at FightCamp.
200+ Pages in 2 Months
Increased campaign page launches to 200+ in 2 months at Winc.
80% Component Adoption
Built React component library adopted by 80% of apps at Internet Brands.
Cutting FightCamp Mobile Load Time from 10s to 2s
Cut mobile load times from 10 seconds to 2 and dropped bounce rates by 39% at FightCamp.
A React Component Library at Internet Brands
Built a React component library adopted by 80% of applications, then trained the team to own it.
A Self-Serve Landing Page CMS at Winc
From 3 pages per week to 200+ in two months. Self-serve tooling eliminated the engineering bottleneck at Winc.
I Audit Before I Build
At FightCamp, I found HD images and 800MB videos loading on every page. Lazy loading, srcset optimization, and bundle analysis cut bundle size by 62% and eliminated render-blocking on every page.
I Build for Autonomy
The best thing I can leave behind is a team that doesn't need me. I build CMS tooling that gets marketing off the engineering backlog, component libraries that new hires learn in a day, and documentation that outlives the person who wrote it. I invest in people the same way. Five developers I've mentored have gone on to promotions and dream jobs, including one now at JPL.
I Measure What Matters
Lighthouse scores, bounce rates, Core Web Vitals. I treat performance as a feature, not an afterthought. At FightCamp, systematic optimization lifted Lighthouse from ~35 to ~80 and cut mobile bounce rates by 39%.
I Think in Systems, Not Just Components
Building auth systems and rate limiters taught me to reason about tradeoffs: JWT vs sessions, in-memory vs distributed state, fail-open vs fail-closed. I bring that architectural thinking to every layer of the stack, not just the UI.
Got a project that needs senior engineering?
I take on 1–2 engagements at a time. If you're building something that matters, let's talk.