Jesse Alvarado.
Available for contract work

Frontend engineer, ten years in software and the last four freelancing for startups. I ship whole features, backend included. I work with teams who have a concept or an MVP and need it finished properly.

Based
Tokyo, remote
Status
US citizen, W-9/1099
Japan visa
Engineer / Specialist in Humanities
Overlap
Full APAC, US West mornings
Jesse Alvarado, Frontend Engineer, Tokyo, Japan.
TypeScript
React
Next.js
Node.js
NestJS
PostgreSQL
Prisma
Stripe
Square
01What you get

The last mile, done properly.

01

A product that ships.

Most of what I am hired for is the last mile: a prototype that runs on the founder’s laptop, a Figma file built through customer interviews, a frontend written fast that can no longer be changed. I take those to production — real users, real payments, real edge cases — and leave a codebase your team can keep working in.

02

Frontend is where I am deep.

It is where most of my hours have gone, and where I am a top contributor from the first week. Interface architecture, state, performance, accessibility, and design systems that hold up as the product grows.

03

Nothing waits on someone else to build the endpoint.

I take features across the stack: the API, the schema, the integration. I have shipped payments, authentication, multi-tenant isolation, and scheduled jobs. I will build that layer, or work cleanly against the one you have. For a small team that is the difference between a feature landing this month and next quarter.

04

Designs that survive the build.

I implement finished designs accurately and keep them fast. Design-to-code tooling gets me a pixel-accurate first pass; I rework it by hand so every file matches the codebase. The speed goes into the first draft, not into what you inherit.

02Selected work

What was wrong, what I did, what happened.

Reboot storefront homepage, showing the Japanese-language subscription hero.

Reboot

Device rental subscriptions, Japan · prototype to launch

2024
The problem
A subscription service renting smartphones and devices across Japan, sitting on a prototype that could not launch.
What I did
Rebuilt the entire e-commerce frontend as a production application against their Django backend, and implemented Square for subscription payments.
  • Next.js
  • TypeScript
  • Square
  • Django
reboot-japan.com
Crewcade homepage, showing a class booking page for a Tokyo pilates instructor.

Crewcade

My own product · booking and payments

2024 — present

Crewcade is a booking and payments platform for independent fitness instructors in Japan. I built all of it — the frontend, the API, multi-tenant data isolation, Stripe Connect payments. It is in limited production, piloting with the fitness community I organize in Tokyo.

  • NestJS
  • Prisma
  • Stripe Connect
  • Multi-tenant
crewcade.com

What building it taught me

  • I narrow scope instead of defending it.

    Each pivot cost me a CMS-backed backend, a tRPC API layer, and a component library. I replaced all three rather than build the wrong product on top of them.

  • I get payments right before there is money on the line.

    Funds route directly to the instructor, never through my platform balance. Cancellation policies drive refunds automatically. Built to the standard it needs at volume, not at one user.

  • I build systems I can still change.

    Multi-tenant isolation is enforced by the database layer, not by anyone remembering to filter a query. Failure modes I have hit are enforced by the build. That is why three rewrites were survivable.

More case studies in progress. Ask and I will walk you through any of them.

03How I work with you

You will never have to ask where things stand.

You will always know where things stand.

Short written updates, decisions recorded with their reasoning, recorded demos, pull requests you can read. The person paying should never have to ask whether progress is being made.

Timezone.

From Tokyo I am live with APAC all day, and with the US West Coast in your morning.

I tell you what something costs before I build it.

Requirements change in startups. When yours do, you hear the tradeoff from me early and in plain terms, and then I keep moving.

I use AI tooling heavily while I own the output.

It is a large part of how I cover the whole stack alone and move as fast as I do. I decide the architecture, review every line, and take responsibility for every defect.

Stack

Deep

Where most of my hours have gone.

  • TypeScript
  • React
  • Next.js
  • State & data layers
  • Design systems
  • Performance
  • Accessibility

Comfortable, shipping in production

Owned end to end for my own features.

  • Node.js
  • NestJS
  • PostgreSQL
  • Prisma
  • Stripe
  • Square
  • OAuth
  • Typed API clients
  • Monorepos
  • CI/CD
Jesse Alvarado, Frontend Engineer
04About

I have worked in software since 2016 and have been freelancing since 2022. I am based in Tokyo, available for contract work or a full-time remote role.

Outside of code I am part of Tokyo’s fitness scene. I spent three years as Captain of Midnight Runners Tokyo, one of 18 chapters worldwide, and serve as Director of SOGO Fitness, a ten-year-old fitness community.

Lately I have been building the partnerships and platform work that connect brands with those communities. Crewcade came out of that.

In software since
2016
Freelancing since
2022
Midnight Runners Tokyo
Captain, 3 years
SOGO Fitness
Director
05Contact

Tell me what you are building and what is in the way.

contact@jessealvarado.com

Tokyo (JST) · US citizen · Japan work visa · APAC and US West overlap