VP Chief Technologist

We need to output HTML fragment with sections: headings

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading (page already shows it). Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting and extract sections. The posting includes: - Introduction: A Career at HARMAN Corporate (some intro paragraphs) - What You’ll Be Part Of (description of role) - Your Team - How You’ll Make An Impact - What Makes You A Strong Fit (requirements/qualifications) - Bonus Points if You Have (additional qualifications) - Things To Know (location, hybrid schedule, travel, background check) - What You Can Expect (benefits, work environment, perks) - Pay Transparency (salary range) - Benefits (description) - You Belong Here (culture) - About HARMAN: Where Innovation Unleashes Next-Level Technology (company description) - Important Notice: Recruitment Scams (boilerplate to remove) - HARMAN is proud to be an Equal Opportunity employer... (EEO boilerplate to remove) We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the "Important Notice: Recruitment Scams" and the EEO statement. Also drop duplicated lines? Not many duplicates. We need to keep substantive info: intro paragraphs, role description, team, impact, qualifications, bonus points, things to know (location, schedule, travel, background check), what you can expect (benefits, perks), pay transparency, benefits description, you belong here (culture), about HARMAN (company overview). Possibly combine some sections. We need to use headings

  for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when there is real specific content. We need to map content to these headings. We have: - About the role: could be the introductory description: "What You’ll Be Part Of", "Your Team", "How You’ll Make An Impact". Could combine as "About the role". Use

  About the role

  then paragraphs. - Responsibilities: could be the "How You’ll Make An Impact" bullet points (list of duties). Use

  Responsibilities

  with
  • items. - Requirements / Qualifications: Could be "What Makes You A Strong Fit" (requirements) and "Bonus Points if You Have" (preferred qualifications). Could combine into Requirements and Qualifications sections, or separate. The instruction says use headings for Requirements, Qualifications, Skills. We could have Requirements (mandatory) and Qualifications (preferred) or Skills. But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section? But they said we can use those headings; we need to include a section only when posting has real specific content. We have both mandatory and bonus points, so we could have two sections: Requirements (mandatory) and Qualifications (bonus). Or we could have Skills section for technical skills. Let's think. The posting includes: "What Makes You A Strong Fit": list of mandatory qualifications: exceptional technical track record, proven experience creating significant technologies, experience spanning research or advanced development and industrial-scale product development, broad systems thinking, proven ability to rapidly understand unfamiliar technical domains, demonstrated ability to translate complex technology into business implications, significant technology leadership experience, demonstrated ability to influence across organizational boundaries, extraordinary communication and interpersonal skills, strong commercial judgment combined with scientific and engineering rigor. Then "Bonus Points if You Have": advanced degree, experience across multiple industries, experience in more than one organizational environment, demonstrated experience taking technology from research or concept through architecture and product realization, experience working with external research ecosystems, proven ability to build new technical capabilities and attract exceptional technical talent, international and cross-cultural leadership experience. Thus we can have:

    Requirements

    with
    • for each mandatory bullet.

      Qualifications

      with
      • for each bonus point. Alternatively, we could have Skills section for technical domains: physics, software, AI, ML, acoustics, material science, signal processing, etc. But we already covered those in requirements. We also have "Things To Know": location (Sunnyvale, CA or Northridge, CA), hybrid schedule, occasional domestic and international travel, background investigation and drug screen. This could map to Schedule and maybe other sections. The schedule heading: we can put schedule info under

        Schedule

        . Location could be part of About the role or a separate section? There's no heading for location; we could fold into About the role or Things To Know paragraph. We have "What You Can Expect": hybrid work environment, employee discounts, learning and development, wellness benefits, tuition reimbursement, access to fitness center and cafeteria, inclusive environment. This is benefits and perks. Could map to Benefits section. We have "Benefits": description of benefits (medical, dental, vision, fertility support, adoption assistance, HSA/FSA, retirement savings, disability, life insurance, etc.). This is also benefits. Could combine with What You Can Expect. We have Pay Transparency: salary range $240,000 - $352,000 plus note about other compensation. This maps to Pay. We have "You Belong Here": culture description. We have "About HARMAN: Where Innovation Unleashes Next-Level Technology": company description. Thus we can produce sections: - About the role (intro + What You’ll Be Part Of + Your Team + How You’ll Make An Impact? Actually How You’ll Make An Impact is responsibilities; we could separate.) Better to follow the headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. About the role: general description of role, purpose, team, maybe "What You’ll Be Part Of", "Your Team". Your Team". Could be a paragraph. Responsibilities: the bullet list from "How You’ll Make An Impact". Requirements: mandatory qualifications from "What Makes You A Strong Fit". Qualifications: bonus points from "Bonus Points if You Have". Skills: maybe we could list technical domains: physics, software, AI, ML, acoustics, material science, signal processing, embedded systems, software platforms, UX/HMI, audio and signal processing, sensing, compute, connectivity, multi-physics systems. But that's already covered in requirements; but we could still create a Skills section summarizing those technical domains. However we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we skip Skills if it's thin. But we have to use headings only when there is real specific content. We could include Skills if we have a list of specific skills. The posting does mention "Exceptional technical track record with demonstrated hands-on depth in a combination of relevant technology domains like physics, software, AI, Machine Learning, acoustics, material science or signal processing, and the ability to reason credibly across adjacent fields." Also "Broad systems thinking across software, hardware and physical systems; relevant domains may include AI/ML, embedded systems, software platforms, UX/HMI, audio and signal processing, sensing, compute, connectivity and multi-physics systems." That's a list of skills. So we could create a Skills section with those. But we already have Requirements covering many of those. However we could still have Skills as a separate section focusing on technical domains. The instruction says prefer a few substantive sections over many thin ones. Having Skills might be thin if it's just a list of domains already covered. But we could combine Requirements and Skills into one section? But headings are separate; we could omit Skills if we think it's redundant. However we need to follow the instruction: "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to use all. So we can omit Skills if not needed. Thus we will produce sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Possibly also "You Belong Here" and "About HARMAN" could be folded into About the role or separate? There's no heading for culture or company description. Could we add a section like "About the company"? Not in the list. The instruction only gave examples; we could still add other headings? It says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings; we should stick to those. So we should not create other headings like "Company Overview" or "Culture". We need to fold that content into existing sections, perhaps About the role or Benefits? But culture and company description may not fit neatly. However we must preserve ALL substantive information; we cannot drop it. So we need to include it somewhere. We could add a paragraph under About the role that includes company description and culture. Or we could add a separate section with a heading like "About HARMAN" but that's not in the list; but the instruction says "e.g." meaning examples, not exhaustive. It might be okay to add other headings as long as they are meaningful. However to be safe, we could incorporate company description and culture into About the role section (since it's about the role at the company). Or we could add a section "About HARMAN" as a heading; it's not prohibited. The instruction didn't forbid other headings, just gave examples. It said "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use other headings if needed. But we should avoid creating sections with filler. So we can add a section "About HARMAN" with the company description. And maybe "You Belong Here" as "Culture". But we risk many sections. However we can combine them. Better approach: Create sections: - About the role (includes intro, What You’ll Be Part Of, Your Team) - Responsibilities (How You’ll Make An Impact) - Requirements (What Makes You A Strong Fit) - Qualifications (Bonus Points if You Have) - Benefits (What You Can Expect + Benefits description) - Pay (Pay Transparency) - Schedule (Things To Know: location, hybrid schedule, travel, background check) - About HARMAN (company description) - Culture (You Belong Here) That's many sections but each has substantive content. The instruction says "Prefer a few substantive sections over many thin ones." These are substantive. Could we combine About HARMAN and Culture into About the role? Possibly but that would make About the role very long. Still okay. But we need to avoid duplication: The intro already includes "A Career at HARMAN Corporate..." which is somewhat company description. The About HARMAN section is more detailed. Could merge. Given the instruction to prefer