BH

Software engineer · Vietnam

I build softwarepeople can rely on.

Product-minded engineering across the stack — from accessible interfaces and maintainable systems to the details that make software feel fast.

Portrait placeholder for Bao Gia Huynh
Portrait / 01

Bao Gia Huynh

Software EngineerVietnam · UTC+7
engineer.ts

const engineer = {

name: "Bao Gia Huynh",

focus: ["product", "systems"],

values: ["clarity", "quality"],

status: "Open to work"

};

Currently exploring

Scalable web architecture & thoughtful developer experience

Full-stack

Product engineering

Type-safe

By default

UTC+7

Vietnam based

Selected work

Proof over promises.

A growing collection of products and engineering explorations. Each case study focuses on the problem, the decisions and the result.

Expertise

How I contribute to a team.

01

Product engineering

Translate ambiguous product needs into clear, maintainable features with sensible scope and fast feedback loops.

DiscoveryUI engineeringIteration
02

System thinking

Design boundaries, data flow and component APIs that stay understandable as the product and team grow.

ArchitectureType safetyAPIs
03

Quality & performance

Treat accessibility, testing and speed as product features—not cleanup work saved for the end.

Web vitalsA11yTesting

Engineering journey

Always learning, always shipping.

Now

Building production-minded web experiences

Deepening full-stack architecture, performance and product craft through hands-on projects.

Ongoing

Learning in public

Turning experiments into documented decisions, reusable patterns and useful case studies.

Next

Joining an ambitious engineering team

Looking for an environment with strong ownership, feedback and meaningful technical challenges.

About

Careful thinking. Practical execution.

I’m Bao, a software engineer who enjoys turning unclear problems into simple, dependable products. I care about code that is easy to change, interfaces that are easy to use and teams that communicate clearly.

  1. Understand the user and constraints before choosing the technology.
  2. Make the simple path obvious—for users and for the next engineer.
  3. Ship, measure and improve instead of polishing assumptions forever.
OwnershipClarityCuriosityCraftContinuous learning

Let’s build

Have a problem worth solving?

I’m open to software engineering roles and collaborations where quality, ownership and continuous learning matter.

Send an email

The GitHub noreply address is temporary — replace it with your preferred public email.