CaixaBank Tech
Banking widgets other teams build on
Built to be built on.
At CaixaBank Tech I built frontend applications and a set of reusable Stencil widgets that other internal teams consumed in their own products — in a regulated banking environment where a bad release is felt immediately.
The context
Code with an audience of engineers
Building components other teams depend on changes the job. Your API is a promise, a breaking change is somebody else's incident, and 'it works on my product' isn't a standard. Stencil kept the widgets framework-agnostic so consuming teams weren't tied to our choices.
The migration
A public site, moved carefully
I led the migration of a legacy public-facing site to modern React, holding Jest coverage above 90% on the components I owned. In banking, coverage isn't a vanity metric — it's what lets a release go out without a week of manual checks.
The releases
Owning what happens after
Deployment and post-release bug resolution were mine, through Azure DevOps, in an environment where mistakes are visible to a lot of people very quickly. Shipping carefully became a habit rather than a policy.