President

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Key sections: - About Korrus (company description) maybe "About the role"? Actually "About Korrus" is company description. Could be "About the role" is a section describing the role. The posting includes "The role" paragraph. So we can have

About the role

with that paragraph. - Responsibilities: The role description includes responsibilities: "You will work with product development, engineering, manufacturing, supply chain, finance and sales. You will sit above the functional layer, with a direct mandate from the CEO and the standing to drive any function to a result, without borrowing anyone else's authority to do it." Also "Be the operator who makes the organization hum." Could be responsibilities. - Requirements/Qualifications: The "Who We Are Looking For" and "What We're Looking For" sections list qualifications. Could combine into Requirements or Qualifications. We need to decide which heading to use. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple: About the role, Responsibilities, Requirements, Qualifications, Skills maybe. But we should avoid thin sections. Better to combine similar content into one section like "Requirements" covering all qualifications. Or we could have "Qualifications" and "Skills". Let's see content: Who We Are Looking For: bullet-like paragraphs describing profile: run real things, carried complex cross-functional work, builder's hands, hardware and manufacturing fluency, meaningful hands-on use of AI, presence and edge, business acumen. What We're Looking For: repeats similar: Proven senior execution, builder's hands, hardware and manufacturing fluency, meaningful hands-on use of AI, presence and edge, business acumen. Thus we can combine into a single "Qualifications" section with bullet list. Responsibilities: The role description includes responsibilities: "You will work with product development, engineering, manufacturing, supply chain, finance and sales. You will sit above the functional layer, with a direct mandate from the CEO and the standing to drive any function to a result, without borrowing anyone else's authority to do it." Also "Be the operator who makes the organization hum." Also "Your mandate is to take that to zero." Could be responsibilities. Also "Logistics And Compensation" includes contract-to-hire, remote US, overlap with Pacific hours, travel to Southern California, reports to CEO. That could be "Logistics" maybe but not in allowed headings. Could be placed under "Schedule" or "Benefits"? Actually schedule: remote US, overlap with Pacific working hours, travel to Southern California and to sites as work requires. That's schedule info. Compensation: "Compensation commensurate with the seniority of the role and the trial structure, discussed directly." That's vague; we should not create Pay section unless posting actually states them. It says compensation commensurate... that's not specific; it's placeholder. According to rule: 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. Here compensation is vague, not specific numbers. So we should NOT create a Pay section. Schedule: they give remote US, overlap with Pacific working hours, travel to Southern California and to sites as work requires. That's specific enough? It's not vague like "varies". It states remote US, overlap with Pacific hours, travel to SoCal. That's specific. So we can create a Schedule section with that info. Benefits: Not mentioned. So no Benefits section. Thus sections: About the role, Responsibilities, Qualifications (or Requirements), Schedule. We need to use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, visa sponsorship, application instructions (Send us your resume, Briefly describe a time...). Also remove "To be considered Send us your resume Briefly describe a time you were responsible for something you had no authority over and got it done anyway." That's application instruction; remove. Also remove "Korrus is an Equal Opportunity Employer..." etc. Also remove "This position is not eligible for current or future visa sponsorship." Also remove "Logistics And Compensation" heading? We'll incorporate relevant info into Schedule. We need to keep the company description "About Korrus". Could be part of About the role? Or we could have a separate "About Korrus" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add About Korrus as a heading. We could incorporate company description into About the role paragraph? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. It might be okay to have other headings but they gave examples. Safer to stick to those. So we can put company description under About the role as prose. Thus About the role section will contain both description of the role and company overview. Now we need to extract responsibilities: The role paragraph: "This is the person who runs execution across the company. The CEO currently spends roughly half his time driving granular execution across sales, marketing, engineering, operations, and manufacturing. Your mandate is to take that to zero. Be the operator who makes the organization hum. You will work with product development, engineering, manufacturing, supply chain, finance and sales. You will sit above the functional layer, with a direct mandate from the CEO and the standing to drive any function to a result, without borrowing anyone else's authority to do it." We can turn duties into bullet list under Responsibilities. Qualifications: combine Who We Are Looking For and What We're Looking For into bullet list. Let's extract bullet points: - Proven senior execution: carried complex, cross-functional work to a result you were accountable for, with no formal authority over most of the people involved; can point to outcomes you owned, not initiatives you supported. - Builder's hands: built things yourself, product, systems, or both; can sit in an engineering or operations review and challenge an estimate on the merits rather than defer to the room. - Hardware and manufacturing fluency: comfortable on a factory floor and in a supply chain; understand what it takes to make and ship a physical product. - Meaningful, hands-on use of AI: genuinely fluent with modern AI tools and agentic workflows in how you actually work; ideally have built something with them that other people came to rely on, not just a line on a skills list. - Presence and edge: can command a room of senior people and drive action. - Business acumen: real comfort with a P&L and general fluency with financial statements. Also from Who We Are Looking For: "You have run real things and want to run more." "You have carried complex, cross-functional work to a result you owned, and you are looking for a company where the whole business is the canvas rather than one function." "You are an operator who builds." "You do not just direct the work; you have built the systems, the products, or the automation yourself, and you are fluent enough to challenge an engineer or an operator on the merits." "You want the number-two seat." "You want proximity to every decision and the authority to act on it." "You have something to prove." "You would rather own the outcome, with your name on it, than build the recommendation and watch someone else run with it." "What every one of those people has in common is capacity, acumen, presence, and the willingness to be measured on what ships." We need to preserve all substantive info; we can include these as bullet points as well, but avoid duplication. Many overlap with Qualifications. We'll combine them into a comprehensive list, ensuring we don't lose any detail. Let's list all distinct points: 1. Have run real things and want to run more. 2. Have carried complex, cross-functional work to a result you owned. 3. Looking for a company where the whole business is the canvas rather than one function. 4. Are an operator who builds. 5. Do not just direct the work; have built the systems, products, or automation yourself; fluent enough to challenge an engineer or operator on the merits. 6. Want the number-two seat. 7. Want proximity to every decision and the authority to act on it. 8. Have something to prove. 9. Would rather own the outcome, with your name on it, than build the recommendation and watch someone else run with it. 10. Possess capacity, acumen, presence, and willingness to be measured on what ships. 11. Proven senior execution: carried complex, cross-functional work to a result you were accountable for, with no formal authority over most of the people involved; can point to outcomes you owned, not initiatives you supported. 12. Builder's hands: built things yourself, product, systems, or both; can sit in an engineering or operations review and challenge an estimate on the merits rather than defer to the room. 13. Hardware and manufacturing fluency: comfortable on a factory floor and in a supply chain; understand what it takes to make and ship a physical product. 14. Meaningful, hands-on use of AI: genuinely fluent with modern AI tools and agentic workflows in how you actually work; ideally have built something with them that other people came to rely on, not just a line on a skills list. 15. Presence and edge: can command a room of senior people and drive action. 16. Business acumen: real comfort with a P&L and general fluency with financial statements. Some duplicates: #1 similar to #11; #2 similar to #11; #4 similar to #12; #5 similar to #12; #15 similar to #10 presence; #10 includes capacity, acumen, presence, willingness to be measured on what ships. We'll keep but avoid exact duplicates. We can produce a bullet list that captures all unique points, maybe grouping similar. Now Responsibilities bullet list: - Run execution across the company. - Reduce CEO's time spent on granular execution across sales, marketing, engineering, operations, and manufacturing to zero. - Be the operator who makes the organization hum. - Work with product development, engineering, manufacturing, supply chain, finance, and sales. - Sit above the functional layer with a direct mandate from the CEO and the standing to drive any function to a result without borrowing anyone else's authority. Now Schedule bullet list (or prose): Remote (US), with meaningful overlap with Pacific working hours, and travel to Southern California and to sites as the work requires. We could put as

  Remote (US), with meaningful overlap with Pacific working hours, and travel to Southern California and to sites as the work requires.

  Now About the role paragraph: combine company description and role overview. Company description: "Korrus is transforming the way people interact with light. We are the leader in human-centric lighting, built on more than 500 patents in spectral and circadian technology, and pioneers in Human Light Interaction, the next frontier in human health and wellness." Role overview: "This is the person who runs execution across the company. The CEO currently spends roughly half his time driving granular execution across sales, marketing, engineering, operations, and manufacturing. Your mandate is to take that to zero. Be the operator who makes the organization hum. You will work with product development, engineering, manufacturing, supply chain, finance and sales. You will sit above the functional layer