Technical Product Manager, China
for each heading. Use - for any list of duties/requirements/benefits, and
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to parse the posting.
We have sections: About The Role & Team (intro). Then Key Working Relationships (maybe part of responsibilities). Then What You’ll Do (responsibilities). Then What Success Looks Like (maybe part of responsibilities or qualifications). Then Required (maybe requirements). Then What You Bring (qualifications/skills). Then Preferred Experience (skills). Then Travel & Logistics (maybe schedule? but not pay). Then Why This Role Stands Out (company description - maybe not needed). Then What We Offer (benefits). Then Compensation Transparency (pay). Then Equal Opportunity Employer (boilerplate to remove). Also list of states where remote workers can be employed (maybe part of benefits? but it's eligibility; could be considered part of benefits? Might be considered boilerplate? It's not EEO but it's location eligibility. Might be considered part of benefits? Probably we can include as part of Benefits? But it's not a benefit per se; it's eligibility. Might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This list of states is not exactly EEO but could be considered eligibility; but it's not a benefit. Might be considered part of "Benefits"? Not really. Safer to drop it as it's not a benefit, pay, schedule. It's more about remote work eligibility; could be considered part of "Benefits"? But it's not a benefit like vacation. I'd drop it.
We need to include sections only when there is real specific content.
Thus sections:
- About the role (intro paragraph)
- Responsibilities (What You’ll Do + maybe Key Working Relationships + What Success Looks Like)
- Requirements (Required + What You Bring? Actually "Required" is a heading; "What You Bring" is qualifications/skills. Could split into Requirements and Qualifications/Skills. But we have headings: Requirements, Qualifications, Skills. We can map.
We have "Required" section: list of bullet-like sentences: Ability to operate comfortably across both IDC's China operations and its US steering committee. 10+ years in technology implementation, including 5+ years leading cross-border China deployments. Hands-on ICP filing experience (at least one prior successful filing) and working knowledge of MLPS 2.0. Prior budget responsibility exceeding $1M USD on a comparable engagement. Hands-on experience with Alibaba Cloud or AWS China (Sinnet), including VPC isolation, network segmentation, and BYOK encryption. Bilingual in Mandarin and English
That's requirements.
Then "What You Bring" seems similar but maybe more like qualifications/skills: Location: West Coast Preferred Experience integrating enterprise platforms with China-approved LLM APIs (DeepSeek, Qwen, Kimi, GLM, Hunyuan, ERNIE, or comparable). Familiarity with Retrieval-Augmented Generation (RAG) architectures designed to prevent raw data transmission to LLM providers. PIPL, PRC data-security, and cross-border data-transfer assessment experience, including coordination with outside legal counsel.
That could be "Preferred Experience" (skills). Also "Travel & Logistics" could be schedule? It mentions occasional travel to Beijing and to IDC's US offices should be expected for steering committee meetings, sprint gate reviews, and key milestones. That's schedule/travel expectations.
We also have "What Success Looks Like" which could be part of responsibilities or qualifications; but it's specific outcomes. Could be part of Responsibilities.
We have "Why This Role Stands Out" (company description) - maybe not needed; could be omitted as boilerplate? It's not required but could be considered "About the role"? Already have about the role. Might be considered fluff; but it's substantive about company. However instruction: Prefer a few substantive sections over many thin ones. Could include as part of About the role? But we already have about the role intro. Could merge.
We have "What We Offer" benefits list: 15 vacation days, 12 company-paid holidays, 6 paid sick days, medical/dental/vision, 2 floating holidays, 1 volunteer day, 401(k) company match, company-paid short-term disability, company-paid life insurance, company-paid parental leave. That's benefits.
Compensation Transparency: expected total annual compensation between $140,000 – $213,000 inclusive of base and variable. That's pay.
Schedule: Not explicitly given besides travel expectations. Could treat Travel & Logistics as schedule. Or we could omit Schedule section if no explicit schedule (like full-time, hours). The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. We have Pay and Benefits. For Schedule, we have travel expectations but not regular schedule. Might be considered schedule? It's not standard work hours. Might be better to omit Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
But we have both Qualifications and Skills; we could combine Qualifications and Skills into one? But we have headings for both; we can use them if we have content.
Qualifications: Could be "What You Bring" (preferred experience) maybe qualifies as qualifications. Skills: Could be "Preferred Experience integrating enterprise platforms..." etc. Actually both are similar. Might be better to have Qualifications (required) and Skills (preferred). But we already have Requirements for required. Then Qualifications for preferred? Let's map:
- Requirements: Required section (mandatory).
- Qualifications: What You Bring (preferred experience) maybe.
- Skills: Preferred Experience integrating enterprise platforms... (maybe skills). But we could also put that under Qualifications.
Given we want few sections, maybe combine Qualifications and Skills into one "Qualifications & Skills". But headings are fixed; we must use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can omit sections we don't have content for. So we can have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Omit Schedule.
Now we need to fill each with appropriate content using
for prose and
- for lists.
Let's extract content.
About the role: The first paragraph(s) under "About The Role & Team". It includes: "We are bringing IDC Quanta — our production enterprise AI platform — into China: connected to China-approved LLMs, running on compliant cloud infrastructure, and operating safely inside a fast-moving regulatory environment. This is a deployment engagement, not a rebuild of the product itself.The Technical Project Manager is IDC's on-the-ground owner in Beijing. You'll run the delivery engine — ICP filing, cloud provisioning, MLPS 2.0 and PIPL compliance, model evaluation logistics, and any implementation vendor's day-to-day work — and make sure nothing that matters gets lost in translation between Beijing and the US steering committee."
Also there is "Key Working Relationships" paragraph: "You'll deliver this jointly with the Head of AI & Automation, China, who co-owns delivery execution and represents the program to local IDC leadership, and with a third-party implementation vendor engaged to execute the sprint-by-sprint build-out (cloud provisioning, model integration, RAG architecture, and production deployment). You are the connective tissue between the vendor's day-to-day execution, the VP's local oversight, and the US steering committee."
We could combine these into About the role prose.
Responsibilities: "What You’ll Do" bullet-like sentences (though not bullet list). Also "What Success Looks Like" could be part of responsibilities. Also maybe "Key Working Relationships" but we already used.
Let's list responsibilities:
- End-to-end delivery of the Pre-Sprint through Sprint 4 plan: cloud VPC provisioning, IDC Quanta test instance stand-up, model evaluation logistics, RAG architecture build-out, and production deployment — on schedule for the Week 12 first-capability target and Week 22 go-live.
- Manage the ICP (Internet Content Provider) filing end-to-end — initiate immediately on program kickoff, engage a qualified filing agent, and keep the 4–8 week process moving without becoming the thing that blocks Week 9.
- Own the MLPS 2.0 gap assessment and PIPL compliance review for the Quanta China deployment, and document the certification level required against current posture.
- Provision and configure China cloud infrastructure (Alibaba Cloud primary, AWS China as fallback) — VPC isolation, BYOK encryption with keys held outside China, and government disclosure notification clauses in every cloud contract.
- Run parallel model evaluation (DeepSeek, Qwen, with Kimi/GLM/Hunyuan/ERNIE as fallback) against the pass/fail quality threshold defined jointly with the US Technical Product Owner.
- Document and maintain the External China-Protected RAG architecture, the identity federation design, and the MCP server build-out — confirming none of it requires touching Quanta's core codebase.
- Chair local steering committee touchpoints, prepare status decks, and escalate any new HIGH-rated risk within 24 hours to the China Country Lead and the US steering committee representative.
- Own weekly status reporting and the Week 9 decision memo inputs from the China side: risk register, deployment readiness, and remediation plans for any red-rated criterion.
- Coordinate with IDC's legal team and outside counsel on the PRC regulatory opinion, and support export control review with a clean, API-calls-only test structure.
Also success criteria:
- ICP filing in-flight or approved with no blocking issues by the Week 9 gate.
- A production-ready China cloud environment — BYOK, VPC isolation, SIEM logging — validated before Sprint 4 go-live.
- Model evaluation results the US side can actually trust, because the threshold was set before testing began.
- A steering committee that never finds out about a HIGH-rated risk after the fact.
We can include these as part of responsibilities (maybe as bullet list). We'll make a
- list.
Requirements: list from Required section:
- Ability to operate comfortably across both IDC's China operations and its US steering committee.
- 10+ years in technology implementation, including 5+ years leading cross-border China deployments.
- Hands-on ICP filing experience (at least one prior successful filing) and working knowledge of MLPS 2.0.
- Prior budget responsibility exceeding $1M USD on a comparable engagement.
- Hands-on experience with Alibaba Cloud or AWS China (Sinnet), including VPC isolation, network segmentation, and BYOK encryption.
- Bilingual in Mandarin and English.
Qualifications: from "What You Bring" (preferred experience) maybe:
- Location: West Coast (maybe not a qualification but location preference). Could be included.
- Preferred Experience integrating enterprise platforms with China-approved LLM APIs (DeepSeek, Qwen, Kimi, GLM, Hunyuan, ERNIE, or comparable).
- Familiarity with Retrieval-Augmented Generation (RAG) architectures designed to prevent raw data transmission to LLM providers.
- PIPL, PRC data-security, and cross-border data-transfer assessment experience, including coordination with outside legal counsel.
We could also include "Travel & Logistics" as part of Qualifications? But it's about travel expectations; maybe better as part of Responsibilities? Actually it's about expectations; could be under Responsibilities as bullet: Occasional travel to Beijing and to IDC's US offices should be expected for steering committee meetings, sprint gate reviews, and key milestones.
We'll add that to Responsibilities
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to parse the posting. We have sections: About The Role & Team (intro). Then Key Working Relationships (maybe part of responsibilities). Then What You’ll Do (responsibilities). Then What Success Looks Like (maybe part of responsibilities or qualifications). Then Required (maybe requirements). Then What You Bring (qualifications/skills). Then Preferred Experience (skills). Then Travel & Logistics (maybe schedule? but not pay). Then Why This Role Stands Out (company description - maybe not needed). Then What We Offer (benefits). Then Compensation Transparency (pay). Then Equal Opportunity Employer (boilerplate to remove). Also list of states where remote workers can be employed (maybe part of benefits? but it's eligibility; could be considered part of benefits? Might be considered boilerplate? It's not EEO but it's location eligibility. Might be considered part of benefits? Probably we can include as part of Benefits? But it's not a benefit per se; it's eligibility. Might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This list of states is not exactly EEO but could be considered eligibility; but it's not a benefit. Might be considered part of "Benefits"? Not really. Safer to drop it as it's not a benefit, pay, schedule. It's more about remote work eligibility; could be considered part of "Benefits"? But it's not a benefit like vacation. I'd drop it. We need to include sections only when there is real specific content. Thus sections: - About the role (intro paragraph) - Responsibilities (What You’ll Do + maybe Key Working Relationships + What Success Looks Like) - Requirements (Required + What You Bring? Actually "Required" is a heading; "What You Bring" is qualifications/skills. Could split into Requirements and Qualifications/Skills. But we have headings: Requirements, Qualifications, Skills. We can map. We have "Required" section: list of bullet-like sentences: Ability to operate comfortably across both IDC's China operations and its US steering committee. 10+ years in technology implementation, including 5+ years leading cross-border China deployments. Hands-on ICP filing experience (at least one prior successful filing) and working knowledge of MLPS 2.0. Prior budget responsibility exceeding $1M USD on a comparable engagement. Hands-on experience with Alibaba Cloud or AWS China (Sinnet), including VPC isolation, network segmentation, and BYOK encryption. Bilingual in Mandarin and English That's requirements. Then "What You Bring" seems similar but maybe more like qualifications/skills: Location: West Coast Preferred Experience integrating enterprise platforms with China-approved LLM APIs (DeepSeek, Qwen, Kimi, GLM, Hunyuan, ERNIE, or comparable). Familiarity with Retrieval-Augmented Generation (RAG) architectures designed to prevent raw data transmission to LLM providers. PIPL, PRC data-security, and cross-border data-transfer assessment experience, including coordination with outside legal counsel. That could be "Preferred Experience" (skills). Also "Travel & Logistics" could be schedule? It mentions occasional travel to Beijing and to IDC's US offices should be expected for steering committee meetings, sprint gate reviews, and key milestones. That's schedule/travel expectations. We also have "What Success Looks Like" which could be part of responsibilities or qualifications; but it's specific outcomes. Could be part of Responsibilities. We have "Why This Role Stands Out" (company description) - maybe not needed; could be omitted as boilerplate? It's not required but could be considered "About the role"? Already have about the role. Might be considered fluff; but it's substantive about company. However instruction: Prefer a few substantive sections over many thin ones. Could include as part of About the role? But we already have about the role intro. Could merge. We have "What We Offer" benefits list: 15 vacation days, 12 company-paid holidays, 6 paid sick days, medical/dental/vision, 2 floating holidays, 1 volunteer day, 401(k) company match, company-paid short-term disability, company-paid life insurance, company-paid parental leave. That's benefits. Compensation Transparency: expected total annual compensation between $140,000 – $213,000 inclusive of base and variable. That's pay. Schedule: Not explicitly given besides travel expectations. Could treat Travel & Logistics as schedule. Or we could omit Schedule section if no explicit schedule (like full-time, hours). The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. We have Pay and Benefits. For Schedule, we have travel expectations but not regular schedule. Might be considered schedule? It's not standard work hours. Might be better to omit Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. But we have both Qualifications and Skills; we could combine Qualifications and Skills into one? But we have headings for both; we can use them if we have content. Qualifications: Could be "What You Bring" (preferred experience) maybe qualifies as qualifications. Skills: Could be "Preferred Experience integrating enterprise platforms..." etc. Actually both are similar. Might be better to have Qualifications (required) and Skills (preferred). But we already have Requirements for required. Then Qualifications for preferred? Let's map: - Requirements: Required section (mandatory). - Qualifications: What You Bring (preferred experience) maybe. - Skills: Preferred Experience integrating enterprise platforms... (maybe skills). But we could also put that under Qualifications. Given we want few sections, maybe combine Qualifications and Skills into one "Qualifications & Skills". But headings are fixed; we must use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can omit sections we don't have content for. So we can have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Omit Schedule. Now we need to fill each with appropriate content using
for prose and
- for lists.
Let's extract content.
About the role: The first paragraph(s) under "About The Role & Team". It includes: "We are bringing IDC Quanta — our production enterprise AI platform — into China: connected to China-approved LLMs, running on compliant cloud infrastructure, and operating safely inside a fast-moving regulatory environment. This is a deployment engagement, not a rebuild of the product itself.The Technical Project Manager is IDC's on-the-ground owner in Beijing. You'll run the delivery engine — ICP filing, cloud provisioning, MLPS 2.0 and PIPL compliance, model evaluation logistics, and any implementation vendor's day-to-day work — and make sure nothing that matters gets lost in translation between Beijing and the US steering committee."
Also there is "Key Working Relationships" paragraph: "You'll deliver this jointly with the Head of AI & Automation, China, who co-owns delivery execution and represents the program to local IDC leadership, and with a third-party implementation vendor engaged to execute the sprint-by-sprint build-out (cloud provisioning, model integration, RAG architecture, and production deployment). You are the connective tissue between the vendor's day-to-day execution, the VP's local oversight, and the US steering committee."
We could combine these into About the role prose.
Responsibilities: "What You’ll Do" bullet-like sentences (though not bullet list). Also "What Success Looks Like" could be part of responsibilities. Also maybe "Key Working Relationships" but we already used.
Let's list responsibilities:
- End-to-end delivery of the Pre-Sprint through Sprint 4 plan: cloud VPC provisioning, IDC Quanta test instance stand-up, model evaluation logistics, RAG architecture build-out, and production deployment — on schedule for the Week 12 first-capability target and Week 22 go-live.
- Manage the ICP (Internet Content Provider) filing end-to-end — initiate immediately on program kickoff, engage a qualified filing agent, and keep the 4–8 week process moving without becoming the thing that blocks Week 9.
- Own the MLPS 2.0 gap assessment and PIPL compliance review for the Quanta China deployment, and document the certification level required against current posture.
- Provision and configure China cloud infrastructure (Alibaba Cloud primary, AWS China as fallback) — VPC isolation, BYOK encryption with keys held outside China, and government disclosure notification clauses in every cloud contract.
- Run parallel model evaluation (DeepSeek, Qwen, with Kimi/GLM/Hunyuan/ERNIE as fallback) against the pass/fail quality threshold defined jointly with the US Technical Product Owner.
- Document and maintain the External China-Protected RAG architecture, the identity federation design, and the MCP server build-out — confirming none of it requires touching Quanta's core codebase.
- Chair local steering committee touchpoints, prepare status decks, and escalate any new HIGH-rated risk within 24 hours to the China Country Lead and the US steering committee representative.
- Own weekly status reporting and the Week 9 decision memo inputs from the China side: risk register, deployment readiness, and remediation plans for any red-rated criterion.
- Coordinate with IDC's legal team and outside counsel on the PRC regulatory opinion, and support export control review with a clean, API-calls-only test structure.
Also success criteria:
- ICP filing in-flight or approved with no blocking issues by the Week 9 gate.
- A production-ready China cloud environment — BYOK, VPC isolation, SIEM logging — validated before Sprint 4 go-live.
- Model evaluation results the US side can actually trust, because the threshold was set before testing began.
- A steering committee that never finds out about a HIGH-rated risk after the fact.
We can include these as part of responsibilities (maybe as bullet list). We'll make a
- list. Requirements: list from Required section: - Ability to operate comfortably across both IDC's China operations and its US steering committee. - 10+ years in technology implementation, including 5+ years leading cross-border China deployments. - Hands-on ICP filing experience (at least one prior successful filing) and working knowledge of MLPS 2.0. - Prior budget responsibility exceeding $1M USD on a comparable engagement. - Hands-on experience with Alibaba Cloud or AWS China (Sinnet), including VPC isolation, network segmentation, and BYOK encryption. - Bilingual in Mandarin and English. Qualifications: from "What You Bring" (preferred experience) maybe: - Location: West Coast (maybe not a qualification but location preference). Could be included. - Preferred Experience integrating enterprise platforms with China-approved LLM APIs (DeepSeek, Qwen, Kimi, GLM, Hunyuan, ERNIE, or comparable). - Familiarity with Retrieval-Augmented Generation (RAG) architectures designed to prevent raw data transmission to LLM providers. - PIPL, PRC data-security, and cross-border data-transfer assessment experience, including coordination with outside legal counsel. We could also include "Travel & Logistics" as part of Qualifications? But it's about travel expectations; maybe better as part of Responsibilities? Actually it's about expectations; could be under Responsibilities as bullet: Occasional travel to Beijing and to IDC's US offices should be expected for steering committee meetings, sprint gate reviews, and key milestones. We'll add that to Responsibilities