Web Content Development Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to extract content: The posting includes "About the role" paragraph, then "What you’ll do" (responsibilities), then "What you’ll bring" (required qualifications), then "Preferred qualifications", then "What success looks like", then "Working model". Also there is a mission statement at top (people-first). Should we include that as part of About the role? Possibly as a brief intro paragraph before About the role. The instructions: Use
for section headings. So we can have:
About the role
with paragraph(s) describing role.
Then Responsibilities
with list of duties (What you’ll do). Could break into subpoints but we can just list as - .
Then
Requirements
with required qualifications (What you’ll bring). Could also separate Required vs Preferred? The instructions allow Qualifications section. Could combine required and preferred under Qualifications? But they said prefer a few substantive sections over many thin ones. Could have Requirements (required) and maybe Preferred qualifications as a subsection? But we can't create subheadings other than . Could combine both required and preferred under Requirements with two lists: Required and Preferred. But we need to preserve all info. Could have Requirements
then
Required qualifications:
then list. Then Preferred qualifications:
then list.
Then maybe Success metrics
or What success looks like
but they didn't list that as allowed heading; allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They said use those as examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also use other headings if needed? Probably better to stick to those. So we could map "What success looks like" to maybe Skills? Not exactly. Could incorporate into Requirements or Responsibilities? Might be better to have a separate section like "Qualifications" for required and preferred, and "Skills" for success metrics? But success metrics is more about outcomes. Could treat as "Qualifications". However we need to preserve all substantive info; we can include it as a paragraph under Requirements or as a separate section like "Qualifications". The instruction: Prefer a few substantive sections over many thin ones. So maybe combine "What success looks like" and "Working model" into a section like "Working model" maybe under "Qualifications"? Hmm.
Better to have sections: About the role, Responsibilities, Requirements (including required and preferred), and maybe Working model (as a separate section). But Working model is not in the list of examples but could be considered as "Qualifications"? Not exactly. However the instruction says use those as examples, not exclusive. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. So we can use other headings if needed, but better to stick to those to be safe. However we need to convey working model and success metrics. Could incorporate them into Requirements or Responsibilities as prose.
Let's extract details:
About the role paragraph: "SolarWinds is seeking a Content Web Development Lead to modernize how web content is planned, created, tested, approved, and published. This role combines AI-forward workflow design, CMS and frontend expertise, QA automation, launch coordination, and team leadership. You will improve publishing across Builder.io, WordPress, Aprimo DAM, React and Next.js experiences, and the workflows connecting Web PMs, Content, SEO, Design, Analytics, Marketing, QA, and Web Development. This player-coach role combines hands-on contribution, team mentorship, operating-model improvement, and prioritization across competing work."
We could also include the earlier mission statement as intro paragraph before About the role? Might be considered boilerplate? It's about company purpose; could be included as a short paragraph before About the role. Not a heading. It's substantive. We'll include as a
before the first heading.
Responsibilities (What you’ll do): list of bullet points:
- Lead AI-forward content operations
- Build governed, spec-driven agentic workflows for content intake, drafting, QA, approvals, and launches.
- Use AI tools such as Claude, GitHub Copilot, Builder.io AI, or comparable platforms to improve requirements refinement, content operations, QA, documentation, triage, and release preparation.
- Design agentic workflows for ticket intake, content drafting, metadata checks, test execution, issue creation, localization support, and launch-readiness reporting.
- Govern automation with draft-first boundaries, human approval, audit trails, permissions, validation evidence, rollback procedures, and clear ownership.
- Measure AI’s impact on delivery speed, throughput, quality, coverage, and team capacity while protecting security, accessibility, SEO, and editorial judgment.
- Own web publishing and CMS delivery
- Manage publishing from intake and prioritization through content preparation, preview, UAT, approval, launch, and post-launch validation.
- Support Builder.io and WordPress templates, components, permissions, content models, revisions, and controlled releases.
- Improve self-service publishing while ensuring complex layouts, integrations, SEO changes, and high-risk releases receive appropriate technical review.
- Provide practical frontend guidance across HTML, CSS, JavaScript/TypeScript, responsive behavior, browser debugging, and component-based web experiences.
- Support CMS migrations and modernization while preserving URLs, content structure, metadata, analytics, redirects, and business functionality.
- Govern Aprimo DAM practices including asset metadata, classification, lifecycle status, approved-public usage, renditions, expiry, and page-usage tracking.
- Lead QA automation and web quality
- Establish automated testing for functional, visual, accessibility, SEO, links, analytics, performance, mobile, cross-browser, and production smoke coverage.
- Use tools such as Playwright, Cypress, Applitools, Lighthouse, crawlers, and real-user monitoring to improve release confidence.
- Define acceptance criteria and evidence requirements so every launch has named approvers, documented validation, and a rollback or remediation path.
- Monitor defect escape rate, test coverage, recurring failure patterns, Core Web Vitals, accessibility issues, and post-launch performance.
- Evaluate usability and user experience across desktop, mobile, content structure, navigation, forms, and key conversion paths.
- Prioritize and coordinate launches
- Partner with Web PMs on campaign, product, event, migration, redesign, and information-architecture launches.
- Prioritize requests using business value, customer impact, SEO and accessibility risk, urgency, effort, dependencies, capacity, and launch timing.
- Maintain transparent backlogs, roadmaps, launch calendars, SLAs, status reporting, and escalation paths.
- Measure SLA attainment, publishing throughput, defect rates, and web performance to guide priorities and improvement.
- Lead readiness reviews and go/no-go decisions covering content, functionality, SEO, analytics, accessibility, localization, approvals, rollback, communications, and monitoring.
- Coordinate production communications, incident escalation, and post-launch reviews.
- Lead and develop the team
- Mentor web publishers, frontend contributors, QA automation specialists, and workflow owners through coaching, pairing, reviews, and knowledge sharing.
- Establish standards for ownership, documentation, prioritization, communication, quality, and continuous improvement.
- Turn recurring issues into reusable workflows, templates, automation, training, or operating procedures.
- Partner across Web PM, Content, SEO, Design, Analytics, Marketing Operations, QA, Web Development, and campaign teams.
We can flatten into a single list of responsibilities, each bullet as
- . Might be long but okay.
Requirements (What you’ll bring): Required qualifications list:
- 5+ years in web publishing, content operations, frontend development, QA automation, digital operations, or a related discipline.
- Demonstrated ownership of production web content and publishing workflows from intake through launch.
- Hands-on knowledge of HTML, CSS, JavaScript/TypeScript, responsive web behavior, browser debugging, and frontend quality fundamentals.
- Experience with Builder.io, WordPress, or a comparable CMS, including templates, components, permissions, content models, and publishing controls.
- Hands-on experience with AI tools such as Claude, GitHub Copilot, Cursor, Builder.io AI, or comparable platforms for content operations, QA, documentation, workflow automation, or release preparation.
- Practical understanding of SEO, accessibility, usability, Core Web Vitals, analytics, consent, redirects, metadata, and conversion flows.
- Experience operating automated QA and release-quality processes.
- Demonstrated ability to prioritize competing work across business goals, deadlines, risks, dependencies, and capacity.
- Experience coordinating launches with product, marketing, content, design, SEO, analytics, QA, and engineering stakeholders.
- Demonstrated ability to validate AI-generated content, code, test results, and recommendations using appropriate human review, privacy, security, accessibility, SEO, and editorial controls.
- Strong communication, organization, facilitation, and decision-making skills.
Preferred qualifications list:
- Aprimo DAM or another enterprise digital asset management platform.
- Working knowledge of React, Next.js, Tailwind, Storybook, design systems, Figma, and component-based frontend development.
- Fluency with Jira, Service Desk, Asana, Azure DevOps, GitHub, CI/CD, and release-management workflows.
- A background leading CMS migrations, redesigns, campaign launches, or multi-site publishing programs.
- AI-forward workflow design involving spec-driven development, prompt and context design, tool integration, automation, human approval, and evaluation.
- Knowledge of accessibility standards, with a track record of improving accessible pages, documents, forms, or user experiences.
What success looks like: Could be included as a paragraph under Requirements or as a separate section "Qualifications"? Might be better to add a section "Qualifications" that includes both required and preferred, and then maybe a separate section "Success metrics"? But we can incorporate success looks like as a paragraph under Requirements (maybe after required qualifications). However the instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Required qualifications, Preferred qualifications, and What success looks like into a single "Qualifications" section with subheadings? But we cannot use subheadings other than
. Could use
bold? Not allowed? We can use
with strong text. That's okay.
Thus we could have:
About the role
...
Responsibilities
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract content: The posting includes "About the role" paragraph, then "What you’ll do" (responsibilities), then "What you’ll bring" (required qualifications), then "Preferred qualifications", then "What success looks like", then "Working model". Also there is a mission statement at top (people-first). Should we include that as part of About the role? Possibly as a brief intro paragraph before About the role. The instructions: Use
for section headings. So we can have:
About the role
with paragraph(s) describing role.
Then Responsibilities
with list of duties (What you’ll do). Could break into subpoints but we can just list as - .
Then
Requirements
with required qualifications (What you’ll bring). Could also separate Required vs Preferred? The instructions allow Qualifications section. Could combine required and preferred under Qualifications? But they said prefer a few substantive sections over many thin ones. Could have Requirements (required) and maybe Preferred qualifications as a subsection? But we can't create subheadings other than . Could combine both required and preferred under Requirements with two lists: Required and Preferred. But we need to preserve all info. Could have Requirements
then
Required qualifications:
then list. Then Preferred qualifications:
then list.
Then maybe Success metrics
or What success looks like
but they didn't list that as allowed heading; allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They said use those as examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also use other headings if needed? Probably better to stick to those. So we could map "What success looks like" to maybe Skills? Not exactly. Could incorporate into Requirements or Responsibilities? Might be better to have a separate section like "Qualifications" for required and preferred, and "Skills" for success metrics? But success metrics is more about outcomes. Could treat as "Qualifications". However we need to preserve all substantive info; we can include it as a paragraph under Requirements or as a separate section like "Qualifications". The instruction: Prefer a few substantive sections over many thin ones. So maybe combine "What success looks like" and "Working model" into a section like "Working model" maybe under "Qualifications"? Hmm.
Better to have sections: About the role, Responsibilities, Requirements (including required and preferred), and maybe Working model (as a separate section). But Working model is not in the list of examples but could be considered as "Qualifications"? Not exactly. However the instruction says use those as examples, not exclusive. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. So we can use other headings if needed, but better to stick to those to be safe. However we need to convey working model and success metrics. Could incorporate them into Requirements or Responsibilities as prose.
Let's extract details:
About the role paragraph: "SolarWinds is seeking a Content Web Development Lead to modernize how web content is planned, created, tested, approved, and published. This role combines AI-forward workflow design, CMS and frontend expertise, QA automation, launch coordination, and team leadership. You will improve publishing across Builder.io, WordPress, Aprimo DAM, React and Next.js experiences, and the workflows connecting Web PMs, Content, SEO, Design, Analytics, Marketing, QA, and Web Development. This player-coach role combines hands-on contribution, team mentorship, operating-model improvement, and prioritization across competing work."
We could also include the earlier mission statement as intro paragraph before About the role? Might be considered boilerplate? It's about company purpose; could be included as a short paragraph before About the role. Not a heading. It's substantive. We'll include as a
before the first heading.
Responsibilities (What you’ll do): list of bullet points:
- Lead AI-forward content operations
- Build governed, spec-driven agentic workflows for content intake, drafting, QA, approvals, and launches.
- Use AI tools such as Claude, GitHub Copilot, Builder.io AI, or comparable platforms to improve requirements refinement, content operations, QA, documentation, triage, and release preparation.
- Design agentic workflows for ticket intake, content drafting, metadata checks, test execution, issue creation, localization support, and launch-readiness reporting.
- Govern automation with draft-first boundaries, human approval, audit trails, permissions, validation evidence, rollback procedures, and clear ownership.
- Measure AI’s impact on delivery speed, throughput, quality, coverage, and team capacity while protecting security, accessibility, SEO, and editorial judgment.
- Own web publishing and CMS delivery
- Manage publishing from intake and prioritization through content preparation, preview, UAT, approval, launch, and post-launch validation.
- Support Builder.io and WordPress templates, components, permissions, content models, revisions, and controlled releases.
- Improve self-service publishing while ensuring complex layouts, integrations, SEO changes, and high-risk releases receive appropriate technical review.
- Provide practical frontend guidance across HTML, CSS, JavaScript/TypeScript, responsive behavior, browser debugging, and component-based web experiences.
- Support CMS migrations and modernization while preserving URLs, content structure, metadata, analytics, redirects, and business functionality.
- Govern Aprimo DAM practices including asset metadata, classification, lifecycle status, approved-public usage, renditions, expiry, and page-usage tracking.
- Lead QA automation and web quality
- Establish automated testing for functional, visual, accessibility, SEO, links, analytics, performance, mobile, cross-browser, and production smoke coverage.
- Use tools such as Playwright, Cypress, Applitools, Lighthouse, crawlers, and real-user monitoring to improve release confidence.
- Define acceptance criteria and evidence requirements so every launch has named approvers, documented validation, and a rollback or remediation path.
- Monitor defect escape rate, test coverage, recurring failure patterns, Core Web Vitals, accessibility issues, and post-launch performance.
- Evaluate usability and user experience across desktop, mobile, content structure, navigation, forms, and key conversion paths.
- Prioritize and coordinate launches
- Partner with Web PMs on campaign, product, event, migration, redesign, and information-architecture launches.
- Prioritize requests using business value, customer impact, SEO and accessibility risk, urgency, effort, dependencies, capacity, and launch timing.
- Maintain transparent backlogs, roadmaps, launch calendars, SLAs, status reporting, and escalation paths.
- Measure SLA attainment, publishing throughput, defect rates, and web performance to guide priorities and improvement.
- Lead readiness reviews and go/no-go decisions covering content, functionality, SEO, analytics, accessibility, localization, approvals, rollback, communications, and monitoring.
- Coordinate production communications, incident escalation, and post-launch reviews.
- Lead and develop the team
- Mentor web publishers, frontend contributors, QA automation specialists, and workflow owners through coaching, pairing, reviews, and knowledge sharing.
- Establish standards for ownership, documentation, prioritization, communication, quality, and continuous improvement.
- Turn recurring issues into reusable workflows, templates, automation, training, or operating procedures.
- Partner across Web PM, Content, SEO, Design, Analytics, Marketing Operations, QA, Web Development, and campaign teams.
We can flatten into a single list of responsibilities, each bullet as
- . Might be long but okay.
Requirements (What you’ll bring): Required qualifications list:
- 5+ years in web publishing, content operations, frontend development, QA automation, digital operations, or a related discipline.
- Demonstrated ownership of production web content and publishing workflows from intake through launch.
- Hands-on knowledge of HTML, CSS, JavaScript/TypeScript, responsive web behavior, browser debugging, and frontend quality fundamentals.
- Experience with Builder.io, WordPress, or a comparable CMS, including templates, components, permissions, content models, and publishing controls.
- Hands-on experience with AI tools such as Claude, GitHub Copilot, Cursor, Builder.io AI, or comparable platforms for content operations, QA, documentation, workflow automation, or release preparation.
- Practical understanding of SEO, accessibility, usability, Core Web Vitals, analytics, consent, redirects, metadata, and conversion flows.
- Experience operating automated QA and release-quality processes.
- Demonstrated ability to prioritize competing work across business goals, deadlines, risks, dependencies, and capacity.
- Experience coordinating launches with product, marketing, content, design, SEO, analytics, QA, and engineering stakeholders.
- Demonstrated ability to validate AI-generated content, code, test results, and recommendations using appropriate human review, privacy, security, accessibility, SEO, and editorial controls.
- Strong communication, organization, facilitation, and decision-making skills.
Preferred qualifications list:
- Aprimo DAM or another enterprise digital asset management platform.
- Working knowledge of React, Next.js, Tailwind, Storybook, design systems, Figma, and component-based frontend development.
- Fluency with Jira, Service Desk, Asana, Azure DevOps, GitHub, CI/CD, and release-management workflows.
- A background leading CMS migrations, redesigns, campaign launches, or multi-site publishing programs.
- AI-forward workflow design involving spec-driven development, prompt and context design, tool integration, automation, human approval, and evaluation.
- Knowledge of accessibility standards, with a track record of improving accessible pages, documents, forms, or user experiences.
What success looks like: Could be included as a paragraph under Requirements or as a separate section "Qualifications"? Might be better to add a section "Qualifications" that includes both required and preferred, and then maybe a separate section "Success metrics"? But we can incorporate success looks like as a paragraph under Requirements (maybe after required qualifications). However the instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Required qualifications, Preferred qualifications, and What success looks like into a single "Qualifications" section with subheadings? But we cannot use subheadings other than
. Could use
bold? Not allowed? We can use
with strong text. That's okay.
Thus we could have:
About the role
...
Responsibilities
Requirements
with required qualifications (What you’ll bring). Could also separate Required vs Preferred? The instructions allow Qualifications section. Could combine required and preferred under Qualifications? But they said prefer a few substantive sections over many thin ones. Could have Requirements (required) and maybe Preferred qualifications as a subsection? But we can't create subheadings other than. Could combine both required and preferred under Requirements with two lists: Required and Preferred. But we need to preserve all info. Could have Requirements
then
Required qualifications:
then- list. Then
- . Might be long but okay.
Requirements (What you’ll bring): Required qualifications list:
- 5+ years in web publishing, content operations, frontend development, QA automation, digital operations, or a related discipline.
- Demonstrated ownership of production web content and publishing workflows from intake through launch.
- Hands-on knowledge of HTML, CSS, JavaScript/TypeScript, responsive web behavior, browser debugging, and frontend quality fundamentals.
- Experience with Builder.io, WordPress, or a comparable CMS, including templates, components, permissions, content models, and publishing controls.
- Hands-on experience with AI tools such as Claude, GitHub Copilot, Cursor, Builder.io AI, or comparable platforms for content operations, QA, documentation, workflow automation, or release preparation.
- Practical understanding of SEO, accessibility, usability, Core Web Vitals, analytics, consent, redirects, metadata, and conversion flows.
- Experience operating automated QA and release-quality processes.
- Demonstrated ability to prioritize competing work across business goals, deadlines, risks, dependencies, and capacity.
- Experience coordinating launches with product, marketing, content, design, SEO, analytics, QA, and engineering stakeholders.
- Demonstrated ability to validate AI-generated content, code, test results, and recommendations using appropriate human review, privacy, security, accessibility, SEO, and editorial controls.
- Strong communication, organization, facilitation, and decision-making skills.
Preferred qualifications list:
- Aprimo DAM or another enterprise digital asset management platform.
- Working knowledge of React, Next.js, Tailwind, Storybook, design systems, Figma, and component-based frontend development.
- Fluency with Jira, Service Desk, Asana, Azure DevOps, GitHub, CI/CD, and release-management workflows.
- A background leading CMS migrations, redesigns, campaign launches, or multi-site publishing programs.
- AI-forward workflow design involving spec-driven development, prompt and context design, tool integration, automation, human approval, and evaluation.
- Knowledge of accessibility standards, with a track record of improving accessible pages, documents, forms, or user experiences.
What success looks like: Could be included as a paragraph under Requirements or as a separate section "Qualifications"? Might be better to add a section "Qualifications" that includes both required and preferred, and then maybe a separate section "Success metrics"? But we can incorporate success looks like as a paragraph under Requirements (maybe after required qualifications). However the instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Required qualifications, Preferred qualifications, and What success looks like into a single "Qualifications" section with subheadings? But we cannot use subheadings other than
. Could use
bold? Not allowed? We can use
with strong text. That's okay. Thus we could have:
About the role
...
Responsibilities
Preferred qualifications:
then- list.
Then maybe
Success metrics
orWhat success looks like
but they didn't list that as allowed heading; allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They said use those as examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also use other headings if needed? Probably better to stick to those. So we could map "What success looks like" to maybe Skills? Not exactly. Could incorporate into Requirements or Responsibilities? Might be better to have a separate section like "Qualifications" for required and preferred, and "Skills" for success metrics? But success metrics is more about outcomes. Could treat as "Qualifications". However we need to preserve all substantive info; we can include it as a paragraph under Requirements or as a separate section like "Qualifications". The instruction: Prefer a few substantive sections over many thin ones. So maybe combine "What success looks like" and "Working model" into a section like "Working model" maybe under "Qualifications"? Hmm.
Better to have sections: About the role, Responsibilities, Requirements (including required and preferred), and maybe Working model (as a separate section). But Working model is not in the list of examples but could be considered as "Qualifications"? Not exactly. However the instruction says use those as examples, not exclusive. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. So we can use other headings if needed, but better to stick to those to be safe. However we need to convey working model and success metrics. Could incorporate them into Requirements or Responsibilities as prose.
Let's extract details:
About the role paragraph: "SolarWinds is seeking a Content Web Development Lead to modernize how web content is planned, created, tested, approved, and published. This role combines AI-forward workflow design, CMS and frontend expertise, QA automation, launch coordination, and team leadership. You will improve publishing across Builder.io, WordPress, Aprimo DAM, React and Next.js experiences, and the workflows connecting Web PMs, Content, SEO, Design, Analytics, Marketing, QA, and Web Development. This player-coach role combines hands-on contribution, team mentorship, operating-model improvement, and prioritization across competing work."
We could also include the earlier mission statement as intro paragraph before About the role? Might be considered boilerplate? It's about company purpose; could be included as a short paragraph before About the role. Not a heading. It's substantive. We'll include as a
before the first heading. Responsibilities (What you’ll do): list of bullet points: - Lead AI-forward content operations - Build governed, spec-driven agentic workflows for content intake, drafting, QA, approvals, and launches. - Use AI tools such as Claude, GitHub Copilot, Builder.io AI, or comparable platforms to improve requirements refinement, content operations, QA, documentation, triage, and release preparation. - Design agentic workflows for ticket intake, content drafting, metadata checks, test execution, issue creation, localization support, and launch-readiness reporting. - Govern automation with draft-first boundaries, human approval, audit trails, permissions, validation evidence, rollback procedures, and clear ownership. - Measure AI’s impact on delivery speed, throughput, quality, coverage, and team capacity while protecting security, accessibility, SEO, and editorial judgment. - Own web publishing and CMS delivery - Manage publishing from intake and prioritization through content preparation, preview, UAT, approval, launch, and post-launch validation. - Support Builder.io and WordPress templates, components, permissions, content models, revisions, and controlled releases. - Improve self-service publishing while ensuring complex layouts, integrations, SEO changes, and high-risk releases receive appropriate technical review. - Provide practical frontend guidance across HTML, CSS, JavaScript/TypeScript, responsive behavior, browser debugging, and component-based web experiences. - Support CMS migrations and modernization while preserving URLs, content structure, metadata, analytics, redirects, and business functionality. - Govern Aprimo DAM practices including asset metadata, classification, lifecycle status, approved-public usage, renditions, expiry, and page-usage tracking. - Lead QA automation and web quality - Establish automated testing for functional, visual, accessibility, SEO, links, analytics, performance, mobile, cross-browser, and production smoke coverage. - Use tools such as Playwright, Cypress, Applitools, Lighthouse, crawlers, and real-user monitoring to improve release confidence. - Define acceptance criteria and evidence requirements so every launch has named approvers, documented validation, and a rollback or remediation path. - Monitor defect escape rate, test coverage, recurring failure patterns, Core Web Vitals, accessibility issues, and post-launch performance. - Evaluate usability and user experience across desktop, mobile, content structure, navigation, forms, and key conversion paths. - Prioritize and coordinate launches - Partner with Web PMs on campaign, product, event, migration, redesign, and information-architecture launches. - Prioritize requests using business value, customer impact, SEO and accessibility risk, urgency, effort, dependencies, capacity, and launch timing. - Maintain transparent backlogs, roadmaps, launch calendars, SLAs, status reporting, and escalation paths. - Measure SLA attainment, publishing throughput, defect rates, and web performance to guide priorities and improvement. - Lead readiness reviews and go/no-go decisions covering content, functionality, SEO, analytics, accessibility, localization, approvals, rollback, communications, and monitoring. - Coordinate production communications, incident escalation, and post-launch reviews. - Lead and develop the team - Mentor web publishers, frontend contributors, QA automation specialists, and workflow owners through coaching, pairing, reviews, and knowledge sharing. - Establish standards for ownership, documentation, prioritization, communication, quality, and continuous improvement. - Turn recurring issues into reusable workflows, templates, automation, training, or operating procedures. - Partner across Web PM, Content, SEO, Design, Analytics, Marketing Operations, QA, Web Development, and campaign teams. We can flatten into a single list of responsibilities, each bullet as