Our First Vietnam Team Stalled at Month 4 and the Second Shipped in 6 Weeks — the 7-Step Playbook for Building a Ho Chi Minh City Team From Singapore

The first Vietnam team we built for a Singapore client was six developers in Ho Chi Minh City, hired through a vendor in three weeks, all technically strong. Four months later they had shipped one feature. Every stand-up ended in agreement, every estimate was met, and nothing reached production, because the team had no owner in Singapore, no written design reviews, and a culture — on both sides — in which nobody said “this brief is wrong”. The second team, for a different client a year later, was four people and shipped a production release in six weeks. Same city, same vendor, similar CVs. The difference was everything except the engineers, and it is the seven steps below.

Why Vietnam, and Why From Singapore Specifically

Singapore engineering leaders have three realistic options when the local market cannot fill a team at a price the business will pay: hire remotely across the region, build in Malaysia across the causeway, or build in Vietnam. Vietnam wins on pool depth and cost. Market guides for 2026 put mid-level developers in Ho Chi Minh City or Hanoi at roughly US$1,500 to US$2,800 a month and seniors at US$2,800 to US$4,500 and above; ITviec’s 2025–2026 salary report shows back-end developer medians rising from about 12 million dong at entry level to about 55 million dong at high seniority, which is under S$3,000 a month. The same senior profile employed in Singapore costs S$9,000 to S$14,000 before CPF.

What makes it work from Singapore, rather than from London or San Francisco, is geography. Vietnam is one hour behind. The flight to Ho Chi Minh City is two hours; to Hanoi, three and a half. A Singapore tech lead can run a stand-up at 9:30 local, be in the Vietnam office by lunchtime on a Monday, and be home for dinner on Tuesday. Every step in this playbook exists to exploit that proximity, because the teams that fail treat Vietnam as an outsourcing destination and the teams that ship treat it as the other floor of the building.

Step 1: Choose the Engagement Model Before You Choose the People

There are three ways to put a developer in Vietnam on your team, and the wrong one for your situation is the most expensive mistake in this playbook because it is the hardest to unwind.

The rule of thumb that has held for our clients: start with a vendor if you need a team next month, start with an EOR if you already know exactly who you want to hire, and only incorporate once the monthly margin or fee across the team exceeds what a local accountant and a part-time HR manager would cost. Whatever you pick, write the exit into the contract on day one — how developers transfer from vendor to EOR to entity, and at what fee — because a successful team will outgrow its first model.

Step 2: Pick the City for the Team You Are Actually Building

“Vietnam” is three different labour markets. Ho Chi Minh City has the deepest pool for product companies, fintech and mobile, the most English, and the highest salaries. Hanoi has the large outsourcing firms, the government and enterprise work, and more depth in Java, .NET and QA at scale, at slightly lower cost. Da Nang is smaller, meaningfully cheaper, and has the best retention we have seen anywhere in the country, because the engineers who choose to live there tend to stay; it suits a team of four to six that you intend to keep for years, not a team of twenty you need by Christmas.

Benchmark salaries per city, not per country, and benchmark them against the local market rather than against your Singapore band with a discount applied. A Singapore company paying 20 percent above the Ho Chi Minh City median for a senior gets first pick of a market that big tech and the well-funded local unicorns are also fishing in; paying the median gets you whoever is available this month. The difference is a few hundred dollars per head and it decides the quality of the whole team.

Step 3: Learn the Labour Code Rules That Will Shape Your Contracts

Vietnam’s 2019 Labour Code is clear and, for an employer who reads it, reasonable. The rules that matter for an engineering team:

• Probation is capped at 60 days for positions requiring college-level or higher qualifications, which covers every developer role, and at 180 days for enterprise managers. Either side can end the relationship during probation without notice or compensation. Use the full 60 days; it is the cleanest exit you will ever have.
• Notice on an indefinite contract is 45 days, and 30 days on fixed-term contracts of 12 to 36 months. Vietnamese developers typically move on that notice, so a hire from another employer is six to eight weeks away, not two.
• Statutory employer contributions run at roughly 21.5 percent of salary — social insurance, health insurance and unemployment insurance — with the employee contributing about 10.5 percent, and personal income tax is progressive from 5 to 35 percent. A quoted salary is not the cost.
• A thirteenth-month payment is customary, paid before Tet, and its absence is noticed. Budget it.
• Tet, the Lunar New Year, removes one to two weeks from late January or February, and the fortnight either side runs slow. Do not schedule a release in that window; the team that ships in six weeks is the one that did not start in the second week of January.

A reliable English-language summary of the termination rules is CXC’s guide to ending employment in Vietnam, and the probation caps by role are laid out in Teamed’s Vietnam probation guide. Neither replaces a Vietnamese employment lawyer for your contract template; both will stop you agreeing to something the law does not allow.

Step 4: Design the Rituals Around a One-Hour Time Gap

The hour is a gift and it is easy to waste. A Singapore team on 9 to 6 and a Vietnam team on 9 to 6 local overlap for seven hours; almost nothing in this section is possible from a European or American head office, and it is why the second team shipped.

• One owner in Singapore. A tech lead or engineering manager whose performance review includes the Vietnam team’s output. Not a vendor account manager, not a rotating “point of contact”. The first team did not have one; that is the whole post-mortem.
• Stand-up at a fixed Singapore time, 9:30 or 10:00, on camera, with the Singapore owner present every day. The Vietnam team joins at 8:30 or 9:00 local, which is normal working hours there.
• Written design reviews before code. A one-page design doc, reviewed asynchronously in English, for anything over two days of work. This is where the “silent yes” gets caught, because it is much easier to write “I do not think this will work because…” than to say it on a call to a senior person from headquarters.
• A monthly visit, alternating direction. The Singapore owner spends two days in the Vietnam office one month; one or two Vietnam engineers spend two days in Singapore the next. Budget it as a cost of the model; it is cheaper than the attrition it prevents.
• Shared tooling, one repository, one on-call rota. If the Vietnam team has its own Jira, its own repo and no pager, you have built an outsourcing relationship with extra steps.

If you already run distributed teams, our guide on managing a remote development team covers the general mechanics; the Vietnam-specific point is that the small time gap lets you run a genuinely synchronous culture, so do.

Step 5: Interview for Written English and Pushback, Not Just Code

Vietnamese engineers are, in our experience, technically strong in exactly the areas Singapore companies need: back-end Java, .NET and Node, mobile, QA automation, and increasingly data and ML. The technical screen rarely surprises. What decides whether the team ships is two things the standard loop does not test.

Written English at design-review level. Spoken English in interviews is often better than written English on a pull request, and it is the written form that carries a distributed team. Add a 45-minute written exercise: here is a one-page design, write your review as comments. You are looking for clarity and the ability to disagree in writing, not grammar.

Pushback on a flawed brief. Give the candidate a short specification with a deliberate contradiction in it — a performance target the proposed architecture cannot meet, a data flow that breaks a stated privacy rule — and ask them to plan the work. The candidates who raise the contradiction, politely and early, are the ones who will tell your Singapore lead that a plan is wrong before four months have passed. The candidates who plan around it are the first team.

For the seniors specifically, add one more: have them run a mock stand-up with two of your Singapore engineers playing the team. You are hiring the person who will run the room when you are not in it.

Step 6: Lock IP, Data and Access Under Both Legal Systems

Three layers, in order of how often we see them missing.

• IP assignment in every contract. Vietnam’s Intellectual Property Law generally gives the organisation that assigns the work the economic rights in what an employee creates in the course of it, unless otherwise agreed — but a default is not a clause. Put an explicit assignment and confidentiality term in the employment contract, and if a vendor employs the team, check that the chain is complete: developer assigns to vendor, vendor assigns to you.
• Data protection on both ends. Vietnam’s Law on Personal Data Protection, No. 91/2025/QH15, has been in force since 1 January 2026, with a guiding decree issued on 31 December 2025; it replaces the 2023 decree regime and carries its own consent, impact-assessment and cross-border rules. On the Singapore side, the PDPA’s transfer limitation obligation applies the moment your Vietnam team can see customer data. The practical answer for most teams is that the Vietnam team does not process production personal data at all: masked datasets, synthetic fixtures, and production access through a Singapore-controlled break-glass process.
• Devices and access. Company-managed laptops with disk encryption and MDM, repository access scoped per project, secrets in a vault rather than in environment files, and no customer data on local machines. A vendor that resists managed devices is telling you something about the other clients its developers work for.

None of this is Vietnam-specific in principle; all of it is Vietnam-specific in practice because a Singapore board will ask about it the first time the offshore team appears in a security questionnaire. Our guide to the seven clauses every outsourcing statement of work needs has the contract language.

Step 7: Run the First 90 Days as a Ramp With Two Seniors First

The single structural difference between the two teams in the opening story was the order of hiring. The first team started six people at once, most of them mid-level, and spent four months waiting for someone to take charge. The second started two seniors, sent a Singapore engineer to sit with them in Ho Chi Minh City for the first two weeks, and only added the mid-levels at day 30, by which point there was a codebase, a review culture and two people who could onboard others without a call to Singapore.

• Days 0–14: two seniors, one Singapore engineer on site, the first design doc through review, local environment and access sorted before day 3.
• Day 30: first milestone, defined before day 0 as something a customer could use; add the mid-level hires now, onboarded by the seniors.
• Day 60: the probation decision on the seniors, taken deliberately rather than by default; the team joins the shared on-call rota.
• Day 90: the Singapore owner skips a stand-up on purpose and reads the notes. If the team ran it, the ramp is done.

Retention starts the same day. Vietnamese IT attrition is real, and the good engineers in Ho Chi Minh City receive approaches weekly. The levers that work are not exotic: the thirteenth month, a learning budget that actually gets spent, titles that mean something on a CV, a visible path to the Singapore office for the best people, and a Singapore owner who knows every engineer’s name and last project. The knowledge-transfer process we use when scaling a dedicated team is the same one that keeps the first two seniors from becoming a single point of failure.

If You Also Build Teams From Dubai

The same playbook, with Cairo or Karachi in place of Ho Chi Minh City and a larger time gap, is what our Dubai colleagues run for UAE companies. Their guides on building an offshore development team from Dubai and managing time-zone overlap with remote developers are worth reading if your engineering org spans both hubs; the ownership rule in Step 4 is identical, and the time-zone rituals are where the two markets differ.

Within Singapore, the practical next move is to name the owner, pick the model from Step 1, and hire two seniors before anyone else. Our Node.js, Java and React benches include Vietnam-based engineers who have already worked under a Singapore lead, which shortens the ramp above by the two weeks it takes most teams to learn the rituals.

FAQ — Building a Vietnam Development Team From Singapore