Backend / Platform / Geospatial

Duc Huynh buildssystems that hold up.

Production engineering across APIs, data, infrastructure, maps, and the workflows between them.

View work Download resume

Duc Huynh sitting by a cafe window — Duc HuynhSoftware Engineer

3 daysInitial city map implementation

50,000Approximate first-week visitors

End to endRequirements through production operation

Work that left the prototype.

Public infrastructure, commercial platforms, and independent products used beyond the development environment.

New Da Nang City Map

Software Engineer

A public mapping platform created after Da Nang's administrative reorganization.

Built the React and Vite frontend with Google Maps, optimized for fast access to city-wide geographic information.

Initial release in about 3 days. About 50,000 unique visitors in week one.

React / Vite / Google Maps / Geospatial data

Visit Mauritius Paradise

Full-stack Developer and Technical Consultant

A complete travel platform for a Mauritius-based transfer and tour business.

Designed the website, booking flows, landing-page structure, performance work, and technical SEO around real transport operations.

Full-stack / Booking workflows / Technical SEO / Performance

TimBoss

Founder and Developer

A community product that helps pet owners in Vietnam search for lost animals.

Owned the product concept, full-stack implementation, database, deployment, infrastructure, and ongoing maintenance.

Product / Full-stack / Database / Infrastructure

How I work

One system, not a pile of parts.

I follow information from the interface to the infrastructure and back to the people operating it.

View Mermaid syntax

flowchart TB
  I["INTERFACE"] --> A["API"]
  A --> D["DOMAIN + STATE"]
  D --> F["DATA + INFRASTRUCTURE"]
  A --> P["PARTNER SYSTEMS"]
  D --> E["EVENTS"]

Read across boundaries. Keep the state explicit.

Public systems need useful speed.

At Da Nang IOC, I worked across map interfaces, Go services, IoT ingestion, and public monitoring for rain and flooding.

Interfaces and pipelines connected to real public-service operations.

State belongs in the design.

At TravelThru, I build transactional booking, driver, supplier, and synchronization workflows with explicit state transitions.

DDD-oriented services backed by MongoDB, PostgreSQL, Redis, and database transactions.

The edge cases are the integration.

I map partner APIs, timezones, webhooks, errors, and operational exceptions into workflows teams can run reliably.

From technical scope and estimation through production delivery and troubleshooting.

Experience

Jul 2025

Da Nang City Intelligent Operations Center

Software Engineer, Geospatial and Public-Service Systems

Built public-facing geospatial and monitoring software for city services.

React interfaces for a city-wide map and rain and flood monitoring
Go ingestion services for distributed IoT rain stations
High-frequency sensor validation, processing, and persistence

Oct 2023 - Present

TravelThru

Software Engineer, Backend and Platform

Work across backend services, travel workflows, integrations, automation, and production infrastructure.

Transactional booking, driver, and supplier workflows
Partner API architecture, webhooks, pagination, and state mapping
Docker, Linux, Coolify, Cloudflare, reverse proxies, and production debugging

Education

BTEC FPT College of Danang

Information Technology, 2024

Good, GPA 3.2 / 4.0

Certification

JavaScript Intermediate

HackerRank, November 2023

View certificate

A practical toolkit.

Languages and platforms change. The constant is choosing what fits the system, team, and operating conditions.

Languages

TypeScript / JavaScript / Go / PHP / Java / C# / SQL

Backend and data

Node.js / NestJS / Laravel / PostgreSQL / MongoDB / MySQL / Redis

Web and maps

React / React Native / Expo / Vite / Google Maps / Mapbox / PostGIS

Infrastructure

Docker / Linux / AWS EC2 / Coolify / Nginx / Cloudflare / n8n

Read the whole system

Application code, databases, APIs, infrastructure, and operations are one problem surface.

Own the path to production

I am comfortable moving from requirements and architecture to delivery, debugging, and maintenance.

Use architecture to remove friction

Patterns matter when they make state clearer, failures safer, and operating work simpler.