Skip to content

Alejandro Solarte

First the business.Then the user.Then the code.

Alejandro Solarte

Front-end developer & designer. Design systems, performance and UX for products at scale.

Open to full-time roles · Available for freelance

Work

Case studies

Three products, the decisions behind them, and what changed.

87%

faster consent flow · Sonesta

25%

faster ecommerce loads · Colombiatodo

45%

of the Portal migrated off MUI · Bosanet

100+

hours mentoring developers · Icesi

Experience

Where I worked

  1. Front-end Developer & Designer · Bosanet

    Marketplace and seller portal: performance and UX on Xpress, design system and dashboards on the Portal.

  2. Web Developer & Designer · Colombiatodo CI SAS

    Ecommerce platform end to end: storefront, CMS, checkout, payments and shipping.

  3. Jan – Jul 2025

    Web UI Developer · Globant — Sonesta International Hotels

    Public web team: consent flow, accessibility and a shared typed component.

  4. Jan – Dec 2024

    Lead Developer · InnLab Icesi

    Led the website rebuild and a small team, running Scrum with the client.

  5. Jan 2023 – Nov 2024

    Coding Mentor · Universidad Icesi

    100+ hours tutoring 20+ peers in programming and web fundamentals.

  6. Aug – Dec 2023

    UX/UI Designer · enerBit

    Redesigned the mobile app for users with low digital literacy.

  7. Jul – Nov 2023

    Front-end Developer · Banco W

    Rebuilt five sections of the public site in HTML, CSS and JavaScript.

Capabilities

What I work with

HTMLCSSJavaScriptTypeScriptReactNext.jsGatsbyTailwind CSS
FigmaStorybookDesign tokensAccessibilityUX researchPrototyping
StrapiSupabaseFirebaseFastifyMercadoPagoGit

About

How I work

Design-trained engineer. The hardest part of the job is not the implementation — it is understanding what the business actually needs. That is the part I optimize for.

  1. Understand the constraint

    I start with the business goal and the person who has to use the thing. A technically elegant answer to the wrong problem is still wrong.

  2. Cut before building

    Scope is a product decision. I remove what the user does not need before writing code, not after shipping it.

  3. Choose the stack last

    Architecture serves the decision above it. React, Next, the database: the choice comes after the problem, never before.

  • Based in Cali, Colombia (UTC−5)
  • B.S. Interactive Media Design, Universidad Icesi
  • Scrum certified (Kleer)
  • Spanish · English · Portuguese (basic)
View full CV (PDF) ↗

Contact

Let's talk

Open to full-time roles and freelance projects. Remote, from Cali, Colombia (UTC−5).