Job Title : Member of Technical StaffLocation : India - Pune and BangaloreJob Type : Regular Employee HireOrganization : GBU Cloud Development Services, Cloud Reliability Services CRS DescriptionCloud Reliability Services (CRS) is a strategic component that will transform Oracle’s Global Business Unit’s (GBU) cloud operations.
As cloud service operations evolve from a predominately re-active model (i.e., responding to emergencies with high levels of human involvement) to a pro-active model (i.
e., preventing emergencies and outages with intelligent tools, services and automation), the mission of the CRS team is to ensure that all GBUs can efficiently operate ultra-scalable and highly-reliable SaaS / Foundation services, across multiple operating models as they iterate to become Cloud Native.
We are looking to assemble some of the smartest people in the industry to build and grow this revolutionary and disruptive team.
Team descriptionThe Oracle Global Business Unit (GBU) Cloud Reliability Services (CRS) team provides Resource Administration, Operations Support, Centralized Logging and Monitoring to GBU Applications Teams to support high margin, highly elastic, and highly available Software as a Service (SaaS) applications using the Oracle Cloud Infrastructure (OCI).
This CRS team is responsible for the development and operation of highly available and scalable services necessary to satisfy the needs of our Oracle Global Business Unit (GBU) partners Roles & ResponsibilitiesThe candidate will work with highly skilled, highly motivated engineers using Agile methodologies based on Scrum or Kanban, and incorporating enterprise agile practices from Scaled Agile Framework (SAFe).
The team embraces a DevOps environment the Developers are the Operators. The work environment is to treat everything as code (code, configuration, infrastructure, pipelines, everything) to achieve the highest quality product in the most efficient amount of time.
You will work alongside a software development team within the greater Oracle Cloud Reliability Engineering team where you will develop new features as well as expand and support existing features.
One week you may be writing automated tests for an existing feature. The next week you may be developing a new feature (design, code, test, and deploy) for a customer in our environment.
The next week you may be providing support to a customer on your new feature. You will learn new technologies based on what we already deploy and use.
You will also learn about and research new technologies that you bring to the team to better our offerings. You will play a key role in building more intelligence, into CRS services that we deliver, so that SaaS services function more and more autonomously over time.
Team Specific Roles and Responsibilities
DevOps engineers will rotate with other team members in a designated, on-call status following in-country requirements. CRS’s primary support model is follow the sun, utilizing geographically diverse team members during normal working hours to provide support.
CRS will strive to have subject matter experts distributed globally. With geographic diversity, countries and regions have a broader array of holidays requiring a flexible support schedule across multiple geographies.
Additionally, coverage is required through the weekend. To provide the required support to Oracle customers, CRS will use additional compensation to cover extended business hours and / or on-call pay based on in-country laws and Oracle policy.
In general, there will be a Primary and Secondary engineer designated in advance to provide coverage for select services.
If numerous services are supported in a specific geographic region, there may be more than one set of Primary / Secondary engineers selected.
Software engineers and database administrators will engage in activities to restore services that are down or degraded. This may be as simple as running an existing script to restart a service or executing a standard operating procedure, or may require code changes with review steps, integration, testing, and software deployments to restore a service to normal operation.
In addition, engagement with other Oracle development and support teams may be needed.