consulting on frontend systems, mostly design systems and platform work.
~ frontend engineer · colombia
I build frontend systems for products that keep changing.
Products change constantly. I build the things that make that manageable.
I work on the platforms other teams build products on: design systems, BDUI, DevExp tooling, frontend architecture, accessibility, and the bugs that only show up in production. When the product needs backend code, I write that too.
/ now
~ 2026
browser fundamentals below the devtools layer. Specs first, then what browsers actually do.
returning to rails and nestjs. MVC, auth, domain models.
what makes teams actually adopt a design system instead of working around it.
/ log
2013 to now
2013
started in software support. SQL reports, legacy PHP, ERP tickets. Built a mobile-friendly app for tracking field overtime, my first real feature.
2015
first remote job, for a london warehouse company running on shared folders instead of version control. Introduced git, then built a map for assigning tasks to warehouse locations and a system for tracking pick runs. Users were warehouse floor workers, not developers.
2018
joined a company with no tests, no CI, and no design system. I was hired to change that.
2019
built an internal chrome extension the team used daily. Built a CSS custom properties theming system so customers could control their brand without an engineering ticket. Took test coverage from zero to where CI/CD was possible.
2021
consulted for a media company. Their reader app had 40,000 downloads. Validated the article-rendering approach through prototypes before writing the javascript that shipped inside the iOS app.
2022
consulting for a hedge fund client. Built an email template system in react so the team could update branded emails without engineering, plus a custom chart configurator on highcharts. Also interviewed frontend candidates.
2023
ran a/b tests on camera selection and a barcode-scanning migration in the verification flow. Together they moved conversion 3%.
2024
started helyx before design had finalized anything. Built around the rules we knew would hold, then let the screens change without rewriting the whole system. Web shipped first, iOS and Android built on the same contract after.
2025
shipped BDUI and WCAG 2.1 AA in the same year, on the same identity flow codebase.
/ work
selected work
a few systems I built, and what changed because of them.
helyx: a design system that runs the flow
the server sends JSON. The browser renders a verified identity flow. No deploy needed.
built helyx while the designs were still changing. Settled the data model and rendering rules before drawing the screens. It's a design system with a BDUI renderer that meets WCAG 2.1 AA, and new identity flows use it by default.
making changes safer
the codebase had no tests, no CI/CD, and no design system. Three years later it had all three.
started with unit tests, added component tests, and moved e2e coverage to cypress. Built a CSS custom properties theming system so customers could change their brand settings without opening an engineering ticket. Then led the move from bootstrap to a custom design system.
/ materials
react · web components · next.js · rails · laravel · nestjs supabase · cloudflare · render · cypress design systems · BDUI · APIs · product backends
not the point of the site. I pick tools based on the problem.
/ contact
bring me a hard problem
me@azapata.io
I take on consulting and contract work when there is a real problem to solve.
I can help with frontend architecture, design systems, accessibility, and reliability. I also write backend code when the product needs it.
me@azapata.io. I read everything.