Whatever the Recruitment Portal Says, Your Chinese Name Is Not an English One
Date Published
A friend forwarded a screenshot on a Tuesday, from a marketing application at a Shenzhen consumer brand. Two grey boxes sat side by side: Last name, First name. Above them, in a smaller font, the system printed what it was about to store.
Last name: Wei
First name: Liu
The applicant's name is 刘伟. The portal had turned a family name into a given name and a given name meaning great into her family name. She typed her name in the order she has used her whole life. The form guessed, and guessed wrong.
Her record was now filed under W, the interview panel would receive a name card reading "Wei Liu", and nobody had been alerted, because in an English-only system the result looks like an ordinary Western name.
Why the form always guesses
Forms assume a family name and a personal name in separate boxes whose order is fixed. Chinese names follow a different layout: the family name comes first, one character in most cases, followed by a one- or two-character individual name, as the site's own explainer at how Chinese names work sets out.
A recruiter reading 刘伟 in a spreadsheet sees three letters with no capitals, no hyphen and no space. Most Western databases were designed around a two-token string. A Chinese name in Latin letters is one token.
So the parser takes the first word as given name, or the last word as surname, because that is the English order. Either rule breaks a Chinese name. The same failure follows the record into the interview schedule, the offer letter and the payroll file.
It is a form problem, and it repeats in visa applications, bank onboarding, university registries and gym memberships.
What the two labels actually hold
The clearest way to see the mismatch is to compare what each side thinks the boxes mean.
Field label | What a Western HR system expects | What a Chinese applicant puts there |
|---|---|---|
Last name | family name, often multi-syllable | family name, usually one character, first in the string |
First name | personal name, may be a nickname | one or two characters, second in the string |
Middle name | optional, often inherited | usually empty, and not a Chinese category |
Name order on documents | given name then family name | family name then given name |
Legal name | the name on government ID | the passport spelling, in romanised form |
A form that asks for a middle name reveals the assumption in one line. Chinese naming has no middle-name slot. A two-character given name is a single unit, and splitting it into "Hui" and "Ling" is not a shortening but a different name. The name-order article makes the same point: the flip happens the moment a Chinese name enters a Western form.
Without a preview, she cannot catch the swap before submission. By the time the rejection email arrives, the record is keyed to the wrong surname, and correcting it means contacting a recruiter who does not know her.
Three names, three outcomes
What decides whether a form breaks a name is the length and shape of the string.
Name | Pinyin | What the person intended | What the portal stored |
|---|---|---|---|
刘峻岭 | Liú Jùnlǐng | 刘 family, given name 峻岭, "steep ridge" | Last: Junling, First: Liu |
周存厚 | Zhōu Cúnhòu | 周 family, given name 存厚, "to keep what is generous" | correct by luck |
马守拙 | Mǎ Shǒuzhuō | 马 family, given name 守拙, "to keep to plainness" | split across three fields |
Look at 刘峻岭. 刘 is among the largest surnames in China, and its surname page traces the line to a Han-era fief. In pinyin the name is three syllables with no marker between family and given. A parser reading "Liu Junling" in a free-text field has a fifty-fifty chance. Split the field and the chance is near zero.
周存厚 ended up correct. The box holds 周 because the applicant typed it under First name and a recruiter moved it later, which the surname page would have settled at a glance. The name survived because a person overrode the machine.
马守拙 goes wrong quietly. 马 has its own page in the surname directory, and 守拙 comes from a line in Tao Yuanming. A three-syllable string gives the parser one extra token to misread. The catalogue names 宁嘉 and 元贞 make the same point: both are single two-character units that split cleanly only for people who do not speak Chinese.
The four ways a form mangles a name
Once the box order is wrong, the errors take recognisable shapes.
The swap. Family and given name exchange places, and the person is filed under the wrong letter for the rest of the process. It is the most common outcome, and the hardest to spot from inside the system.
The split. A two-character given name is divided across first and middle, so a single idea becomes two fragments, one rendered as an initial.
The weld. No space appears between family and given name, so one token does the work of two and sorting fails.
The flatten. Tone marks vanish, so two different names collapse toward one Latin string, and a recruiter cannot tell the files apart. There is a whole article on that failure.
Each one is small. Together they mean the name a candidate uses every day is not the name in the hiring file, and the correction lands mid-search.
What to do before you press submit
The fix is administrative: two minutes now, not two weeks after.
1. Put your family name in the surname box and the full given name in the first-name field. Never use the middle box for the second character. If the portal refuses, leave it empty and note the order in any free-text area.
2. Check for a preview screen. If the assembled record prints your given name first, you have found the swap while it is cheap to fix.
3. Use one romanisation everywhere. Use the passport spelling, with tone marks where the system allows them, on the CV, the portal and your email signature. Mixed spellings make the mismatch look like your error.
4. Tell the recruiter in your first reply. One line is enough: "My family name is 刘; the surname is Liu." A recruiter who knows the order will key the record correctly.
5. Keep the legal name in the legal field. The passport spelling goes there; the everyday name goes in the preferred field. The CV guidance covers the same split.
What native speakers notice
- The name card gives it away. A Chinese colleague looking at "Wei Liu" hears a surname in the wrong slot, and her next thought is that nobody checked the file.
- The middle initial reads as a mistake. Splitting 慧玲 into Hui L. does not sound like shorthand. It sounds like a person who does not know their own name has two characters.
- The correction comes fast. Nobody is offended by a portal. They are impatient, because they fixed the same field at a bank, a clinic and a university in the same year.
- The surname carries the family. Ask which part of 马守拙 matters and the answer is 马. The given name is the parents' gift; the surname is the line.
The cultural risk audit
Register collapse. A wrong-order record makes a Chinese name read as a Western one, which carries different expectations about family, age and formality.
Surname erasure. When the family name lands in the given-name field, the record loses the part that carries the lineage. Ancestral tablets and generation poems attach to that character.
Search and sort failure. Databases sort on the surname field. A swapped record puts a Rén under R, and the candidate becomes unfindable in a system built to find people.
The quiet cascade. The schedule, the name card, the offer letter and the payroll record each inherit the wrong field and need separate fixes.
The courtesy trap. A recruiter who tries to be warm with the wrong name has made the error social, and the candidate now corrects a person rather than a form.
Two moves fix most of it: set your romanisation once, and say your family name in your first message. The free generator shows how surname and given name sit together in a record; the Premium Blueprint is for names going onto official documents that have to hold under an HR system.