SRE-( Python Automation,Linux)

Description

About the Company / Team The OCI Compute team operates cloud services and components with a focus on reliability, scalability, performance and operational efficiency. Site Reliability Engineers work with development and infrastructure teams to improve production safety, strengthen service ownership and respond to customer-impacting incidents.

Key Responsibilities

• Improve the reliability, scalability, performance, and operational efficiency of assigned OCI Compute services and components.
• Investigate and resolve complex production incidents; contribute to mitigation, recovery, RCA, and follow-up actions. Contribute to incident-management practices, operational readiness, and service ownership improvements.
• Own and improve service-level KPIs, SLOs, dashboards, alerting, deployment validation, and operational procedures for assigned systems.
• Build automation and tooling to reduce operational toil and improve production safety.
• Partner with development and infrastructure teams on service architecture, deployment, configuration, and reliability improvements. Share technical knowledge and support team members through documentation, reviews, and collaboration.
• Use observability, telemetry, event correlation, and AIOps capabilities to improve detection, diagnosis, and incident response. Troubleshoot distributed-system issues by analyzing service topology, dependencies, configuration, and failure modes.
• Support upgrades, migrations, patching, capacity planning, performance tuning, security vulnerability management and production rollouts.
• Participate in a 12x7 on-call rotation and support response to customer-impacting incidents.

Responsibilities

Qualifications & Skills

Mandatory

• 4–8 years of experience in SRE, Production Engineering, Cloud Operations, Systems Engineering, or a similar role.
• Experience operating and improving highly available production systems.
• Strong programming or scripting skills in Python, Java, Go, or similar languages.
• Hands-on experience with Linux, cloud infrastructure, networking, compute, and storage.
• Experience with production monitoring, alerting, dashboards, logs, metrics, and tracing.
• Experience owning or improving service SLIs, SLOs, KPIs, and operational procedures.
• Strong incident troubleshooting, RCA, debugging, and problem-solving skills.
• Experience with deployment pipelines, release validation, automation, and change-management practices.
• Understanding of distributed systems, service dependencies, capacity planning, and performance tuning.
• Ability to work independently on technical problems and collaborate effectively with engineering teams.
• Strong written and verbal communication skills.
• Participate in a 12×7 on-call rotation and respond to customer-impacting incidents.

Good-to-Have

• Experience with OCI and cloud infrastructure services.
• Experience with AIOps, anomaly detection, event correlation, predictive alerting, or automated remediation.
• Experience with Kubernetes, containers, infrastructure-as-code, and CI/CD.
• Experience with service migrations, fleet maintenance, upgrades, patching, or production rollouts.
• Experience with architecture reviews, operational-readiness reviews, and post-incident improvements.
• Experience contributing to technical initiatives, knowledge sharing, code reviews, or operational improvements within the team.
• Familiarity with security, compliance, and access-control practices in production environments.

Self-Assessment Questions

1. Do I have 4–8 years of relevant SRE, Production Engineering, Cloud Operations or Systems Engineering experience, including highly available production systems?
2. Can I independently investigate incidents, support mitigation and recovery, perform RCA and troubleshoot distributed-system dependencies and failure modes?
3. Do I have hands-on Linux, cloud infrastructure, networking, compute and storage experience and strong Python, Java, Go or similar programming/scripting skills?
4. Have I improved monitoring, alerting, logs/metrics/traces, SLOs/KPIs, deployment validation, release pipelines, automation and change management?
5. Can I communicate clearly, collaborate with engineering teams, manage independent technical work and participate in a 12×7 on-call rotation?