Head of Policy

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: 1. Use

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

• for lists of duties/requirements/benefits, and

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

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting: The posting has: - Overview/About the organization (PowerLines) - About the role (Head of Policy) - Key Responsibilities (broken into sub-sections: Team Leadership, Policy Campaign Strategy and Execution, Policy Product Development, Research, and Analysis, Policymaker Education and Engagement, Coalition Building and Stakeholder Engagement, External Representation and Fundraising, Cross-Team Coordination) - Requirements/Qualifications (Required and Preferred) - Benefits/Compensation (salary range and benefits package) I need to structure this into semantic HTML with h3 headings and appropriate lists/paragraphs. Sections I'll create: 1. About the role (or Overview) - but the rule says "About the role" as a heading example. The posting has an "Overview" section that describes the organization and the role. I'll use "About the role" as h3. 2. Responsibilities - with sub-sections? The rules say use h3 for section headings. The responsibilities have multiple categories. I could make each category an h3, but that might be too many thin sections. The rule says "Prefer a few substantive sections over many thin ones." But the responsibilities are detailed and distinct. I'll make "Responsibilities" as h3 and then use sub-lists? But the rule says use h3 for section headings. The examples include "Responsibilities" as a heading. I think I should have "Responsibilities" as h3 and then list the key responsibilities as bullet points, but they are grouped. I could keep the groupings as subheadings using h4? But the rule only mentions h3. It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid h4, but it says use h3 for section headings. I'll use h3 for main sections and maybe h4 for sub-sections? But the instruction says "use

  for section headings". It doesn't say not to use h4. However, to be safe, I'll use h3 for main sections and within Responsibilities, I'll use a list of the responsibility areas with sub-lists? That might be messy. Better: Create an h3 for "Responsibilities" and then use a

  with each top-level responsibility as a
  • containing a for the category and then a nested
    for the bullet points. That preserves structure. Similarly for Qualifications: Required and Preferred. Benefits: Compensation and Benefits. Also, there is metadata: remote position, travel 10-20%, reports to Founder/Executive Director, headquarters in DC. That can go in a short

    under About the role or a separate "Details" section? The rule says fold minor metadata into a short

    or drop it. I'll include a paragraph in About the role. Also note: "PowerLines is currently also recruiting for a Head of Regulatory role..." - that's minor metadata, can be dropped or folded. Now, let's craft the HTML. I'll start with an h3 "About the role" and a paragraph describing the organization and role, including location, remote, travel, reporting. Then h3 "Responsibilities" with a list of the seven categories, each with sub-bullets. Then h3 "Qualifications" with two sub-sections: Required and Preferred. I'll use h4 for those? Or just use strong labels within a list. Since the rule says use h3 for section headings, I'll keep Qualifications as h3 and then use

    for Required and Preferred? The rule doesn't mention h4. But it's semantic. I think it's okay. However, to strictly follow "use

    for section headings", maybe I should not use h4. I'll use within list items. Alternatively, I can make "Required Qualifications" and "Preferred Qualifications" as h3? That would be two sections. But they are subsections of Qualifications. The rule says "include a section ONLY when the posting has real, specific content for it". Both have content. I could make them separate h3 sections: "Required Qualifications" and "Preferred Qualifications". That might be better. Similarly, Benefits: "Compensation and Benefits" as h3. Let's outline:

    About the role

    ...overview...

    Responsibilities

    • Team Leadership
      • Oversee Policy Team...
      ...
    ...

    Required Qualifications

    • 10+ years of experience...
    ...

    Preferred Qualifications

    • Deep knowledge of energy...
    ...

    Compensation and Benefits

    Expected salary range: $175,000-$225,000...

    • Unlimited PTO
    • Paid holidays
    • Health insurance
    • 401k employer match
    • Sick leave
    • Health and wellness benefits

    That seems good. Now, I need to ensure I preserve ALL substantive information. I'll copy the bullet points verbatim from the posting. Let's extract the responsibilities: Team Leadership: - Oversee Policy Team currently consisting of a full-time State Policy Lead, part-time Policy Advisors, and part-time Senior Advisors - Lead Policy Team meetings on a weekly basis and set team priorities, manage workflow and workstreams across team, and ensure quality control on all policy products - Serve on PowerLines' executive leadership team and provide counsel on policy issues, opportunities, developments, and strategy - Own day-to-day policy and team management decisions, and bring decisions on programmatic strategy, flagship products, highest-stakes external relationships, budget, senior hiring, and final personnel actions to the leadership team - Provide mentorship to junior team members on programmatic and organizational issues - Lead hiring for the Policy Team as it grows, in partnership with the Chief of Staff, who owns the recruitment and hiring process, with the Executive Director making final decisions on senior hires - Define scopes for and direct the work of Senior Advisors and policy consultants Policy Campaign Strategy and Execution: - Develop PowerLines' annual policy strategy to be updated on a regular basis, including identification of team goals, OKRs, and internal calendar with key dates and timelines, with the Executive Director - Develop campaign strategy for 2027 policy campaigns across states, including recommending priority states and engagement strategy in each state - Execute policy engagement strategy with policymakers, particularly at the state level including governors, state legislators, and state energy offices, including partnership and coalition building, policymaker education, and technical assistance - Vet and recommend consultants and lobbyists as needed, with final engagement and budget decisions made by the Executive Director - Oversee regular tracking and reporting of PowerLines' policy impact to iteratively inform strategy development and execution - Oversee compliance with lobbying registration and filing requirements Policy Product Development, Research, and Analysis: - Oversee development and distribution of key PowerLines policy products, including policy playbooks, dashboards, and issue briefs, with Executive Director sign-off on flagship products - Oversee the tracking and monitoring of key utility regulatory policy developments and legislation happening across the country - Lead drafting and preparation of written communications, testimony, and thought leadership as needed Policymaker Education and Engagement: - Serve as a key ambassador of PowerLines with policymakers including governors, state legislators, and state energy offices, coordinating with the Executive Director on the highest-stakes relationships - Lead relationship building with key policymaker network partners, including National Governors Association, Western Governors Association, Midwestern Governors Association, National Conference of State Legislatures, National Association of State Energy Officials, and other policymaker networks - Oversee provision of research and technical assistance to support policymakers - Oversee development and execution of "utility regulation 101" briefings for policymakers and partners less familiar with utility regulatory issues Coalition Building and Stakeholder Engagement: - Conduct landscape assessment of current and target coalition partners to engage on utility regulatory issues - Build partnerships with coalition partners reflecting PowerLines' commitment to bipartisan, multi-sectoral, and cross-customer class engagement - Lead relationship building with key coalition partners, including managing existing coalitions and partners and building new ones - Coordinate with the Executive Director on engagement with senior policymakers and key partners External Representation and Fundraising: - Represent PowerLines on external engagement and speaking opportunities, including media inquiries, event speaking opportunities, reporter and podcast interviews, committee hearings, workshops, and roundtables, in coordination with the Executive Director and Communications Team - Support Strategy & Operations Team in developing donor communications, grant, and other fundraising materials - Regularly update and maintain an internal tracker of major policy accomplishments and successes to inform PowerLines' policy impact - Attend relevant events and conferences (e.g., NGA, NCSL) Cross-Team Coordination: - Coordinate with Regulatory Team and Communications Team on issues and workstreams impacting multiple teams - Coordinate with Communications Team to equip reporters and other media partners with key 101-level materials relevant to policy work - Coordinate with Communications Team on policy content in communications products - Partner with the Chief of Staff, who owns cross-team prioritization and capacity allocation, to plan Regulatory and Communications Team support for policy priorities Required Qualifications: - 10+ years of experience in state or federal policy, legislative affairs, or advocacy - Experience managing, mentoring, and developing staff, including strong leadership skills and emotional intelligence - Proven record of developing and executing multi-state legislative or policy campaigns that delivered results - Strong relationships with governors' offices, state legislators, and policymaker networks such as NGA and NCSL - Experience working across the political spectrum and keeping positions nonpartisan in a politically sensitive issue area - Experience building and managing coalitions with diverse partners - Comfort building systems and processes in a startup environment - Excellent writer and communicator who can turn complex policy into clear products for policymakers and represent an organization in a diverse range of settings - Comfort operating as both a senior strategic leader and a hands-on individual contributor on a small team in a rapidly growing organization Preferred Qualifications: - Deep knowledge of energy, utility, or consumer protection policy, including how legislation interacts with utility regulation - Established relationships with consumer advocates, public utilities commissions, and regulatory networks - Experience working in or with state government, such as governor's office, state legislator's office