Skip to content
Biliane Silva — home
About — Product Designer & Front-end Developer

I design the thing, then I build the thing.

Biliane Silva at her desk in Maceió, Brazil
Based in
Maceió, Brazil
Overlap
UTC-3 — a full workday with US teams
Languages
English · Portuguese · Spanish
Open to
Full-time · Contract · US teams

I'm a product designer and front-end developer from Maceió, Brazil. I've designed for a decade and I spent the last four years on game launchers — first as a product designer, then as the developer shipping the same interface.

At HyperPlay I worked in the design team — research, interviews, prototypes, components, and responsibility for the design system — then joined the engineering team and worked on the same interface in React. At CoinFello I built the design system and implemented it myself. The through-line is the hand-off: I kept ending up on the other side of it, so eventually I stopped crossing back.

I wrote production front-end for a year before I used AI for any of it. I use it daily now and review everything it produces, but that order matters — you can't review what an assistant writes if you've never built the thing yourself.

The work I can show you in full is open source. In 2020 I led the validation research — desk research and interviews with Linux users — that established Heroic Games Launcher was worth building. It now has over 500,000 monthly users, and I've designed for it ever since, and written its front-end since 2025. Every decision I made there is a public pull request you can read, argue with, and check against what I say here.

In 2021 and 2022 I was at Starbreeze in Stockholm, doing quality-of-life UI on Payday 2 and making the game's 2D assets in Photoshop and Illustrator, then bringing them into the build myself. Before design was anyone's job title for me, there were years of freelance in Brazil building client sites on WordPress and Joomla — designing them and shipping them. That is where the habit started, and I have not managed to shake it.

I also hold a law degree, and passed the Brazilian bar exam in 2018 while I was still finishing it. I interned in small claims courts, the regional labour court and the public prosecutor's office. Legal training taught me to read something dense and badly organised, work out what it actually commits you to, and argue a position in writing to someone who starts out disagreeing — which turns out to be most of product design.

I am taking that into digital law: data protection, AI and blockchain. Those are the rules the products I design already run on, so the two halves answer to each other rather than compete. It is the reason a fintech and a web3 launcher felt like familiar ground rather than a compliance minefield — and the reason I am the person on a team who will actually read the data processing agreement.

I lived in Europe from 2019 to 2026 — Stockholm among other places — and work from Brazil now. English, Portuguese and Spanish, remote since 2022 with teams spread across the US, Europe and Latin America.

01How I work

Six things I will not trade away.

01

The problem before the pixels

Most design debates are really unstated disagreements about the problem. I'd rather spend the first week on framing than the last month on revisions.

02

Ship it or it didn't happen

A design that never survives implementation is a document, not a product. I measure my work by what is in production, not what is in the file.

03

Systems over screens

Screens are instances. Tokens, components and documented states are what keep the twentieth screen as good as the first — and I've owned that system twice.

04

Accessibility is a requirement

Contrast, focus order, keyboard paths and reduced-motion are part of the definition of done, not a pass someone does later. I learned this as a user: I get motion sickness from first-person games, and at Starbreeze I proposed the fix I personally needed.

05

AI moves the slow parts, not the judgement

I use AI daily and review everything it produces as if a junior wrote it. What to build, what the component should do, and what to refuse stays mine.

06

Write the rationale down

Working remotely across time zones means the argument has to survive without me in the room. Every decision gets a written why.

02Tools

Design

  • Figma
  • Figma variables
  • Prototyping
  • Adobe CC
  • FigJam

Code

  • TypeScript
  • React
  • Next.js
  • Tailwind CSS
  • SCSS
  • Electron
  • Docker

Process

  • Git & code review
  • AI-assisted workflow
  • Design systems
  • Analytics
  • Async writing
03Timeline
  1. 2025 — 2026Front-end Developer, CoinFello (US) — built and implemented the design system
  2. 2024 — 2026Front-end Developer, HyperPlay (Texas, US)
  3. 2022 — 2025Product Designer, HyperPlay — responsible for the design system
  4. 2021 — 2022UI/UX Designer, Starbreeze Entertainment — Payday 2, on-site in Stockholm
  5. 2020 — nowValidation research, design & front-end, Heroic Games Launcher — 500k+ monthly users
  6. 2019 — 2026Living in Europe — Stockholm among other places
  7. 2018Law degree and Brazilian bar exam, passed in my final year
  8. 2016 — 2018Freelance UI Designer, Alagoas — alongside law school
  9. 2012 — 2014Career break — full-time parenting, and the start of law school
  10. 2010 — 2012Graphic and web design, Brazil — where it started
Next step

Still reading? Let's talk.

I am looking for full-time roles or contractor engagements with US companies. Since 2022 I have worked remotely with US teams whose members sit across the US, Europe and Latin America — the time zones are a problem I have already solved.