/ Experience

Fiveyearsshippingfintech,AIandWeb3allofitinproduction.

None of it was a demo — live users, real balances, and every release had to hold.

/ Keep scrolling

  1. May 2023 - Present

    Nanovest

    Jakarta, Indonesia / Remote

    Frontend Engineer

    • Multi-chain Web3 wallet — Ethereum, Solana, Base, BNB — on Dynamic Labs, wagmi and viem: no seed phrase, gas-free, CCTP deposits under 20 seconds, ~$50k a day in trading volume.
    • Built 24K, a licensed tokenized-gold platform, end to end: Next.js over a multi-tenant NestJS core, ledger and pricing across 10 services.
    • Owned delivery too: Jenkins pipelines, GCP, and the releases themselves — branch to production, no hand-off.
    • Built the team's AI tooling: 52 MCP tools driving agents that spec-check branches, heal Playwright suites and review PRs — 687 QA findings in H1 2026.
  2. May 2022 - May 2023

    Techconnect

    Jakarta, Indonesia / Remote

    Full Stack Developer Trainee

    • Developed StarAM asset management dashboard tracking 5+ mutual fund products with daily fund flows, used by 10+ asset managers.
    • Built full-stack applications during 12-month training using React.js, React Native, Golang, and PostgreSQL with RESTful API design and unit testing.
  3. Dec 2021 - Mar 2022

    BNI

    Jakarta, Indonesia / Remote

    IT Business Partner

    • Bridged communication between international treasury department and development team by translating requirements into 20+ technical documents including use case diagrams, activity flows, and mockups.
  4. Jun - Dec 2021

    BNI

    Jakarta, Indonesia / Remote

    UI/UX Designer

    • Designed 50+ app pages and the design system behind them: custom UI assets, illustrations, and a reusable Figma component library for web and mobile.

/ Worked with

Nanovest, Obox Systems, Techconnect, Bank Negara Indonesia, Bank Rakyat Indonesia, Sinarmas Mining, Harisenin, 4nesia

/ What carried forward

None of it was put down.

  1. From the design year

    A screen that will not work dies in the file, not in code review. That is the cheapest place to be wrong, and after 50+ pages and a component library it is still where I start.

  2. From the analyst year

    I write the spec I will be held to. Twenty-plus of them for a treasury desk that did not speak engineering — so ambiguity gets settled on paper, by the person who then has to build it.

  3. From the code years

    Building it taught me what not to draw. A screen I cannot ship does not get designed, and a spec I cannot build does not get written — the last five years are what makes the first two honest.