Guest: Wei Xiaokang, human resources specialist and AI product manager, formerly recruiting leader at ByteDance and Meituan, then founding an AI recruiting product
Host: Qu Kai
Originally published: June 27, 2026 | Duration: 50 minutes 20 seconds
Edited: October 18, 2026 | Official episode
Why might one successful company recruit strong people before assigning jobs, while another starts with operating plans and headcount? Wei's experience across ByteDance and Meituan suggests that organization is not a collection of practices detached from business. Chains, cycles, and margins shape staffing and cooperation.
The discussion combines recruiting methods with strong personal preferences. Observable business problems can become practical methods; views about age, individual companies, and ability rankings should retain disagreement. Finding an allegedly advanced organization does not remove the need to examine one's own conditions.
1. Organization has two dimensions; even three people need shared goals
Listen: 02:08–02:41, 09:53–13:59, and 36:47–39:11. Wei separates how people operate—selection, deployment, development, incentives, and adjustment—from how people and business work together through goals, responsibility, and cooperation. Recruiting belongs to the first but cannot answer what everyone should complete today.
Three people can hold three interpretations. A small team need not build heavy hierarchy, but can review goals, owners, and dependencies weekly or monthly. Alignment is useful when it reduces conflicting optimization rather than merely adds meetings.
Wei places Google and ByteDance toward shorter chains, shorter cycles, and higher margins, and Amazon and Meituan toward longer chains and cycles with lower margins. The former may better tolerate hiring before placement; the latter needs clearer operating budgets and staffing coordination. These are analytical coordinates rather than exhaustive descriptions of every department.
Editorial inference: An online AI tool and a business dependent on offline suppliers and human service should not share an organization chart merely because both use models. Map delivery, waits, rework, and specialist checks before combining roles.
2. Culture needs examples; less formal appraisal still needs feedback
Listen: 13:59–18:39. Wei sees culture beginning with core members' actual behavior. Many companies use similar words about candor and quality. Differences emerge when leaders handle bad news, mistakes, disagreement, and unacceptable conduct.
He criticizes early teams spending lengthy periods on promotion documents and layered appraisal. Leaders close to work can observe results directly; elaborate processes can encourage performance for evaluation criteria. This challenges administrative cost without making fairness, pay, and feedback irrelevant.
The episode uses rapid growth and rising equity values to explain why small bonus differences might seem less important. Valuations are not realized income, however, and growth does not automatically remove unfairness. Clearer mechanisms may become more necessary as size increases, visibility decreases, or growth slows.
The seventy percent practice, twenty percent learning from others, and ten percent training model is experiential rather than precise measurement. A stronger qualification appears later: when Qu suggests recruiting a group and discarding those who fail, Wei rejects it. Organization serves the business, not elimination. Real work needs resources, guidance, and feedback; unsupported exposure is not development.
3. Recruiting starts with demand and supply, not interview scheduling
Listen: 18:39–27:50. Hiring often begins after a problem becomes urgent, although suitable people may arrive months later. Wei recommends repeatedly asking what kind of person is needed, how many, and when. Staffing preparation must therefore look beyond the immediate gap.
Demand and supply deserve attention: which teams solve comparable problems, which capabilities are essential, and whether a leading specialist or a competent experienced practitioner is necessary. Talent density should concern fit and joint delivery rather than salary, prestigious schools, or titles.
Experience versus potential also has no universal answer. Established supply-chain problems may benefit greatly from existing expertise. New AI search problems may place everyone in a learning process. Assess tasks, learning, and motivation rather than use age as a proxy.
Wei's suggestions about spending 80–90% of organizational attention on hiring and most recruiting effort on demand and supply are experiential allocations, not mandatory ratios. Founders should define work personally without neglecting customers or support for existing colleagues.
Editorial inference: A job description should start with three current problems and observable success before a title. Unclear demand makes numerous interviews comparisons of conversation. Changed tasks can also make the most impressive résumé less relevant.
4. Several records of actual work beat one persuasive conversation
Listen: 27:08–33:14 and 35:24–36:39. Prepared candidates can hide gaps in short interviews. Even after years together, colleagues may evaluate the same person differently. Wei's misjudgment percentages are personal estimates without research samples, but the evidence problem remains useful.
Independent interviews before discussion reduce anchoring. Specific accounts from reliable former colleagues can supplement brief performance. Reference checks still require consent and privacy boundaries, separating facts, interpretations, and relationships. Referrals are not exemptions from checking, and one manager's preferences are not a final verdict.
In offer discussions, Wei asks what candidates want over three to five years and what previously gave them satisfaction. People may not initially know, and both sides can explore. Meaning cannot replace reasonable pay. The company must also explain work, risks, development, and limitations honestly rather than only elicit the candidate's needs.
His contemporary AI approach searches public talent signals while business leaders define and assess requirements, with recruiters connecting to real people. This is not unrestricted permission to collect private résumés, label individuals automatically, or contact them without authorization. Faster sourcing still needs responsibility for accuracy and candidate experience.
5. AI can reduce handoffs without using labels to bypass disagreement
Listen: 39:22–48:53. Wei imagines responsibility by business module, with one person using AI from product definition through testing. Programming in growth, sales, and moderation could reduce dependence on engineering queues. Estimates of five- or tenfold efficiency lack identical-task comparisons and cannot directly determine headcount.
Professional responsibility remains. Model-generated code needs checks of requirements, permissions, security, and outcomes. One person completing product and testing work may still need another person accepting high impact results. Fewer handoffs should improve complete delivery rather than eliminate anyone able to challenge mistakes.
Views about OPCs—one-person companies—and young founders are contested. Wei prefers one or two capable people in each major area and worries about limited fundraising, team-building, and competitive experience. Qu notes that experienced people can be constrained by familiar rules, while younger people may break conventions. Preserving both positions avoids turning preference into an eligibility rule.
Individual companies may pursue autonomy and income rather than large scale. Different goals require different evaluations. Age remains a rough label; the useful questions concern access to resources, learning through unknowns, and responsibility for critical work.
Wei's closing recruiting vision concerns better matching and less deception. An extremely high claim about workers experiencing fraud has no survey source and is not adopted as population fact. Finding people, accurate matching, reduced discrimination, and reduced fraud are separate outcomes, none established by a vision alone.
Exercise: define the task before deciding to hire
Choose one business bottleneck:
- State the actual customer or internal problem, frequency, failure impact, and deadline.
- Identify what current people and AI can do and what is missing: time, specialist knowledge, or decision authority.
- If hiring is necessary, design an observable work sample and two questions about past collaboration, explaining information and consent boundaries beforehand.
- Define initial goals, available resources, feedback, and job realities. Ask both sides to restate expectations.
Then revisit the chain. Who receives responsibility when a handoff disappears? Which actual constraint does a new role remove? If the answers are unclear, improve the problem definition before copying a large company's structure.
Source boundary
This reading uses the official introduction and complete transcript. Company policies, pay, headcounts, efficiency, and talent judgments remain experience reported in June 2026, without organizational audit. The official description says the voice was altered to discourage training and imitation; public availability does not establish copying permission. School rankings, age, attrition rates, and fraud percentages are not generalized facts. Songs are not arguments. Editorial inferences and the exercise are marked separately.
Listening navigation
- 02:08–13:59: Business differences and two organizational dimensions.
- 13:59–18:39: Culture, appraisal, and learning through work.
- 18:39–27:50: Demand, supply, and experience.
- 27:50–33:14: Evaluation evidence and mutual expectations.
- 35:24–39:11: AI sourcing and organizational comparisons.
- 39:22–48:53: Module ownership, OPCs, and age disagreements.
Related themes: organizational fit, recruiting evidence, AI collaboration. Further listening: Palona AI's outcome ownership and Yu Beichuan on growth and operating habits.