Bridging business and UI
I am strongest when I can take requirements, user flows, and business logic, then turn them into clearer screens and prototypes that give the team something concrete to react to.
IT Business Analyst & UI/UX Prototyper
I work between business logic, user needs, and UI prototypes. With a Software Engineering background and hands-on development experience, I help teams move from unclear requirements to screens that are easier to discuss, build, and improve.
I am still growing through real projects, but I already know the kind of work I care about most: clear requirements, usable screens, and smoother collaboration between business and technical teams.
I am a Software Engineering graduate from FPT University, currently working as a Business Analyst at PTN Global. My work focuses on understanding requirements, organizing business logic, and translating ideas into UI/UX prototypes that development teams can actually build, mainly using Figma.
Before this, I worked at FPT Software as a Software Engineer and Java Web Developer, and I also took on Unit Manager responsibilities. That background still shapes how I think today. I do not only look at how a screen should appear. I also think about behavior, data flow, technical constraints, and how a feature will move from discussion to implementation.
I am still early in my career, so I do not want this site to sound bigger than it is. What I do bring is a practical mindset, steady curiosity, and a habit of asking questions until things become clearer. I like working at the intersection of analysis, design, and development because that is where I can help teams make ideas more concrete.
These are some of the structured courses and certifications that helped shape how I approach business analysis, delivery, and communication. Click any card to open the full certificate.
I do not try to present myself as an expert in everything. These are the areas where I am most comfortable contributing and still actively improving.
I am strongest when I can take requirements, user flows, and business logic, then turn them into clearer screens and prototypes that give the team something concrete to react to.
Because I started from software engineering and Java web development, I tend to think beyond the visual layer. I care about behavior, data, constraints, and how a screen will actually be implemented.
I use Figma to make ideas easier to discuss, validate, and hand off. I care less about decoration for its own sake and more about making flows understandable and usable.
When requirements are vague, I try to slow things down in a useful way: ask better questions, separate assumptions from actual needs, and help different people align before development starts.
I am comfortable learning across BA work, UI/UX, documentation, development, and coordination. To me, that is less about switching identities and more about helping the product move forward.
My working style is shaped by both BA thinking and development experience, so I usually move from problem understanding to practical structure as early as possible.
I try to understand the business goal before jumping into screens or documents.
I would rather clarify assumptions early than let a vague idea quietly become a feature.
I find it easier to reason about a feature when I can see the main flow, edge cases, and screen states clearly.
A practical prototype helps people react to something specific instead of talking around an abstract idea.
I want this part of the site to stay honest and a little personal, because it is where I keep track of what I am learning, building, and still figuring out.
I want this section to stay flexible, but these are the kinds of projects that fit the mix of analysis, prototyping, and software thinking I am trying to grow.
A lightweight portfolio and blog built as a static site on Firebase Hosting. It reflects how I like to work: keep the setup simple, make the content easy to maintain, and improve the experience step by step.
Read the related postA boarding-house rental platform concept where the interesting part for me is clarifying flows, organizing information, and making the experience easier for both users and the team building it.
An educational web idea that lets me think about simple interactions, understandable screens, and how small product decisions affect usability.
The blog is where I write about work, learning, and whatever feels worth keeping instead of letting it disappear into random notes.
A more personal post about growing up in Vietnam, changing through school and university, showing up for people, and why curiosity has probably shaped me more than any single job title.
The first proper post on the site: why I wanted more than a portfolio, what BA work and prototyping are teaching me, and why this space is basically where I yap in public and keep breadcrumbs for later.
If you want to reach out, the easiest option is the Google Form below. It is intentionally simple, just an email field and a message, so it feels closer to sending a lightweight anonymous text than filling out a formal contact form.