Senior Manager, Systems Software Engineering

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if content exists. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Must not create sections with filler like "commensurate with experience". Must include Pay and Benefits only if posting actually states them. The posting includes salary range and benefits details. So we can include Pay and Benefits sections. Schedule? Not mentioned. So we should not include Schedule heading. Also Skills? The posting includes qualifications and responsibilities; we could put Skills under Qualifications or separate? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real, specific content. We have content for About the role (the initial paragraph). Responsibilities (list). Qualifications (list). Also there is a "Core Responsibilities" section with subcategories like Planning & Execution etc. That seems like more responsibilities detail; we can incorporate into Responsibilities. There's also a "Qualifications Disclaimer" etc. That's boilerplate? It's about immunization etc; might be considered legal boilerplate; we should remove. Also "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $146,300 - $306,400 per year. May be eligible for bonus, equity, and compensation deferral." That's Pay. Benefits list. So we need Benefits section with list of benefits. Also we have "Career Level - M3" maybe minor metadata; could be folded into short p or drop. "About Us" section is promotional; could be considered boilerplate? It's about company; maybe we can keep as About the role? Actually About the role is separate; About Us is company description; could be considered boilerplate but it's substantive about company. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not explicitly listed to remove, but it's generic marketing; but we might keep it as part of About the role? However we already have About the role paragraph; we could add About Us as a separate section maybe "About the Company"? Not in allowed headings. Allowed headings list does not include About Us. So we should not create a heading for it. Could fold into About the role paragraph? Might be okay to include as a

after About the role? But we must not invent headings. So we can just include the About Us paragraph as a

without a heading, or we could omit it as it's not required? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep About Us info. Since we cannot create a heading not in list, we can just put it as a

after the About the role heading? But About the role heading is for role description; we could combine both under About the role heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we can use those headings; we can also have other headings? Probably not; better to stick to those. So we can put About the role heading and include both the initial role description and the About Us paragraph under it. That preserves info. Now Responsibilities: we have a list under "Responsibilities" heading with bullet points. Also there is "Core Responsibilities" with subheadings Planning & Execution etc. We could incorporate those as sub-items under Responsibilities. But we must not invent headings like Planning & Execution unless we treat them as part of list items. Could make them as

with bold? But we must preserve content. We could create a nested list? The instruction: Use

• for any list of duties/requirements/benefits. So we can have a main
  for responsibilities, and inside we could have
  • that contain further
    for subpoints. That's acceptable. Similarly Qualifications: we have a list under "Qualifications" heading with bullet points. Also there is "Qualifications Disclaimer" etc which we should remove (legal). Also there is "Career Level - M3" maybe minor metadata; we can drop or put in a short p. We also have "Skills" heading not present explicitly; but we could extract skills from qualifications? Might be thin. Better not to create Skills section if no explicit skills list. The qualifications list includes skills like experience with platforms, understanding, etc. Could treat as Qualifications only. Now Benefits: we have a list of benefits. We'll create Benefits heading with
    • . Pay: we have salary range and bonus etc. We'll create Pay heading with

      containing that info. Now we must not include Schedule. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

      About the role

      We are seeking a Senior Manager, Systems Software Engineering to lead the strategy, delivery, and operational excellence of enterprise device-management systems and services. This role owns the technical roadmap and cross-functional execution for device policies, certification, approval workflows, vendor and procurement integrations, mobile and device lifecycle management, recycling, and printer services.

      Only Oracle brings together the data, infrastructure, applications, and expertise to power everything from industry innovations to life-saving care. And with AI embedded across our products and services, we help customers turn that promise into a better future for all. Discover your potential at a company leading the way in AI and cloud solutions that impact billions of lives. True innovation starts when everyone is empowered to contribute. That’s why we’re committed to growing a workforce that promotes opportunities for all with competitive benefits that support our people with flexible medical, life insurance, and retirement options. We also encourage employees to give back to their communities through our volunteer programs. We’re committed to including people with disabilities at all stages of the employment process. If you require accessibility assistance or accommodation for a disability at any point, let us know by emailing accommodation-request_mb@oracle.com or by calling 1-888-404-2494 in the United States. Oracle is an Equal Employment Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, national origin, sexual orientation, gender identity, disability and protected veterans’ status, or any other characteristic protected by law. Oracle will consider for employment qualified applicants with arrest and conviction records pursuant to applicable law.

      But note: The EEO statement is legal boilerplate; we should remove EEO/equal-opportunity boilerplate per instruction. So we must delete that paragraph. Also the accommodation request line maybe also legal? It's about accommodation; could be considered legal? It's about disability accommodation; might be considered EEO-related. Safer to remove that as well. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the EEO statement and accommodation request. Also the "Only Oracle brings together..." is marketing but not legal; we can keep. Thus About the role paragraph: first paragraph (role description) plus the marketing paragraph about Oracle (the "Only Oracle brings together..."). Now Responsibilities: We need to list responsibilities from the "Responsibilities" section and also incorporate "Core Responsibilities" subpoints. Let's extract responsibilities bullet points: - Lead and mentor a team of systems software engineers responsible for enterprise endpoint and device-management platforms. - Define and maintain scalable device policies across laptops, mobile devices, peripherals, and shared equipment, balancing security, usability, and compliance. - Own the device certification process for new hardware, operating systems, applications, and accessories; establish testing standards, approval criteria, and release readiness. - Design and improve automated approval workflows for device requests, exceptions, software access, procurement, and lifecycle changes. - Partner with IT, Security, Finance, Legal, Procurement, and business stakeholders to translate operational needs into reliable technical solutions. - Manage vendor relationships, technical evaluations, contract requirements, integrations, and service performance for endpoint, procurement, MDM, and printing partners. - Oversee procurement and mobile/device-management (MDM) processes, including asset enrollment, provisioning, inventory accuracy, replacement cycles, and support handoffs. - Develop sustainable device recycling and disposition programs, ensuring secure data wiping, chain-of-custody controls, regulatory compliance, and reporting. - Lead the architecture and operation of enterprise printing services, including secure print policies, printer fleet management, access controls, monitoring, and vendor coordination. - Establish metrics, dashboards, and operational reviews for service health, policy compliance, device lifecycle cost, certification throughput, and user experience. - Drive automation and self-service capabilities to reduce manual work, improve auditability, and accelerate employee access to approved devices and services. - Manage priorities, budgets, risks, and roadmaps across multiple concurrent systems and stakeholder groups. Now Core Responsibilities subcategories: Planning & Execution: - Creates and owns the execution plan for the team's work and multiple projects or initiatives, monitoring timelines and budgets when applicable to ensure projects are completed on time and in adherence with requirements. - Delegates work across the team and helps them prioritize their work. - Identifies resource needs and adapts plans based on changing priorities and business needs. Collaboration & Partnership: - Strengthens collaborative partnerships across teams to align expectations and shared objectives. - Guides team members to build relationships with business leaders, stakeholders, and/or customers to ensure effective collaboration. - Practices active listening and asks insightful questions to promote an inclusive culture. Problem Solving: - Leads team to identify and address moderately complex operational and/or technical issues in accordance with standard practices, providing guidance as appropriate. - Directs team to analyze data and/or information from multiple sources to troubleshoot moderately complex errors. Continuous Learning: - Actively seeks learning opportunities for self and team to enhance knowledge and skills in key areas and remain current with industry advancements. - Uses feedback and training to elevate personal and team skills, modeling a commitment to learning. - Identifies skill gaps within the team and supports team members in learning opportunities by providing resources and fostering an environment that encourages knowledge-sharing. Continuous Improvement: - Identifies and recommends improvements as well as encourages team to share ideas to increase the efficiency and effectiveness of processes, protocols, and workflows within a team. - Reviews and provides feedback on team member's ideas and seeks input from others on alternative approaches and methods for improving work. Performance and Development: - Coaches and provides direction to team members in alignment with performance management processes, guidelines, and expectations. - Facilitates goal setting discussions with team members, ensuring individual goals are aligned with broader team goals. - Identifies development opportunities to help team member's improve performance. - Contributes to the talent acquisition pipeline by leading candidate interviews, assessing promotion eligibility, and managing talent resources. We can incorporate these as sub-items under Responsibilities, maybe as nested lists. Now Qualifications: From Qualifications section: - 8+ years of experience in systems software engineering, endpoint engineering, IT engineering, or a related discipline. - 3+ years of people-management or technical-leadership experience. - Experience with enterprise device management platforms such as Microsoft Intune, Jamf, Workspace ONE, Kandji, or similar tools. - Strong understanding of endpoint security, identity/access management, device compliance, software deployment, and asset lifecycle management. - Demonstrated experience building workflow automation and integrations using APIs, scripting, or enterprise workflow platforms. - Experience managing vendors, procurement processes, hardware certification, and service delivery agreements. - Familiarity with secure asset disposition, recycling requirements, and enterprise printing environments. - Strong program-management, communication, and stakeholder-management skills. - Bachelor’s degree in Computer Science, Engineering, Information Systems, or equivalent practical experience. Also there is a "Qualifications Disclaimer" about immunization etc