Frontend Developer · React · TypeScript

Frontend work for
real-world systems.

React · TypeScript · production systems

Production frontend work

Frontend problems, in context.

2022 — 2024
01

Fintech · 2024

PedidosYa

Checkout work and reusable components for a payment flow with many states and edge cases.

ReactTypeScriptDesign system
02

SaaS · 2023

Pulse

A metrics dashboard where dense data needs to stay readable, consistent and useful.

ReactData-heavy UIUX/UI
03

Platform · 2022

Civic Lab

Components and prototypes for turning complex processes into clearer product flows.

ReactAccessibilityFigma

Experience

01/2023 — Present

Web UI Developer

Growin | Swissquote

Braga, Portugal

Frontend Developer at Growin, working for Swissquote on complex financial applications. Responsible for frontend features, business logic analysis, technical tasks, grooming sessions and onboarding new developers.

Focused on maintainable, well-tested code, architecture, coding standards and gradually improving frontend performance.

08/2019 — 10/2022

Web UI Developer

Globant

Rosario, Argentina

Worked on React applications for real-time feedback, employee engagement and internal tools in agile teams. Started with bug fixes and improvements before taking part in larger features such as dashboards, suggestions and data visualizations.

Contributed to React migrations, Storybook components, analytics improvements, unit testing, API integration and shared styling with SASS and BEM.

02/2020 — 07/2020

Student Mentor

Acámica

Rosario, Argentina

Supported students in the frontend track of the Full Stack Developer program through live classes, technical explanations and guidance on frontend practices.

Worked with HTML, CSS, JavaScript and React while developing communication and teaching skills through real-time problem solving.

How I work

I care about how things work, not just that they work.

I like understanding how an application is put together before changing it — why something behaves the way it does, where a problem actually comes from and which patterns are already established in the codebase.

I prefer simple, reusable solutions over unnecessary abstractions. I care about accessibility, maintainability and testing the behavior that matters. Whether I'm building something new, debugging an issue or improving existing code, I try to leave things a little clearer than I found them.

Tools and practices

React & TypeScriptReact Query & ZustandReact Aria & accessibilityStorybook & design systemsSCSS / BEMTesting & CI/CDAPI integrationComplex data interfaces

Working on a frontend problem?

Let's talk about
the work.