Manager, PAR Ecosystem Enablement
Faraday Future · El Segundo, CA · 1 mo ago
On-siteOTHR$90k–$105k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "The Company:" description, "Your Role:" description, "Key Responsibilities:", "Basic Qualifications:", "Preferred Qualifications:", "Salary Range:", "Perks + Benefits". Also location info.
We must not repeat job title as heading. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content appropriately. The instructions: Use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content appropriately. The instructions: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content. Must include a section only when posting has real, specific content for it. So we need sections: About the role (maybe from "Your Role:" description), Responsibilities (Key Responsibilities), Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe from Basic Qualifications includes technical skills), Benefits (Perks + Benefits), Pay (Salary Range). Schedule not present, so omit.
We must not include filler like "commensurate with experience". Salary range is given: ($90,000-$105,000 DOE), plus benefits and incentive plans. That's specific enough to include Pay section.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include details from company description, role description, responsibilities bullet points, qualifications bullet points, preferred qualifications bullet points, skills (technical), benefits list.
We must not include boilerplate like EEO, equal opportunity, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we drop the EEO statement at end.
We also need to drop duplicated lines (maybe none). Also drop "The Company:" heading? We'll incorporate company description into About the role? Actually About the role section likely includes description of role and company? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role containing both company overview and role description? Probably yes.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role containing both company overview and role description? Probably yes.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
Company description ...
Role description ...
ThenResponsibilities
- ... each bullet from Key Responsibilities (multiple sub-bullets). Need to preserve each bullet as list item. The responsibilities have headings like "Enablement Strategy & Program Ownership" etc with sub-bullets. We should flatten? Probably each bullet line is a responsibility. We'll capture each line starting with a bold heading? The text includes headings and then sentences. We'll treat each sentence as a list item? Better to keep each bullet as a list item preserving the content. The original bullet list: Enablement Strategy & Program Ownership Define and own the overall PAR dealer enablement strategy, establishing a clear vision for how FF develops and sustains a high-performing dealer ecosystem. Lead the design, launch, and continuous improvement of structured enablement programs covering dealer onboarding, product training, go-to-market readiness, and commercial capability building. Translate business objectives from PAR leadership into executable enablement roadmaps with defined milestones, resource requirements, and success metrics. Act as the accountable owner for enablement program outcomes, regularly reviewing KPIs and adjusting strategy based on data, dealer feedback, and business performance. Cross-functional Leadership & Stakeholder Management Lead cross-functional enablement initiatives by aligning and coordinating stakeholders across Business, Legal, Content, Marketing, and Sales pillars — setting direction, managing dependencies, and driving decision-making. Serve as the senior point of contact for enablement-related topics in leadership discussions, representing the PAR team's dealer development needs and progress. Build strong working relationships with functional leaders and subject matter experts to ensure enablement programs reflect the latest product, commercial, and compliance requirements. Proactively identify gaps, risks, and opportunities across the dealer ecosystem and bring structured proposals to leadership for prioritization. Dealer Development & Ecosystem Growth Lead the design of scalable dealer development frameworks that enable FF's partner network to grow in capability, coverage, and commercial performance over time. Oversee dealer-facing communications strategy, ensuring consistent, professional, and bilingual messaging across the PAR network. Drive the planning and execution of dealer development events, training programs, and partner engagement initiatives — from strategy through logistics. Build feedback loops with the dealer ecosystem and translate insights into program improvements and strategic recommendations for PAR leadership. Legal, Compliance & Policy Integration Work closely with Legal and Compliance to ensure all dealer-facing enablement materials, onboarding processes, and partner communications meet FF's regulatory and governance standards. Own the compliance dimension of dealer enablement, including qualification checkpoints, certification tracking, and audit-readiness of program documentation. Lead the update process for compliance-sensitive enablement content, ensuring materials remain current with regulatory changes and internal policy updates. Content & Knowledge Management Leadership Direct the development of bilingual enablement content — including training curricula, product guides, sales playbooks, and partner portal resources — in partnership with the Content team. Establish and maintain content governance standards, version control processes, and distribution channels to ensure the dealer network always has access to accurate, up-to-date resources. Build internal knowledge management systems for the PAR Enablement function, enabling institutional knowledge to scale with the team. Performance Management & Continuous Improvement Define, own, and report on key performance indicators (KPIs) for dealer enablement programs, including onboarding completion, training engagement, partner readiness scores, and program ROI. Present regular program performance reviews to PAR leadership with data-driven insights, trend analysis, and clear recommendations for program evolution. Foster a culture of continuous improvement within the enablement function, regularly benchmarking against industry best practices and incorporating learnings into program design. Team & Capability Building Provide mentorship and guidance to more junior team members or cross-functional contributors involved in enablement activities. Develop the PAR team's overall enablement capability by introducing frameworks, tools, and best practices that raise the standard of partner program management across the organization. We'll turn each sentence into
- . The headings like "Enablement Strategy & Program Ownership" are not sentences; we could either include them as
- or maybe treat as subheading but we only allowed
for sections. Could embed them as inside
- . Probably better to keep them as part of the list item: e.g.,
- Enablement Strategy & Program Ownership: Define and own ...
. That preserves content. Similarly for each heading. NowRequirements
for Basic Qualifications. We'll list each bullet. Basic Qualifications list: - Bachelor Degree in related field - Minimum 5 years of professional experience in program management, sales enablement, partner/channel operations, or a closely related cross-functional leadership role. Experience managing programs with significant cross-functional scope and measurable business impact is required. - Program Leadership: Demonstrated track record of owning and delivering complex, multi-stakeholder programs end-to-end — from strategy through execution — in a fast-paced, ambiguous environment. - Bilingual: in Mandarin Chinese (written and verbal) is required, as this role involves frequent communication with internal teams and dealer partners. - Cross-functional Influence: Proven ability to lead without direct authority — aligning stakeholders, driving alignment across functions, and influencing outcomes at multiple levels of the organization. - Strategic Thinking: Ability to develop and articulate a clear enablement strategy, connect it to business objectives, and translate it into actionable, measurable programs. - Communication & Presentation: Excellent written and verbal communication skills; able to present complex program updates and strategic recommendations to senior leadership with clarity and confidence. - Work Ethic: Self-directed and resilient; comfortable setting priorities, managing trade-offs, and leading through ambiguity in a high-growth startup environment. - Technical Skills: Proficiency in Microsoft PowerPoint, Word, and Excel; familiarity with project management tools (e.g., Notion, Asana, or similar); comfort with AI productivity tools. We'll turn each into- . Possibly combine some sentences. Now
Qualifications
for Preferred Qualifications. List: - Sales Enablement or Channel Enablement Leadership: Prior experience leading a sales enablement or partner enablement function, particularly in a dealer, distributor, or franchise channel model. - China Market Expertise: Deep familiarity with China-based dealer or partner ecosystems, including business norms, regulatory considerations, and communication expectations. - Content & Curriculum Development: Demonstrated experience building bilingual training programs, sales playbooks, or partner certification curricula at scale. - Cross-border Business Leadership: Experience leading programs in US-China cross-border business environments or managing enablement across multiple geographies. - Industry Fit: Background in automotive, EV, robotics, smart hardware, or consumer technology industries. - Big Firm Exposure: Experience at a top-tier professional services, consulting, or large enterprise organization (e.g., Big 4, MBB, or Fortune 500) in a program management or commercial capacity. - Legal & Compliance Familiarity: Working knowledge of commercial agreements, dealer contracts, or regulatory compliance requirements in a B2B or channel context. NowSkills
maybe we could extract technical skills from Basic Qualifications (Technical Skills) but we already included that as part of Requirements. However we could still have a Skills section for technical skills like proficiency in MS Office, project management tools, AI productivity tools. But to avoid duplication, maybe we keep Skills separate: list technical skills. The instruction: prefer a few substantive sections over many thin ones. Could combine Technical Skills into Requirements. But we already have Requirements section with many items; we could keep Skills separate for clarity. However we must not create thin sections; but Skills would have a few items, okay. We have Pay section: Salary Range: ($90,000-$105,000 DOE), plus benefits and incentive plans. We have Benefits section: list perks. Benefits list: - Healthcare + dental + vision benefits (Free for you/discounted for family) - 401(k) options - Casual dress code + relaxed work environment - Culturally diverse, progressive atmosphere - "Soul of Faraday" community outreach team We'll output as- ... . We must not include duplicated lines, boilerplate. Also remove location? Location is "Work location is El Segundo, CA; domestic and international travel may be required to support dealer engagements and partner events." This is substantive; we could include in About the role paragraph or maybe a separate section? Not among allowed headings; we could include in About the role paragraph. Now ensure we don't include any heading with empty content. Now produce HTML. Let's craft. About the role paragraph: combine company description and role description. Company description: "The Company: Faraday Future is a California-based technology company focused on the design, engineering, and development of intelligent, connected electric vehicles and related artificial intelligence–enabled technologies. Founded in 2014, the Company's mission is to disrupt the automotive and technology industries by creating user-centric, technology-first experiences. The Company, together with its controlled subsidiaries, operates across multiple technology-driven areas, including AI electric vehicles, robotics, and its crypto business (AIXC), all under its upgraded Global EAI Industry Bridge Strategy, marking the beginning of a new chapter in AI mobility and Web3 integration. The Company aims to leverage the latest technologies and world's best talent to realize exciting new possibilities across all of these lines. Faraday Future's automotive business exemplifies its vision for luxury, innovation, and performance, while its FX strategy aims to introduce mass production models equipped with state-of-the-art luxury technology derived from the FF brand, targeted towards a broader market with middle-to-low price range offerings. FF is committed to redefining mobility through AI innovation. Join us in shaping the future of intelligent transportation and technology by creating something new, something connected, and something with a true global impact." Role description: "Your Role: The Manager, PAR Ecosystem En