Blog

What employers actually see when you've shipped a project

· buildtolaunch

You shipped a small app, and now you wonder whether anyone hiring will care. This guide is for university students in any major in Vietnam and Southeast Asia. It shows what a recruiter or hiring manager actually looks at when you point them to a live project, and how to make those first minutes work for you. For the full picture, see Students outside IT in the AI era (in Vietnamese).

Short answer

Most employers outside engineering will not read your code. In a few minutes they check whether the link opens, whether you can explain the problem and who used it, what you decided and why, and whether the story matches your CV. A shipped project is evidence that you can finish something and learn from real users. A live link, a clear one-page write-up and an honest account of AI's role do most of the work.

What a hiring person actually does with your link

Most people reviewing entry-level applications are not engineers. Even technical reviewers spend their time on the question that matters: can this person do the job and learn fast? In practice, they tend to run through the same short check.

StepWhat they look atWhat helps you
1. Open the linkDoes it load on a phone and a laptop?A working URL, a clear name, no broken pages
2. First screenCan they tell what it does in 10 seconds?One sentence of purpose, a screenshot or short demo
3. The storyProblem, user, what you built, what happenedA short write-up with real numbers
4. Your roleWhat you decided versus what a tool or teammate didSpecific choices you made
5. MatchDoes it fit the role and your CV?A line on the CV pointing to the same project

If step 1 fails, nothing else gets read. Test your link on a friend's phone before you send it.

What employers say they want (and what that means for a project)

The US National Association of Colleges and Employers (NACE) surveyed employers in early 2026. Its press release says the top things employers want are the ability to work in a team, problem-solving and communication, and that it is not enough for candidates to simply list their skills. Another NACE release says 70% of surveyed employers use skills-based hiring, up from 65% the year before. These are US employers, so treat them as a signal, not a rule for every company in Vietnam or Singapore.

A shipped project maps well to this. It is one place where you can show:

  • Problem-solving: you picked a real problem and narrowed it down.
  • Communication: you explained it to users and to a stranger reading your page.
  • Teamwork: if you built with others, you can say who did what.
  • Evidence: a link and numbers instead of an adjective on your CV.

What they notice that you may not expect

A real user beats a polished design. Five classmates who used your app twice a week tell a better story than a beautiful app with zero users. Say how many people used it and what you learned from them.

The edges. Does the app handle an empty form, a wrong password or a bad link? You do not need a perfect product. You need to show that you tested it as a user would.

The write-up. Many strong projects lose points because they have no explanation. A one-page description (see the template below) is often the first thing a non-technical reviewer reads.

Consistency. The project name, dates and numbers on your CV, LinkedIn and page should match. Small mismatches look careless.

Your honesty about AI. Many reviewers now assume you used AI tools. What they want is to see that you directed and checked the work. Say which tool you used, what you asked it to do, and what you reviewed or fixed yourself.

A one-page write-up you can copy

Put this on the project page, a short post or a document linked from your CV.

  1. Name and link. One line: what it is and where to open it.
  2. Problem. Who has it and how they handled it before.
  3. What I built. Three bullets on the main things the app does.
  4. My role. What I decided, what I tested, what I asked AI to do.
  5. Result. Number of users, what they said, one thing that surprised you.
  6. What I would do next. Two lines.

Keep it under 300 words. Add one screenshot or a 60-second demo video.

What does not impress

  • A list of tools with no outcome ("Lovable, React, Supabase").
  • A project that only works on your own laptop.
  • Claims you cannot back up, such as "improved efficiency by 300%".
  • A project you cannot explain when asked a follow-up question. Be ready to walk through one decision and one mistake.

How to get your project in front of them

Put the link on your CV beside the project line, on your LinkedIn Featured section and in the first paragraph of your cover letter. When you apply, add one sentence that connects the project to the role. See how to put a vibe coding project on your CV and how to talk about a personal project in interviews (both in Vietnamese). For a broader list of what employers ask of non-tech graduates, read AI skills employers want from non-tech students.

Getting something to show, for free

buildtolaunch is a free community for university students across Southeast Asia, any major, no coding needed to start. You can take free courses from Anthropic, Google, Lovable, DeepLearning.AI and others, build in a project Space with an AI teammate, and post to the Launch League, a public board that resets every Monday. A weekly habit of shipping gives you a dated record of what you built. You can also look for hackathons and programs on the opportunities page.

FAQ

Do employers actually click on student project links?

Some do and some do not, so do not rely on the link alone. Put one line on your CV that states the result, such as the number of users, and add the link so a curious reviewer can check. Make the page load fast and explain itself, because a reviewer may give it only a minute or two.

Does it matter if I built the project with AI?

Many employers now expect you to use AI tools. What matters is that you can explain the problem, the choices you made and how you checked the output. Say plainly which parts the tool produced and which parts you decided, tested or fixed. Hiding it is riskier than saying it.

Is a project better than a certificate?

They show different things. A certificate shows you finished a course. A shipped project shows you can apply what you learned and handle real feedback. Use both: the course gives you the method, and the project gives you proof. See certificate or real project (in Vietnamese).

What if my project has very few users?

Report the real number and what you learned from those users. Ten people who used it twice and gave feedback is a stronger story than a vague claim. Explain what you changed because of their comments and what you would do next.

Which roles care about shipped projects?

Product, operations, marketing, data and startup roles often value them, because those jobs involve finishing work with limited resources. For other roles, a project still shows initiative and learning speed. Match the project to the role in your cover letter.

Should I show the code?

Only if the role is technical. For most non-IT roles, a live link and a clear write-up matter more. If you want to share code, keep it tidy and add a short README. See GitHub for people who do not code (in Vietnamese).

Read the full guide for skills, portfolio and job search for non-IT students (in Vietnamese).