Skip to content
Tadashi Hammada
Available for new projects

I design and ship
web products end to end.

Software engineer working across product teams and my own builds — interfaces that feel effortless, systems that scale quietly in the background.

View case studies hello@tadashi.tech
Jakarta, ID · GMT+7 Remote-friendlyEN / ID
Portrait
jakarta · idgmt+7 · remote ok

Tadashi Hammada — software engineer

01 — About

Engineer, builder, lifelong learner.

I'm a full-stack engineer who cares about the whole path of a feature: the moment a user taps something, the request it triggers, and the system that answers it. Most of my work sits where product thinking meets solid engineering.

I've shipped internal tools that replaced hours of manual work, rebuilt frontends that had grown brittle, and modernised deployments so a release became a non-event. Along the way I learned that the boring parts — naming, error states, observability — are what make software feel trustworthy.

Outside of client work I maintain small open-source tools, write notes about what I learn, and test new stacks before recommending them to anyone.

Product engineering

From rough idea to shipped feature, with you in the loop the whole way.

Interfaces & design systems

Accessible UI, consistent tokens, components that don't fight you later.

Backend & infrastructure

APIs, data models, queues, deploys — built to be understood by the next person.

Performance & DX

Fewer bytes, faster feedback loops, tooling that gets out of the way.

6+Years shipping software
24Projects delivered
12Open-source repos
<1sMedian page load, current builds

02 — Selected work

Three builds, and what changed because of them.

Each one written as a short case study: the problem, what I built, and the measurable result.

  • Realtime analytics dashboard

    2025 · product team of 6
    Problem

    Operators waited up to a day for reports, so they acted on stale numbers and kept a parallel spreadsheet nobody trusted.

    What I built

    A streaming pipeline (Postgres → queue → websocket) with a virtualised table that renders 50k rows without stutter, plus saved views per team.

    How it shipped

    Weekly releases behind feature flags, old reports kept alive until the new numbers matched for two weeks.

    Result: report latency dropped from ~24h to under 4s; the spreadsheet was retired in a month and two other teams adopted the saved views.

    Next.jsWebSocketPostgreSQLRedis
    Live demo Code Write-up

  • AI content studio

    2025 · solo build
    Problem

    A two-person marketing team rewrote the same product copy for every channel, by hand, every week.

    What I built

    An editor with reusable brand-voice presets, streaming generations, and a diff view so nothing published without a human approving it.

    How it shipped

    Started as a CLI the team already trusted, then grew a UI once the prompts proved stable.

    Result: first drafts became minutes instead of hours; the team doubled published variants per week with the same headcount.

    TypeScriptNode.jsStreaming SSEDocker
    Code Write-up

  • E-commerce checkout rebuild

    2024 · agency project
    Problem

    Checkout dropped three of four carts on mobile, and every UI change risked breaking payments.

    What I built

    A three-step checkout with optimistic validation, retry-safe payment intents, and typed contracts shared between client and API.

    How it shipped

    A/B tested on 10% of traffic first, with alerts on every payment state so a bad release could be reverted in minutes.

    Result: mobile checkout completion up ~28% over eight weeks, payment-related support tickets cut roughly in half.

    ReactZodPayments APIPlaywright
    Case study

03 — Tech stack

Tools I reach for by default.

  • Frontend

    TypeScriptReactNext.jsTailwindSvelte

  • Backend & data

    Node.jsPythonPostgreSQLRedisGraphQL

  • Tooling & infra

    DockerAWSGitHub ActionsViteVercel

04 — Journey

The road so far.

  • Senior Software Engineer

    Product team · remote

    Leading frontend architecture for a data-heavy product, mentoring two engineers, and owning the release pipeline end to end.

  • Full-stack Developer

    Digital agency

    Delivered a dozen client builds — commerce, dashboards, internal tools — usually as the only engineer on the project.

  • Frontend Engineer

    Startup · 15 people

    Rebuilt a legacy interface into a component system that cut new-feature time roughly in half.

  • Started coding seriously

    Self-taught, then formal training

    First paid work was a small business site that still runs today — that project is why I care about maintenance, not just launch day.

05 — Contact

Let's build something together.

I'm open to product work, contract builds, and interesting problems. Tell me what you're making and what's blocking it.

hello@tadashi.tech
TelegramGitHubXLinkedInInstagram