Engineering Manager, Software Development & Digital Platforms (No Sponsorship Provided)

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. The posting includes: About The Opportunity (we can map to About the role). Key Responsibilities (Responsibilities). Required Qualifications (Requirements/Qualifications). Preferred Qualifications (maybe Skills? but we can treat as Qualifications? Actually we have sections: Requirements, Qualifications, Skills. We need to decide mapping. The posting includes "Required Qualifications" and "Preferred Qualifications". Also "Compensation & Benefits" includes salary range and benefits. So we can have sections: About the role (About The Opportunity), Responsibilities (Key Responsibilities), Requirements (Required Qualifications), Qualifications (Preferred Qualifications maybe?), Benefits (Compensation & Benefits includes benefits). Pay (Salary Range). Schedule? Not mentioned (Hybrid location but schedule not specified). So we should not include Schedule section because no specific content. Also Skills? Not explicit separate; we could embed technical skills within Requirements/Qualifications. But we could create a Skills section if we have specific list of skills. The posting lists many technologies under Required Qualifications: "Strong hands-on experience with several of the following technologies: ..." That's a list of skills. Could create a Skills section. However we must not repeat content; we need to preserve all substantive info. If we create Skills section, we need to move that list there, but then we would lose it from Requirements. Better to keep it within Requirements or Qualifications. The instruction: Use headings for sections (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include multiple of those as appropriate. We need to decide which sections to include based on content. We have content for About the role, Responsibilities, Required Qualifications (leadership experience, technical expertise, software delivery experience, AI & Innovation), Preferred Qualifications (additional experience, education), Compensation & Benefits (salary range, benefits). No explicit Skills separate, but we could treat the technical expertise list as Skills. However the Required Qualifications already includes leadership experience etc. Might be okay to have Requirements section covering leadership experience, and Qualifications covering technical expertise and preferred qualifications. But we also have Skills heading; we could put the list of technologies there. However that would split the Required Qualifications content. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all details. If we split, we still preserve all details, just moved. That's okay as long as we don't lose or invent. So we can create sections: About the role, Responsibilities, Requirements (leadership experience, software delivery experience, AI & Innovation), Qualifications (technical expertise list), Skills (maybe we could combine technical expertise and preferred qualifications? Hmm). Actually we have two qualification sections: Required Qualifications and Preferred Qualifications. Could map Required Qualifications to Requirements section, and Preferred Qualifications to Qualifications section. Then Skills could be omitted or we could put the technical expertise list under Skills. But then we would lose technical expertise from Requirements/Qualifications. Better to put technical expertise under Skills, and keep leadership experience etc under Requirements, and preferred qualifications under Qualifications. Let's see if that covers all. Required Qualifications includes: - Leadership Experience: 10+ years software dev, 5+ years managing teams, experience leading multiple teams, partnering with stakeholders. - Technical Expertise: strong hands-on experience with several of the following technologies: list. - Software Delivery Experience: experience delivering enterprise software using Agile, understanding modern architecture, building high-volume digital commerce platforms, designing scalable APIs, expertise with automated testing, DevOps, secure SDLC. - AI & Innovation Experience: implementing AI-assisted dev tools, understanding AI benefits, ability to evaluate emerging tech. Preferred Qualifications: - Experience supporting B2B/B2C eCommerce platforms. - Experience within manufacturing, industrial, distribution, logistics, or related environments. - Mobile app development experience across iOS, Android, Windows. - Exposure to A/B testing and experimentation frameworks. - Experience managing globally distributed engineering teams. - Education: Bachelor's degree required; Master's preferred. Thus we can allocate: - Requirements: Leadership Experience + Software Delivery Experience + AI & Innovation Experience (maybe combine). - Qualifications: Technical Expertise (list of technologies) + Education (Bachelor's required, Master's preferred). - Skills: maybe we could put the list of technologies under Skills instead, but then Qualifications would be just education. However we need to keep all info; we can put technical expertise under Skills, and education under Qualifications. That seems reasonable. But we also have Preferred Qualifications items like B2B/B2C eCommerce, manufacturing experience, mobile dev, A/B testing, global teams. Those could go under Skills as well, or maybe under Qualifications as "Preferred Qualifications". However we already used Qualifications for education; we could rename Qualifications to "Preferred Qualifications". But the heading list includes Qualifications (generic). We can put preferred qualifications there. Then Skills could be technical expertise list. Let's decide: Sections: - About the role (About The Opportunity) - Responsibilities (Key Responsibilities) - Requirements (Leadership Experience, Software Delivery Experience, AI & Innovation Experience) - Skills (Technical Expertise list) - Qualifications (Preferred Qualifications + Education) - Benefits (Compensation & Benefits benefits list) - Pay (Salary Range) We should not include Schedule. Now we need to format each section with

heading, then content: either

for prose,

• for lists. We must not include boilerplate like EEO, etc. Not present. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must preserve all substantive info. Let's extract content. About The Opportunity paragraph: "Recruit22 is seeking an experienced Engineering Manager to lead software engineering teams responsible for building and scaling modern digital platforms that support global business operations. This leader will oversee the development and delivery of enterprise applications, eCommerce solutions, cloud-native services, AI-enabled capabilities, and integration platforms. The ideal candidate combines strong technical expertise with proven leadership experience managing multiple engineering teams, driving modernization initiatives, and delivering scalable, secure, and high-performing software solutions. This position offers the opportunity to influence architecture strategy, cloud transformation efforts, AI adoption, and engineering excellence across a complex technology ecosystem." We'll put that in

  . Key Responsibilities: bullet list under headings: Engineering Leadership, Software Delivery & Architecture, Cloud & DevOps, AI & Emerging Technologies, Team Development. Each has sub-bullets. We need to preserve all detail. We'll create a

  with
  • for each top-level responsibility, and inside each
  • we can have
    for sub-items. That's acceptable. Required Qualifications (we will split into Requirements, Skills, Qualifications). Let's parse. Leadership Experience (under Requirements): - 10+ years of software development experience. - 5+ years managing software engineering teams. - Experience leading multiple development teams, managers, contractors, and vendor resources. - Proven success partnering with senior business and technology stakeholders. Software Delivery Experience (under Requirements): - Experience delivering enterprise software using Agile methodologies. - Strong understanding of modern software architecture and distributed systems. - Experience building and supporting high-volume digital commerce platforms. - Expertise designing scalable APIs and cloud-native applications. - Experience with automated testing, DevOps practices, and secure software development. AI & Innovation Experience (under Requirements): - Experience implementing AI-assisted development tools and workflows. - Understanding of how AI can improve software delivery, operational efficiency, and engineering effectiveness. - Ability to evaluate and implement emerging technologies that create business value. Technical Expertise (under Skills): - Strong hands-on experience with several of the following technologies: - C# .NET Core / ASP.NET Core - JavaScript / TypeScript - Node.js - React - REST APIs - GraphQL - SQL Server - PostgreSQL - MySQL - NoSQL Databases - Redis - Kafka - Azure Service Bus - Event Hub - Microservices Architecture - Event-Driven Architecture - Docker - Kubernetes - CI/CD Pipelines - Azure, AWS, or GCP Preferred Qualifications (under Qualifications): - Experience supporting B2B and B2C eCommerce platforms. - Experience within manufacturing, industrial, distribution, logistics, or related environments. - Mobile application development experience across iOS, Android, or Windows platforms. - Exposure to A/B testing and experimentation frameworks. - Experience managing globally distributed engineering teams. - Education: Bachelor's degree in Computer Science, Information Systems, Engineering, or related field required. - Master's degree, MBA, or advanced technical degree preferred. Compensation & Benefits: - Salary Range: $145,000 - $210,000 annually - Compensation will be determined based on experience, technical expertise, leadership background, and overall qualifications. - Additional benefits may include: - Health, Dental, and Vision Insurance - 401(k) Program - Paid Time Off - Paid Holidays - Life Insurance - Short-Term and Long-Term Disability Coverage - Performance-Based Incentive Opportunities We need to separate Pay and Benefits sections. Pay: salary range and note about determination. Benefits: list of benefits. We should not include filler like "commensurate with experience". The note about compensation determination is substantive; we can keep. Now produce HTML. Structure:

    About the role

    ...

    Responsibilities

    • Engineering Leadership
      • Lead and mentor multiple software development teams, managers, architects, developers, and engineers.
      • Establish engineering best practices, development standards, and software delivery processes.
      • Partner with Product, Architecture, Data, Infrastructure, DevOps, and business stakeholders to deliver strategic technology initiatives.
      • Foster a culture of accountability, innovation, collaboration, and continuous improvement.
      • Manage engineering capacity, resource allocation, project prioritization, and delivery commitments.
    • Software Delivery & Architecture
      • Drive the design, development, and deployment of enterprise-scale applications and digital platforms.
      • Lead modernization initiatives involving cloud-native architectures, microservices, APIs, and event-driven systems.
      • Oversee full software development lifecycle activities using Agile and Scrum methodologies.
      • Ensure delivery of secure, scalable, resilient, and maintainable software solutions.
      • Collaborate with architects and product teams to define technical roadmaps and solution designs.
    • Cloud & DevOps
      • Support cloud transformation initiatives across Azure, AWS, or similar cloud environments.
      • Promote adoption of CI/CD pipelines, Infrastructure as Code (IaC), automated testing, and containerization technologies.
      • Drive operational excellence through observability, monitoring, telemetry, and performance metrics.
      • Champion engineering practices that improve deployment reliability, scalability, and system performance.
    • AI & Emerging Technologies
      • Lead adoption of AI-assisted engineering tools and processes.
      • Identify opportunities to improve engineering productivity and software quality through AI-driven solutions.
      • Collaborate with technical teams to implement scalable AI-enabled business and operational capabilities.
    • Team Development
      • Coach and mentor engineers and engineering leaders.
      • Support career growth, technical skill development, and leadership readiness.
      • Conduct performance reviews, establish goals, and provide ongoing feedback.
      • Build and maintain high-performing engineering teams.

    Requirements

    Leadership Experience

    • 10+ years of software development experience.