Lead Principal Platform Software Engineer, AI Acceleration, Developer Tools

for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into 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 job description. Content: - Intro paragraph: "This is an emerging space where the technology, developer expectations, and best practices are changing quickly. We are looking for a technical leader who is energized by that uncertainty: someone who is willing to experiment, prototype, challenge established approaches, learn quickly, and form strong technical opinions based on evidence. You will explore new capabilities across LLMs, AI agents, reasoning systems, context and retrieval, evaluation, and intelligent automation, while determining which ideas can deliver meaningful and durable improvements to developer productivity. Success requires more than applying existing AI technologies. You will identify where AI can fundamentally change engineering workflows, develop a technical point of view on where we should invest, and define the architectures and platform capabilities needed to move promising ideas from experimentation to production at OCI scale. As a Lead Principal Engineer, you will influence the technical direction of AI-powered developer experiences across teams and organizational boundaries. You will work with senior engineers, engineering leaders, product managers, AI/ML teams, researchers, and OCI service organizations to identify opportunities, test hypotheses, establish architectural direction, and build alignment around consequential technical decisions. You will remain deeply hands-on. You will build prototypes, evaluate emerging technologies, design foundational systems, and work alongside engineers to prove what is possible. Equally important, you will know when an experiment has provided enough evidence to invest, pivot, or stop—and how to turn successful experimentation into reliable, secure, scalable platform capabilities." - Then "Responsibilities" heading (uppercase). Then list of responsibilities (multiple bullet-like sentences). They are separated by periods but each bullet is a sentence. We need to put them in

• . - Then "Required Qualifications" heading. Then list of required qualifications (multiple bullet-like sentences). Use
  • . - Then "Desired Qualifications" heading. Then list of desired qualifications (multiple bullet-like sentences). Use
    • . - Then "Qualifications Disclaimer:" paragraph about US based roles etc. This is boilerplate? It's legal/EEO? Might be considered boilerplate but it's not exactly EEO; it's about immunization/drug testing. Might be considered legal boilerplate; but we need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal disclaimer about immunization/occupational health mandates and drug testing. Likely considered legal boilerplate; we should remove it. - Then "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $96,800 - $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. Oracle US offers a comprehensive benefits package which includes the following: ..." This includes Pay (range) and Benefits list. So we need to include Pay and Benefits sections if they have real specific content. The posting states a hiring range and benefits list. So we should include Pay section with the range info, and Benefits section with the list. We must not include placeholder/filler like "commensurate with experience". The range is specific: $96,800 - $306,400 per year. Also mention bonus, equity, compensation deferral. That's substantive. 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 put these as
      • items. Also there is a line: "The role will generally accept applications for at least three calendar days from the posting date or as long as the job remains posted." That's application instructions; we should remove. Then "As part of Oracle's onboarding process and consistent with applicable law, US-based employees are required to complete identity verification, which involves the collection and processing of their biometric information. Accommodations to this requirement may be granted following an individualized assessment." This is legal/boilerplate; remove. Then "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. 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." This is EEO boilerplate; remove. Thus we keep: intro paragraph (maybe as About the role?), Responsibilities, Required Qualifications, Desired Qualifications, Pay, Benefits. We need headings: About the role (maybe we can use that heading for intro). The instructions: use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have h3 for each section we include. We should not repeat job title as heading. So we will not add a heading for the job title. We need to decide whether to combine Required and Desired Qualifications into a Qualifications section? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It mentions "Qualifications" as a possible heading. Could combine required and desired under Qualifications? But we have both required and desired; maybe we can have two subsections? However instruction: Prefer a few substantive sections over many thin ones. Could combine required and desired into one Qualifications section with two lists? But we need to preserve all substantive information; we can keep both lists under Qualifications heading, maybe separate with

        indicating Required vs Desired. Or we could have separate sections: Required Qualifications and Desired Qualifications, but that would be many thin sections. The instruction says prefer a few substantive sections over many thin ones. So better to have one Qualifications section, and within it we can have two

        headings? But we cannot use headings inside besides h3? We could use

        Required Qualifications:

        then list. That's acceptable. Similarly, we could have a Skills section? Not present. Thus sections: About the role (intro), Responsibilities, Qualifications (combined required and desired), Pay, Benefits. We need to ensure we don't include filler like "commensurate with experience". Not present. Now craft HTML. We'll start with

        About the role

        then

        intro paragraph. Then

        Responsibilities

        then
        with each responsibility as
        • . Responsibilities list from posting: - Build the architecture and technical strategy for AI Acceleration across Developer Tools, identifying where AI can materially improve developer productivity and establishing the foundational platforms, abstractions, and services required to enable those experiences. - Experiment aggressively and learn quickly by building prototypes, evaluating emerging models and agentic technologies, testing unconventional approaches, and using measurable results to determine which ideas should progress from exploration to production. - Create clarity from ambiguity by identifying high-value problems, forming technical hypotheses, challenging assumptions, evaluating competing approaches, and translating rapidly evolving AI capabilities into actionable architectural direction. - Influence technical direction across the org building alignment among senior engineers, engineering leaders, AI/ML teams, product organizations, and service teams around architectural choices and strategic investments without relying on direct authority. - Architect platforms for AI agents, LLM-powered developer experiences, context and retrieval, tool integration, orchestration, evaluation, and intelligent automation, with clear separation between rapidly evolving AI technologies and durable platform abstractions. - Establish a disciplined path from prototype to production, defining engineering patterns that allow successful experiments to evolve into secure, observable, reliable, cost-efficient, and scalable OCI services. - Raise the technical bar for AI engineering through architecture reviews, reference implementations, evaluation frameworks, technical mentorship, engineering standards, and clear communication of complex architectural tradeoffs. - Develop mechanisms to measure whether AI actually improves the developer experience, using evaluation, telemetry, experimentation, developer feedback, and productivity signals to guide technical decisions and future investment. - Anticipate changes in models, agent architectures, developer workflows, and AI infrastructure, designing platforms that can evolve without requiring fundamental rearchitecture as the underlying technology changes. - Serve as a senior technical voice for AI Acceleration and Developer Tools, shaping technical strategy and representing the organization in architecture reviews and cross-OCI technical forums. Make sure each is a separate
        • . Now Qualifications section: We'll have

          Qualifications

          . Then maybe

          Required Qualifications:

          then
          list required qualifications. Then

          Desired Qualifications:

          then
          list desired qualifications. Required qualifications list: - 12+ years of software engineering experience with a demonstrated track record of architecting complex production systems