BankingActive Solution Architect 2026 — now Phnom Penh, Cambodia
Architecture that has to answer to a regulator.
Banking systems don't get to move fast and break things. As Solution Architect I own technical design for systems where security, compliance, and auditability are entry requirements, not features — translating business goals into architectures that engineers can build and a regulator can approve.
What made it hard
Regulatory and compliance standards are hard gates — a design that can't pass security review doesn't get built
Business, risk, and engineering stakeholders each hold real veto power over a design
Changes land in systems that move real money — rollback and failure paths are part of the design, not an afterthought
The flight plan
Lead the architecture of scalable, secure, high-performance banking services
Translate business needs into technical designs with explicit security and compliance checkpoints
Review code and architecture across teams to hold one engineering standard
Mentor engineers so the standard survives without me in the room
Evaluate emerging technologies before they get anywhere near production
What held
- Designs arrive at build-ready with security and compliance addressed up front — not retrofitted after review bounces them
- A shared architecture-review standard across teams, so audits bring fewer surprises
- An ongoing engagement — this is the day job that keeps my freelance work sharp
Debrief
JavaSpring BootMicroservicesDockerKubernetesCI/CDDatabase Design
MicroservicesDefense in depthDesign-review gatesExplicit failure paths
Details are anonymized to respect confidentiality — the patterns are real, the internals stay private. Happy to go deeper on the architecture in a call.
Have a mission like this?
One freelance slot per quarter — the same rigor, on your product.