SA.

Experience

From technical leadership to architecture ownership: building systems that survive load, failure, changing data, and real production constraints.

Career timeline

  1. Technical Lead

    FPT Software

    • Leading technical direction for a delivery team migrating a legacy healthcare platform to microservice and distributed architecture.
    • Applying CQRS and Saga patterns to manage distributed command flows and multi-service transaction compensation.
    • Integrating Azure AI Foundry Agent Service, Document Intelligence (OCR), and Content Understanding for AI-powered clinical workflows.
    • Working within an 8-team program (~56 engineers) spanning backend, frontend, QA, and delivery roles.
    • Core stack: .NET, Angular, SQL Server, Azure — structured for scale and compliance in the healthcare domain.
  2. Senior Software Engineer

    FPT Software

    • Contributed to distributed healthcare services using .NET and clean architecture in a large-scale program.
    • Applied CQRS to separate command and query paths across microservice boundaries.
    • Worked with Azure cloud infrastructure including OCR pipelines for clinical document ingestion.
  3. Software Architect

    DFT

    • Designed scalable data platforms processing academic data for Japanese institutions.
    • Built systems used in 20+ classrooms through a STEM robotics platform.
    • Focused on scalability, maintainability, and performance.
  4. Technical Lead

    DFT Technology

    • Led 10+ engineers across telecom, government, and LMS systems.
    • Designed and deployed a nationwide Network Monitoring System managing 1000+ nodes.
    • Built a citizen data system handling 10M+ records with 99.9% uptime.
    • Delivered LMS, CRM, and chatbot platforms end-to-end.
    • Improved system reliability and delivery speed through architecture and engineering standards.
  5. Team Lead

    DFT Technology JSC Company

    • Used React JS to build new web analytics report interfaces on top of existing web applications.
    • Worked closely with database engineers to build intelligent analytics reporting with AngularJS and ASP.NET for a mobile telecom customer with multi-source big data.
    • Improved report page speed by about 10%, reducing report wait time for average users by roughly 1 to 2 minutes.
    • Contributed across the full software development life cycle, from customer requirement gathering through build, test, and maintenance.
  6. Web Developer

    DFT Technology JSC Company

    • Built customer-requested features with ASP.NET Boilerplate in an existing application.
    • Practiced reading established code, following project conventions, and delivering maintainable changes.
  7. Junior Web Developer

    DFT Technology JSC Company

    • Learned professional development habits in a full-time team environment.
    • Worked on a healthcare management module customized around customer requirements.
  8. Associate Degree, Computer Science

    Ha Noi Vocational College Of Technology

    • Studied computer science fundamentals before moving into full-time web development.
    • Built the learning base that later supported backend, frontend, and architecture work.
  9. Self-educated

    Continuous learning

    • Kept learning beyond formal education and job responsibilities.
    • Used each role as a chance to improve communication, system thinking, and software craftsmanship.

Skills by production system layer

Backend, data, frontend, DevOps, and the operating mindset behind scalable systems.

  • Infrastructure

    • Multi-environment topology, network boundaries, and capacity guardrails for .NET and React workloads.
    • Kubernetes-style isolation, progressive delivery, and failure-domain thinking for stateful dependencies.
  • Backend

    • .NET service boundaries, CQRS-style command paths, and API design where idempotency and versioning are explicit.
    • Workflow and outbox patterns for side effects—replay, compensation, and operator-visible stuck states.
  • Data

    • PostgreSQL as authoritative store: constraints, migrations, and contention-aware schema evolution.
    • Read models, integration offsets, and reconciliation when external systems are eventually truthful.
  • DevOps

    • Pipelines, infrastructure-as-code discipline, and safe rollbacks—treating deploy risk as an architecture concern.
    • SLOs, structured logging, tracing, and alert budgets so on-call reacts to journeys—not noisy pods.