Senior Manager, Platform Software Engineering, AI Acceleration, Developer Tools

We need to output HTML fragment with sections: About the role? Actually the posting includes "Job Description" then paragraphs. We need headings for sections like About the role, Responsibilities? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting and extract sections. The posting includes: - Job Description (intro paragraph) - Responsibilities (list of bullet-like sentences) - Required Qualifications (list) - Desired Qualifications (list) - Qualifications Disclaimer (some text about US based roles) - Range and benefit information (Pay and Benefits) - About Us (company description) - Some other paragraphs about onboarding, accommodations, EEO etc. Those are boilerplate to remove. We need to decide which sections to include: About the role (maybe the intro paragraph under Job Description). Responsibilities (list). Requirements (maybe combine Required Qualifications and Desired Qualifications? The instruction says we can have Requirements, Qualifications sections. Could separate Required Qualifications as Requirements, Desired Qualifications as Qualifications? Or combine? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly Skills not present. Schedule not present. We need to decide what content goes where. The posting includes: - Job Description paragraph: "The Developer Tools space is evolving rapidly..." That's about the role context. Could be About the role. - Responsibilities: a list of bullet points (starting with "Build, lead, and develop..."). - Required Qualifications: list of items (starting with "10+ years of software engineering experience..."). - Desired Qualifications: list (starting with "Experience building AI-powered developer tools..."). - Qualifications Disclaimer: about US based roles etc. Might be considered part of Qualifications? But it's a disclaimer; maybe we can include it under Qualifications as a note? However it's not a requirement; it's a disclaimer. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that disclaimer text somewhere. Could be placed under a "Qualifications" section as a note after the lists. Or we could have a separate "Qualifications" section that includes both Required and Desired plus disclaimer. But we also have a separate "Requirements" section maybe for Required Qualifications. Let's think. We need to avoid thin sections. Perhaps combine Required and Desired into one "Qualifications" section with subheadings? But we cannot use headings inside? We could just list them as

  • with maybe marking required vs desired? But we need to preserve the distinction. Could we have two sections: "Required Qualifications" and "Desired Qualifications"? The instruction gave examples but not limited to those. It said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't forbid other headings, but we should follow the pattern. Could use "Required Qualifications" and "Desired Qualifications" as headings; they are similar to Requirements and Qualifications. Might be okay. But we also have a "Qualifications Disclaimer" which is a paragraph; could be placed under a "Qualifications" section after the lists. We also have Pay and Benefits: The posting includes "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $120,000 - $306,400 per year. May be eligible for bonus, equity, and compensation deferral." Then a paragraph about Oracle maintains broad salary ranges etc. Then "Oracle US offers a comprehensive benefits package which includes the following:" followed by a list of benefits. Thus we have Pay (salary range) and Benefits (list). So we should have sections Pay and Benefits. We also have About Us: a paragraph about Oracle's mission etc. That could be "About the role"? Actually About the role is more about the job; About Us is about company. The instruction's example includes "About the role". Not "About Us". But we could put the company description under "About the role"? Might be misrepresent. However we could include an "About the company" section? Not in examples but maybe okay. But we should prefer few substantive sections. The About Us is substantive; we could include it as a section maybe "About the company". But the instruction didn't list that as example; but we can still use

    for any section heading. It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." implies those are examples, not exclusive. So we can add other headings like "About the company". However to be safe, we could incorporate the About Us paragraph into the "About the role" section as additional context. But the About the role currently is the introductory paragraph about Developer Tools space. Adding the company mission might be okay but could blur. However the instruction says preserve ALL substantive information; we need to keep that About Us paragraph somewhere. If we put it under About the role, we are still preserving it. It's not contradictory. Thus we can have sections: - About the role (intro paragraph + maybe About Us) - Responsibilities (list) - Required Qualifications (list) - Desired Qualifications (list) - Qualifications Disclaimer (paragraph) maybe under Qualifications? Could be a separate "Qualifications" section that includes the disclaimer after lists? But we already have Required and Desired sections. Could combine them into a single "Qualifications" section with two sublists? But we need to preserve the distinction; we could have a

    Qualifications and then inside have two

    maybe? But we are only allowed to use

    for section headings; we could still use

    but not specified. Safer to keep separate sections. - Pay (salary range paragraph) - Benefits (list) We also need to remove boilerplate: EEO, equal opportunity, scam warning, application instructions, etc. Also remove lines like "The role will generally accept applications for at least three calendar days..." etc. Also remove "As part of Oracle's onboarding process..." etc. Also remove "Accommodations to this requirement may be granted..." etc. Also remove "About Us" maybe we keep but we need to check if it's boilerplate? It's a company description; it's substantive but could be considered boilerplate? It's not legal/EEO; it's about Oracle's mission. It's okay to keep. We also need to remove duplicated lines. There's no duplication obvious. Now we need to format. We'll output something like:

    About the role

    The Developer Tools space is evolving rapidly as advances in large language models (LLMs), AI agents, and intelligent automation create new possibilities for how software is designed, built, tested, deployed, and operated. Many of the most valuable problems in this space do not yet have established solutions, architectures, or even clearly defined requirements. Success in this role therefore requires a leader who is comfortable operating in highly ambiguous environments, can identify the right problems to solve, and can turn emerging technologies and loosely defined opportunities into a clear engineering strategy and executable roadmap. As a Senior Manager, you will provide both organizational and technical leadership. You will build and develop a high-performing engineering team, establish priorities and operating mechanisms, and create clarity where requirements and technical approaches are still evolving. You will work closely with senior engineers, product managers, data scientists, AI/ML teams, and OCI service organizations to identify high-impact opportunities and take them from early exploration through architecture, production deployment, and broad adoption. You will be expected to balance experimentation with disciplined execution—enabling teams to move quickly in a rapidly changing AI landscape while maintaining the engineering rigor, security, reliability, and operational excellence expected of OCI 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.

    But note: The second paragraph includes EEO statement? Actually it includes accommodation request line and EEO? It includes "Oracle is an Equal Employment Opportunity Employer..." later. That part we need to remove. The About Us paragraph we extracted ends before the EEO line. Let's check the original: After "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." We need to remove the EEO lines. So we keep up to the accommodation line. Good. Now Responsibilities section: we need to list each responsibility as
  • . The responsibilities are a series of sentences separated by periods. Let's extract them: - Build, lead, and develop a high-performing engineering organization , hiring and growing engineers and technical leaders while establishing a culture of ownership, technical excellence, collaboration, and customer focus. - Create clarity from ambiguity by identifying high-value problems, defining engineering priorities, making informed tradeoffs with incomplete information, and translating broad opportunities in AI and developer productivity into actionable strategies and roadmaps. - Define and drive the engineering strategy for AI-powered developer tools, platforms, and intelligent software development workflows , balancing near-term delivery with longer-term platform investments. - Partner across product management, AI/ML, data science, platform engineering, and OCI service teams to establish shared priorities, influence technical direction, and drive complex initiatives across organizational boundaries. - Provide strong technical leadership across distributed systems, cloud-native architectures, AI/LLM integration, developer platforms, data and evaluation systems , ensuring architectural decisions support scale, extensibility, security, and operational excellence. - Establish mechanisms