Digital Health • Telecom • Operational Platforms
My strength is production systems integration.
I've worked on platforms where the challenge wasn't just building screens or endpoints, but keeping real-time operational state trustworthy across mobile, backend, data stores, and external systems.
8 years across healthcare IoT, telecom, and real-time payment infrastructure. The common thread is systems where product behavior depends on more than one service, device, or state model being right at the same time.
Remote. UTC+7. Working across AU, EU, and US teams.
How I think about this
Most software looks straightforward until the real problem appears: state lives in more than one place, different systems disagree, and the user still expects the product to feel clear and reliable.
That is the kind of work I know well.
The systems I've worked on are usually the hard end of product engineering: live telemetry, role-based workflows, payment state, external integrations, and user-facing decisions that depend on accurate data.
What matters to me is not just shipping features, but giving each moving part a clear responsibility so the whole product holds up in production.
Selected Work
Proof from systems with real operational complexity.
These projects span healthcare IoT, telecom, and real-time payment infrastructure. Each one involved multiple systems that had to stay aligned in production.
A Norwegian care platform needed to turn noisy sensor telemetry, caregiver actions, alarm state, and operational rules into a live resident view that staff could actually trust during care decisions. The challenge was not just IoT ingestion, but keeping real-time operational state trustworthy across mobile, backend, data stores, and external systems.
- • 5 coordinated codebases across backend, ingestion, processing, web, and mobile
- • Azure Event Hubs, Cosmos DB, Redis, Flutter, and Azure AD in one production platform
- • Multi-tenant RBAC, live caregiver workflows, and 10+ external integrations
Banglalink's super-app had to serve millions of users across telecom, payments, offers, loyalty, and partner flows inside one product experience, on devices with real performance and storage constraints. The hard part was not shipping more screens, but keeping a large, stateful mobile product reliable as business complexity, user scale, and integration surface kept growing.
- • 10M-user telecom super-app with payments, loyalty, campaigns, and deep-link flows
- • 192 REST endpoints and 9 business domains inside one Android client
- • High-scale mobile state, multi-account context, and rollout complexity in production
A fuel and payment platform had to coordinate mobile payment state, backend workflows, and physical fueling equipment across two consumer brands without letting those systems drift out of sync. In practice, the product was only as good as its ability to keep operational truth consistent when money, devices, and real-world actions all met at once.
- • Physical and digital state kept in sync across mobile, backend, and fueling hardware
- • Kafka, Redis, Keycloak, and multi-role flows across a white-label multi-brand platform
- • Payment, dispute, and reconciliation logic built into real operational workflows
Worth a conversation?
Work where the hard part is in the system, not just the interface.
I'm most useful in products where mobile, backend, data, and integrations all affect the user-facing outcome.
If you reach out, a short note on what you're building is enough.