Senior News Editor

We need to produce HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Must not repeat job title. No Job ID etc. Remove boilerplate. Include only sections with real content. Let's parse the posting: Job ID, Job Views, Location, Zip Code, Job Category, Employment Type, Salary, Posted date: these are metadata; we can fold minor metadata into a short

or drop it. Probably we can include location and maybe salary in Pay section. Salary is given: $77600-$93100 per year. So we need a Pay section with that. Benefits: described: health, dental, vision insurance; company paid short- and long-term disability; flexible spending accounts; 403(b) savings plan with company match and a free on-site fitness center. Three weeks of vacation, twelve paid holidays, two floating personal days, and paid sick and parental leave. So Benefits section. Schedule: Not explicitly given; it's full-time, exempt, on-site. Could infer schedule but not given explicit hours. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Schedule not stated explicitly (just full-time). Might be considered implied but not explicit. Safer to omit Schedule section. About the role: The job description paragraph: "The Senior News Editor helps shape NHPR's journalism strategy..." etc. That's about the role. So we can have About the role section. Responsibilities: Essential Duties Include list, plus Other Responsibilities Include list. Combine into Responsibilities section with

• . Requirements: Job Requirements Preferred Experience list. Could be Requirements section. Qualifications: maybe overlapping with Requirements; but we can treat Requirements as qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include. We have content for About the role, Responsibilities, Requirements (or Qualifications), Benefits, Pay. Skills maybe part of Requirements. We could split: Requirements (experience) and Skills (specific skills). But we need to avoid thin sections. Better to combine into Requirements (includes experience and skills). Or we could have Requirements and Skills separate if we have distinct content. Let's see: The posting lists "Preferred Experience" with bullet points: minimum 7 years journalism experience, broadcast journalism experience desirable, prior editing experience strongly preferred, prior experience on climate/environment beat preferred, comfort working in a digital newsroom, ability to manage a team of reporters in a hybrid environment, excellent organizational skills and ability to manage multiple projects simultaneously, ability to meet tight deadlines, ability to write quickly for broadcast, knowledge of relevant FCC rules and regulations, excellent people skills, Bachelor's degree in a related subject area or relevant experience. That's a mix of experience and skills. Could split: Requirements (experience) and Skills (skills). But we risk thin sections. However we have enough content for both maybe. But we must not create sections with filler like "not specified". We have real content for both. Let's decide: We'll include About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We'll not include Qualifications (since we have Requirements and Skills). Or we could include Qualifications instead of Requirements. But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It's okay to omit some. Now we need to preserve all substantive information, not invent or summarize away detail. Must not drop any substantive info. So we need to include all duties, responsibilities, requirements, skills, benefits, pay. We must not include boilerplate like EEO, application instructions, etc. Remove those. We need to format as HTML fragment: use

  for headings,

  • for lists,

    for prose. We need to ensure we don't repeat job title. Let's extract content: About the role: The Senior News Editor helps shape NHPR's journalism strategy, both online and on air. They are an experienced journalist who plays a key role on the newsroom's editorial team, working with reporters and across content teams to ensure NHPR's journalism is timely, useful, and engaging. They manage and edit a small team of reporters and work closely with the VP of News and other newsroom leaders to seek out ways to push our journalism into new, creative and impactful directions. This editor will oversee By Degrees, NHPR’s climate change reporting vertical. We’re looking for someone who will lead this project into its next chapter, set its editorial direction and build a strategy to reach the audiences who are hungry for in-depth and solutions-oriented climate stories. This is a full-time, exempt, on-site role based in Concord, NH, reporting to the VP of News. We could also include location and reporting line here. Responsibilities: Essential Duties Include list: - Work in conjunction with the VP of News and other news editors to plan NHPR's daily and long-term news coverage and publishing strategy. - Manage and edit a small team of reporters; assign daily stories and features to that team and shepherd them to publication. - Help oversee the daily news desk as part of a rotating editorial team, editing and publishing stories for broadcast and on NHPR.org, including newscasts and audio stories, digital projects and features. - Ensure that our journalism adheres to the highest ethical standards and practices. - Act as a face of the newsroom to external audiences as needed. - Participate in on-air fundraising as needed. Other Responsibilities Include: - Pitch, develop and manage occasional special projects and series, overseeing newsroom teams working towards a common editorial goal. - Work in collaboration with NHPR's audience team to ensure our digital journalism reaches large and diverse audiences. - Other duties as assigned. We should combine into one list maybe. Requirements (experience): Preferred Experience list: - A minimum of 7 years of journalism experience. - Broadcast journalism experience is desirable. - Prior editing experience strongly preferred. - Prior experience on the climate/environment beat preferred. - Comfort working in a digital newsroom. - Ability to manage a team of reporters in a hybrid environment. - Excellent organizational skills and ability to manage multiple projects simultaneously. - Ability to meet tight deadlines. - Ability to write quickly for broadcast. - Knowledge of relevant FCC rules and regulations. - Excellent people skills. - Bachelor's degree in a related subject area or relevant experience. - However, we know there are great candidates who may not have all these qualities or who have important skills we may not have outlined above. If this is you, do not hesitate to apply and tell us about yourself. We could keep the last sentence as prose. Skills: maybe we can extract specific skills from the list: ability to manage a team, excellent organizational skills, ability to manage multiple projects, ability to meet tight deadlines, ability to write quickly for broadcast, knowledge of FCC rules, excellent people skills. But these are already in Requirements. To avoid duplication, we could treat Requirements as experience and qualifications, and Skills as separate list of skills. But we risk duplication. The instruction says preserve ALL substantive information; not to invent or summarize away detail. Duplication is okay if it's present in source? The source lists them under "Preferred Experience". It's not separated into skills vs experience. So we could just have one section Requirements (or Qualifications) that includes all those bullet points. That would preserve all info. Then we wouldn't need a separate Skills section. That seems fine. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We need to include Pay: starting salary range $77,600 - $93,100 per year. Also mention that we consider internal equity etc. That's part of Pay? Could include in Pay section. Benefits: as described. We should not include location as separate heading; we can include in About the role paragraph. Now ensure we don't include any boilerplate: remove Job ID, Job Views, Zip Code, Job Category, Employment Type, Posted date, etc. Also remove "Things to Know About Us", "Learn more about NHPR", "To Apply", EEO statement, etc. We must preserve all substantive information: The "Things to Know About Us" includes info about NHPR being independent trusted source, location, mission, accolades, culture values. Is that substantive? It's descriptive about the organization. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Things to Know About Us" is not boilerplate; it's organizational description. Should we keep it? It's substantive info about the employer. The instruction didn't explicitly say to remove that. It says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we can keep "Things to Know About Us" as part of About the role or maybe a separate section like "About the organization". But we only have allowed headings list; we could add a section like "About NHPR" but not in list. Better to incorporate into About the role paragraph? The About the role currently is about the job. We could add a separate section "About NHPR" but not in allowed headings; but we could still use

    for any heading? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list? It says use

    for section headings (e.g. ...). Likely they expect only those headings. Safer to stick to those. So we can incorporate the org description into About the role paragraph as extra prose. Thus About the role paragraph will include both role description and org description. Now we need to ensure we don't miss any substantive info from the job description: The line "The starting salary range for this position is $77,600 - $93,100 based on experience. We also consider internal equity, among other factors, when deciding compensation." That's Pay. Benefits: as described. Now let's craft HTML. We'll start with

    About the role

    then

    ...

    . Inside the p we can include multiple sentences. We need to avoid line breaks? It's fine. Now Responsibilities:

    Responsibilities

    • ...
    combine all duties. We need to list each duty as separate
  • . Let's list: - Work in conjunction with the VP of News and other news editors to plan NHPR's daily and long-term news coverage and publishing strategy. - Manage and edit a small team of reporters; assign daily stories and features to that team and shepherd them to publication. - Help oversee the daily news desk as part of a rotating editorial team, editing and publishing stories for broadcast and on NHPR.org, including newscasts and audio stories, digital projects and features. - Ensure that our journalism adheres to the highest ethical standards and practices. - Act as a face of the newsroom to external audiences as needed. - Participate in on-air fundraising as needed. - Pitch, develop and manage occasional special projects and series, overseeing newsroom teams working towards a common editorial goal. - Work in collaboration with NHPR's audience team to ensure our digital journalism reaches large and diverse audiences. - Other duties as assigned. Now Requirements:

    Requirements

    • ...
    plus maybe a prose sentence about great candidates. List: - A minimum of 7 years of journalism experience. - Broadcast journalism experience is desirable. - Prior editing experience strongly preferred. - Prior experience on the climate/environment beat preferred. - Comfort working in a digital newsroom. - Ability to manage a team of reporters in a hybrid environment. - Excellent organizational skills and ability to manage multiple projects simultaneously. - Ability to meet tight deadlines. - Ability to write quickly for broadcast.