Hello, I'm

Hoàng Đức Mạnh.

A Control and Automation graduate from HUST, drawn to the boundary where hardware and software meet.

Embedded control board with cable harness and diagnostic LEDs
Embedded LinuxOTA rollbackPOSIX IPCFPGA I/OProduction systems

Choose your reading depth

The same work, framed for a fast scan or a technical review.

Scan ownership, outcomes and experience first.

Operating principles

How I make systems understandable before I make them faster.

Measure before guessing

Trace behavior across the hardware and software boundary before changing code.

See the FPGA system case

Design for recovery

Treat rollback, watchdogs and heartbeats as core behavior, not cleanup work.

Open the OTA lab

Test the failure path

Exercise network, verification and health failures before the system reaches production.

Inject a failure

Capability evidence

Filter the matrix to connect each capability with shipped work.

Capability What I shipped Evidence

Selected work

Production work explained through ownership, constraints and decisions.

Firmware System Manager

Case study on this page

What I owned

Embedded Linux firmware controlling gimbal, camera, lens and laser subsystems.

Constraint

Coordinate FPGA I/O and multiple hardware interfaces inside a multithreaded system.

Decision

Use POSIX threads, typed Protobuf messages and explicit watchdog and heartbeat paths.

Evidence

TCP/IP, pipes, message queues, FPGA mmap and UART formed the system boundary.

Architecture Replay

Step through a command from service input to supervised hardware control.

  1. HPC command
  2. TCP/IP + Protobuf
  3. System manager
  4. IPC and device control
  5. Heartbeat feedback

Konica Minolta Printer Driver

Case study on this page

What I owned

IPv6 Single Stack work, conflict fixes, V3 and V4 driver changes and documentation.

Constraint

Make networking changes within an established driver codebase and a 30-person team.

Decision

Separate protocol conflict fixes from driver behavior and cover changes with Google Test.

Evidence

IPv6 implementation, V3 and V4 fixes, unit tests and customer documentation.

Experience

  1. 06/2026 - Present

    Embedded Software Engineer · Viettel Hightech

    Develop Embedded Linux firmware for an FPGA electro-optical system, owning control paths and reliability mechanisms.

  2. 03/2026 - 06/2026

    C/C++ Engineer · BlueOC

    Designed the IPC layer and device-side OTA client for Jetson Orin NX, including delivery tooling.

  3. 03/2025 - 03/2026

    C/C++ Engineer · FPT Software Hòa Lạc

    Delivered IPv6 and driver changes with Google Test coverage and customer documentation.

  4. 09/2024 - 12/2024

    Image Processing Intern · Sotatek

    Applied and tuned CNN models for an IoT product deployed on Jetson Nano.

  5. 09/2023 - 09/2024

    Research Member · RF Plus Lab, MICA Institute, HUST

    Built robot, face recognition and microcontroller prototypes across sensing and actuation.

  6. 08/2020 - 08/2025

    Control Engineering & Automation · Hanoi University of Science and Technology

    Advanced Program in Industrial Informatics. GPA 3.2/4.0.

Engineering notes

A few decisions I return to when reliability matters.

A rollback path belongs in the first design.

An update is not complete when it downloads. It is complete when a device can safely return to known-good firmware.

IPC is an ownership boundary.

A clear service boundary makes control paths easier to test, supervise and change.

Health checks must decide something.

A signal only matters when it drives a safe next action, such as commit, retry or rollback.

Start a conversation

For a role, project or technical discussion, choose the contact channel that works best for you.

QR code for Hoàng Đức Mạnh's contact card
Save my contact card
Scan the QR code or download the vCard to save my details.
Download vCard