Frontend engineer fluent in React,
TS
& the platform.
Three years shipping accessible, performant interfaces in React, TypeScript, Next.js and Sitecore AI CMS. Deep on the web platform, design systems and the small details that make UI feel inevitable.
Three years of caring about the small things — focus states, keystroke latency, and the gap between a designer’s file and the live DOM.
I’m Renan Garcia, a frontend engineer working out of Quito, Ecuador. I help product and design teams turn complicated specs into interfaces that feel inevitable — fast to load, easy to operate, friendly to assistive tech.
Day-to-day that means React + TypeScript on top of Sitecore, Next.js or Astro. Off-hours that means experimenting with view-transitions, scroll-driven animations, and any CSS feature that ships in Chrome that month.
- Born1997 · Quito, EC
- Years building3+ in production
- EducationB.S. Software Eng.
- Lighthouse avg.98 / 100
- LanguagesES (native) · EN (C1)
- Coffee/day2.4 — measured
What I bring to every codebase.
- 01
Calm over clever.
Interfaces should disappear into the task. Animation has a job. Colors earn their place. If something feels loud, it’s usually wrong — or it’s deliberately the one moment that should sing.
- 02
Accessibility is the brief.
I write to WCAG 2.2 AA as a floor, not a ceiling. Keyboard reachability, focus visibility, semantic landmarks, reduced-motion variants — table stakes before pixel pushing begins.
- 03
Perf is a feature.
Every animation is profiled. Every image is sized. Every JS bundle has a budget. The fastest UI is the one that’s already painted before the user expected it.
Four areas I’ve gone deep.
My day job is at an agency, so finished work sits behind NDAs. What I can share is the shape of the expertise itself — the patterns, tools and trade-offs I’ve internalized.
- 01
Modern React architecture.
Component composition, state colocation, server components, suspense boundaries, data-fetching patterns. I write React the way React wants to be written — and know when to break the rules on purpose.
- 02
Headless enterprise CMS.
Sitecore AI CMS, JSS, content modeling, multi-region marketing platforms. I know where the abstractions leak and how to make a head feel native on top of an enterprise CMS.
- 03
Performance & accessibility.
Core Web Vitals, INP, hydration costs, image pipelines. WCAG 2.2 AA as a floor, manual screen-reader passes as a habit. I treat both as features, not afterthoughts.
- 04
Design systems & tokens.
Token-first component libraries, theming primitives, headless patterns, the connective tissue between Figma and production. The kind of work that pays back ten engagements later.
How I actually work.
- → 01 Read
Read
Before I write a line, I read the codebase, the design files and the metrics. Patterns first, opinions second.
- → 02 Frame
Frame
Constraints before code: perf budget, browser matrix, a11y floor, naming conventions. The boring decisions made once, so the interesting ones can stay interesting.
- → 03 Build
Build
Small PRs, candid changelogs, no surprise scope. Each commit ships with a benchmark, a screenshot diff and an accessibility note.
- → 04 Polish
Polish
The last 10% is the part that matters: focus states, transitions, error copy, empty states. Where craft compounds.
The kit I reach for first.
Currently on the desk.
Sitecore AI CMS + Next.js 16
A multi-region marketing platform for a fintech. Personalization, AI-assisted content, sub-second TTFB.
Scroll-driven animations
Replacing JS scroll listeners with native animation-timeline: scroll(). Almost there in stable.
Refactoring UI
Wathan & Schoger. Re-reading the chapter on visual hierarchy for the third time, no shame.
Fred again..
The Actual Life trilogy on loop. Vocal samples and chopped textures — somehow the right tempo for a long refactor.