Senior software engineer. I build with React, TypeScript and Node.js, from the interface to the services behind it.

I’m Ramsés Fernández, based in Málaga. For more than eight years I’ve built enterprise products in travel, banking and consulting on both sides of the API: frontend architecture in React and TypeScript, the Node.js services and GraphQL contracts behind it, and the pipelines that ship both. Right now I own the technical design of exchanges and refunds at Travelport.

Open to remote or hybrid roles, EU timezones

What I build, top to bottom
  1. Interface React, TypeScript, React Native
  2. GraphQL, REST
  3. Services Node.js, Express
  4. SQL
  5. Data PostgreSQL

Shipped with Docker, Kubernetes, GitHub Actions and Datadog.

Selected work

Three projects, three kinds of ownership: a system inside a large platform, the foundation other teams built on, and a product I built alone.

2022 – present

Travelport

Exchanges and refunds for a travel platform

I own the technical design of the exchanges and refunds system: the part of the platform that handles what happens when a booking changes after it has been sold.

Role
Senior Software Engineer, via Pasiona
Domain
Travel technology
Stack
  • React
  • TypeScript
  • Node.js
  • GraphQL
  • Docker
  • Kubernetes
  • Datadog
How it’s built and what I do
  • I define the frontend architecture and lead the implementation. The UI is split into micro frontends built from plugins, each one talking to a Node.js frontend service over GraphQL.
  • I design those Node.js services, one per plugin, each its own dockerised microservice, and the GraphQL contract each micro frontend consumes. React stays decoupled from how the .NET services behind them are split up or changed.
  • I instrument frontend and service telemetry with Datadog. Regressions usually show up there before anyone files a ticket.
  • I own the frontend CI/CD pipelines on GitHub Actions and Azure DevOps.
  • I review most of the pull requests on the codebase and mentor junior developers.
Mine Other teams
Each plugin has its own Node.js service, and that service talks to its own slice of the .NET backend. I own the top two layers and the GraphQL contract between them.

2021 – 2022

BBVA

The frontend architecture other teams built on

I co-designed the core frontend architecture used across BBVA’s product teams, and built the design system on top of it. Other teams built their applications on that foundation.

Role
Senior Software Engineer, via SNGULAR
Domain
Banking
Stack
  • Web Components
  • Lit
  • Micro frontends
  • Design systems
  • Accessibility
What the foundation covered
  • Built on Web Components with Lit, so any product team could adopt it regardless of the framework they used.
  • A design system and component library on top: over 200 reusable components covering UI behaviour, accessibility and visual consistency.
  • Independently deployable micro frontends, so each product team could ship without coordinating releases with anyone else.
  • I reviewed pull requests from multiple engineering teams on the shared codebase, mainly for architectural consistency and accessibility.
Co-designed and built by me Other teams
Each team deploys on its own schedule. What they share is the layer underneath: the design system and the Web Components it is built from.

Personal project

RadarFish

A forecast app I designed, built and shipped alone

A mobile app that turns tides, swell, wind and pressure into one score per zone and hour. I built the React Native client, the Node.js backend and the scoring model, and I run the releases on both stores.

downloads
16,000+
active users in Spain
10,000+
star average across 400+ reviews
4.9
Role
Creator and sole engineer
Domain
Cross-platform mobile
Stack
  • React Native
  • Expo
  • Node.js
  • PostgreSQL
  • RadarFish screen: the score for one zone, with the variables behind it
  • RadarFish screen: scored fishing zones on the map
  • RadarFish screen: hour-by-hour scores per species

How I work

The tools matter less than the decisions they serve. These are the five I keep coming back to, and where each one has been tested.

Boundaries before components

The first decision is where one micro frontend ends and another team’s begins, and what belongs in a shared design system instead of a single product. Components come after.

  • Micro frontends
  • Web Components (Lit)
  • Design systems

Seen at BBVA and Travelport

A Node.js service behind every interface

I write the Node.js service that sits behind each micro frontend and design its GraphQL contract for that UI, so React doesn’t change when the services further back are split or reshaped.

  • Node.js
  • GraphQL
  • REST
  • Docker
  • Kubernetes

Seen at Travelport

Production is part of the work

I instrument the frontend and its services and own the pipelines that ship them. Regressions usually show up in telemetry before anyone files a ticket.

  • Datadog
  • GitHub Actions
  • Azure DevOps

Seen at Travelport

Shared code stays coherent through review

I review most pull requests on my current codebase and reviewed across teams at BBVA, mainly for architectural consistency and accessibility. I also mentor junior developers.

  • Code review
  • Accessibility
  • Mentoring

Seen at BBVA and Travelport

Able to ship the whole thing

RadarFish had no designer, no backend engineer and no one reviewing the architecture. Product scope, data model, API, both clients and both store releases were mine.

  • React Native
  • Expo
  • Node.js
  • PostgreSQL

Seen at RadarFish

Experience

Five companies since 2018, in travel, banking, consulting and healthcare tech.

  1. 2022 – present

    Travelport

    Senior Software Engineer, via Pasiona

    Technical design of the exchanges and refunds system: micro frontends, the Node.js services behind them, telemetry and CI/CD.

  2. 2021 – 2022

    BBVA

    Senior Software Engineer, via SNGULAR

    Co-designed the shared frontend architecture and built the design system on top of it, with over 200 components.

  3. 2020 – 2021

    PwC

    Software Engineer

    Frontend features for a project management app in React and TypeScript, on an international team working in English.

  4. 2019 – 2020

    DEKRA

    Software Engineer

    Frontend features for a medical project management app, in a regulated, quality-sensitive space.

  5. 2018 – 2019

    Rocketfy

    Software Engineer

    JavaScript frontend and Node.js backend on a small team. I owned my modules from design through release.

Education

Higher Technician in Web Application Development (DAW)

IES Politécnico Jesús Marín, 2016 – 2018. Spanish higher vocational qualification, EQF level 5.

Certification

Certified SAFe 5 Practitioner

2022

Languages

Spanish and English

Spanish is native. English at professional working proficiency.

About

Portrait of Ramsés Fernández

I’ve worked at five companies so far, in travel, banking, consulting, healthcare tech and one early-stage startup. Each one needed something different, and I kept ending up with the same kind of work anyway: the architecture several teams share, not a single product.

Most of what I do now is drawing boundaries. Where one micro frontend ends and another team’s starts. Where the UI stops and the API begins. What belongs in a shared design system and what belongs to one product. Get those wrong and everyone feels it for years. I work on both sides of that line: React and TypeScript in the browser, Node.js services behind it.

Outside client work I built RadarFish by myself: product, interface, backend and both app-store releases. Nobody else was checking my calls on that one, which makes it the clearest evidence I have that they hold up.

Have a role or a project in mind? Write to me.

LinkedIn
linkedin.com/in/ramsesfernandez (opens in a new tab)
CV
Download as PDF
Based in
Málaga, Spain
Availability
Open to remote or hybrid roles, EU timezones