01SOFTWARE ENGINEER / BACKEND-FOCUSED FULLSTACK

NGUYENTIENHUNG

I build product systems that solve real problems.

3 years building backend-focused fullstack products across fintech, public service, e-commerce and telecom — from business workflows and distributed services to real-time and AI-powered product experiences.

  • 3 YEARS EXPERIENCE
  • HO CHI MINH CITY, VIETNAM
LET’S TALKVIEW WORK ↓
02TECHNOLOGY

REAL TOOLS.REAL PRODUCTS.

03ABOUT ME

THE ENGINEERBEHIND THE SYSTEM

I started from the backend, where I learned to think in services, data, boundaries and failure cases. Working closer to business and product gradually changed how I build — I care not only about how a feature is implemented, but why it exists, where its responsibilities should live, and what happens after it reaches production. Today I still write code deeply, but I own the system around it too.

  1. STARTEDBackendServicesDataFailure cases

    On the backend — services, data, boundaries and failure cases.

  2. SHIFTEDBusinessProductRequirementsOwnership

    Closer to product: why a feature exists, where responsibility lives, what happens after it ships.

  3. TODAYBackend-focused fullstackSystem thinkingProduct ownership

    Deep in the code, responsible for the whole system around it.

04WHERE I HAVE WORKED

DIFFERENT DOMAINS.ONE MINDSET.

Four business environments, one evolving way of thinking about systems.

  1. Public ServiceCorrectness & ProcessSystems where workflows, rules and data integrity are the whole point.
  2. E-commerceBusiness WorkflowsTurning product rules into dependable order and fulfillment flows.
  3. TelecomScale & OperationsWorking around performance, deployment and production reliability.
  4. FintechData & IntelligenceMarket, news and social data becoming structured product intelligence.
05WORK HISTORY

EXPERIENCE

Four roles across fintech, public service, telecom and e-commerce — newest first, reading back from technical analysis and system ownership to the first backend role.

CURRENT · FINTECH · AI

HongThai

Fullstack Engineer / Technical Analyst

10/2025 — Present

Building the AI + real-time backend of a product-stage financial platform.

CASE STUDY ↓

Key highlights

  • Co-developed an AI orchestration flow — an orchestrator coordinating specialized C#/.NET agents built as reusable skills.
  • Shipped real-time AI and market-data experiences streaming over SignalR.
  • Built a data-first AI workflow that prepares & validates data before the model reasons over it.

What I did

  • Build backend and fullstack features with .NET 8, C#, Next.js, TypeScript, REST, SignalR, Redis, MySQL, Elasticsearch, RabbitMQ and Docker.
  • Co-develop an AI Stream Chat flow in C#/.NET: an orchestrator coordinating specialized agents that expose reusable skills.
  • Build real-time AI and market-data features over SignalR — structured AI metadata drives charts, tables and financial widgets.
  • Build Hangfire ingestion for RSS, Reddit and market-data sources, with AI sentiment scoring, tagging and summaries.
  • .NET 8
  • C#
  • SignalR
  • Next.js
  • TypeScript
  • Redis
  • MySQL
  • Elasticsearch
  • RabbitMQ
  • Hangfire
  • Docker
BACKEND · MICROSERVICES · LEADERSHIP

IZOTA

Backend Developer → BA → Sub Team Lead

08/2024 — 09/2025

From Backend Developer to Sub Team Lead — owning the core product end to end.

Key highlights

  • Progressed Backend Developer → Business Analyst → Sub Team Lead.
  • Built the backend on .NET microservices with REST + gRPC and Kafka / RabbitMQ async workflows.
  • Owned deployments, CI/CD and production incident handling.

What I did

  • Develop backend services for the core product with .NET and a microservices architecture.
  • Design RESTful APIs and use gRPC for service-to-service communication; async workflows with Kafka and RabbitMQ.
  • Maintain data with PostgreSQL and MongoDB; contribute to CI/CD and deployment.
  • Contribute to the frontend with Blazor and later ReactJS for end-to-end delivery.
  • .NET
  • Microservices
  • gRPC
  • Kafka
  • REST
  • RabbitMQ
  • PostgreSQL
  • MongoDB
  • Blazor
  • ReactJS
PUBLIC SERVICE · JAVA · MICROSERVICES

VNPT HCMC

Backend Developer

09/2023 — 06/2024

Backend services for government-oriented systems, in Java Spring Boot.

Key highlights

  • Built backend services in Java Spring Boot for government-oriented systems.
  • Worked with Microservices, MongoDB and Elasticsearch.

What I did

  • Develop backend services with Java Spring Boot for government-oriented systems.
  • Work with a Microservices architecture, MongoDB and Elasticsearch.
  • Java
  • Spring Boot
  • Microservices
  • MongoDB
  • Elasticsearch
WHERE IT STARTED · JAVA

FPT Software

Fresher Developer

09/2021 — 01/2022

Where it started — Java development, testing and bug fixing on a delivery team.

Key highlights

  • Contributed to Java development, testing and bug fixing as part of the team.
  • First hands-on experience shipping software in a professional team.

What I did

  • Participate in Java development, testing and bug fixing as part of the development team.
  • Java
  • Testing
  • Debugging
06WHAT I DO

CAPABILITIES

Not a skills list — the five things I actually do when I build.

  1. Build the Backend

    Design APIs, services and data access around clear boundaries — C# / .NET 8, Clean Architecture, EF Core & Dapper.

  2. Think in Systems

    Connect services, messaging, caching, search and real-time delivery into one working system — microservices, REST & gRPC, Kafka / RabbitMQ, Redis, Elasticsearch.

  3. Ship End to End

    Move from the backend into React / Next.js / TypeScript when the product needs it, and carry a feature all the way to the UI.

  4. Work Close to the Product

    Translate business requirements into technical workflows and implementation decisions — the analyst side of the work.

  5. Extend the System with AI

    Build data-first AI workflows, orchestration and reusable skills around the model — AI as a system, not a chatbox.

07FEATURED CASE STUDY

TOPONELOGIC

ACT 01PRODUCT

AI-POWEREDFINANCIALPLATFORM

Financial analysis, portfolio workflows, market data, news and social intelligence, real-time experiences and AI-assisted decision support — built by a 6-person product team.

What
AI financial platform — stocks & crypto
My role
Fullstack Engineer / Technical Analyst
Team
6-person product team
Core stack
.NET 8 · SignalR · Next.js

DEMONSTRATION CONTENT — NOT INVESTMENT ADVICE

The product · toponelogic.com

TopOne trading platform overview — market watch, live chart, positions, portfolio summary, risk overview, backtest results and strategy builder.
Trading platformLive chart, positions, risk overview and strategy builder in one workspace.
ACT 02PROBLEM

FINANCIAL DATA IS NOISY,FRAGMENTED ANDCONSTANTLY CHANGING.

Financial data is noisy, fragmented and constantly changing. Prices, news and social chatter arrive from many sources in many shapes — and a language model on its own will happily reason over the wrong facts, or facts it never actually had.

  • MARKET DATA
  • NEWS
  • SOCIAL · RSS · REDDIT
ACT 03SYSTEM

Data flows one way, and each stage does one job.

  1. DataMarket data · news & social (RSS, Reddit) — ingested with Hangfire
  2. PreparationNormalize, enrich and structure before any model reasons
  3. OrchestratorOne C#/.NET flow coordinating the work
  4. Specialized AgentsReusable C#/.NET skills the agents share
  5. AnalysisSentiment, classification, tagging, summaries
  6. Real-Time UISignalR streams results and financial widgets as they happen
ACT 04CONTRIBUTION

Fullstack Engineer / Technical Analyst at HongThai (Oct 2025 – Present): AI architecture, backend and fullstack features, real-time delivery, and the data-first workflow behind the analysis.

  • AI ORCHESTRATIONAn orchestrator coordinating specialized C#/.NET agents built as reusable skills.
  • DATA-FIRST WORKFLOWData is gathered, normalized and prepared before the model reasons over it.
  • REAL-TIME DELIVERYAI and market-data experiences streaming over SignalR.
  • BACKEND + FULLSTACKBackend and fullstack features across .NET 8 and Next.js, carried to the UI.

What was hard

Making AI genuinely useful without letting the model own the whole workflow — keeping preparation, orchestration and results as designed system parts, and balancing real-time streaming against reliable background processing.

What it taught me

AI works better when the system around the model is designed well: prepared data and clear orchestration beat asking the model to do everything.

  • .NET 8
  • C#
  • Next.js
  • TypeScript
  • SignalR
  • Redis
  • MySQL
  • Elasticsearch
  • RabbitMQ
  • Hangfire
  • Docker
08STRENGTHS

WHAT I BRING

Why a team would want me in the room.

  1. I think beyond the ticket.

    I care about the system behind the feature, not just the endpoint that implements it.

  2. I move across the stack.

    Backend is my strength, but I can follow a feature through React / Next.js to the product.

  3. I speak product and engineering.

    BA experience taught me to turn ambiguous requirements into concrete system decisions.

  4. I stay close to production.

    Deployment, monitoring and incident response changed how I think about reliability.

  5. I use AI without outsourcing engineering.

    AI accelerates implementation; architecture, decisions and code ownership stay mine.

09DIRECTION

WHAT'S NEXT

  • BUILDDEEPER.
  • SCALESMARTER.
  • LEARNFASTER.

I want to keep getting better at the hard part of software: designing systems that stay useful as the product grows.

Looking for teams where engineering is close to the product, decisions are thoughtful, and people care about what they ship.

Open to

  • Software Engineer
  • Backend Engineer
  • Fullstack Engineer (.NET / React / Next.js)

.NET / React / Next.js

10GET IN TOUCH

LET'STALK.

Open to Software Engineer, Backend Engineer and Fullstack roles (.NET / React / Next.js). If you are building something real, let’s talk.

LET’S TALK