Web-Based Tools Management Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule only if present. The posting includes description, required skills, desired skills, what you will be doing, tech breakdown, daily responsibilities. No explicit Benefits, Pay, Schedule. So we should not create those sections. We need headings: About the role (maybe intro), Responsibilities (daily responsibilities), Requirements (required skills & experience), Qualifications (maybe education?), Skills (desired skills & experience?), maybe combine. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include those that have content. We must not repeat job title. Also we should not include metadata like Posted By. Remove boilerplate. So we need to extract substantive info. Let's parse: Intro: "Take ownership of the web-based tools that help internal teams and customers access critical technical content and services. As a Senior Web-Based Tools Management Engineer, you’ll guide tool development from early concepts through implementation while supporting portals, content management platforms, automation, cloud infrastructure, and customer-facing applications. This role is ideal for a technology leader who enjoys turning business needs into useful, reliable tools. You’ll help shape the strategy for both quick-turn solutions and larger platform initiatives, explore ways to apply AI and automation, and work across engineering, infrastructure, security, vendors, and customer teams. The right candidate is entrepreneurial, technically curious, and motivated by seeing their work adopted in real-world operations." That's about the role. Required Skills & Experience bullet list: - 5–8 years of experience in web content management, web-based development, or a related technology field - Bachelor’s degree in Engineering, Computer Science, Web Development, or a related field—or equivalent experience - Experience managing and implementing web-based information management or customer engagement tools - Ability to translate customer and business requirements into technical specifications and product improvements - Understanding of web application security, technical infrastructure, cloud governance, and automation - Strong communication, problem-solving, project management, and cross-functional collaboration skills Desired Skills & Experience: - Advanced degree in Engineering, Computer Science, or a related discipline - Experience integrating AI and automation into web-based tools - Experience with content management systems, portals, file-transfer tools, or collaboration platforms - Experience with data center architecture, infrastructure design, or cloud governance planning - Familiarity with telecommunications technologies and operational processes - Experience managing vendors, development resources, or multiple concurrent projects What You Will Be Doing (Responsibilities): - Manage the development, enhancement, and support of internal and external web-based tools - Create short-term and long-term strategies for improving tool efficiency and customer experience - Define requirements and benchmark standards for information and content management platforms - Guide the integration of AI and automation into new and existing tools - Oversee security, software, infrastructure, hardware, and compliance requirements - Manage tooling scripts, automation initiatives, vendor coordination, project updates, and implementation activities Tech Breakdown (percentages) maybe not needed as separate section; could be part of responsibilities? But we can include as a list under Responsibilities or maybe separate? The instruction: include a section ONLY when posting has real, specific content for it. Tech Breakdown is specific content; but we don't have a heading for it in the allowed list. Could we put under Responsibilities? Probably better to include as a bullet list under Responsibilities or maybe as a separate section named "Tech Breakdown" but not allowed headings. The allowed headings list is just examples; we could still use other headings? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should stick to those? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings. Tech Breakdown could be part of Responsibilities or maybe under Skills? Not ideal. Could include as a

paragraph under Responsibilities. Daily Responsibilities list similar to What You Will Be Doing; we can combine. Thus sections:

About the role

...

Responsibilities

• ... (combined from What You Will Be Doing and Daily Responsibilities)

Requirements

• ... (Required Skills & Experience)

Qualifications

• ... (Bachelor's degree etc? Actually that's also in Requirements. Could split: Requirements = experience, Qualifications = education. But we have both. Let's put education under Qualifications.

Skills

• ... (Desired Skills & Experience)

We must not include Benefits, Pay, Schedule. We need to preserve all substantive info; not invent or summarize away detail. So we need to keep each bullet exactly as given, maybe rephrase slightly? Must not invent. We can copy the bullet points. Let's extract bullets: Required Skills & Experience: - 5–8 years of experience in web content management, web-based development, or a related technology field - Bachelor’s degree in Engineering, Computer Science, Web Development, or a related field—or equivalent experience - Experience managing and implementing web-based information management or customer engagement tools - Ability to translate customer and business requirements into technical specifications and product improvements - Understanding of web application security, technical infrastructure, cloud governance, and automation - Strong communication, problem-solving, project management, and cross-functional collaboration skills Desired Skills & Experience: - Advanced degree in Engineering, Computer Science, or a related discipline - Experience integrating AI and automation into web-based tools - Experience with content management systems, portals, file-transfer tools, or collaboration platforms - Experience with data center architecture, infrastructure design, or cloud governance planning - Familiarity with telecommunications technologies and operational processes - Experience managing vendors, development resources, or multiple concurrent projects What You Will Be Doing: - Manage the development, enhancement, and support of internal and external web-based tools - Create short-term and long-term strategies for improving tool efficiency and customer experience - Define requirements and benchmark standards for information and content management platforms - Guide the integration of AI and automation into new and existing tools - Oversee security, software, infrastructure, hardware, and compliance requirements - Manage tooling scripts, automation initiatives, vendor coordination, project updates, and implementation activities Daily Responsibilities: - Manage tool development projects from initial concept through implementation - Gather requirements and coordinate with customers, business teams, engineers, and vendors - Review platform security, infrastructure, software, hardware, and compliance needs - Identify opportunities to improve tools through automation and AI capabilities - Track project timelines, deliverables, risks, decisions, and implementation progress - Communicate updates, resolve issues, and challenge processes that limit efficiency We can combine What You Will Be Doing and Daily Responsibilities into Responsibilities section, ensuring we don't duplicate similar items. There is some overlap: both mention managing development, requirements, security, AI, vendor coordination, etc. We should keep all distinct bullets; but if duplicates appear we could merge but must preserve all substantive info; merging could lose nuance. Safer to keep both lists but maybe combine and deduplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we combine and remove duplicates, we might lose some nuance but not lose info if we keep each unique bullet. Overlap: "Manage the development, enhancement, and support of internal and external web-based tools" vs "Manage tool development projects from initial concept through implementation" similar but not identical. Keep both. "Create short-term and long-term strategies for improving tool efficiency and customer experience" vs none else. "Define requirements and benchmark standards for information and content management platforms" vs "Gather requirements and coordinate with customers, business teams, engineers, and vendors" similar but distinct. "Guide the integration of AI and automation into new and existing tools" vs "Identify opportunities to improve tools through automation and AI capabilities" similar but distinct. "Oversee security, software, infrastructure, hardware, and compliance requirements" vs "Review platform security, infrastructure, software, hardware, and compliance needs" similar. "Manage tooling scripts, automation initiatives, vendor coordination, project updates, and implementation activities" vs "Track project timelines, deliverables, risks, decisions, and implementation progress" vs "Communicate updates, resolve issues, and challenge processes that limit efficiency". Keep all. Thus Responsibilities list will be long but okay. Now Qualifications: maybe just the Bachelor's degree? But we already included Bachelor's degree in Required Skills & Experience. Actually the Required list includes Bachelor's degree. So we could treat Requirements as experience and skills, Qualifications as education. But we have Bachelor's degree in Required list; we could move it to Qualifications. Let's decide: Requirements: experience items (5-8 years, managing tools, ability to translate, understanding of security, strong communication). Qualifications: education items (Bachelor's degree, Advanced degree desired? Actually Advanced degree is desired, not required). So Qualifications could be Bachelor's degree (required) and maybe also note Advanced degree as desired? But desired goes under Skills. We'll put Bachelor's degree under Qualifications. Thus:

Requirements

• 5–8 years of experience in web content management, web-based development, or a related technology field
• Experience managing and implementing web-based information management or customer engagement tools
• Ability to translate customer and business requirements into technical specifications and product improvements
• Understanding of web application security, technical infrastructure, cloud governance, and automation
• Strong communication, problem-solving, project management, and cross-functional collaboration skills

Qualifications

• Bachelor’s degree in Engineering, Computer Science, Web Development, or a related field—or equivalent experience

Skills

• Advanced degree in Engineering, Computer Science, or a related discipline
• Experience integrating AI and automation into web-based tools
• Experience with content management systems, portals, file-transfer tools, or collaboration platforms
• Experience with data center architecture, infrastructure design, or cloud governance planning
• Familiarity with telecommunications technologies and operational processes
• Experience managing vendors, development resources, or multiple concurrent projects

Responsibilities

• Take ownership of the web-based tools that help internal teams and customers access critical technical content and services.
• As a Senior Web-Based Tools Management Engineer, guide tool development from early concepts through implementation while supporting portals, content management platforms, automation, cloud infrastructure, and customer-facing applications.
• Help shape the strategy for both quick-turn solutions and larger platform initiatives, explore ways to apply AI and automation, and work across engineering, infrastructure, security, vendors, and customer teams.
• Manage the development, enhancement, and support of internal and external web-based tools
• Create short-term and long-term strategies for improving tool efficiency and customer experience
• Define requirements and benchmark standards for information and content management platforms
• Guide the integration of AI and automation into new and existing tools
• Oversee security, software, infrastructure, hardware, and compliance requirements
• Manage tooling scripts, automation initiatives, vendor coordination, project updates, and implementation activities
• Manage tool development projects from initial concept through implementation
• Gather requirements and coordinate with customers, business teams, engineers, and vendors
• Review platform security, infrastructure, software, hardware, and compliance needs
• Identify opportunities to improve tools through automation and AI capabilities