Senior OCI Engineer interview questions

I've been on OCI for five years, four of them in Oman. Started with on-prem Oracle databases at an Indian banking IT services firm, moved into OCI as our customers migrated, and for the past three years I've been senior OCI engineer at an Omani bank running a multi-region OCI footprint. My remit covers compute, networking, IAM, security services, and the database services that we use heavily (ATP, ADW, ExaCS). OCI Architect Professional and Operations Associate certified. I've led two major OCI migrations from on-prem.

Multi-compartment hierarchy reflecting the organisation: separate compartments for production, non-production, security, networking, audit. IAM with proper policies, no broad-grant administration. Multiple VCNs as needed for isolation (DMZ, application, database tiers). Subnet design with public/private segregation, NSGs for fine-grained access control. Logging and audit to OCI Logging plus export to SIEM. Security tooling: Cloud Guard for posture management, Vulnerability Scanning Service. Budgets and tagging enforced from day one; tagging at scale is painful retrospectively. Compliance baseline: CIS OCI Benchmark.

Production workloads run across multiple availability domains within an OCI region. Critical workloads have cross-region DR to a second OCI region within the GCC for data residency. RTO target 4 hours for tier-1 workloads, 24 hours for tier-2. Tested quarterly through actual failover (not just paperwork). For databases: Data Guard for sync replication where RPO needs to be near-zero, async for less critical. For object storage: cross-region replication enabled. DR isn't checking boxes; it's actually being able to recover when needed.

Federated identity via our Azure AD as identity provider. OCI users are exclusively service accounts; all human access is federated. Groups mapped from AD groups to OCI policies, so role provisioning happens at the AD layer. Compartment hierarchy reflects organisational boundaries with policy scope limited per compartment. Privileged access is just-in-time via dedicated workflows requiring approval. MFA enforced. Regular access reviews quarterly. Audit logs on every IAM action. The discipline is in keeping it simple as it scales; complexity in IAM creates security gaps.

Self-service where possible. Application teams should be able to provision their own resources within guardrails (compartment, tags, NSG rules pre-approved). I focus my time on the platform itself and on consulting with teams on architecture decisions, not on operating their workloads. I respond fast to queries; the worst cloud platform teams take days to answer simple questions. Periodic office hours where teams can bring architecture questions in advance. Cloud platform teams succeed when they make application teams' work easier.

For a senior OCI engineer role in Oman banking I'd target OMR 1,800 to 2,300 total package depending on the workload complexity and on-call expectations. OCI engineers with multi-cloud or hybrid experience command a premium. I'm on 60 days' notice. Beyond pay I'd value continued certification investment; cloud skills decay fast without continuous learning.