Web Content Development Manager

We need to output HTML fragment with sections: About the role, Responsibilities (What you’ll do), Requirements (What you’ll bring), maybe Skills, Benefits, Pay, Schedule only if present. The posting includes "What you’ll do" (responsibilities), "What you’ll bring" (required and preferred qualifications). Also "Working model" mentions US time zone role, but not explicit schedule. No explicit pay or benefits. So we should include sections: About the role (maybe from intro? Actually there is an "About the role" heading in the posting). The text before "About the role" is generic company description; we should not repeat job title as heading, but we can include a paragraph about company? The instruction: "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." The intro about SolarWinds is not a heading; we can keep as a paragraph before the About the role section? The instruction: "Prefer a few substantive sections over many thin ones." We could include an introductory paragraph about the company as a

before the first heading. Then headings: About the role, Responsibilities, Requirements (maybe combine required and preferred?), Skills? The posting includes required qualifications and preferred qualifications; we could put them under Requirements (or Qualifications). The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include a section only when posting has real specific content. So we can have About the role (the paragraph after that heading). Responsibilities (What you’ll do). Requirements (maybe combine required qualifications). Skills (maybe list specific skills like HTML/CSS/JS, AI tools, etc). But we might combine required qualifications into Requirements and preferred into Skills? However the instruction says prefer few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements (including required and preferred), and maybe Skills? But we could embed skills within Requirements. Let's decide: Use About the role (intro description of role), Responsibilities (What you’ll do), Requirements (What you’ll bring – required qualifications), Skills (maybe list specific technical skills from required and preferred). But that could be thin. Better: About the role, Responsibilities, Requirements (including required and preferred). No separate Skills unless we have distinct list. The posting includes "Required qualifications" and "Preferred qualifications". We could put both under Requirements with subheadings? But we cannot add extra headings beyond allowed list? We could still use

• inside Requirements. We can separate required and preferred as separate
  with a preceding

  indicating required vs preferred. That's okay. We must not include boilerplate like EEO, privacy notice, etc. Remove those lines. We must preserve all substantive information. So we need to keep details about AI workflow, CMS, QA automation, launches, team leadership, etc. Let's extract content. Intro paragraph before About the role: "At SolarWinds, we’re a people-first company. Our purpose is to enrich the lives of the people we serve—including our employees, customers, shareholders, partners, and communities. Join us in our mission to help customers accelerate business transformation with simple, powerful, and secure solutions.The ideal candidate thrives in an innovative, fast-paced environment and is collaborative, accountable, ready, and empathetic. We’re looking for individuals who believe they can accomplish more as a team and create lasting growth for themselves and others. We hire based on attitude, competency, and commitment. Solarians are ready to advance our world-class solutions in a fast-paced environment and accept the challenge to lead with purpose. If you’re looking to build your career with an exceptional team, you’ve come to the right place. Join SolarWinds and grow with us!" We can keep that as a

  before the first heading. Then heading

  About the role

  followed by 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." Then heading

  Responsibilities

  then we need to capture "What you’ll do" content. It's a long list. We'll convert each bullet into
  • . The text includes paragraphs with multiple sentences; we can break into list items per sentence or per bullet. The original uses line breaks? It's a paragraph with sentences separated by periods. We'll create
    • for each distinct duty. Let's parse: - 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'll put each as
    • . Then heading

      Requirements

      (or Qualifications). We'll include required qualifications and preferred qualifications. Required qualifications paragraph: "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: "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." We can combine into a single
      • list, maybe separate required vs preferred with a

        preceding each list. We'll not include Benefits, Pay, Schedule as they are not present. We'll also include Working model? It's a paragraph: "This is a US time zone role with responsibility for collaboration, launch coordination, and production support during US business hours. The role is hands-on, cross-functional, and accountable for both the quality of published experiences and the workflows that deliver them." This is substantive; we could include it under a heading like "Working model" but not in allowed headings list? The allowed headings include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Working model is not listed; we could fold it into About the role or Responsibilities? Probably better to add a short paragraph after About the role before Responsibilities, maybe as part of About the role. But the instruction: "Prefer a few substantive sections over many thin ones." We could add a section "Working model" but it's not in the allowed list; we should not create arbitrary headings. So we should incorporate that content into existing sections, maybe under About the role or Responsibilities. Since it's about role expectations, we could add to About the role section as an extra paragraph. Thus About the role will have two paragraphs: the description and the working model. Now produce HTML fragment. We must not include or . Just the fragment. Let's craft:

        At SolarWinds, we’re a people-first company. Our purpose is to enrich the lives of the people we serve—including our employees, customers, shareholders, partners, and communities. Join us in our mission to help