Front-End Web Developer (Marketing and Communications)

We need to output HTML fragment with sections: About the role (maybe "About The Role" heading), Responsibilities (What You'll Do), Requirements/Qualifications (What You'll Bring), Benefits (What We'll Provide). Also Pay and Schedule if present. Pay: Salary Range given: $78,000 - $119,000/year. So we need a Pay section. Schedule: Not mentioned (Full-Time is job type but not schedule details). Should we include Schedule? The rule: only include section if posting has real, specific content. Full-Time is job type but not schedule details like hours. Probably not include Schedule. Benefits: we have description of benefits. So include Benefits. We must not repeat job title as heading. Use

for section headings. Use

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

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: posting date, address, location line? The location line: "Posting Date 09/25/2026 2000 16th Street, Denver, Colorado, 80202, United States of America Location: Denver/Remote Job Type: Full-Time Department: Development (Marketing & Communications)". This is metadata; we can fold minor metadata into a short

  or drop it. Probably we can include a short

  with location and job type? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a

  with location and job type maybe. But we need to preserve ALL substantive information; location is substantive? It's location: Denver/Remote. Job type: Full-Time. Department: Development (Marketing & Communications). We could include a short paragraph at top:

  Location: Denver/Remote • Job Type: Full-Time • Department: Development (Marketing & Communications)

  . That seems okay. Now sections: About The Role: we have paragraph: "We’re looking for a skilled and collaborative Front-End Web Developer to join our team and help build performant, accessible, and user-focused websites for healthcare organizations. This role is ideal for a developer who is fluent in modern front-end development practices and has hands-on experience working with WordPress VIP and Gutenberg in content-heavy, CMS-driven environments. You’ll report to a Design and Development Manager and work as part of a cross-functional team that includes UI/UX designers, back-end developers, content strategists, and a product/project management team." We'll put that in

  under

  About The Role

  . Responsibilities: "What You’ll Do" bullet list. We'll convert each line to
• . Need to preserve all details. Let's list: - Develop responsive, accessible front-end code using HTML, CSS/SCSS, and modern JavaScript (ES6+) - Build and extend custom themes, templates, and components within WordPress VIP, including custom Gutenberg blocks - Collaborate with designers to implement visually precise, performant UI from high-fidelity mockups and prototypes - Work closely with the Product Manager, Scrum Master, and development team to break down and estimate tasks during sprint planning - Ensure cross-browser, cross-device compatibility and performance optimization - Integrate structured content and custom fields using WordPress APIs and CMS admin tools - Apply accessibility best practices and adhere to WCAG guidelines - Contribute to component libraries and internal dev standards - Troubleshoot bugs and support iterative improvements post-launch - Stay current with front-end trends, tooling, and WordPress ecosystem updates We'll put under

  Responsibilities

  with
  . Requirements/Qualifications: "What You’ll Bring". We'll treat as Requirements. List: - 3-5 years of experience in front-end development, including work on CMS-based, responsive websites - Demonstrated experience working within WordPress VIP, including code standards, deployment workflows, and performance tuning - Hands-on experience building custom Gutenberg blocks (React-based) - Proficiency in semantic HTML5, modern CSS (SCSS/SASS), and JavaScript (ES6+); experience with React is a plus - Familiarity with Git/GitHub-based workflows - Strong collaboration skills and comfort working in a cross-functional team that includes non-developers - Understanding of accessibility (WCAG), responsive design, and mobile-first development - Experience working in Agile or Scrum environments - Experience in healthcare, nonprofit, or other regulated content environments is a strong plus - Familiarity with Figma or other design tools to support close designer/developer handoff We'll put under

  Requirements

  (or Qualifications). The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose Requirements. We'll put Requirements. Benefits: "What We’ll Provide". We need to capture all benefit details. The paragraph: "More than just pay, our DaVita Rewards package connects teammates to what matters most. Teammates are eligible to begin receiving benefits on the first day of the month following or coinciding with one month of continuous employment. Below are some of our benefit offerings. Comprehensive benefits: Medical, dental, vision, 401(k) match, paid time off, PTO cash out Support for you and your family: Family resources, EAP counseling sessions, access Headspace®, backup child and elder care, maternity/paternity leave and more Professional development programs: DaVita offers a variety of programs to help strong performers grow within their career and also offers on-demand virtual leadership and development courses through DaVita’s online training platform StarLearning. At DaVita, we strive to be a community first and a company second. We want all teammates to experience DaVita as "a place where I belong." Our goal is to embed belonging into everything we do in our Village, so that it becomes part of who we are. We are proud to be an equal opportunity workplace and comply with state and federal affirmative action requirements. Individuals are recruited, hired, assigned and promoted without regard to race, national origin, religion, age, color, sex, sexual orientation, gender identity, disability, protected veteran status, or any other protected characteristic. This position will be open for a minimum of three days. The Salary Range for the role is $78,000.00 - $119,000.00/year. For location-specific minimum wage details, see the following link: DaVita.jobs/WageRates Compensation for the role will depend on a number of factors, including a candidate’s qualifications, skills, competencies and experience. DaVita offers a competitive total rewards package, which includes a 401k match, healthcare coverage and a broad range of other benefits. Learn more at https://careers.davita.com/benefits Colorado Residents: Please do not respond to any questions in this initial application that may seek age-identifying information such as age, date of birth, or dates of school attendance or graduation. You may also redact this information from any materials you submit during the application process. You will not be penalized for redacting or removing this information. Beware of Recruitment Fraud DaVita will never ask for payment or personal financial information at any point in the hiring process, nor will we ever communicate with you using email addresses outside of the DaVita secure network. If you receive a request like this, it is not legitimate. Do not share your information. Career Growth - From clinical and operations to corporate jobs, our learning and development programs help guide your career journey." We need to strip boilerplate: EEO, equal opportunity, scam warning, Colorado resident instructions, recruitment fraud, career growth? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove EEO statement, Colorado resident instructions, Beware of Recruitment Fraud, Career Growth. Also remove "This position will be open for a minimum of three days." That's maybe application instruction? It's about posting duration; could be considered boilerplate. Probably remove. Also remove link to DaVita.jobs/WageRates? Might be considered location-specific minimum wage details; maybe keep? It's a link; but it's not substantive benefit. Might be considered metadata; we could drop. The instruction: "fold minor metadata into a short

  or drop it." So we could drop that link. Also "Learn more at https://careers.davita.com/benefits" maybe keep as part of benefits? It's a link to benefits; could be considered reference. Might keep as part of benefits paragraph? But we need to preserve substantive information; the link is not essential but could be considered minor metadata. Safer to drop. Thus Benefits section should contain: "More than just pay, our DaVita Rewards package connects teammates to what matters most. Teammates are eligible to begin receiving benefits on the first day of the month following or coinciding with one month of continuous employment. Below are some of our benefit offerings. Comprehensive benefits: Medical, dental, vision, 401(k) match, paid time off, PTO cash out Support for you and your family: Family resources, EAP counseling sessions, access Headspace®, backup child and elder care, maternity/paternity leave and more Professional development programs: DaVita offers a variety of programs to help strong performers grow within their career and also offers on-demand virtual leadership and development courses through DaVita’s online training platform StarLearning. At DaVita, we strive to be a community first and a company second. We want all teammates to experience DaVita as "a place where I belong." Our goal is to embed belonging into everything we do in our Village, so that it becomes part of who we are." We could also keep the sentence about competitive total rewards package includes 401k match, healthcare coverage and a broad range of other benefits. That's somewhat redundant but we can keep. We'll format as

  prose; but we have lists within benefits (comprehensive benefits etc). The instruction: Use

  • for any list of duties/requirements/benefits. So we should turn the benefit items into lists. However the benefits are described in sentences with colon separated lists. We could create
    for each category: Comprehensive benefits, Support for you and your family, Professional development programs. But we need to preserve all substantive information; we can convert to list items. Let's parse: Comprehensive benefits: Medical, dental, vision, 401(k) match, paid time off, PTO cash out Support for you and your family: Family resources, EAP counseling sessions, access Headspace®, backup child and elder care, maternity/paternity leave and more Professional development programs: DaVita offers a variety of programs to help strong performers grow within their career and also offers on-demand virtual leadership and development courses through DaVita’s online training platform StarLearning. Then the rest about belonging etc is prose. Thus we can have

    Benefits

    then

    More than just pay, our DaVita Rewards package connects teammates to what matters most. Teammates are eligible to begin receiving benefits on the first day of the month following or coinciding with one month of continuous employment.

    then
    • Comprehensive benefits: Medical, dental, vision, 401(k) match, paid time off, PTO cash out
    etc. But the instruction says use
    • for any list of duties/requirements/benefits. So each benefit item could be a
    • . However the benefit categories themselves are not individual items; but we could treat each benefit as a list item. Eg
    • Medical
    ,
    • Dental
    , etc. But we need to preserve the grouping? Might be okay to flatten. Simplify: Provide a
    with each benefit as
    • . Let's list: - Medical