Francisco Diaz Paccot

Senior frontend engineering at the intersection of product, performance, and platform.

I design and build web experiences where architecture decisions show up in metrics, velocity, and how the product feels under real load, not just in a demo environment.

Selected work Writing on performance
Francisco Diaz Paccot

7+

Years in production frontends

Org products and customer-facing performance work

Deel

Current

Org, planning, and integrations on customer-critical surfaces

Perf / platform

Recurring remit

Web quality, build ergonomics, how UI ships under constraint

Bilingual work

EN · ES

Same rigor, same craft—regardless of market

Case studies

How engineering choices surface in the product

A sample of work where architecture, performance, and product tradeoffs are explicit. For a broader list, use the full portfolio.

View full portfolio
Turnox product screenshot
Turnox — live site

SaaS · booking

Turnox

Problem · Service businesses need reliable scheduling without a heavy enterprise stack. The product had to feel instant on mobile and stay operable on flaky networks.

Solution · A focused client-and-admin flow for appointments, with a frontend tuned for quick first paint and predictable state after navigation.

Architecture

Separation of public booking and authenticated views, with shared design primitives so UX stays consistent as features ship.

Tradeoffs

Favored convention and speed of iteration over a maximal component library, while keeping routes and data boundaries clear for future growth.

Outcomes

Operators onboard in minutes. The surface area stays small on purpose, which keeps maintenance cost predictable as usage scales.

Wanna Work product screenshot
Wanna Work — live site

Productivity · documents

Wanna Work

Problem · Resume builders often ship generic templates; users need confidence that what they see is what recruiters see, and fast time-to-export.

Solution · Template system with a strong default visual hierarchy, optimized asset loading so the editor remains responsive on average hardware.

Architecture

Content and presentation are structured so new templates do not require forked logic; export paths stay stable as layouts evolve.

Tradeoffs

Chose a thinner animation layer in favor of consistent layout and print-friendly output, which is where the product’s credibility lives.

Outcomes

Users can go from sign-up to a presentable document quickly, with fewer support edge cases from layout breakage across viewports.

Blabi product screenshot
Blabi — live site

Platform · no-code web

Blabi

Problem · Non-technical users need a site that feels custom without a full agency engagement. Page weight and clarity matter as much as templates.

Solution · A generator-led experience that keeps pages lean and enforces a coherent structure so sites stay performant and accessible by default.

Architecture

Treating pages as composable blocks with shared head metadata patterns, so SEO and social previews stay correct as users iterate.

Tradeoffs

Narrower layout freedom than a raw CMS, in exchange for fewer performance cliffs and a more supportable long tail of customers.

Outcomes

Faster paths from idea to published site, with frontends that remain easy to reason about as the product adds vertical-specific flows.

Philosophy

How I work

Performance is a product feature. I treat web vitals, bundle shape, and data-fetching as design constraints—because they decide whether a feature feels “premium” in production, not in a local demo. That mindset scales to teams: shared foundations beat one-off heroics.

Platform work is how frontend seniority compounds: design systems, build pipelines, and clear boundaries between product surfaces. I invest there so the next project ships faster with fewer regressions, and so engineers can reason about the system a year from now.

I work best in cross-functional teams with strong product ownership—where tradeoffs are explicit, written down, and tied to business outcomes, not just ticket throughput.

Extended background

Writing

Performance, tooling, and practice

Shorter pieces on the craft: metrics, build tooling, and how the web actually behaves in the field.

All articles

Work together

Open to senior frontend, platform, and product-facing roles.

If you are scaling a web product and care about performance, maintainability, and how engineering decisions show up in the business, I would like to hear from you.

Email Contact page