Principal Engineer, Core Infrastructure

Principal Member Of Technical Staff

Within OCI, the Technical Strategy & Oversight organization builds foundational systems for OCI's most demanding services. One of its boldest initiatives is Autonomous OCI: a greenfield effort to build a cloud platform that can operate and scale with far less manual work.

Today, every new region and service feature adds operational cost and complexity. Autonomous OCI is designed to change that by making services fast, resilient, and self-healing by default—helping OCI scale to thousands of regions without growing operations teams at the same rate.

As a Principal Member of Technical Staff, you will help shape Lightweight Infrastructure (LWI), the next-generation runtime and platform layer for compute, storage, networking, identity, observability, and governance.

Qualifications

• BS/MS in Computer Science, or equivalent practical experience.
• 6–10+ years of software engineering experience building highly available, scalable distributed systems or cloud infrastructure.
• Strong programming skills in Java, Go, Rust, C/C++, or a similar systems or backend language.
• Deep experience in one or more core infrastructure areas: distributed systems, cloud control planes, management planes, scheduling, virtualization, storage, networking, security, reliability, or platform automation.
• Ability to independently lead the design and delivery of complex services that must be correct, resilient, observable, and easy to operate.
• Strong understanding of failure handling, concurrency, asynchronous workflows, safe retries, and lifecycle management in distributed systems.
• Strong debugging and problem-solving skills, including the ability to drive resolution for complex production and performance issues.
• Experience collaborating across teams and turning broad platform goals into clear designs and executable plans.
• Ability to raise the technical bar through mentoring, design reviews, code reviews, and hands-on technical leadership.

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.

Key Responsibilities

• System Design & Architecture
  - System Scalability:
• 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.
• Optimize code and/or systems for large-scale data processing and high-throughput requirements to support hyper-scale systems.
• Define scalability requirements for owned components and ensure design and implementation requirements are met.
• Design systems to scale with elasticity (e.g., effectively scaling both up and down).
• Leverage data plane platforms to effectively handle large-scale data retrieval, storage, and processing.
• Design performance and load testing.
• System Design & Architecture
  - System Reliability Design:
• Build and design fault-tolerant components and systems capable of withstanding in-service updates by implementing redundancy, replication, and automatic failover mechanisms.
• Design systems to effectively handle service disruptions (e.g., network partitions) by prioritizing consistency, availability, or partition tolerance.
• Imp…