Skip to main content
Los Angeles, CA10+ years

Daniel Joffe

Senior frontend engineer turned full-stack. I ship complete products — Next.js frontends, Python/FastAPI backends, Postgres, and the LLM pipelines in between.

View case studies
Currently building

WyrdFold

Live

AI-powered job-search product I built and run solo. Resume tailoring, job ingestion, match scoring — with the production LLM pipelines (versioned prompts, shadow runs, async observability) behind them.

How I operate the LLM pipelines
Achievements

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.

Teams I've worked with

I've worked with these companies to build fast, beautiful, and inclusive digital experiences.

  • Winc
  • Internet Brands
  • The Library Corporation
  • FightCamp
  • Independent
Featured Projects
How I Think

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.

Building something that needs senior full-stack engineering?

Open to full-time roles with product-focused teams. If the frontend has to be excellent and you want one engineer who can own the whole stack, let's talk.