Sr Software Enginner, Core Infrastructure

We need to produce HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. We need to preserve all substantive information. Let's parse the job description. The description includes: - Intro paragraph: "As a Senior Core Infrastructure Engineer, you will design and develop major new features within existing systems, playing a key role in driving engineering excellence. You'll help elevate development practices, operational efficiency, team ownership, and mentoring culture. You may also collaborate with teams across the organization. You will write secure, maintainable, and robust code along with comprehensive tests. You'll lead the design and implementation of features and subsystems, ensuring their operational readiness and excellence. You will actively participate in planning and risk mitigation for systems and services across the organization. You'll work independently on most projects, occasionally requiring guidance in areas that demand deep industry experience—such as designing secure, high-performance, scalable systems or managing complex cross-team dependencies. You'll frequently identify and resolve issues without needing assistance, lead root cause analysis efforts, and recommend effective solutions. You'll also build new metrics and dashboards to enhance visibility and situational awareness. Additionally, you'll identify and implement improvements that reduce operational overhead, increase availability, improve compliance with organizational standards, and minimize technical debt." That's the "About the role" section. Then "Responsibilities" heading with subheadings: Key Responsibilities, then bullet lists under System Design & Architecture categories, Operational Troubleshooting & Incident Management, Compliance & Security, Automation & Change Management, Core Responsibilities (Planning & Execution, Collaboration & Partnership, Problem Solving, Continuous Learning, Continuous Improvement), Other Responsibilities (list of bullet-like sentences). We need to output

• for any list of duties/requirements/benefits. So we need to convert each bullet point into
• . The subheadings like "System Design & Architecture - System Scalability:" could be considered headings but we only allowed

  for sections; we could keep them as plain text or maybe as but not required. 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. So we can have

    Responsibilities

    then under that we can have paragraphs or lists. The subheadings inside responsibilities could be just plain text or maybe . Not required to be headings. We need to preserve all substantive info. So we need to include all bullet points. Then "Qualifications" section: includes a disclaimer about US based roles, immunization, etc. Then "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $79,200 - $209,500 per year. May be eligible for bonus and equity. Oracle maintains broad salary ranges..." Then benefits list. Also "Career Level - IC3". Also "About Us" section (but that's boilerplate? It's about Oracle mission; maybe we can include as "About the company"? Not in allowed sections. The allowed sections are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Us" is not listed; we should drop it as boilerplate? It's not exactly boilerplate but it's company description. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" might be considered boilerplate but it's not legal/EEO. However the allowed sections do not include a generic "About Us". The instruction says "Prefer a few substantive sections over many thin ones." So we could incorporate the "About Us" into "About the role"? Probably not. Better to drop it as it's not required. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we can drop the About Us. We also have "Career Level - IC3" which could be considered metadata; we could fold into a short

    under Qualifications or maybe under About the role. But we can include as a

    under Qualifications. We need to include Pay section if posting actually states them. Yes, there is hiring range: $79,200 - $209,500 per year. Also mention bonus and equity. So we should have a Pay section with that info. Benefits section: they list many benefits. So include Benefits. Schedule: Not mentioned. So we should not include Schedule. Skills: Not explicitly listed; maybe we could infer from responsibilities but not explicit. The instruction: include a section ONLY when the posting has real, specific content for it. So we should not create Skills unless there is explicit skills list. There's none. So omit Skills. Requirements: The Qualifications section includes qualifications and maybe requirements. There's a "Qualifications" heading in the posting. So we should have a Requirements section? The allowed sections include Requirements and Qualifications separately. The posting has "Qualifications" heading with disclaimer, salary range, benefits, career level. There's no separate "Requirements" heading. However we could treat the qualifications as Requirements? But we have both Requirements and Qualifications as possible sections. The posting only has Qualifications. So we should put that content under Qualifications section. Requirements could be omitted if no explicit requirements. However there may be implicit requirements like experience etc. But not explicit. So we omit Requirements. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to output HTML fragment only. Let's craft. First, About the role: combine the introductory paragraph(s) into

    . Might be multiple sentences; we can keep as one

    . Then Responsibilities:

    Responsibilities

    . Then we need to list all duties as
    • . We have many bullet points grouped under headings. We'll flatten them into list items. We need to ensure we capture all bullet points. Let's extract bullet points from the responsibilities section. Original text after "Responsibilities": "Key Responsibilities System Design & Architecture - System Scalability: –Implements and contributes to the development for components of distributed systems that support horizontal and vertical scaling including leveraging distributed state management tools. –Optimizes code and/or systems for large-scale data processing in large-scale systems. –Implements scalability requirements for assigned components and reviews implementation of team members. –Leverages components of data plane platforms to handle large-scale data retrieval, storage, and processing. –Implements performance and load testing. System Design & Architecture - System Reliability Design: –Collaborates with team to build fault-tolerant components capable of withstanding in-service updates by implementing redundancy, replication, and automatic failover mechanisms. –Applies recovery oriented computing principles to design components that effectively handle service disruptions. –Implements retry mechanisms, circuit breakers, and timeouts to help handle network unreliability. System Design & Architecture - System Reliability Performance: –Implements tests and alarm configurations to proactively detect and address issues/failures. –Supports efforts to recover from failures by drafting and executing runbooks and operational procedures. –Builds and customizes dashboards, telemetry systems, and alerting mechanisms to monitor component health. System Design & Architecture - Correctness / Availability: –Designs and implements functional requirements and testing for assigned features within an existing system. –Implements tests scenarios (e.g., fault-injection, brown-out) to evaluate system correctness. –Implements standard data replication and synchronization techniques to maintain data integrity and availability. Operational Troubleshooting & Incident Management: –Diagnoses, debugs, and resolves issues in system components to support ongoing operation. –Implements basic strategies to prevent interruptions, ensuring no maintenance windows are required for customers and users when resolving issues. –Designs and implements automation scripts and tooling used to troubleshoot operational issues. –Participates in operational support rotations, assisting in incident responses and root cause investigations. Compliance & Security: –Applies advanced security measures to protect data and applications in multi-tenant environments, including encryption and access controls. –Implements remediation plans to continuously improve security. –Collaborates with the team to ensure cloud infrastructure complies with relevant industry standards and regulations and that documentation is up-to-date Automation & Change Management: –Maintains automation scripts and tools (e.g., Infrastructure as Code (IaC)) for managing cloud infrastructure. –Adheres to change management plans for patching, updating, and rolling back applications. Core Responsibilities Planning & Execution: –Track timelines with minimal supervision, ensuring work is completed in a timely manner and is in alignment with project requirements. –Prioritize and adjust work as resources or timelines change, with some guidance Collaboration & Partnership: –Collaborates across teams to align on expectations and achieve shared objectives. Builds and maintains a comprehensive understanding of business, stakeholder, and/or customer needs to build and support effective partnerships. Actively listens to diverse perspectives and asks questions to ensure understanding of others. Problem Solving: –Independently identifies and addresses standard and non-standard issues in accordance with standard practices, escalating more complex issues as appropriate. Analyzes data and/or information from multiple sources to troubleshoot standard and non-standard errors. Contributes to knowledge sharing and best practices Continuous Learning: –Embraces continuous learning by actively seeking to build knowledge and new skills and/or tools, and staying current with industry trends and best practices. Seeks out and leverages feedback and training to improve skills. Contributes to a culture of continuous learning and knowledge sharing with team members.. Continuous Improvement: –Develops ideas and recommends updates to increase the efficiency and effectiveness of processes, protocols, and workflows within a team. Seeks input from team members on alternative approaches and methods for improving work. Other Responsibilities: Hands-on and seasoned engineer who can design and drive end to end engineering efforts (incld design, development, test infrastructure, operational excellence) Strong Operational posture Resolve complex technical issues and make design decisions to meet the critical requirements of this scalable, highly available, secure multi-tenant enablement of services in cloud. Mentor and guide junior members in the team on the technological front. Work closely with all the stakeholders to deliver product features on time and with high quality. Proactively identify and resolve risks and issues that may dent the team's ability to execute. Work with various external teams' integration with the product and help guide the integration. Understand various Cloud technologies in Oracle to help evolve the cloud provisioning and enablement process on a continuous basis." We need to split each bullet that starts with "–" (en dash) or maybe a hyphen. Also there are sentences not preceded by dash like "Hands-on and seasoned engineer..." etc. Those are also responsibilities. We'll treat each line that starts with "–" as a list item. Also the sentences after "Other Responsibilities:" that are not preceded by dash but are separate sentences; we can split them into separate list items as well. Let's list them: System Design & Architecture - System Scalability: - Implements and contributes to the development for components of distributed systems that support horizontal and vertical scaling including leveraging distributed state management tools. - Optimizes code and/or systems for large-scale data processing in large-scale systems. - Implements scalability requirements for assigned components and reviews implementation of team members. - Leverages components of data plane platforms to handle large-scale data retrieval, storage, and processing. - Implements performance and load testing. System Design & Architecture - System Reliability Design: - Collaborates with team to build fault-tolerant components capable of withstanding in-service updates by implementing redundancy, replication, and automatic failover mechanisms. - Applies recovery oriented computing principles to design components that effectively handle service disruptions. - Implements retry mechanisms