Principal Software Engineer, Platform

We need to produce HTML fragment with sections: h3 headings for sections present: About the role? The description includes "Job Description Responsibilites:" then responsibilities, then qualifications, then later "Key Responsibilities" etc. There's also "Qualifications Disclaimer", "Range and benefit information", "About Us". We need to include only sections with real content. We must not repeat job title. No Job ID. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We have responsibilities: many bullet-like sentences. We'll put them in

• . Qualifications: list of qualifications. Benefits: list of benefits. Pay: range given. Schedule? Not mentioned. So we omit Schedule. Also "About the role" maybe we can include a short paragraph summarizing role? The posting includes "Job Description Responsibilites:" then responsibilities. Could treat that as About the role? But we have a Responsibilities section already. The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have responsibilities content (multiple paragraphs). We'll put under

  Responsibilities

  . We have qualifications content: under

  Qualifications

  . We have benefits content: under

  Benefits

  . We have pay range: under

  Pay

  . We have maybe "About the role" could be a brief intro: The first sentence "Job Description Responsibilites: Lead engineering and operational management for highly available, large-scale Oracle database fleets." That's more like responsibilities. Could treat as About the role: a short paragraph describing role. But we already have Responsibilities. Might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So we could combine About the role and Responsibilities? But they said use headings for those sections. Could include About the role with a brief summary, then Responsibilities with detailed list. That's okay. We also have "Skills" maybe not explicit; we could omit. We have "Requirements" maybe same as Qualifications; we can use Qualifications. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, qualifications, benefits, pay. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Qualifications Disclaimer:" maybe that's boilerplate? It's about immunization etc. Might be considered boilerplate; but it's a qualification disclaimer about US-based roles. Might be considered relevant? It's not about qualifications per se; it's a legal requirement. Probably we should drop it as boilerplate. Also "The role will generally accept applications..." is application instruction; drop. Also "As part of Oracle's onboarding process..." is legal; drop. Also "About Us" section maybe we can keep as About the role? Actually About Us is company description; could be considered boilerplate but it's substantive about company. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not explicitly listed; but could be considered boilerplate? It's generic marketing. Might be okay to keep? The instruction says preserve ALL substantive information; About Us is substantive about company. However the sections we can output are limited to those headings. We could put About Us under

  About the role

  maybe? But About the role is about the role, not company. Could we add a section "About the company"? Not in allowed headings. So maybe we omit About Us to stay within allowed headings. The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those? It gives examples. Likely we should stick to those headings. So we will not include About Us. Thus we will output:

  About the role

  Lead engineering and operational management for highly available, large-scale Oracle database fleets.

  But that seems too minimal; we already have responsibilities. Maybe we combine About the role with a brief summary: "Lead engineering and operational management for highly available, large-scale Oracle database fleets." That's from first sentence. Then responsibilities list. Now responsibilities: many bullet points. We'll extract each sentence that describes a responsibility. From the text: "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 under "Key Responsibilities" there are many more items grouped under categories: Platform Software Development, Software Development and Coding, Software Architecture, Issue/Defect Collaboration, Practices and Standards Compliance, Development Operations, Core Responsibilities (Planning & Execution, Collaboration & Partnership, Problem Solving, Continuous Learning, Continuous Improvement, Performance and Development). We need to include all those as responsibilities as well. They are substantive. So we need to list them all. We must not duplicate lines. Some sentences may repeat earlier responsibilities; we need to deduplicate. Let's extract all distinct responsibility statements. I'll go through the text after "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. Now we need to combine with earlier responsibilities list (the first set). Ensure no duplicates. Let's list all unique items. I'll create a set mentally. First set: 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. Now from Platform Software Development: 10. Lead