About

I am a backend-first engineer based in Ho Chi Minh City, Vietnam.

The kind of systems I enjoy most are the ones that have real operational weight behind them: approval flows that people depend on, marketplace backends that have to coordinate multiple moving parts, analytics pipelines that turn raw activity into something decision-makers can use, and AI features that need to fit into a product instead of living as a demo in isolation.

That is the thread running through most of my work. I am less interested in building isolated features than in shaping the underlying system that makes a product reliable, understandable, and scalable over time.

Overview

My background started with backend development in ASP.NET Core, then gradually expanded into event-driven architecture, cloud deployment workflows, analytics systems, and practical AI integration. What ties those areas together for me is not the technology itself, but the kind of responsibility they require. Once a system touches approvals, payments, notifications, infrastructure boundaries, or machine-generated decisions, the backend stops being an invisible layer and becomes the place where product trust is actually built.

I learn the most from environments where business rules are messy, system boundaries matter, and reliability is part of the user experience. Those are the projects that force better engineering judgment, not just more implementation.

Focus Areas

• Workflow-heavy backend systems where state, auditability, and business rules matter as much as feature delivery.
• Distributed and cloud-native architectures using tools such as Kafka, YARP, SignalR, and AWS serverless services.
• Applied AI in product contexts, especially when a model needs to be integrated into a usable end-to-end workflow.
• Operationally meaningful integrations across payments, notifications, geolocation, media storage, and analytics.
• Product engineering that stays grounded in real constraints instead of stopping at a technical prototype.

Experience Snapshot

At Amazon Web Services, through the FCAJ program, I worked on a clickstream analytics platform that combined ingestion, scheduled transformation, internal data access boundaries, and dashboard-ready output. What stayed with me from that experience was not just the AWS stack itself, but the discipline of thinking about pipelines as systems that must be safe to operate, repeatable to deploy, and understandable to the people using the output.

At FPT Software, I worked on the Claim Request System, a workflow-driven internal platform for financial approvals. That project sharpened a different side of my engineering mindset: how to model state transitions carefully, how to make business rules explicit, and how to turn a manual operational process into software that people can trust across departments.

Across personal and team projects, I kept moving in that same direction. AlohaMarket pushed me deeper into service boundaries and event-driven design. EzyFix made payments, settlement, and operational coordination more concrete. SnakeAid pushed me to think about how AI should support a real product workflow rather than sit beside it as a separate experiment.

Education & Certifications

I am studying Software Engineering at FPT University, Ho Chi Minh City Campus, with expected graduation in June 2026.

Along the way, I have also used certifications as a way to strengthen fundamentals around delivery, process, and engineering discipline instead of treating them as credentials alone.

Selected certifications include:

• LFS167: Introduction to Jenkins - The Linux Foundation
• Project Management Principles and Practices Specialization - UC Irvine
• Java FullStack Developer Specialization - Board Infinity
• Software Development Lifecycle Specialization - University of Minnesota

Selected Timeline