Web User Interface Developer
Apex Systems · Clayton, MO · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with headings for sections: 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. Must preserve all substantive info, no invention, no summarizing away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions.
We need to parse the job description.
Key parts:
Position Overview: "We are seeking an experienced Web Content Manager to oversee the day-to-day management of multiple websites and drive the successful execution of digital content initiatives. This role bridges content, user experience, and technology teams to ensure websites are updated, optimized, and aligned with business objectives. The ideal candidate is highly organized, detail-oriented, and experienced in content management systems, web publishing workflows, and cross-functional project coordination. This individual will be responsible for managing website updates, prioritizing incoming requests, supporting website migrations, and ensuring a seamless user experience across digital properties."
That's about the role.
Key Responsibilities bullet list:
- Manage and maintain multiple websites through a content management system (CMS).
- Oversee digital publishing workflows, website updates, and ongoing content maintenance.
- Coordinate with UX, content, and technical teams to build, update, and publish web pages.
- Manage incoming web requests, ticket queues, and project priorities while ensuring timely delivery.
- Lead or support website migration initiatives, including content inventory, asset management, and redirect mapping.
- Translate design mockups into responsive, functional web experiences while maintaining quality and consistency.
- Partner with stakeholders to define technical requirements and implement website enhancements.
- Monitor website performance and user engagement metrics to identify opportunities for optimization.
- Support landing page creation, personalization initiatives, A/B testing efforts, and conversion optimization strategies.
- Maintain documentation, publishing standards, and reusable digital interface patterns.
Required Qualifications bullet list:
- Bachelor's degree or equivalent professional experience.
- 5+ years of experience in web content management, digital publishing, or website operations.
- Experience managing multiple websites within a fast-paced environment.
- Strong knowledge of CMS platforms, such as Sitecore, Liferay, or similar enterprise content management systems.
- Experience managing web requests, prioritizing competing deadlines, and coordinating multiple projects simultaneously.
- Working knowledge of HTML, CSS, JavaScript, and web publishing best practices.
- Experience collaborating with UX, content, and development teams.
- Strong written and verbal communication skills with both technical and non-technical stakeholders.
- Proven ability to work independently while managing cross-functional initiatives.
Preferred Qualifications bullet list:
- Experience with CMS migrations and website redesign projects.
- Familiarity with design and prototyping tools such as Figma.
- Experience using AI-powered tools to improve productivity, streamline workflows, or support content operations.
- Understanding of web analytics, conversion optimization, personalization, or A/B testing platforms.
- Experience working with CRM platforms and digital marketing technologies.
- Project management experience within web or digital transformation initiatives.
What We're Looking For bullet list:
- Exceptional attention to detail and commitment to quality.
- Strong organizational and problem-solving skills.
- Ability to manage multiple priorities in a dynamic environment.
- Collaborative mindset with a focus on stakeholder partnership.
- Technical curiosity and willingness to adopt new tools and technologies.
Contract Length: "Initial 12-month contract with potential for extension or conversion to a full-time opportunity."
Company description: "Everforth Apex is a world-class IT services company that serves thousands of clients across the globe. When you join Everforth Apex, you become part of a team that values innovation, collaboration, and continuous learning. We offer quality career resources, training, certifications, development opportunities, and a comprehensive benefits package. Our commitment to excellence is reflected in many awards, including ClearlyRateds Best of Staffing® in Talent Satisfaction in the United States and Great Place to Work® in the United Kingdom and Mexico."
Then there is a paragraph about virtual recruiter etc - that's application instructions / boilerplate; we must remove.
Then "Everforth Apex Benefits Overview: ..." This contains benefits details. We need to include Benefits section if there is real specific content. The benefits overview includes medical, dental, vision, life, disability, other insurance plans, ESPP, 401K with company match after 12 months, HSA, SupportLinc EAP, corporate discount savings program, on-demand training program, certification prep, library of technical and leadership courses/books/seminars after 6+ months tenure, certification discounts, perks to associations (CompTIA, IIBA), dedicated customer service team for consultants, certified Career Coach, Welcome Packet.
That's substantive benefits. So we should include a Benefits section with
for sections: 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. Must preserve all substantive info, no invention, no summarizing away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions.
We need to parse the job description.
Key parts:
Position Overview: "We are seeking an experienced Web Content Manager to oversee the day-to-day management of multiple websites and drive the successful execution of digital content initiatives. This role bridges content, user experience, and technology teams to ensure websites are updated, optimized, and aligned with business objectives. The ideal candidate is highly organized, detail-oriented, and experienced in content management systems, web publishing workflows, and cross-functional project coordination. This individual will be responsible for managing website updates, prioritizing incoming requests, supporting website migrations, and ensuring a seamless user experience across digital properties."
That's about the role.
Key Responsibilities bullet list:
- Manage and maintain multiple websites through a content management system (CMS).
- Oversee digital publishing workflows, website updates, and ongoing content maintenance.
- Coordinate with UX, content, and technical teams to build, update, and publish web pages.
- Manage incoming web requests, ticket queues, and project priorities while ensuring timely delivery.
- Lead or support website migration initiatives, including content inventory, asset management, and redirect mapping.
- Translate design mockups into responsive, functional web experiences while maintaining quality and consistency.
- Partner with stakeholders to define technical requirements and implement website enhancements.
- Monitor website performance and user engagement metrics to identify opportunities for optimization.
- Support landing page creation, personalization initiatives, A/B testing efforts, and conversion optimization strategies.
- Maintain documentation, publishing standards, and reusable digital interface patterns.
Required Qualifications bullet list:
- Bachelor's degree or equivalent professional experience.
- 5+ years of experience in web content management, digital publishing, or website operations.
- Experience managing multiple websites within a fast-paced environment.
- Strong knowledge of CMS platforms, such as Sitecore, Liferay, or similar enterprise content management systems.
- Experience managing web requests, prioritizing competing deadlines, and coordinating multiple projects simultaneously.
- Working knowledge of HTML, CSS, JavaScript, and web publishing best practices.
- Experience collaborating with UX, content, and development teams.
- Strong written and verbal communication skills with both technical and non-technical stakeholders.
- Proven ability to work independently while managing cross-functional initiatives.
Preferred Qualifications bullet list:
- Experience with CMS migrations and website redesign projects.
- Familiarity with design and prototyping tools such as Figma.
- Experience using AI-powered tools to improve productivity, streamline workflows, or support content operations.
- Understanding of web analytics, conversion optimization, personalization, or A/B testing platforms.
- Experience working with CRM platforms and digital marketing technologies.
- Project management experience within web or digital transformation initiatives.
What We're Looking For bullet list:
- Exceptional attention to detail and commitment to quality.
- Strong organizational and problem-solving skills.
- Ability to manage multiple priorities in a dynamic environment.
- Collaborative mindset with a focus on stakeholder partnership.
- Technical curiosity and willingness to adopt new tools and technologies.
Contract Length: "Initial 12-month contract with potential for extension or conversion to a full-time opportunity."
Company description: "Everforth Apex is a world-class IT services company that serves thousands of clients across the globe. When you join Everforth Apex, you become part of a team that values innovation, collaboration, and continuous learning. We offer quality career resources, training, certifications, development opportunities, and a comprehensive benefits package. Our commitment to excellence is reflected in many awards, including ClearlyRateds Best of Staffing® in Talent Satisfaction in the United States and Great Place to Work® in the United Kingdom and Mexico."
Then there is a paragraph about virtual recruiter etc - that's application instructions / boilerplate; we must remove.
Then "Everforth Apex Benefits Overview: ..." This contains benefits details. We need to include Benefits section if there is real specific content. The benefits overview includes medical, dental, vision, life, disability, other insurance plans, ESPP, 401K with company match after 12 months, HSA, SupportLinc EAP, corporate discount savings program, on-demand training program, certification prep, library of technical and leadership courses/books/seminars after 6+ months tenure, certification discounts, perks to associations (CompTIA, IIBA), dedicated customer service team for consultants, certified Career Coach, Welcome Packet.
That's substantive benefits. So we should include a Benefits section with - items.
Pay: Not mentioned besides maybe contract length; no salary. So we should NOT include Pay section.
Schedule: Not mentioned besides contract length (initial 12-month contract). Not a schedule like full-time/part-time hours. So we should NOT include Schedule.
We also have "Contract Length" which could be considered under "Schedule"? But schedule usually refers to work hours, shift, etc. Contract length is not schedule. The instruction: include Schedule section only if posting actually states them. It does not state schedule like "Full-time, 40 hrs/week" etc. So we omit Schedule.
We also have "About the role" maybe we can use Position Overview as About the role. We'll create
About the role
with containing the overview.
Responsibilities:
Responsibilities
with - each bullet.
Requirements: Could combine Required Qualifications and maybe also "What We're Looking For"? The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide where to put each piece.
We have Required Qualifications (education, experience). We have Preferred Qualifications (nice-to-have). We have What We're Looking For (soft skills/attributes). We have Skills maybe from technical skills (HTML, CSS, JS, CMS, etc). We could separate.
We need to preserve all substantive info. So we need to include sections for Requirements, Qualifications, Skills maybe.
But we must not create empty sections. So we need to decide mapping.
Potential approach:
- About the role: Position Overview paragraph.
- Responsibilities: list of responsibilities.
- Requirements: Required Qualifications (education, years experience, managing multiple websites, CMS knowledge, managing web requests, HTML/CSS/JS, collaborating, communication, independent work). Could also include "Bachelor's degree or equivalent professional experience." etc.
- Qualifications: Preferred Qualifications (CMS migrations, Figma, AI tools, web analytics, CRM/digital marketing, project management). Could also include "What We're Looking For" maybe as Skills? But we have Skills heading.
- Skills: Could include technical skills: HTML, CSS, JavaScript, CMS platforms (Sitecore, Liferay), web publishing best practices, UX/content/dev collaboration, etc. Also maybe "design and prototyping tools such as Figma", "AI-powered tools", "web analytics, conversion optimization, personalization, A/B testing platforms", "CRM platforms and digital marketing technologies". Also "project management experience". Also "strong written and verbal communication". However some of these overlap with qualifications.
We need to avoid duplication but preserve all info. Could split: Requirements = mandatory qualifications (required). Qualifications = preferred qualifications (nice-to-have). Skills = technical and soft skills enumerated elsewhere (like "Working knowledge of HTML, CSS, JavaScript, and web publishing best practices.", "Experience collaborating with UX, content, and development teams.", "Strong written and verbal communication skills", "Exceptional attention to detail", etc). But we must ensure we don't lose any info.
Let's extract all bullet points from the posting:
From Position Overview (prose): we already captured.
From Key Responsibilities (list): we have 10 items.
From Required Qualifications (list): 9 items.
From Preferred Qualifications (list): 6 items.
From What We're Looking For (list): 5 items.
From Contract Length: sentence.
From Benefits Overview: paragraph with many items.
We need to output HTML with sections.
We'll create:
About the role
... (position overview)
Responsibilities
- ... each responsibility
Requirements
- ... each required qualification
Qualifications
- ... each preferred qualification
Skills
- ... combine technical skills from required, preferred, and what we're looking for? But we risk duplication. However we can include skills that are not already captured as requirements or qualifications. For example: "Working knowledge of HTML, CSS, JavaScript, and web publishing best practices." is already in Required Qualifications. If we put it also in Skills, it's duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However we need to include a Skills section only if there is real specific content for it. We could place skills that are not already covered: maybe "Experience collaborating with UX, content, and development teams." is also in Required Qualifications. "Strong written and verbal communication skills with both technical and non-technical stakeholders." also in Required. "Proven ability to work independently while managing cross-functional initiatives." also in Required. "Exceptional attention to detail and commitment to quality." is in What We're Looking For. "Strong organizational and problem-solving skills." also in What We're Looking For. "Ability to manage multiple priorities in a dynamic environment." also in What We're Looking For. "Collaborative mindset with a focus on stakeholder partnership." also in What We're Looking For. "Technical curiosity and willingness to adopt new tools and technologies." also in What We're Looking For.
Thus all those items appear either in Required Qualifications or What We're Looking For. So we might not need a separate Skills section; we could omit Skills if no unique content. But we need to check if any skill not captured elsewhere: maybe "Experience managing web requests, prioritizing competing deadlines, and coordinating multiple projects simultaneously." is in Required. "Experience managing multiple websites within a fast-paced environment." also Required. "Strong knowledge of CMS platforms, such as Sitecore, Liferay, or similar enterprise content management systems." Required. "Experience with CMS migrations and website redesign projects." Preferred. "Familiarity with design and prototyping tools such as Figma." Preferred. "Experience using AI-powered tools to improve productivity, streamline workflows, or support content operations." Preferred. "Understanding of web analytics, conversion optimization, personalization, or A/B testing platforms." Preferred. "Experience working with CRM platforms and digital marketing technologies." Preferred. "Project management experience within web or digital transformation initiatives." Preferred.
Thus all technical/soft skills appear in either Required, Preferred, or What We're Looking For. So we could omit Skills section. However the instruction says: "Prefer a few substantive sections over many thin ones." So we can omit Skills if no unique content.
But we need to include Benefits section.
We also have Contract Length sentence; where to put? Could be under About the role? Or maybe under a separate section like "Contract" but not in allowed headings. The allowed headings list does not include Contract. So we need to fold it into a suitable section, maybe About the role or Responsibilities? The contract length is not a responsibility but could be part of About the role (overview). We can add a sentence at end of About the role paragraph: "Initial 12-month contract with potential for extension or conversion to a full-time opportunity."
We must not repeat job title as heading. Already not.
We must not include Job ID etc. We'll drop.
We must remove boilerplate: virtual recruiter, EEO, etc. Also remove the repeated EEO paragraph at end. Also remove the privacy policy link etc. Also remove the
About the role
withcontaining the overview. Responsibilities:
Responsibilities
with- each bullet.
Requirements: Could combine Required Qualifications and maybe also "What We're Looking For"? The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide where to put each piece.
We have Required Qualifications (education, experience). We have Preferred Qualifications (nice-to-have). We have What We're Looking For (soft skills/attributes). We have Skills maybe from technical skills (HTML, CSS, JS, CMS, etc). We could separate.
We need to preserve all substantive info. So we need to include sections for Requirements, Qualifications, Skills maybe.
But we must not create empty sections. So we need to decide mapping.
Potential approach:
- About the role: Position Overview paragraph.
- Responsibilities: list of responsibilities.
- Requirements: Required Qualifications (education, years experience, managing multiple websites, CMS knowledge, managing web requests, HTML/CSS/JS, collaborating, communication, independent work). Could also include "Bachelor's degree or equivalent professional experience." etc.
- Qualifications: Preferred Qualifications (CMS migrations, Figma, AI tools, web analytics, CRM/digital marketing, project management). Could also include "What We're Looking For" maybe as Skills? But we have Skills heading.
- Skills: Could include technical skills: HTML, CSS, JavaScript, CMS platforms (Sitecore, Liferay), web publishing best practices, UX/content/dev collaboration, etc. Also maybe "design and prototyping tools such as Figma", "AI-powered tools", "web analytics, conversion optimization, personalization, A/B testing platforms", "CRM platforms and digital marketing technologies". Also "project management experience". Also "strong written and verbal communication". However some of these overlap with qualifications.
We need to avoid duplication but preserve all info. Could split: Requirements = mandatory qualifications (required). Qualifications = preferred qualifications (nice-to-have). Skills = technical and soft skills enumerated elsewhere (like "Working knowledge of HTML, CSS, JavaScript, and web publishing best practices.", "Experience collaborating with UX, content, and development teams.", "Strong written and verbal communication skills", "Exceptional attention to detail", etc). But we must ensure we don't lose any info.
Let's extract all bullet points from the posting:
From Position Overview (prose): we already captured.
From Key Responsibilities (list): we have 10 items.
From Required Qualifications (list): 9 items.
From Preferred Qualifications (list): 6 items.
From What We're Looking For (list): 5 items.
From Contract Length: sentence.
From Benefits Overview: paragraph with many items.
We need to output HTML with sections.
We'll create:
About the role
... (position overview)
Responsibilities
- ... each responsibility
Requirements
- ... each required qualification
Qualifications
- ... each preferred qualification
Skills
- ... combine technical skills from required, preferred, and what we're looking for? But we risk duplication. However we can include skills that are not already captured as requirements or qualifications. For example: "Working knowledge of HTML, CSS, JavaScript, and web publishing best practices." is already in Required Qualifications. If we put it also in Skills, it's duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However we need to include a Skills section only if there is real specific content for it. We could place skills that are not already covered: maybe "Experience collaborating with UX, content, and development teams." is also in Required Qualifications. "Strong written and verbal communication skills with both technical and non-technical stakeholders." also in Required. "Proven ability to work independently while managing cross-functional initiatives." also in Required. "Exceptional attention to detail and commitment to quality." is in What We're Looking For. "Strong organizational and problem-solving skills." also in What We're Looking For. "Ability to manage multiple priorities in a dynamic environment." also in What We're Looking For. "Collaborative mindset with a focus on stakeholder partnership." also in What We're Looking For. "Technical curiosity and willingness to adopt new tools and technologies." also in What We're Looking For. Thus all those items appear either in Required Qualifications or What We're Looking For. So we might not need a separate Skills section; we could omit Skills if no unique content. But we need to check if any skill not captured elsewhere: maybe "Experience managing web requests, prioritizing competing deadlines, and coordinating multiple projects simultaneously." is in Required. "Experience managing multiple websites within a fast-paced environment." also Required. "Strong knowledge of CMS platforms, such as Sitecore, Liferay, or similar enterprise content management systems." Required. "Experience with CMS migrations and website redesign projects." Preferred. "Familiarity with design and prototyping tools such as Figma." Preferred. "Experience using AI-powered tools to improve productivity, streamline workflows, or support content operations." Preferred. "Understanding of web analytics, conversion optimization, personalization, or A/B testing platforms." Preferred. "Experience working with CRM platforms and digital marketing technologies." Preferred. "Project management experience within web or digital transformation initiatives." Preferred. Thus all technical/soft skills appear in either Required, Preferred, or What We're Looking For. So we could omit Skills section. However the instruction says: "Prefer a few substantive sections over many thin ones." So we can omit Skills if no unique content. But we need to include Benefits section. We also have Contract Length sentence; where to put? Could be under About the role? Or maybe under a separate section like "Contract" but not in allowed headings. The allowed headings list does not include Contract. So we need to fold it into a suitable section, maybe About the role or Responsibilities? The contract length is not a responsibility but could be part of About the role (overview). We can add a sentence at end of About the role paragraph: "Initial 12-month contract with potential for extension or conversion to a full-time opportunity." We must not repeat job title as heading. Already not. We must not include Job ID etc. We'll drop. We must remove boilerplate: virtual recruiter, EEO, etc. Also remove the repeated EEO paragraph at end. Also remove the privacy policy link etc. Also remove the