Communications Specialist II (Gov't Tech)

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, description includes "Communications Specialist II (US- Remote)". Title not used as heading. We need sections: - About the role: likely the introductory paragraph(s) before Position summary? The posting starts with description: "Communications Specialist II (US- Remote) What to expect when you join Sikich Team members at Sikich have a lot in common..." That's about company culture. Could be "About the role" or maybe "About Sikich". But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. Let's extract: - About the role: Could be the initial paragraph about Sikich culture, mission, etc. That seems appropriate. - Responsibilities: The "What will you do in this role?" section with bullet points (Enterprise Communications Execution, Training and Informational Materials, Knowledge Management and Distribution, Branding, Visual Communications, and Executive Materials, Accessibility and Standards Compliance, Ad-Hoc Communications Support). Those are responsibilities. - Requirements: The "What do you need to succeed in this role?" includes Bachelor's degree, 5+ years experience, demonstrated ability, strong proficiency, experience with enterprise-level distribution list, etc. That's requirements. - Qualifications: Might be overlapping with requirements; but we could treat "Qualifications" as the list of preferred knowledge areas (Prior experience supporting CMS/CCSQ programs, etc.) Or we could treat "Qualifications" as the required qualifications (the bullet list). However we already used Requirements for those. Could split: Requirements = mandatory; Qualifications = preferred. The posting includes "Knowledge in the following areas preferred:" after the required list. So we can put that under Qualifications. - Skills: Could be the list of tools proficiency: Collaboration & PM: Atlassian Jira, Confluence, Slack, Microsoft Teams, LucidWeb & Distribution: QualityNet website, QualityNet Mailer, QualityNet ServiceNow, SurveyMonkey Design & Multimedia: Adobe Creative Cloud, Canva for Teams, 123RF licensed media library Automation: UiPath (for listserv and channel management automation) Productivity: Adobe Pro, Microsoft Office Suite. Also the "Servant Leader – ..." etc are competencies/behaviors; could be Skills as well. But we need to decide. - Benefits: The section "Sikich Total Rewards" lists benefits: Flexible Time Off (FTO) Policy, paid holidays, wellness program, flexible work arrangements, health/dental/vision/life/accident insurance, HSA employer contribution, 11 paid holidays, parental bonding leave, 401(k) with employer contributions, tuition reimbursement, employee referral bonus, client referral bonus, pet insurance, FORCE volunteer program. That's benefits. - Pay: The posting includes compensation range: "In compliance with this state’s pay transparency laws, the base compensation range (25%-50%-75%) for this role is $70,000- $77,500- $85,000." That's pay. - Schedule: Not mentioned explicitly; maybe remote work? The title says US- Remote. Could infer schedule? Not given. So we should not include Schedule section because no specific content. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We must not include empty sections. Now we need to format: Use

for section headings. Use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Want to learn more? Visit our Careers website or Glassdoor profile." and the EEO statement, etc. Also remove the long Sikich description about alternative practice structure etc at end (the legal). Also remove "Sikich is an Equal Opportunity Employer M/F/D/V" etc. We need to keep all substantive content: company culture paragraphs, position summary, responsibilities details, requirements, preferred qualifications, skills/tools, benefits, pay. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings (none present). We need to ensure we don't include filler like "commensurate with experience" etc. The pay range is specific; we keep. Now craft HTML. We'll start with

  About the role

  then a

  containing the introductory paragraphs about Sikich culture and mission. We need to capture the text: "What to expect when you join Sikich Team members at Sikich have a lot in common while also being part of a rich and varied group of contributors, creating a distinct and thriving culture. Chief among our commonalities is a desire for growth and a shared unity of purpose in our professional lives. We believe that through diverse perspectives, challenging the status quo and rewarding action, we accelerate innovation and drive growth – for our clients, for ourselves and for our communities. The professional services landscape continues to evolve. For Sikich, this means we have an opportunity to further cement our leadership position in this industry and continue to grow our organization in increasingly exciting ways. This growth is meaningful for every team member at our company because larger companies simply see more interesting client opportunities and can attract impressively talented individuals like you. Through a dedicated focus on key business priorities and intentionally creating rewarding employee experience, Sikich has developed into a highly regarded provider of professional services and a sought-after employer of choice. Do you want to work with other skilled and agile practitioners who thrive on challenge and growth? We believe everyone has untapped potential. That’s why we lead with vision and act fast, pairing deep expertise with practical solutions. Our teams cut through complexity and deliver real impact. It's our hope that you find more than just a job. At Sikich, you'll find optimism, clear insights and genuine warmth, without egos. Are you ready to grow with us?" That's a big paragraph; we can keep as

  . Then maybe also include the Position summary? Actually Position summary is separate: "Position summary The Communications Specialist supports enterprise-scale communications and stakeholder engagement across CMS/CCSQ programs and Lines of Business (LOBs). Working under the direction of the Communications Lead, this role develops written, visual, and multimedia content; maintains knowledge repositories; manages distribution channels; and ensures all communications products comply with Section 508 and WCAG accessibility standards. The Communications Specialist operates within a high-volume, fast-paced federal health IT environment, supporting both planned program communications and ad-hoc, time-sensitive needs for ISG leadership, program offices, and external stakeholders." That could be part of About the role or Responsibilities. But we already have About the role covering culture; we could add Position summary as part of About the role or maybe as a separate section? The headings list doesn't have "Position summary". So we could incorporate it into About the role or Responsibilities. Probably better to put it under About the role as it's a summary of the role. However the instructions: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can decide to put Position summary under About the role. Thus About the role will contain the culture paragraphs plus the Position summary. Now Responsibilities: we need to list the duties under "What will you do in this role?" with subheadings: Enterprise Communications Execution, Training and Informational Materials, Knowledge Management and Distribution, Branding, Visual Communications, and Executive Materials, Accessibility and Standards Compliance, Ad-Hoc Communications Support. Each of these is a duty area with bullet points (some are paragraphs). We need to use

  • for any list of duties/requirements/benefits. So we can make a
    where each
    • contains the heading (maybe bold) and the description. We must preserve all substantive information; do not invent or summarize away detail. So we need to include the details under each duty. Let's extract each duty's details: **Enterprise Communications Execution**: - Develop and deliver operational and end-user communications including downtime notices, system upgrade announcements, release notifications, and change alerts for QualityNet Shared Services and LOB systems. - Tailor communications to specific audiences across LOBs, teams, and initiatives using written, visual, and multimedia formats. - Deliver communications through CMS-approved channels including email, Slack, and the QualityNet website. - Coordinate with technical, program, and leadership teams to validate all content prior to release. - Support enterprise communications planning, scheduling, and intake processes under the direction of the Communications Lead. - Serve as a senior contributor to communications strategy planning, coordinating closely with the Communications Lead on high-visibility deliverables, content calendars, and cross-program messaging alignment. **Training and Informational Materials**: - Produce and distribute training and informational materials to support adoption of new tools, system enhancements, and process changes, including videos, graphics, user guides, and microlearning assets. - Develop content aligned with CMS plain-language, branding, and accessibility standards as maintained in the Communications Toolkit in Confluence. - Help onboard and mentor junior communications specialists on training and informational content development. **Knowledge Management and Distribution**: - Maintain communications-related and supporting reference content in Confluence, the QualityNet website, and other knowledge repositories to provide guidance, reference materials, and training content for internal and public-facing use. - Manage and maintain enterprise email listservs, distribution lists, and Slack channels to ensure accurate targeting, access control, and minimization of misdirected or unauthorized communications. - Apply process improvements and automation (e.g., UiPath) to streamline the creation and management of listservs, distribution lists, and Slack channels. - Submit content management requests through QualityNet ServiceNow as applicable. - Guide knowledge article creation and manage communications-related Confluence repositories to ensure accuracy, currency, and usability. **Branding, Visual Communications, and Executive Materials**: - Develop branding assets and visual materials, including logos, templates, and style elements, in alignment with CMS branding standards. - Produce executive briefings, presentations, and stakeholder engagement materials for CCSQ leadership and program offices. - Design graphics, infographics, and multimedia content using tools such as Adobe Creative Cloud and Canva for Teams. - Lead the development and quality review of written and visual content across the communications team, ensuring alignment with program messaging and enterprise branding standards. **Accessibility and Standards Compliance**: - Ensure all communications products, including end-user notifications, web content, surveys, training materials, and multimedia assets, comply with Section 508 and WCAG accessibility standards prior to release. - Apply universal design principles throughout content development to ensure materials are usable by individuals with disabilities. **Ad-Hoc Communications Support**: - Provide timely communications development and distribution support for emerging, unplanned, or time-sensitive needs including executive briefings, governance materials, user notifications, and internal stakeholder engagement content. - Support CCSQ leadership, CCSQ OD, and program offices with tailored communications outside planned schedules while maintaining alignment with enterprise standards. Now Requirements: "What do you need to succeed in this role?" includes: - Bachelor’s degree in Communications, English, Journalism, Public Affairs, or related field. - 5+ years of experience in communications, content strategy, or stakeholder engagement in a federal IT or health IT environment. - Demonstrated ability to lead content development, manage repositories, and guide junior team members. - Strong proficiency with Adobe Creative Cloud, Canva, and other visual communications tools. - Experience with enterprise-level distribution list and listserv management. We'll put these in a
      . Qualifications: "Knowledge in the following areas preferred:" list: - Prior experience supporting CMS/CCSQ programs (e.g., PM3 II, QualityNet, iQIES, HQR, QPP, EQRS, CQP). - Experience with Quality