01 — CV + Project Stories

Based on your latest CV.

Positioning

Your CV presents you as:

  • Full-stack .NET Engineer with 5+ years
  • .NET + PostgreSQL/SQL Server + React + Flutter
  • modular backend architecture
  • REST APIs
  • query/data-access optimization
  • Docker, CI/CD, Azure
  • production environment management
  • end-to-end system ownership

Self introduction — 60–90 seconds

Hi, I’m Vu. I’m a full-stack .NET engineer with more than five years of experience, with my strongest area being backend development and system integration.

My main stack is .NET, Entity Framework, PostgreSQL and SQL Server. I also work with React, Flutter, Docker, Azure and CI/CD.

In my current role at Idle Mind Technologies, I own system design and implementation across backend architecture, database design, API contracts, web and mobile integration, deployment and production operations.

I also work on modernizing legacy modules, improving database performance, troubleshooting production issues and coordinating delivery with QA, Product and other stakeholders.

I’m now looking for a role where I can go deeper into .NET, architecture and production-critical systems, which is why the Manufacturing Systems role at Bosch is interesting to me.

Current project story

Prepare:
Context → Problem → Your responsibility → Decision → Trade-off → Implementation → Result → Learning

Architecture ownership

Be ready for:

  • How did you design the backend architecture?
  • What did you personally decide?
  • Why modular architecture?
  • What trade-offs did you make?
  • What would you redesign today?

Legacy modernization

Safe approach:

  1. Understand current behavior
  2. Identify risks/dependencies
  3. Add tests/observability
  4. Refactor incrementally
  5. Keep compatibility
  6. Deploy gradually
  7. Monitor

Production issue story

Prepare one real story:
Symptom → Impact → Investigation → Root cause → Mitigation → Permanent fix → Prevention

AI-assisted engineering

I use AI as an engineering accelerator, not as an authority. I keep requirements and technical design explicit, use AI for planning and implementation support, then validate changes through code review, tests, build results and Git diff. Architecture decisions and final responsibility remain with me.

Azure DevOps / delivery

Requirement → technical design → task breakdown → implementation → review/test → build → deployment → monitoring → follow-up

Questions to practice

  1. Tell me about yourself.
  2. What are you responsible for now?
  3. What architecture decisions did you personally make?
  4. Tell me about a legacy module you modernized.
  5. Tell me about a difficult production issue.
  6. How do you improve performance?
  7. How do you use AI in development?
  8. How do you coordinate releases?