Jobs · Engineering

Principal Core Infrastructure Software Engineer

Oracle · United States · Yesterday
RemoteRemoteEngineering$115k–$235k/yrFull-time
We need to output HTML fragment with sections: h3 for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: Job Description (intro) which could be "About the role". Responsibilities section present. Required Qualifications and Preferred Qualifications. Also "Qualifications Disclaimer" maybe part of qualifications. There's also "Range and benefit information" includes Pay and Benefits. There's also "Career Level - IC4" maybe not needed. There's no explicit Schedule. So we should not create Schedule section. Pay: we have hiring range $114,600 - $234,600 per year, plus bonus, equity, compensation deferral. That's pay info. Benefits: list of benefits. So we include Pay and Benefits sections. We also need Skills? Could be derived from required qualifications: programming languages, Kubernetes, etc. But we should not invent sections unless posting has real specific content for it. The posting does not have a separate "Skills" heading, but we could include a Skills section if we extract from qualifications? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid creating a Skills section if we can pull specific content that matches skills. However the posting does not have a explicit Skills heading, but we could still create a Skills section if we list skills from the qualifications. The instruction says "Prefer a few substantive sections over many thin ones." Might be better to combine qualifications and skills into one "Requirements" or "Qualifications". Since we already have Required Qualifications and Preferred Qualifications, we could put them under "Qualifications". The instruction lists possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to use. We have About the role (intro). Responsibilities. Qualifications (required + preferred). Pay. Benefits. We might not need separate Requirements or Skills. So output sections: About the role, Responsibilities, Qualifications, Pay, Benefits. We need to use

for each section heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must preserve ALL substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Qualifications Disclaimer" maybe it's legal? It's about immunization/occupational health mandates, drug testing. That's likely boilerplate legal; we should remove it. Also remove "Career Level - IC4". Remove "About Us" maybe? That's boilerplate? It's about Oracle mission; could be considered boilerplate but maybe it's substantive? The instruction says 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 considered boilerplate; safer to remove. Also remove "Oracle is an Equal Employment Opportunity Employer..." etc. Also remove "The role will generally accept applications for at least three calendar days..." (application instructions). Also remove "Range and benefit information provided in this posting are specific to the stated locations only US:" maybe keep pay info but remove the sentence about specific to locations? We can keep the pay range and benefits details. The sentence about "Oracle maintains broad salary ranges..." is generic; maybe keep? It's not boilerplate but could be considered filler. The instruction: do not emit heading followed by filler/placeholder text. But that sentence is not a heading; it's prose. We can keep it if it's substantive? It's somewhat generic but still info about salary ranges. Might keep. We need to preserve all substantive information: responsibilities list, qualifications list, benefits list, pay range. Let's extract: About the role: The paragraph after "Job Description": "The Principal Core Infrastructure Software Engineer is a Senior Staff-level, hands-on technical leadership role responsible for defining, building, and operating next-generation AI systems on Oracle Cloud Infrastructure (OCI). This person will set architecture and engineering direction for production-grade cloud distributed systems, agentic AI platforms, autonomous workflows, scalable inference infrastructure, and enterprise AI applications used in large-scale, business-critical environments. This role requires a proven engineer who can translate ambiguous product and platform goals into durable technical strategy, lead multi-team execution without direct authority, and remain deeply hands-on in design, code, reviews, operations, and incident follow-up. The ideal candidate combines deep distributed systems experience with practical AI-native engineering, including orchestration of LLMs, tools, APIs, memory, retrieval, evaluation, guardrails, and cloud services. The expectation is to ship, scale, and operate reliable, secure, observable, and cost-aware AI platform systems while raising the technical bar for engineers across the organization." That's the About the role. Responsibilities: list under "Key Responsibilities include:" then bullet points. We need to capture each bullet as

  • . The bullet points start with "Lead the development and implementation, and begin to architect, components of scalable distributed systems..." etc. We'll list each. Qualifications: combine Required Qualifications and Preferred Qualifications. Also maybe include "Qualifications Disclaimer" but we remove. So we need to list required qualifications as bullet points? The required qualifications are sentences separated by periods. Could turn each into
  • . Similarly preferred qualifications. We need to avoid duplication. Let's extract required qualifications: - Bachelor's, Master's, or Ph.D. in Computer Science, AI/ML, Engineering, or a related field, or equivalent practical experience. - 6-10+ years of professional software engineering experience, including significant ownership of production systems; or equivalent experience demonstrating Senior Staff / Principal-level impact. - Deep experience designing, building, and operating high-scale distributed systems, cloud services, infrastructure platforms, or AI/ML platform services. - Strong programming skills in Java or Golang or Python and ability to contribute high-quality production code, reviews, tests, and debugging in complex distributed environments. - Strong expertise with Kubernetes, Docker, cloud-native infrastructure, service-to-service communication, scalability, fault tolerance, observability, and performance analysis. - Experience defining SLIs/SLOs, production readiness criteria, incident response practices, monitoring, tracing, experiments, and reliability programs for AI or distributed systems. - Software Estimation: Demonstrated ability to provide accurate software effort and complexity estimates for project planning and scheduling. - Agile Methodologies: Demonstrated ability to use agile methodologies to drive continuous improvement and product delivery - Excellent written and verbal communication, with demonstrated ability to lead technical direction, resolve ambiguity, and influence senior stakeholders. Preferred qualifications: - Experience with large scale cloud platforms (e.g., AWS, Azure, Google, Oracle Cloud). - Practical experience with orchestration frameworks such as LangGraph, LangChain, CrewAI, AutoGen, LlamaIndex, or similar ecosystems. - Deep understanding of LLM application patterns, including prompt design, structured outputs, function/tool calling, context management, RAG, memory, tool safety, and evaluation. - Experience using AI-assisted software development tools such as Codex, Claude Code, Cursor, Copilot, or similar systems in large-scale engineering environments. - Experience in enterprise, cloud infrastructure, regulated, security-sensitive, or mission-critical environments. We could also include "Qualifications Disclaimer" but remove. Pay: "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." We could keep the first sentence about hiring range and bonus etc. The rest maybe generic but still substantive. We'll keep all. Benefits: list of benefits after "Oracle US offers a comprehensive benefits package which includes the following:" then bullet list. We need to output HTML fragment only. Let's craft:

    About the role

    ... (the paragraph)

    Responsibilities

    • Lead the development and implementation, and begin to architect, components of scalable distributed systems that support horizontal and vertical scaling to meet system demands, including leveraging distributed state management tools.
    • Design, architect, and deliver scalable agentic AI systems capable of reasoning, planning, tool use, workflow execution, multi-step task orchestration, and safe human-in-the-loop escalation.
    • Define scalability, performance, availability, and durability requirements for owned services and components.
    • Build fault-tolerant systems that support redundancy, replication, automated failover, and in-service upgrades.
    • Optimize services for high-throughput, low-latency, and large-scale cloud workloads.
    • Design systems that handle network unreliability, service disruptions, and partition scenarios while meeting SLOs.
    • Establish telemetry, KPIs, dashboards, and alerts to monitor service health, performance, reliability, and customer impact.
    • Drive performance testing, load testing, fault injection, brownout testing, and other validation strategies to ensure correctness and resiliency.
    • Implement secure infrastructure controls for multi-tenant cloud environments, including access controls, encryption, and remediation of security gaps.
    • Develop automation, Infrastructure as Code, and deployment tooling to support safe patching, updates, rollbacks, and operational recovery.
    • Take ownership of production operations, including troubleshooting, incident response, root cause analysis, and ongoing service improvements.
    • Strengthen operational readiness by improving runbooks, monitoring, change management, deployment safety, and recovery processes.
    • Collaborate with partner teams across OCI to align architecture, dependencies, and service requirements.
    • Mentor engineers, review technical designs, guide implementation decisions, and help raise the engineering bar across the team.

    Qualifications

    • Bachelor's, Master's, or Ph.D. in Computer Science, AI/ML, Engineering, or a related field, or equivalent practical experience.
    • 6-10+ years of professional software engineering experience, including significant ownership of production systems; or equivalent experience demonstrating Senior Staff / Principal-level impact.
    • Deep experience designing, building, and operating high-scale distributed systems, cloud services, infrastructure platforms, or AI/ML platform services.
    • Strong programming skills in Java or Golang or Python and ability to contribute high-quality production code, reviews, tests, and debugging in complex distributed environments.
    • Strong expertise with Kubernetes, Docker, cloud-native infrastructure, service-to-service communication, scalability, fault tolerance, observability, and performance analysis.
    • Experience defining SLIs/SLOs, production readiness criteria, incident response practices, monitoring, tracing, experiments, and reliability programs for AI or distributed systems.
    • Software Estimation: Demonstrated ability to provide accurate software effort and complexity estimates for project planning and scheduling.
    • Agile Methodologies: Demonstrated ability to use agile methodologies to drive continuous improvement and product delivery
    • Excellent written and verbal communication, with demonstrated ability to lead technical direction, resolve ambiguity, and influence senior stakeholders.
    • Experience with large scale cloud platforms (e.g., AWS, Azure, Google, Oracle Cloud).
    • Practical experience with orchestration frameworks such as LangGraph, LangChain, CrewAI, AutoGen, LlamaIndex, or similar ecosystems.
    • Deep understanding of LLM application patterns, including prompt design, structured outputs, function/tool calling, context management, RAG, memory, tool safety, and evaluation.

Similar jobs