Manager-State & Local Public Affairs

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real content. Remove boilerplate. We need to parse the posting. Key sections: - Position Overview / Job Description: we can treat as "About the role" maybe. The posting includes "Position Overview JOB DESCRIPTION". We'll create a

About the role

with prose summarizing the overview (but we must preserve all substantive info, not summarize away detail). However we cannot invent or summarize away detail. We need to preserve all substantive information; we can include the overview text as a

. That's okay. - Responsibilities: there is a list of duties. We'll create

Responsibilities

with

• each duty. - Education: there is "Education QUALIFICATIONS". Actually they have "Education" then "QUALIFICATIONS". We'll treat Education as a heading? The instruction says use h3 for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Qualifications (maybe includes Education, Experience/Specific Knowledge, Certifications, etc). But we need to decide. We have sections: Education, Experience/Specific Knowledge, Certifications, Licenses & Registrations, Competencies, Skills & Abilities, Physical Demands, Working Conditions, Supervisory Responsibility, Preferred Education..., Compensation, About Us, etc. We need to include only sections with real content. Many of these have content. We should avoid repeating job title as heading. Also avoid Job ID etc. We need to output only HTML fragment. Let's extract content. Position Overview: "Position Overview JOB DESCRIPTION The Manager of State & Local Public Affairs (Eastern) is a key position within the Government and Public Affairs (G&PA) department and is responsible for executing the company’s external affairs strategies. This position provides comprehensive support to the Projects, Commercial, and Operations departments by representing the company in relevant communities and with key stakeholders such as elected officials, regulatory agencies, nongovernmental organizations,and industry associations. Candidates should have an extensive knowledge of the energy industry and strong relationships across the region which could include, but is not limited to, IL, IN, OH, WV, and KY. The position will be open to remote consideration, especially in the OH region." We'll put that in a

  under About the role. Responsibilities list: "Essential duties and responsibilities: Develop strong external relationships with local communities, businesses, government officials, industry associations, advocacy groups, and non-governmental organizations. Develop engagement strategies, approaches, and tools to achieve business objectives and minimize risk. Monitor and analyze local and state government policy changes, elections, city and town ordinances, board, and council activities; identifying emerging issues early and building fit-for-purpose advocacy plans to achieve company objectives. Ensure proactive, timely, and effective communications with community leaders on siting, permitting, construction, and maintenance activities.Represent Tallgrass at community gatherings or forums and serve as the local point of contact for stakeholders. Advise senior leadership on potential risks and opportunities and provide guidance on how to navigate complex regulatory and political environments, aimed at the most favorable long-term results for the company." We'll split each sentence as

• . Education: "Bachelor’s degree from an accredited institution in Public Policy, Communications, Public Relations, or a related discipline." Experience/Specific Knowledge: "A minimum of seven (7) years of experience in the energy industry serving in government affairs, lobbying, or public affairs roles.Demonstrated superior leadership outcomes in the areas of leading self, leading others, and leading an organization. Proven ability to drive positive change and continuous improvement.Proven track record of successful, innovative leadership and delivery of performance results.Intermediate proficiency level in MS Office applications that may include but are not limited to Excel, Word, Teams, Access, PowerPoint and Outlook." Certifications, Licenses & Registrations: "Must possess and maintain a valid driver’s license and a driving record satisfactory to the company and its insurers (for travel)." Competencies, Skills & Abilities: "Excellent oral and written communication skills.Strong organizational skills and ability to multi-task.Strong analysis, decision making, and logic skills.Self-motivated with a high level of initiative.Must be able to perform all essential and marginal functions of the job.Must be able to work with a team, take direction from management, adhere to required work schedules, focus attention on details, and follow work rules.Ability to successfully perform multiple tasks with strict deadlines.Ability to organize and prioritize daily work.Job level commensurate with experience and skill sets; position will be filled depending on qualifications, experience, and skill sets of the successful candidate." Physical Demands: long paragraph. We'll include as a section maybe "Physical Demands". But the instruction only lists certain headings; but we can still use h3 for any section heading we deem appropriate? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Probably we should stick to those headings where applicable. Physical Demands maybe not needed as separate heading; could be part of Requirements or Qualifications? But we have to preserve all substantive info; we could include it under a heading like "Requirements" (which could encompass Education, Experience, Certifications, Physical Demands, Working Conditions). However the instruction says we can use those headings; we can also create other headings if needed? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the allowed headings; we should not create others like Physical Demands. So we need to map content into those allowed headings. Thus we need to decide which sections to include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Qualifications (Education, Experience, Certifications), Skills (Competencies, Skills & Abilities), Benefits (About Us includes benefits), Pay (Compensation), Schedule maybe not present (no schedule info). Working Conditions maybe could be part of Requirements? But we don't have a heading for Working Conditions; we could fold into Requirements or Qualifications? The instruction says we can use Requirements heading for any list of duties/requirements/benefits. Actually they said: Use

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

    for prose. So Requirements heading could contain requirements like education, experience, certifications, physical demands, working conditions. But they also have Qualifications heading separate. Might be overlapping. But we need to follow instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have those headings. We need to decide what goes where. Probably: - About the role: overview paragraph. - Responsibilities: list of duties. - Requirements: maybe includes Education, Experience/Specific Knowledge, Certifications, Licenses & Registrations, Physical Demands, Working Conditions? But they also have Qualifications heading; maybe Qualifications is for education/degrees etc. However we can't have both Requirements and Qualifications with overlapping content; but we can split: Qualifications for education and experience; Requirements for physical demands, working conditions, certifications? But certifications could be qualifications too. Better to follow typical job posting: Qualifications includes education, experience, certifications. Skills includes competencies. Benefits includes benefits. Pay includes salary. Schedule maybe not present. Thus we can omit Requirements heading if not needed; but we need to include only when posting has real specific content for it. If we don't have distinct "Requirements" beyond what's covered in Qualifications, Skills, etc., we may omit Requirements. Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. Check if we have Schedule: none. Now we need to ensure we don't include filler like "Job level commensurate with experience and skill sets; position will be filled depending on qualifications, experience, and skill sets of the successful candidate." That's under Competencies, Skills & Abilities but it's somewhat filler; but it's still substantive? It's a statement about job level; we can keep it. We must not include boilerplate like EEO, legal, application instructions, etc. So we need to strip those. Now let's extract Benefits from About Us section: "Tallgrass was named one of the Top Workplaces USA and highlighted in Colorado's Top Workplaces for the past seven consecutive years. Tallgrass is a leading energy infrastructure company focused on safely, reliably, and sustainably delivering the energy and services that power our nation and enable our quality of life. At Tallgrass, we value our teams and strive to create an environment where employees feel respected, and their contributions are valued. We aim to support employees' physical, mental, and financial well-being through a comprehensive Total Rewards Program. Industry competitive payHealth insurance package options that include Flexible Spending & Health Savings AccountsInfertility CoverageParental Leave401(k) with up to a 6% match that vests immediately plus an employer discretionary contribution of up to 4%Wellness Programs and Mental Health ResourcesEmployer-paid life insurance, short-term disability, and long-term disability coverageCritical Illness & Accident InsuranceVacation, sick days, paid caregiver leave, volunteer and bereavement paid time offIdentity theft protectionAnnual discretionary bonusGenerous Tuition Reimbursement ProgramCompany-paid holidays and floating holidaysCompany vehicle (if applicable)Employee discounts; vehicles, tires, cellular plans, and moreNetworking and employee engagement eventsPersonal development to grow your career with us based on your strengths and interests" We need to format as list maybe. But it's a paragraph with no clear separation. We could turn into

    • each benefit separated by maybe punctuation. But we must preserve all substantive information; we can keep as

      but the instruction says use

      • for any list of duties/requirements/benefits. So we should make a list. We need to split benefits into items. Let's parse: - Industry competitive pay - Health insurance package options that include Flexible Spending & Health Savings Accounts - Infertility Coverage - Parental Leave - 401(k) with up to a 6% match that vests immediately plus an employer discretionary contribution of up to 4% - Wellness Programs and Mental Health Resources - Employer-paid life insurance, short-term disability, and long-term disability coverage - Critical Illness & Accident Insurance - Vacation, sick days, paid caregiver leave, volunteer and bereavement paid time off - Identity theft protection - Annual discretionary bonus - Generous Tuition Reimbursement Program - Company-paid holidays and floating holidays - Company vehicle (if applicable) - Employee discounts; vehicles, tires, cellular plans, and more - Networking and employee engagement events - Personal development to grow your career with us based on your strengths and interests Also earlier sentences about Top Workplaces etc could be part of About Us but not a benefit; we could include as prose under Benefits heading maybe as a

        before list. Now Pay: "The annual salary range for this position will be $125,600-$188,400/yr." Also later there is a Compensation section with disclaimer: "Compensation: Compensation ranges are provided in good faith based on what we anticipate when researching wages for this position at the state and national levels. We may ultimately pay more or less than the posted range. This salary range may also be modified in the future." That's also compensation info but includes disclaimer; we should include the range and maybe the disclaimer? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the disclaimer as part of Pay section. However the disclaimer is somewhat boilerplate but it's about compensation;