Curriculum vitae
Lâm Quang Vinh
Backend Engineer / Systems Builder
I design backend systems around explicit state, durable data, and operations that remain explainable after the request ends.
- Primary focus
- Reliable backend systems
- Core stack
- .NET / SQL / Linux
- Public practice
- Writing and case studies
01Model the business state
02Protect the data boundary
03Make operations observable
Professional profile
Backend engineer focused on database-backed business workflows, integration-heavy applications, and technical communication that makes system decisions easier to inspect.
My work connects API behavior to database guarantees: concurrency control, idempotent operations, explicit state transitions, useful audit records, and failure-aware integration boundaries.
Selected engineering work
LETOS
An e-commerce operations system centered on inventory, order flow, marketplace integration, and backend reliability.
.NET / MySQL / EF Core / NginxZenpack
A cloud-based logistics and operations platform focused on workflow clarity and integration-heavy backend design.
Next.js / .NET / PostgreSQL / DockerVietnamese News Summarization Research
An applied NLP project connecting dataset preparation, model adaptation, evaluation, and engineering workflow.
Python / Transformers / LoRA / QLoRACore capabilities
Backend systems
.NET, ASP.NET Core, API design, background processing, and integration boundaries.
Data reliability
MySQL/PostgreSQL, transactions, concurrency, idempotency, and audit-friendly models.
Delivery and operations
Linux, Nginx, Docker, logging, deployment, and practical production diagnostics.
Applied AI/NLP
Transformers, LoRA/QLoRA, summarization, evaluation, and research workflow.
Research and continuous learning
I maintain a public learning trail across systems fundamentals and applied AI/NLP. Current work includes Transformers, parameter-efficient fine-tuning, Vietnamese summarization, evaluation, C++, and performance fundamentals.
The writing on this site is part of the CV: it shows the questions I ask, the trade-offs I notice, and how I turn implementation experience into reusable knowledge.