Lucas Almeida

Engineering × Product × Design

I build products people actually enjoy using.

I'm a Product Engineer with more than 15 years of experience helping companies transform ideas into scalable digital products. My work sits at the intersection of engineering, product strategy, user experience and business.

Whether I'm improving onboarding, rebuilding legacy systems, optimizing performance or designing new experiences, the goal is always the same: create products that people love using and teams love building.

View selected workLet's build something together

01 — What I do

Building products, not just software.

Writing code is only part of the job. The real challenge is understanding people, business goals and technical constraints at the same time.

Technology changes constantly. Great products don't.

Across the full product lifecycle

  1. Discovering problems
  2. Designing better experiences
  3. Building scalable software
  4. Improving performance
  5. Measuring impact

02 — Core philosophy

Four principles behind everything I ship.

  1. Think before building.

    Understand the business before writing code.

  2. Design with purpose.

    Every interface should solve a problem, not create one.

  3. Keep complexity invisible.

    Users should experience simplicity even when the system behind it is complex.

  4. Measure everything.

    If it doesn't improve outcomes, it isn't finished.

03 — Impact

Outcomes, not technologies.

15+
Years building digital products
100+
Projects delivered
Millions
Users impacted through products I've contributed to
10k+
Daily platform interactions on products I've helped improve
34k+
Monthly subscribers supported on gaming infrastructure products

04 — Selected work

Three stories about product decisions.

Not a list of repositories. Each one starts with a problem and ends with what changed because of it.

01Featured · Esports platform

Gamers Club

One of Latin America's largest esports platforms — millions of competitive players, matches running around the clock.

Gamers Club key art: the tenth-anniversary logo over a masked competitive player.

The challenge

A frontend grown faster than its architecture. Feature velocity was slowing, the experience felt inconsistent across surfaces, and peak-traffic performance shaped how players perceived the whole product.

Decisions

Restructure the frontend around product domains instead of pages. Standardize shared interface patterns so teams stop re-deciding the same things. Treat performance as a product requirement with an owner, not a cleanup task.

My contribution

Frontend architecture and scalability, shared component foundations, and the product work around the competitive experience — sitting between design, product and platform teams rather than waiting for specs.

What changed

10k+
daily interactions on improved surfaces
34k+
monthly subscribers supported

02Onboarding · Conversion

Minehut

One of the world's largest Minecraft hosting platforms, where most new users are teenagers creating their first server.

The Minehut logo over a dimmed screenshot of a player-built Minecraft world.

The challenge

Creating a server required understanding infrastructure concepts before getting to the fun part. Plenty of signups, far fewer players who ever reached a running world — and premium upgrades were framed as features, not as outcomes people wanted.

Decisions

Move the first success moment as early as possible and defer every configuration choice that isn't required to play. Explain premium in terms of what it unlocks for a player's community. Instrument the funnel step by step before changing it.

My contribution

Onboarding and server-creation experience, premium conversion surfaces, and the UX decisions behind them — from flow design through implementation and measurement.

What changed

A shorter path from signup to a live server, a clearer premium story, and a funnel the team could reason about with data instead of opinions.

03Discovery → Deployment

Freelance & Consulting

Complete digital products across healthcare, finance, retail, beauty and service industries.

  • Healthcare
  • Finance
  • Retail
  • Beauty
  • Services

The challenge

Most clients arrived with a solution already written down. The actual work was separating the request from the problem underneath it — often before a single line of code was justified.

Decisions

Start every engagement with discovery and a written definition of success. Ship a small, real slice early instead of a long specification. Choose boring, maintainable technology the client's team can own after handover.

My contribution

End-to-end ownership: discovery, product definition, interface design, architecture, implementation, deployment and the follow-up work after launch.

What changed

100+ products delivered across five industries — several replacing manual operations entirely, and most maintained by the client's own team afterwards.

05 — How I work

A process that keeps decisions cheap.

  1. Understand

    Learn the business.

  2. Simplify

    Reduce unnecessary complexity.

  3. Prototype

    Validate ideas quickly.

  4. Build

    Create scalable systems.

  5. Measure

    Optimize using real feedback and data.

06 — Design mindset

I started as a designer, then became an engineer. That order changed everything.

Design taught me to look at a product from the outside in — what someone is trying to accomplish, where they hesitate, what they should never have to think about. Engineering taught me what it costs to deliver that.

So usability, accessibility, visual hierarchy, developer experience and business impact are part of how I think before implementation starts — not a review step afterwards. Bridging those two languages is the most useful thing I do.

07 — Capabilities

Organized by what it lets me do.

Tools are interchangeable. The capability is what a team actually hires.

Frontend

  • React
  • Next.js
  • Vue
  • TypeScript

Backend

  • Node.js
  • NestJS
  • PHP
  • Go

Infrastructure

  • Docker
  • Kubernetes
  • Cloudflare
  • Redis
  • MySQL
  • PostgreSQL

Developer Experience

  • Architecture
  • Performance
  • Testing
  • CI/CD

Product

  • UX
  • Analytics
  • Design Systems
  • Experimentation
  • AI Integrations

08 — About

Started
As a designer, learning how people actually use things.
Then
Moved into software engineering to build what I was drawing.
Later
Expanded into architecture, because scale is a product concern.
Today
Product Engineering — technical depth, design thinking and business understanding in one role.

The through line is the same at every step: build products that are easier to use, easier to scale and more valuable for the companies behind them. Fifteen years in, that’s still the only scorecard I trust.

Lucas Almeida, photographed against a weathered concrete wall.

09 — Contact

Have an interesting product challenge?

Whether you're launching something new, modernizing an existing platform or simply exploring an idea, I'd love to hear about it. Let's build something meaningful together.