Back to FAQ Hub
FAQ Category
Team & Communication
Who works on your project, time-zone overlap, language fluency, and the engagement model that makes async-first delivery work.
Who is on my project team?
A named tech lead (the one throat to choke), 1-2 senior engineers, and a 0.25 FTE engagement sponsor for QA and escalation. The team is stable for the duration of the engagement — we do not staff with a rotating bench. Tech lead changes require 2 weeks notice and your written approval.
What time zone are you in and how does overlap work?
We are based in Hangzhou, China (UTC+8). For US buyers, our morning is your evening, providing 1-3 hours of overlap. We operate async-first: architecture decision records, written changelog per sprint, asynchronous demo videos, weekly written status. Synchronous overlap is reserved for kickoff, architecture review, demo, and escalation.
How fluent is the English on the team?
Tech lead and at least one client-facing engineer are fluent in written and spoken English. The full engineering team writes English in commits, PRs, written changelog, and ADRs. Synchronous calls are conducted in English with the tech lead.
How do daily standups work across time zones?
Two patterns. Async standup written in your shared Slack channel before vendor team logs off (your morning). Or weekly synchronous status with mid-week async written check-in. Most engagements settle on weekly synchronous + daily async after the first sprint.
Who do I escalate to if there is a problem?
Named escalation path documented at Day 1: tech lead first (24-hour SLA), engagement sponsor second (48-hour SLA). For production-impacting incidents, an on-call rotation with paging is established before launch.