Menu
Theme

Years I contributed:2024Digital currency · Operations platform

CBDC

Shared front-end architecture for digital-currency administration, participant accounts, and transfer workflows.

My role
Front-end architecture & team leadership
Context
Soramitsu · Technical direction, review & delivery
Explore the project

The CBDC platform gives administrators and participating institutions separate browser interfaces for issuing assets, managing banks and accounts, and handling transfers. Related applications also support bond workflows.

At Soramitsu, I was responsible for front-end architecture, code review, and team delivery. The team implemented the operational workflows across these applications, using shared Vue and TypeScript packages.

Built with
VueTypeScriptVitePiniaSoramitsu UI KitSCSS

Inside the product

Recreated currency balances and asset-issuance controls in the CBDC administration interface.

Administration and issuance

Administrators manage issuance and operational controls; participating institutions use related account and transfer interfaces. I led front-end architecture and review across that shared codebase.

A reconstructed bond-creation form with illustrative issue and payment terms.

Another workflow on shared foundations

The codebase also supports bond workflows. Shared components and tooling let the applications reuse common foundations while retaining the fields and actions each workflow needs.

  • Architecture across related applications

    Owned front-end architectural decisions for administration and participant applications, including the shared components and tooling they used.

  • Review and team delivery

    Led front-end delivery and reviewed the team’s implementation across the shared packages and individual applications. Worked with engineers to carry architectural decisions into the digital-currency workflows.

Reviewing a change across several applications

The same front-end packages supported interfaces with different responsibilities. An administrator could issue assets or manage institutions, while a participant worked with accounts and transfers. A change to shared functionality therefore needed review beyond the screen where it first appeared.

My architecture and review work covered that relationship between shared code and individual applications. I made cross-project effects part of the pull-request information, alongside the reason for a change, testing, edge cases, and potential risks. The reviewer checklist also asked engineers to check related areas when another project could be affected.

My work at Soramitsu

At Soramitsu, I grew from Senior Front-end Developer to Front-end Team Leader, then Head of Front-end Development. That progression covered work across banking, wallets, exchanges, and shared front-end infrastructure.

Career timeline January 2020–2026

  1. Head of Front-end Development

    May 2024–2026

  2. Front-end Team Leader

    January 2021–May 2024

  3. Senior Front-end Developer

    January 2020–January 2021

Broader responsibilities

Progressed from senior engineering to leading the front-end department, while continuing implementation and code review.

  • Created the front-end department and established its structure, engineering workflows, and quality standards.
  • Built shared design-system foundations and helped migrate projects to a common front-end technology stack.
  • Hired and mentored developers, coordinated roadmaps and delivery, and supported collaboration across product, design, and engineering.
  • Organized internal meetups and knowledge-sharing sessions, and contributed to technical direction across company projects.
Full CV
Start a conversation

What are you
working on?

An engineering role, a product to build, or a technical problem to work through. I’d like to hear about it.