Partner Director – Data Center & Energy Solutions
About the role
then...
. - Responsibilities: The bullet list under "Responsibilities". It includes multiple sub-sections: Partner Strategy & Ecosystem Development, Partner Recruitment & Onboarding, Partner Management & Enablement, Partner Sales & Revenue Growth, Go-To-Market & Co-Marketing Execution, Operational Rigor & Relationship Governance. Each has sentences. We need to output a- for any list of duties/requirements/benefits. So we can treat each responsibility as a list item. Could also break sub-bullets but not needed. We'll output each responsibility as
- containing the text.
- Requirements: There's "Required Qualifications" section. That could map to Requirements or Qualifications. The instruction says we have both Requirements and Qualifications headings possible. We need to decide where to put content. The posting has "Required Qualifications". That likely belongs under Qualifications. Requirements could be things like experience, skills etc. But we have only that section. We could put it under Qualifications. Or we could split: Requirements could be the list of qualifications (8-12+ years etc). Since there is no separate Skills section, we could put skills under Qualifications or maybe under Skills if we extract skills like "Strong executive communication skills", "Proficiency in CRM tools". But better to follow instruction: Use headings only when posting has real specific content. We have content for Qualifications (the Required Qualifications). We could also have a Skills section if we extract skills from that. But we might just have Qualifications section and maybe Requirements omitted if no distinct content. However we have "Required Qualifications" which includes experience, track record, etc. That could be considered Qualifications. We'll output
Qualifications
with- items.
We also have "Physical, Mental & Environmental Demands" which could be considered Requirements? But it's about physical demands; not typical. Might be considered Requirements but it's specific. However the instruction says include section only when posting has real specific content for it. This is specific content. Could map to Requirements. But the heading list includes Requirements. So we could put that under Requirements. However the content is a list of physical demands with percentages etc. That is specific. We'll include Requirements section with that content.
We also have salary range mention: "The salary range is required by the California Pay Transparency Act..." This is Pay info. So we should include Pay section with that paragraph. It's specific. So we include
Pay
with... . We have no explicit Benefits or Schedule. So we omit those. We also have "Hanwha Q CELLS America Inc. (“HQCA”) is a Qcells company..." That's about company description; could be part of About the role or maybe separate but we can incorporate into About the role paragraph. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes some legal stuff at end: "You may view your privacy rights by reviewing Qcells' Privacy Policy or by contacting our HR team for a copy." That's boilerplate; remove. Also the earlier paragraph about Hanwha Q CELLS America Inc. is not boilerplate; it's company description; keep. Also "Physical, Mental & Environmental Demands" includes a paragraph about Rehabilitation Act; that's legal but it's describing demands; we keep the demands but maybe remove the introductory sentence about Rehabilitation Act? The instruction: remove EEO/equal-opportunity/scam-warning boilerplate. The Rehabilitation Act mention is legal but it's part of demands; we could keep the demands but maybe drop the first sentence: "To comply with the Rehabilitation Act of 1973 the essential physical, mental and environmental requirements for this job are listed below." That's boilerplate; we can drop it and keep the list. Also there is a line: "Incumbent must be able to successfully perform all of the functions of the job with or without reasonable accommodation." That's also boilerplate; drop. We'll keep the bullet list of demands. Now format. We need to output only HTML fragment, no /, no markdown. We'll produce:
About the role
...
Responsibilities
- Partner Strategy & Ecosystem Development: Support and drive growth across strategic partners within the energy, utility, digital infrastructure, and data center ecosystem, aligning partner activities with company growth objectives, target markets, and revenue goals. Identify and develop partnership opportunities that accelerate customer adoption, pipeline generation, and revenue growth across data center, utility, and energy infrastructure markets. Actively prospect and onboard high-value partners, pitching the joint value proposition to C-level stakeholders. Develop partner joint business plans and an end-to-end partner journey focused on measurable outcomes.
- Partner Recruitment & Onboarding: Lead partner identification, recruitment, and onboarding, building a high-impact partner bench from the ground up. Create and execute a partner recruitment strategy, including value proposition, qualification criteria, and engagement model. Be the first point of contact for prospective partners and newly identified opportunities. Establish clear partner expectations, success criteria, and engagement frameworks.
- Partner Management & Enablement: Serve as the primary relationship owner for key strategic partners, building trust and long-term value. Ensure partners deeply understand our solutions, positioning, and value propositions. Provide partners with the enablement, tools, training, and resources required to sell, implement, and support our offerings. Develop conflict management and rules-of-engagement frameworks, including executive escalation paths when needed.
- Partner Sales & Revenue Growth: Own partner-sourced and partner-influenced pipeline and revenue, you will be responsible for forecasting, tracking, and delivering on channel sales goals. Drive top-of-funnel pipeline generation jointly with partners through co-selling, joint prospecting, and GTM plays. Integrate partners into active sales cycles early to shorten sales cycles and increase deal size. Collaborate closely with Sales to advise on partner selection, deal strategy, and execution. Co-sell complex opportunities, guiding both internal sellers and partner teams through the entire deal lifecycle.
- Go-To-Market & Co-Marketing Execution: Design and execute joint GTM plays, including use-case and solution-based motions. Partner with Marketing to deliver co-marketing initiatives such as events, campaigns, content, and thought leadership. Ensure partner offerings and messaging align with our evolving GTM strategy and customer needs. Act as the internal partner champion, educating teams on how to successfully work with and leverage partners. Represent the company externally as a partner ecosystem leader at industry events and partner forums. Provide feedback to product and leadership based on partner and market insights.
- Operational Rigor & Relationship Governance: Build and manage partner pipeline tracking, forecasting accuracy, and performance metrics. Conduct regular performance reviews with key partners to track progress, identify friction points, strengthen alignment and deepen engagement. Identify gaps in partner capability or engagement and take corrective action. Create lightweight, scalable partner processes appropriate for a startup but designed to grow with the business.
Requirements
- Mobility: Standing 20% of time, Sitting 70% of time, Walking 10% of time.
- Strength: Pulling up to 10 Pounds, Pushing up to 10 Pounds, Carrying up to 10 Pounds, Lifting up to 10 Pounds.
- Dexterity: Typing F, Handling F, Reaching F.
- Agility: Turning F, Twisting F, Bending O, Crouching O, Balancing N, Climbing N, Crawling N, Kneeling N.
Qualifications
- 8–12+ years of experience in partner management, partner sales, business development, or ecosystem roles, ideally within high-growth or startup environments.
- Proven track record of recruiting, enabling, and monetizing partners. Evidence of having built or significantly scaled a partner program from an early stage.
- Strong experience driving partner-led revenue, including sourcing, co-selling, and owning the deal cycle.
- Comfortable operating across strategy and execution, with a bias toward action and high level of ownership.
- Strong executive communication skills and ability to influence internally and externally.
- Adept at managing complex, multi-stakeholder projects across Sales, Marketing, and Product teams, and with partner teams.
- Thrives in ambiguity and is comfortable building the plane while flying it. Doesn't need a pre-existing playbook; wants to write it.
- Has a "sales-first" mindset. Understands that a partnership is only as good as the revenue it generates.
- Proficiency in CRM tools and the ability to use data to justify investments.
- Travel may be required up to 20-30%, depending on business needs.
Pay
The salary range is required by the California Pay Transparency Act and may differ depending on the location of those candidates hired nationwide. Actual compensation is influenced by a wide array of factors including but not limited to, skill set, education, licenses and certifications, essential job duties and requirements, and the necessary experience relative to the job’s minimum qualifications. This target salary range is for CA positions only and should not be interpreted as an offer of compensation.
We should ensure no duplicate content. Also we removed the privacy line. Check for any leftover boilerplate: The "Hanwha Q CELLS America Inc. (“HQCA”) is a Qcells company..." we kept in About the role? We didn't explicitly include it. We should incorporate that into About the role paragraph. Let's adjust About the role to include that description. We'll rewrite About the role paragraph to include: "As Partner Director, Data Center & Energy Solutions at Hanwha Qcells Grid & Energy Services, you will serve as the architect and driving force behind our partner ecosystem strategy, building and scaling partnerships as a core engine of business growth. This is a high-impact role within a startup environment, combining strategic ownership with hands-on execution across partner recruitment, enablement, and revenue generation. You will own the full partner lifecycle—from identifying and onboarding the right
- items.
We also have "Physical, Mental & Environmental Demands" which could be considered Requirements? But it's about physical demands; not typical. Might be considered Requirements but it's specific. However the instruction says include section only when posting has real specific content for it. This is specific content. Could map to Requirements. But the heading list includes Requirements. So we could put that under Requirements. However the content is a list of physical demands with percentages etc. That is specific. We'll include Requirements section with that content.
We also have salary range mention: "The salary range is required by the California Pay Transparency Act..." This is Pay info. So we should include Pay section with that paragraph. It's specific. So we include