Senior Writer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate like EEO, legal, navigation, cookie, application instructions, interview process, why work for us, etc. Keep substantive info. We need to parse the posting. Let's extract sections: - About the role: The first paragraph: "Senior Staff Writer HighSpeedInternet.com is seeking a versatile writer who brings a combination of content expertise and marketing instincts to write for and residential internet. We’re looking for a driven, experienced copywriter who cares about user experience." Actually there is a typo: "write for and residential internet". Probably "write for residential internet". We'll keep as is. - Responsibilities: The list under "The Impact You Will Make" bullet points. - Requirements/Qualifications/Skills: The "What You Bring" list. - Benefits: The "Perks That Set Us Apart" list. - Pay: Not mentioned. No pay info. So omit Pay section. - Schedule: There is schedule info: "Clearlink is a remote-friendly company... This is a remote-first role for candidates who are located outside of Utah and outside of commuting distance. For candidates residing within 50 miles of our Salt Lake City, Utah office, a hybrid schedule of 2-3 days in-office is required." Also later under Perks: "Flex Schedule: This role is remote-first, with a hybrid requirement for team members located within a 50-mile radius of our Salt Lake City, Utah office. For locals, expect in-office collaboration on Tuesdays and Thursdays, with Wednesdays designated as a flex day based on team and manager needs. Remaining workdays are remote, depending on role requirements." So schedule content exists. We'll include Schedule section. We must not repeat job title as heading. Use

for each section heading. We need to use

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

  for prose. We must preserve all substantive info; do not invent or summarize away detail. Remove boilerplate: interview process, why work for us, Clearlink Partners & Awards, values, accommodation statement, etc. Also remove "Interviewing at Clearlink" etc. Also remove "Clearlink Partners & Awards" etc. Also remove "Clearlink Values (CLEAR): ..." etc. Also remove "Committed to accessibility..." etc. Also remove "Your unique strengths matter..." etc. Also remove "Since 2001..." etc. Also remove "Why Work For Us" etc. Also remove "Clearlink Partners & Awards:" etc. Also remove "Clearlink Values (CLEAR): ..." etc. Also remove "At Clearlink, we go beyond the basics..." maybe part of Perks? Actually that sentence is after perks list: "At Clearlink, we go beyond the basics, ensuring your experience with us is not just professionally fulfilling but personally enriching too." That's fluff but maybe considered boilerplate? It's not a specific benefit; could be considered generic. Safer to remove. Also remove "Clearlink is a remote-friendly company, prioritizing virtual and in-person collaboration." That's schedule info; keep. Now produce HTML. Structure:

  About the role

  Senior Staff Writer HighSpeedInternet.com is seeking a versatile writer who brings a combination of content expertise and marketing instincts to write for and residential internet. We’re looking for a driven, experienced copywriter who cares about user experience.

  But maybe we can combine first two sentences into one paragraph. Then Responsibilities:

  Responsibilities

  • Research topics in the Internet space and turn that information into useful, engaging, authoritative stories
  • Pitch ideas that align with website strategy and expertise
  • Use AI to create new story ideas, angles and data-driven content
  • Develop sources and conduct interviews
  • Maintain existing content to make sure it remains up-to-date and accurate and meets content quality standards
  • Ensure content aligns with brand voice, positioning, and project type
  • Collaborate with managing editor, brand director, SEO specialists, project managers, and designers to own strategic projects
  • Balance numerous tasks, including writing new pieces, rewrites of existing content, and smaller updates
  • Own high-priority, high-impact writing projects
  • Track and analyze the performance of content, making recommendations to improve performance
  • Stay up to date on digital marketing and UX best practices and help share standard methodologies with other team members
  Then Requirements/Qualifications/Skills: The posting has "What You Bring". Could split into Requirements (experience), Qualifications (education?), Skills (specific). But we can combine into one section maybe "Requirements". However instructions: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include multiple if content exists. Let's parse "What You Bring": - 6+ years’ experience in journalism, content marketing, or related field - Established expertise in writing, with a strong portfolio of consumer-focused content - An established understanding of, and use of, AI in your workflow - Ability to quickly research and write clean, in-depth content that requires minimal editing - Solid communication and organizational skills - Ability to take and provide constructive feedback - Strong grasp of marketing trends and UX and SEO best practices - Excellent spelling and grammar skills - Solid understanding of AP style, Google Analytics and/or other analytics platforms - Experience with Google Suite, Microsoft Excel, Adobe Acrobat, Airtable, or similar software applications We could separate into Requirements (experience), Qualifications (maybe education not mentioned), Skills (the rest). But we don't have explicit education. Could put all under Requirements. Or we could make two sections: Requirements and Skills. Since we have no Qualifications content, we should not create a Qualifications heading with filler. So we can have Requirements and Skills. Let's decide: Requirements: 6+ years’ experience in journalism, content marketing, or related field; Established expertise in writing, with a strong portfolio of consumer-focused content; Ability to quickly research and write clean, in-depth content that requires minimal editing; Solid communication and organizational skills; Ability to take and provide constructive feedback; Strong grasp of marketing trends and UX and SEO best practices; Excellent spelling and grammar skills; Solid understanding of AP style, Google Analytics and/or other analytics platforms; Experience with Google Suite, Microsoft Excel, Adobe Acrobat, Airtable, or similar software applications. Skills: An established understanding of, and use of, AI in your workflow. Also maybe "Ability to quickly research..." but that's more skill. But we need to avoid duplication. Let's think: The list includes both experience and skills. Could split: Requirements (experience) and Skills (specific abilities). But we need to ensure we don't lose any info. Simplify: Use one section "Requirements" containing all bullet points. That's acceptable; we don't need Qualifications or Skills separate if they'd be thin. The instruction: Prefer a few substantive sections over many thin ones. So we can combine into Requirements. Thus we will have:

  Requirements

  • 6+ years’ experience in journalism, content marketing, or related field
  • Established expertise in writing, with a strong portfolio of consumer-focused content
  • An established understanding of, and use of, AI in your workflow
  • Ability to quickly research and write clean, in-depth content that requires minimal editing
  • Solid communication and organizational skills
  • Ability to take and provide constructive feedback
  • Strong grasp of marketing trends and UX and SEO best practices
  • Excellent spelling and grammar skills
  • Solid understanding of AP style, Google Analytics and/or other analytics platforms
  • Experience with Google Suite, Microsoft Excel, Adobe Acrobat, Airtable, or similar software applications
  Now Benefits: The perks list. We need to capture each bullet with emojis? Keep the text but maybe drop emojis? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Emojis are part of the posting; they are not substantive? They are decorative but could be considered part of the content. Safer to keep them as they appear. However HTML may treat emojis as characters; fine. We'll produce
  • for each perk. List: - 🩺 Healthcare: We offer low-cost, competitive health coverage (domestic partners included!) with employer-paid counseling services. - 💰 Invest in the Future: Enjoy 401(k) matching after just two months of employment, with employer matching starting at ~3%. - 🧘‍♀️ Lifestyle Spending Stipends: Access an employer-paid spending account for physical, financial, and emotional wellbeing expenses. - 🏝️ Flexible Time Off: We offer competitive time-off balances that accrue weekly, just like your paycheck. (Yes, we’re paid weekly too!) - 👶🏻 Parental Leave: We provide 2 weeks of paid parental leave during the first year and up to 9 weeks after one year of employment. - ✈️ Generous Paid Holidays: Celebrate cultural diversity with additional flex holidays in addition to our company paid holidays. - 🧑‍💻 Flex Schedule: This role is remote-first, with a hybrid requirement for team members located within a 50-mile radius of our Salt Lake City, Utah office. For locals, expect in-office collaboration on Tuesdays and Thursdays, with Wednesdays designated as a flex day based on team and manager needs. Remaining workdays are remote, depending on role requirements. - 🛟 Comprehensive Life Insurance: Ensure peace of mind with coverage that extends beyond the workplace with employer paid life insurance (including coverage for dependents and spouses). - 🤝 Employee Resource Groups (ERGs): Join us in fostering connections, celebrating diversity, and providing a supportive community for all. Note: The Flex Schedule bullet duplicates schedule info; we also have a Schedule section. Might be redundant but we need to preserve all substantive info. However we should avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't say to deduplicate. So we can keep both. However the schedule section will also contain similar info; we can keep both. But we might want to avoid duplication by moving schedule info to Schedule section and not include in Benefits. However the Flex Schedule bullet is under Perks That Set Us Apart; it's a perk. If we remove it from Benefits, we lose that perk description. But we could keep it in Benefits and also have Schedule section with schedule details (maybe less detailed). The instruction: Prefer a few substantive sections over many thin ones. Having both may be okay. But we could combine schedule info into Schedule section and keep Benefits without the Flex Schedule bullet. However that would remove the Flex Schedule perk from Benefits, which is substantive. The instruction says preserve ALL substantive information. So we need to keep that info somewhere. If we put it in Schedule section, we still preserve it. So we can omit it from Benefits to avoid duplication. That seems reasonable: we keep schedule info in Schedule section, and we keep other benefits. Thus Benefits list will exclude the Flex Schedule bullet. Now Schedule section: We need to include schedule details from both the earlier paragraph and the Flex Schedule bullet. We have: - Clearlink is a remote-friendly company, prioritizing virtual and in-person collaboration. This is a remote-first role for candidates who are located outside of Utah and outside of commuting distance. For candidates residing within 50 miles of our Salt Lake City, Utah office, a hybrid schedule of 2-3 days in-office is required. - Flex Schedule: This role