Principal Software Engineer, Core Infrastructure

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections where posting has real specific content. We have content: job description (maybe "About the role"? Actually the description is the first paragraph(s) before "Responsibilities". That could be "About the role". We'll put that in

under h3 About the role. Responsibilities: we have bullet list after "Responsibilities". We'll put

• each line. Skills: there is "Required/Preferred Skills" list. We'll put under h3 Skills (or maybe Requirements?). The instruction says use headings like Skills, Requirements, Qualifications. We have "Required/Preferred Skills" and also "Required Soft Skills". Could combine under Skills. Also there is "Qualifications" section with disclaimer and pay range and benefits. We'll put Qualifications heading for qualifications (maybe includes disclaimer, pay range). Benefits heading for benefits details. Pay heading for pay range. Schedule heading? Not present. So we omit Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, legal, etc. Also remove "About Us" maybe? It's not a required heading but could be considered "About the role"? Actually "About Us" is company description; we could include under About the role? The instruction: "About the role" heading for role description. The "About Us" is company overview; maybe we can include under About the role as extra paragraph? But we should preserve all substantive information. The "About Us" paragraph is substantive about company; we could include it under About the role as additional paragraph. Or we could create a separate heading "About the company"? Not in allowed headings list. So we incorporate into About the role. We must not include sections with filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. First paragraph(s) before "Responsibilities": "Leads development and begins architecting components of scalable, elastic distributed systems. Defines and enforces scalability requirements for owned components; optimizes code and data paths for high‑throughput, hyper‑scale workloads; and leverages data plane platforms for large‑scale retrieval, storage, and processing. Designs fault‑tolerant, in‑service‑upgradable systems using redundancy, replication, failover, and policies for partitions, applying load‑shedding, throttling, and rate‑limiting to handle network unreliability while meeting SLOs. Establishes KPIs and telemetry; builds proactive dashboards and alerts; and designs complex validation (fault injection, brownouts), replication, and synchronization for correctness and durability. Proactively diagnoses and resolves production issues, mentors peers, and ensures operational readiness. Implements robust security controls, executes remediation, maintains compliance documentation, and develops IaC and automation that enable safe patching, updates, and rollbacks within change‑management plans." That's the role description. Now Responsibilities list: - Utilize standard software development practices and procedures towards scoping, architecture, specification, development, source control, code review, documentation and testing of features. - Work closely with fellow team members, geographically distributed teammates, and cross-functional teams toward the execution of agreed project milestones and delivery dates. - Communicate status, and risks, and offer mitigation strategies to ensure on-time delivery of all committed items. - Support operational excellence in a Cloud DevOps environment. Now Required/Preferred Skills list (the block after "Required/Preferred Skills"): - Proficiency with C/C++. - Scripting proficiency in a language such as Python, Perl or Bash. - Hands-on experience developing multi-threaded embedded Linux application/infrastructure. - Experience in one or more Network or Storage stacks and protocols such as P4, DOCA, TCP/IP, NVMe, PCIe, DPDK. - Firmware development skills and experience with embedded systems. - Knowledge of at least one of Intel/AMD/ARM computer architectures. - Hardware and/or System bring-up experience. - Experience with Linux Kernel/Driver programming. - Proficiency with Linux. - Proficiency Virtualization technologies (SRIOV, VirtIO, VDPA etc). - Experience in CI/CD environments. - Comfortable working with remote lab equipment. Then "Required Soft Skills:" list: - Excellent problem solving, analytical skills and technical troubleshooting skills. - Ability to learn new skills quickly as needed. - Ability to work with minimal supervision. - Ability to prioritize, self-manage, self-study, and organize effectively. - Ability to collaborate and work as a team with peers and project members. - Outstanding communication and presentation abilities. - Strong drive for success. - Engaging actively in the technical decision-making process. - Participate in technical discussions and providing feedback depending on the needs of the team/department - Ensure compliance with development methodology and technical process. We could combine both under Skills heading, maybe separate subheadings? But we only allowed h3 headings; we could just list all items under Skills. Now Qualifications section: includes disclaimer about US based roles, immunization, drug testing. Then "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $114,600 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral. Oracle maintains broad salary ranges ..." Then benefits list. We need to separate Pay and Benefits sections if they have specific content. Pay: we have hiring range. Benefits: we have list of benefits. Qualifications: maybe we keep the disclaimer and maybe the statement about placement etc. But we could put disclaimer under Qualifications, and Pay and Benefits separate. Let's extract Qualifications substantive content: The disclaimer paragraph: "Disclaimer: Certain U.S. based or U.S. customer or client-facing roles may be required to comply with applicable requirements, such as immunization/occupational health mandates, and/or drug testing requirements." That's qualification-related. Also maybe the statement: "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $114,600 - $234,600 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." That's more about pay and benefits; we could split. Thus Qualifications heading could contain the disclaimer only (or also include the placement statement). But we need to avoid filler like "not specified". Not present. We'll create:

  About the role

  ... (role description) ...

  About Us: Only Oracle brings together ... (the About Us paragraph) ...

  But we might combine About Us into same paragraph. Better: After role description, add a paragraph containing the About Us text. Now Responsibilities. Now Skills. Now Qualifications (disclaimer). Now Pay. Now Benefits. We must not include Schedule. Now ensure we don't include any boilerplate like EEO, legal, accommodation request, equal opportunity, etc. Remove those. Now produce HTML. Let's craft. Role description paragraph: combine sentences as given. 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." But we need to remove EEO/equal-opportunity boilerplate. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So we must strip the EEO statements. That includes the sentences about Equal Employment Opportunity Employer and consideration without regard... and arrest and conviction records. So we should remove those sentences. Also the accommodation request line maybe not EEO but it's about accommodation; might be considered legal? It's about accommodation request; could be considered legal but not explicitly EEO. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The accommodation request line is not EEO but it's about accommodation for disability; might be considered part of EEO? Safer to remove it as it's about accommodation request. However it's substantive about accessibility assistance; but it's likely considered boilerplate. I'd remove it. Thus About Us paragraph after removing EEO lines: Keep the first sentences about Oracle's mission, AI, etc., the part about True innovation..., workforce, benefits, volunteer programs, commitment to including people with disabilities (that's not EEO but about inclusion). Might keep that. The accommodation request line and EEO statements remove. Let's craft 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." Now we have that. Now Responsibilities list as above. Now Skills list: combine required/preferred skills and soft skills. We'll list each as
• . Now Qualifications: disclaimer paragraph. Now Pay: hiring range statement. Now Benefits: list of benefits. Benefits list from posting: - 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. -