Skip to content
Jimmy Hwang
Available from Q4 2026 · contract or fixed price

Your hire takes six months. Your roadmap can't wait.

Senior TypeScript engineer on contract. I build and run PartyX alone: six apps, live payments, pipelines and the cloud under them. You get that person from week one, for as long as the gap lasts.

Remote: EU hours or US East Coast overlap On-site in Berlin B2B invoice, EUR or USD

partyx.info
PartyX guest app on desktop: events happening now in Berlin
PartyX iOS app: your ticket QR code
Payments liveStripe, checkout to refund
One person on callTwo years. No outsourcing

Stack

TypeScriptReactNext.jsVue 3NuxtReact NativeNodeGraphQLNestJSPostgreSQLSQLiteStripeCloudflare WorkersVercelAWSGitHub ActionsPython
6apps, one person
6,000+commits since 2024
10,000+events kept fresh
50+organizers
8cities
Why me, not the usual options

Three ways to fill the gap. One person who has already done the hard part.

Instead of an agency

The person on the call writes the code

  • You pay for a team, the work goes to whoever is free
  • One senior engineer who writes and reviews every line
Instead of a platform freelancer

Owned production, not just features

  • Most have shipped tickets inside someone else's system
  • Two years running payments, refunds and on-call for my own product
Instead of waiting for a hire

Starts in weeks, ends cleanly

  • Months to find, a notice period on top, then onboarding
  • Contract starts fast and hands over when your permanent hire arrives

Start with two paid days.

One real ticket from your backlog. You see the code, the review notes and the questions I ask. Then decide.

Book a trial

The operator console I own at WiTTRA Networks is used every shift at Stockholm Arlanda Airport, Eramet and ArcelorMittal.

The platform, in plain words

What one person runs.

Every screen is live, or in App Store review.

Guest app

Find tonight, buy, show at the door.

Open partyx.info

iOS app

Launching soon.

Host console

Create, sell, scan, get paid.

Back-office

Refunds, payouts, the ledger.

Onboarding

Claim your venue in minutes.

Ingestion

10,000+ events kept fresh, 8 cities.

Three databasesCore, search, back-office, kept apart

Object storageLike S3. Posters, images, caches

Queues with retriesEmail, images, tickets in the background

PaymentsStripe, checkout to refund

Automated releasesTested and shipped by pipeline

One person on callTwo years. No outsourcing

All of it runs on Cloudflare's global network.Five services, 300+ cities, no servers to patch. The same design ports to AWS or Google Cloud.

Built for 2026

AI writes the code now. The job is knowing when it is wrong.

Frontend

React, Next.js, Vue, React Native, design systems, realtime UI. The guest app and the industrial console.

Backend

APIs, data models, background jobs, payments, auth. Less time in Java and Go.

Cloud and operations

Cloudflare, Vercel, AWS basics, pipelines, monitoring. Not my lane: Terraform, Kubernetes, very high traffic.

The bottleneck moved

Review, not typing

With agents in the loop, pull requests run about 50% larger and wait around four times longer for a reviewer. I am the reviewer who also ships: agents draft, I own every line that reaches production.

Where agents fail

The unhappy path

They build the checkout that works and miss the refund that should not be allowed. PartyX's payments, payouts and refunds are exactly that code, live for two years with real money on it.

What one person means now

Deciding, not generating

Six apps in 22 months is not typing speed. It is choosing what to build, what to reject and what to delete, then carrying the pager for the result.

Why it matters 45% of AI-generated code ships with a known security flaw (Veracode, 2026). Somebody has to be the other half.

Fixed price

Need payments or ticketing built, not a contractor?

The same system PartyX runs on, built for your product. Scoped in writing, delivered in about four weeks.

Payments and ticketing backend, in four weeks.

Checkout, refunds, payouts and the ledger behind them, on Stripe and Cloudflare or your existing cloud. The unhappy paths included, because that is where money goes missing.

  1. Week 0One scoping call. You get a written scope and a fixed price within two business days.
  2. Week 1–2Checkout, webhooks, refund rules. Demo on your staging at the end of week two.
  3. Week 3–4Payouts, ledger, tests, runbook. Handover session with your team.
From €20,000Fixed price, set in the written scope. 50% to start, 50% on handover.
  • Your repository, your accounts, your code from day one
  • Tests for refunds, disputes and failed payouts
  • 30 days of fixes after handover, at no charge
Scope a fixed-price build
Proof

Check it yourself.

Work

Two products in daily use.

PartyX Founder

Problem
Small organizers could not sell tickets cheaply or be found.
Did
Built and run the whole platform: six apps, payments, ingestion, cloud.
50+ organizers, 10,000+ events · one operator, two yearsNext.jsCloudflareStripe
2020 – now

WiTTRA Networks Senior Software Developer

Problem
Operators at airports and mines needed every asset live, without calling support.
Did
Own the operator Console end to end, plus the realtime API under it.
Used every shift at Arlanda, Eramet, ArcelorMittal · continuous releases since 2023Vue 3NuxtGraphQL
2023 – now

PartyX rebuild

Six apps, 6,000+ commits, nights and weekends
2024 – now

Enklare, Stockholm

TypeScript / NestJS product work
2023

PartyX v1

First version, first paying organizers
2020 – 22
Off the record

What the CV leaves out.

Before codeRan a 40-bed hostel in Montpellier for three years. That is where the product sense comes from.
LanguagesEnglish, French, Korean. German enough for stand-up.
Working styleDirect. Writes the decision down before the code.
Says no toSelling what I have not shipped.
Send a brief

The five things I will ask anyway.

Answer here, skip the first call. Written yes or no within one business day.

Prefer email? founder@partyx.infoPrefer a CV? One page, PDF

Goes to one inbox. Nothing else.