Front-end engineer · Mérida, México

Hi, I'm Berty.

I build fast, accessible websites and web apps, and I like knowing why they exist before I start.

Five years of hands-on experience: 30+ live websites, a ticketing web app built from zero, and the servers underneath it all. Engineer by training, creative by nature.

Illustrated portrait of Berty: long dark hair, round glasses and a big smile.
See the work Tell me about your project Open to full-time front-end roles · Get my résumé (PDF) (opens in a new tab)

01 · The work

Work that's live, and that I still look after

Case study · 2024 to today

A ticketing web app for a ferry operator in the Mexican Caribbean

Travellers buy ferry tickets online at any hour, and agents sell from the same system.

The need
Sell tickets online, and give counter agents a fast way to book.
What I built
A web app with two sides: a public booking site for travellers and an internal sales system for agents, connected to the operator's reservations API. It covers the whole sale, from the reservation to the bank's payment link to the final ticket once payment is confirmed. Built from zero with Laravel, Inertia.js and Vue. I also set up its server: an Ubuntu Server virtual machine on Hyper-V, running on the client's Windows Server, with PHP, Laravel and everything the app needs.
The result
Live and issuing real tickets. I still support it in production.
  • PHP
  • Laravel
  • Inertia.js
  • Vue
  • REST API
  • Ubuntu Server
  • Nginx
  • Hyper-V
  • Windows Server

Ongoing · since 2021

30+ websites for research labs and science teams

Research labs get sites that load fast, work for everyone, and stay online.

The need
Many sites, one small team, and visitors who all deserve the same fast, accessible experience.
What I built
I'm one of a two-person development team at a science communication studio. I turn designers' layouts into working sites with WordPress, PHP, custom Gutenberg blocks, SCSS, JavaScript and GSAP. I build reusable components, make accessibility part of every build, and handle deployments across several hosts.
The result
30+ sites live, and I'm the first call when one of them breaks.
  • WordPress
  • PHP
  • Gutenberg blocks
  • SCSS
  • JavaScript
  • GSAP
  • WCAG 2.2

Launch and hosting, handled

I take care of hosting and launch, so you don't need to find someone else for it. Your site or web app goes wherever suits you best.

Technical details: hosting, servers, deployment

I've deployed to managed and shared hosting, Windows Server and Linux virtual machines, over SSH or with automated GitHub Actions pipelines.

  • Cloudways
  • GoDaddy
  • JustHost
  • Bluehost
  • Windows Server
  • Linux virtual machines
  • SSH
  • GitHub Actions
Illustration: Berty at her laptop, sending a finished site up to the cloud.

02 · Who I am

I make things that work, and feel good to use.

I studied computer systems engineering because software is where I always wanted to be: a place to make things as well as calculate them.

I bring an engineer's questions to every project. Who is it for? What fails first? Who looks after it once it's live?

Lately I've started designing too. I shaped my own brand in Figma, crocodile included, and set the direction for this site. In 2024 I earned the Google UX Design certificate.

That's how I like to work: creative on the surface, solid underneath.

03 · Both sides

People expect me to pick a side. I don't.

The engineer

  • Accessibility built in from the first line of code.
  • Fast pages: optimized images, lazy loading and caching.
  • Linux, Nginx, DNS and SSL, and the deployments that keep sites running.
  • Reusable components that keep 30+ sites consistent.

The creative

  • Motion that helps people follow the story.
  • Turning a designer's layout into a site that feels the way they meant it.
  • Turning a rough brief into a clear plan.
  • A crocodile in my logo, because I love them and they make people smile.

My best work happens where the two meet.

04 · How I work

Good work needs a steady pace.

I take on a small number of projects at a time, so each one gets my full attention, from the first call to long after launch.

  1. I listen first.

    Before I estimate anything, we talk through what you need, who it's for, and how we'll know it worked.

  2. Clear scope, honest timelines.

    You'll know what I'm building, when, and what it costs, in writing, before work starts. If something changes, you'll hear it from me early.

  3. Focused days, quick replies.

    I work focused days, Monday to Friday on Central time (UTC−6), and reply to messages within one working day. Organized work has fewer mistakes.

  4. Here after launch, if you need me.

    Once your site is live, we can agree on an ongoing support plan: updates, fixes and small changes, on clear terms. Some clients have kept working with me long after launch.

05 · Bigger projects

When a project needs a team

I'm a partner at Neurona Tech, a small studio that builds software. When a project needs back-end work or more hands, we take it on together, and I stay your main contact.

Partner studio

Visit Neurona Tech (opens in a new tab)
Illustration: Berty and Carlos from Neurona Tech, side by side at their laptops, solving a problem together.

06 · Let's talk

Let's make something that lasts.

Hiring for a front-end role?

I'm open to full-time roles with English-speaking teams. My résumé is right below.

Résumé (PDF) (opens in a new tab) LinkedIn (opens in a new tab) GitHub (opens in a new tab)

Have a project in mind?

Tell me what you're building and who it's for. I'll reply within one working day.