WordPress Developer-Frontend

We need to produce HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: EEO, legal, etc. Also remove duplicated lines, application instructions. Preserve all substantive info. Let's parse the posting: Title: WordPress Developer-Frontend Location: 100% Remote - Must be Local to Alhambra, CA Pay rate: $38.00 - 42/hour DOE Duration: 12+Months (Possibility of extension) Skills: (list of many experience requirements) Education Required Bachelor’s degree in an IT-related or Engineering field. Education Preferred Bachelor’s degree in an IT-related or Engineering field. Additional Information Work is expected to be done in a 100% remote. Russell Tobin offers eligible employees comprehensive healthcare coverage (medical, dental, and vision plans), supplemental coverage (accident insurance, critical illness insurance and hospital indemnity), a 401(k)-retirement savings, life & disability insurance, an employee assistance program, identity theft protection, legal support, auto and home insurance, pet insurance, and employee discounts with some preferred vendors. Then there is a lot of EEO etc. Then PrideGlobal similar benefits. We need to extract substantive info: role description? Not given explicitly besides title. Could have "About the role" maybe not present. We can create sections based on content we have: maybe "Responsibilities" not explicit; "Requirements" could be the skills/experience list; "Qualifications" could be education; "Skills" could be the long list; "Benefits" from Russell Tobin and PrideGlobal; "Pay" from pay rate; "Schedule" maybe not given; "Location" maybe could be part of About the role? But we have no heading for location; we could include location in a paragraph under About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections as appropriate. We have location info: "100% Remote - Must be Local to Alhambra, CA". Could be part of About the role or maybe a separate section? Not in list but we could embed in About the role paragraph. We have duration: "12+Months (Possibility of extension)". Could be part of About the role or maybe Schedule? Not exactly schedule. Could be part of About the role. We have pay rate: $38.00 - 42/hour DOE. That's Pay. We have benefits: Russell Tobin offers ... and PrideGlobal offers ... We'll combine. We have skills/experience list: many bullet-like statements. We'll put under Skills (or Requirements). The instruction: Use

• for any list of duties/requirements/benefits. So we need to convert the list into
  • . The list is long and repetitive; we need to preserve all substantive information, not invent or summarize away detail. So we need to include each requirement as a list item. However many are similar: "5 years of experience in WordPress administration, development, migration, and optimization. At least 3 years of that experience must be in a lead capacity." Then many "3 years of experience within the last 5 years in ...". We'll keep each as separate list items. Education: "Education Required Bachelor’s degree in an IT-related or Engineering field." and "Education Preferred Bachelor’s degree in an IT-related or Engineering field." Could be under Qualifications. Additional Information: "Work is expected to be done in a 100% remote." Already covered location. We must not include boilerplate: EEO, Fair Chance, Accommodations, Lactation, etc. Also remove duplicated lines (the PrideGlobal benefits duplicate Russell Tobin? We'll keep only one benefits section maybe combine but not duplicate). We'll need to deduplicate. Let's extract benefits: Russell Tobin offers eligible employees comprehensive healthcare coverage (medical, dental, and vision plans), supplemental coverage (accident insurance, critical illness insurance and hospital indemnity), a 401(k)-retirement savings, life & disability insurance, an employee assistance program, identity theft protection, legal support, auto and home insurance, pet insurance, and employee discounts with some preferred vendors. PrideGlobal offers similar: comprehensive healthcare coverage (medical, dental, and vision plans), supplemental coverage (accident insurance, critical illness insurance and hospital indemnity), 401(k)-retirement savings, life & disability insurance, an employee assistance program, legal support, pet insurance and employee discounts with preferred vendors. We can combine: mention both? Might be duplicate. Since they are similar, we could just list benefits once, but we must preserve ALL substantive information; not invent or summarize away detail. If we combine, we might lose the distinction that both companies offer similar benefits. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Summarizing away detail could be considered summarizing. But we could keep both statements as separate paragraphs, even if similar. That preserves detail. However we must avoid duplicated lines? The instruction says remove duplicated lines. The two benefit statements are not identical lines but similar. Might be considered duplicated content? Safer to keep both as separate paragraphs under Benefits. Now we need to output only HTML fragment, no markdown fences. Let's structure:

    About the role

    WordPress Developer-Frontend position. 100% remote work, must be local to Alhambra, CA. Duration: 12+ months with possibility of extension.

    Responsibilities

    ? Not explicitly given. Could we infer responsibilities from skills? Might be risky to invent. Better to omit Responsibilities section if no specific content. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should not include Responsibilities if not present.

    Requirements

    Maybe we can put the experience list under Requirements. But we also have Skills section. Could combine? The instruction says prefer a few substantive sections over many thin ones. So we could have Requirements covering experience and education, and Skills covering technical skills? But the list includes both experience and technical skills. Might be better to have one Requirements section that includes all experience requirements, and a Skills section for technical proficiencies? However the list includes many technical skills like WordPress, PHP, HTML, CSS, SASS/SCSS, JAVASCRIPT, etc. That's also experience. Given the instruction to prefer few sections, we could have: - About the role - Requirements (includes experience, education) - Benefits - Pay We could also have Skills if we want to separate but maybe not needed. But we need to use

    for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It's okay to use others? Probably they expect those headings. We'll stick to those. We have content for About the role, Requirements (experience + education), Benefits, Pay. We don't have Schedule. We'll not include Qualifications separate if we put education under Requirements. Let's extract experience list exactly as written: "5 years of experience in WordPress administration, development, migration, and optimization. At least 3 years of that experience must be in a lead capacity." "3 years of experience within the last 5 years in leading conversion projects, meetings, and communication directly with business owners." "3 years of experience within the last 5 years in the WordPress Platform." "3 years of experience within the last 5 years with converting mockups to WordPress pages." "3 years of experience within the last 5 years with migrating websites from other platforms to WordPress." "3 years of experience within the last 5 years troubleshooting cross-browser compatibility issues." "3 years of experience within the last 5 years with responsive web design techniques." "3 years of experience within the last 5 years with common WordPress Plugins/Features such as Advanced Custom Fields, Custom Post Type, and Duplication or Backups." "3 years of experience within the last 5 years with optimizing performance of WordPress sites." "3 years of experience within the last 5 years with Search Engine Optimization (SEO)." "3 years of experience within the last 5 years in WordPress, PHP, HTML, CSS, SASS/SCSS, JAVASCRIPT." "3 years of experience within the last 5 years in WordPress Custom Theme and Plugin Development." "3 years of experience within the last 5 years with WordPress REST API." We need to preserve each as separate list item. Education: "Education Required Bachelor’s degree in an IT-related or Engineering field." and "Education Preferred Bachelor’s degree in an IT-related or Engineering field." We'll put as list items under Requirements maybe. Now Benefits: We'll have two paragraphs maybe each as

    under Benefits. Pay:

    Pay rate: $38.00 - 42/hour DOE

    Now we need to ensure we don't include any boilerplate: remove EEO, Fair Chance, Accommodations, Lactation, etc. Also remove duplicated lines like "Work is expected to be done in a 100% remote." Already covered in About the role. Also remove "Apply today for consideration!" maybe not needed as it's application instruction; we should remove application instructions. So we drop that line. Now produce HTML. Let's craft:

    About the role

    WordPress Developer-Frontend position. 100% remote work, must be local to Alhambra, CA. Duration: 12+ months with possibility of extension.

    Requirements

    • 5 years of experience in WordPress administration, development, migration, and optimization. At least 3 years of that experience must be in a lead capacity.
    • 3 years of experience within the last 5 years in leading conversion projects, meetings, and communication directly with business owners.
    • 3 years of experience within the last 5 years in the WordPress Platform.
    • 3 years of experience within the last 5 years with converting mockups to WordPress pages.
    • 3 years of experience within the last 5 years with migrating websites from other platforms to WordPress.
    • 3 years of experience within the last 5 years troubleshooting cross-browser compatibility issues.
    • 3 years of experience within the last 5 years with responsive web design techniques.
    • 3 years of experience within the last 5 years with common WordPress Plugins/Features such as Advanced Custom Fields, Custom Post Type, and Duplication or Backups.
    • 3 years of experience within the last 5 years with optimizing performance of WordPress sites.
    • 3 years of experience within the last 5 years with Search Engine Optimization (SEO).
    • 3 years of experience within the last 5 years in WordPress, PHP, HTML, CSS, SASS/SCSS, JAVASCRIPT.
    • 3 years of experience within the last 5 years in WordPress Custom Theme and Plugin Development.
    • 3 years of experience within the last 5 years with WordPress REST API.
    • Education Required: Bachelor’s degree in an IT-related or Engineering field.
    • Education Preferred: Bachelor’s degree in an IT-related or Engineering field.

    Benefits

    Russell Tobin offers eligible employees comprehensive healthcare coverage (medical, dental, and vision plans), supplemental coverage (accident insurance, critical illness insurance and hospital indemnity), a 401(k)-retirement savings, life & disability insurance, an employee assistance program, identity theft protection, legal support, auto and home insurance, pet insurance, and employee discounts