All posts
Operations

How to Check if a Software Company Really Speaks English and Works in Your Timezone

Published on 10 Nov 2026

how-to-check-if-a-software-company-really-speaks-english-and-works-in-your-timezone

In our experience, many offshore engagements that fail on communication were never tested on it. The buyer judged English on a sales call and judged timezone fit on a map. A reliable check has two parts: test the engineers who will actually join your team, both in writing and live, and then put the overlap window and incident response time into the contract.

As a Vietnam IT company whose whole team works in English for clients in 10+ countries, 724SOFTWARE is regularly asked these questions by prospective clients. Below are the checks we recommend buyers run on any vendor, including us.

TL;DR

  • Test the delivery team, not the sales team. A fluent sales call tells you little about the people who will write your tickets.

  • Written English matters most. In our experience, distributed teams make most of their decisions in tickets and pull requests.

  • Use CEFR B2 as a baseline, and ask how the vendor verifies it.

  • Overlap is not coverage. Overlap means shared meeting hours. Coverage means someone responds when production breaks at night.

  • Put it in the contract: named engineers, the overlap window in your local time, and a written incident response time.

About the Author: This guide comes from the delivery leadership at 724SOFTWARE, a Vietnam-based engineering company of 200+ professionals (58% senior). We run dedicated teams in English for clients across 10+ countries, with additional Mandarin, Korean and Japanese support.

What does "speaks English" actually mean for an offshore software team?

Before you test anything, define what you are testing for. For a software team, "speaks English" means every person who touches your product can do four things in English without a go-between:

  • Reading: specs, API docs and existing code comments.

  • Async writing: tickets, pull request descriptions and handoff notes.

  • Live discussion: stand-ups, design reviews and debugging calls.

  • Escalation under pressure: saying "this will not work" or "we are late" clearly and early.

The Council of Europe's Common European Framework of Reference for Languages (CEFR) is a shared reference scale for language ability, used in Europe and on other continents. In the Council of Europe's CEFR global scale, B2 is the level at which a person can understand the main ideas of complex text, including technical discussions in their own field, and interact with native speakers without strain for either party.

Our expert opinion: written fluency predicts project health better than accent or spoken polish, because most decisions in a distributed team are made in text.

Watch for the relay model, where one English-speaking project manager translates for engineers who do not work in English. It behaves like a single-lane bridge. Every question has to pass through one person, so the team's throughput is capped by that person's calendar. When they go on leave, traffic stops. Each crossing also strips away some context, which is why requirements quietly drift.

How can you test a vendor's English before you sign?

The real risk sits with the engineers, so your test has to reach them directly. Here is a five-step check:

  1. Ask for named people, not profiles. Request CVs for the specific engineers proposed for your team.

  2. Run an unscripted technical call with at least two of them, and do not let the project manager answer for them. Ask each engineer to walk through a past design decision and something that went wrong.

  3. Request a written sample. Send a short brief and ask a proposed engineer to write a bug report or design note.

  4. Send an ambiguous requirement on purpose. Strong engineers ask clarifying questions. Weak ones guess silently.

  5. Ask how English is assessed at hiring: which level is required, which test is used, and who checks the results.

Both are useful for screening. Neither shows whether an engineer will push back on a bad requirement. Only a live work sample does that.

How much timezone overlap do you actually need?

Language decides whether your teams can understand each other. Timezone decides when they can. Timezone overlap is the number of hours both teams are working at the same time. Vietnam runs on UTC+7, and the figures below use standard time:

Client location

Offset from Vietnam

Typical business-hour overlap

 

US East (EST)

Vietnam 12 hours ahead

Minimal

US West (PST)

Vietnam 15 hours ahead

Minimal

UK (GMT)

Vietnam 7 hours ahead

1 to 2 hours (European morning)

Central Europe (CET)

Vietnam 6 hours ahead

1 to 2 hours (European morning)

Australia (east coast)

Australia ahead of Vietnam

A large share of the working day

Our expert opinion: a protected daily window of an hour or two is enough for decisions and unblocking, provided the handoff notes are well written. Without that writing discipline, even a longer overlap feels short.

Verify the overlap claim rather than accepting it:

  • Ask which hours the team works, and whether any shifted hours are a permanent schedule or a one-off favour.

  • Book test meetings at both edges of the promised window.

  • Send a question at the end of your day and see what is waiting for you the next morning.

What is the difference between timezone overlap and 24/7 coverage?

Once you know the overlap, the harder question is what happens outside it. Overlap supports collaboration. Coverage supports response: someone qualified is reachable when production fails at 3 a.m. your time.

A follow-the-sun model hands work and on-call duty across timezones so that someone is always on shift. When you assess one, ask:

  • What is the incident response time, and is it in writing?

  • Who is on call, and do they have production access?

  • How are handoff notes written, and in what language?

That last question connects coverage back to English. A follow-the-sun model is only as good as its handoff notes. At 724SOFTWARE, our follow-the-sun model is backed by a commitment to respond to incidents in under 10 minutes.

Which red flags suggest the promises will not hold?

Beyond the individual checks, a few patterns during the sales process, in our experience, often predict problems later.

Signal

Why it matters

What to ask

 

Only the sales lead or PM speaks on calls

Possible relay model

"Can two proposed engineers join?"

Anonymous profiles instead of named engineers

Team may be assembled after signing

"Who exactly is on my team?"

Overlap described as "as needed"

No committed schedule

"Which hours, in my local time?"

No written response time

Coverage is only a promise

"What is the incident SLA?"

Hours worked are not visible

Timezone claims cannot be checked

"Can I see time reports directly?"

What should the contract say about language and working hours?

Everything you verify should end up in writing, because sales-stage promises can change when account managers do. Include:

  • Named team members and a replacement process with a defined handover period.

  • The overlap window, stated in your local time.

  • English as the working language for all artefacts, including tickets, code comments and documentation.

  • The incident response time and on-call coverage.

  • Billing based on actual hours worked, with reports you can access yourself.

  • A review checkpoint after the first month.

Frequently Asked Questions

Is an English certificate enough proof?

No. A certificate shows test performance. Combine it with a live technical call and a written work sample.

What English level should offshore developers have?

We recommend CEFR B2 as a baseline for technical work and C1 for client-facing leads and architects.

Can a Vietnam-based team cover US hours?

Business-hour overlap with the US is minimal, so coverage depends on shifted schedules or a follow-the-sun setup. Ask which one the vendor uses and get it in writing.

Does a Vietnam software team suit European clients?

Yes, as long as the 1 to 2 hours of morning overlap are used well and written handoffs are strong.

How quickly can a vetted team start?

It varies by vendor. 724SOFTWARE ramps dedicated teams of 1 to 50+ pre-vetted engineers in 2 to 4 weeks.

About 724SOFTWARE

724SOFTWARE is a Vietnam-based software engineering company that works as a long-term technology partner to product companies, consultancies and enterprises. We have 200+ professionals and a 95% client retention rate.

Our dedicated teams, embedded engineers and offshore development centres all work in English, with Mandarin, Korean and Japanese support, and operate on a follow-the-sun model with incident response under 10 minutes. We are compliant with ISO 9001 and ISO 27001:2022 and GDPR compliant. Billing is based on actual working hours, and clients can monitor team health and delivery performance directly.

If you are shortlisting vendors now, start by asking each one for an unscripted call with two of the engineers they would put on your team. We are glad to be tested the same way, and you can start that conversation at https://724software.com.vn/.

Share this article

Operations

Shrimpie Tran

AI Engineer

Keep Reading

Explore more from our experts.

View all

Stay ahead with our insights.

Get the latest on software design, strategy, and what's working in the field.

We respect your inbox. Unsubscribe anytime from any email.