Profile system

Nguyen Linh Khang

Born in 1995, based in Hanoi.

I work around the place where technical design, product decisions, and delivery discipline meet. I care about how systems are designed, how products behave in real use, and how clear notes make decisions less vague.

General model

A compact profile

A personal operating model built from architecture work, product context, planning, writing, and a preference for clear execution.

Identity

Nguyen Linh Khang. Born in 1995. Living and working from Hanoi.

Operating style

I like work that is structured, direct, and followed through until it becomes usable.

Craft

Software, architecture, product details, and the tradeoffs behind them.

Writing

I write to organize thinking, record decisions, and make complex work easier to revisit.

Principles

Simple where possible, durable where needed, and always checked against real use.

Identity

Nguyen Linh Khang. Born in 1995. Living and working from Hanoi.

Background in full-stack development, team leadership, and delivery management.
Current direction: solution architecture, technical PM, and presales for practical systems.
Comfortable working with international teams, especially Japan-facing projects.

Operating style

I like work that is structured, direct, and followed through until it becomes usable.

Turn unclear requirements into scope, flows, risks, and a delivery plan.
Estimate both development effort and infrastructure cost before the team commits.
Keep documents useful: SRS, basic design, proposal, and decision notes.

Craft

Software, architecture, product details, and the tradeoffs behind them.

Web, mobile, AI, realtime, queues, dashboards, and data-heavy operation tools.
Choose technology by cost, performance, team fit, and maintainability.
Design systems that can be shipped, operated, measured, and revised.

Writing

I write to organize thinking, record decisions, and make complex work easier to revisit.

Notes are a working tool, not a performance of certainty.
Good writing makes assumptions, constraints, and tradeoffs visible.
This blog keeps reusable lessons from delivery, architecture, and product work.

Principles

Simple where possible, durable where needed, and always checked against real use.

Prefer a small system that the team understands over a large one nobody owns.
Make the happy path clear, then handle the operational edge cases carefully.
Verification matters: prototypes, tests, demos, metrics, and real user feedback.

What tends to stand out

The shape behind the work

The useful pattern is not a single domain. It is the habit of entering messy problems, separating the moving parts, and turning them into work a team can build.

01 / Ambiguity

Good at reading unfinished problems

I usually start before the brief is clean: identify the real users, hidden constraints, risky assumptions, and the smallest version that can prove the direction.

02 / Bridge

Business language into technical shape

I am comfortable moving between stakeholder conversations, product flows, architecture diagrams, estimates, and implementation tradeoffs.

03 / Delivery

Not just design, also landing

A design is only useful when it survives planning, backlog cuts, QA, release pressure, operational edge cases, and the first real users.

04 / Range

Wide domains, same operating method

Golf AR, clinics, HR, AI, logistics, booking, ERP, and realtime dashboards look different, but they all need clear models, ownership, and feedback loops.

Selected anonymous work

Selected problem spaces

The details below are intentionally anonymized. They describe scope, system concerns, and responsibility, not the client or company behind the work.

AR / mobile

Golf practice and management systems

A mobile and operations system around golf booking, member management, tournament workflows, and AR-assisted practice analysis.

Designed flows for tee-time booking, membership, tournament operations, and player progress.
Worked with AR-based distance or shot tracking so practice data could become visible and reviewable.
Balanced mobile interaction, realtime updates, operational dashboards, and maintainable backend services.

Operations

Clinic management platform

A clinic operations platform that connects patient flow, payment, medical records, customer-care work, and external service integrations.

Mapped appointment, reception, payment, medical record, follow-up, and care-team workflows.
Planned integrations with inbox, commerce, and payment tools without binding the system to one vendor.
Separated clinical records, customer context, permissions, reporting, and operational dashboards.

AI / analytics

Conversation analysis and AI assistants

Systems that analyze customer-care conversations, assist marketing or sales teams, and generate text, image, video, or slide assets.

Designed evaluation flows for customer-care conversations: tags, quality signals, summaries, and follow-up insights.
Connected AI features to real workflows instead of treating them as isolated chat boxes.
Worked with multi-agent or automation flows for content, slides, media generation, and cross-channel publishing.

Product platforms

HR and internal operation apps

Web and app products for internal HR and operational teams, built around clearer employee, request, approval, and reporting flows.

Translated internal work habits into product flows that non-technical teams could use repeatedly.
Handled roles, permissions, approval states, notifications, and admin surfaces.
Kept organization and client identities private while preserving the system lessons that matter.

Commerce / ERP

Marketplace and inventory automation

Automation systems for syncing orders, stock, business dashboards, and operational queues across multiple sales channels.

Designed order synchronization, inventory updates, queue handling, and failure recovery paths.
Used realtime dashboards to make business state visible to operators.
Separated platform-specific integrations from internal inventory and reporting logic.

Realtime / logistics

Booking, warehouse, and realtime operation tools

Systems where users need current state: restaurant reservations, warehouse logistics, vehicle or spatial tracking, and operational reporting.

Modeled capacity, slots, inbound/outbound movement, status changes, and realtime visibility.
Worked across dashboards, mobile or desktop clients, backend services, and data pipelines.
Kept attention on operational correctness, not only the screen that users see first.

Privacy note Client names, company names, and confidential business details are not published here. I only describe public-safe problem types and responsibilities.

How to read this site

This blog is a place for notes that are practical enough to reuse: system design observations, product decisions, delivery habits, and small technical lessons that were worth writing down.

Read posts