Principal Software Engineer, Platform

We need to output only HTML fragment, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real specific content. We need to parse the job description. First, note the job title is not repeated as heading. The content includes "Job Description Responsibilites:" then bullet-like sentences. We need to extract sections: About the role? There's a paragraph at end: "About Us Only Oracle brings together..." That's about the company, not about the role. There's no explicit "About the role" section. Could we infer? The instruction: include a section ONLY when the posting has real, specific content for it. So we should not create About the role if not present. However there is some description of role in the responsibilities. Could treat that as Responsibilities. We have Responsibilities: there is a block after "Job Description Responsibilites:" then later "Responsibilities Key Responsibilities". So we have responsibilities content. Qualifications: there is a "Qualifications" block after responsibilities, then later "Qualifications Disclaimer:" etc. Skills: maybe we can extract skills from qualifications: deep expertise with Oracle 19c, Python/Shell, etc. Could be a Skills section. Benefits: there is a block about benefits: "Oracle US offers a comprehensive benefits package which includes the following: ..." So we can create Benefits section. Pay: there is "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $104,500 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral." So we have Pay. Schedule: not mentioned. No schedule info. So we should not create Schedule. Also there is "About Us" but not "About the role". So we skip About the role. We need to preserve all substantive information, not invent or summarize away detail. Use

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

  for prose. We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Qualifications Disclaimer:" maybe it's boilerplate? It's about immunization etc. Might be considered boilerplate? It's a disclaimer about US based roles. Might be considered legal boilerplate; we should remove it. Also remove "The role will generally accept applications for at least three calendar days..." that's application instructions; remove. Also remove "As part of Oracle's onboarding process..." that's also boilerplate. Remove "About Us" maybe? It's not about the role but could be considered company description; but instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not explicitly prohibited, but we should only include sections when posting has real specific content for it. There's no "About the role" heading; but we could include a section like "About the role" if we have prose describing the role. However we already have responsibilities covering role. The "About Us" is about company, not role. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should stick to those. Probably we should not include About Us. Thus sections: Responsibilities, Qualifications, Skills, Benefits, Pay. We need to extract responsibilities content: The responsibilities block includes many bullet-like sentences. We need to turn them into

  • . We must preserve all substantive information; not invent or summarize away detail. So we need to list each responsibility as a list item. Let's parse responsibilities section: From the text: "Job Description Responsibilites: Lead engineering and operational management for highly available, large-scale Oracle database fleets.Drive Oracle 19c performance analysis, complex tuning, diagnostics, and reliability improvements.Design and implement database architecture, access methods, allocation strategies, validation controls, protection, and security standards.Build scalable fleet-management automation and tooling using Python and/or Shell scripting.Lead technical analysis for database upgrades, patches, enhancements, and architectural changes.Define long-range database capacity, availability, and operational requirements with OCI service owners.Lead incident response, root-cause analysis, and prevention initiatives for complex production issues.Mentor engineers, review designs and code, and establish operational best practices and runbooks.Collaborate with Compute, Storage, Networking, Governance, and other OCI teams to deliver resilient cloud services." Then later "Responsibilities Key Responsibilities Platform Software Development: Lead cross-team evolution of middleware patterns or runtimes to standardize interoperability at scale.Define and enforce versioning, deprecation, and rollout strategies that minimize downstream breaks.Drive shared observability baselines (SLOs, error budgets) and resilience patterns across several services. Software Development and Coding - Design, Testing, and Optimization: Designs software solutions and analyzes and identifies requirements to achieve business and operational goals, sharing results with manager upon completion.Adheres to and improves execution of all phases of the software development lifecycle; provides guidance and coaching to engineers to drive improvements.Utilizes advanced knowledge to develop and guide new software features and enhancements leading design specifications, ensuring accessibility, and develops documents to clarify software design and code.Leads code reviews in multiple areas to help drive improvements.Conducts debugging and troubleshooting to identify and fix complex software issues.Develops fixes for identified issues.Implements comprehensive software testing (e.g., functional and non-functional testing), quality assurance processes, software error logging, monitoring, and observability for effective debugging, sharing work with manager and/or lead upon completion.Conducts performance profiling and optimization of coding, building scalable solutions, and anticipating and resolving potential outcomes.Troubleshoots and resolves complex issues related to application programming interface (API) functionality and integration.Implements complex API versioning, lifecycle, and interoperability strategies. Software Architecture - Software System Structural Design: Implements and contributes to developing software, systems, and services, ensuring review by manager and/or senior technical leaders upon completion. Recommends project or design scope.Provides technical guidance and coaching to less experienced developers in existing software architecture.Contributes to periodic reviews and ensures adherence to architectural standards.Collaborates with stakeholders and networks externally to ensure work aligns with software architecture.Implements complex performance optimization and scalability strategies in software design.Occasionally conducts technology research and evaluation for potential architectural changes that may have an impact on results for the team. Issue/Defect Collaboration - Software Products Support: Collaborates with stakeholders to understand customer issues and align solutions.May provide advanced technical guidance and support to customers regarding customer-reported issues.Advocates for customers' interests and suggests product enhancements based on feedback.Provides input to ensure customer satisfaction through timely resolution of issues and effective communication.Identifies and implements customer issue and/or defect handling and training processes.Investigates and troubleshoots complex and broad-reaching/scoped maintenance issues to ensure customer agreement on short- and long-term solutions (e.g., future enhancements). Practices and Standards Compliance - Security and Compliance: Collaborates with the team and externally to follow development practices and coding standards, providing coaching to less experienced team members.Participates in peer review processes, provides technical leadership, and ensures code quality and adherence to broad acceptance criteria during development, independently.Demonstrates and shares advanced knowledge of industry best practices and applies them to software development processes.Implements complex secure coding practices to prevent security vulnerabilities. Development Operations - System Maintenance: Performs periodic maintenance and testing operations for systems that require upgrading or patching (e.g., for critical vulnerabilities), sharing results with manager upon completion.Drives improvements, ensures automation, testing, and debugging of systems to ensure service/product availability, health, support, and reliability. Core Responsibilities Planning & Execution: Manages and coordinates moderately complex tasks, monitoring timelines and deliverables to ensure timely completion and adherence to requirements for a moderately sized project or initiative. Efficiently delegates, monitors, and prioritizes work across multiple projects, providing technical oversight and adjusting plans to address shifts in resources or timelines. Collaboration & Partnership: Collaborates across the organization to align on expectations and achieve shared objectives. Leverages understanding of business leaders, stakeholders, and/or customers to ensure proposed solutions meet their needs. Supports inclusivity by actively seeking and listening to diverse perspectives, ensuring others feel heard and respected. Problem Solving: Identifies and addresses moderately complex issues by analyzing a wide range of data and/or information to identify solutions in accordance with standard practices. Proactively escalates unresolved or critical issues with a thorough assessment and suggests potential solutions. Reviews, contributes to, and documents problem solving strategies. Continuous Learning: Pursues learning opportunities to expand knowledge and skills and/or tools in new areas and stays abreast of the latest industry trends and best practices. Proactively seeks and leverages ongoing feedback and training to improve skills. Coaches and mentors junior team members, fostering continuous learning and knowledge sharing within and across teams. Continuous Improvement: Develops ideas, recommends updates, and/or collaborates on the implementation of process improvements to increase the efficiency and effectiveness of processes, protocols, and workflows across teams, and evaluates the impact on key stakeholders. Solicits feedback from others on ideas for alternative approaches and methods for continued improvement. Performance and Development: Contributes to the talent development pipeline by participating in candidate interviews, assessing candidates, and providing hiring recommendations." That's a huge block. We need to turn each sentence into list items? The instruction: Use
    • for any list of duties/requirements/benefits. So we should treat each distinct duty as a list item. However the text is dense with many sentences separated by periods. We could split by periods and treat each as a list item, but need to avoid creating items that are just filler like "Lead engineering and operational management for highly available, large-scale Oracle database fleets." That's substantive. We must preserve all substantive information; not invent or summarize away detail. So we need to include each duty exactly as written, maybe as separate list items. But the block also includes headings like "Software Development and Coding - Design, Testing, and Optimization:" which are subheadings within responsibilities. Should we treat those as headings? The instruction only allows

      for section headings like About the role, Responsibilities, etc. It didn't forbid using headings inside? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to keep to spec, we likely should not add extra headings; we can just treat them as part of the prose or list items. Simplify: We'll create a

      Responsibilities

      then a
      with each duty as
      • . We'll need to parse the responsibilities text into items. Given the large volume, we need to be careful not to miss any. Let's extract responsibilities sentences from the two blocks. First block (initial responsibilities): 1. Lead engineering and operational management for highly available, large-scale Oracle database fleets. 2. Drive Oracle 19c performance analysis, complex tuning, diagnostics, and reliability improvements. 3. Design and implement database architecture, access methods, allocation strategies, validation controls, protection, and security standards. 4. Build scalable fleet-management automation and tooling using Python and/or Shell scripting. 5. Lead technical analysis for database upgrades, patches, enhancements, and architectural changes. 6. Define long-range database capacity, availability, and operational requirements with OCI service owners. 7. Lead incident response, root-cause analysis, and prevention initiatives for complex production issues. 8. Mentor engineers, review designs and code, and establish operational best practices and runbooks. 9. Collaborate with Compute, Storage, Networking, Governance, and other OCI teams to deliver resilient cloud services. Second block (Responsibilities Key Responsibilities) includes many sub-sections. Let's extract each sentence after each colon or period. I'll rewrite the second block as a series of statements: Platform Software Development: - Lead cross-team evolution of middleware patterns