ODM Program Manager Audio Devices

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. The posting includes: About Fairphone (intro) but we should not repeat job title; we can include an "About the role" maybe? Actually the posting includes "About Your Role" and then responsibilities etc. We need to map content to sections. We must not include boilerplate like cookie/navigation/legal/EEO etc. Remove application instructions etc. Also remove "Please know that we acknowledge..." about AI usage. Also remove location/hours/start/deadline? Those are metadata; we can fold minor metadata into a short

or drop it. Probably we can include location/hours in a short paragraph under maybe "About the role" or separate? But we should not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are mentioned: "Competitive salary aligned with market standards. Statutory paid annual leave (10 days upon joining), public holidays, and rest days in accordance with the labour law. Social benefits & contributions made by both employer and employee as required under Chinese law. Professional development opportunities for training, skill development, and career advancement." That's benefits. So we can include Benefits section. Pay: "Competitive salary aligned with market standards." That's pay info. So we can include Pay section. Schedule: "Hours: 40 hours per week". That's schedule. So we can include Schedule section. We also have location: "Location: China (you should have the right to work in either of these locations)". That's metadata; we can put in a short p maybe under About the role or separate? Probably we can include a short paragraph with location and hours etc. But we should not create extra sections for location. We need to preserve all substantive information. Must not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings (none present). Must not include boilerplate like DEI etc? The DEI section is substantive? It's about DEI @Fairphone. Might be considered boilerplate but it's part of posting. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." DEI is not exactly EEO but could be considered similar. However it's part of the company description; maybe we keep it under About Fairphone? But we are not to repeat job title as heading; we could have a section "About Fairphone" but not listed as allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should only use those headings. So we need to map content accordingly. Thus we need sections: - About the role: include description of role, mission, maybe location/hours? Could include location and hours as a short p. - Responsibilities: list of responsibilities. - Requirements: maybe "Must-haves" and "Nice-to-haves"? Could be Requirements and Qualifications. The posting has "Must-haves" and "Nice-to-haves". We could put Must-haves under Requirements, Nice-to-haves under Qualifications, or combine. But we need to follow headings: Requirements, Qualifications, Skills. The posting also has "Your Skills & Experience". That includes must-haves and nice-to-haves. Could treat Skills section for skills & experience. But we also have separate Requirements and Qualifications maybe not needed. However we must only include sections when posting has real specific content. We have content for Skills & Experience (must-haves, nice-to-haves). So we can make a Skills section. We also have Responsibilities section clearly. We have Benefits, Pay, Schedule. We might not need Requirements or Qualifications if we put all under Skills. But we could also split: Requirements = Must-haves, Qualifications = Nice-to-haves. However the instruction says prefer a few substantive sections over many thin ones. So better to have fewer sections: About the role, Responsibilities, Skills, Benefits, Pay, Schedule. That's six sections. We must not include empty sections. Now we need to preserve all substantive information: The About Fairphone intro paragraph about company mission etc. Should we include that? It's substantive about company. Could be placed under About the role? Or maybe we could include a brief intro under About the role as part of role description. The posting includes "About Fairphone" then "About Your Role". The "About Fairphone" is generic company description; we could include it under About the role as context. It's substantive, not boilerplate. So we should keep it. We also need to keep the line about limiting AI usage etc. That's application instruction? It's a request to limit AI tools. That's like application instruction; we should remove it per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So remove that. Also remove "Location: China (you should have the right to work in either of these locations) Hours: 40 hours per weekStart: ASAPDeadline to apply: We review applications on a rolling basis. Please apply as soon as possible." That's metadata; we can fold minor metadata into a short

or drop it. We could include location and hours in a short p under About the role. Start ASAP and deadline rolling basis maybe also minor; we could drop or include. Probably we can include location and hours in a short p, and drop start/deadline as they are not crucial? But we should preserve all substantive information; start date and deadline are substantive? They are about timing. Could be considered metadata but still info. The instruction says fold minor metadata into a short

or drop it. So we can include a short p with location, hours, start, deadline. That's okay. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft:

About the role

Fairphone is a global leader in sustainable, modular electronics, on a mission to change the electronics industry from the inside out. Built on strong social and environmental values, we are a diverse and inclusive team creating market consumer electronics that make a real impact. As an ODM Program Manager for Audio Devices, you will manage the end-to-end lifecycle of Fairphone’s audio hardware development in collaboration with Original Design Manufacturers (ODMs). Location: China (you should have the right to work in either of these locations). Hours: 40 hours per week. Start: ASAP. Deadline to apply: Applications are reviewed on a rolling basis; please apply as soon as possible.

Then Responsibilities:

Responsibilities

• Lead program planning, execution, and monitoring for audio device development with ODMs.
• Manage ODM deliverables including project timelines, prototypes, testing, validation, and product ramp‑up.
• Review and assess ODM capabilities, and lead partner onboarding and readiness evaluation.
• Serve as the primary interface between Fairphone and ODMs for day‑to‑day technical and program communication.
• Collaborate with internal engineering teams to ensure cross‑functional alignment (audio, software, mechanical, EE).
• Track program risks and issues, facilitating quick resolution and ensuring contingency planning.
• Ensure ODM compliance with Fairphone’s quality, sustainability, modularity, and repairability goals.
• Support product certification and field readiness activities including pilot runs and validation milestones.
• Coordinate post‑launch support activities including failure analysis, firmware updates, and customer service escalations.

Skills:

Skills & Experience

Must‑haves:

• Bachelor’s degree in Engineering (Electrical, Mechanical, or Industrial) or related field.
• Good English and native Mandarin skills in writing and speaking to support communicating project progress and technical issues to stakeholders and addressing concerns.
• 10+ years experience in consumer electronics or mobile industry, with a focus on ODM management.
• Proven success managing hardware development programs, especially in audio or mobile accessories.
• Strong project and program management skills, including cross‑functional coordination.
• Deep understanding of product development lifecycle, DFM/DFT, and validation processes.
• Experience collaborating with overseas ODMs and manufacturers.
• Excellent communication and interpersonal skills; fluency in English and Mandarin.
• Strong problem‑solving skills with a proactive, results‑oriented mindset.

Nice‑to‑haves:

• Experience working on sustainable and modular hardware projects.
• Knowledge of product environmental compliance standards (e.g., RoHS, REACH).
• Familiarity with Android audio architecture or embedded audio platforms.

Benefits:

Benefits

• Competitive salary aligned with market standards.
• Statutory paid annual leave (10 days upon joining), public holidays, and rest days in accordance with the labour law.
• Social benefits & contributions made by both employer and employee as required under Chinese law.
• Professional development opportunities for training, skill development, and career advancement.

Pay: Actually we already included competitive salary in Benefits; but we need a Pay section per instruction if posting actually states them. The posting says "Competitive salary aligned with market standards." That's pay. We could either keep it in Benefits or separate Pay. Since we already have Benefits section, we could move salary to Pay section and keep other benefits in Benefits. Let's do that. Thus:

Pay

Competitive salary aligned with market standards.

Benefits

• Statutory paid annual leave (10 days upon joining), public holidays, and rest days in accordance with the labour law.
• Social benefits & contributions made by both employer and employee as required under Chinese law.
• Professional development opportunities for training, skill development, and career advancement.

Schedule:

Schedule

40 hours per week.

We already included location/hours/start/deadline in About the role paragraph; but we also have Schedule section now with 40 hours per week. Might duplicate hours. We could keep schedule only and remove hours from About the role. Let's adjust: About the role paragraph will include location, start, deadline. Hours moved to Schedule. Thus About the role paragraph: location, start, deadline. Now we need to ensure we haven't missed any substantive info: The "Key Objectives" and "Core Activities" sections are similar to responsibilities; we might incorporate them? They are somewhat repetitive. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include those as well. They are under "Key Objectives" and "Core Activities". We could merge them into Responsibilities or maybe add a separate section? But we already have Responsibilities covering many points. The Key Objectives and Core Activities are essentially rephrasing responsibilities. To preserve all detail, we could include them as part of Responsibilities (maybe as additional bullet points). Let's extract them: Key Objectives: - Ensure timely and successful delivery of audio device programs with ODM partners. - Managing ODM deliverables such as project timelines, prototypes, testing, validation, and product ramp-up. - Translate Fairphone’s sustainability and product quality standards into actionable plans with external partners. - Coordinate across internal teams (Audio Design, Software, Hardware, Operations) to support ODM execution. - Drive continuous improvement in ODM collaboration practices, processes, and product outcomes. Core Activities: - Track program milestones and manage detailed project schedules with