Alejandro Maciá

Scroll

Problem Solver

Full-stack engineer with 4+ years of experience building for the web.

ResumeLinkedIn

01/

I like making code easier to work with: clearer types, reusable components and faster feedback.

React, Next.js, Node.js and Java. These days mostly frontend, with a soft spot for TypeScript and developer experience.

Experience
4+ years, full-stack
Core stack
React, Next.js, TypeScript, Node.js, Java
Languages
Spanish (native), English (C2)
Work style
Remote, international teams

02/

Four teams so far, each one a step up: from client websites to product and platform work.

  1. Jun 2025 — Present

    Apipana.io

    Product & platform

    Software Engineer

    • Type-safe templating for Next.js: prop errors caught at compile time.
    • Island Watch Mode with a dependency graph and SSE: up to 90% faster feedback.
    • Platform work across 13+ themes: shared components, design tokens, faster builds.
    • Cross-device state and a new product variant across 6+ page types.

  2. Feb 2024 — Jun 2025

    Ensolvers

    Evolving live products

    Software Engineer

    • Migrated React 17 → 18 and a Java service to AWS SDK v2, backed by integration tests.
    • Services in NestJS, Spring Boot and React. Fixed dependency vulnerabilities.
    • CI/CD with Bitbucket and SonarQube: automated deploys and quality checks.

  3. 2022 — 2024

    Freelance

    Working with clients

    Web Developer

    • Worked directly with clients: scope, questions, delivery.
    • Custom projects, built for what they actually needed.

  4. 2022 — 2023

    Coverit

    Learning the craft

    Web Developer

    • Team websites in JavaScript and WordPress, responsive by default.

Education

  1. 2022 — 2024

    Certified Tech Developer

    Digital House · Mercado Libre · Globant

    JavaScript, React, Java, Spring, AWS, testing and UX/UI.

  2. 2016 — 2024

    Degree in International Relations

    Universidad Católica de Santa Fe

03/Problem solving

How I tend to work: understand the problem, simplify it, then build.

  1. 01

    Slow feedback loops

    Problem

    Every change meant waiting to see it.

    Approach

    A dependency graph finds what changed. Server-Sent Events push only that.

    Result

    0%

    faster feedback, over 95% in some cases

  2. 02

    Templates that broke at runtime

    Problem

    Any prop was accepted, so mistakes surfaced in production.

    Approach

    Advanced TypeScript types check every prop as you write it.

    Result

    Compile-time

    prop safety, enforced by the type system

  3. 03

    A platform that has to scale

    Problem

    13+ themes on one platform drift apart.

    Approach

    Shared components and design tokens every theme inherits.

    Result

    0+

    themes improved on one shared platform

  4. 04

    Upgrading live systems

    Problem

    React 17 and AWS SDK v1 had to move on without breaking anything.

    Approach

    Step-by-step migration, backed by integration tests.

    Result

    0

    major migrations, shipped safely

04/

Tools change. Habits don't: types first, test what matters, automate the rest.

  • Languages

    TypeScriptJavaScriptJavaSQLHTMLCSS / SCSS

  • Frontend

    ReactNext.jsTailwind CSSBootstrap

  • Backend

    Node.jsNestJSSpring Boot

  • Databases

    SQLMongoDB

  • Cloud & DevOps

    AWSDockerCI/CD

  • Testing

    JestReact Testing LibraryPlaywrightUnit & integration testing

  • Tools

    GitGitHubBitbucketSonarQube

  • AI tooling

    Claude CodeGitHub CopilotOpenCodeOllamaAI coding agentsPrompt engineering

05/

Software is built by people. Most hard problems are unclear expectations, not code.

Understanding people first

International Relations taught me negotiation and seeing a problem from every side.

Working with clients

No one between me and the client. I turned vague requests into clear scope.

Remote and international

Native Spanish, C2 English. A clear PR message matters as much as the code.

06/Contact

Have a project or a role in mind? Let's talk.

Always happy to talk about React, TypeScript or a problem worth solving.

© 2026 Alejandro MaciáDesigned and built by me