We need to output HTML fragment with sections only if content present. Use
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content.
Let's parse the posting.
We have Title: Sr. Director, Tech Strategy. Department: Tech Center – Tech Strategy. Location: Houston, TX. Supervisor: Head of Tech Center. FLSA Status: Exempt. Position Status: Permanent, Full-time. Work Status: Hybrid.
Then description: "Hanwha Qcells USA Corp (Qcells USA), headquartered in Houston, TX, specializes..." etc. That's about the company. Could be "About the role" or "About the company"? The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content.
We have a Summary paragraph describing role. That could go under "About the role". Then "Essential Job Function & Responsibilities" list -> Responsibilities.
Then "Required Qualifications" and "Preferred Qualifications" -> Requirements? Actually "Requirements" heading could contain required qualifications. "Qualifications" heading could contain preferred? But we have both Required and Preferred. Could combine under "Requirements" for required, and maybe "Qualifications" for preferred? Or we could have "Requirements" for required qualifications, and "Qualifications" for preferred qualifications. The instruction: Use headings exactly as given; we can decide which content goes where. We must not create empty sections.
We also have "EXAMPLES OF PHYSICAL DEMANDS" and "EXAMPLES OF WORK ENVIRONMENT" - these are not in the allowed headings; we should drop them as boilerplate? They are not navigation/legal/EEO but they are not in allowed headings. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. These sections are not explicitly listed as boilerplate but they are not part of allowed headings. Should we include them? Probably drop them because they are not relevant to allowed headings and not required to preserve? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. But we must only use allowed headings. If we drop those sections, we lose substantive info (physical demands, work environment). However maybe they are considered boilerplate? Not exactly EEO but could be considered generic. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say to remove physical demands. But we have no heading for them; we could incorporate them into a
under maybe "About the role" or "Responsibilities"? But they'd be unrelated. Better to keep them as a paragraph under maybe "About the role" or a generic section? But we cannot create new headings. We could put them in a
without a heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we must wrap everything in headings; we can have
elements outside headings. So we can include physical demands and work environment as paragraphs without a heading. That's acceptable.
Similarly, the EEO statement at end is boilerplate to remove. Also the statement about job descriptions not comprehensive etc is boilerplate? Might be considered legal. We'll remove that.
Also "Applicants must be authorized to work for any employer in the United States. We are unable to sponsor or take over sponsorship of an employment visa at this time." That's substantive (work authorization). Could be placed under maybe "Requirements" or a paragraph.
Also "Standard working hours are Monday through Friday from 8:00 AM to 5:00 PM or 9:00 AM to 6:00 PM local time." That's schedule info -> we can create a Schedule section.
Also "This position is expected to travel up to 30%." That's also schedule/travel; could be under Schedule.
Also "This position is hybrid, based out of our Houston, TX office, requiring up to 4 days per week in the office. May be remote if outside of Office Mobilization Plan." That's also schedule/work status.
Thus we can create a Schedule section with those details.
Pay: No mention of salary/pay. So we should NOT create a Pay section.
Benefits: No mention of benefits. So we should NOT create Benefits section.
Skills: Could be derived from qualifications but we have no explicit skills list. Could we create Skills section from required qualifications? Might be thin. Better to omit Skills if no explicit skills list. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills.
Thus sections we will have:
- About the role (summary paragraph)
- Responsibilities (list from Essential Job Function & Responsibilities)
- Requirements (Required Qualifications)
- Qualifications (Preferred Qualifications) maybe? Or we could combine required and preferred under Requirements and omit Qualifications. But we have both; we could put required under Requirements, preferred under Qualifications. That seems appropriate.
- Schedule (hybrid, remote, hours, travel)
We may also include a paragraph for work authorization (maybe under Requirements). Or we could add a separate paragraph after Requirements.
We also need to include location, department, supervisor etc? That's metadata; we could fold into a short
after the heading? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph with location, department, supervisor, FLSA, position status, work status. That's minor metadata.
Thus structure:
About the role
Summary paragraph (the Summary section).
Maybe also include company description? That's not about the role but about company. Could be included in About the role? The summary already includes role description. The earlier paragraphs about Qcells USA could be considered company overview; we could include them in About the role as context. But we must preserve all substantive information. So we should include that company description somewhere. Could be in About the role as well.
Thus About the role will contain: company description paragraph(s) + summary of role.
We'll combine them into maybe multiple
tags.
Then Responsibilities:
Responsibilities
- ... each responsibility line.
We need to extract each responsibility from "Essential Job Function & Responsibilities". The text is a long sentence with many clauses separated by periods? Let's parse:
"Lead development and implementation of technology and product strategies within the Tech Strategy organization, aligned with overall Tech Center strategy and EPC business objectives.Lead the process for engaging EPC Project Management, Construction, Operations, and other project execution organizations to identify technology opportunities and translate field needs and lessons learned into technology initiatives and product requirements.Develop portfolio analyses and prioritization recommendations based on business value, project impact, technical feasibility, risk, investment requirements, timing, and scalability.Develop business cases for technology initiatives, including NPV/IRR/ROI, unit benefits, project volume, investment requirements, implementation timing, and portfolio value.Assess emerging technologies, market developments, and competitive trends to determine potential EPC value, constructability, deployability, economics, and scalability, in collaboration with Product R&D and other appropriate functions.Develop build, buy, or partner recommendations and identify strategic suppliers, technology partners, and joint-development opportunities.Lead the Tech Center Product Management function, including product strategy, requirements, roadmaps, launch planning, commercialization, and lifecycle management.Partner with Product R&D to establish business and product requirements, development priorities, target performance, and commercialization objectives, and monitor development progress against business requirements and deployment needs.Lead commercialization and deployment planning for priority technologies, incorporating field-validation results, project applicability, implementation timing, adoption requirements, and lessons learned.Coordinate technology strategy, product priorities, and external partnerships with Qcells and Hanwha organizations in the U.S., Korea, and other global locations, including support for supplier collaboration, contracting, and intellectual property strategy.Lead the Tech Solutions and Product Management teams, including organizational priorities, resource planning, budgets, performance management, and employee development.Develop KPI reviews and decision materials that support Tech Center governance and investment decisions by the Head of Tech Center and other senior stakeholders.Foster a culture of practical innovation, cross-functional collaboration, disciplined decision-making, and measurable business results.Perform other duties and special projects as assigned by Management."
We need to split into list items at each period that starts a new clause (but some clauses have commas). We'll treat each sentence as a responsibility.
Thus list items:
- Lead development and implementation of technology and product strategies within the Tech Strategy organization, aligned with overall Tech Center strategy and EPC business objectives.
- Lead the process for engaging EPC Project Management, Construction, Operations, and other project execution organizations to identify technology opportunities and translate field needs and lessons learned into technology initiatives and product requirements.
- Develop portfolio analyses and prioritization recommendations based on business value, project impact, technical feasibility, risk, investment requirements, timing, and scalability.
- Develop business cases for technology initiatives, including NPV/IRR/ROI, unit benefits, project volume, investment requirements, implementation timing, and portfolio value.
- Assess emerging technologies, market developments, and competitive trends to determine potential EPC value, constructability, deployability, economics, and scalability, in collaboration with Product R&D and other appropriate functions.
- Develop build, buy, or partner recommendations and identify strategic suppliers, technology partners, and joint-development opportunities.
- Lead the Tech Center Product Management function, including product strategy, requirements, roadmaps, launch planning, commercialization, and lifecycle management.
- Partner with Product R&D to establish business and product requirements, development priorities, target performance, and commercialization objectives, and monitor development progress against business requirements and deployment needs.
- Lead commercialization and deployment planning for priority technologies, incorporating field-validation results, project applicability, implementation timing, adoption requirements, and lessons learned.
- Coordinate technology strategy, product priorities, and external partnerships with Qcells and Hanwha organizations in the U.S., Korea, and other global locations, including support for supplier collaboration, contracting, and intellectual property strategy.
- Lead the Tech Solutions and Product Management teams, including organizational priorities, resource planning, budgets, performance management, and employee development.
- Develop KPI reviews and decision materials that support Tech Center governance and investment decisions by the Head of Tech Center and other senior stakeholders.
- Foster a culture of practical innovation, cross-functional collaboration, disciplined decision-making, and measurable business results.
- Perform other duties and special projects as assigned by Management.
Now Requirements: Required Qualifications bullet list.
We need to extract each qualification line.
The Required Qualifications paragraph:
"Bachelor’s degree in engineering, science, or another relevant technical discipline.
15+ years of relevant experience in renewable energy, EPC, engineering, construction technology, product management, technology strategy, technology development, or related functions, including significant leadership responsibility.
Demonstrated experience leading complex, cross-functional technology or product initiatives from opportunity identification and strategy through implementation or commercialization.
Strong systems-level understanding of utility-scale energy projects and the relationship between technology, engineering, project design, construction, operations, and project economics.
Demonstrated ability to translate business and field needs into technology priorities, product requirements, and actionable initiatives and to evaluate technologies from both technical and business perspectives.
Strong financial and analytical skills, including business-case development, investment analysis, NPV/IRR/ROI, and technology benefit assessment.
Experience developing technology or product strategies, roadmaps, portfolio recommendations, and commercialization plans.
Experience with new product introduction (NPI), commercialization, and deployment processes for new products or technology solutions.
Demonstrated ability to work effectively across engineering/R&D, project management, construction, operations, supply chain, commercial, finance, and other business functions.
Experience leading professional teams and working with technology suppliers and external partners.
Strong executive communication, stakeholder management, and influencing skills, with demonstrated ability to build alignment across organizational boundaries."
We'll make each line a