Senior Manager, Core Infrastructure Engineering
for each section: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real content. The posting includes "Description" which is like About the role. It includes Responsibilities, Qualifications, and also a disclaimer about US location and range/benefits. There's also "About Us". Could map to "About the role" or maybe "About Us". The instruction: use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly.
We have description paragraph: "OCI is seeking a Senior Manager of Firmware Management to lead teams..." That's about the role. So we can put that in About the role
with
. Responsibilities: list items under RESPONSIBILITIES. We'll output
- each.
Qualifications: there is a Qualifications heading then a disclaimer about US based roles etc. Then "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." Then details about Oracle maintains broad salary ranges... Then "Oracle US offers a comprehensive benefits package which includes the following:" then list.
We need to separate Pay and Benefits sections. So Qualifications section should contain the qualifications (maybe the disclaimer about US based roles etc). But the posting didn't list explicit qualifications like education/experience; it's more about the role. However we have a "Qualifications" heading in the source. We'll include whatever is under that heading before the pay/benefits details. That includes: "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." That's it. Then after that comes the pay and benefits info. So we will put that disclaimer in Qualifications section as a
. Then Pay section: include the hiring range and bonus etc. Benefits section: list the benefits. We also have "About Us" section after benefits. Could map to "About the role"? But we already used About the role for the description. Maybe we can treat "About Us" as another section but not in the list of allowed headings? The instruction says use 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 (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should limit to those headings. So we should not add an "About Us" heading; we could incorporate that content into About the role or maybe omit? But we must preserve ALL substantive information. The About Us paragraph is substantive. We could add it to About the role section as additional paragraph. That would be okay. Thus final HTML:
About the role
OCI is seeking a Senior Manager of Firmware Management to lead teams responsible for the strategy, delivery, validation, and lifecycle management of firmware across our global cloud infrastructure. This leader will manage engineers who build and operate firmware solutions for server platforms and critical hardware components, including BIOS/BMC, storage, networking, accelerators, and platform security technologies. You will establish a high bar for firmware quality, security, fleet reliability, and operational excellence. Working across hardware engineering, infrastructure, security, supply-chain, and operations teams, you will drive safe firmware release processes—from vendor qualification and compatibility testing through staged deployment, monitoring, rollback, and incident response. The ideal candidate combines strong technical depth in systems and firmware with demonstrated people leadership. You are comfortable making risk-based decisions at hyperscale, developing engineering talent, and translating complex hardware and firmware concerns into clear operational plans.
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 we should remove EEO/equal-opportunity boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we must remove the EEO statement. Also remove the accommodation request line? That might be considered legal/accommodation but not EEO. It's about disability accommodation; might be considered legal but not EEO. The instruction says remove EEO/equal-opportunity boilerplate. The accommodation request line is not EEO but could be considered legal. However it's about providing accommodation for disability; might be considered part of equal opportunity. Safer to remove it? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The accommodation request is not exactly EEO but it's about disability accommodation; could be considered part of EEO. I'd remove it to be safe. Also remove the line about Oracle is an Equal Employment Opportunity Employer... and the arrest and conviction records line. So we will omit those. Thus the About the role section will contain the initial description paragraph and the "About Us" paragraph (without EEO). Let's extract the About Us paragraph: "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." We can keep that but remove the accommodation request line and EEO line. So we keep up to "We’re committed to including people with disabilities at all stages of the employment process." That's fine. Now Responsibilities: list each bullet. We need to preserve all substantive information. The responsibilities list: - Lead and develop a high-performing firmware engineering and management organization supporting OCI’s global infrastructure fleet. - Define the firmware lifecycle strategy for server and hardware platforms, including intake, qualification, release, deployment, maintenance, and end-of-life planning. - Establish scalable standards for firmware versioning, configuration management, validation, release readiness, and change control. - Drive cross-functional firmware qualification with hardware vendors, platform engineering, security, supply chain, and cloud operations teams. - Oversee validation for BIOS, BMC, storage, network, accelerator, and other platform firmware, emphasizing compatibility, performance, reliability, and security. - Ensure safe fleet deployment mechanisms, including phased rollouts, health monitoring, automated remediation, rollback plans, and operational readiness. - Establish measurable reliability, availability, security, and deployment KPIs; use telemetry and dashboards to identify risks and improve fleet health. - Lead investigation and resolution of complex firmware-related incidents, defects, regressions, and interoperability issues. - Partner with security teams to ensure firmware integrity, secure boot, vulnerability remediation, access control, and compliance requirements are met. - Drive automation and infrastructure-as-code practices that reduce manual operational work and improve repeatability of firmware updates. - Manage multiple medium- to large-scale programs, balancing technical risk, business priorities, customer impact, timelines, and available resources. - Build strong relationships with internal stakeholders and external hardware and firmware vendors; influence product roadmaps and escalation paths. - Coach managers and engineers, set clear goals, provide performance feedback, build succession plans, and grow the firmware talent pipeline. - Foster a culture of operational ownership, continuous learning, inclusion, and continuous improvement. We'll output each as - .
Qualifications: we have the disclaimer: "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." We'll put that as
. Pay: we have "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. Oracle maintains broad salary ranges for its roles in order to account for variations in knowledge, skills, experience, market conditions and locations, as well as reflect Oracle's differing products, industries and lines of business. Candidates are typically placed into the range based on the preceding factors as well as internal peer equity." We'll put that as
under Pay. Benefits: list: "Oracle US offers a comprehensive benefits package which includes the following:" then list items: - 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'll output each as
- under Benefits. We should not include Schedule section. We must not include any markdown code fences. Just raw HTML. Let