Web Developer II

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like About Us, EEO, scam warning, etc. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". Must include Pay section only if posting actually states them. The posting includes "$72,000 - $85,760 a year". So we need Pay section with that. Benefits: there is a list of benefits. So Benefits section. Schedule: not mentioned explicitly. No schedule info. So we should not create Schedule section. Skills: maybe we can combine Qualifications and Skills? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to include sections only when posting has real specific content. We have About the role (the paragraph after "About The Role"). Responsibilities (Duties & Responsibilities). Qualifications (Qualifications and Desired Qualifications). Skills maybe could be derived from qualifications but we might treat Skills as separate if there is specific skill list. The posting includes many skills: HTML5, CSS3, responsive design, modern JavaScript, WordPress, PHP, MySQL, REST APIs, Git, WCAG, etc. Could put them under Skills. But we also have Qualifications (education, experience). To avoid duplication, we could put Qualifications for education/experience, Skills for technical skills. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one "Qualifications" section that includes both education/experience and skills. But they said we can use Skills heading if there is real specific content. We have specific skills list. Could create Skills section. However we must not repeat content. If we split, we need to ensure we don't duplicate. Let's decide: We'll have sections: About the role, Responsibilities, Qualifications (including education/experience and desired qualifications), Skills (technical skills), Benefits, Pay. That seems reasonable. We must not include schedule. Must not include About Us. Must not include EEO etc. Must not include scam warning. Must not include "We understand that not everyone will match..." maybe that's part of encouragement but could be considered boilerplate? It's not a standard boilerplate but it's encouraging applicants; could be kept? It's not a heading; it's prose. Might be considered part of the posting but not essential. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that sentence? It's not boilerplate; it's part of the posting encouraging applicants. It's substantive? It's more of a encouragement. I'd keep it as part of Qualifications maybe? But it's not a qualification. Could be placed after Qualifications as a note. However it's not a heading; we can include as a

under Qualifications or as its own paragraph after Qualifications. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The encouragement sentence is not those. So we keep. Also "We're a tight-knit team..." etc is also substantive about culture; we could keep as part of Benefits? Actually it's about culture and benefits. Could be part of Benefits section? But we already have Benefits list. Might keep as separate paragraph under Benefits or after Benefits. It's not boilerplate. We'll keep. We must output only HTML fragment, no markdown fences. Let's extract content: About the role paragraph: "The Web Developer will support the development, maintenance, and continuous improvement of our portfolio of websites, helping advance our mission through accessible, reliable, and engaging digital experiences. This role will build and update web pages, develop custom website functionality, troubleshoot technical issues, improve site performance, and help ensure our websites meet security, accessibility, and usability standards. Working within the Marketing Department’s Web Team and reporting to the Senior Website Manager, this position will collaborate with marketing, design, communications, program teams, and external partners to bring digital projects to life. This is an opportunity to contribute to high-impact websites and campaigns while supporting an organization working to accelerate clean transportation and create healthier communities." Responsibilities (Duties & Responsibilities) list: - Develop, maintain, and enhance our websites, landing pages, and web applications using WordPress, PHP, HTML, CSS, JavaScript, and MySQL. - Independently manage assigned our web properties, including routine maintenance, technical troubleshooting, testing, deployments, and post-launch support. - Build and modify WordPress themes, templates, reusable components, blocks, plugins, and custom functionality. - Translate approved designs and business requirements into responsive, accessible, and user-friendly web experiences that meet WCAG 2.2 AA standards. - Support website launches, redesigns, migrations, integrations, and strategic projects, including the upcoming rebrand and rebuild. - Develop and maintain integrations with REST APIs, forms, analytics platforms, CRM systems, Salesforce, and other third-party services. - Collaborate with the Senior Web Developer, designers, Marketing, IT, program teams, and other stakeholders throughout planning, development, quality assurance, and launch. - Monitor and improve website performance, security, accessibility, uptime, scalability, and Core Web Vitals across our web portfolio. - Maintain technical documentation and contribute to development standards, reusable components, testing practices, deployment procedures, and Web Team workflows. Qualifications (education/experience): - Bachelor’s degree in computer science, web development, software engineering, or a related field, or equivalent professional experience. - Five or more years of professional web development experience, including experience developing and maintaining WordPress websites. Desired Qualifications list (many items). We'll include under Qualifications maybe as a sublist or separate? Could be part of Qualifications as "Desired Qualifications". We'll keep as part of Qualifications section. Skills list: Many technical skills: Strong proficiency in HTML5, CSS3, responsive design, modern JavaScript, and building or modifying WordPress themes, templates, blocks, plugins, or custom functionality. Working knowledge of PHP, MySQL, REST APIs, third-party web services, and Git-based development workflows. Experience applying web accessibility standards, preferably WCAG 2.1 or newer, along with an understanding of website security, privacy, performance optimization, cross-browser compatibility, and testing practices. Ability to independently troubleshoot issues across front-end, back-end, CMS, database, integration, and hosting environments. Strong organizational and project administration skills, with the ability to manage multiple assignments across a portfolio of websites. Strong communication, collaboration, accountability, adaptability, and problem-solving skills, including the ability to explain technical information to non-technical stakeholders. Desired Qualifications also include experience with hosting platforms, ACF, Gutenberg, WPBakery, CI/CD, Docker, Salesforce, HubSpot, marketing automation, Google Analytics, GTM, consent-management, React, Vue, automated testing tools, website migrations, redesigns, data visualizations, GIS tools, multisite web portfolios, nonprofit experience. We could treat all these as Skills. But there is overlap with Qualifications. To avoid duplication, maybe we put all under Skills and keep Qualifications just for education/experience. However the instruction: Prefer a few substantive sections over many thin ones. Having both Qualifications and Skills may be okay if both have substantive content. We'll have Qualifications (education/experience) and Skills (technical and soft skills). That seems fine. Now Benefits: list: - 100% company paid comprehensive health benefits for Medical, Dental, Vision, Short Term Disability, Long Term Disability and Life Insurance - Retirement plan with generous company contributions - FSA for Health and Dependent Care - 3 weeks of vacation time in the first year of employment - 11 paid company holidays - paid sick time - paid family leave - and more! Also culture paragraph: "We're a tight-knit team of world-class innovators, business minds, and change agents who believe passionately in our mission and put our team ahead of self. We are committed to the continued development and growth of our employees and invest in your success! We care about your personal well being as much as your professional success and offer generous benefits to full time employees including:" Actually that paragraph introduces benefits; we already have benefits list. We could keep that as a preamble

before the

. It's substantive. Pay: "$72,000 - $85,760 a year" Now we must not include sections like Schedule. Now produce HTML:

About the Role

...

Responsibilities

• ...
...

Qualifications

... maybe combine education/experience and desired qualifications? Could have two paragraphs: one for required qualifications, one for desired. Or we can have

for required and

for desired. Let's do:

Bachelor’s degree ...

Five or more years ...

Desired qualifications include:

...
But we need to avoid duplication with Skills. We'll put desired qualifications as part of Qualifications. Then Skills section:

Skills

...
(list of technical and soft skills). Could be many items; we can break into logical groups but just list each as
• . Then Benefits:

  Benefits

  We're a tight-knit team ...

  ...
  Pay:

  Pay

  $72,000 - $85,760 a year

  Make sure not to include extra whitespace? It's fine. Now ensure we didn't include any boilerplate like About Us, EEO, scam warning, etc. Check for duplicated lines: we must not repeat same content. We'll be careful. Now extract exact text for each item. About the role paragraph: We'll copy exactly as in posting: "The Web Developer will support the development, maintenance, and continuous improvement of our portfolio of websites, helping advance our mission through accessible, reliable, and engaging digital experiences. This role will build and update web pages, develop custom website functionality, troubleshoot technical issues, improve site performance, and help ensure our websites meet security, accessibility, and usability standards. Working within the Marketing Department’s Web Team and reporting to the Senior Website Manager, this position will collaborate with marketing, design, communications, program teams, and external partners to bring digital projects to life. This is an opportunity to contribute to high-impact websites and campaigns while supporting an organization working to accelerate clean transportation and create healthier communities." Responsibilities list items: copy each bullet. Let's list them: 1. Develop, maintain, and enhance our websites, landing pages, and web applications using WordPress, PHP, HTML, CSS, JavaScript, and MySQL. 2. Independently manage assigned our web properties, including routine maintenance, technical troubleshooting, testing, deployments, and post-launch support. 3. Build and modify WordPress themes, templates, reusable components, blocks, plugins, and custom functionality. 4. Translate approved designs and business requirements into responsive, accessible, and user-friendly web experiences that meet WCAG 2.2 AA standards. 5. Support website launches, redesigns, migrations, integrations, and strategic projects, including the upcoming rebrand and rebuild. 6. Develop and maintain integrations with REST APIs, forms, analytics platforms, CRM systems, Salesforce, and other third-party services. 7. Collaborate with the Senior Web Developer, designers, Marketing, IT, program teams, and other stakeholders throughout planning, development, quality assurance, and launch. 8. Monitor and improve website performance, security, accessibility, uptime, scalability, and Core Web Vitals