Senior Manager, Systems Software Engineering

We need to output HTML fragment with sections: About the role? The job description includes "Job Description" then paragraphs. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real content. We need to parse the posting: It includes: - Job Description paragraph: "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." That's like an overview; could be "About the role". We'll put that in

. - Responsibilities: list of key responsibilities (bulleted). We'll put under

Responsibilities

with

• each. - Qualifications: includes bullet list of qualifications (8+ years etc). Also later "Core Responsibilities" which seems like more responsibilities but maybe part of responsibilities. Also there is "Qualifications Disclaimer" etc. We need to include qualifications section with the list. - Benefits: there is a long benefits list after "Oracle US offers a comprehensive benefits package which includes the following:" then bullet list. - Pay: there is "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 info. So we need a Pay section. - Schedule: not mentioned. No schedule info. So we omit Schedule. - Skills: maybe not explicit separate; but we could include under Qualifications or Skills? The instruction: use headings for Skills if present. There's no explicit Skills section; we could omit. - About the role: we have overview paragraph. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: EEO, legal, etc. Also remove "About Us" maybe? It's not required but could be considered boilerplate? It's about company; but we might keep as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Us" paragraph is not exactly boilerplate but could be considered company description; but we might keep it as part of About the role? However we already have overview; the "About Us" is more generic. Safer to omit it as it's not specific to role. Also remove "Career Level - M3". Also remove "The role will generally accept applications..." etc. Also remove "Disclaimer: Certain U.S. based..." maybe part of qualifications? It's a disclaimer; could be considered boilerplate; but it's about immunization etc. Might be considered legal; better to remove. Also remove "Range and benefit information provided in this posting are specific to the stated locations only US:" but we need to keep the pay range. The sentence includes that phrase; we can keep the pay range but maybe drop the prefatory phrase. We'll keep the pay range and bonus eligibility. We must preserve all substantive information; not invent or summarize away detail. So we need to keep all responsibilities, qualifications, benefits, pay. We need to format as HTML fragment only. Let's extract responsibilities list: From "Key Responsibilities" then 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. Then later "Core Responsibilities" with subheadings: Planning & Execution, Collaboration & Partnership, Problem Solving, Continuous Learning, Continuous Improvement, Performance and Development. Those are also responsibilities but more generic leadership competencies. Should we include them? They are substantive; we could include them under Responsibilities as additional items. However they are formatted as headings with bullet points. We could treat them as sub-sections but instruction: use

  for section headings only; we could keep them as

  • under Responsibilities. But they'd lose the subheading. However we could keep them as separate

    sections? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

    for section headings (list). It implies we should use those headings for sections. It doesn't say we cannot have other headings, but better to stick to those. The "Core Responsibilities" could be considered part of Responsibilities; we can incorporate its bullet points as list items under Responsibilities. Thus we need to extract those bullet points: Under 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'll include these as list items under Responsibilities. Now Qualifications list: 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. Then there is "Qualifications Disclaimer: Certain U.S. based or U.S. customer or client-facing roles may be required to comply with applicable requirements, such as immunization/occupational health mandates, and/or drug testing requirements." This is a disclaimer; could be considered boilerplate/legal; we should remove. Then later "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. Then benefits list: - Medical, dental, and vision insurance, including expert medical opinion - Short term disability and long term disability - Life insurance and AD&D - Supplemental life insurance (Employee/Spouse/Child) - Health care and dependent care Flexible Spending Accounts - Pre-tax commuter and parking benefits - 401(k) Savings and Investment Plan with company match - Paid time off: Flexible Vacation is provided to all eligible employees assigned to a salaried (non-overtime eligible) position. Accrued Vacation is provided to all other employees eligible for vacation benefits. For employees working at least 35 hours per week, the vacation accrual rate is 13 days annually for the first three years of employment and 18 days annually for subsequent years of employment. Vacation accrual is prorated for employees working between 20 and 34 hours per week. Employees working fewer than 20 hours per week are not eligible for vacation. - 11 paid holidays - Paid sick leave: 72 hours of paid sick leave upon date of hire. Refreshes each calendar year. Unused balance will carry over each year up to a maximum cap of 112 hours. - Paid parental leave - Adoption assistance - Employee Stock Purchase Plan - Financial planning and group legal - Voluntary benefits including auto, homeowner and pet insurance We need to keep all that. Now Pay section: we need to include the hiring range and bonus eligibility. We'll phrase as: "Hiring Range in USD: $146,300 - $306,400 per year. May be eligible for bonus, equity, and compensation deferral." We should not include the prefatory sentence about "Range and benefit information provided in this posting are specific to the stated locations only US:" as it's boilerplate; but we can keep the range and bonus. Now About the role: we have the initial paragraph. Could also include the sentence "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." That's part of the overview. Thus About the role paragraph: "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