Table of Contents
Toggle- Text Display
- ►Traditional
- ►Simplified
- Pinyin Display
- ►Visible
- ►Mouseover
- ►Hidden
Cross-Strait Workplace Notes
The Unspoken Rules: Taiwan & China Tech Culture, Explained for Foreign Engineers
職場文化的潛規則职场文化的潜规则 · “the unwritten rules of workplace culture”
Show up to a standup in Taipei or Shenzhen expecting the same social contract you had in San Francisco or Berlin, and you will misread almost everything: the silence, the smiles, the “sure, no problem,” the 2 a.m. Slack messages. None of it is random. It is a codebase of its own — just not one anyone hands you a README for. This is that README.
Do Taiwan and China Have the Same Tech Work Culture?
No — and conflating them is one of the most common mistakes foreign engineers make. Both cultures share a Confucian-influenced respect for hierarchy, indirect speech, and “face” (面子面子), but they express those values very differently on the ground. Taiwan’s tech culture is closer to a quieter, more relationship-based version of corporate Japan or Korea, softened by decades of small-and-medium-enterprise pragmatism. China’s tech culture — especially at large platform companies — has been shaped by hypergrowth, intense competition for a small number of elite jobs, and a much more explicit performance-and-visibility economy.
The short version: Taiwan optimizes for harmony and long-term relationships; China’s big tech optimizes for speed and visible effort. Startups on both sides borrow heavily from Silicon Valley, which is exactly why a foreign engineer can walk into two companies a subway ride apart and have wildly different experiences.
Politeness Is the Interface, Not the Message
🔑 “We can think about this more” means no
When a manager responds to a proposal by saying the following, it is not an invitation to iterate together next week — it is a rejection, delivered softly enough that neither party has to lose face.
Literally: “This part, we can think about more.” Foreign engineers who take it literally and return with “iteration two” of the same idea are often quietly confused why it keeps not landing. Find out privately, later, what would actually work.
🔑 “You’ve worked hard” is a goodbye, not a compliment
Gets said dozens of times a day — at the end of a meeting, when someone hands off a task, when you leave for the day. It functions closer to “take care” or “thanks for that” than to genuine recognition of exceptional effort. Don’t read it as a performance review.
🔑 Disagreement happens after the meeting, not in it
Open, real-time pushback is rare, even when several people privately think a plan is flawed. Objections tend to surface as a hedged, softly-framed question during the meeting:
“I have a small doubt…” — said before what is often a serious, considered objection. Or the objection surfaces privately afterward, one-on-one, once the group setting no longer puts anyone’s face at risk. If you ask a room “does everyone agree?” you will usually get nods — including from people who disagree. Ask instead, “does anyone see a problem with this?” and wait through a silence that will feel too long. It usually isn’t.
Hours, Titles, and the Weight of “Sorry”
🔑 Overtime is unspoken, not unenforced
Nobody will tell you to stay late. Nobody has to. In Taiwan’s hardware and semiconductor ecosystem — Hsinchu Science Park, TSMC’s supply chain, and the contract manufacturers around it — leaving exactly on time, even with your work finished, can quietly read as under-committed. It’s common to see engineers stay until a manager leaves first — office shorthand for “sitting until the boss goes.” Software startups are looser and more Silicon-Valley-inflected, but the culture is a genuine mix — influenced as much by mainland Chinese hustle norms as by Western flexibility, and it varies a lot company to company.
🔑 Titles encode rank more than they sound like they do
These three titles aren’t just resume flavor — they carry real, understood seniority that shapes who gets asked for sign-off, who speaks first in a review, and who a junior colleague will approach with a problem:
Engineer, senior engineer, principal/lead engineer — foreign hires often arrive flat-structured and don’t realize a title mismatch is quietly affecting how much weight their opinion carries in the room.
🔑 “Sorry to bother you” is a doorbell, not an apology
Precedes almost everything: asking a question, interrupting, even flagging a bug in someone else’s code. Foreign colleagues sometimes mistake this for a lack of confidence. It isn’t — it’s a conversational doorbell, said before nearly any imposition on someone else’s attention, confident or not.
Speed, Visibility, and Who You Know
🔑 996 and “wolf culture” were the default, not the exception
At major platforms — Alibaba, Tencent, ByteDance — working roughly 9 a.m. to 9 p.m., six days a week (996) was for years not just tolerated but implicitly expected and, at some firms, factored into performance reviews. The term below describes the aggressive, all-in ethic this produced:
“Wolf culture.” Regulatory pressure and public backlash since 2021 have pushed official policy away from 996, and some firms have scaled it back on paper — but norms shift slower than policy, and the underlying expectation of intensity hasn’t disappeared everywhere.
🔑 “Managing up” is a hard skill, not a soft one
Making your effort visible to leadership — replying in the group chat late at night, being seen at your desk, narrating progress proactively — can matter as much as the underlying output itself. This is a much more explicit, almost quantified expectation than in Taiwan, where visibility tends to accrue quietly through relationships rather than active self-promotion.
🔑 Guanxi shapes technical decisions more than outsiders expect
“Guanxi” — who referred whom, who shares a hometown or alma mater with whom — genuinely influences project staffing and promotion decisions, not just office politics in the abstract. Foreign engineers, used to org charts and documented decision criteria, routinely underestimate how much this informal network explains outcomes that otherwise look arbitrary.
🔑 Meetings can be blunter — and blame-shifting is its own skill
Criticism in meetings, especially at younger, startup-influenced companies like ByteDance, is often more direct than in Taiwan. But that directness coexists with a well-developed culture of the following, literally “throwing the pot” — deflecting blame when something breaks:
Knowing how to avoid being left holding responsibility for a shared failure is treated as a real, if unofficial, professional skill.
Things Both Sides Get Wrong About Each Other’s Words
🔑 “Read, no reply” is a soft no in both places
A message marked as read that goes unanswered for hours or days is rarely an oversight in either culture — it’s frequently a gentle way of declining or postponing without the discomfort of saying so directly. Don’t assume it didn’t get seen.
🔑 The same job title can mean a very different job
Taiwan tends to say “engineer” and “PM” in ways closer to their Western meaning. Mainland Chinese companies favor the terms below — which look like direct translations but sit inside a different org logic:
Product manager, and R&D. A Chinese PM often holds significantly more authority than a Western or Taiwanese PM, functioning closer to a mini-general-manager who can unilaterally shape a product’s direction rather than a coordinator who facilitates consensus.
Translation Guide: What’s Said vs. What’s Meant
Taiwan
“This part, we can think about more.”
This isn’t happening as proposed.
“I have a small doubt…”
I have a serious objection.
“You’ve worked hard.”
Goodbye / thanks, said reflexively.
China
“We’ll try our best.”
This probably won’t happen.
“There might be some challenges.”
This is going to fail.
“That’s an interesting idea.”
I don’t like your idea.
What to Actually Do With This
- Never ask “does everyone agree?” — ask “does anyone see a problem with this?” and sit through the pause.
- Treat understatement as a signal, not modesty. “A little difficult” often means “not happening.”
- Deliver bad news privately first, especially to someone senior, before it ever reaches a group setting.
- Learn your local title hierarchy — it quietly determines who gets asked for sign-off and whose disagreement carries weight.
- In China, make progress visible — silent competence is read very differently there than in Taiwan or the West.
- In Taiwan, match your hours to the room, at least until you understand which team you’re on — hardware and software often run on different clocks.
- Don’t mistake “read, no reply” for a technical glitch. Follow up once, gently, then take the hint.
- Ask what a title actually implies before assuming a “PM” or “engineer” role maps to what it means at your last company.
