Senior Content Ideation Specialist

We need to output HTML fragment with sections: About the role? Actually the posting includes "A Little About Us", "A Little About You", "Position Overview", "Key Responsibilities", "Key Qualifications", "Location and Workplace Flexibility", "Base Salary Range", "Benefits". We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must not include Job ID etc. We must only include sections when posting has real specific content. So we need to map content to appropriate headings. We have: - About the role: could be "Position Overview". Use heading "About the role" maybe? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when appropriate. So we need sections: About the role, Responsibilities, Requirements (or Qualifications?), Skills, Benefits, Pay, Schedule. We need to decide which sections we have content for. We have Position Overview -> can map to About the role. Key Responsibilities -> Responsibilities. Key Qualifications -> Requirements (or Qualifications). The instruction includes Requirements and Qualifications as separate possible headings. We can combine? Probably we should use "Requirements" for qualifications. Or we could have both Requirements and Qualifications if we have distinct content. The posting has "Key Qualifications" which includes credentials, experience, etc. Also there is a separate "Independence/ Accountability", "Communication Skills". Those could be under Skills? Actually they are more like competencies. Could map to Skills. We also have Location and Workplace Flexibility -> maybe not a standard heading; but we could drop as not required? The instruction says include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It lists example headings but not mandatory to include all. So we can include Location if we want but not in the list? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. So we may omit Location unless we map to something else (maybe Schedule? Not really). Could include Schedule if there is info about hybrid approach. The posting mentions hybrid approach flexible, in-office presence guided by team needs. That's schedule info. So we can put that under Schedule. Base Salary Range -> Pay. Benefits -> Benefits. We also have "A Little About Us" and "A Little About You" which are fluff; we might not need to include as they are not substantive for role? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info? It's about company and candidate profile. Might be considered substantive but not required sections. Could we include under About the role? Probably we can incorporate that info into About the role section as prose. The instruction says use

for prose. So we can put that content in About the role

. Similarly "A Little About You" could be part of About the role or maybe we could omit as it's fluff? But it's substantive description of ideal candidate; could be part of Requirements or Skills. Safer to incorporate into About the role or Requirements. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to cut out the EEO paragraph, Accessibility Support, Disclaimer, etc. Also remove "Please note at this time we are unable to proceed with candidates who require visa sponsorship now or in the future." That's a requirement about visa sponsorship; we should keep as part of Requirements? It's a restriction. Could include under Requirements. We need to preserve all substantive information: So we need to keep the visa restriction, location preferences, hybrid approach, salary range, benefits list. Let's extract content: About Zelis (A Little About Us) - description of company. A Little About You - description of candidate. Position Overview - description of role. Key Responsibilities - bullet list (we need to convert to

• ). Key Qualifications - bullet list (but it's paragraph with line breaks). We'll need to parse into list items. Independence/ Accountability - bullet list. Communication Skills - bullet list. Location and Workplace Flexibility - paragraph. Base Salary Range - sentence. Benefits - paragraph. We need to output only HTML fragment. We'll create sections:

  About the role

  Combine A Little About Us, A Little About You, Position Overview into prose.

  Responsibilities

  • ...

  Requirements

  • ...
  (include Key Qualifications, Independence/Accountability, Communication Skills, visa restriction maybe)

  Skills

  Maybe we could separate but we already put communication skills etc under Requirements. Could also have Skills separate for things like "Strong organization and project/process management skills", "Ability to leverage reporting tools", etc. But we can keep them under Requirements. But we have separate headings for Skills; maybe better to put communication skills etc under Skills. However the instruction says we can use those headings as examples; we can decide. Let's think: The posting has distinct sections: Key Qualifications (credentials, experience), Independence/Accountability (soft skills), Communication Skills (soft skills). Could map Key Qualifications to Requirements, Independence/Accountability and Communication Skills to Skills. Thus:

  Requirements

  • Current, active CIC or CCS or equivalent credentialing is required
  • RN or LPN with coding certification, or certified coder, or registered health information technician (RHIA/RHIT) with at least 6-8 years of experience
  • Experience with MS-DRG/APR-DRG coding and compliance required
  • Experience performing regulatory research from multiple sources, formulating an opinion, and presenting findings in an organized, concise manner
  • Knowledge of National Medicare and Medicaid regulations
  • Knowledge of payer reimbursement policies
  • Creative problem-solving skills, leveraging insights and input from other parts of an organization
  • Ability to leverage reporting tools to research claim data, trending and analysis for concept ideation processes
  • Understanding of JIRA/Confluence recommended
  • Strong organization and project/process management skills
  • Independence/Accountability: Regularly reviews goals and objectives with supervisor; Must have professional manner and respect the confidentiality of administrative matters and files; Ability to manage and prioritize multiple tasks; Ability to be a self-starter and meet deadlines; Ability to follow detailed instructions on assignments, where necessary; Ability to be a self-motivator and track against personal goals
  • Communication Skills: Must work well with others; Communicates accurately, honestly, and effectively, both in oral and written form, practices active listening; Clearly conveys information and ideas through a variety of media to individuals and groups in a manner that engages the audience and helps them understand the information
  • Please note at this time we are unable to proceed with candidates who require visa sponsorship now or in the future.
  But we need to keep each as separate
• maybe too long. Could break into multiple
• . We'll keep each bullet as separate
• . For the compound ones we can keep as one
• with semicolons. Now Skills section maybe not needed if we included those under Requirements. But we could still have Skills separate for things like "Strong organization and project/process management skills", "Ability to leverage reporting tools", etc. However we already included them. Might be okay. Now Benefits section:

  Benefits

  Zelis’ full-time associates are eligible for a highly competitive benefits package as well, which demonstrates our commitment to our employees’ health, well-being, and financial protection. The US-based benefits include a 401k plan with employer match, flexible paid time off, holidays, parental leaves, life and disability insurance, and health benefits including medical, dental, vision, and prescription drug coverage.

  Pay section:

  Pay

  Base Salary Range $105,000.00 - $133,000.00

  Schedule section:

  Schedule

  Zelis is headquartered in the U.S., with multiple locations across the country and in Hyderabad, India. All employee work locations are based on the needs of the position and are determined by the Leadership team. In-office work and activities vary based on work and team objectives in accordance with Company policies. While location expectations vary by role, candidates within approximately 50 miles of a U.S. office are generally preferred to support collaboration when needed. Our hybrid approach is flexible, and in-office presence is guided by team and business needs rather than a fixed weekly schedule.

  We need to ensure we didn't include boilerplate like EEO, Accessibility Support, Disclaimer. Also we removed "Please note at this time we are unable to proceed with candidates who require visa sponsorship now or in the future." we kept under Requirements. We also removed "A Little About Us" and "A Little About You" as separate headings; we merged into About the role. Now check that we preserved all substantive information: Company description, candidate description, position overview, responsibilities list, qualifications list, independence/accountability, communication skills, visa restriction, location info, hybrid approach, salary, benefits. Yes. Now ensure we didn't include any filler like "commensurate with experience". Not present. Now output only HTML fragment. Let's craft the HTML. We'll need to escape any HTML special characters? Not needed. We'll produce:

  About the role

  ...

  Then responsibilities etc. Let's write the About the role paragraph: combine: "At Zelis, we Get Stuff Done. So, let’s get to it! A Little About Us Zelis is modernizing the healthcare financial experience across payers, providers, and healthcare consumers. We serve more than 750 payers, including the top five national health plans, regional health plans, TPAs and millions of healthcare providers and consumers across our platform of solutions. Zelis sees across the system to identify, optimize, and solve problems holistically with technology built by healthcare experts – driving real, measurable results for clients. At Zelis, AI is woven into the fabric of how we work. Every associate is expected - and empowered - to partner with AI to challenge the status quo, accelerate innovation, and amplify their impact. This is a place for builders with a growth mindset who act with agility, embrace change, and use modern technology to shape smarter solutions, exceptional experiences, and the future of our industry for our clients, customers, and our culture. A Little About You You bring a unique blend of personality and professional expertise to your work, inspiring others with your passion and dedication. Your career is a testament to your diverse experiences, community involvement, and the valuable lessons you've learned along the way. You are more than just your resume; you are a reflection of your achievements, the knowledge you've gained, and the personal interests that shape who you are. Position Overview The Senior Concept Ideation Analyst, Bill Review role is responsible for development and delivery of initiatives focused on bill review content management. The Ideation Team researches and produces new bill review content as well as enhances existing bill review content using sources such as ICD-10, AHA, AMA, CPT, AAPC, CMS and/or clinical research sources. This role partners closely with the team in producing clinical content for bill reviews of facility claims including support for communication and documentation. They will work closely with Operations and Product teams in the development and maintenance of the content as