Chanheng
Seang

Staff Software Engineer, Architect Team at Mbanq

I design the backend systems that move money: ACH, wire transfers, card processing, and the banking platforms behind them.

Portrait of Chanheng Seang

About

I'm a Staff Software Engineer with more than six years in fintech, enterprise backend systems, and payment platforms. My work sits where scale, security, and money meet: designing services that stay fast under load, pass SOC 2 and PCI DSS scrutiny, and integrate cleanly with core banking.

Day to day that means Java and Spring Boot, Go services on AWS Lambda, relational databases, and event-driven microservices, plus the architecture reviews and mentoring that help a team ship complex financial products with confidence.

Outside the core platform I build end to end: Python Telegram bots and Mini Apps that run a business's daily operations, Next.js middleware in front of Apache Fineract for loan officers, and LLM-powered tools that turn messages into structured records. I hold a Master of Science in Computer Science from Westcliff University.

Based in
Bothell, Washington, USA
Currently
Staff Software Engineer at Mbanq
Education
MS Computer Science, Westcliff University, 2026
Speaks
Khmer, Mandarin Chinese, English, some Spanish

Problem solving

Most of the problems I get are ones where money, compliance, and uptime pull in different directions. I start by mapping how the system fails before deciding how it should work, then look for the smallest design that holds up under those failures, and I write the reasoning down so the team can challenge it.

  • Start from the failure modes

    What happens when a partner bank times out, a message arrives twice, or a node dies mid-transfer? Those answers shape the design more than the happy path does.

  • Remove before adding

    No database, no session, no extra service unless it earns its place. Less state means fewer ways to be wrong about money.

  • Least privilege by default

    Services get exactly the permissions they need, and secrets and access are reviewed as part of the design, not after it.

  • Prove it, then decide

    When options are close, I build a small spike and measure it rather than argue from preference.

Problems I've worked through

Consumers need to see their account and card status during a bank event, exactly when upstream systems are most likely to be degraded.

Designed a stateless Go service on AWS Lambda that queries core banking and card management in parallel and returns partial results when one side fails, with typed errors mapped to clear HTTP responses. No database and no session state means nothing to corrupt or migrate under pressure.

Authentication lived inside the core banking platform, so it scaled with the platform and every new channel needed its own login.

Proposed moving identity out into a centralized Keycloak service with OAuth2 and SSO, so the core can scale on its own and new apps get single sign-on, MFA, and role-based access without touching the core.

A middleware app was talking to a live lending core using a service account with super-user rights.

Inventoried every API the app actually calls and replaced super-user access with a dedicated role holding only the permissions those calls need, covering client and loan creation and repayments.

A chat-based bookkeeping bot was a single process on one host, so any restart meant missed sales and expense messages.

Reworked it into an active-passive pair with a clean hand-over, and put the LLM parser behind its own client interface so the model provider could be swapped without touching the bot logic.

Search over large PostgreSQL-backed datasets was slow and limited to exact matches.

Evaluated Elasticsearch and OpenSearch side by side against real queries, then integrated full-text search while keeping PostgreSQL as the source of truth.

Technical skills

Arranged the way a payments platform is built: from the business domain down to the infrastructure it runs on.

  1. Payments domain

    The money movement I build for

    • ACH
    • Wire transfers
    • FedNow
    • ISO 20022
    • Card processing
    • Bank partner integrations
    • Core banking (Apache Fineract)
    • Lending and loan origination
  2. Architecture

    How the pieces fit together

    • Microservices
    • Modular monolith
    • Event-driven architecture
    • Serverless
    • REST API design
    • Architecture reviews
  3. Interfaces

    Where customers and staff meet the system

    • Angular
    • Vue
    • Next.js
    • React
    • Flutter
    • Telegram bots
    • Telegram Mini Apps
  4. Services

    Languages and frameworks I write in

    • Java
    • Spring Boot
    • Spring Data
    • Jersey (JAX-RS)
    • Go
    • Python
    • TypeScript
    • Node.js
    • Prisma
    • Zod
    • SQL
  5. Identity & security

    Who gets in, and what they can do

    • Keycloak
    • OAuth2
    • SSO
    • LDAP
    • RBAC
    • MFA
    • SOC 2
    • PCI DSS
  6. Data & search

    Where records live and how they're found

    • PostgreSQL
    • Oracle Database
    • RDBMS design
    • Elasticsearch
    • OpenSearch
    • LLM data extraction
  7. Cloud & infrastructure

    Where it all runs

    • AWS Lambda
    • Amazon ECS
    • API Gateway
    • Docker
    • Linux and systemd
    • Active-passive high availability
    • On-premise migration

Across every layer: Technical leadership, Problem solving under constraints, Mentoring engineers, Design reviews, Scrum (PSM I), Working with AI coding agents, Cross-team delivery.

Experience

  1. May 2023 – present

    Staff Software Engineer, Architect Team

    Mbanq, Washington, USA

    • Contribute to architecture design and technical leadership for enterprise-grade fintech and banking platforms.
    • Design and implement scalable, high-performance backend systems using Java, Spring Boot, AWS, and serverless technologies.
    • Lead architecture decisions for payment systems, including ACH, wire transfers, and card processing workflows.
    • Drive improvements in scalability, security, compliance, and operational reliability in SOC 2 and PCI DSS aligned environments.
    • Support modernization work: platform modularization, authentication redesign, and infrastructure transition planning.
    • Work across engineering, product, and operations on architecture reviews, integration design, and delivery of complex financial products.
  2. Before May 2023

    Backend Team Lead / Senior Backend Developer

    Mbanq, Cambodia, remote

    • Led backend development for fintech platform features and services.
    • Built and maintained microservices and backend APIs for banking and payment operations.
    • Improved system performance, reliability, and development processes across engineering teams.
    • Mentored developers, reviewed designs, and supported delivery of business-critical solutions.

Selected projects

Authentication modernization

Moving authentication out of the core platform into a centralized Keycloak identity service, for better scalability and single sign-on.

Keycloak, SSO, OAuth2

Consumer lookup service for bank events

A stateless Go service on AWS Lambda that lets consumers check their account and card status during a bank event, fanning out to core banking and card management and returning partial results when one side is down.

Go, AWS Lambda, API Gateway, Compliance

Real-time payments in Go

Services for FedNow instant payments and ISO 20022 message handling, alongside webhook processing for sub-ledger balances.

Go, FedNow, ISO 20022

Loan officer app on Apache Fineract

Next.js middleware and mobile-friendly app in front of a microfinance lender's Fineract core: client search, loan creation, and repayments behind a least-privilege service role.

Next.js, Prisma, Zod, Apache Fineract

Office automation on Telegram

Attendance, shifts, leave, working days, and holiday rules for a multi-location business, run through Telegram bots and a Vue Mini App admin, with a layered Python backend.

Python, python-telegram-bot, Vue, Telegram Mini Apps

Chat-to-ledger bookkeeping bot

A Telegram bot that reads sales and expense messages, parses them with an LLM into structured entries, and keeps running balances, deployed as an active-passive pair for uptime.

Python, LLM, Telethon, High availability

Cloud to on-premise migration

Planning how platform components move from AWS cloud infrastructure to on-premise environments without disrupting operations.

AWS, Infrastructure, Migration

Full-text search

Implemented and evaluated Elasticsearch and OpenSearch alongside PostgreSQL-backed systems.

Elasticsearch, OpenSearch, PostgreSQL

Education and certifications

  • Master of Science in Computer ScienceWestcliff University, United States. Graduated April 2026
  • Bachelor's degree in Computer ScienceDali University, China

Languages

  • KhmerNative
  • Chinese (Mandarin)Professional
  • EnglishProfessional working
  • SpanishBasic
  • Professional Scrum Master I (PSM I)Certified
  • Oracle Certified Professional, Database 11gCertified
  • Oracle Certified Associate, Database 11gCertified

Let's talk about payments, platforms, or architecture.

chanheng.sng3@gmail.com