写明 Meta 超级智能实验室的人中,77% 在实验室成立时已在 Meta 工作
2026 年
- 722
- 936 人中,
2025 年 6 月实验室成立时已在 Meta 工作的人数 (77.1%) - 31
- 从外部
加入的 214 人中,刚离开 五家 AI 实验室之一的人数 (14.5%)
Meta 在 2025 年 6 月 30 日宣布成立该实验室时,把现有的 AI 团队(包括 FAIR)并入其中,所以实验室里本来就会有很多老员工。个人档案显示的是有多少,以及谁是新加入的。
写明实验室的
722 人在实验室成立时已在 Meta,44 人以前在 Meta 但当时不在,170 人是 Meta 新人。
统计的是谁
- 写明实验室
- 个人
资料 标题或当前 职位写有 superintelligence 或 MSL: 936 个档案, 其中 790 个写的是 superintelligence。 - 雇主
- 当前有一段在
Meta 的工作。 Metix AI Platform 把 Facebook 和 Meta 视为同一个 雇主; 以前的 Meta 工作也包括 Instagram、 WhatsApp 和 Oculus。 - 成立时已在 Meta
- 有一段
不是 实习的 Meta 工作, 开始于 2025 年 6 月以前, 并且到 2025 年 5 月或更晚仍在 进行。 - 外部加入
- 其余的人:
Meta 新人, 离开后又回到 Meta 的人,以及 只在 Meta 实习过的人。 - 日期
- 工作
开始 日期 截至 2026 年 4 月。个人档案 更新有滞后,最后 几个月的人数偏少。只写 年份的日期按 1 月算。 - 计数的含义
- 这是自己写明实验室的人的
可见 档案,数的是 档案, 不是 实验室的人数。不点任何人的名字。
要点
- 写明实验室的
936 人中, 722 人(77.1%)在实验室成立时已在 Meta。只算写 superintelligence 的 790 人,这个 比例是 78.1%。 - 170 名 Meta
新人从 2025 年 6 月(实验室成立的那个月)起集中 加入: 其中 107 人在 6 月到 9 月加入。 - 214 名外部
加入者中, 31 人(14.5%)刚离开 五家 AI 实验室之一, 其中 18 人来自 Google DeepMind; 22 人来自 大学, 16 人来自 Scale AI。 - 外部
加入者更偏研究: 50.5% 做研究,已在 Meta 的人是 30.6%。 实验室研究 人员中 67.5% 写有博士 学历, Meta 其他 研究 人员是 41.0%。
已在 Meta 的人
第 1 部分,图 01、02、03
写明实验室的人最早
01
典型成员在 2022 年首次加入 Meta;新人在 2025 年夏天集中加入
写明实验室的人首次
2014 年以前:14 人;2014 年 1 月到 2015 年 12 月:26 人,每年 13 人;2016 年 1 月到 2017 年 12 月:75 人,每年 37 人;2018 年 1 月到 2019 年 12 月:128 人,每年 64 人;2020 年 1 月到 2021 年 12 月:190 人,每年 95 人;2022 年 1 月到 12 月:114 人,每年 114 人;2023 年 1 月到 12 月:24 人,每年 24 人;2024 年 1 月到 12 月:118 人,每年 118 人;2025 年 1 月到 5 月:77 人,每年 186 人;2025 年 6 月:20 人,每年 244 人;2025 年 7 月:36 人,每年 424 人;2025 年 8 月:28 人,每年 330 人;2025 年 9 月:23 人,每年 280 人;2025 年 10 月到 12 月:29 人,每年 115 人;2026 年 1 月起,或没有开始日期:34 人,每年 103 人
图中所见
766 人在 2025 年 6 月以前首次加入 Meta,占写明实验室的人的 81.8%;一半的人在 2022 年底以前首次加入。2025 年 6 月到 9 月,平均每月 27 人首次加入,2024 年是每月 10 人。
方法与局限
首次加入是一个人最早那段 Meta 工作的开始日期,包括实习,所以成立前的部分也包括离开后又回来的人和只实习过的人(合计 44 人)。最后一段截至 2026 年 4 月,其中有不到 10 人没有开始日期;个人档案有滞后,这一段很可能偏少。早年只算到现在仍在 Meta、并写明实验室的人,所以和最近几个月相比会偏少。只写年份的开始日期按 1 月算,所以只写了 2025 年的新人会算在 2025 年 6 月以前。
来源:Metix AI Platform 个人档案数据,2026-09-22。
查询population.json · measures.json
{ "note": "Who is counted. A person counts when one job entry is at Meta and current (experience.company.name match current_employer and experience.is_current eq true, in one has_experience entry) and the profile's headline or current_title names the lab with one of lab_terms. The Platform matches text word by word, in any order, and ignores case, so MSL also matches msl and superintelligence also matches SuperIntelligence. Counts are profiles visible through the Metix AI Platform, never the lab's headcount; stale profiles count as current, so a count is not a guaranteed floor either.", "current_employer": "Meta", "current_employer_note": "match Meta on the current entry. The name also matches entries written as Facebook: a current entry named Facebook counts, and a Facebook condition returned all 790 profiles of the narrow definition, so the two names are one employer on the Platform and a Facebook condition is no separate test. company.name eq Meta returned the same 790 profiles as match Meta, and every one of the 63 profiles read in the audit has a current entry at Meta itself.", "lab_terms": [ "superintelligence", "MSL" ], "lab_fields": [ "headline", "current_title" ], "lab_terms_note": "superintelligence alone (the narrow definition) gives 790 profiles. MSL, the lab's short name, adds 146 current Meta profiles that never write superintelligence; 13 of 14 read in a whole slice use it for the lab, and the rest recruit for it. FAIR, one of the lab's groups since 2025, is not a lab term: people who name only FAIR do not name the lab, and teams.json counts them as context (fair_only).", "narrow_terms": [ "superintelligence" ], "history_names": [ "Meta", "Facebook", "Instagram", "WhatsApp", "Oculus" ], "history_names_note": "Names that count as an earlier job at Meta, matched word by word in one has_experience entry. The name Meta does not match an entry listed under Instagram; adding the other names moves fewer than 10 people.", "cut": "2025-06-01", "cut_note": "Meta announced Meta Superintelligence Labs at the end of June 2025. A person with a job entry at a history name that started before the cut had a Meta job before the lab. experience.start_date is a month (YYYY-MM) or a year; the Platform compares it as its first day, so a year alone reads as January. A newcomer whose Meta entry says only 2025 therefore counts as at Meta before the cut, which raises the share at Meta when the lab formed, and an earlier entry whose end date says only 2025 counts as ending before May 2025, which can move someone who was at Meta into returned.", "stay_end": "2025-05-01", "cohorts_note": "Four groups that do not overlap and add up to the whole. Stayed: a non-intern Meta entry that started before the cut and is current or ended in May 2025 or later, so the person was at Meta when the lab formed. Returned: a non-intern Meta entry before the cut, but none that lasted into May 2025, so they had left and came back. Former interns: the only Meta entries before the cut are internships. New to Meta: no Meta entry that started before the cut, including fewer than 10 whose current Meta entry has no start date. Returned, former interns, and new to Meta together are the outside hires, everyone who was not at Meta when the lab formed.", "intern_rule": "An entry is an internship when experience.seniority eq Intern or experience.title matches intern. Both are tested inside the same has_experience entry as the employer and the date.", "labeling_terms": [ "labeling", "labelling", "annotation", "annotator", "red teamer", "red teaming" ], "labeling_note": "Titles and headlines that name data labeling, annotation, or red teaming. The audit found such roles among recent hires (fewer than 10 in the slice read); vendors often staff them, but the profile lists Meta.", "freshness_note": "Profiles are a periodically refreshed snapshot. Across all Meta job entries on the Platform, 3,988 start in 2026, 1,104 of them in March and April and fewer than 10 in May or later, so start dates stop in April 2026 and the most recent months are probably undercounted. April 2026 is the last month shown, and people who joined since are missing.", "audit": "63 profiles read in whole slices, never from the top of a search, because Search ranks by match quality. The slices covered people with no Meta-named entry before the cut, people with a Meta entry before the cut, people who write MSL but not superintelligence, and the profiles whose Meta entry has no start date (fewer than 10). 62 of 63 describe themselves as working in the lab, and the rest recruit for it. All 63 have a current Meta entry, almost all of them named Meta. All 31 read with a Meta entry before the cut had a real Meta job there, not only an internship. Among people without a Meta-named entry before the cut, an earlier Meta job turned up listed under Instagram, which is why Instagram is a history name, and fewer than 10 of them hold data labeling or red teaming roles. Separate reads of sub-team matches found fewer than 10 profiles that say they have left the lab while the Meta entry is still current, so a few members are out of date. Records read for the audit are kept private.", "comparison": { "id": "microsoft", "label": "Microsoft", "current_employer": "Microsoft", "lab_terms": [ "superintelligence" ], "history_names": [ "Microsoft" ], "cut": "2025-11-01", "stay_end": "2025-10-01", "edges": [ "2012-01-01", "2016-01-01", "2020-01-01", "2023-01-01", "2025-01-01" ], "note": "Current Microsoft staff whose headline or current_title names superintelligence. Microsoft AI announced its superintelligence team in November 2025, so the cut for this group is 2025-11-01. Microsoft also matches Microsoft AI and Microsoft Research; subsidiaries with their own names (LinkedIn, GitHub) are not history names. A whole slice of 15 all named the Microsoft AI superintelligence team; fewer than 10 of them are recruiters or sourcers for it." }}
{ "note": "What is counted, all within the population in queries/population.json unless a block says otherwise. Every count is sent with size 1, so it costs 1 API Credit, or nothing when it finds no one, and reads no record.", "first_joined": { "edges": [ "2012-01-01", "2014-01-01", "2016-01-01", "2018-01-01", "2020-01-01", "2022-01-01", "2023-01-01", "2024-01-01", "2025-01-01" ], "after_cut_edges": [ "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "A person's first Meta job started before a date exactly when they have an entry at a history name that started before it, so a count at each edge gives how many first joined before it, and the difference between two edges is a band of first-join dates. Bands run from the start of the record through the cut (the dates in edges) and on month by month and quarter by quarter to April 2026 (after_cut_edges). The last band holds April 2026 and anything later, and the fewer than 10 whose Meta entry has no start date. Adjacent bands merge wherever one would hold 1 to 9 people; the cut is never merged away. The second series counts only non-intern entries, so it gives each person's first Meta job that was not an internship; it runs to the cut, and everyone without such a job before the cut is one band." }, "moves": { "edges": [ "2025-01-01", "2025-04-01", "2025-06-01", "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "For the people who stayed: when their latest current Meta entry started. A count of people with a current Meta entry that started on or after an edge gives how many started their newest current role since then, so a person with two current entries is placed by the newer one. Many people change teams inside Meta without adding an entry, so this shows who recorded a new role, a lower bound on who moved." }, "sources": { "ended_from": "2025-01-01", "note": "Where the outside hires (everyone not at Meta when the lab formed) had just been: a job entry that ended in 2025 or later (experience.end_date gte ended_from), which also means it is no longer current. Internships do not count for companies (the intern rule in population.json), so a PhD student's summer at a lab is not where they came from; for academia they do count, because doctoral students' university entries often carry the Intern label. Rows do not overlap: each person counts at the first row in this order whose condition they meet, and the rest are other employers or none. ai_lab marks the five AI labs whose subtotal is published.", "order": [ { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ], "ai_lab": true }, { "id": "google-deepmind", "label": "Google DeepMind", "names": [ "DeepMind" ], "ai_lab": true }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ], "ai_lab": true }, { "id": "xai", "label": "xAI", "names": [ "xAI" ], "ai_lab": true }, { "id": "thinking-machines", "label": "Thinking Machines Lab", "names": [ "Thinking Machines" ], "ai_lab": true }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "scale-ai", "label": "Scale AI", "names": [ "Scale AI" ] }, { "id": "google", "label": "Google, other than Google DeepMind", "names": [ "Google" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] }, { "id": "nvidia", "label": "NVIDIA", "names": [ "NVIDIA" ] }, { "id": "academia", "label": "A university or other educational institution", "company_type": "Educational" } ], "context": [ { "id": "google", "label": "Google, including Google DeepMind", "names": [ "Google", "DeepMind" ] }, { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ] }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ] }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] } ], "context_note": "For the whole group: anyone with a past (not current) non-intern job at the employer, at any time. These rows overlap and have no total. Names match word by word, so Google also matches Google DeepMind and Amazon matches Amazon Web Services (AWS). company.type Educational is the employer type the Platform records for universities and schools." }, "roles": { "functions": [ "Research", "Engineering and Technical", "Product" ], "senior": [ "Senior" ], "manager_up": [ "Manager", "Head", "Director", "Vice President", "President/Vice President", "C-Level", "Partner", "Founder", "Owner" ], "note": "current_function and current_seniority describe the current job and come from the Platform's fixed sets; either can be missing. Senior covers senior, staff, and principal individual contributors (the audit saw Staff, Senior Staff, and Principal titles labelled Senior); manager_up is Manager and every level above it; the rest of those with a stated level are Specialist or Intern. A doctorate is an education entry with education.degree eq Doctorate, finished or in progress.", "baseline_note": "The baseline is Meta's other research staff: a current Meta entry, current_function eq Research, and no lab term in the headline or current title. It includes people who name FAIR only." }, "teams": [ { "id": "fair", "label": "FAIR", "terms": [ "FAIR" ] }, { "id": "tbd-lab", "label": "TBD Lab", "terms": [ "TBD" ] }, { "id": "infra", "label": "MSL Infra and other infrastructure", "terms": [ "infra", "infrastructure" ] }, { "id": "par", "label": "Products and Applied Research", "terms": [ "PAR", "product applied research" ] } ], "teams_note": "Sub-team names in the headline or current title of people in the population, matched word by word; a person can name more than one. Audited: FAIR, 10 profiles naming it read in whole slices, nearly all naming it as the current team. TBD, all 13 matches read: 10 are in TBD Lab or report to it, and the rest name TBD while recruiting for it, while saying they are not in it, or while saying they have left the lab. Infra, the first 15 of 49 matches for infra or infrastructure (not a whole slice): all 15 work on infrastructure inside the lab, 11 of them naming MSL Infra or Infra at MSL. Products and Applied Research: the words applied research mostly match the job title Applied Research Scientist (most of those read) or an old team name, so the row needs PAR or all of product, applied, and research. fair_only counts current Meta profiles that name FAIR and no lab term; it was not audited outside the population.", "places": { "states": [ "California", "New York", "Washington" ], "bay_area": [ "Menlo Park", "San Francisco", "Sunnyvale", "Palo Alto", "Mountain View", "Redwood City", "Burlingame", "Fremont", "San Jose", "Santa Clara", "San Mateo", "Foster City", "Oakland", "Berkeley", "Cupertino", "Los Altos", "Belmont", "San Carlos", "Millbrae", "San Bruno", "Newark", "Milpitas", "Los Gatos", "Campbell", "Saratoga", "Daly City", "South San Francisco", "Emeryville", "Alameda", "Hayward", "Dublin", "Pleasanton", "Walnut Creek", "Atherton", "Portola Valley", "Woodside", "Half Moon Bay" ], "countries": [ "United Kingdom" ], "note": "The profile's own location, where people list themselves: location.country and location.state, and location.city for the Bay Area, whose cities are listed one by one and compared exactly." }, "postings": { "company": "Meta", "title_terms": [ "superintelligence", "MSL" ], "description_terms": [ "superintelligence labs" ], "research_title": "research", "cities": [ "Menlo Park", "San Francisco" ], "states": [ "New York" ], "experience_max_months": 36, "posted_from": "2026-09-01", "note": "Open Meta postings (is_open eq true) whose title names superintelligence or MSL, or whose description contains the words superintelligence and labs. All 30 read on 2026-09-22 are Meta postings whose description names Meta Superintelligence Labs. Every one carries the seniority label Not Applicable, so seniority says nothing here, and all were posted in September 2026, so the index shows the openings of the moment rather than a history. Counts of postings carry no minimum." }}
02
77.1% 的人在实验室成立时已在 Meta;只算写 superintelligence 的人是 78.1%
每一行是
写 superintelligence 或 MSL:722 人成立时在 Meta,44 人以前在,170 人是新人;只写 superintelligence:617 / 790;团队成立前在本公司工作过:Meta 81.8%,Microsoft 76.3%
图中所见
两种口径下,成立时已在 Meta 的比例只差 1.0 个百分点。Microsoft 在 2025 年 11 月宣布组建超级智能团队;用同一口径,它的 80 人中 76.3% 以前在 Microsoft 工作过,Meta 是 81.8%。
方法与局限
以前在 Meta、当时不在的 44 人中,19 人离开后又回来,25 人只实习过。Microsoft 的 80 人是当前在 Microsoft、标题或职位写有 superintelligence 的档案;抽读时发现其中有招聘人员,而且公司名不包括 LinkedIn、GitHub 等子公司。只写年份的日期按 1 月算,所以只写了 2025 年结束的工作算作在 2025 年 5 月以前结束,可能把人算进离开后又回来的 19 人。个人档案截至 2026 年 4 月,这对 Microsoft 团队成立以来那几个月的影响比对 Meta 大,所以它的比例可能偏高。
来源:Metix AI Platform 个人档案数据,2026-09-22。
查询population.json · measures.json
{ "note": "Who is counted. A person counts when one job entry is at Meta and current (experience.company.name match current_employer and experience.is_current eq true, in one has_experience entry) and the profile's headline or current_title names the lab with one of lab_terms. The Platform matches text word by word, in any order, and ignores case, so MSL also matches msl and superintelligence also matches SuperIntelligence. Counts are profiles visible through the Metix AI Platform, never the lab's headcount; stale profiles count as current, so a count is not a guaranteed floor either.", "current_employer": "Meta", "current_employer_note": "match Meta on the current entry. The name also matches entries written as Facebook: a current entry named Facebook counts, and a Facebook condition returned all 790 profiles of the narrow definition, so the two names are one employer on the Platform and a Facebook condition is no separate test. company.name eq Meta returned the same 790 profiles as match Meta, and every one of the 63 profiles read in the audit has a current entry at Meta itself.", "lab_terms": [ "superintelligence", "MSL" ], "lab_fields": [ "headline", "current_title" ], "lab_terms_note": "superintelligence alone (the narrow definition) gives 790 profiles. MSL, the lab's short name, adds 146 current Meta profiles that never write superintelligence; 13 of 14 read in a whole slice use it for the lab, and the rest recruit for it. FAIR, one of the lab's groups since 2025, is not a lab term: people who name only FAIR do not name the lab, and teams.json counts them as context (fair_only).", "narrow_terms": [ "superintelligence" ], "history_names": [ "Meta", "Facebook", "Instagram", "WhatsApp", "Oculus" ], "history_names_note": "Names that count as an earlier job at Meta, matched word by word in one has_experience entry. The name Meta does not match an entry listed under Instagram; adding the other names moves fewer than 10 people.", "cut": "2025-06-01", "cut_note": "Meta announced Meta Superintelligence Labs at the end of June 2025. A person with a job entry at a history name that started before the cut had a Meta job before the lab. experience.start_date is a month (YYYY-MM) or a year; the Platform compares it as its first day, so a year alone reads as January. A newcomer whose Meta entry says only 2025 therefore counts as at Meta before the cut, which raises the share at Meta when the lab formed, and an earlier entry whose end date says only 2025 counts as ending before May 2025, which can move someone who was at Meta into returned.", "stay_end": "2025-05-01", "cohorts_note": "Four groups that do not overlap and add up to the whole. Stayed: a non-intern Meta entry that started before the cut and is current or ended in May 2025 or later, so the person was at Meta when the lab formed. Returned: a non-intern Meta entry before the cut, but none that lasted into May 2025, so they had left and came back. Former interns: the only Meta entries before the cut are internships. New to Meta: no Meta entry that started before the cut, including fewer than 10 whose current Meta entry has no start date. Returned, former interns, and new to Meta together are the outside hires, everyone who was not at Meta when the lab formed.", "intern_rule": "An entry is an internship when experience.seniority eq Intern or experience.title matches intern. Both are tested inside the same has_experience entry as the employer and the date.", "labeling_terms": [ "labeling", "labelling", "annotation", "annotator", "red teamer", "red teaming" ], "labeling_note": "Titles and headlines that name data labeling, annotation, or red teaming. The audit found such roles among recent hires (fewer than 10 in the slice read); vendors often staff them, but the profile lists Meta.", "freshness_note": "Profiles are a periodically refreshed snapshot. Across all Meta job entries on the Platform, 3,988 start in 2026, 1,104 of them in March and April and fewer than 10 in May or later, so start dates stop in April 2026 and the most recent months are probably undercounted. April 2026 is the last month shown, and people who joined since are missing.", "audit": "63 profiles read in whole slices, never from the top of a search, because Search ranks by match quality. The slices covered people with no Meta-named entry before the cut, people with a Meta entry before the cut, people who write MSL but not superintelligence, and the profiles whose Meta entry has no start date (fewer than 10). 62 of 63 describe themselves as working in the lab, and the rest recruit for it. All 63 have a current Meta entry, almost all of them named Meta. All 31 read with a Meta entry before the cut had a real Meta job there, not only an internship. Among people without a Meta-named entry before the cut, an earlier Meta job turned up listed under Instagram, which is why Instagram is a history name, and fewer than 10 of them hold data labeling or red teaming roles. Separate reads of sub-team matches found fewer than 10 profiles that say they have left the lab while the Meta entry is still current, so a few members are out of date. Records read for the audit are kept private.", "comparison": { "id": "microsoft", "label": "Microsoft", "current_employer": "Microsoft", "lab_terms": [ "superintelligence" ], "history_names": [ "Microsoft" ], "cut": "2025-11-01", "stay_end": "2025-10-01", "edges": [ "2012-01-01", "2016-01-01", "2020-01-01", "2023-01-01", "2025-01-01" ], "note": "Current Microsoft staff whose headline or current_title names superintelligence. Microsoft AI announced its superintelligence team in November 2025, so the cut for this group is 2025-11-01. Microsoft also matches Microsoft AI and Microsoft Research; subsidiaries with their own names (LinkedIn, GitHub) are not history names. A whole slice of 15 all named the Microsoft AI superintelligence team; fewer than 10 of them are recruiters or sourcers for it." }}
{ "note": "What is counted, all within the population in queries/population.json unless a block says otherwise. Every count is sent with size 1, so it costs 1 API Credit, or nothing when it finds no one, and reads no record.", "first_joined": { "edges": [ "2012-01-01", "2014-01-01", "2016-01-01", "2018-01-01", "2020-01-01", "2022-01-01", "2023-01-01", "2024-01-01", "2025-01-01" ], "after_cut_edges": [ "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "A person's first Meta job started before a date exactly when they have an entry at a history name that started before it, so a count at each edge gives how many first joined before it, and the difference between two edges is a band of first-join dates. Bands run from the start of the record through the cut (the dates in edges) and on month by month and quarter by quarter to April 2026 (after_cut_edges). The last band holds April 2026 and anything later, and the fewer than 10 whose Meta entry has no start date. Adjacent bands merge wherever one would hold 1 to 9 people; the cut is never merged away. The second series counts only non-intern entries, so it gives each person's first Meta job that was not an internship; it runs to the cut, and everyone without such a job before the cut is one band." }, "moves": { "edges": [ "2025-01-01", "2025-04-01", "2025-06-01", "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "For the people who stayed: when their latest current Meta entry started. A count of people with a current Meta entry that started on or after an edge gives how many started their newest current role since then, so a person with two current entries is placed by the newer one. Many people change teams inside Meta without adding an entry, so this shows who recorded a new role, a lower bound on who moved." }, "sources": { "ended_from": "2025-01-01", "note": "Where the outside hires (everyone not at Meta when the lab formed) had just been: a job entry that ended in 2025 or later (experience.end_date gte ended_from), which also means it is no longer current. Internships do not count for companies (the intern rule in population.json), so a PhD student's summer at a lab is not where they came from; for academia they do count, because doctoral students' university entries often carry the Intern label. Rows do not overlap: each person counts at the first row in this order whose condition they meet, and the rest are other employers or none. ai_lab marks the five AI labs whose subtotal is published.", "order": [ { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ], "ai_lab": true }, { "id": "google-deepmind", "label": "Google DeepMind", "names": [ "DeepMind" ], "ai_lab": true }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ], "ai_lab": true }, { "id": "xai", "label": "xAI", "names": [ "xAI" ], "ai_lab": true }, { "id": "thinking-machines", "label": "Thinking Machines Lab", "names": [ "Thinking Machines" ], "ai_lab": true }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "scale-ai", "label": "Scale AI", "names": [ "Scale AI" ] }, { "id": "google", "label": "Google, other than Google DeepMind", "names": [ "Google" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] }, { "id": "nvidia", "label": "NVIDIA", "names": [ "NVIDIA" ] }, { "id": "academia", "label": "A university or other educational institution", "company_type": "Educational" } ], "context": [ { "id": "google", "label": "Google, including Google DeepMind", "names": [ "Google", "DeepMind" ] }, { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ] }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ] }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] } ], "context_note": "For the whole group: anyone with a past (not current) non-intern job at the employer, at any time. These rows overlap and have no total. Names match word by word, so Google also matches Google DeepMind and Amazon matches Amazon Web Services (AWS). company.type Educational is the employer type the Platform records for universities and schools." }, "roles": { "functions": [ "Research", "Engineering and Technical", "Product" ], "senior": [ "Senior" ], "manager_up": [ "Manager", "Head", "Director", "Vice President", "President/Vice President", "C-Level", "Partner", "Founder", "Owner" ], "note": "current_function and current_seniority describe the current job and come from the Platform's fixed sets; either can be missing. Senior covers senior, staff, and principal individual contributors (the audit saw Staff, Senior Staff, and Principal titles labelled Senior); manager_up is Manager and every level above it; the rest of those with a stated level are Specialist or Intern. A doctorate is an education entry with education.degree eq Doctorate, finished or in progress.", "baseline_note": "The baseline is Meta's other research staff: a current Meta entry, current_function eq Research, and no lab term in the headline or current title. It includes people who name FAIR only." }, "teams": [ { "id": "fair", "label": "FAIR", "terms": [ "FAIR" ] }, { "id": "tbd-lab", "label": "TBD Lab", "terms": [ "TBD" ] }, { "id": "infra", "label": "MSL Infra and other infrastructure", "terms": [ "infra", "infrastructure" ] }, { "id": "par", "label": "Products and Applied Research", "terms": [ "PAR", "product applied research" ] } ], "teams_note": "Sub-team names in the headline or current title of people in the population, matched word by word; a person can name more than one. Audited: FAIR, 10 profiles naming it read in whole slices, nearly all naming it as the current team. TBD, all 13 matches read: 10 are in TBD Lab or report to it, and the rest name TBD while recruiting for it, while saying they are not in it, or while saying they have left the lab. Infra, the first 15 of 49 matches for infra or infrastructure (not a whole slice): all 15 work on infrastructure inside the lab, 11 of them naming MSL Infra or Infra at MSL. Products and Applied Research: the words applied research mostly match the job title Applied Research Scientist (most of those read) or an old team name, so the row needs PAR or all of product, applied, and research. fair_only counts current Meta profiles that name FAIR and no lab term; it was not audited outside the population.", "places": { "states": [ "California", "New York", "Washington" ], "bay_area": [ "Menlo Park", "San Francisco", "Sunnyvale", "Palo Alto", "Mountain View", "Redwood City", "Burlingame", "Fremont", "San Jose", "Santa Clara", "San Mateo", "Foster City", "Oakland", "Berkeley", "Cupertino", "Los Altos", "Belmont", "San Carlos", "Millbrae", "San Bruno", "Newark", "Milpitas", "Los Gatos", "Campbell", "Saratoga", "Daly City", "South San Francisco", "Emeryville", "Alameda", "Hayward", "Dublin", "Pleasanton", "Walnut Creek", "Atherton", "Portola Valley", "Woodside", "Half Moon Bay" ], "countries": [ "United Kingdom" ], "note": "The profile's own location, where people list themselves: location.country and location.state, and location.city for the Bay Area, whose cities are listed one by one and compared exactly." }, "postings": { "company": "Meta", "title_terms": [ "superintelligence", "MSL" ], "description_terms": [ "superintelligence labs" ], "research_title": "research", "cities": [ "Menlo Park", "San Francisco" ], "states": [ "New York" ], "experience_max_months": 36, "posted_from": "2026-09-01", "note": "Open Meta postings (is_open eq true) whose title names superintelligence or MSL, or whose description contains the words superintelligence and labs. All 30 read on 2026-09-22 are Meta postings whose description names Meta Superintelligence Labs. Every one carries the seniority label Not Applicable, so seniority says nothing here, and all were posted in September 2026, so the index shows the openings of the moment rather than a history. Counts of postings carry no minimum." }}
03
实验室成立时已在 Meta 的人中,14.8% 从 2025 年 6 月起记录了新的 Meta 职位
成立时已在
2025 年以前,或没有日期 476,2025 年 1 月到 3 月 86,2025 年 4 月到 5 月 53,2025 年 6 月到 7 月 28,2025 年 8 月 27,2025 年 9 月到 12 月 21,2026 年 1 月起 31
2025 年 6 月以前
- 2025 年以前,或没有日期476 · 65.9%
- 2025 年 1 月到 3 月86 · 11.9%
- 2025 年 4 月到 5 月53 · 7.3%
2025 年 6 月起:107 人,14.8%
- 2025 年 6 月到 7 月28 · 3.9%
- 2025 年 8 月27 · 3.7%
- 2025 年 9 月到 12 月21 · 2.9%
- 2026 年 1 月起31 · 4.3%
图中所见
已在 Meta 的人中,2025 年 6 月起记录新职位的 107 人里,55 人在 2025 年 8 月底以前。大多数已在 Meta 的人(65.9%)的最新职位开始于 2025 年以前,或没有日期。
方法与局限
日期是一个人当前最新一段 Meta 工作的开始日期。很多人在 Meta 内部换团队时不会新加一段经历,所以这是换岗人数的下限。第一行也包括没有开始日期的工作。
来源:Metix AI Platform 个人档案数据,2026-09-22。
查询population.json · measures.json
{ "note": "Who is counted. A person counts when one job entry is at Meta and current (experience.company.name match current_employer and experience.is_current eq true, in one has_experience entry) and the profile's headline or current_title names the lab with one of lab_terms. The Platform matches text word by word, in any order, and ignores case, so MSL also matches msl and superintelligence also matches SuperIntelligence. Counts are profiles visible through the Metix AI Platform, never the lab's headcount; stale profiles count as current, so a count is not a guaranteed floor either.", "current_employer": "Meta", "current_employer_note": "match Meta on the current entry. The name also matches entries written as Facebook: a current entry named Facebook counts, and a Facebook condition returned all 790 profiles of the narrow definition, so the two names are one employer on the Platform and a Facebook condition is no separate test. company.name eq Meta returned the same 790 profiles as match Meta, and every one of the 63 profiles read in the audit has a current entry at Meta itself.", "lab_terms": [ "superintelligence", "MSL" ], "lab_fields": [ "headline", "current_title" ], "lab_terms_note": "superintelligence alone (the narrow definition) gives 790 profiles. MSL, the lab's short name, adds 146 current Meta profiles that never write superintelligence; 13 of 14 read in a whole slice use it for the lab, and the rest recruit for it. FAIR, one of the lab's groups since 2025, is not a lab term: people who name only FAIR do not name the lab, and teams.json counts them as context (fair_only).", "narrow_terms": [ "superintelligence" ], "history_names": [ "Meta", "Facebook", "Instagram", "WhatsApp", "Oculus" ], "history_names_note": "Names that count as an earlier job at Meta, matched word by word in one has_experience entry. The name Meta does not match an entry listed under Instagram; adding the other names moves fewer than 10 people.", "cut": "2025-06-01", "cut_note": "Meta announced Meta Superintelligence Labs at the end of June 2025. A person with a job entry at a history name that started before the cut had a Meta job before the lab. experience.start_date is a month (YYYY-MM) or a year; the Platform compares it as its first day, so a year alone reads as January. A newcomer whose Meta entry says only 2025 therefore counts as at Meta before the cut, which raises the share at Meta when the lab formed, and an earlier entry whose end date says only 2025 counts as ending before May 2025, which can move someone who was at Meta into returned.", "stay_end": "2025-05-01", "cohorts_note": "Four groups that do not overlap and add up to the whole. Stayed: a non-intern Meta entry that started before the cut and is current or ended in May 2025 or later, so the person was at Meta when the lab formed. Returned: a non-intern Meta entry before the cut, but none that lasted into May 2025, so they had left and came back. Former interns: the only Meta entries before the cut are internships. New to Meta: no Meta entry that started before the cut, including fewer than 10 whose current Meta entry has no start date. Returned, former interns, and new to Meta together are the outside hires, everyone who was not at Meta when the lab formed.", "intern_rule": "An entry is an internship when experience.seniority eq Intern or experience.title matches intern. Both are tested inside the same has_experience entry as the employer and the date.", "labeling_terms": [ "labeling", "labelling", "annotation", "annotator", "red teamer", "red teaming" ], "labeling_note": "Titles and headlines that name data labeling, annotation, or red teaming. The audit found such roles among recent hires (fewer than 10 in the slice read); vendors often staff them, but the profile lists Meta.", "freshness_note": "Profiles are a periodically refreshed snapshot. Across all Meta job entries on the Platform, 3,988 start in 2026, 1,104 of them in March and April and fewer than 10 in May or later, so start dates stop in April 2026 and the most recent months are probably undercounted. April 2026 is the last month shown, and people who joined since are missing.", "audit": "63 profiles read in whole slices, never from the top of a search, because Search ranks by match quality. The slices covered people with no Meta-named entry before the cut, people with a Meta entry before the cut, people who write MSL but not superintelligence, and the profiles whose Meta entry has no start date (fewer than 10). 62 of 63 describe themselves as working in the lab, and the rest recruit for it. All 63 have a current Meta entry, almost all of them named Meta. All 31 read with a Meta entry before the cut had a real Meta job there, not only an internship. Among people without a Meta-named entry before the cut, an earlier Meta job turned up listed under Instagram, which is why Instagram is a history name, and fewer than 10 of them hold data labeling or red teaming roles. Separate reads of sub-team matches found fewer than 10 profiles that say they have left the lab while the Meta entry is still current, so a few members are out of date. Records read for the audit are kept private.", "comparison": { "id": "microsoft", "label": "Microsoft", "current_employer": "Microsoft", "lab_terms": [ "superintelligence" ], "history_names": [ "Microsoft" ], "cut": "2025-11-01", "stay_end": "2025-10-01", "edges": [ "2012-01-01", "2016-01-01", "2020-01-01", "2023-01-01", "2025-01-01" ], "note": "Current Microsoft staff whose headline or current_title names superintelligence. Microsoft AI announced its superintelligence team in November 2025, so the cut for this group is 2025-11-01. Microsoft also matches Microsoft AI and Microsoft Research; subsidiaries with their own names (LinkedIn, GitHub) are not history names. A whole slice of 15 all named the Microsoft AI superintelligence team; fewer than 10 of them are recruiters or sourcers for it." }}
{ "note": "What is counted, all within the population in queries/population.json unless a block says otherwise. Every count is sent with size 1, so it costs 1 API Credit, or nothing when it finds no one, and reads no record.", "first_joined": { "edges": [ "2012-01-01", "2014-01-01", "2016-01-01", "2018-01-01", "2020-01-01", "2022-01-01", "2023-01-01", "2024-01-01", "2025-01-01" ], "after_cut_edges": [ "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "A person's first Meta job started before a date exactly when they have an entry at a history name that started before it, so a count at each edge gives how many first joined before it, and the difference between two edges is a band of first-join dates. Bands run from the start of the record through the cut (the dates in edges) and on month by month and quarter by quarter to April 2026 (after_cut_edges). The last band holds April 2026 and anything later, and the fewer than 10 whose Meta entry has no start date. Adjacent bands merge wherever one would hold 1 to 9 people; the cut is never merged away. The second series counts only non-intern entries, so it gives each person's first Meta job that was not an internship; it runs to the cut, and everyone without such a job before the cut is one band." }, "moves": { "edges": [ "2025-01-01", "2025-04-01", "2025-06-01", "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "For the people who stayed: when their latest current Meta entry started. A count of people with a current Meta entry that started on or after an edge gives how many started their newest current role since then, so a person with two current entries is placed by the newer one. Many people change teams inside Meta without adding an entry, so this shows who recorded a new role, a lower bound on who moved." }, "sources": { "ended_from": "2025-01-01", "note": "Where the outside hires (everyone not at Meta when the lab formed) had just been: a job entry that ended in 2025 or later (experience.end_date gte ended_from), which also means it is no longer current. Internships do not count for companies (the intern rule in population.json), so a PhD student's summer at a lab is not where they came from; for academia they do count, because doctoral students' university entries often carry the Intern label. Rows do not overlap: each person counts at the first row in this order whose condition they meet, and the rest are other employers or none. ai_lab marks the five AI labs whose subtotal is published.", "order": [ { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ], "ai_lab": true }, { "id": "google-deepmind", "label": "Google DeepMind", "names": [ "DeepMind" ], "ai_lab": true }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ], "ai_lab": true }, { "id": "xai", "label": "xAI", "names": [ "xAI" ], "ai_lab": true }, { "id": "thinking-machines", "label": "Thinking Machines Lab", "names": [ "Thinking Machines" ], "ai_lab": true }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "scale-ai", "label": "Scale AI", "names": [ "Scale AI" ] }, { "id": "google", "label": "Google, other than Google DeepMind", "names": [ "Google" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] }, { "id": "nvidia", "label": "NVIDIA", "names": [ "NVIDIA" ] }, { "id": "academia", "label": "A university or other educational institution", "company_type": "Educational" } ], "context": [ { "id": "google", "label": "Google, including Google DeepMind", "names": [ "Google", "DeepMind" ] }, { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ] }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ] }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] } ], "context_note": "For the whole group: anyone with a past (not current) non-intern job at the employer, at any time. These rows overlap and have no total. Names match word by word, so Google also matches Google DeepMind and Amazon matches Amazon Web Services (AWS). company.type Educational is the employer type the Platform records for universities and schools." }, "roles": { "functions": [ "Research", "Engineering and Technical", "Product" ], "senior": [ "Senior" ], "manager_up": [ "Manager", "Head", "Director", "Vice President", "President/Vice President", "C-Level", "Partner", "Founder", "Owner" ], "note": "current_function and current_seniority describe the current job and come from the Platform's fixed sets; either can be missing. Senior covers senior, staff, and principal individual contributors (the audit saw Staff, Senior Staff, and Principal titles labelled Senior); manager_up is Manager and every level above it; the rest of those with a stated level are Specialist or Intern. A doctorate is an education entry with education.degree eq Doctorate, finished or in progress.", "baseline_note": "The baseline is Meta's other research staff: a current Meta entry, current_function eq Research, and no lab term in the headline or current title. It includes people who name FAIR only." }, "teams": [ { "id": "fair", "label": "FAIR", "terms": [ "FAIR" ] }, { "id": "tbd-lab", "label": "TBD Lab", "terms": [ "TBD" ] }, { "id": "infra", "label": "MSL Infra and other infrastructure", "terms": [ "infra", "infrastructure" ] }, { "id": "par", "label": "Products and Applied Research", "terms": [ "PAR", "product applied research" ] } ], "teams_note": "Sub-team names in the headline or current title of people in the population, matched word by word; a person can name more than one. Audited: FAIR, 10 profiles naming it read in whole slices, nearly all naming it as the current team. TBD, all 13 matches read: 10 are in TBD Lab or report to it, and the rest name TBD while recruiting for it, while saying they are not in it, or while saying they have left the lab. Infra, the first 15 of 49 matches for infra or infrastructure (not a whole slice): all 15 work on infrastructure inside the lab, 11 of them naming MSL Infra or Infra at MSL. Products and Applied Research: the words applied research mostly match the job title Applied Research Scientist (most of those read) or an old team name, so the row needs PAR or all of product, applied, and research. fair_only counts current Meta profiles that name FAIR and no lab term; it was not audited outside the population.", "places": { "states": [ "California", "New York", "Washington" ], "bay_area": [ "Menlo Park", "San Francisco", "Sunnyvale", "Palo Alto", "Mountain View", "Redwood City", "Burlingame", "Fremont", "San Jose", "Santa Clara", "San Mateo", "Foster City", "Oakland", "Berkeley", "Cupertino", "Los Altos", "Belmont", "San Carlos", "Millbrae", "San Bruno", "Newark", "Milpitas", "Los Gatos", "Campbell", "Saratoga", "Daly City", "South San Francisco", "Emeryville", "Alameda", "Hayward", "Dublin", "Pleasanton", "Walnut Creek", "Atherton", "Portola Valley", "Woodside", "Half Moon Bay" ], "countries": [ "United Kingdom" ], "note": "The profile's own location, where people list themselves: location.country and location.state, and location.city for the Bay Area, whose cities are listed one by one and compared exactly." }, "postings": { "company": "Meta", "title_terms": [ "superintelligence", "MSL" ], "description_terms": [ "superintelligence labs" ], "research_title": "research", "cities": [ "Menlo Park", "San Francisco" ], "states": [ "New York" ], "experience_max_months": 36, "posted_from": "2026-09-01", "note": "Open Meta postings (is_open eq true) whose title names superintelligence or MSL, or whose description contains the words superintelligence and labs. All 30 read on 2026-09-22 are Meta postings whose description names Meta Superintelligence Labs. Every one carries the seniority label Not Applicable, so seniority says nothing here, and all were posted in September 2026, so the index shows the openings of the moment rather than a history. Counts of postings carry no minimum." }}
从外部加入的人
第 2 部分,图 04、05
214 名外部
04
214 名外部加入者中,31 人刚离开五家 AI 实验室之一,其中 18 人来自 Google DeepMind
外部
OpenAI <10,Google DeepMind 18,Anthropic 0,xAI <10,Thinking Machines Lab 0,Apple <10,Scale AI 16,Google(Google DeepMind 以外) 16,Microsoft <10,Amazon 10,NVIDIA <10,大学或其他教育机构 22,其他雇主,或没有 2025 年或以后结束的工作 101
五家 AI 实验室:31 人,14.5%
- Google DeepMind18 · 8.4%
- OpenAI<10
- xAI<10
- Anthropic0
- Thinking Machines Lab0
其他地方
- 大学或其他教育机构22 · 10.3%
- Scale AI16 · 7.5%
- Google(Google DeepMind 以外)16 · 7.5%
- Amazon10 · 4.7%
- Apple<10
- Microsoft<10
- NVIDIA<10
- 其他雇主,或没有 2025 年或以后结束的工作101 · 47.2%
图中所见
在整个群体里,在大型科技公司工作过的人很多:133 人(14.2%)曾在 Google 工作(包括 Google DeepMind),110 人在 Amazon,92 人在 Microsoft。在 OpenAI 工作过的只有 12 人,Anthropic 没有。据 Axios 报道,Meta 在 2025 年 6 月大笔入股 Scale AI。
方法与局限
一段工作必须不是实习、并在 2025 年或以后结束才算。每人按固定顺序只算在第一个匹配的雇主:OpenAI、Google DeepMind、Anthropic、xAI、Thinking Machines Lab、Apple、Scale AI、Google、Microsoft、Amazon、NVIDIA,最后是大学;大学的实习也算,因为博士生的经历常标为实习。1 到 9 人显示为 <10,画成可能的最大值处的空框。
来源:Metix AI Platform 个人档案数据,2026-09-22。
查询population.json · measures.json
{ "note": "Who is counted. A person counts when one job entry is at Meta and current (experience.company.name match current_employer and experience.is_current eq true, in one has_experience entry) and the profile's headline or current_title names the lab with one of lab_terms. The Platform matches text word by word, in any order, and ignores case, so MSL also matches msl and superintelligence also matches SuperIntelligence. Counts are profiles visible through the Metix AI Platform, never the lab's headcount; stale profiles count as current, so a count is not a guaranteed floor either.", "current_employer": "Meta", "current_employer_note": "match Meta on the current entry. The name also matches entries written as Facebook: a current entry named Facebook counts, and a Facebook condition returned all 790 profiles of the narrow definition, so the two names are one employer on the Platform and a Facebook condition is no separate test. company.name eq Meta returned the same 790 profiles as match Meta, and every one of the 63 profiles read in the audit has a current entry at Meta itself.", "lab_terms": [ "superintelligence", "MSL" ], "lab_fields": [ "headline", "current_title" ], "lab_terms_note": "superintelligence alone (the narrow definition) gives 790 profiles. MSL, the lab's short name, adds 146 current Meta profiles that never write superintelligence; 13 of 14 read in a whole slice use it for the lab, and the rest recruit for it. FAIR, one of the lab's groups since 2025, is not a lab term: people who name only FAIR do not name the lab, and teams.json counts them as context (fair_only).", "narrow_terms": [ "superintelligence" ], "history_names": [ "Meta", "Facebook", "Instagram", "WhatsApp", "Oculus" ], "history_names_note": "Names that count as an earlier job at Meta, matched word by word in one has_experience entry. The name Meta does not match an entry listed under Instagram; adding the other names moves fewer than 10 people.", "cut": "2025-06-01", "cut_note": "Meta announced Meta Superintelligence Labs at the end of June 2025. A person with a job entry at a history name that started before the cut had a Meta job before the lab. experience.start_date is a month (YYYY-MM) or a year; the Platform compares it as its first day, so a year alone reads as January. A newcomer whose Meta entry says only 2025 therefore counts as at Meta before the cut, which raises the share at Meta when the lab formed, and an earlier entry whose end date says only 2025 counts as ending before May 2025, which can move someone who was at Meta into returned.", "stay_end": "2025-05-01", "cohorts_note": "Four groups that do not overlap and add up to the whole. Stayed: a non-intern Meta entry that started before the cut and is current or ended in May 2025 or later, so the person was at Meta when the lab formed. Returned: a non-intern Meta entry before the cut, but none that lasted into May 2025, so they had left and came back. Former interns: the only Meta entries before the cut are internships. New to Meta: no Meta entry that started before the cut, including fewer than 10 whose current Meta entry has no start date. Returned, former interns, and new to Meta together are the outside hires, everyone who was not at Meta when the lab formed.", "intern_rule": "An entry is an internship when experience.seniority eq Intern or experience.title matches intern. Both are tested inside the same has_experience entry as the employer and the date.", "labeling_terms": [ "labeling", "labelling", "annotation", "annotator", "red teamer", "red teaming" ], "labeling_note": "Titles and headlines that name data labeling, annotation, or red teaming. The audit found such roles among recent hires (fewer than 10 in the slice read); vendors often staff them, but the profile lists Meta.", "freshness_note": "Profiles are a periodically refreshed snapshot. Across all Meta job entries on the Platform, 3,988 start in 2026, 1,104 of them in March and April and fewer than 10 in May or later, so start dates stop in April 2026 and the most recent months are probably undercounted. April 2026 is the last month shown, and people who joined since are missing.", "audit": "63 profiles read in whole slices, never from the top of a search, because Search ranks by match quality. The slices covered people with no Meta-named entry before the cut, people with a Meta entry before the cut, people who write MSL but not superintelligence, and the profiles whose Meta entry has no start date (fewer than 10). 62 of 63 describe themselves as working in the lab, and the rest recruit for it. All 63 have a current Meta entry, almost all of them named Meta. All 31 read with a Meta entry before the cut had a real Meta job there, not only an internship. Among people without a Meta-named entry before the cut, an earlier Meta job turned up listed under Instagram, which is why Instagram is a history name, and fewer than 10 of them hold data labeling or red teaming roles. Separate reads of sub-team matches found fewer than 10 profiles that say they have left the lab while the Meta entry is still current, so a few members are out of date. Records read for the audit are kept private.", "comparison": { "id": "microsoft", "label": "Microsoft", "current_employer": "Microsoft", "lab_terms": [ "superintelligence" ], "history_names": [ "Microsoft" ], "cut": "2025-11-01", "stay_end": "2025-10-01", "edges": [ "2012-01-01", "2016-01-01", "2020-01-01", "2023-01-01", "2025-01-01" ], "note": "Current Microsoft staff whose headline or current_title names superintelligence. Microsoft AI announced its superintelligence team in November 2025, so the cut for this group is 2025-11-01. Microsoft also matches Microsoft AI and Microsoft Research; subsidiaries with their own names (LinkedIn, GitHub) are not history names. A whole slice of 15 all named the Microsoft AI superintelligence team; fewer than 10 of them are recruiters or sourcers for it." }}
{ "note": "What is counted, all within the population in queries/population.json unless a block says otherwise. Every count is sent with size 1, so it costs 1 API Credit, or nothing when it finds no one, and reads no record.", "first_joined": { "edges": [ "2012-01-01", "2014-01-01", "2016-01-01", "2018-01-01", "2020-01-01", "2022-01-01", "2023-01-01", "2024-01-01", "2025-01-01" ], "after_cut_edges": [ "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "A person's first Meta job started before a date exactly when they have an entry at a history name that started before it, so a count at each edge gives how many first joined before it, and the difference between two edges is a band of first-join dates. Bands run from the start of the record through the cut (the dates in edges) and on month by month and quarter by quarter to April 2026 (after_cut_edges). The last band holds April 2026 and anything later, and the fewer than 10 whose Meta entry has no start date. Adjacent bands merge wherever one would hold 1 to 9 people; the cut is never merged away. The second series counts only non-intern entries, so it gives each person's first Meta job that was not an internship; it runs to the cut, and everyone without such a job before the cut is one band." }, "moves": { "edges": [ "2025-01-01", "2025-04-01", "2025-06-01", "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "For the people who stayed: when their latest current Meta entry started. A count of people with a current Meta entry that started on or after an edge gives how many started their newest current role since then, so a person with two current entries is placed by the newer one. Many people change teams inside Meta without adding an entry, so this shows who recorded a new role, a lower bound on who moved." }, "sources": { "ended_from": "2025-01-01", "note": "Where the outside hires (everyone not at Meta when the lab formed) had just been: a job entry that ended in 2025 or later (experience.end_date gte ended_from), which also means it is no longer current. Internships do not count for companies (the intern rule in population.json), so a PhD student's summer at a lab is not where they came from; for academia they do count, because doctoral students' university entries often carry the Intern label. Rows do not overlap: each person counts at the first row in this order whose condition they meet, and the rest are other employers or none. ai_lab marks the five AI labs whose subtotal is published.", "order": [ { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ], "ai_lab": true }, { "id": "google-deepmind", "label": "Google DeepMind", "names": [ "DeepMind" ], "ai_lab": true }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ], "ai_lab": true }, { "id": "xai", "label": "xAI", "names": [ "xAI" ], "ai_lab": true }, { "id": "thinking-machines", "label": "Thinking Machines Lab", "names": [ "Thinking Machines" ], "ai_lab": true }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "scale-ai", "label": "Scale AI", "names": [ "Scale AI" ] }, { "id": "google", "label": "Google, other than Google DeepMind", "names": [ "Google" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] }, { "id": "nvidia", "label": "NVIDIA", "names": [ "NVIDIA" ] }, { "id": "academia", "label": "A university or other educational institution", "company_type": "Educational" } ], "context": [ { "id": "google", "label": "Google, including Google DeepMind", "names": [ "Google", "DeepMind" ] }, { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ] }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ] }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] } ], "context_note": "For the whole group: anyone with a past (not current) non-intern job at the employer, at any time. These rows overlap and have no total. Names match word by word, so Google also matches Google DeepMind and Amazon matches Amazon Web Services (AWS). company.type Educational is the employer type the Platform records for universities and schools." }, "roles": { "functions": [ "Research", "Engineering and Technical", "Product" ], "senior": [ "Senior" ], "manager_up": [ "Manager", "Head", "Director", "Vice President", "President/Vice President", "C-Level", "Partner", "Founder", "Owner" ], "note": "current_function and current_seniority describe the current job and come from the Platform's fixed sets; either can be missing. Senior covers senior, staff, and principal individual contributors (the audit saw Staff, Senior Staff, and Principal titles labelled Senior); manager_up is Manager and every level above it; the rest of those with a stated level are Specialist or Intern. A doctorate is an education entry with education.degree eq Doctorate, finished or in progress.", "baseline_note": "The baseline is Meta's other research staff: a current Meta entry, current_function eq Research, and no lab term in the headline or current title. It includes people who name FAIR only." }, "teams": [ { "id": "fair", "label": "FAIR", "terms": [ "FAIR" ] }, { "id": "tbd-lab", "label": "TBD Lab", "terms": [ "TBD" ] }, { "id": "infra", "label": "MSL Infra and other infrastructure", "terms": [ "infra", "infrastructure" ] }, { "id": "par", "label": "Products and Applied Research", "terms": [ "PAR", "product applied research" ] } ], "teams_note": "Sub-team names in the headline or current title of people in the population, matched word by word; a person can name more than one. Audited: FAIR, 10 profiles naming it read in whole slices, nearly all naming it as the current team. TBD, all 13 matches read: 10 are in TBD Lab or report to it, and the rest name TBD while recruiting for it, while saying they are not in it, or while saying they have left the lab. Infra, the first 15 of 49 matches for infra or infrastructure (not a whole slice): all 15 work on infrastructure inside the lab, 11 of them naming MSL Infra or Infra at MSL. Products and Applied Research: the words applied research mostly match the job title Applied Research Scientist (most of those read) or an old team name, so the row needs PAR or all of product, applied, and research. fair_only counts current Meta profiles that name FAIR and no lab term; it was not audited outside the population.", "places": { "states": [ "California", "New York", "Washington" ], "bay_area": [ "Menlo Park", "San Francisco", "Sunnyvale", "Palo Alto", "Mountain View", "Redwood City", "Burlingame", "Fremont", "San Jose", "Santa Clara", "San Mateo", "Foster City", "Oakland", "Berkeley", "Cupertino", "Los Altos", "Belmont", "San Carlos", "Millbrae", "San Bruno", "Newark", "Milpitas", "Los Gatos", "Campbell", "Saratoga", "Daly City", "South San Francisco", "Emeryville", "Alameda", "Hayward", "Dublin", "Pleasanton", "Walnut Creek", "Atherton", "Portola Valley", "Woodside", "Half Moon Bay" ], "countries": [ "United Kingdom" ], "note": "The profile's own location, where people list themselves: location.country and location.state, and location.city for the Bay Area, whose cities are listed one by one and compared exactly." }, "postings": { "company": "Meta", "title_terms": [ "superintelligence", "MSL" ], "description_terms": [ "superintelligence labs" ], "research_title": "research", "cities": [ "Menlo Park", "San Francisco" ], "states": [ "New York" ], "experience_max_months": 36, "posted_from": "2026-09-01", "note": "Open Meta postings (is_open eq true) whose title names superintelligence or MSL, or whose description contains the words superintelligence and labs. All 30 read on 2026-09-22 are Meta postings whose description names Meta Superintelligence Labs. Every one carries the seniority label Not Applicable, so seniority says nothing here, and all were posted in September 2026, so the index shows the openings of the moment rather than a history. Counts of postings carry no minimum." }}
05
外部加入者中 50.5% 做研究,已在 Meta 的人是 30.6%
当前
研究:已在 Meta 30.6%,外部 50.5%;工程与技术:已在 Meta 42.2%,外部 28.5%;产品:已在 Meta 6.8%,外部 5.1%;其他职能:已在 Meta 9.6%,外部 8.4%;未写明:已在 Meta 10.8%,外部 7.5%;写有博士学历:已在 Meta 29.6%,外部 37.9%
图中所见
已在 Meta 的人中最大的职能是工程与技术(42.2%),外部加入者中是研究。外部加入者写有博士学历的比例是 37.9%,已在 Meta 的人是 29.6%。
方法与局限
职能是 Metix AI Platform 对当前工作的固定分类。其他职能指写明的其余职能;94 人没有写明。
来源:Metix AI Platform 个人档案数据,2026-09-22。
查询population.json · measures.json
{ "note": "Who is counted. A person counts when one job entry is at Meta and current (experience.company.name match current_employer and experience.is_current eq true, in one has_experience entry) and the profile's headline or current_title names the lab with one of lab_terms. The Platform matches text word by word, in any order, and ignores case, so MSL also matches msl and superintelligence also matches SuperIntelligence. Counts are profiles visible through the Metix AI Platform, never the lab's headcount; stale profiles count as current, so a count is not a guaranteed floor either.", "current_employer": "Meta", "current_employer_note": "match Meta on the current entry. The name also matches entries written as Facebook: a current entry named Facebook counts, and a Facebook condition returned all 790 profiles of the narrow definition, so the two names are one employer on the Platform and a Facebook condition is no separate test. company.name eq Meta returned the same 790 profiles as match Meta, and every one of the 63 profiles read in the audit has a current entry at Meta itself.", "lab_terms": [ "superintelligence", "MSL" ], "lab_fields": [ "headline", "current_title" ], "lab_terms_note": "superintelligence alone (the narrow definition) gives 790 profiles. MSL, the lab's short name, adds 146 current Meta profiles that never write superintelligence; 13 of 14 read in a whole slice use it for the lab, and the rest recruit for it. FAIR, one of the lab's groups since 2025, is not a lab term: people who name only FAIR do not name the lab, and teams.json counts them as context (fair_only).", "narrow_terms": [ "superintelligence" ], "history_names": [ "Meta", "Facebook", "Instagram", "WhatsApp", "Oculus" ], "history_names_note": "Names that count as an earlier job at Meta, matched word by word in one has_experience entry. The name Meta does not match an entry listed under Instagram; adding the other names moves fewer than 10 people.", "cut": "2025-06-01", "cut_note": "Meta announced Meta Superintelligence Labs at the end of June 2025. A person with a job entry at a history name that started before the cut had a Meta job before the lab. experience.start_date is a month (YYYY-MM) or a year; the Platform compares it as its first day, so a year alone reads as January. A newcomer whose Meta entry says only 2025 therefore counts as at Meta before the cut, which raises the share at Meta when the lab formed, and an earlier entry whose end date says only 2025 counts as ending before May 2025, which can move someone who was at Meta into returned.", "stay_end": "2025-05-01", "cohorts_note": "Four groups that do not overlap and add up to the whole. Stayed: a non-intern Meta entry that started before the cut and is current or ended in May 2025 or later, so the person was at Meta when the lab formed. Returned: a non-intern Meta entry before the cut, but none that lasted into May 2025, so they had left and came back. Former interns: the only Meta entries before the cut are internships. New to Meta: no Meta entry that started before the cut, including fewer than 10 whose current Meta entry has no start date. Returned, former interns, and new to Meta together are the outside hires, everyone who was not at Meta when the lab formed.", "intern_rule": "An entry is an internship when experience.seniority eq Intern or experience.title matches intern. Both are tested inside the same has_experience entry as the employer and the date.", "labeling_terms": [ "labeling", "labelling", "annotation", "annotator", "red teamer", "red teaming" ], "labeling_note": "Titles and headlines that name data labeling, annotation, or red teaming. The audit found such roles among recent hires (fewer than 10 in the slice read); vendors often staff them, but the profile lists Meta.", "freshness_note": "Profiles are a periodically refreshed snapshot. Across all Meta job entries on the Platform, 3,988 start in 2026, 1,104 of them in March and April and fewer than 10 in May or later, so start dates stop in April 2026 and the most recent months are probably undercounted. April 2026 is the last month shown, and people who joined since are missing.", "audit": "63 profiles read in whole slices, never from the top of a search, because Search ranks by match quality. The slices covered people with no Meta-named entry before the cut, people with a Meta entry before the cut, people who write MSL but not superintelligence, and the profiles whose Meta entry has no start date (fewer than 10). 62 of 63 describe themselves as working in the lab, and the rest recruit for it. All 63 have a current Meta entry, almost all of them named Meta. All 31 read with a Meta entry before the cut had a real Meta job there, not only an internship. Among people without a Meta-named entry before the cut, an earlier Meta job turned up listed under Instagram, which is why Instagram is a history name, and fewer than 10 of them hold data labeling or red teaming roles. Separate reads of sub-team matches found fewer than 10 profiles that say they have left the lab while the Meta entry is still current, so a few members are out of date. Records read for the audit are kept private.", "comparison": { "id": "microsoft", "label": "Microsoft", "current_employer": "Microsoft", "lab_terms": [ "superintelligence" ], "history_names": [ "Microsoft" ], "cut": "2025-11-01", "stay_end": "2025-10-01", "edges": [ "2012-01-01", "2016-01-01", "2020-01-01", "2023-01-01", "2025-01-01" ], "note": "Current Microsoft staff whose headline or current_title names superintelligence. Microsoft AI announced its superintelligence team in November 2025, so the cut for this group is 2025-11-01. Microsoft also matches Microsoft AI and Microsoft Research; subsidiaries with their own names (LinkedIn, GitHub) are not history names. A whole slice of 15 all named the Microsoft AI superintelligence team; fewer than 10 of them are recruiters or sourcers for it." }}
{ "note": "What is counted, all within the population in queries/population.json unless a block says otherwise. Every count is sent with size 1, so it costs 1 API Credit, or nothing when it finds no one, and reads no record.", "first_joined": { "edges": [ "2012-01-01", "2014-01-01", "2016-01-01", "2018-01-01", "2020-01-01", "2022-01-01", "2023-01-01", "2024-01-01", "2025-01-01" ], "after_cut_edges": [ "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "A person's first Meta job started before a date exactly when they have an entry at a history name that started before it, so a count at each edge gives how many first joined before it, and the difference between two edges is a band of first-join dates. Bands run from the start of the record through the cut (the dates in edges) and on month by month and quarter by quarter to April 2026 (after_cut_edges). The last band holds April 2026 and anything later, and the fewer than 10 whose Meta entry has no start date. Adjacent bands merge wherever one would hold 1 to 9 people; the cut is never merged away. The second series counts only non-intern entries, so it gives each person's first Meta job that was not an internship; it runs to the cut, and everyone without such a job before the cut is one band." }, "moves": { "edges": [ "2025-01-01", "2025-04-01", "2025-06-01", "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "For the people who stayed: when their latest current Meta entry started. A count of people with a current Meta entry that started on or after an edge gives how many started their newest current role since then, so a person with two current entries is placed by the newer one. Many people change teams inside Meta without adding an entry, so this shows who recorded a new role, a lower bound on who moved." }, "sources": { "ended_from": "2025-01-01", "note": "Where the outside hires (everyone not at Meta when the lab formed) had just been: a job entry that ended in 2025 or later (experience.end_date gte ended_from), which also means it is no longer current. Internships do not count for companies (the intern rule in population.json), so a PhD student's summer at a lab is not where they came from; for academia they do count, because doctoral students' university entries often carry the Intern label. Rows do not overlap: each person counts at the first row in this order whose condition they meet, and the rest are other employers or none. ai_lab marks the five AI labs whose subtotal is published.", "order": [ { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ], "ai_lab": true }, { "id": "google-deepmind", "label": "Google DeepMind", "names": [ "DeepMind" ], "ai_lab": true }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ], "ai_lab": true }, { "id": "xai", "label": "xAI", "names": [ "xAI" ], "ai_lab": true }, { "id": "thinking-machines", "label": "Thinking Machines Lab", "names": [ "Thinking Machines" ], "ai_lab": true }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "scale-ai", "label": "Scale AI", "names": [ "Scale AI" ] }, { "id": "google", "label": "Google, other than Google DeepMind", "names": [ "Google" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] }, { "id": "nvidia", "label": "NVIDIA", "names": [ "NVIDIA" ] }, { "id": "academia", "label": "A university or other educational institution", "company_type": "Educational" } ], "context": [ { "id": "google", "label": "Google, including Google DeepMind", "names": [ "Google", "DeepMind" ] }, { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ] }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ] }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] } ], "context_note": "For the whole group: anyone with a past (not current) non-intern job at the employer, at any time. These rows overlap and have no total. Names match word by word, so Google also matches Google DeepMind and Amazon matches Amazon Web Services (AWS). company.type Educational is the employer type the Platform records for universities and schools." }, "roles": { "functions": [ "Research", "Engineering and Technical", "Product" ], "senior": [ "Senior" ], "manager_up": [ "Manager", "Head", "Director", "Vice President", "President/Vice President", "C-Level", "Partner", "Founder", "Owner" ], "note": "current_function and current_seniority describe the current job and come from the Platform's fixed sets; either can be missing. Senior covers senior, staff, and principal individual contributors (the audit saw Staff, Senior Staff, and Principal titles labelled Senior); manager_up is Manager and every level above it; the rest of those with a stated level are Specialist or Intern. A doctorate is an education entry with education.degree eq Doctorate, finished or in progress.", "baseline_note": "The baseline is Meta's other research staff: a current Meta entry, current_function eq Research, and no lab term in the headline or current title. It includes people who name FAIR only." }, "teams": [ { "id": "fair", "label": "FAIR", "terms": [ "FAIR" ] }, { "id": "tbd-lab", "label": "TBD Lab", "terms": [ "TBD" ] }, { "id": "infra", "label": "MSL Infra and other infrastructure", "terms": [ "infra", "infrastructure" ] }, { "id": "par", "label": "Products and Applied Research", "terms": [ "PAR", "product applied research" ] } ], "teams_note": "Sub-team names in the headline or current title of people in the population, matched word by word; a person can name more than one. Audited: FAIR, 10 profiles naming it read in whole slices, nearly all naming it as the current team. TBD, all 13 matches read: 10 are in TBD Lab or report to it, and the rest name TBD while recruiting for it, while saying they are not in it, or while saying they have left the lab. Infra, the first 15 of 49 matches for infra or infrastructure (not a whole slice): all 15 work on infrastructure inside the lab, 11 of them naming MSL Infra or Infra at MSL. Products and Applied Research: the words applied research mostly match the job title Applied Research Scientist (most of those read) or an old team name, so the row needs PAR or all of product, applied, and research. fair_only counts current Meta profiles that name FAIR and no lab term; it was not audited outside the population.", "places": { "states": [ "California", "New York", "Washington" ], "bay_area": [ "Menlo Park", "San Francisco", "Sunnyvale", "Palo Alto", "Mountain View", "Redwood City", "Burlingame", "Fremont", "San Jose", "Santa Clara", "San Mateo", "Foster City", "Oakland", "Berkeley", "Cupertino", "Los Altos", "Belmont", "San Carlos", "Millbrae", "San Bruno", "Newark", "Milpitas", "Los Gatos", "Campbell", "Saratoga", "Daly City", "South San Francisco", "Emeryville", "Alameda", "Hayward", "Dublin", "Pleasanton", "Walnut Creek", "Atherton", "Portola Valley", "Woodside", "Half Moon Bay" ], "countries": [ "United Kingdom" ], "note": "The profile's own location, where people list themselves: location.country and location.state, and location.city for the Bay Area, whose cities are listed one by one and compared exactly." }, "postings": { "company": "Meta", "title_terms": [ "superintelligence", "MSL" ], "description_terms": [ "superintelligence labs" ], "research_title": "research", "cities": [ "Menlo Park", "San Francisco" ], "states": [ "New York" ], "experience_max_months": 36, "posted_from": "2026-09-01", "note": "Open Meta postings (is_open eq true) whose title names superintelligence or MSL, or whose description contains the words superintelligence and labs. All 30 read on 2026-09-22 are Meta postings whose description names Meta Superintelligence Labs. Every one carries the seniority label Not Applicable, so seniority says nothing here, and all were posted in September 2026, so the index shows the openings of the moment rather than a history. Counts of postings carry no minimum." }}
实验室现在的样子
第 3 部分,图 06、07、08、09
研究
06
实验室研究人员中 67.5% 写有博士学历,Meta 其他研究人员是 41.0%
当前
实验室研究人员 67.5%(329 人);Meta 其他研究人员 41.0%(8,955 人)
- 实验室的研究人员329 人222 · 67.5%
- Meta 其他研究人员8,955 人3,670 · 41.0%
图中所见
实验室的研究人员也更常标为 Senior(15.8%,其他研究人员是 10.8%);经理及以上的差别在偶然误差范围内(6.7% 对 9.0%)。
方法与局限
对照组是当前在 Meta、职能为研究、标题和职位都没有写实验室的人:8,955 个档案,包括只写 FAIR 的人,而 FAIR 已并入实验室。Senior 包括 senior、staff 和 principal 级别。
来源:Metix AI Platform 个人档案数据,2026-09-22。
查询population.json · measures.json
{ "note": "Who is counted. A person counts when one job entry is at Meta and current (experience.company.name match current_employer and experience.is_current eq true, in one has_experience entry) and the profile's headline or current_title names the lab with one of lab_terms. The Platform matches text word by word, in any order, and ignores case, so MSL also matches msl and superintelligence also matches SuperIntelligence. Counts are profiles visible through the Metix AI Platform, never the lab's headcount; stale profiles count as current, so a count is not a guaranteed floor either.", "current_employer": "Meta", "current_employer_note": "match Meta on the current entry. The name also matches entries written as Facebook: a current entry named Facebook counts, and a Facebook condition returned all 790 profiles of the narrow definition, so the two names are one employer on the Platform and a Facebook condition is no separate test. company.name eq Meta returned the same 790 profiles as match Meta, and every one of the 63 profiles read in the audit has a current entry at Meta itself.", "lab_terms": [ "superintelligence", "MSL" ], "lab_fields": [ "headline", "current_title" ], "lab_terms_note": "superintelligence alone (the narrow definition) gives 790 profiles. MSL, the lab's short name, adds 146 current Meta profiles that never write superintelligence; 13 of 14 read in a whole slice use it for the lab, and the rest recruit for it. FAIR, one of the lab's groups since 2025, is not a lab term: people who name only FAIR do not name the lab, and teams.json counts them as context (fair_only).", "narrow_terms": [ "superintelligence" ], "history_names": [ "Meta", "Facebook", "Instagram", "WhatsApp", "Oculus" ], "history_names_note": "Names that count as an earlier job at Meta, matched word by word in one has_experience entry. The name Meta does not match an entry listed under Instagram; adding the other names moves fewer than 10 people.", "cut": "2025-06-01", "cut_note": "Meta announced Meta Superintelligence Labs at the end of June 2025. A person with a job entry at a history name that started before the cut had a Meta job before the lab. experience.start_date is a month (YYYY-MM) or a year; the Platform compares it as its first day, so a year alone reads as January. A newcomer whose Meta entry says only 2025 therefore counts as at Meta before the cut, which raises the share at Meta when the lab formed, and an earlier entry whose end date says only 2025 counts as ending before May 2025, which can move someone who was at Meta into returned.", "stay_end": "2025-05-01", "cohorts_note": "Four groups that do not overlap and add up to the whole. Stayed: a non-intern Meta entry that started before the cut and is current or ended in May 2025 or later, so the person was at Meta when the lab formed. Returned: a non-intern Meta entry before the cut, but none that lasted into May 2025, so they had left and came back. Former interns: the only Meta entries before the cut are internships. New to Meta: no Meta entry that started before the cut, including fewer than 10 whose current Meta entry has no start date. Returned, former interns, and new to Meta together are the outside hires, everyone who was not at Meta when the lab formed.", "intern_rule": "An entry is an internship when experience.seniority eq Intern or experience.title matches intern. Both are tested inside the same has_experience entry as the employer and the date.", "labeling_terms": [ "labeling", "labelling", "annotation", "annotator", "red teamer", "red teaming" ], "labeling_note": "Titles and headlines that name data labeling, annotation, or red teaming. The audit found such roles among recent hires (fewer than 10 in the slice read); vendors often staff them, but the profile lists Meta.", "freshness_note": "Profiles are a periodically refreshed snapshot. Across all Meta job entries on the Platform, 3,988 start in 2026, 1,104 of them in March and April and fewer than 10 in May or later, so start dates stop in April 2026 and the most recent months are probably undercounted. April 2026 is the last month shown, and people who joined since are missing.", "audit": "63 profiles read in whole slices, never from the top of a search, because Search ranks by match quality. The slices covered people with no Meta-named entry before the cut, people with a Meta entry before the cut, people who write MSL but not superintelligence, and the profiles whose Meta entry has no start date (fewer than 10). 62 of 63 describe themselves as working in the lab, and the rest recruit for it. All 63 have a current Meta entry, almost all of them named Meta. All 31 read with a Meta entry before the cut had a real Meta job there, not only an internship. Among people without a Meta-named entry before the cut, an earlier Meta job turned up listed under Instagram, which is why Instagram is a history name, and fewer than 10 of them hold data labeling or red teaming roles. Separate reads of sub-team matches found fewer than 10 profiles that say they have left the lab while the Meta entry is still current, so a few members are out of date. Records read for the audit are kept private.", "comparison": { "id": "microsoft", "label": "Microsoft", "current_employer": "Microsoft", "lab_terms": [ "superintelligence" ], "history_names": [ "Microsoft" ], "cut": "2025-11-01", "stay_end": "2025-10-01", "edges": [ "2012-01-01", "2016-01-01", "2020-01-01", "2023-01-01", "2025-01-01" ], "note": "Current Microsoft staff whose headline or current_title names superintelligence. Microsoft AI announced its superintelligence team in November 2025, so the cut for this group is 2025-11-01. Microsoft also matches Microsoft AI and Microsoft Research; subsidiaries with their own names (LinkedIn, GitHub) are not history names. A whole slice of 15 all named the Microsoft AI superintelligence team; fewer than 10 of them are recruiters or sourcers for it." }}
{ "note": "What is counted, all within the population in queries/population.json unless a block says otherwise. Every count is sent with size 1, so it costs 1 API Credit, or nothing when it finds no one, and reads no record.", "first_joined": { "edges": [ "2012-01-01", "2014-01-01", "2016-01-01", "2018-01-01", "2020-01-01", "2022-01-01", "2023-01-01", "2024-01-01", "2025-01-01" ], "after_cut_edges": [ "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "A person's first Meta job started before a date exactly when they have an entry at a history name that started before it, so a count at each edge gives how many first joined before it, and the difference between two edges is a band of first-join dates. Bands run from the start of the record through the cut (the dates in edges) and on month by month and quarter by quarter to April 2026 (after_cut_edges). The last band holds April 2026 and anything later, and the fewer than 10 whose Meta entry has no start date. Adjacent bands merge wherever one would hold 1 to 9 people; the cut is never merged away. The second series counts only non-intern entries, so it gives each person's first Meta job that was not an internship; it runs to the cut, and everyone without such a job before the cut is one band." }, "moves": { "edges": [ "2025-01-01", "2025-04-01", "2025-06-01", "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "For the people who stayed: when their latest current Meta entry started. A count of people with a current Meta entry that started on or after an edge gives how many started their newest current role since then, so a person with two current entries is placed by the newer one. Many people change teams inside Meta without adding an entry, so this shows who recorded a new role, a lower bound on who moved." }, "sources": { "ended_from": "2025-01-01", "note": "Where the outside hires (everyone not at Meta when the lab formed) had just been: a job entry that ended in 2025 or later (experience.end_date gte ended_from), which also means it is no longer current. Internships do not count for companies (the intern rule in population.json), so a PhD student's summer at a lab is not where they came from; for academia they do count, because doctoral students' university entries often carry the Intern label. Rows do not overlap: each person counts at the first row in this order whose condition they meet, and the rest are other employers or none. ai_lab marks the five AI labs whose subtotal is published.", "order": [ { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ], "ai_lab": true }, { "id": "google-deepmind", "label": "Google DeepMind", "names": [ "DeepMind" ], "ai_lab": true }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ], "ai_lab": true }, { "id": "xai", "label": "xAI", "names": [ "xAI" ], "ai_lab": true }, { "id": "thinking-machines", "label": "Thinking Machines Lab", "names": [ "Thinking Machines" ], "ai_lab": true }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "scale-ai", "label": "Scale AI", "names": [ "Scale AI" ] }, { "id": "google", "label": "Google, other than Google DeepMind", "names": [ "Google" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] }, { "id": "nvidia", "label": "NVIDIA", "names": [ "NVIDIA" ] }, { "id": "academia", "label": "A university or other educational institution", "company_type": "Educational" } ], "context": [ { "id": "google", "label": "Google, including Google DeepMind", "names": [ "Google", "DeepMind" ] }, { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ] }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ] }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] } ], "context_note": "For the whole group: anyone with a past (not current) non-intern job at the employer, at any time. These rows overlap and have no total. Names match word by word, so Google also matches Google DeepMind and Amazon matches Amazon Web Services (AWS). company.type Educational is the employer type the Platform records for universities and schools." }, "roles": { "functions": [ "Research", "Engineering and Technical", "Product" ], "senior": [ "Senior" ], "manager_up": [ "Manager", "Head", "Director", "Vice President", "President/Vice President", "C-Level", "Partner", "Founder", "Owner" ], "note": "current_function and current_seniority describe the current job and come from the Platform's fixed sets; either can be missing. Senior covers senior, staff, and principal individual contributors (the audit saw Staff, Senior Staff, and Principal titles labelled Senior); manager_up is Manager and every level above it; the rest of those with a stated level are Specialist or Intern. A doctorate is an education entry with education.degree eq Doctorate, finished or in progress.", "baseline_note": "The baseline is Meta's other research staff: a current Meta entry, current_function eq Research, and no lab term in the headline or current title. It includes people who name FAIR only." }, "teams": [ { "id": "fair", "label": "FAIR", "terms": [ "FAIR" ] }, { "id": "tbd-lab", "label": "TBD Lab", "terms": [ "TBD" ] }, { "id": "infra", "label": "MSL Infra and other infrastructure", "terms": [ "infra", "infrastructure" ] }, { "id": "par", "label": "Products and Applied Research", "terms": [ "PAR", "product applied research" ] } ], "teams_note": "Sub-team names in the headline or current title of people in the population, matched word by word; a person can name more than one. Audited: FAIR, 10 profiles naming it read in whole slices, nearly all naming it as the current team. TBD, all 13 matches read: 10 are in TBD Lab or report to it, and the rest name TBD while recruiting for it, while saying they are not in it, or while saying they have left the lab. Infra, the first 15 of 49 matches for infra or infrastructure (not a whole slice): all 15 work on infrastructure inside the lab, 11 of them naming MSL Infra or Infra at MSL. Products and Applied Research: the words applied research mostly match the job title Applied Research Scientist (most of those read) or an old team name, so the row needs PAR or all of product, applied, and research. fair_only counts current Meta profiles that name FAIR and no lab term; it was not audited outside the population.", "places": { "states": [ "California", "New York", "Washington" ], "bay_area": [ "Menlo Park", "San Francisco", "Sunnyvale", "Palo Alto", "Mountain View", "Redwood City", "Burlingame", "Fremont", "San Jose", "Santa Clara", "San Mateo", "Foster City", "Oakland", "Berkeley", "Cupertino", "Los Altos", "Belmont", "San Carlos", "Millbrae", "San Bruno", "Newark", "Milpitas", "Los Gatos", "Campbell", "Saratoga", "Daly City", "South San Francisco", "Emeryville", "Alameda", "Hayward", "Dublin", "Pleasanton", "Walnut Creek", "Atherton", "Portola Valley", "Woodside", "Half Moon Bay" ], "countries": [ "United Kingdom" ], "note": "The profile's own location, where people list themselves: location.country and location.state, and location.city for the Bay Area, whose cities are listed one by one and compared exactly." }, "postings": { "company": "Meta", "title_terms": [ "superintelligence", "MSL" ], "description_terms": [ "superintelligence labs" ], "research_title": "research", "cities": [ "Menlo Park", "San Francisco" ], "states": [ "New York" ], "experience_max_months": 36, "posted_from": "2026-09-01", "note": "Open Meta postings (is_open eq true) whose title names superintelligence or MSL, or whose description contains the words superintelligence and labs. All 30 read on 2026-09-22 are Meta postings whose description names Meta Superintelligence Labs. Every one carries the seniority label Not Applicable, so seniority says nothing here, and all were posted in September 2026, so the index shows the openings of the moment rather than a history. Counts of postings carry no minimum." }}
07
不到六分之一的人写明实验室四个团队中的任何一个;写得最多的是 FAIR,占 6.7%
标题或职位里写明的团队。
FAIR 63,MSL Infra 及其他基础设施 49,TBD Lab 13,Products and Applied Research <10
- FAIR63 · 6.7%
- MSL Infra 及其他基础设施49 · 5.2%
- TBD Lab13 · 1.4%
- Products and Applied Research<10
图中所见
最多 134 人写明了其中一个团队,所以至少 85% 的人一个都没写。另有 238 个当前 Meta 档案写了 FAIR 但没写实验室,这些人不在本次统计里。
方法与局限
检索了四个团队:FAIR、TBD Lab、基础设施和 Products and Applied Research。FAIR 和 TBD 也是普通单词,所以匹配结果逐条读过:13 个 TBD 匹配里有 10 个在 TBD Lab。applied research 大多匹配的是 Applied Research Scientist 这个职位,所以 Products and Applied Research 只数写 PAR 或写全这几个词的人。
来源:Metix AI Platform 个人档案数据,2026-09-22。
查询population.json · measures.json
{ "note": "Who is counted. A person counts when one job entry is at Meta and current (experience.company.name match current_employer and experience.is_current eq true, in one has_experience entry) and the profile's headline or current_title names the lab with one of lab_terms. The Platform matches text word by word, in any order, and ignores case, so MSL also matches msl and superintelligence also matches SuperIntelligence. Counts are profiles visible through the Metix AI Platform, never the lab's headcount; stale profiles count as current, so a count is not a guaranteed floor either.", "current_employer": "Meta", "current_employer_note": "match Meta on the current entry. The name also matches entries written as Facebook: a current entry named Facebook counts, and a Facebook condition returned all 790 profiles of the narrow definition, so the two names are one employer on the Platform and a Facebook condition is no separate test. company.name eq Meta returned the same 790 profiles as match Meta, and every one of the 63 profiles read in the audit has a current entry at Meta itself.", "lab_terms": [ "superintelligence", "MSL" ], "lab_fields": [ "headline", "current_title" ], "lab_terms_note": "superintelligence alone (the narrow definition) gives 790 profiles. MSL, the lab's short name, adds 146 current Meta profiles that never write superintelligence; 13 of 14 read in a whole slice use it for the lab, and the rest recruit for it. FAIR, one of the lab's groups since 2025, is not a lab term: people who name only FAIR do not name the lab, and teams.json counts them as context (fair_only).", "narrow_terms": [ "superintelligence" ], "history_names": [ "Meta", "Facebook", "Instagram", "WhatsApp", "Oculus" ], "history_names_note": "Names that count as an earlier job at Meta, matched word by word in one has_experience entry. The name Meta does not match an entry listed under Instagram; adding the other names moves fewer than 10 people.", "cut": "2025-06-01", "cut_note": "Meta announced Meta Superintelligence Labs at the end of June 2025. A person with a job entry at a history name that started before the cut had a Meta job before the lab. experience.start_date is a month (YYYY-MM) or a year; the Platform compares it as its first day, so a year alone reads as January. A newcomer whose Meta entry says only 2025 therefore counts as at Meta before the cut, which raises the share at Meta when the lab formed, and an earlier entry whose end date says only 2025 counts as ending before May 2025, which can move someone who was at Meta into returned.", "stay_end": "2025-05-01", "cohorts_note": "Four groups that do not overlap and add up to the whole. Stayed: a non-intern Meta entry that started before the cut and is current or ended in May 2025 or later, so the person was at Meta when the lab formed. Returned: a non-intern Meta entry before the cut, but none that lasted into May 2025, so they had left and came back. Former interns: the only Meta entries before the cut are internships. New to Meta: no Meta entry that started before the cut, including fewer than 10 whose current Meta entry has no start date. Returned, former interns, and new to Meta together are the outside hires, everyone who was not at Meta when the lab formed.", "intern_rule": "An entry is an internship when experience.seniority eq Intern or experience.title matches intern. Both are tested inside the same has_experience entry as the employer and the date.", "labeling_terms": [ "labeling", "labelling", "annotation", "annotator", "red teamer", "red teaming" ], "labeling_note": "Titles and headlines that name data labeling, annotation, or red teaming. The audit found such roles among recent hires (fewer than 10 in the slice read); vendors often staff them, but the profile lists Meta.", "freshness_note": "Profiles are a periodically refreshed snapshot. Across all Meta job entries on the Platform, 3,988 start in 2026, 1,104 of them in March and April and fewer than 10 in May or later, so start dates stop in April 2026 and the most recent months are probably undercounted. April 2026 is the last month shown, and people who joined since are missing.", "audit": "63 profiles read in whole slices, never from the top of a search, because Search ranks by match quality. The slices covered people with no Meta-named entry before the cut, people with a Meta entry before the cut, people who write MSL but not superintelligence, and the profiles whose Meta entry has no start date (fewer than 10). 62 of 63 describe themselves as working in the lab, and the rest recruit for it. All 63 have a current Meta entry, almost all of them named Meta. All 31 read with a Meta entry before the cut had a real Meta job there, not only an internship. Among people without a Meta-named entry before the cut, an earlier Meta job turned up listed under Instagram, which is why Instagram is a history name, and fewer than 10 of them hold data labeling or red teaming roles. Separate reads of sub-team matches found fewer than 10 profiles that say they have left the lab while the Meta entry is still current, so a few members are out of date. Records read for the audit are kept private.", "comparison": { "id": "microsoft", "label": "Microsoft", "current_employer": "Microsoft", "lab_terms": [ "superintelligence" ], "history_names": [ "Microsoft" ], "cut": "2025-11-01", "stay_end": "2025-10-01", "edges": [ "2012-01-01", "2016-01-01", "2020-01-01", "2023-01-01", "2025-01-01" ], "note": "Current Microsoft staff whose headline or current_title names superintelligence. Microsoft AI announced its superintelligence team in November 2025, so the cut for this group is 2025-11-01. Microsoft also matches Microsoft AI and Microsoft Research; subsidiaries with their own names (LinkedIn, GitHub) are not history names. A whole slice of 15 all named the Microsoft AI superintelligence team; fewer than 10 of them are recruiters or sourcers for it." }}
{ "note": "What is counted, all within the population in queries/population.json unless a block says otherwise. Every count is sent with size 1, so it costs 1 API Credit, or nothing when it finds no one, and reads no record.", "first_joined": { "edges": [ "2012-01-01", "2014-01-01", "2016-01-01", "2018-01-01", "2020-01-01", "2022-01-01", "2023-01-01", "2024-01-01", "2025-01-01" ], "after_cut_edges": [ "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "A person's first Meta job started before a date exactly when they have an entry at a history name that started before it, so a count at each edge gives how many first joined before it, and the difference between two edges is a band of first-join dates. Bands run from the start of the record through the cut (the dates in edges) and on month by month and quarter by quarter to April 2026 (after_cut_edges). The last band holds April 2026 and anything later, and the fewer than 10 whose Meta entry has no start date. Adjacent bands merge wherever one would hold 1 to 9 people; the cut is never merged away. The second series counts only non-intern entries, so it gives each person's first Meta job that was not an internship; it runs to the cut, and everyone without such a job before the cut is one band." }, "moves": { "edges": [ "2025-01-01", "2025-04-01", "2025-06-01", "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "For the people who stayed: when their latest current Meta entry started. A count of people with a current Meta entry that started on or after an edge gives how many started their newest current role since then, so a person with two current entries is placed by the newer one. Many people change teams inside Meta without adding an entry, so this shows who recorded a new role, a lower bound on who moved." }, "sources": { "ended_from": "2025-01-01", "note": "Where the outside hires (everyone not at Meta when the lab formed) had just been: a job entry that ended in 2025 or later (experience.end_date gte ended_from), which also means it is no longer current. Internships do not count for companies (the intern rule in population.json), so a PhD student's summer at a lab is not where they came from; for academia they do count, because doctoral students' university entries often carry the Intern label. Rows do not overlap: each person counts at the first row in this order whose condition they meet, and the rest are other employers or none. ai_lab marks the five AI labs whose subtotal is published.", "order": [ { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ], "ai_lab": true }, { "id": "google-deepmind", "label": "Google DeepMind", "names": [ "DeepMind" ], "ai_lab": true }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ], "ai_lab": true }, { "id": "xai", "label": "xAI", "names": [ "xAI" ], "ai_lab": true }, { "id": "thinking-machines", "label": "Thinking Machines Lab", "names": [ "Thinking Machines" ], "ai_lab": true }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "scale-ai", "label": "Scale AI", "names": [ "Scale AI" ] }, { "id": "google", "label": "Google, other than Google DeepMind", "names": [ "Google" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] }, { "id": "nvidia", "label": "NVIDIA", "names": [ "NVIDIA" ] }, { "id": "academia", "label": "A university or other educational institution", "company_type": "Educational" } ], "context": [ { "id": "google", "label": "Google, including Google DeepMind", "names": [ "Google", "DeepMind" ] }, { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ] }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ] }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] } ], "context_note": "For the whole group: anyone with a past (not current) non-intern job at the employer, at any time. These rows overlap and have no total. Names match word by word, so Google also matches Google DeepMind and Amazon matches Amazon Web Services (AWS). company.type Educational is the employer type the Platform records for universities and schools." }, "roles": { "functions": [ "Research", "Engineering and Technical", "Product" ], "senior": [ "Senior" ], "manager_up": [ "Manager", "Head", "Director", "Vice President", "President/Vice President", "C-Level", "Partner", "Founder", "Owner" ], "note": "current_function and current_seniority describe the current job and come from the Platform's fixed sets; either can be missing. Senior covers senior, staff, and principal individual contributors (the audit saw Staff, Senior Staff, and Principal titles labelled Senior); manager_up is Manager and every level above it; the rest of those with a stated level are Specialist or Intern. A doctorate is an education entry with education.degree eq Doctorate, finished or in progress.", "baseline_note": "The baseline is Meta's other research staff: a current Meta entry, current_function eq Research, and no lab term in the headline or current title. It includes people who name FAIR only." }, "teams": [ { "id": "fair", "label": "FAIR", "terms": [ "FAIR" ] }, { "id": "tbd-lab", "label": "TBD Lab", "terms": [ "TBD" ] }, { "id": "infra", "label": "MSL Infra and other infrastructure", "terms": [ "infra", "infrastructure" ] }, { "id": "par", "label": "Products and Applied Research", "terms": [ "PAR", "product applied research" ] } ], "teams_note": "Sub-team names in the headline or current title of people in the population, matched word by word; a person can name more than one. Audited: FAIR, 10 profiles naming it read in whole slices, nearly all naming it as the current team. TBD, all 13 matches read: 10 are in TBD Lab or report to it, and the rest name TBD while recruiting for it, while saying they are not in it, or while saying they have left the lab. Infra, the first 15 of 49 matches for infra or infrastructure (not a whole slice): all 15 work on infrastructure inside the lab, 11 of them naming MSL Infra or Infra at MSL. Products and Applied Research: the words applied research mostly match the job title Applied Research Scientist (most of those read) or an old team name, so the row needs PAR or all of product, applied, and research. fair_only counts current Meta profiles that name FAIR and no lab term; it was not audited outside the population.", "places": { "states": [ "California", "New York", "Washington" ], "bay_area": [ "Menlo Park", "San Francisco", "Sunnyvale", "Palo Alto", "Mountain View", "Redwood City", "Burlingame", "Fremont", "San Jose", "Santa Clara", "San Mateo", "Foster City", "Oakland", "Berkeley", "Cupertino", "Los Altos", "Belmont", "San Carlos", "Millbrae", "San Bruno", "Newark", "Milpitas", "Los Gatos", "Campbell", "Saratoga", "Daly City", "South San Francisco", "Emeryville", "Alameda", "Hayward", "Dublin", "Pleasanton", "Walnut Creek", "Atherton", "Portola Valley", "Woodside", "Half Moon Bay" ], "countries": [ "United Kingdom" ], "note": "The profile's own location, where people list themselves: location.country and location.state, and location.city for the Bay Area, whose cities are listed one by one and compared exactly." }, "postings": { "company": "Meta", "title_terms": [ "superintelligence", "MSL" ], "description_terms": [ "superintelligence labs" ], "research_title": "research", "cities": [ "Menlo Park", "San Francisco" ], "states": [ "New York" ], "experience_max_months": 36, "posted_from": "2026-09-01", "note": "Open Meta postings (is_open eq true) whose title names superintelligence or MSL, or whose description contains the words superintelligence and labs. All 30 read on 2026-09-22 are Meta postings whose description names Meta Superintelligence Labs. Every one carries the seniority label Not Applicable, so seniority says nothing here, and all were posted in September 2026, so the index shows the openings of the moment rather than a history. Counts of postings carry no minimum." }}
08
48.4% 的人写的所在地是旧金山湾区,94.1% 是美国
个人档案上写的
旧金山湾区 453,纽约州 118,华盛顿州 84,加州其他地区 27,美国其他地区,或未写州 199,英国 19,其他国家,或未写国家 36
- 旧金山湾区453 · 48.4%
- 纽约州118 · 12.6%
- 华盛顿州84 · 9.0%
- 加州其他地区27 · 2.9%
- 美国其他地区,或未写州199 · 21.3%
- 英国19 · 2.0%
- 其他国家,或未写国家36 · 3.8%
图中所见
湾区之后是纽约州(12.6%)和华盛顿州(9.0%);19 人写的是英国。
方法与局限
所在地是个人档案上写的地点。美国其他地区包括没写州的档案。
来源:Metix AI Platform 个人档案数据,2026-09-22。
查询population.json · measures.json
{ "note": "Who is counted. A person counts when one job entry is at Meta and current (experience.company.name match current_employer and experience.is_current eq true, in one has_experience entry) and the profile's headline or current_title names the lab with one of lab_terms. The Platform matches text word by word, in any order, and ignores case, so MSL also matches msl and superintelligence also matches SuperIntelligence. Counts are profiles visible through the Metix AI Platform, never the lab's headcount; stale profiles count as current, so a count is not a guaranteed floor either.", "current_employer": "Meta", "current_employer_note": "match Meta on the current entry. The name also matches entries written as Facebook: a current entry named Facebook counts, and a Facebook condition returned all 790 profiles of the narrow definition, so the two names are one employer on the Platform and a Facebook condition is no separate test. company.name eq Meta returned the same 790 profiles as match Meta, and every one of the 63 profiles read in the audit has a current entry at Meta itself.", "lab_terms": [ "superintelligence", "MSL" ], "lab_fields": [ "headline", "current_title" ], "lab_terms_note": "superintelligence alone (the narrow definition) gives 790 profiles. MSL, the lab's short name, adds 146 current Meta profiles that never write superintelligence; 13 of 14 read in a whole slice use it for the lab, and the rest recruit for it. FAIR, one of the lab's groups since 2025, is not a lab term: people who name only FAIR do not name the lab, and teams.json counts them as context (fair_only).", "narrow_terms": [ "superintelligence" ], "history_names": [ "Meta", "Facebook", "Instagram", "WhatsApp", "Oculus" ], "history_names_note": "Names that count as an earlier job at Meta, matched word by word in one has_experience entry. The name Meta does not match an entry listed under Instagram; adding the other names moves fewer than 10 people.", "cut": "2025-06-01", "cut_note": "Meta announced Meta Superintelligence Labs at the end of June 2025. A person with a job entry at a history name that started before the cut had a Meta job before the lab. experience.start_date is a month (YYYY-MM) or a year; the Platform compares it as its first day, so a year alone reads as January. A newcomer whose Meta entry says only 2025 therefore counts as at Meta before the cut, which raises the share at Meta when the lab formed, and an earlier entry whose end date says only 2025 counts as ending before May 2025, which can move someone who was at Meta into returned.", "stay_end": "2025-05-01", "cohorts_note": "Four groups that do not overlap and add up to the whole. Stayed: a non-intern Meta entry that started before the cut and is current or ended in May 2025 or later, so the person was at Meta when the lab formed. Returned: a non-intern Meta entry before the cut, but none that lasted into May 2025, so they had left and came back. Former interns: the only Meta entries before the cut are internships. New to Meta: no Meta entry that started before the cut, including fewer than 10 whose current Meta entry has no start date. Returned, former interns, and new to Meta together are the outside hires, everyone who was not at Meta when the lab formed.", "intern_rule": "An entry is an internship when experience.seniority eq Intern or experience.title matches intern. Both are tested inside the same has_experience entry as the employer and the date.", "labeling_terms": [ "labeling", "labelling", "annotation", "annotator", "red teamer", "red teaming" ], "labeling_note": "Titles and headlines that name data labeling, annotation, or red teaming. The audit found such roles among recent hires (fewer than 10 in the slice read); vendors often staff them, but the profile lists Meta.", "freshness_note": "Profiles are a periodically refreshed snapshot. Across all Meta job entries on the Platform, 3,988 start in 2026, 1,104 of them in March and April and fewer than 10 in May or later, so start dates stop in April 2026 and the most recent months are probably undercounted. April 2026 is the last month shown, and people who joined since are missing.", "audit": "63 profiles read in whole slices, never from the top of a search, because Search ranks by match quality. The slices covered people with no Meta-named entry before the cut, people with a Meta entry before the cut, people who write MSL but not superintelligence, and the profiles whose Meta entry has no start date (fewer than 10). 62 of 63 describe themselves as working in the lab, and the rest recruit for it. All 63 have a current Meta entry, almost all of them named Meta. All 31 read with a Meta entry before the cut had a real Meta job there, not only an internship. Among people without a Meta-named entry before the cut, an earlier Meta job turned up listed under Instagram, which is why Instagram is a history name, and fewer than 10 of them hold data labeling or red teaming roles. Separate reads of sub-team matches found fewer than 10 profiles that say they have left the lab while the Meta entry is still current, so a few members are out of date. Records read for the audit are kept private.", "comparison": { "id": "microsoft", "label": "Microsoft", "current_employer": "Microsoft", "lab_terms": [ "superintelligence" ], "history_names": [ "Microsoft" ], "cut": "2025-11-01", "stay_end": "2025-10-01", "edges": [ "2012-01-01", "2016-01-01", "2020-01-01", "2023-01-01", "2025-01-01" ], "note": "Current Microsoft staff whose headline or current_title names superintelligence. Microsoft AI announced its superintelligence team in November 2025, so the cut for this group is 2025-11-01. Microsoft also matches Microsoft AI and Microsoft Research; subsidiaries with their own names (LinkedIn, GitHub) are not history names. A whole slice of 15 all named the Microsoft AI superintelligence team; fewer than 10 of them are recruiters or sourcers for it." }}
{ "note": "What is counted, all within the population in queries/population.json unless a block says otherwise. Every count is sent with size 1, so it costs 1 API Credit, or nothing when it finds no one, and reads no record.", "first_joined": { "edges": [ "2012-01-01", "2014-01-01", "2016-01-01", "2018-01-01", "2020-01-01", "2022-01-01", "2023-01-01", "2024-01-01", "2025-01-01" ], "after_cut_edges": [ "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "A person's first Meta job started before a date exactly when they have an entry at a history name that started before it, so a count at each edge gives how many first joined before it, and the difference between two edges is a band of first-join dates. Bands run from the start of the record through the cut (the dates in edges) and on month by month and quarter by quarter to April 2026 (after_cut_edges). The last band holds April 2026 and anything later, and the fewer than 10 whose Meta entry has no start date. Adjacent bands merge wherever one would hold 1 to 9 people; the cut is never merged away. The second series counts only non-intern entries, so it gives each person's first Meta job that was not an internship; it runs to the cut, and everyone without such a job before the cut is one band." }, "moves": { "edges": [ "2025-01-01", "2025-04-01", "2025-06-01", "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "For the people who stayed: when their latest current Meta entry started. A count of people with a current Meta entry that started on or after an edge gives how many started their newest current role since then, so a person with two current entries is placed by the newer one. Many people change teams inside Meta without adding an entry, so this shows who recorded a new role, a lower bound on who moved." }, "sources": { "ended_from": "2025-01-01", "note": "Where the outside hires (everyone not at Meta when the lab formed) had just been: a job entry that ended in 2025 or later (experience.end_date gte ended_from), which also means it is no longer current. Internships do not count for companies (the intern rule in population.json), so a PhD student's summer at a lab is not where they came from; for academia they do count, because doctoral students' university entries often carry the Intern label. Rows do not overlap: each person counts at the first row in this order whose condition they meet, and the rest are other employers or none. ai_lab marks the five AI labs whose subtotal is published.", "order": [ { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ], "ai_lab": true }, { "id": "google-deepmind", "label": "Google DeepMind", "names": [ "DeepMind" ], "ai_lab": true }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ], "ai_lab": true }, { "id": "xai", "label": "xAI", "names": [ "xAI" ], "ai_lab": true }, { "id": "thinking-machines", "label": "Thinking Machines Lab", "names": [ "Thinking Machines" ], "ai_lab": true }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "scale-ai", "label": "Scale AI", "names": [ "Scale AI" ] }, { "id": "google", "label": "Google, other than Google DeepMind", "names": [ "Google" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] }, { "id": "nvidia", "label": "NVIDIA", "names": [ "NVIDIA" ] }, { "id": "academia", "label": "A university or other educational institution", "company_type": "Educational" } ], "context": [ { "id": "google", "label": "Google, including Google DeepMind", "names": [ "Google", "DeepMind" ] }, { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ] }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ] }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] } ], "context_note": "For the whole group: anyone with a past (not current) non-intern job at the employer, at any time. These rows overlap and have no total. Names match word by word, so Google also matches Google DeepMind and Amazon matches Amazon Web Services (AWS). company.type Educational is the employer type the Platform records for universities and schools." }, "roles": { "functions": [ "Research", "Engineering and Technical", "Product" ], "senior": [ "Senior" ], "manager_up": [ "Manager", "Head", "Director", "Vice President", "President/Vice President", "C-Level", "Partner", "Founder", "Owner" ], "note": "current_function and current_seniority describe the current job and come from the Platform's fixed sets; either can be missing. Senior covers senior, staff, and principal individual contributors (the audit saw Staff, Senior Staff, and Principal titles labelled Senior); manager_up is Manager and every level above it; the rest of those with a stated level are Specialist or Intern. A doctorate is an education entry with education.degree eq Doctorate, finished or in progress.", "baseline_note": "The baseline is Meta's other research staff: a current Meta entry, current_function eq Research, and no lab term in the headline or current title. It includes people who name FAIR only." }, "teams": [ { "id": "fair", "label": "FAIR", "terms": [ "FAIR" ] }, { "id": "tbd-lab", "label": "TBD Lab", "terms": [ "TBD" ] }, { "id": "infra", "label": "MSL Infra and other infrastructure", "terms": [ "infra", "infrastructure" ] }, { "id": "par", "label": "Products and Applied Research", "terms": [ "PAR", "product applied research" ] } ], "teams_note": "Sub-team names in the headline or current title of people in the population, matched word by word; a person can name more than one. Audited: FAIR, 10 profiles naming it read in whole slices, nearly all naming it as the current team. TBD, all 13 matches read: 10 are in TBD Lab or report to it, and the rest name TBD while recruiting for it, while saying they are not in it, or while saying they have left the lab. Infra, the first 15 of 49 matches for infra or infrastructure (not a whole slice): all 15 work on infrastructure inside the lab, 11 of them naming MSL Infra or Infra at MSL. Products and Applied Research: the words applied research mostly match the job title Applied Research Scientist (most of those read) or an old team name, so the row needs PAR or all of product, applied, and research. fair_only counts current Meta profiles that name FAIR and no lab term; it was not audited outside the population.", "places": { "states": [ "California", "New York", "Washington" ], "bay_area": [ "Menlo Park", "San Francisco", "Sunnyvale", "Palo Alto", "Mountain View", "Redwood City", "Burlingame", "Fremont", "San Jose", "Santa Clara", "San Mateo", "Foster City", "Oakland", "Berkeley", "Cupertino", "Los Altos", "Belmont", "San Carlos", "Millbrae", "San Bruno", "Newark", "Milpitas", "Los Gatos", "Campbell", "Saratoga", "Daly City", "South San Francisco", "Emeryville", "Alameda", "Hayward", "Dublin", "Pleasanton", "Walnut Creek", "Atherton", "Portola Valley", "Woodside", "Half Moon Bay" ], "countries": [ "United Kingdom" ], "note": "The profile's own location, where people list themselves: location.country and location.state, and location.city for the Bay Area, whose cities are listed one by one and compared exactly." }, "postings": { "company": "Meta", "title_terms": [ "superintelligence", "MSL" ], "description_terms": [ "superintelligence labs" ], "research_title": "research", "cities": [ "Menlo Park", "San Francisco" ], "states": [ "New York" ], "experience_max_months": 36, "posted_from": "2026-09-01", "note": "Open Meta postings (is_open eq true) whose title names superintelligence or MSL, or whose description contains the words superintelligence and labs. All 30 read on 2026-09-22 are Meta postings whose description names Meta Superintelligence Labs. Every one carries the seniority label Not Applicable, so seniority says nothing here, and all were posted in September 2026, so the index shows the openings of the moment rather than a history. Counts of postings carry no minimum." }}
09
30 个在招的 Meta 岗位写明实验室,其中 23 个在 Menlo Park
快照
Menlo Park 23,旧金山 3,纽约 2,其他地点 2
- Menlo Park23 · 76.7%
- 旧金山3 · 10.0%
- 纽约2 · 6.7%
- 其他地点2 · 6.7%
图中所见
它们占 Meta 2,104 个在招岗位的 1.4%;14 个的职位名称里有 research。
方法与局限
只是一天的岗位。30 个岗位都发布于 2026 年 9 月,资历标签都是 Not Applicable,所以这两项在这里说明不了什么。写明经验要求的 26 个岗位中,7 个要求 36 个月以内。
来源:Metix AI Platform 岗位数据,2026-09-22。
查询population.json · measures.json
{ "note": "Who is counted. A person counts when one job entry is at Meta and current (experience.company.name match current_employer and experience.is_current eq true, in one has_experience entry) and the profile's headline or current_title names the lab with one of lab_terms. The Platform matches text word by word, in any order, and ignores case, so MSL also matches msl and superintelligence also matches SuperIntelligence. Counts are profiles visible through the Metix AI Platform, never the lab's headcount; stale profiles count as current, so a count is not a guaranteed floor either.", "current_employer": "Meta", "current_employer_note": "match Meta on the current entry. The name also matches entries written as Facebook: a current entry named Facebook counts, and a Facebook condition returned all 790 profiles of the narrow definition, so the two names are one employer on the Platform and a Facebook condition is no separate test. company.name eq Meta returned the same 790 profiles as match Meta, and every one of the 63 profiles read in the audit has a current entry at Meta itself.", "lab_terms": [ "superintelligence", "MSL" ], "lab_fields": [ "headline", "current_title" ], "lab_terms_note": "superintelligence alone (the narrow definition) gives 790 profiles. MSL, the lab's short name, adds 146 current Meta profiles that never write superintelligence; 13 of 14 read in a whole slice use it for the lab, and the rest recruit for it. FAIR, one of the lab's groups since 2025, is not a lab term: people who name only FAIR do not name the lab, and teams.json counts them as context (fair_only).", "narrow_terms": [ "superintelligence" ], "history_names": [ "Meta", "Facebook", "Instagram", "WhatsApp", "Oculus" ], "history_names_note": "Names that count as an earlier job at Meta, matched word by word in one has_experience entry. The name Meta does not match an entry listed under Instagram; adding the other names moves fewer than 10 people.", "cut": "2025-06-01", "cut_note": "Meta announced Meta Superintelligence Labs at the end of June 2025. A person with a job entry at a history name that started before the cut had a Meta job before the lab. experience.start_date is a month (YYYY-MM) or a year; the Platform compares it as its first day, so a year alone reads as January. A newcomer whose Meta entry says only 2025 therefore counts as at Meta before the cut, which raises the share at Meta when the lab formed, and an earlier entry whose end date says only 2025 counts as ending before May 2025, which can move someone who was at Meta into returned.", "stay_end": "2025-05-01", "cohorts_note": "Four groups that do not overlap and add up to the whole. Stayed: a non-intern Meta entry that started before the cut and is current or ended in May 2025 or later, so the person was at Meta when the lab formed. Returned: a non-intern Meta entry before the cut, but none that lasted into May 2025, so they had left and came back. Former interns: the only Meta entries before the cut are internships. New to Meta: no Meta entry that started before the cut, including fewer than 10 whose current Meta entry has no start date. Returned, former interns, and new to Meta together are the outside hires, everyone who was not at Meta when the lab formed.", "intern_rule": "An entry is an internship when experience.seniority eq Intern or experience.title matches intern. Both are tested inside the same has_experience entry as the employer and the date.", "labeling_terms": [ "labeling", "labelling", "annotation", "annotator", "red teamer", "red teaming" ], "labeling_note": "Titles and headlines that name data labeling, annotation, or red teaming. The audit found such roles among recent hires (fewer than 10 in the slice read); vendors often staff them, but the profile lists Meta.", "freshness_note": "Profiles are a periodically refreshed snapshot. Across all Meta job entries on the Platform, 3,988 start in 2026, 1,104 of them in March and April and fewer than 10 in May or later, so start dates stop in April 2026 and the most recent months are probably undercounted. April 2026 is the last month shown, and people who joined since are missing.", "audit": "63 profiles read in whole slices, never from the top of a search, because Search ranks by match quality. The slices covered people with no Meta-named entry before the cut, people with a Meta entry before the cut, people who write MSL but not superintelligence, and the profiles whose Meta entry has no start date (fewer than 10). 62 of 63 describe themselves as working in the lab, and the rest recruit for it. All 63 have a current Meta entry, almost all of them named Meta. All 31 read with a Meta entry before the cut had a real Meta job there, not only an internship. Among people without a Meta-named entry before the cut, an earlier Meta job turned up listed under Instagram, which is why Instagram is a history name, and fewer than 10 of them hold data labeling or red teaming roles. Separate reads of sub-team matches found fewer than 10 profiles that say they have left the lab while the Meta entry is still current, so a few members are out of date. Records read for the audit are kept private.", "comparison": { "id": "microsoft", "label": "Microsoft", "current_employer": "Microsoft", "lab_terms": [ "superintelligence" ], "history_names": [ "Microsoft" ], "cut": "2025-11-01", "stay_end": "2025-10-01", "edges": [ "2012-01-01", "2016-01-01", "2020-01-01", "2023-01-01", "2025-01-01" ], "note": "Current Microsoft staff whose headline or current_title names superintelligence. Microsoft AI announced its superintelligence team in November 2025, so the cut for this group is 2025-11-01. Microsoft also matches Microsoft AI and Microsoft Research; subsidiaries with their own names (LinkedIn, GitHub) are not history names. A whole slice of 15 all named the Microsoft AI superintelligence team; fewer than 10 of them are recruiters or sourcers for it." }}
{ "note": "What is counted, all within the population in queries/population.json unless a block says otherwise. Every count is sent with size 1, so it costs 1 API Credit, or nothing when it finds no one, and reads no record.", "first_joined": { "edges": [ "2012-01-01", "2014-01-01", "2016-01-01", "2018-01-01", "2020-01-01", "2022-01-01", "2023-01-01", "2024-01-01", "2025-01-01" ], "after_cut_edges": [ "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "A person's first Meta job started before a date exactly when they have an entry at a history name that started before it, so a count at each edge gives how many first joined before it, and the difference between two edges is a band of first-join dates. Bands run from the start of the record through the cut (the dates in edges) and on month by month and quarter by quarter to April 2026 (after_cut_edges). The last band holds April 2026 and anything later, and the fewer than 10 whose Meta entry has no start date. Adjacent bands merge wherever one would hold 1 to 9 people; the cut is never merged away. The second series counts only non-intern entries, so it gives each person's first Meta job that was not an internship; it runs to the cut, and everyone without such a job before the cut is one band." }, "moves": { "edges": [ "2025-01-01", "2025-04-01", "2025-06-01", "2025-07-01", "2025-08-01", "2025-09-01", "2025-10-01", "2026-01-01", "2026-04-01" ], "note": "For the people who stayed: when their latest current Meta entry started. A count of people with a current Meta entry that started on or after an edge gives how many started their newest current role since then, so a person with two current entries is placed by the newer one. Many people change teams inside Meta without adding an entry, so this shows who recorded a new role, a lower bound on who moved." }, "sources": { "ended_from": "2025-01-01", "note": "Where the outside hires (everyone not at Meta when the lab formed) had just been: a job entry that ended in 2025 or later (experience.end_date gte ended_from), which also means it is no longer current. Internships do not count for companies (the intern rule in population.json), so a PhD student's summer at a lab is not where they came from; for academia they do count, because doctoral students' university entries often carry the Intern label. Rows do not overlap: each person counts at the first row in this order whose condition they meet, and the rest are other employers or none. ai_lab marks the five AI labs whose subtotal is published.", "order": [ { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ], "ai_lab": true }, { "id": "google-deepmind", "label": "Google DeepMind", "names": [ "DeepMind" ], "ai_lab": true }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ], "ai_lab": true }, { "id": "xai", "label": "xAI", "names": [ "xAI" ], "ai_lab": true }, { "id": "thinking-machines", "label": "Thinking Machines Lab", "names": [ "Thinking Machines" ], "ai_lab": true }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "scale-ai", "label": "Scale AI", "names": [ "Scale AI" ] }, { "id": "google", "label": "Google, other than Google DeepMind", "names": [ "Google" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] }, { "id": "nvidia", "label": "NVIDIA", "names": [ "NVIDIA" ] }, { "id": "academia", "label": "A university or other educational institution", "company_type": "Educational" } ], "context": [ { "id": "google", "label": "Google, including Google DeepMind", "names": [ "Google", "DeepMind" ] }, { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ] }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ] }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] } ], "context_note": "For the whole group: anyone with a past (not current) non-intern job at the employer, at any time. These rows overlap and have no total. Names match word by word, so Google also matches Google DeepMind and Amazon matches Amazon Web Services (AWS). company.type Educational is the employer type the Platform records for universities and schools." }, "roles": { "functions": [ "Research", "Engineering and Technical", "Product" ], "senior": [ "Senior" ], "manager_up": [ "Manager", "Head", "Director", "Vice President", "President/Vice President", "C-Level", "Partner", "Founder", "Owner" ], "note": "current_function and current_seniority describe the current job and come from the Platform's fixed sets; either can be missing. Senior covers senior, staff, and principal individual contributors (the audit saw Staff, Senior Staff, and Principal titles labelled Senior); manager_up is Manager and every level above it; the rest of those with a stated level are Specialist or Intern. A doctorate is an education entry with education.degree eq Doctorate, finished or in progress.", "baseline_note": "The baseline is Meta's other research staff: a current Meta entry, current_function eq Research, and no lab term in the headline or current title. It includes people who name FAIR only." }, "teams": [ { "id": "fair", "label": "FAIR", "terms": [ "FAIR" ] }, { "id": "tbd-lab", "label": "TBD Lab", "terms": [ "TBD" ] }, { "id": "infra", "label": "MSL Infra and other infrastructure", "terms": [ "infra", "infrastructure" ] }, { "id": "par", "label": "Products and Applied Research", "terms": [ "PAR", "product applied research" ] } ], "teams_note": "Sub-team names in the headline or current title of people in the population, matched word by word; a person can name more than one. Audited: FAIR, 10 profiles naming it read in whole slices, nearly all naming it as the current team. TBD, all 13 matches read: 10 are in TBD Lab or report to it, and the rest name TBD while recruiting for it, while saying they are not in it, or while saying they have left the lab. Infra, the first 15 of 49 matches for infra or infrastructure (not a whole slice): all 15 work on infrastructure inside the lab, 11 of them naming MSL Infra or Infra at MSL. Products and Applied Research: the words applied research mostly match the job title Applied Research Scientist (most of those read) or an old team name, so the row needs PAR or all of product, applied, and research. fair_only counts current Meta profiles that name FAIR and no lab term; it was not audited outside the population.", "places": { "states": [ "California", "New York", "Washington" ], "bay_area": [ "Menlo Park", "San Francisco", "Sunnyvale", "Palo Alto", "Mountain View", "Redwood City", "Burlingame", "Fremont", "San Jose", "Santa Clara", "San Mateo", "Foster City", "Oakland", "Berkeley", "Cupertino", "Los Altos", "Belmont", "San Carlos", "Millbrae", "San Bruno", "Newark", "Milpitas", "Los Gatos", "Campbell", "Saratoga", "Daly City", "South San Francisco", "Emeryville", "Alameda", "Hayward", "Dublin", "Pleasanton", "Walnut Creek", "Atherton", "Portola Valley", "Woodside", "Half Moon Bay" ], "countries": [ "United Kingdom" ], "note": "The profile's own location, where people list themselves: location.country and location.state, and location.city for the Bay Area, whose cities are listed one by one and compared exactly." }, "postings": { "company": "Meta", "title_terms": [ "superintelligence", "MSL" ], "description_terms": [ "superintelligence labs" ], "research_title": "research", "cities": [ "Menlo Park", "San Francisco" ], "states": [ "New York" ], "experience_max_months": 36, "posted_from": "2026-09-01", "note": "Open Meta postings (is_open eq true) whose title names superintelligence or MSL, or whose description contains the words superintelligence and labs. All 30 read on 2026-09-22 are Meta postings whose description names Meta Superintelligence Labs. Every one carries the seniority label Not Applicable, so seniority says nothing here, and all were posted in September 2026, so the index shows the openings of the moment rather than a history. Counts of postings carry no minimum." }}
第二阶段 · 组织地图
实验室占 Meta 可见 AI 员工的九分之一;离开 Meta 去 AI 实验室的人,比从那里加入的人多
第一
Meta 在 2025 年 6 月 30 日成立实验室,2025 年 8 月把它分成四个团队(TBD Lab、FAIR、Products and Applied Research 和 MSL Infra),2025 年 10 月在其中三个团队裁减 600 多个职位,TBD Lab 未受影响。截至 2026 年 6 月 30 日,Meta 报告员工 75,472 人。
要点
- 8,257 个当前在
Meta 的个人档案写明了 AI 岗位。 其中 62.8% 九个单元 都没写;写明的单元里实验室最大,有 936 人,其次是原组织名 GenAI,有 506 人。 - 没写实验室的
FAIR 是研究 比例 最高的单元: 69.8% 做研究, 57.2% 写有博士 学历。 AI 基础设施 74.4% 是工程; 广告与变现有 34.4% 在经理及以上, 全体是 14.2%。 - 实验室
35.1% 做研究, Meta 其他 可见 AI 员工是 17.8%; 其他人里 24.2% 的职位是机器 学习 工程师。 - 2025 年
6 月以来, Meta 所有 岗位 中有 379 人离开, 去了 五家 AI 实验室,从那里 加入 Meta 的最多 107 人;同期从 Amazon 加入 691 人,从 Microsoft 加入 343 人。
形态
第 4 部分,图 10、11
Meta 的
10
Meta 可见 AI 员工中 63% 九个单元都没写;写明的单元里实验室最大,占 11.3%
每人只算一次,按说明里的固定
一张流向图:左边 Meta 可见的 AI 员工 8,257 人,按比例分成十条色带流向各单元,实验室占 11.3%,一个单元都没写的占 62.8%;实验室的色带再分给它的四个团队,放大 4 倍画,936 人中至少 802 人四个团队都没写。旁边的面板给出所选单元六项比例和 Meta 全体的对比。
实验室的 936 人,放大 4 倍
FAIR63
MSL Infra
TBD Lab13
Products and Applied Research<10
四个团队
FAIR63
MSL Infra
TBD Lab13
Products and Applied Research<10
四个团队
单元画像
Meta · 可见的 AI 员工
8,257 个档案 · 第二阶段的全部人群
- 研究20%
- 工程58%
- 经理及以上14%
- 博士29%
- 大陆本科20%
- 美国83%
其他单元的竖线就是这里的数值。
单元画像
Meta 超级智能实验室
936 个档案 · 占 Meta 可见 AI 员工的 11.3%
- 研究8 个单元中第 235%
- 工程9 个单元中第 639%
- 经理及以上9 个单元中第 718%
- 博士8 个单元中第 332%
- 大陆本科8 个单元中第 320%
- 美国8 个单元中第 294%
竖线:Meta 全体四个团队会重叠,图 07 分别列出。
单元画像
GenAI(原组织名)
506 个档案 · 占 Meta 可见 AI 员工的 6.1%
- 研究8 个单元中第 420%
- 工程9 个单元中第 734%
- 经理及以上9 个单元中第 325%
- 博士8 个单元中第 620%
- 大陆本科8 个单元中第 712%
- 美国8 个单元中第 590%
竖线:Meta 全体
单元画像
Reality Labs、AR、VR 与可穿戴设备
400 个档案 · 占 Meta 可见 AI 员工的 4.8%
- 研究8 个单元中第 517%
- 工程9 个单元中第 540%
- 经理及以上9 个单元中第 620%
- 博士8 个单元中第 524%
- 大陆本科8 个单元中最低4%
- 美国8 个单元中第 682%
竖线:Meta 全体
单元画像
AI 基础设施
390 个档案 · 占 Meta 可见 AI 员工的 4.7%
- 研究8 个单元中最低4%
- 工程9 个单元中最高74%
- 经理及以上9 个单元中第 522%
- 博士8 个单元中最低10%
- 大陆本科8 个单元中第 515%
- 美国8 个单元中最高94%
竖线:Meta 全体
单元画像
广告与变现
314 个档案 · 占 Meta 可见 AI 员工的 3.8%
- 研究8 个单元中第 711%
- 工程9 个单元中第 452%
- 经理及以上9 个单元中最高34%
- 博士8 个单元中第 425%
- 大陆本科8 个单元中第 222%
- 美国8 个单元中第 491%
竖线:Meta 全体
单元画像
FAIR(没写实验室)
215 个档案 · 占 Meta 可见 AI 员工的 2.6%
- 研究8 个单元中最高70%
- 工程9 个单元中最低16%
- 经理及以上9 个单元中最低8%
- 博士8 个单元中最高57%
- 大陆本科8 个单元中第 416%
- 美国8 个单元中最低66%
竖线:Meta 全体
单元画像
排序与推荐
152 个档案 · 占 Meta 可见 AI 员工的 1.8%
- 研究8 个单元中第 323%
- 工程9 个单元中第 259%
- 经理及以上9 个单元中第 816%
- 博士8 个单元中第 236%
- 大陆本科8 个单元中最高28%
- 美国8 个单元中第 391%
竖线:Meta 全体
单元画像
Instagram、WhatsApp、Messenger、Threads
104 个档案 · 占 Meta 可见 AI 员工的 1.3%
- 研究8 个单元中第 612%
- 工程9 个单元中第 353%
- 经理及以上9 个单元中第 423%
- 博士8 个单元中第 718%
- 大陆本科8 个单元中第 613%
- 美国不公开
竖线:Meta 全体
单元画像
内容安全(Integrity)
52 个档案 · 占 Meta 可见 AI 员工的 0.6%
- 研究不公开
- 工程9 个单元中第 831%
- 经理及以上9 个单元中第 227%
- 博士不公开
- 大陆本科不公开
- 美国8 个单元中第 771%
竖线:Meta 全体
单元画像
以上都没写
5,188 个档案 · 占 Meta 可见 AI 员工的 62.8%
- 研究不公开
- 工程66%
- 经理及以上10%
- 博士不公开
- 大陆本科不公开
- 美国不公开
竖线:Meta 全体这里大部分比例不公开,否则可以用减法算出小群体。
| 单元 | 人数 | 占全部的比例 | 研究 | 工程 | 经理及以上 | 博士 | 大陆本科 | 美国 |
|---|---|---|---|---|---|---|---|---|
| Meta · 可见的 AI 员工 | 8,257 | 100.0% | 20% | 58% | 14% | 29% | 20% | 83% |
| Meta 超级智能实验室 | 936 | 11.3% | 35% | 39% | 18% | 32% | 20% | 94% |
| 其中(实验室):FAIR | 63 | 不适用 | 未统计 | 未统计 | 未统计 | 未统计 | 未统计 | 未统计 |
| 其中(实验室):MSL Infra 及其他基础设施 | 49 | 不适用 | 未统计 | 未统计 | 未统计 | 未统计 | 未统计 | 未统计 |
| 其中(实验室):TBD Lab | 13 | 不适用 | 未统计 | 未统计 | 未统计 | 未统计 | 未统计 | 未统计 |
| 其中(实验室):Products and Applied Research | <10 | 不适用 | 未统计 | 未统计 | 未统计 | 未统计 | 未统计 | 未统计 |
| 其中(实验室):四个团队都没写 | ≥ 802 | 不适用 | 未统计 | 未统计 | 未统计 | 未统计 | 未统计 | 未统计 |
| GenAI(原组织名) | 506 | 6.1% | 20% | 34% | 25% | 20% | 12% | 90% |
| Reality Labs、AR、VR 与可穿戴设备 | 400 | 4.8% | 17% | 40% | 20% | 24% | 4% | 82% |
| AI 基础设施 | 390 | 4.7% | 4% | 74% | 22% | 10% | 15% | 94% |
| 广告与变现 | 314 | 3.8% | 11% | 52% | 34% | 25% | 22% | 91% |
| FAIR(没写实验室) | 215 | 2.6% | 70% | 16% | 8% | 57% | 16% | 66% |
| 排序与推荐 | 152 | 1.8% | 23% | 59% | 16% | 36% | 28% | 91% |
| Instagram、WhatsApp、Messenger、Threads | 104 | 1.3% | 12% | 53% | 23% | 18% | 13% | 不公开 |
| 内容安全(Integrity) | 52 | 0.6% | 不公开 | 31% | 27% | 不公开 | 不公开 | 71% |
| 以上都没写 | 5,188 | 62.8% | 不公开 | 66% | 10% | 不公开 | 不公开 | 不公开 |
图中所见
实验室占 Meta 可见 AI 员工的 11.3%,其中 35.1% 做研究,全体是 19.8%。没写实验室的 FAIR 是研究比例最高的单元(69.8% 做研究,57.2% 写有博士学历);AI 基础设施 74.4% 是工程;广告与变现有 34.4% 在经理及以上。在公开的单元中,中国大陆本科的比例从 Reality Labs 的 4.4% 到排序与推荐的 27.9%。
方法与局限
单元是大家自己写的,不是 Meta 的组织架构图。顺序是实验室、FAIR、Reality Labs、基础设施、广告、排序、内容安全、应用、GenAI;GenAI 排在各产品领域之后,因为抽读的 GenAI 中有三分之一指的是话题,不是原组织。实验室下面的四个团队来自第一阶段,会重叠。第一阶段有 238 个档案写了 FAIR 但没写实验室,其中 215 个符合第二阶段的定义。中国大陆本科的比例以写有本科者为分母。"·"是为了不让读者算出 1 到 9 人的小群体而不公开的格子。
来源:Metix AI Platform 个人档案数据,2026-09-22。
查询mapping.json (population, units) · population.json
{ "population": { "id": "p2", "label": "Meta's visible AI staff", "note": "A current Meta entry (the stage-1 entry: experience.company.name match Meta and experience.is_current eq true), an AI term in the headline or current title, and three filters that apply to everyone except the lab. The lab's 936 people (queries/population.json) are all in P2 by construction, so the lab node is exactly the stage-1 population and no stage-2 count of the lab differs from a stage-1 count by a small group. Everyone else also needs a current Meta entry whose employer size is 10,001+, a current_function outside non_technical_functions, and a current title with none of non_technical_title_words.", "ai_terms": [ "machine learning", "ML", "deep learning", "computer vision", "NLP", "natural language processing", "LLM", "LLMs", "large language models", "reinforcement learning", "generative AI", "GenAI", "artificial intelligence", "superintelligence", "MSL", "FAIR" ], "ai_terms_fields": [ "headline", "current_title" ], "title_only_terms": [ "AI" ], "employer_size": "10,001+", "non_technical_functions": [ "Human Resources", "Sales", "Marketing", "Administrative", "Finance & Accounting", "Legal", "Customer Service", "Real Estate" ], "non_technical_title_words": [ "marketing", "sales", "recruiter", "recruiting", "sourcer", "sourcing", "talent", "administrative", "assistant", "counsel", "attorney", "paralegal", "accountant", "communications", "partnerships" ], "lab_note": "26 of the 936 list a non-technical function (recruiting and administration, mostly) and 12 more a non-technical title word. They stay in P2 as members of the lab, so the lab row carries them (about 4% of it) while the rest of P2 does not; the function table shows them among other functions.", "decisions": [ "The draft term list (machine learning, AI, artificial intelligence, research scientist, research engineer, applied scientist, deep learning, LLM, computer vision, NLP, superintelligence, MSL, FAIR, generative AI, GenAI) gave 15,229 current Meta profiles and 14,297 after the function filter.", "AI alone counts only in the current title. 4,003 draft profiles entered only through AI in the headline, where it is mostly a buzzword (AI-driven testing, cloud and AI platforms); in the first slice read, about half of them held AI roles.", "Research scientist, research engineer, and applied scientist are not AI terms. Matching is word by word, so research engineer also matched titles such as a software engineer in Reality Labs Research, and plain research titles at Meta also cover people research, survey science, software testing, photonics, materials, and physical modeling. With these titles admitted, reads in California and Washington found 75 to 82% in AI roles; without them, 92%. 2,180 profiles entered only through such a title and are left out; research scientists who name an AI term, FAIR, or the lab stay in.", "The employer must be the 10,001+ company. Outside the US the name Meta also matches small companies: 6 of 25 profiles in one slice outside the US worked at other firms whose names contain Meta, none of them sized 10,001+. The rule drops 845 draft profiles, most of them Meta work recorded under variant names or through staffing agencies, and a few that are not Meta at all.", "ML, LLMs, large language models, natural language processing, and reinforcement learning were added; together they bring 547 profiles the draft missed.", "Title words exclude marketing, sales, recruiting, and other non-technical roles whose current_function is missing or not in the excluded set (administrative, marketing, and sales roles in the reads)." ], "audit": "365 profiles read in whole slices, each a narrow filter read in full (one state or country and a range of total_experience_months), never the top of a search. The first slice (49 profiles of the draft) and three candidate slices (53) set the rules above. 150 profiles in eight whole slices fall in the final P2: 138 (92.0%) hold AI roles by their title, headline, and current job description. The last slice, 39 profiles read after the definition was fixed, gave 35 (89.7%) when two borderline creative and advisory roles count as misses. The misses are stale profiles that still list a current Meta job, generic engineers whose headline lists AI words, and a few operations roles. Contract data workers (prompt engineers, annotators, knowledge experts) who list Meta count as AI roles; they appear under data titles. No lab member with a non-technical function falls in the slices read. Records read for the audit are kept private.", "size_note": "The name Meta on a current entry gives 66,757 profiles in the US and more than 100,000 elsewhere, because outside the US it also matches other companies. With the employer size 10,001+ in the same entry the count is exact on both sides. A company's reported headcount is the comparison; visible profiles also include contractors and profiles not yet updated after someone left." }, "units": { "note": "Each person counts at the first unit in this order whose terms appear in the headline or current title, so the rows do not overlap and add up to P2. The lab comes first, so every lab member is in the lab row whatever else they name. Units are what people write, not Meta's org chart.", "order": [ { "id": "lab", "label": "Meta Superintelligence Labs", "terms": [ "superintelligence", "MSL" ] }, { "id": "fair", "label": "FAIR, outside the lab", "terms": [ "FAIR" ] }, { "id": "reality-labs", "label": "Reality Labs, AR, VR, and wearables", "terms": [ "Reality Labs", "AR", "VR", "XR", "augmented reality", "virtual reality", "mixed reality", "wearables", "smart glasses", "Oculus" ] }, { "id": "infrastructure", "label": "AI infrastructure", "terms": [ "infra", "infrastructure" ] }, { "id": "ads", "label": "Ads and monetization", "terms": [ "ads", "monetization", "advertising" ] }, { "id": "ranking", "label": "Ranking and recommendations", "terms": [ "ranking", "recommendation", "recommendations", "recommender", "recsys" ] }, { "id": "integrity", "label": "Integrity", "terms": [ "integrity" ] }, { "id": "apps", "label": "Instagram, WhatsApp, Messenger, Threads", "terms": [ "Instagram", "WhatsApp", "Messenger", "Threads" ] }, { "id": "genai", "label": "GenAI, the former org name", "terms": [ "GenAI" ] } ], "none": { "id": "none", "label": "Names none of these" }, "attributes": { "research": "current_function eq Research", "engineering": "current_function eq Engineering and Technical", "manager_up": "current_seniority in Manager, Head, Director, Vice President, President/Vice President, C-Level, Partner, Founder, Owner (the stage-1 set in queries/measures.json)", "doctorate": "an education entry with degree Doctorate", "us": "location.country eq United States", "china_educated": "a Bachelor entry at an institution on the mainland-China list (china_educated below)", "bachelor": "any Bachelor entry, the base of the China-educated share" }, "audit": [ "GenAI: a whole slice of 24 profiles outside the lab: 16 name Meta's former GenAI org, and 8 use the word for the topic, 5 of them inside ads, integrity, Instagram, or AR and VR work. GenAI therefore comes after the product areas, so that topic uses that name an area count there.", "Generative AI without GenAI: a whole slice of 23: 5 read as the org, all of them job titles, and 18 as the topic. The phrase is not a unit term.", "AR, VR, and wearables without Reality Labs: a whole slice of 16: 12 describe work on Reality Labs products (Quest, smart glasses, wearables), 4 do not (ads, sales, creator, and stale profiles). Reality Labs itself is the org name.", "Infra or infrastructure outside the lab: a whole slice of 28: 26 work on AI infrastructure, 6 of them ads ML infrastructure, which counts here because infrastructure comes before ads; 2 work on network or general infrastructure.", "FAIR outside the lab: all 7 who name it in the eight P2 slices are FAIR research staff. 215 of the 238 current Meta profiles that name FAIR and no lab term (stage 1) are in P2.", "Ads, ranking, integrity, and app names were not read in slices of their own; in the P2 slices they name the current team's product area (ads ranking, Reels ranking, integrity, Instagram)." ] }}
{ "note": "Who is counted. A person counts when one job entry is at Meta and current (experience.company.name match current_employer and experience.is_current eq true, in one has_experience entry) and the profile's headline or current_title names the lab with one of lab_terms. The Platform matches text word by word, in any order, and ignores case, so MSL also matches msl and superintelligence also matches SuperIntelligence. Counts are profiles visible through the Metix AI Platform, never the lab's headcount; stale profiles count as current, so a count is not a guaranteed floor either.", "current_employer": "Meta", "current_employer_note": "match Meta on the current entry. The name also matches entries written as Facebook: a current entry named Facebook counts, and a Facebook condition returned all 790 profiles of the narrow definition, so the two names are one employer on the Platform and a Facebook condition is no separate test. company.name eq Meta returned the same 790 profiles as match Meta, and every one of the 63 profiles read in the audit has a current entry at Meta itself.", "lab_terms": [ "superintelligence", "MSL" ], "lab_fields": [ "headline", "current_title" ], "lab_terms_note": "superintelligence alone (the narrow definition) gives 790 profiles. MSL, the lab's short name, adds 146 current Meta profiles that never write superintelligence; 13 of 14 read in a whole slice use it for the lab, and the rest recruit for it. FAIR, one of the lab's groups since 2025, is not a lab term: people who name only FAIR do not name the lab, and teams.json counts them as context (fair_only).", "narrow_terms": [ "superintelligence" ], "history_names": [ "Meta", "Facebook", "Instagram", "WhatsApp", "Oculus" ], "history_names_note": "Names that count as an earlier job at Meta, matched word by word in one has_experience entry. The name Meta does not match an entry listed under Instagram; adding the other names moves fewer than 10 people.", "cut": "2025-06-01", "cut_note": "Meta announced Meta Superintelligence Labs at the end of June 2025. A person with a job entry at a history name that started before the cut had a Meta job before the lab. experience.start_date is a month (YYYY-MM) or a year; the Platform compares it as its first day, so a year alone reads as January. A newcomer whose Meta entry says only 2025 therefore counts as at Meta before the cut, which raises the share at Meta when the lab formed, and an earlier entry whose end date says only 2025 counts as ending before May 2025, which can move someone who was at Meta into returned.", "stay_end": "2025-05-01", "cohorts_note": "Four groups that do not overlap and add up to the whole. Stayed: a non-intern Meta entry that started before the cut and is current or ended in May 2025 or later, so the person was at Meta when the lab formed. Returned: a non-intern Meta entry before the cut, but none that lasted into May 2025, so they had left and came back. Former interns: the only Meta entries before the cut are internships. New to Meta: no Meta entry that started before the cut, including fewer than 10 whose current Meta entry has no start date. Returned, former interns, and new to Meta together are the outside hires, everyone who was not at Meta when the lab formed.", "intern_rule": "An entry is an internship when experience.seniority eq Intern or experience.title matches intern. Both are tested inside the same has_experience entry as the employer and the date.", "labeling_terms": [ "labeling", "labelling", "annotation", "annotator", "red teamer", "red teaming" ], "labeling_note": "Titles and headlines that name data labeling, annotation, or red teaming. The audit found such roles among recent hires (fewer than 10 in the slice read); vendors often staff them, but the profile lists Meta.", "freshness_note": "Profiles are a periodically refreshed snapshot. Across all Meta job entries on the Platform, 3,988 start in 2026, 1,104 of them in March and April and fewer than 10 in May or later, so start dates stop in April 2026 and the most recent months are probably undercounted. April 2026 is the last month shown, and people who joined since are missing.", "audit": "63 profiles read in whole slices, never from the top of a search, because Search ranks by match quality. The slices covered people with no Meta-named entry before the cut, people with a Meta entry before the cut, people who write MSL but not superintelligence, and the profiles whose Meta entry has no start date (fewer than 10). 62 of 63 describe themselves as working in the lab, and the rest recruit for it. All 63 have a current Meta entry, almost all of them named Meta. All 31 read with a Meta entry before the cut had a real Meta job there, not only an internship. Among people without a Meta-named entry before the cut, an earlier Meta job turned up listed under Instagram, which is why Instagram is a history name, and fewer than 10 of them hold data labeling or red teaming roles. Separate reads of sub-team matches found fewer than 10 profiles that say they have left the lab while the Meta entry is still current, so a few members are out of date. Records read for the audit are kept private.", "comparison": { "id": "microsoft", "label": "Microsoft", "current_employer": "Microsoft", "lab_terms": [ "superintelligence" ], "history_names": [ "Microsoft" ], "cut": "2025-11-01", "stay_end": "2025-10-01", "edges": [ "2012-01-01", "2016-01-01", "2020-01-01", "2023-01-01", "2025-01-01" ], "note": "Current Microsoft staff whose headline or current_title names superintelligence. Microsoft AI announced its superintelligence team in November 2025, so the cut for this group is 2025-11-01. Microsoft also matches Microsoft AI and Microsoft Research; subsidiaries with their own names (LinkedIn, GitHub) are not history names. A whole slice of 15 all named the Microsoft AI superintelligence team; fewer than 10 of them are recruiters or sourcers for it." }}
11
当前在 Meta 的个人档案是 Meta 报告员工数的 1.7 倍,所以这里数的是档案,不是员工
条形
可见档案 128,970;报告员工数 75,472;写明 AI 岗位 8,257;写明实验室 936
- 当前在 Meta 的可见个人档案观测值128,970
- Meta 报告的员工人数,2026 年 6 月 30 日公开资料,SEC 文件75,472
- 写明 AI 岗位的档案观测值8,257
- 其中写明实验室观测值936
图中所见
Meta 报告 2026 年 6 月 30 日有员工 75,472 人,平台上当前在 Meta 的档案是 128,970 个,每名员工对应 1.7 个。离职后没更新的档案和写 Meta 的外包人员都算作当前在职,所以这里数的是档案;8,257 这个数既不是 Meta AI 员工的下限,也不是上限。
方法与局限
档案数是当前在 Meta(规模 10,001 人以上的这家公司)的档案,美国和美国以外相加。员工数是 Meta 自己的数字(SEC 文件,2026 年 7 月 29 日),其中包括约 8,000 名受 2026 年 5 月裁员影响的员工;档案日期截至 2026 年 4 月,所以数据里看不到这次裁员。
来源:Metix AI Platform 个人档案与岗位数据,2026-09-22。
查询mapping.json (population)
{ "population": { "id": "p2", "label": "Meta's visible AI staff", "note": "A current Meta entry (the stage-1 entry: experience.company.name match Meta and experience.is_current eq true), an AI term in the headline or current title, and three filters that apply to everyone except the lab. The lab's 936 people (queries/population.json) are all in P2 by construction, so the lab node is exactly the stage-1 population and no stage-2 count of the lab differs from a stage-1 count by a small group. Everyone else also needs a current Meta entry whose employer size is 10,001+, a current_function outside non_technical_functions, and a current title with none of non_technical_title_words.", "ai_terms": [ "machine learning", "ML", "deep learning", "computer vision", "NLP", "natural language processing", "LLM", "LLMs", "large language models", "reinforcement learning", "generative AI", "GenAI", "artificial intelligence", "superintelligence", "MSL", "FAIR" ], "ai_terms_fields": [ "headline", "current_title" ], "title_only_terms": [ "AI" ], "employer_size": "10,001+", "non_technical_functions": [ "Human Resources", "Sales", "Marketing", "Administrative", "Finance & Accounting", "Legal", "Customer Service", "Real Estate" ], "non_technical_title_words": [ "marketing", "sales", "recruiter", "recruiting", "sourcer", "sourcing", "talent", "administrative", "assistant", "counsel", "attorney", "paralegal", "accountant", "communications", "partnerships" ], "lab_note": "26 of the 936 list a non-technical function (recruiting and administration, mostly) and 12 more a non-technical title word. They stay in P2 as members of the lab, so the lab row carries them (about 4% of it) while the rest of P2 does not; the function table shows them among other functions.", "decisions": [ "The draft term list (machine learning, AI, artificial intelligence, research scientist, research engineer, applied scientist, deep learning, LLM, computer vision, NLP, superintelligence, MSL, FAIR, generative AI, GenAI) gave 15,229 current Meta profiles and 14,297 after the function filter.", "AI alone counts only in the current title. 4,003 draft profiles entered only through AI in the headline, where it is mostly a buzzword (AI-driven testing, cloud and AI platforms); in the first slice read, about half of them held AI roles.", "Research scientist, research engineer, and applied scientist are not AI terms. Matching is word by word, so research engineer also matched titles such as a software engineer in Reality Labs Research, and plain research titles at Meta also cover people research, survey science, software testing, photonics, materials, and physical modeling. With these titles admitted, reads in California and Washington found 75 to 82% in AI roles; without them, 92%. 2,180 profiles entered only through such a title and are left out; research scientists who name an AI term, FAIR, or the lab stay in.", "The employer must be the 10,001+ company. Outside the US the name Meta also matches small companies: 6 of 25 profiles in one slice outside the US worked at other firms whose names contain Meta, none of them sized 10,001+. The rule drops 845 draft profiles, most of them Meta work recorded under variant names or through staffing agencies, and a few that are not Meta at all.", "ML, LLMs, large language models, natural language processing, and reinforcement learning were added; together they bring 547 profiles the draft missed.", "Title words exclude marketing, sales, recruiting, and other non-technical roles whose current_function is missing or not in the excluded set (administrative, marketing, and sales roles in the reads)." ], "audit": "365 profiles read in whole slices, each a narrow filter read in full (one state or country and a range of total_experience_months), never the top of a search. The first slice (49 profiles of the draft) and three candidate slices (53) set the rules above. 150 profiles in eight whole slices fall in the final P2: 138 (92.0%) hold AI roles by their title, headline, and current job description. The last slice, 39 profiles read after the definition was fixed, gave 35 (89.7%) when two borderline creative and advisory roles count as misses. The misses are stale profiles that still list a current Meta job, generic engineers whose headline lists AI words, and a few operations roles. Contract data workers (prompt engineers, annotators, knowledge experts) who list Meta count as AI roles; they appear under data titles. No lab member with a non-technical function falls in the slices read. Records read for the audit are kept private.", "size_note": "The name Meta on a current entry gives 66,757 profiles in the US and more than 100,000 elsewhere, because outside the US it also matches other companies. With the employer size 10,001+ in the same entry the count is exact on both sides. A company's reported headcount is the comparison; visible profiles also include contractors and profiles not yet updated after someone left." }}
工作
第 5 部分,图 12、13、14
实验室和
12
实验室 35.1% 做研究,Meta 其他可见 AI 员工是 17.8%
当前
研究: 35.1% / 17.8% / 23.9%;工程: 37.3% / 58.0% / 49.1%;产品、设计与项目: 10.6% / 8.0% / 6.4%;数据: 3.2% / 6.3% / 4.1%;其他或未写明: 13.8% / 9.8% / 16.5%;专员或实习: 38.7% / 50.0%;资深: 16.5% / 13.5%;经理: 12.3% / 10.4%;负责人、总监及以上: 5.3% / 3.3%;未写明: 27.2% / 22.8%
图中所见
实验室 35.1% 做研究,37.3% 做工程;其他 AI 员工分别是 17.8% 和 58.0%。Meta 的 AI 岗位里,工程类职位占 49.1%,研究类职位占 23.9%。
层级上,实验室经理及以上占 17.6%,其他人是 13.7%;负责人、总监或更高是 5.3% 对 3.3%。
方法与局限
职能是平台对当前工作的固定分类;职能不是研究的人,职位名称是数据类的先归到数据。实验室约 4% 的人写的是非技术职能或职位,为了和第一阶段一致仍算在实验室里;实验室的"其他"和"未写明"合并成一格,这样第一阶段的格子减不出小群体。岗位按职位名称归类:研究科学家和研究工程师算研究,机器学习和软件工程师算工程。这个比较本身不对称:实验室的人只要写明实验室就算,其他人要写有 AI 词语才算,所以约 2,200 个没有 AI 词语的研究类职位不在其他人里。如果其中很多是 AI 岗位,其他人的研究比例会更高,差距会更小。
层级也是平台的固定分类,是按职称推出的可见层级,不是经过核实的汇报关系。实验室有 27.2%、其他人有 22.8% 没写层级。实验室的实习生和总监以上的人都不到 10 人,所以实习并入专员,负责人及以上合成一组。
来源:Metix AI Platform 个人档案与岗位数据,2026-09-22。
查询mapping.json (population, functions, levels, postings)
{ "population": { "id": "p2", "label": "Meta's visible AI staff", "note": "A current Meta entry (the stage-1 entry: experience.company.name match Meta and experience.is_current eq true), an AI term in the headline or current title, and three filters that apply to everyone except the lab. The lab's 936 people (queries/population.json) are all in P2 by construction, so the lab node is exactly the stage-1 population and no stage-2 count of the lab differs from a stage-1 count by a small group. Everyone else also needs a current Meta entry whose employer size is 10,001+, a current_function outside non_technical_functions, and a current title with none of non_technical_title_words.", "ai_terms": [ "machine learning", "ML", "deep learning", "computer vision", "NLP", "natural language processing", "LLM", "LLMs", "large language models", "reinforcement learning", "generative AI", "GenAI", "artificial intelligence", "superintelligence", "MSL", "FAIR" ], "ai_terms_fields": [ "headline", "current_title" ], "title_only_terms": [ "AI" ], "employer_size": "10,001+", "non_technical_functions": [ "Human Resources", "Sales", "Marketing", "Administrative", "Finance & Accounting", "Legal", "Customer Service", "Real Estate" ], "non_technical_title_words": [ "marketing", "sales", "recruiter", "recruiting", "sourcer", "sourcing", "talent", "administrative", "assistant", "counsel", "attorney", "paralegal", "accountant", "communications", "partnerships" ], "lab_note": "26 of the 936 list a non-technical function (recruiting and administration, mostly) and 12 more a non-technical title word. They stay in P2 as members of the lab, so the lab row carries them (about 4% of it) while the rest of P2 does not; the function table shows them among other functions.", "decisions": [ "The draft term list (machine learning, AI, artificial intelligence, research scientist, research engineer, applied scientist, deep learning, LLM, computer vision, NLP, superintelligence, MSL, FAIR, generative AI, GenAI) gave 15,229 current Meta profiles and 14,297 after the function filter.", "AI alone counts only in the current title. 4,003 draft profiles entered only through AI in the headline, where it is mostly a buzzword (AI-driven testing, cloud and AI platforms); in the first slice read, about half of them held AI roles.", "Research scientist, research engineer, and applied scientist are not AI terms. Matching is word by word, so research engineer also matched titles such as a software engineer in Reality Labs Research, and plain research titles at Meta also cover people research, survey science, software testing, photonics, materials, and physical modeling. With these titles admitted, reads in California and Washington found 75 to 82% in AI roles; without them, 92%. 2,180 profiles entered only through such a title and are left out; research scientists who name an AI term, FAIR, or the lab stay in.", "The employer must be the 10,001+ company. Outside the US the name Meta also matches small companies: 6 of 25 profiles in one slice outside the US worked at other firms whose names contain Meta, none of them sized 10,001+. The rule drops 845 draft profiles, most of them Meta work recorded under variant names or through staffing agencies, and a few that are not Meta at all.", "ML, LLMs, large language models, natural language processing, and reinforcement learning were added; together they bring 547 profiles the draft missed.", "Title words exclude marketing, sales, recruiting, and other non-technical roles whose current_function is missing or not in the excluded set (administrative, marketing, and sales roles in the reads)." ], "audit": "365 profiles read in whole slices, each a narrow filter read in full (one state or country and a range of total_experience_months), never the top of a search. The first slice (49 profiles of the draft) and three candidate slices (53) set the rules above. 150 profiles in eight whole slices fall in the final P2: 138 (92.0%) hold AI roles by their title, headline, and current job description. The last slice, 39 profiles read after the definition was fixed, gave 35 (89.7%) when two borderline creative and advisory roles count as misses. The misses are stale profiles that still list a current Meta job, generic engineers whose headline lists AI words, and a few operations roles. Contract data workers (prompt engineers, annotators, knowledge experts) who list Meta count as AI roles; they appear under data titles. No lab member with a non-technical function falls in the slices read. Records read for the audit are kept private.", "size_note": "The name Meta on a current entry gives 66,757 profiles in the US and more than 100,000 elsewhere, because outside the US it also matches other companies. With the employer size 10,001+ in the same entry the count is exact on both sides. A company's reported headcount is the comparison; visible profiles also include contractors and profiles not yet updated after someone left." }, "functions": { "note": "Five functions and none, exclusive, in this order: research (current_function Research), data (a data title and not Research), engineering (Engineering and Technical, no data title), product (Product, Design, or Project Management, no data title), other stated, none stated. The lab and the rest of P2 each add up to their total.", "data_title_words": [ "data", "annotation", "annotations", "annotator", "labeling", "labelling", "labeler", "prompt", "knowledge expert", "rater", "evaluator" ], "product_functions": [ "Product", "Design", "Project Management" ], "audit": "Data titles in the reads: data engineers and data scientists, annotators and data labeling analysts, prompt engineers, knowledge experts, and AI data quality reviewers, many of them contract workers. Several annotators carry the Research function, which is why research comes first and keeps them: the data row is a lower bound on data work.", "lab_rule": "The lab's functions are also published in stage 1 (data/roles.json). When a difference between a stage-1 cell and a stage-2 cell would be 1 to 9 people, the lab row merges other and none into one cell; if a difference is still 1 to 9, the run stops without writing." }, "levels": { "note": "current_seniority is counted in the groups below (Vice President and above is manager_up minus Manager, Head, and Director) and published in five: specialist-or-intern, senior, manager, head-and-above (Head, Director, and every level above), and none stated. The lab holds fewer than 10 interns and fewer than 10 above Director, and with the lab's manager_up published a reader could work out both, so Intern joins Specialist (as in stage 1) and the levels from Head up form one group. A visible hierarchy, not a reporting line.", "groups": [ { "id": "intern", "values": [ "Intern" ] }, { "id": "specialist", "values": [ "Specialist" ] }, { "id": "senior", "values": [ "Senior" ] }, { "id": "manager", "values": [ "Manager" ] }, { "id": "head-director", "values": [ "Head", "Director" ] }, { "id": "vp-up", "values": [ "Vice President", "President/Vice President", "C-Level", "Partner", "Founder", "Owner" ] } ], "individual_contributor": [ "Intern", "Specialist", "Senior" ], "published": [ "specialist-or-intern", "senior", "manager", "head-and-above", "none" ] }, "postings": { "note": "Meta postings (company.name match Meta; the jobs index has no employer size, so a few postings at other companies named Meta may be included) posted in the last 180 days (posted_date gte now-180d) whose title contains a P2 AI term or AI, and none of the non-technical title words. The index holds open postings only, and every one read was posted within three weeks of the snapshot, so this is the demand open on the day. A role posted in several cities counts once per city. Counts of postings carry no minimum.", "posted_from": "now-180d", "families": [ { "id": "research-scientist", "label": "Research scientist", "title": [ "research scientist" ] }, { "id": "research-engineer", "label": "Research engineer", "title": [ "research engineer" ] }, { "id": "ml-software-engineer", "label": "Machine learning or software engineer", "title": [ "software engineer", "machine learning engineer", "ML engineer", "AI engineer" ] }, { "id": "data", "label": "Data", "title": [ "data", "annotation", "annotator", "labeling", "prompt", "evaluator" ] }, { "id": "product-program", "label": "Product, program, and design", "title": [ "product manager", "product management", "program manager", "designer" ] } ], "families_note": "Exclusive, first match in this order; the rest are other (hardware, production, security, network, and leadership titles).", "audit": "91 read (see directions): 73 pass the title rule. Plain research scientist postings include demography and survey science, server demand forecasting, and infrastructure reliability, and AI in a title also names marketing and business development roles; the rule drops those. The 73 left are AI roles, a few of them borderline (security for AI, analytics for AI ranking, AI hardware bring-up). 90 of 91 state a range in USD." }}
13
其他 AI 员工中 24.2% 的职位是机器学习工程师,实验室是 3.8%
职位名称里含有
机器学习工程师: 3.8% / 24.2%;软件工程师: 24.4% / 20.5%;研究科学家: 25.3% / 10.4%;工程经理: 4.3% / 4.3%;总监: 5.6% / 2.3%;产品经理: 4.0% / 2.4%;研究工程师: 5.6% / 2.1%;数据科学家: 2.6% / 2.4%;项目经理: <1% / 2.3%;数据工程师: 1.5% / 1.1%
图中所见
实验室最常见的职位是研究科学家(25.3%)和软件工程师(24.4%);其他人里研究科学家是 10.4%。
方法与局限
职位名称含有候选词的全部单词就算,所以各行会重叠(Software Engineer, Machine Learning 两行都算)。候选词来自抽读档案里反复出现的职位,这里列出人数最多的十个。其他人不含没有 AI 词语的研究类职位(见图 12),这会抬高其中机器学习工程师的比例。
来源:Metix AI Platform 个人档案数据,2026-09-22。
查询mapping.json (population, titles)
{ "population": { "id": "p2", "label": "Meta's visible AI staff", "note": "A current Meta entry (the stage-1 entry: experience.company.name match Meta and experience.is_current eq true), an AI term in the headline or current title, and three filters that apply to everyone except the lab. The lab's 936 people (queries/population.json) are all in P2 by construction, so the lab node is exactly the stage-1 population and no stage-2 count of the lab differs from a stage-1 count by a small group. Everyone else also needs a current Meta entry whose employer size is 10,001+, a current_function outside non_technical_functions, and a current title with none of non_technical_title_words.", "ai_terms": [ "machine learning", "ML", "deep learning", "computer vision", "NLP", "natural language processing", "LLM", "LLMs", "large language models", "reinforcement learning", "generative AI", "GenAI", "artificial intelligence", "superintelligence", "MSL", "FAIR" ], "ai_terms_fields": [ "headline", "current_title" ], "title_only_terms": [ "AI" ], "employer_size": "10,001+", "non_technical_functions": [ "Human Resources", "Sales", "Marketing", "Administrative", "Finance & Accounting", "Legal", "Customer Service", "Real Estate" ], "non_technical_title_words": [ "marketing", "sales", "recruiter", "recruiting", "sourcer", "sourcing", "talent", "administrative", "assistant", "counsel", "attorney", "paralegal", "accountant", "communications", "partnerships" ], "lab_note": "26 of the 936 list a non-technical function (recruiting and administration, mostly) and 12 more a non-technical title word. They stay in P2 as members of the lab, so the lab row carries them (about 4% of it) while the rest of P2 does not; the function table shows them among other functions.", "decisions": [ "The draft term list (machine learning, AI, artificial intelligence, research scientist, research engineer, applied scientist, deep learning, LLM, computer vision, NLP, superintelligence, MSL, FAIR, generative AI, GenAI) gave 15,229 current Meta profiles and 14,297 after the function filter.", "AI alone counts only in the current title. 4,003 draft profiles entered only through AI in the headline, where it is mostly a buzzword (AI-driven testing, cloud and AI platforms); in the first slice read, about half of them held AI roles.", "Research scientist, research engineer, and applied scientist are not AI terms. Matching is word by word, so research engineer also matched titles such as a software engineer in Reality Labs Research, and plain research titles at Meta also cover people research, survey science, software testing, photonics, materials, and physical modeling. With these titles admitted, reads in California and Washington found 75 to 82% in AI roles; without them, 92%. 2,180 profiles entered only through such a title and are left out; research scientists who name an AI term, FAIR, or the lab stay in.", "The employer must be the 10,001+ company. Outside the US the name Meta also matches small companies: 6 of 25 profiles in one slice outside the US worked at other firms whose names contain Meta, none of them sized 10,001+. The rule drops 845 draft profiles, most of them Meta work recorded under variant names or through staffing agencies, and a few that are not Meta at all.", "ML, LLMs, large language models, natural language processing, and reinforcement learning were added; together they bring 547 profiles the draft missed.", "Title words exclude marketing, sales, recruiting, and other non-technical roles whose current_function is missing or not in the excluded set (administrative, marketing, and sales roles in the reads)." ], "audit": "365 profiles read in whole slices, each a narrow filter read in full (one state or country and a range of total_experience_months), never the top of a search. The first slice (49 profiles of the draft) and three candidate slices (53) set the rules above. 150 profiles in eight whole slices fall in the final P2: 138 (92.0%) hold AI roles by their title, headline, and current job description. The last slice, 39 profiles read after the definition was fixed, gave 35 (89.7%) when two borderline creative and advisory roles count as misses. The misses are stale profiles that still list a current Meta job, generic engineers whose headline lists AI words, and a few operations roles. Contract data workers (prompt engineers, annotators, knowledge experts) who list Meta count as AI roles; they appear under data titles. No lab member with a non-technical function falls in the slices read. Records read for the audit are kept private.", "size_note": "The name Meta on a current entry gives 66,757 profiles in the US and more than 100,000 elsewhere, because outside the US it also matches other companies. With the employer size 10,001+ in the same entry the count is exact on both sides. A company's reported headcount is the comparison; visible profiles also include contractors and profiles not yet updated after someone left." }, "titles": { "note": "Current titles that contain all the words of a candidate, in any order, so rows overlap: Software Engineer, Machine Learning counts under both software engineer and machine learning engineer. Candidates are the titles that recur in the audit reads; the ten with the most P2 profiles are published.", "candidates": [ "machine learning engineer", "software engineer", "research scientist", "research engineer", "engineering manager", "product manager", "program manager", "data scientist", "data engineer", "prompt engineer", "production engineer", "director" ], "publish": 10 }}
14
Meta 的 AI 岗位最常写排序与推荐、大语言模型和 AI 基础设施;实验室员工最偏向大语言模型
左边:写明该方向的员工,占各组的比例,
排序与推荐: 8.2% / 17.9%;岗位 46.3%。基础模型与大语言模型: 28.7% / 18.5%;岗位 35.8%。AI 基础设施: 13.1% / 15.5%;岗位 34.9%。Agent: 5.7% / 5.0%;岗位 17.4%。后训练与对齐: 8.8% / 6.4%;岗位 14.7%。多模态与感知: 15.9% / 12.8%;岗位 12.4%。AR、VR 与设备: 2.7% / 7.3%;岗位 6.4%。安全与评测: 4.2% / 3.6%;岗位 4.1%
图中所见
岗位写得最多的是排序与推荐(46.3%),然后是大语言模型(35.8%)和 AI 基础设施(34.9%)。员工里,实验室偏向基础模型与大语言模型(28.7%,其他人 18.5%),其他人更多是排序与推荐(17.9%,实验室 8.2%)。
方法与局限
一个人或一个岗位可以写多个方向。员工按个人资料标题、职位和技能匹配,岗位按职位名称和描述匹配。岗位描述比个人资料长,所以两边比的是顺序,不是高低。岗位是快照当天仍开放、近 180 天发布的 Meta 的 218 个 AI 岗位,同一个岗位在几个城市发布按城市各算一次;岗位数据没有雇主规模字段,所以可能包括少数其他名为 Meta 的公司的岗位。每个描述都有一段关于 AR 和 VR 的标准文字,所以描述只用有区分度的单词匹配。
来源:Metix AI Platform 个人档案与岗位数据,2026-09-22。
查询mapping.json (population, directions, postings)
{ "population": { "id": "p2", "label": "Meta's visible AI staff", "note": "A current Meta entry (the stage-1 entry: experience.company.name match Meta and experience.is_current eq true), an AI term in the headline or current title, and three filters that apply to everyone except the lab. The lab's 936 people (queries/population.json) are all in P2 by construction, so the lab node is exactly the stage-1 population and no stage-2 count of the lab differs from a stage-1 count by a small group. Everyone else also needs a current Meta entry whose employer size is 10,001+, a current_function outside non_technical_functions, and a current title with none of non_technical_title_words.", "ai_terms": [ "machine learning", "ML", "deep learning", "computer vision", "NLP", "natural language processing", "LLM", "LLMs", "large language models", "reinforcement learning", "generative AI", "GenAI", "artificial intelligence", "superintelligence", "MSL", "FAIR" ], "ai_terms_fields": [ "headline", "current_title" ], "title_only_terms": [ "AI" ], "employer_size": "10,001+", "non_technical_functions": [ "Human Resources", "Sales", "Marketing", "Administrative", "Finance & Accounting", "Legal", "Customer Service", "Real Estate" ], "non_technical_title_words": [ "marketing", "sales", "recruiter", "recruiting", "sourcer", "sourcing", "talent", "administrative", "assistant", "counsel", "attorney", "paralegal", "accountant", "communications", "partnerships" ], "lab_note": "26 of the 936 list a non-technical function (recruiting and administration, mostly) and 12 more a non-technical title word. They stay in P2 as members of the lab, so the lab row carries them (about 4% of it) while the rest of P2 does not; the function table shows them among other functions.", "decisions": [ "The draft term list (machine learning, AI, artificial intelligence, research scientist, research engineer, applied scientist, deep learning, LLM, computer vision, NLP, superintelligence, MSL, FAIR, generative AI, GenAI) gave 15,229 current Meta profiles and 14,297 after the function filter.", "AI alone counts only in the current title. 4,003 draft profiles entered only through AI in the headline, where it is mostly a buzzword (AI-driven testing, cloud and AI platforms); in the first slice read, about half of them held AI roles.", "Research scientist, research engineer, and applied scientist are not AI terms. Matching is word by word, so research engineer also matched titles such as a software engineer in Reality Labs Research, and plain research titles at Meta also cover people research, survey science, software testing, photonics, materials, and physical modeling. With these titles admitted, reads in California and Washington found 75 to 82% in AI roles; without them, 92%. 2,180 profiles entered only through such a title and are left out; research scientists who name an AI term, FAIR, or the lab stay in.", "The employer must be the 10,001+ company. Outside the US the name Meta also matches small companies: 6 of 25 profiles in one slice outside the US worked at other firms whose names contain Meta, none of them sized 10,001+. The rule drops 845 draft profiles, most of them Meta work recorded under variant names or through staffing agencies, and a few that are not Meta at all.", "ML, LLMs, large language models, natural language processing, and reinforcement learning were added; together they bring 547 profiles the draft missed.", "Title words exclude marketing, sales, recruiting, and other non-technical roles whose current_function is missing or not in the excluded set (administrative, marketing, and sales roles in the reads)." ], "audit": "365 profiles read in whole slices, each a narrow filter read in full (one state or country and a range of total_experience_months), never the top of a search. The first slice (49 profiles of the draft) and three candidate slices (53) set the rules above. 150 profiles in eight whole slices fall in the final P2: 138 (92.0%) hold AI roles by their title, headline, and current job description. The last slice, 39 profiles read after the definition was fixed, gave 35 (89.7%) when two borderline creative and advisory roles count as misses. The misses are stale profiles that still list a current Meta job, generic engineers whose headline lists AI words, and a few operations roles. Contract data workers (prompt engineers, annotators, knowledge experts) who list Meta count as AI roles; they appear under data titles. No lab member with a non-technical function falls in the slices read. Records read for the audit are kept private.", "size_note": "The name Meta on a current entry gives 66,757 profiles in the US and more than 100,000 elsewhere, because outside the US it also matches other companies. With the employer size 10,001+ in the same entry the count is exact on both sides. A company's reported headcount is the comparison; visible profiles also include contractors and profiles not yet updated after someone left." }, "directions": { "note": "Multi-label. Stock: P2 profiles whose headline or current title contains a phrase, or whose skills contain a single word, of the direction. Flow: Meta AI postings (postings below) whose title contains a phrase or whose description contains a single word. Long fields (skills lists, descriptions) take single distinctive words only, because a phrase matches its words anywhere in the text.", "list": [ { "id": "foundation-models", "label": "Foundation models and LLMs", "phrase": [ "LLM", "LLMs", "large language model", "large language models", "foundation model", "foundation models", "language model", "language models", "pre-training", "pretraining", "Llama" ], "word": [ "LLM", "LLMs", "pretraining", "Llama" ] }, { "id": "post-training", "label": "Post-training and alignment", "phrase": [ "post-training", "post training", "RLHF", "reinforcement learning", "fine-tuning", "alignment" ], "word": [ "RLHF", "RLVR", "reinforcement" ] }, { "id": "multimodal-perception", "label": "Multimodal and perception", "phrase": [ "computer vision", "vision", "multimodal", "speech", "video", "image", "perception", "3D", "VLM" ], "word": [ "multimodal", "VLM", "VLMs", "speech" ] }, { "id": "ai-infrastructure", "label": "AI infrastructure", "phrase": [ "infra", "infrastructure", "GPU", "GPUs", "CUDA", "inference", "compiler", "compilers", "accelerator", "accelerators", "kernels", "distributed training", "systems ML", "SystemML", "HPC", "MTIA", "PyTorch" ], "word": [ "GPU", "GPUs", "CUDA", "compiler", "compilers", "accelerator", "accelerators", "kernels", "MTIA", "HPC" ] }, { "id": "agents", "label": "Agents", "phrase": [ "agent", "agents", "agentic" ], "word": [ "agentic", "agents" ] }, { "id": "ranking-recommendations", "label": "Ranking and recommendations", "phrase": [ "ranking", "recommendation", "recommendations", "recommender", "recsys" ], "word": [ "ranking", "recommendation", "recommender", "recsys" ] }, { "id": "ar-vr-devices", "label": "AR, VR, and devices", "phrase": [ "AR", "VR", "XR", "augmented reality", "virtual reality", "mixed reality", "wearables", "smart glasses", "Reality Labs", "Oculus" ], "word": [ "wearables", "XR", "glasses" ] }, { "id": "safety-evaluation", "label": "Safety and evaluation", "phrase": [ "safety", "evaluation", "evals", "red teaming", "responsible AI" ], "word": [ "evals", "teaming" ] } ], "audit": "91 postings read in two whole slices (every Meta AI-titled posting of the last 180 days in New York, 30, and in Menlo Park, 61). Every description carries Meta's standard paragraph on augmented and virtual reality, and 59 of 91 mention responsible AI, so those phrases would match nearly every posting. Alignment appears mostly as stakeholder alignment, post-training also matches post-silicon in accelerator postings that mention training, inference also means causal inference, and computer vision matches any description with Computer Science and vision. Hence single distinctive words for descriptions; with them the matches read as the direction, except agents, which one security posting uses for its own tooling. In skills, safety mostly meant workplace safety and perception included brand perception, so neither is a skill word." }, "postings": { "note": "Meta postings (company.name match Meta; the jobs index has no employer size, so a few postings at other companies named Meta may be included) posted in the last 180 days (posted_date gte now-180d) whose title contains a P2 AI term or AI, and none of the non-technical title words. The index holds open postings only, and every one read was posted within three weeks of the snapshot, so this is the demand open on the day. A role posted in several cities counts once per city. Counts of postings carry no minimum.", "posted_from": "now-180d", "families": [ { "id": "research-scientist", "label": "Research scientist", "title": [ "research scientist" ] }, { "id": "research-engineer", "label": "Research engineer", "title": [ "research engineer" ] }, { "id": "ml-software-engineer", "label": "Machine learning or software engineer", "title": [ "software engineer", "machine learning engineer", "ML engineer", "AI engineer" ] }, { "id": "data", "label": "Data", "title": [ "data", "annotation", "annotator", "labeling", "prompt", "evaluator" ] }, { "id": "product-program", "label": "Product, program, and design", "title": [ "product manager", "product management", "program manager", "designer" ] } ], "families_note": "Exclusive, first match in this order; the rest are other (hardware, production, security, network, and leadership titles).", "audit": "91 read (see directions): 73 pass the title rule. Plain research scientist postings include demography and survey science, server demand forecasting, and infrastructure reliability, and AI in a title also names marketing and business development roles; the rule drops those. The 73 left are AI roles, a few of them borderline (security for AI, analytics for AI ranking, AI hardware bring-up). 90 of 91 state a range in USD." }}
流入与流出
第 6 部分,图 15、16、17
他们
15
实验室在 Google 工作过的比例更高(14.2% 对 8.3%);中国大陆本科的比例和其他人一样,约 20%
以前
Google(含 Google DeepMind): 14.2% / 8.3%;Amazon: 11.8% / 10.2%;Microsoft: 9.8% / 7.7%;Apple: 3.8% / 3.0%;字节跳动或 TikTok: 1.7% / 2.3%;OpenAI: 1.3% / 0.3%;NVIDIA: 1.1% / 0.7%;加州大学伯克利分校: 5.7% / 3.9%;卡内基梅隆大学: 5.4% / 3.8%;斯坦福大学: 5.1% / 3.9%;印度理工学院: 4.5% / 3.9%;伊利诺伊大学厄巴纳-香槟分校: 3.3% / 2.4%;麻省理工学院: 2.4% / 1.3%;中国大陆本科(占写有本科者): 19.8% / 19.6%;其中:个人贡献者: · / 21.8%;其中:经理及以上: · / 15.6%
图中所见
实验室在卡内基梅隆和伯克利读过书的比例(5.4% 和 5.7%,其他人是 3.8% 和 3.9%)也更高;斯坦福的差距在随机波动范围内。其他 AI 员工里,个人贡献者中大陆本科的比例是 21.8%,经理及以上是 15.6%。
方法与局限
以前工作过指在那里有过一段不是实习的工作;学校指任何学位;各行会重叠。中国大陆本科沿用中国教育背景研究的院校清单。实验室按层级拆分达不到每格 20 人的门槛,所以不公开("·")。Anthropic 没列出:实验室里没有人,其他人里不到 10 人。
来源:Metix AI Platform 个人档案数据,2026-09-22。
查询mapping.json (population, sources, china_educated)
{ "population": { "id": "p2", "label": "Meta's visible AI staff", "note": "A current Meta entry (the stage-1 entry: experience.company.name match Meta and experience.is_current eq true), an AI term in the headline or current title, and three filters that apply to everyone except the lab. The lab's 936 people (queries/population.json) are all in P2 by construction, so the lab node is exactly the stage-1 population and no stage-2 count of the lab differs from a stage-1 count by a small group. Everyone else also needs a current Meta entry whose employer size is 10,001+, a current_function outside non_technical_functions, and a current title with none of non_technical_title_words.", "ai_terms": [ "machine learning", "ML", "deep learning", "computer vision", "NLP", "natural language processing", "LLM", "LLMs", "large language models", "reinforcement learning", "generative AI", "GenAI", "artificial intelligence", "superintelligence", "MSL", "FAIR" ], "ai_terms_fields": [ "headline", "current_title" ], "title_only_terms": [ "AI" ], "employer_size": "10,001+", "non_technical_functions": [ "Human Resources", "Sales", "Marketing", "Administrative", "Finance & Accounting", "Legal", "Customer Service", "Real Estate" ], "non_technical_title_words": [ "marketing", "sales", "recruiter", "recruiting", "sourcer", "sourcing", "talent", "administrative", "assistant", "counsel", "attorney", "paralegal", "accountant", "communications", "partnerships" ], "lab_note": "26 of the 936 list a non-technical function (recruiting and administration, mostly) and 12 more a non-technical title word. They stay in P2 as members of the lab, so the lab row carries them (about 4% of it) while the rest of P2 does not; the function table shows them among other functions.", "decisions": [ "The draft term list (machine learning, AI, artificial intelligence, research scientist, research engineer, applied scientist, deep learning, LLM, computer vision, NLP, superintelligence, MSL, FAIR, generative AI, GenAI) gave 15,229 current Meta profiles and 14,297 after the function filter.", "AI alone counts only in the current title. 4,003 draft profiles entered only through AI in the headline, where it is mostly a buzzword (AI-driven testing, cloud and AI platforms); in the first slice read, about half of them held AI roles.", "Research scientist, research engineer, and applied scientist are not AI terms. Matching is word by word, so research engineer also matched titles such as a software engineer in Reality Labs Research, and plain research titles at Meta also cover people research, survey science, software testing, photonics, materials, and physical modeling. With these titles admitted, reads in California and Washington found 75 to 82% in AI roles; without them, 92%. 2,180 profiles entered only through such a title and are left out; research scientists who name an AI term, FAIR, or the lab stay in.", "The employer must be the 10,001+ company. Outside the US the name Meta also matches small companies: 6 of 25 profiles in one slice outside the US worked at other firms whose names contain Meta, none of them sized 10,001+. The rule drops 845 draft profiles, most of them Meta work recorded under variant names or through staffing agencies, and a few that are not Meta at all.", "ML, LLMs, large language models, natural language processing, and reinforcement learning were added; together they bring 547 profiles the draft missed.", "Title words exclude marketing, sales, recruiting, and other non-technical roles whose current_function is missing or not in the excluded set (administrative, marketing, and sales roles in the reads)." ], "audit": "365 profiles read in whole slices, each a narrow filter read in full (one state or country and a range of total_experience_months), never the top of a search. The first slice (49 profiles of the draft) and three candidate slices (53) set the rules above. 150 profiles in eight whole slices fall in the final P2: 138 (92.0%) hold AI roles by their title, headline, and current job description. The last slice, 39 profiles read after the definition was fixed, gave 35 (89.7%) when two borderline creative and advisory roles count as misses. The misses are stale profiles that still list a current Meta job, generic engineers whose headline lists AI words, and a few operations roles. Contract data workers (prompt engineers, annotators, knowledge experts) who list Meta count as AI roles; they appear under data titles. No lab member with a non-technical function falls in the slices read. Records read for the audit are kept private.", "size_note": "The name Meta on a current entry gives 66,757 profiles in the US and more than 100,000 elsewhere, because outside the US it also matches other companies. With the employer size 10,001+ in the same entry the count is exact on both sides. A company's reported headcount is the comparison; visible profiles also include contractors and profiles not yet updated after someone left." }, "sources": { "employers_note": "Anyone with a past (not current) non-intern job at the employer, at any time, for the lab and the rest of P2; rows overlap. The first six are the stage-1 ever-worked-at rows, with the same definitions, so the lab's counts equal data/sources.json.", "employers": [ { "id": "google", "label": "Google, including Google DeepMind", "names": [ "Google", "DeepMind" ] }, { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ] }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ] }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] }, { "id": "nvidia", "label": "NVIDIA", "names": [ "NVIDIA" ] }, { "id": "bytedance", "label": "ByteDance or TikTok", "names": [ "ByteDance", "TikTok" ] } ], "schools_note": "Any education entry at the school, any degree; rows overlap.", "schools": [ { "id": "stanford", "label": "Stanford University", "names": [ "Stanford" ] }, { "id": "carnegie-mellon", "label": "Carnegie Mellon University", "names": [ "Carnegie Mellon" ] }, { "id": "berkeley", "label": "University of California, Berkeley", "names": [ "Berkeley" ] }, { "id": "mit", "label": "Massachusetts Institute of Technology", "names": [ "Massachusetts Institute of Technology" ] }, { "id": "uiuc", "label": "University of Illinois Urbana-Champaign", "names": [ "Urbana" ] }, { "id": "iit", "label": "Indian Institutes of Technology", "names": [ "Indian Institute of Technology" ] } ] }, "china_educated": { "institutions_file": "cases/china-educated-ai-talent-2026/queries/institutions.json", "note": "China-educated means a Bachelor entry that names an institution on the China-educated study's mainland list (its match and exact names, none of its exclude words), read from that file. The query sends the match and exact names in one in leaf and the exclude words in another; on P2 it gives the same 1,227 profiles as the study's own form with one match leaf per name. The share is of people with any Bachelor entry.", "level_gate_count": 20, "level_note": "By level (individual contributors, that is Intern, Specialist, and Senior, against manager and above) only where all four cells of a group (China-educated and Bachelor-listed, at each level) hold 20 or more." }}
16
2025 年 6 月以来,191 人离开 Meta 去了 OpenAI,从那里加入的是 37 人;从 Amazon 加入的有 691 人
2025 年
OpenAI:离开 191,加入 37;Anthropic:离开 81,加入 <10;Google DeepMind:离开 58,加入 41;xAI:离开 33,加入 11;Thinking Machines Lab:离开 16,加入 <10;Amazon:离开 153,加入 691;Microsoft:离开 154,加入 343;Google(DeepMind 以外):离开 308,加入 317;Apple:离开 134,加入 158;NVIDIA:离开 82,加入 20
图中所见
379 人离开 Meta 去了五家 AI 实验室,从那里加入的最多 107 人。和 Amazon、Microsoft 和 Apple 之间则相反,加入的多于离开的:从 Amazon 加入 691 人、离开去 Amazon 153 人,从 Microsoft 加入 343 人、离开 154 人。NVIDIA 是例外:离开去 NVIDIA 的有 82 人,从那里加入的是 20 人。Google(DeepMind 以外):两个方向相当(加入 317 人、离开 308 人)。算上所有雇主,离开 8,054 人,加入 7,787 人。
方法与局限
新工作开始于 2025 年 6 月 1 日或以后、上一份工作在 2025 年 5 月 1 日或以后结束,才算一次换工作,不算实习;包括 Meta 的所有岗位,不只是 AI 岗位。去 AI 实验室的人大多职位里没有 AI 字样,这和这些实验室常用 Member of Technical Staff 的职称一致。档案日期截至 2026 年 4 月,之后的变动(包括 2026 年 5 月的裁员)都不在内;2025 年 10 月 Meta 在 AI 团队裁减 600 多个职位,这些人要等下一份工作出现在档案里才算。"<10" 画成可能的最大值处的空框。
来源:Metix AI Platform 个人档案数据,2026-09-22。
查询mapping.json (flows)
{ "flows": { "note": "Moves since 2025-06-01, with symmetric windows, non-intern entries only. Meta is the same employer as in P2: the name Meta with employer size 10,001+, since outside the US the name alone also matches other companies; Facebook, Instagram, WhatsApp, and Oculus entries count by name. Out to X: a current entry at X that started on or after 2025-06-01, a Meta entry that ended on or after 2025-05-01, and no current entry under the name Meta at any size, so a current Meta job whose entry lacks a size never counts as a move away. In from X: a current Meta entry that started on or after 2025-06-01, an entry at X that ended on or after 2025-05-01, and no current entry at X. All movers: the same with any employer outside the Meta names. The AI-titled subset adds the P2 AI terms in the headline or current title, and is counted only where the row holds 10 or more. Rows by employer can overlap.", "start_from": "2025-06-01", "ended_from": "2025-05-01", "peers": [ { "id": "openai", "label": "OpenAI", "names": [ "OpenAI" ] }, { "id": "google-deepmind", "label": "Google DeepMind", "names": [ "DeepMind" ] }, { "id": "anthropic", "label": "Anthropic", "names": [ "Anthropic" ] }, { "id": "xai", "label": "xAI", "names": [ "xAI" ] }, { "id": "thinking-machines", "label": "Thinking Machines Lab", "names": [ "Thinking Machines" ] }, { "id": "microsoft", "label": "Microsoft", "names": [ "Microsoft" ] }, { "id": "apple", "label": "Apple", "names": [ "Apple" ] }, { "id": "amazon", "label": "Amazon", "names": [ "Amazon", "AWS" ] }, { "id": "nvidia", "label": "NVIDIA", "names": [ "NVIDIA" ] }, { "id": "google", "label": "Google, other than Google DeepMind", "names": [ "Google" ], "exclude": [ "DeepMind" ] } ], "limits": "Profiles lag: start dates stop in April 2026, so a move needs a new entry by then to count, and the most recent months are undercounted. Meta cut more than 600 roles in its AI organization in October 2025 (SiliconANGLE, 2025-10-22, https://siliconangle.com/2025/10/22/meta-lays-off-600-ai-workers-looks-streamline-superintelligence-labs/); people who left then count as out-movers only once their next job appears. An entry whose date gives only a year reads as January of that year." }}
17
Meta AI 岗位写明的底薪上限,中位数在 25 万到 29.5 万美元之间
美国
全部 AI 岗位 (197): 21.5 万以下 18, 21.5 万到 25 万 59, 25 万到 29.5 万 75, 29.5 万到 34 万 37, 34 万及以上 8;研究科学家 (33): 21.5 万以下 3, 21.5 万到 25 万 12, 25 万到 29.5 万 13, 29.5 万到 34 万 3, 34 万及以上 2;机器学习或软件工程师 (99): 21.5 万以下 8, 21.5 万到 25 万 24, 25 万到 29.5 万 41, 29.5 万到 34 万 22, 34 万及以上 4
图中所见
写明底薪的 197 个美国 AI 岗位里,区间下限的中位数在 18 万到 21.5 万美元之间,上限的中位数在 25 万到 29.5 万美元之间。研究科学家岗位的上限并不更高:54.5% 达到 25 万美元 或以上,机器学习和软件工程师岗位是 67.7%。
方法与局限
只算美国、以美元计、写明上下限的岗位;只是岗位写明的底薪,不含奖金、股票和福利,也不说明任何人实际拿多少。一类岗位至少有 15 个才公开,研究工程师(12 个)不公开。
来源:Metix AI Platform 岗位数据,2026-09-22。
查询mapping.json (postings, pay)
{ "postings": { "note": "Meta postings (company.name match Meta; the jobs index has no employer size, so a few postings at other companies named Meta may be included) posted in the last 180 days (posted_date gte now-180d) whose title contains a P2 AI term or AI, and none of the non-technical title words. The index holds open postings only, and every one read was posted within three weeks of the snapshot, so this is the demand open on the day. A role posted in several cities counts once per city. Counts of postings carry no minimum.", "posted_from": "now-180d", "families": [ { "id": "research-scientist", "label": "Research scientist", "title": [ "research scientist" ] }, { "id": "research-engineer", "label": "Research engineer", "title": [ "research engineer" ] }, { "id": "ml-software-engineer", "label": "Machine learning or software engineer", "title": [ "software engineer", "machine learning engineer", "ML engineer", "AI engineer" ] }, { "id": "data", "label": "Data", "title": [ "data", "annotation", "annotator", "labeling", "prompt", "evaluator" ] }, { "id": "product-program", "label": "Product, program, and design", "title": [ "product manager", "product management", "program manager", "designer" ] } ], "families_note": "Exclusive, first match in this order; the rest are other (hardware, production, security, network, and leadership titles).", "audit": "91 read (see directions): 73 pass the title rule. Plain research scientist postings include demography and survey science, server demand forecasting, and infrastructure reliability, and AI in a title also names marketing and business development roles; the rule drops those. The 73 left are AI roles, a few of them borderline (security for AI, analytics for AI ranking, AI hardware bring-up). 90 of 91 state a range in USD." }, "pay": { "note": "US postings (location.country eq United States) in USD that state both salary.annual_min and salary.annual_max, by family. A family is published only with 15 or more such postings. Counts at thresholds describe the posted base range; bonus, equity, and benefits are not in these figures, and no statistic describes what anyone is paid.", "gate_count": 15, "annual_min_thresholds": [ 150000, 180000, 215000, 265000 ], "annual_max_thresholds": [ 215000, 250000, 295000, 340000 ], "thresholds_note": "Meta's posted ranges fall on a few fixed bands (for example 122,000 to 181,000, 154,000 to 217,000, 184,000 to 257,000, 219,000 to 301,000, and 271,000 to 347,000 in the reads), so these thresholds separate the bands." }}
运行这个案例
三种方式,每一种都先告诉你要花多少。
1 API Credit 可以买 25 个搜索结果或 5 条完整记录;1 美元可以买 30 API Credits。
交给你的 agent 来跑
500 到 600 API Credits16.67 到 20.00 美元超过新账户赠送的 100 API Credits
花费超过 650 API Credits 之前,agent 会先停下来问你。
你的 agent 按提示词一步步执行:先读规则,再计数,按提示词的要求检查定义,最后写出文件和图表。请使用能写文件的 agent,比如 Claude Code 或 Codex。
一次性配置key、连接和一次免费检查。如果你的 agent 已经接入 Metix AI Platform,可以跳过。
1获取 key
在 Metix AI Platform 上创建 key →新账户一次性赠送 100 API Credits,30 天内有效。在启动 agent 的终端里设置,或者把这一行写进 ~/.zshrc 或 ~/.bashrc,新开的终端也能用:
终端export METIX_KEY=metix_xxxxxxxx
2连接你的 agent
Claude Code
为所有项目注册 Metix AI Platform。在任意目录启动 claude,就能看到十个 metix 工具。
MCP 配置指南 →终端: "${METIX_KEY:?run step 1 first}" && claude mcp add --scope user --transport http metix \ https://mira-api.metix.ai/mcp \ --header "Authorization: Bearer $METIX_KEY"Codex
注册同一个服务。key 留在环境变量里,不写进配置文件。
MCP 配置指南 →终端codex mcp add metix \ --url https://mira-api.metix.ai/mcp \ --bearer-token-env-var METIX_KEY
Skills
四个 skill,教任何 agent 使用 Metix AI Platform 的接口和查询规则,适合不支持 MCP 的 agent。安装程序默认一项都不勾选:在每一项上按空格,再按回车。
Skills 安装说明 →终端npx skills add MetixAI-Official/metix-skills
其他 MCP
让客户端通过 streamable HTTP 连接这个地址,并带上这两个请求头;缺少 Accept 请求头时服务器会返回 406。较旧的客户端使用同一主机上的 /sse。
MCP 配置指南 →地址和请求头https://mira-api.metix.ai/mcp Authorization: Bearer <your key> Accept: application/json, text/event-stream
3检查配置
先问这一句。它只读取余额和字段列表,不做任何搜索,不花 API Credits:
发给 agent 的提示使用 Metix AI Platform:查询我的 key 状态并读取 contract,这两项都免费。然后告诉我我的 API Credit 余额和可以查询哪些数据集。不要做任何搜索。
4粘贴提示词
在一个空文件夹里启动 agent,再粘贴。它会把文件写在那里。
要回答的问题
用 Metix AI Platform 回答两个问题:在公开资料中写明自己属于 Meta Superintelligence Labs 的人里,有多少人在 2025 年 6 月实验室成立时已经在 Meta 工作?其余的人是从哪里来的?另外,Meta 可见的 AI 人员分布在哪些部门,这个实验室在其中处于什么位置?只通过公开的 Platform 访问(REST 地址 https://mira-api.metix.ai、MCP 服务或 metix-skills),密钥从 METIX_KEY 读取,任何时候都不要打印密钥。
01先读规则再查询
调用 GET /contract(免费),所有条件只用 querySpecByEntity.profile 和 querySpecByEntity.job 里的字段;再读 GET /docs/api/people(免费)。描述同一份工作的条件要放在同一个 has_experience 里,才能保证说的是同一份工作。文本字段按词匹配,顺序不限,不分大小写;current_function、current_seniority、experience.seniority 和 experience.company.type 只取固定值,用 eq 或 in。一次查询最多 64 个条件,嵌套最多 6 层。size 1 的计数花 1 API Credit,查不到任何人时不收费;搜索每返回 25 个 ID 花 1 API Credit,读取详情每 5 条记录花 1 API Credit,所以每个要发布的数字都按计数来设计。每个查询先加一个什么也匹配不到的词发一次:Platform 会按限制检查查询,结果为空不收费。开始和结束时各调用一次 GET /auth/key/status(免费)查余额,总花费超过 650 API Credits 之前先停下来问我。
02范围
当前在 Meta 工作(experience.company.name match "Meta" 且 experience.is_current eq true,放在同一个 has_experience 里),并且 headline 或 current_title 匹配 superintelligence 或 MSL。用计数确认 company.name eq "Meta" 得到同样的总数,说明这个名字没有匹配到别的公司;再确认 Facebook 在 Platform 上就是同一个雇主,不能当作单独的检验。以前在 Meta 的工作,指雇主名为 Meta、Facebook、Instagram、WhatsApp 或 Oculus 的经历。实习指 experience.seniority eq "Intern" 或 experience.title 匹配 intern 的经历,在同一条经历里判断。另外统计较窄的定义(只写 superintelligence),并作为背景统计写了 FAIR 却没写实验室名称的 Meta 在职资料。
03先核对再计数
搜索结果按匹配程度排序,只看最前面会让这个群体显得比实际更干净。所以要读完整的切片:size 25 的搜索花 1 API Credit,同时返回总数,25 人以内的切片会完整返回。分五个切片读约 60 份资料(某个州里 2025 年 6 月前没有 Meta 经历的人,两个城市里有这类经历的人,Meta 经历没有开始日期的人,某个州里写 MSL 但没写 superintelligence 的人),用 POST /entity/v1/profiles/detail-by-id,_source 只取 headline、current_title、current_function 和经历里的 company.name、title、start_date、end_date、is_current、seniority,不取姓名。报告其中有多少人写的是在这个实验室工作,确认老员工以前在 Meta 有正式工作而不只是实习,并找出名单漏掉的 Meta 公司名称。子团队的每个词、Microsoft 群体的一个完整切片和所有在招职位,都用同样的方法读。读到的记录不能出现在任何公开文件里。
04分组
分界日期是 2025-06-01。统计总数;以前在 Meta 有经历、且开始于分界日期之前的人;去掉实习后的同一个数;以及留任的人:有一条非实习的 Meta 经历开始于分界日期之前,并且仍在进行或 experience.end_date gte "2025-05-01"(这两个条件用 any 放在同一条经历里)。回流的人等于非实习的数减去留任的数,前实习生等于第一个数减去非实习的数,新加入 Meta 的人等于总数减去第一个数;后三组合起来是外部招聘。较窄的定义也统计总数、以前的经历和留任三个数;写 superintelligence 的 Microsoft 在职资料统计四组,分界日期 2025-11-01,结束日期 2025-10-01。
05日期
统计以前的 Meta 经历开始于以下每个日期之前的人数:2012-01-01、2014-01-01、2016-01-01、2018-01-01、2020-01-01、2022-01-01、2023-01-01、2024-01-01、2025-01-01、分界日期、2025-07-01、2025-08-01、2025-09-01、2025-10-01、2026-01-01 和 2026-04-01;相邻两个日期的差就是一段首次加入的时间。去掉实习再做一遍,做到分界日期为止。对留任的人,统计当前 Meta 经历开始于以下每个日期当天或之后的人数:2025-01-01、2025-04-01、2025-06-01、2025-07-01、2025-08-01、2025-09-01、2025-10-01、2026-01-01 和 2026-04-01,这样每个人按最新的职位归入一段。Microsoft 统计 2012、2016、2020、2023、2025-01-01 和它的分界日期之前的人数。个人资料的更新有滞后,所以要按开始月份统计所有资料里的 Meta 经历,说明最后一个完整的月份是哪个月。
06来源
对外部招聘的人(范围内、不属于留任的人),统计一条 experience.end_date gte "2025-01-01" 的非实习经历,雇主依次为:OpenAI、DeepMind、Anthropic、xAI、Thinking Machines、Apple、Scale AI、Google、Microsoft、Amazon 或 AWS、NVIDIA;最后是 experience.company.type eq "Educational",这一行实习也算。每一行都排除前面各行已经匹配到的人,剩下的算作其他雇主或没有。对整个群体,统计以前在 Google 或 DeepMind、OpenAI、Anthropic、Apple、Microsoft、Amazon 或 AWS 有过非实习工作的人;这些行会重叠。
07岗位、团队、地点和职位
对整个群体和外部招聘的人,分别统计 current_function eq Research、Engineering and Technical、Product,以及 current_function exists。对当前职能是 Research 的人,在实验室里和作为基准的其他 Meta 研究人员里(当前在 Meta、职能是 Research、没写实验室名称),分别统计 current_seniority 为 Senior、为 Manager 或更高级别、有级别,以及有 Doctorate 学历的人;整个群体和外部招聘的人也统计博士。统计 headline 或 title 里提到 FAIR、TBD、infra 或 infrastructure、PAR 或 product applied research 的人。统计 location.country 为 United States,location.state 为 California、New York、Washington,加州境内的湾区城市,以及 United Kingdom。对 Meta 在招职位(is_open eq true、company.name match "Meta",并且标题匹配 superintelligence 或 MSL,或者描述匹配 superintelligence labs),统计总数、标题带 research 的职位、Menlo Park、San Francisco、New York、写明 min_experience_months 的职位和其中不超过 36 个月的职位、资历标签、2026-09-01 以来发布的职位,以及 Meta 全部在招职位。
08输出
写出汇总文件,每个都带 "unit"("profiles" 或 "jobs")、快照日期和来源查询文件。每个 1 到 9 人的计数都写成 "<10"。一段日期如果只有 1 到 9 人,就和相邻的一段合并,但不能跨过分界日期。某个公开的合计里,隐藏的格子加起来如果是 1 到 9 人,就再隐藏一个格子。较窄的定义和 Microsoft 群体只分到公开的计数之间每个差值都是 0 或至少 10 的程度。分母不少于 30 才发布比例。写任何文件之前,检查读者能算出的每个差值;写出的任何文字里都不写个人姓名,包括新闻里点名的人;链接新闻报道可以。
09图表
首次加入的各段画成时间线,标出分界日期,后面是新加入 Meta 的人按月的分布,Microsoft 画在同一条时间轴上;四组画成一根条形,较窄的定义和 Microsoft 放在下面;外部招聘的人按刚离开的雇主分组,五家 AI 实验室放在一起;留任的人和外部招聘的人的当前职能;实验室研究人员与基准的博士比例和级别;子团队的提及;各州;在招职位的地点。数值直接标在条上,每张图的标题用中性、客观的措辞写出结论。
10局限
这个范围是主动写明实验室的人,不等于实验室本身:只写 FAIR 或什么都没写的人不在其中,新加入的人和老员工写明的比例也可能不同。计数是可见的资料,不是员工人数;过时的资料也算作在职,所以也不保证是下限。有些资料已经过时,最近几个月的数字偏少。只写年份的日期按 1 月算,会把一些人移到分界的另一边,要说明是哪个方向。新增一条 Meta 经历只是调岗人数的下限,很多团队调动不会新增经历。来源依据的是经历的结束日期。Microsoft 群体规模小,还包括招聘人员。在招职位只是某一天的情况。用中性的动词(加入、离开、调动、招聘),除第 17 步职位里写明的基本薪资范围外,不涉及薪酬。
11版图的范围
Meta 可见的 AI 人员(P2)指有第一部分那条 Meta 在职经历、并且 headline 或 current_title 写有 AI 词的人:machine learning、ML、deep learning、computer vision、NLP、natural language processing、LLM、LLMs、large language models、reinforcement learning、generative AI、GenAI、artificial intelligence、superintelligence、MSL 或 FAIR;单独的 AI 只在 current_title 里算。实验室以外的人还要满足三个条件:在同一个 has_experience 里有一条 experience.company.size eq "10,001+" 的 Meta 在职经历;current_function 不是 Human Resources、Sales、Marketing、Administrative、Finance & Accounting、Legal、Customer Service 或 Real Estate;当前职位里没有 marketing、sales、recruiter、recruiting、sourcer、sourcing、talent、administrative、assistant、counsel、attorney、paralegal、accountant、communications 或 partnerships。把这三个条件各自和两个实验室名称条件放进同一个 any,这样第一部分的实验室成员全部留在 P2 里,两部分说的是同一群人。文本字段的词表用 in 发送:效果和每个词一个 match 条件相同,还能让每个查询保持在 64 个条件以内。
12核对版图
按 P2 的完整切片读至少 100 份资料(一个州或国家加一小段 total_experience_months,匹配到的全部读完),只取 headline、current_title、current_function、summary,以及当前经历的职位、描述、公司名称和规模,不取姓名,报告其中做 AI 工作的比例,必须达到 90%。确定词表之前,先检验读取中发现的陷阱:headline 里单独的 AI 多半是流行词;research scientist 和 research engineer 按词匹配,会把人员研究、调查科学、光子学,以及 Reality Labs Research 的软件工程师都算进来;在美国以外,Meta 这个名字还会匹配到别的公司。部门词(GenAI、generative AI、AR 和 VR 相关词、infra)也各读一个完整切片,据此判断每个词指的是团队还是话题,以及部门的先后顺序。
13部门和规模
统计美国的 Meta 在职资料数,以及规模为 10,001+ 的 Meta 在职经历在美国和美国以外各有多少,这样没有一个计数会变成 100000+。把 P2 的每个人归到 headline 或 current_title 里第一个出现的部门,顺序如下:实验室(superintelligence、MSL);FAIR;Reality Labs,加上 AR、VR、XR、augmented reality、virtual reality、mixed reality、wearables、smart glasses 和 Oculus;infra 或 infrastructure;ads、monetization 或 advertising;ranking、recommendation、recommendations、recommender 或 recsys;integrity;Instagram、WhatsApp、Messenger 或 Threads;GenAI;以及都没写的人。对每个部门和整个 P2,统计总数、Research 和 Engineering and Technical 两种职能、经理及以上、博士、在美国、有 Bachelor 学历,以及 Bachelor 学历来自 cases/china-educated-ai-talent-2026/queries/institutions.json 里中国大陆院校的人。实验室的总数、职能、博士和美国人数就是第一部分对同一群人的计数。
14职能、级别和职位
对实验室和 P2,统计职位带数据类词(data、annotation、annotator、labeling、prompt、knowledge expert、rater、evaluator)且职能不是 Research 的人,再统计职位不带这些词的 Engineering and Technical、Product(连同 Design 和 Project Management)以及没写职能的人;research 用第 13 步的 Research 计数,other 是剩下的人。统计 current_seniority 为 Intern、Specialist、Senior、Manager、Head 或 Director 的人;Vice President 及以上等于经理及以上减去 Manager、Head 和 Director。统计当前职位包含 machine learning engineer、software engineer、research scientist、research engineer、engineering manager、product manager、program manager、data scientist、data engineer、prompt engineer、production engineer 和 director 的人,保留人数最多的十个。
15技术方向
对基础模型和 LLM、后训练和对齐、多模态和感知、AI 基础设施、智能体、排序和推荐、AR、VR 和设备、安全和评估这八个方向,按 headline 或 current_title 里的短语或 skills 里的单个词统计实验室和 P2,按标题里的短语或描述里的单个词统计 Meta 的 AI 职位(第 17 步)。Meta 每条职位描述都有一段讲增强现实和虚拟现实的固定文字,大多数还提到 responsible AI,而短语在长文本里会拆成词分别匹配,所以选描述用词之前先读一个完整的职位切片;词表见 queries/mapping.json。
16来源和流动
对实验室和 P2,统计以前在 Google 或 DeepMind、OpenAI、Anthropic、Apple、Microsoft、Amazon 或 AWS、NVIDIA、ByteDance 或 TikTok 有过非实习工作的人,以及在 Stanford、Carnegie Mellon、Berkeley、Massachusetts Institute of Technology、Urbana 和 Indian Institute of Technology 有任何学历的人。中国大陆本科的比例只有在每个格子都不少于 20 人时,才按级别拆分(Intern、Specialist 和 Senior 对比经理及以上)。统计 2025-06-01 以来的流动,两个方向用同样的时间窗,Meta 和 P2 是同一个雇主(名称为 Meta 且雇主规模为 10,001+;Facebook、Instagram、WhatsApp 和 Oculus 按名称):流向 X 指一条 2025-06-01 或之后开始的 X 非实习在职经历、一条 2025-05-01 或之后结束的 Meta 非实习经历,并且目前没有任何名称为 Meta 的在职经历(不论规模);从 X 流入指一条 2025-06-01 或之后开始的 Meta 非实习在职经历、一条 2025-05-01 或之后结束的 X 非实习经历,并且目前不在 X 任职。统计 OpenAI、DeepMind、Anthropic、xAI、Thinking Machines、Microsoft、Apple、Amazon 或 AWS、NVIDIA、同一条经历里不含 DeepMind 的 Google,以及 Meta 名称以外的任何雇主;某一行不少于 10 人时,再加上 AI 词统计一次。
17职位和薪资
取 posted_date gte "now-180d"、标题含 P2 的 AI 词或 AI、且不含那些非技术职位词的 Meta 职位,按职位族依次归类,取第一个匹配:research scientist;research engineer;software engineer、machine learning engineer、ML engineer 或 AI engineer;数据类职位;product manager、product management、program manager 或 designer;其他。对美国、以美元计、同时写明 salary.annual_min 和 salary.annual_max 的职位,统计全部以及前三个职位族各有多少;达到 15 条的,再统计 annual_min 不低于 150,000、180,000、215,000 和 265,000,以及 annual_max 不低于 215,000、250,000、295,000 和 340,000 的职位数。这是职位里写明的基本薪资范围,不是实际薪酬。
18版图的输出
每个指标写一个汇总文件:data/map_size、map_units、map_functions、map_levels、map_titles、map_directions、map_sources、map_flows、map_postings 和 map_pay。每个 1 到 9 人的计数都写成 "<10",分母不少于 30 才发布比例。列出读者能算出的每一个合计(各部门加起来是 P2,表里每一行加起来是它的总数,一个部门在美国的人包含在它的总数里,第二部分的实验室格子包含在第一部分对应的格子里,一行流动里带 AI 词的部分包含在这一行里),逐个隐藏最小的格子,直到算不出任何 1 到 9 人的群体。第一部分已经发布了实验室的职能,所以当拆出数据类职位会留下这样的差值时,把实验室的 other 和 none 合并。任何一项检查不通过就什么也不写。
19版图的图表和局限
组织版图画成一棵树:P2、各部门,实验室和第一部分的几个小组挂在实验室下面;然后是各部门的职能和级别、技术方向(资料对比职位)、来源、流动(成对的条形),以及各职位族写明的薪资区间。要说明:部门是人们自己写的,不是 Meta 的组织架构;P2 数的是资料,不是员工,准确率由核对测得;职位只是某一天在招的岗位,同一个岗位在几个城市发布会按城市各算一次;流动依据的资料滞后,日期只到 2026 年 4 月,而且跨过了 2025 年 10 月 Meta AI 部门的裁员;只看一家公司无法衡量招聘难度,这一项不在范围内。
你会得到
聚合文件和图表,一段说明抽检发现了什么、改了什么,以及这次运行花了多少 API Credits(取自运行前后的余额)。
如果调用返回 402 insufficient_quota,说明 key 有效,只是余额用完了。
复现数字
353 API Credits11.77 美元超过新账户赠送的 100 API Credits
一个只用 Python 标准库的小脚本,把已提交的查询按计数发出去,写出这个页面所用的聚合文件。需要 Python,并在终端里设置好 METIX_KEY(见 agent 路径的第 1 步),也可以让你的 agent 替你运行这几行。
curl -fsSL https://platform.metix.ai/casebook/source/meta-superintelligence-labs-2026.tar.gz | tar xz
cd meta-superintelligence-labs-2026
: "${METIX_KEY:?set METIX_KEY first}" && python3 cases/meta-superintelligence-labs-2026/fetch.py你会得到
data/*.json 和 data/receipt.json。运行 git diff cases/meta-superintelligence-labs-2026/data 看哪些数字变了:除去快照之后数据本身的变化,数字应该一致。
改成你的问题
花费取决于你的版本读取多少。在提示词第 1 步里写上你自己的上限。
提示词就是这个案例本身。改掉下表里的部分,你的 agent 就会回答你的问题,用同样的检查和同样的花费记录方式。
| 想改的 | 改哪里 | 例子 |
|---|---|---|
| 实验室 | 第 2 步的雇主和实验室名称,并按第 3 步重新核对 | 写 Gemini 的 Google DeepMind 员工,或 Microsoft AI |
| 实验室成立的日期 | 第 4 步和第 5 步的分界日期 | Microsoft 超级智能团队用 2025-11-01 |
| 新人来自哪里 | 第 6 步的雇主顺序 | 加上 Mistral AI 或 Cohere |
| 版图的部门 | 第 13 步的顺序和词表,并按第 12 步重新核对 | 单列 WhatsApp,或者 Llama |
| API Credit 上限 | 第 1 步、第 3 步和第 12 步 | 只跑第 1 到第 10 步,花费约 200 API Credits |
运行前先问清楚
有人带着更笼统的问题来时,先把这几件事定下来,每一件都会改变查询或花费:
- 哪些词表示一个人属于这个实验室?其中有没有词还有别的意思?
- 哪些公司名称算同一个雇主,现在的和以前的都算吗?
- 用哪个日期区分原本就在的人和后来加入的人?
- 实习算不算以前在那里工作过?
- 核对读取最多能花多少 API Credits?
- headline 里哪些词指的是团队,哪些只是话题?
用 Metix AI Platform 回答两个问题:在公开资料中写明自己属于 Meta Superintelligence Labs 的人里,有多少人在 2025 年 6 月实验室成立时已经在 Meta 工作?其余的人是从哪里来的?另外,Meta 可见的 AI 人员分布在哪些部门,这个实验室在其中处于什么位置?只通过公开的 Platform 访问(REST 地址 https://mira-api.metix.ai、MCP 服务或 metix-skills),密钥从 METIX_KEY 读取,任何时候都不要打印密钥。 1. 先读规则再查询。调用 GET /contract(免费),所有条件只用 querySpecByEntity.profile 和 querySpecByEntity.job 里的字段;再读 GET /docs/api/people(免费)。描述同一份工作的条件要放在同一个 has_experience 里,才能保证说的是同一份工作。文本字段按词匹配,顺序不限,不分大小写;current_function、current_seniority、experience.seniority 和 experience.company.type 只取固定值,用 eq 或 in。一次查询最多 64 个条件,嵌套最多 6 层。size 1 的计数花 1 API Credit,查不到任何人时不收费;搜索每返回 25 个 ID 花 1 API Credit,读取详情每 5 条记录花 1 API Credit,所以每个要发布的数字都按计数来设计。每个查询先加一个什么也匹配不到的词发一次:Platform 会按限制检查查询,结果为空不收费。开始和结束时各调用一次 GET /auth/key/status(免费)查余额,总花费超过 650 API Credits 之前先停下来问我。 2. 范围。当前在 Meta 工作(experience.company.name match "Meta" 且 experience.is_current eq true,放在同一个 has_experience 里),并且 headline 或 current_title 匹配 superintelligence 或 MSL。用计数确认 company.name eq "Meta" 得到同样的总数,说明这个名字没有匹配到别的公司;再确认 Facebook 在 Platform 上就是同一个雇主,不能当作单独的检验。以前在 Meta 的工作,指雇主名为 Meta、Facebook、Instagram、WhatsApp 或 Oculus 的经历。实习指 experience.seniority eq "Intern" 或 experience.title 匹配 intern 的经历,在同一条经历里判断。另外统计较窄的定义(只写 superintelligence),并作为背景统计写了 FAIR 却没写实验室名称的 Meta 在职资料。 3. 先核对再计数。搜索结果按匹配程度排序,只看最前面会让这个群体显得比实际更干净。所以要读完整的切片:size 25 的搜索花 1 API Credit,同时返回总数,25 人以内的切片会完整返回。分五个切片读约 60 份资料(某个州里 2025 年 6 月前没有 Meta 经历的人,两个城市里有这类经历的人,Meta 经历没有开始日期的人,某个州里写 MSL 但没写 superintelligence 的人),用 POST /entity/v1/profiles/detail-by-id,_source 只取 headline、current_title、current_function 和经历里的 company.name、title、start_date、end_date、is_current、seniority,不取姓名。报告其中有多少人写的是在这个实验室工作,确认老员工以前在 Meta 有正式工作而不只是实习,并找出名单漏掉的 Meta 公司名称。子团队的每个词、Microsoft 群体的一个完整切片和所有在招职位,都用同样的方法读。读到的记录不能出现在任何公开文件里。 4. 分组。分界日期是 2025-06-01。统计总数;以前在 Meta 有经历、且开始于分界日期之前的人;去掉实习后的同一个数;以及留任的人:有一条非实习的 Meta 经历开始于分界日期之前,并且仍在进行或 experience.end_date gte "2025-05-01"(这两个条件用 any 放在同一条经历里)。回流的人等于非实习的数减去留任的数,前实习生等于第一个数减去非实习的数,新加入 Meta 的人等于总数减去第一个数;后三组合起来是外部招聘。较窄的定义也统计总数、以前的经历和留任三个数;写 superintelligence 的 Microsoft 在职资料统计四组,分界日期 2025-11-01,结束日期 2025-10-01。 5. 日期。统计以前的 Meta 经历开始于以下每个日期之前的人数:2012-01-01、2014-01-01、2016-01-01、2018-01-01、2020-01-01、2022-01-01、2023-01-01、2024-01-01、2025-01-01、分界日期、2025-07-01、2025-08-01、2025-09-01、2025-10-01、2026-01-01 和 2026-04-01;相邻两个日期的差就是一段首次加入的时间。去掉实习再做一遍,做到分界日期为止。对留任的人,统计当前 Meta 经历开始于以下每个日期当天或之后的人数:2025-01-01、2025-04-01、2025-06-01、2025-07-01、2025-08-01、2025-09-01、2025-10-01、2026-01-01 和 2026-04-01,这样每个人按最新的职位归入一段。Microsoft 统计 2012、2016、2020、2023、2025-01-01 和它的分界日期之前的人数。个人资料的更新有滞后,所以要按开始月份统计所有资料里的 Meta 经历,说明最后一个完整的月份是哪个月。 6. 来源。对外部招聘的人(范围内、不属于留任的人),统计一条 experience.end_date gte "2025-01-01" 的非实习经历,雇主依次为:OpenAI、DeepMind、Anthropic、xAI、Thinking Machines、Apple、Scale AI、Google、Microsoft、Amazon 或 AWS、NVIDIA;最后是 experience.company.type eq "Educational",这一行实习也算。每一行都排除前面各行已经匹配到的人,剩下的算作其他雇主或没有。对整个群体,统计以前在 Google 或 DeepMind、OpenAI、Anthropic、Apple、Microsoft、Amazon 或 AWS 有过非实习工作的人;这些行会重叠。 7. 岗位、团队、地点和职位。对整个群体和外部招聘的人,分别统计 current_function eq Research、Engineering and Technical、Product,以及 current_function exists。对当前职能是 Research 的人,在实验室里和作为基准的其他 Meta 研究人员里(当前在 Meta、职能是 Research、没写实验室名称),分别统计 current_seniority 为 Senior、为 Manager 或更高级别、有级别,以及有 Doctorate 学历的人;整个群体和外部招聘的人也统计博士。统计 headline 或 title 里提到 FAIR、TBD、infra 或 infrastructure、PAR 或 product applied research 的人。统计 location.country 为 United States,location.state 为 California、New York、Washington,加州境内的湾区城市,以及 United Kingdom。对 Meta 在招职位(is_open eq true、company.name match "Meta",并且标题匹配 superintelligence 或 MSL,或者描述匹配 superintelligence labs),统计总数、标题带 research 的职位、Menlo Park、San Francisco、New York、写明 min_experience_months 的职位和其中不超过 36 个月的职位、资历标签、2026-09-01 以来发布的职位,以及 Meta 全部在招职位。 8. 输出。写出汇总文件,每个都带 "unit"("profiles" 或 "jobs")、快照日期和来源查询文件。每个 1 到 9 人的计数都写成 "<10"。一段日期如果只有 1 到 9 人,就和相邻的一段合并,但不能跨过分界日期。某个公开的合计里,隐藏的格子加起来如果是 1 到 9 人,就再隐藏一个格子。较窄的定义和 Microsoft 群体只分到公开的计数之间每个差值都是 0 或至少 10 的程度。分母不少于 30 才发布比例。写任何文件之前,检查读者能算出的每个差值;写出的任何文字里都不写个人姓名,包括新闻里点名的人;链接新闻报道可以。 9. 图表。首次加入的各段画成时间线,标出分界日期,后面是新加入 Meta 的人按月的分布,Microsoft 画在同一条时间轴上;四组画成一根条形,较窄的定义和 Microsoft 放在下面;外部招聘的人按刚离开的雇主分组,五家 AI 实验室放在一起;留任的人和外部招聘的人的当前职能;实验室研究人员与基准的博士比例和级别;子团队的提及;各州;在招职位的地点。数值直接标在条上,每张图的标题用中性、客观的措辞写出结论。 10. 局限。这个范围是主动写明实验室的人,不等于实验室本身:只写 FAIR 或什么都没写的人不在其中,新加入的人和老员工写明的比例也可能不同。计数是可见的资料,不是员工人数;过时的资料也算作在职,所以也不保证是下限。有些资料已经过时,最近几个月的数字偏少。只写年份的日期按 1 月算,会把一些人移到分界的另一边,要说明是哪个方向。新增一条 Meta 经历只是调岗人数的下限,很多团队调动不会新增经历。来源依据的是经历的结束日期。Microsoft 群体规模小,还包括招聘人员。在招职位只是某一天的情况。用中性的动词(加入、离开、调动、招聘),除第 17 步职位里写明的基本薪资范围外,不涉及薪酬。 11. 版图的范围。Meta 可见的 AI 人员(P2)指有第一部分那条 Meta 在职经历、并且 headline 或 current_title 写有 AI 词的人:machine learning、ML、deep learning、computer vision、NLP、natural language processing、LLM、LLMs、large language models、reinforcement learning、generative AI、GenAI、artificial intelligence、superintelligence、MSL 或 FAIR;单独的 AI 只在 current_title 里算。实验室以外的人还要满足三个条件:在同一个 has_experience 里有一条 experience.company.size eq "10,001+" 的 Meta 在职经历;current_function 不是 Human Resources、Sales、Marketing、Administrative、Finance & Accounting、Legal、Customer Service 或 Real Estate;当前职位里没有 marketing、sales、recruiter、recruiting、sourcer、sourcing、talent、administrative、assistant、counsel、attorney、paralegal、accountant、communications 或 partnerships。把这三个条件各自和两个实验室名称条件放进同一个 any,这样第一部分的实验室成员全部留在 P2 里,两部分说的是同一群人。文本字段的词表用 in 发送:效果和每个词一个 match 条件相同,还能让每个查询保持在 64 个条件以内。 12. 核对版图。按 P2 的完整切片读至少 100 份资料(一个州或国家加一小段 total_experience_months,匹配到的全部读完),只取 headline、current_title、current_function、summary,以及当前经历的职位、描述、公司名称和规模,不取姓名,报告其中做 AI 工作的比例,必须达到 90%。确定词表之前,先检验读取中发现的陷阱:headline 里单独的 AI 多半是流行词;research scientist 和 research engineer 按词匹配,会把人员研究、调查科学、光子学,以及 Reality Labs Research 的软件工程师都算进来;在美国以外,Meta 这个名字还会匹配到别的公司。部门词(GenAI、generative AI、AR 和 VR 相关词、infra)也各读一个完整切片,据此判断每个词指的是团队还是话题,以及部门的先后顺序。 13. 部门和规模。统计美国的 Meta 在职资料数,以及规模为 10,001+ 的 Meta 在职经历在美国和美国以外各有多少,这样没有一个计数会变成 100000+。把 P2 的每个人归到 headline 或 current_title 里第一个出现的部门,顺序如下:实验室(superintelligence、MSL);FAIR;Reality Labs,加上 AR、VR、XR、augmented reality、virtual reality、mixed reality、wearables、smart glasses 和 Oculus;infra 或 infrastructure;ads、monetization 或 advertising;ranking、recommendation、recommendations、recommender 或 recsys;integrity;Instagram、WhatsApp、Messenger 或 Threads;GenAI;以及都没写的人。对每个部门和整个 P2,统计总数、Research 和 Engineering and Technical 两种职能、经理及以上、博士、在美国、有 Bachelor 学历,以及 Bachelor 学历来自 cases/china-educated-ai-talent-2026/queries/institutions.json 里中国大陆院校的人。实验室的总数、职能、博士和美国人数就是第一部分对同一群人的计数。 14. 职能、级别和职位。对实验室和 P2,统计职位带数据类词(data、annotation、annotator、labeling、prompt、knowledge expert、rater、evaluator)且职能不是 Research 的人,再统计职位不带这些词的 Engineering and Technical、Product(连同 Design 和 Project Management)以及没写职能的人;research 用第 13 步的 Research 计数,other 是剩下的人。统计 current_seniority 为 Intern、Specialist、Senior、Manager、Head 或 Director 的人;Vice President 及以上等于经理及以上减去 Manager、Head 和 Director。统计当前职位包含 machine learning engineer、software engineer、research scientist、research engineer、engineering manager、product manager、program manager、data scientist、data engineer、prompt engineer、production engineer 和 director 的人,保留人数最多的十个。 15. 技术方向。对基础模型和 LLM、后训练和对齐、多模态和感知、AI 基础设施、智能体、排序和推荐、AR、VR 和设备、安全和评估这八个方向,按 headline 或 current_title 里的短语或 skills 里的单个词统计实验室和 P2,按标题里的短语或描述里的单个词统计 Meta 的 AI 职位(第 17 步)。Meta 每条职位描述都有一段讲增强现实和虚拟现实的固定文字,大多数还提到 responsible AI,而短语在长文本里会拆成词分别匹配,所以选描述用词之前先读一个完整的职位切片;词表见 queries/mapping.json。 16. 来源和流动。对实验室和 P2,统计以前在 Google 或 DeepMind、OpenAI、Anthropic、Apple、Microsoft、Amazon 或 AWS、NVIDIA、ByteDance 或 TikTok 有过非实习工作的人,以及在 Stanford、Carnegie Mellon、Berkeley、Massachusetts Institute of Technology、Urbana 和 Indian Institute of Technology 有任何学历的人。中国大陆本科的比例只有在每个格子都不少于 20 人时,才按级别拆分(Intern、Specialist 和 Senior 对比经理及以上)。统计 2025-06-01 以来的流动,两个方向用同样的时间窗,Meta 和 P2 是同一个雇主(名称为 Meta 且雇主规模为 10,001+;Facebook、Instagram、WhatsApp 和 Oculus 按名称):流向 X 指一条 2025-06-01 或之后开始的 X 非实习在职经历、一条 2025-05-01 或之后结束的 Meta 非实习经历,并且目前没有任何名称为 Meta 的在职经历(不论规模);从 X 流入指一条 2025-06-01 或之后开始的 Meta 非实习在职经历、一条 2025-05-01 或之后结束的 X 非实习经历,并且目前不在 X 任职。统计 OpenAI、DeepMind、Anthropic、xAI、Thinking Machines、Microsoft、Apple、Amazon 或 AWS、NVIDIA、同一条经历里不含 DeepMind 的 Google,以及 Meta 名称以外的任何雇主;某一行不少于 10 人时,再加上 AI 词统计一次。 17. 职位和薪资。取 posted_date gte "now-180d"、标题含 P2 的 AI 词或 AI、且不含那些非技术职位词的 Meta 职位,按职位族依次归类,取第一个匹配:research scientist;research engineer;software engineer、machine learning engineer、ML engineer 或 AI engineer;数据类职位;product manager、product management、program manager 或 designer;其他。对美国、以美元计、同时写明 salary.annual_min 和 salary.annual_max 的职位,统计全部以及前三个职位族各有多少;达到 15 条的,再统计 annual_min 不低于 150,000、180,000、215,000 和 265,000,以及 annual_max 不低于 215,000、250,000、295,000 和 340,000 的职位数。这是职位里写明的基本薪资范围,不是实际薪酬。 18. 版图的输出。每个指标写一个汇总文件:data/map_size、map_units、map_functions、map_levels、map_titles、map_directions、map_sources、map_flows、map_postings 和 map_pay。每个 1 到 9 人的计数都写成 "<10",分母不少于 30 才发布比例。列出读者能算出的每一个合计(各部门加起来是 P2,表里每一行加起来是它的总数,一个部门在美国的人包含在它的总数里,第二部分的实验室格子包含在第一部分对应的格子里,一行流动里带 AI 词的部分包含在这一行里),逐个隐藏最小的格子,直到算不出任何 1 到 9 人的群体。第一部分已经发布了实验室的职能,所以当拆出数据类职位会留下这样的差值时,把实验室的 other 和 none 合并。任何一项检查不通过就什么也不写。 19. 版图的图表和局限。组织版图画成一棵树:P2、各部门,实验室和第一部分的几个小组挂在实验室下面;然后是各部门的职能和级别、技术方向(资料对比职位)、来源、流动(成对的条形),以及各职位族写明的薪资区间。要说明:部门是人们自己写的,不是 Meta 的组织架构;P2 数的是资料,不是员工,准确率由核对测得;职位只是某一天在招的岗位,同一个岗位在几个城市发布会按城市各算一次;流动依据的资料滞后,日期只到 2026 年 4 月,而且跨过了 2025 年 10 月 Meta AI 部门的裁员;只看一家公司无法衡量招聘难度,这一项不在范围内。
方法与局限
统计范围怎么定义、怎么计数和抽检,以及这些数字不能说明什么。
人群
2026 年 9 月 22 日 Metix AI Platform 上的个人档案:有一段当前在 Meta 的工作,并且个人资料标题或当前职位写有 superintelligence 或 MSL(逐词匹配,不分大小写)。共 936 人,其中 790 人写的是 superintelligence。定义在 queries/population.json 和 queries/measures.json。
四组人
分界是 2025 年 6 月 1 日;Meta 在当月底宣布成立实验室。成立时已在 Meta:有一段不是实习的 Meta 工作,开始于分界以前,并且当前仍在或在 2025 年 5 月或以后结束。离开后回来:分界以前有过不是实习的 Meta 工作,但都没有持续到 2025 年 5 月。只实习过:分界以前在 Meta 只有实习。Meta 新人:分界以前没有任何 Meta 经历,包括不到 10 个没有开始日期的人。后三组合称外部加入者。以前的 Meta 工作包括 Meta、Facebook、Instagram、WhatsApp 和 Oculus;实习是资历为 Intern 或职位名称含 intern 的经历。
刚离开的雇主
外部加入者在 2025 年或以后结束的一段工作,按固定顺序只算第一个匹配的雇主。公司的实习不算,所以博士生在某个实验室的暑期实习不算他来自哪里;大学的实习算,因为博士生的经历常标为实习。
日期
首次加入是一个人最早那段 Meta 经历的开始日期,由"在某个日期以前有 Meta 经历"的累计人数相减得到,所以不需要读取任何人。人数少于 10 的时段与相邻时段合并。个人档案有滞后:平台上所有 Meta 经历中,2026 年开始的有 3,988 段,其中 3 月和 4 月 1,104 段,5 月及以后不到 10 段,所以日期截至 2026 年 4 月,最后几个月偏少。只写年份的日期按 1 月算。
抽读
定义是这份研究的关键,所以按完整切片读了 63 个档案,而不是搜索结果的最前面几条:62 个写的是自己在实验室工作,其余的是为实验室招聘的人。抽读改了三处定义:写 MSL 的人也算(读了 14 个,13 个指的是实验室);以前的 Meta 工作加上 Instagram、WhatsApp 和 Oculus;少数数据标注或红队测试的岗位单独统计。读过的档案都不会公开。
局限
这是自己写明实验室的人,不是实验室本身:只写 FAIR 或什么都不写的人不在里面;如果新人比老员工更爱写,或者更少写,这个比例会随之变化。人数数的是可见档案,不是员工:不写实验室的人不在里面,离开后没更新的档案还在里面,所以它不是员工总数,也不保证是下限(图 11 显示当前在 Meta 的档案是 Meta 报告员工数的 1.7 倍)。只写年份的日期按 1 月算,所以只写了 2025 年的新人会算作实验室成立时已在 Meta,已在 Meta 的人也可能被算作离开后又回来。刚离开的雇主依赖结束日期,有 47.2% 的外部加入者在列出的雇主和大学都没有 2025 年或以后结束的工作。Microsoft 组人数少,包括招聘人员,个人档案的滞后对它的影响也比对 Meta 大。岗位只是一天的数据。不点任何人的名字,也不涉及薪资。
第二阶段:统计的是谁
当前在 Meta(规模 10,001 人以上的这家公司)工作、个人资料标题或当前职位写有 AI 相关词语的档案(词表见 queries/mapping.json;单独的 AI 只在职位里算),去掉非技术职能和职位:共8,257 人。实验室的 936 人全部算进来,和第一阶段一致,其中约 4% 写的是非技术职能或职位。没有 AI 词语的研究类职位不算,因为在 Meta 这类职位也包括用户研究、调查科学和硬件。按八个完整切片抽读了 150 个档案,92% 是 AI 岗位。
第二阶段:单元、工作与方向
单元按实验室、FAIR、Reality Labs、基础设施、广告、排序、内容安全、应用、GenAI 的顺序,算在个人资料标题或职位里最先写到的那一个。职能和层级是平台对当前工作的固定分类;职位名称含有候选词的全部单词就算。方向可以多选:员工按标题、职位和技能匹配,近 180 天 Meta 的 218 个 AI 岗位按职位名称和描述匹配。
第二阶段:流动与薪资
新工作开始于 2025 年 6 月 1 日或以后、上一份工作在 2025 年 5 月 1 日或以后结束,才算一次换工作,不算实习,包括 Meta 的所有岗位。薪资是美国岗位以美元写明的底薪区间,一类岗位至少有 15 个才公开。
局限:第二阶段
当前在 Meta 的档案是 Meta 报告员工数的 1.7 倍,所以第二阶段数的都是档案,不是员工数的下限,也不是上限。单元是大家自己写的,不是 Meta 的组织架构图,62.8% 的人九个单元都没写。档案日期截至 2026 年 4 月,2026 年 5 月的裁员和之后的变动都不在数据里。层级是按职称推出的可见层级,不是汇报关系。岗位招聘难度不在范围内:它需要跨雇主的比较,不是一家公司能回答的。
来源
Meta 宣布成立实验室(CNBC,2025 年 6 月 30 日);Meta 投资 Scale AI(Axios,2025 年 6 月 12 日);Microsoft 组建超级智能团队(CNBC,2025 年 11 月 6 日);实验室分成四个团队(Built In,2025 年 8 月 27 日);Meta 在 AI 团队裁员(SiliconANGLE,2025 年 10 月 22 日);Meta 的员工人数(SEC 文件,2026 年 7 月 29 日)。
最近一次复现
上一次复现花了多少,取自运行前后 Metix AI Platform 记录的余额。
- 运行日期
- 2026-09-22
- 调用次数
- 358
- 搜索结果
- 353
- 读取记录
- 0
- API Credits
- 353
搜索结果是搜索返回的 ID 数,每次计数查询算一个,完整搜索按命中数算。记录是完整读取的岗位或档案:这个案例一条都没读。
做这个案例另外花了大约 1,629 API Credits:agent 做的抽检、试探性查询,以及被公开复现取代的早先运行。你不需要再花这部分。