Product Communications Specialist

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. The posting includes a lot of prose about role, responsibilities, etc. We need to parse. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "NOTE: This job description is not intended to be all-inclusive... etc. Also remove "At ClassLink, we believe..." intro? That's about company, maybe part of About the role? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we should not include job title heading. We need to produce sections: maybe About the role (intro), Responsibilities (list of duties), Requirements (list), Benefits (list), maybe Skills? The posting includes "What You'll Bring" which is requirements. Also "Nice to Have". Could combine as Requirements and Nice to Have? But we should only include sections with real specific content. Benefits are listed: Generous Paid Time Off, Parental Leave, Retirement, Comprehensive Health Coverage, Insurance, Perks (Volunteer Time Off, Lifelong Learning, Growth & Development, Supportive Culture, Connection & Community). So we can include Benefits section with ul. Pay and Schedule: not mentioned. So we should NOT include Pay or Schedule sections. Qualifications: maybe same as Requirements? The posting includes "5+ years in product communications... plus a bachelor’s degree". That's qualifications. Could put under Requirements. Skills: maybe not explicit separate list. Could omit. Thus sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (list), Benefits (list). Possibly also "What Success Looks Like" could be considered responsibilities? But it's more about expectations. Could treat as Responsibilities? But we already have responsibilities list from earlier sections: "A Day in The Life….Product Communication & Messaging", "Campaigns & Content", "Cross-Functional Collaboration". Those are responsibilities. Also "What Success Looks Like" sections (first 30 days, 60 days, 90 days) could be considered expectations but could be part of Responsibilities or separate? The instruction: prefer few substantive sections over many thin ones. So we could combine responsibilities and expectations into one Responsibilities section with subpoints? But we need to use ul li for any list of duties/requirements/benefits. So we can make a big ul with all responsibilities items. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include all details from the posting, but we can format as lists. Must not lose any detail. That's a lot of text. We need to capture all bullet-like sentences. Let's extract substantive content: Intro paragraph about company mission etc. That's About the role? Could be considered About the role. Then: "As our Product Communications Specialist, you’ll help us figure out how to talk about what we’re building. That starts before you write a word. You’ll work out who needs to know, why it matters to them, and what we should create. Then you’ll carry that thinking into launches, nurturing campaigns, webpages, product news, and internal communication. You’ll also think about what comes after launch, because hitting publish is only part of the job." Then "Some days, you’ll turn a complex feature into three useful sentences. Other days, you’ll see how those three sentences could become a campaign. We’ll count on you to spot what’s missing, suggest what comes next, and keep the details and deadlines straight along the way. And if you’ve already tightened a sentence or three in this description, we should probably talk." Then "A Day in The Life….Product Communication & Messaging" with bullet-like paragraphs: - Get to know our products, features, and releases well enough to explain them to someone who doesn’t speak fluent ClassLink. - Dig into workflows, use cases, and limitations. Keep asking questions until you can explain what a feature does, who it helps, and why they’d care. - Build messaging, value statements, FAQs, talking points, and terminology other teams can trust and reuse. A good explanation shouldn’t have to start from scratch every time. - Keep product webpages current and useful. If a page is telling last year’s story or leaving readers wondering what to do next, you’ll help fix it. - Spot where a new page, FAQ, or resource would help someone find the answer they need, whether they’re searching on Google or asking AI. - Adjust the story for clients, prospects, partners, and employees. They bring different questions, and you’ll help answer them without losing the facts along the way. Then "Campaigns & Content": - Get involved early with Product and Marketing to understand what’s coming and what communication is needed. - Turn those conversations into communication plans that make the audience, message, channels, content, owners, and timing clear. Everyone should know their part. - Match the communication to the release. Sometimes a useful update is enough. Sometimes we need a full campaign. - Spot missing information and creative needs early, giving Creative, Web, Learning Design, Technical Writing, and other teams time to do their best work. - Keep the product story consistent across webpages, email, campaigns, product news, presentations, events, and internal communication. Consistent doesn’t mean copied and pasted. - Keep useful product content coming between launches, too. Think blog series, explainers, comparisons, FAQs, use cases, and resources people will still need six months from now. - Write the content yourself or give another writer a brief they can work from. Bring in customer stories and proof when they help make the point. Then "Cross-Functional Collaboration": - Build relationships across Product, Marketing, Sales, Client Services, Learning Design, Technical Writing, and Creative. Knowing who to ask is a real part of this job. - Keep owners, deadlines, and next steps clear, including who needs what before they can move forward. We’ll count on you to notice when something needs a follow-up. - Know when to pull in the right people across events, webinars, social, PR, newsletters, customer stories, case studies, and other channels to make the product story stronger. - Use good judgment when customer needs, technical details, marketing goals, and business priorities pull in different directions. Help us find language that’s both accurate and worth reading. - Build repeatable ways to plan, create, update, and reuse communication. Use AI where it helps, with your judgment and fact-checking still very much on the job. - Stay curious about buyer questions, product marketing, search and AI discovery, and new ways to communicate. Bring back the ideas worth trying and help us put them to work. Then "What Success Looks Like First 30 Days: Learn Products, People & Processes" with bullet-like paragraphs: - Start by getting curious. Learn the products, meet the people, and get a feel for how communication happens here. Before you suggest a better way, understand why we do it this way. - Get comfortable with our products, terminology, and audiences, and learn how a release moves from Product to market. - Meet the people involved in product communication. Understand what they own, what they need from you, and where your work connects. - Look through recent launches, webpages, nurture campaigns, product content, internal communication, and enablement resources. Notice what’s working, too. We want to keep the good stuff. - Follow the product story across events, social, customer stories, PR, newsletters, and blogs to see how the pieces fit together. - Notice where communication starts too late, useful stories go untold, or someone says, “Didn’t we already write this?” Those are worth a closer look. Then "By 60 Days: Put What You're Learning to Work": - You’ll still have questions. You’ll also have enough context to say, “Here’s how I think we should handle this,” and start making it happen. - Take ownership of communication for assigned releases and features, from the first planning conversation through delivery. - Build launch plans that make it clear who we’re reaching, what we’re saying, what we’re creating, and who’s doing what by when. - Develop product messaging for webpages, nurture campaigns, client communication, and resources our internal teams can use. - Start lining up product campaigns and content ideas before the next request arrives. You’re getting to know the products well enough to see what’s worth talking about. - Flag missing information and content or creative needs while there’s still time to act. If something is unclear, help get it sorted. Then "By 90 Days: Own the Work": - By this point, we should be able to talk through a goal and trust you to work out the next steps. You’ll know when to move something forward and when to pull someone in. - Independently take assigned product communication projects from planning through completion, keeping the people involved informed along the way. - Keep an active pipeline of launches, nurture campaigns, product content, and webpage opportunities, with a clear view of what’s next. - Bring recommendations when you spot a gap. “Here’s what I noticed, and here’s what I think we should do” is a good place to start. - Put repeatable launch plans and reusable messaging to work so each project starts a little further along. - Use product priorities, audience feedback, and what people actually engage with to recommend the stories we should tell next. - Become someone teams trust to help answer, “How should we communicate this?” Then "NOTE: This job description is not intended to be all-inclusive..." remove. Then "Requirements What You'll Bring You like figuring things out, finding the right words, and getting the work out the door. Here’s what will help you do that here." Then list: - 5+ years in product communications, product marketing, content strategy, B2B marketing, or related work, plus a bachelor’s degree or equivalent professional experience. - Strong writing and editing skills. You can make a complicated idea clear without accidentally editing out the part that matters. - Experience with launches, nurture campaigns, webpages, blogs, email, or other content that helps someone go from “That’s interesting” to taking the next step. - Curiosity about how a product works and what someone can do with it. You’ll ask the extra question that helps the story click. - A way to keep projects, people, and deadlines straight. The small details make it onto your list, too. - The initiative to notice what’s missing and suggest what comes next. You’re comfortable getting started before someone has written out every step. - Good judgment and experience working across Product, Marketing, Sales, technical teams, and other partners. You know when to ask, when to recommend, and when to rethink your favorite line. - Comfort using AI and marketing data to improve the work. You bring your own judgment, even when the answer sounds very sure of itself. Then "Nice to Have A few things that would give you a head start:" list: - Experience in edtech, SaaS, cybersecurity, identity and access management, or another industry where the products take some explaining. - Time spent working directly with product managers, engineers, technical writers, and customer-facing teams. - Familiarity with SEO, AI-powered discovery, marketing automation, CRM, or web analytics. - Experience building product content or nurture programs that help prospects move toward a decision and clients get more from the product. - Ability to travel up to 15% for Company and Team Retreats and Meetings. Then "Benefits:" list: - Generous Paid Time Off: 4+ weeks of vacation and 13+ paid holidays - Parental Leave: 12 weeks fully paid for all parents - Retirement: 401(k) with 0.5:1 company match - Comprehensive Health Coverage: Medical, dental, and vision plans - Insurance: Company-paid life, short-term disability, and long-term disability, plus voluntary options including supplemental life, accident, and pet insurance - Perks: - Volunteer Time Off: Give back through ClassLink Cares paid volunteer days - Lifelong Learning: Tu