Hi
Our client is looking for a Senior DevOps Engineer Consultant with a Full Time project in Remote below is the detailed requirement.
Job positing Title :Senior DevOps Engineer
Location: Remote
Type: Full Time
Required Skills :Strong Oracle on Azure, Oracle , Azure, Terraform * CI/CD.
Job description:
Bachelor’s or Master’s degree in Computer Science, Information Systems, Finance, Data Engineering or a related field
1) Core Platform & Architecture (Oracle Database@Azure)
Must have
• Oracle Database@Azure concepts: Understand that Exadata infrastructure runs in Azure datacenters but is managed via OCI control plane and provisioned through the Azure portal (linking an Azure subscription to an OCI tenancy). Know service scope (RAC support, Exadata performance, Azure billing/MACC) and onboarding steps. [docs.oracle.com]
• Provisioning flow: Hands on with creating Exadata Infrastructure, VM Clusters, and Databases from the OracleDB@Azure blade; familiarity with supported models (X9M/X11M, and Exascale), quotas/limits, maintenance windows, and regions/AZs. [learn.microsoft.com], [docs.oracle.com], [docs.oracle.com]
• Service nuances vs OCI: IP address reservation differences (e.g., 13 IPs on client subnet vs 3 in OCI), delegated subnet constraints, and how Azure/OCI APIs interplay.
2) Network & Connectivity (Azure first, OCI aware)
Must have
• Azure VNet design for OracleDB@Azure: Building delegated subnets (Oracle.Database/networkAttachment), peering/hub and spoke, NSGs, route tables/NVAs (e.g., Azure Firewall), no default internet egress, and split DNS patterns. [learn.microsoft.com], [learn.microsoft.com]
• Advanced networking features for Database@Azure (regions, registration steps before creating the delegated subnet). [learn.microsoft.com]
• Hybrid connectivity for migration and app access: ExpressRoute/S2S VPN planning, bandwidth/resiliency, and routing inspection through hub NVA. [learn.microsoft.com], [learn.microsoft.com]
3) Security, Identity & Governance
Must have
• Azure RBAC/Policies/Blueprints for Oracle resources in the subscription and resource groups; secure delegated subnets (private only, NSGs, routing through NVA). [learn.microsoft.com]
• Key Vault/Secrets handling for DB credentials, wallet files, and automation pipelines; logging/monitoring via Azure Monitor and Defender for Cloud (often with Azure Arc).
4) Oracle Database & Exadata Administration
Must have
• Exadata fundamentals: Storage cells, ASM, DB nodes, resource management, IORM, patching cycles, and AWR based performance tuning; experience administering CDB/PDB and RAC in production. [docs.oracle.com]
• Backup/Recovery & HA/DR: RMAN strategies, Data Guard topologies, and cutover playbooks aligned to RPO/RTO; understanding of service managed backup networks for *************
-
- Migration Expertise (Critical)
Must have
• Physical & logical migration paths: RMAN, Data Guard, Data Pump, Oracle GoldenGate, and especially Oracle Zero Downtime Migration (ZDM) for minimal downtime cutovers from on prem Exadata → ************* [learn.microsoft.com], [docs.oracle.com]
• Reference blueprints for OD@A migrations with ZDM: network setup, route tables, hub NVA routing to on prem, and stepwise execution.
6;Automation, Scripting & IaC
Must have
• Scripting & IaC: Azure CLI/PowerShell, ARM/Bicep or Terraform/OpenTofu for consistent provisioning of VNets, delegated subnets, route tables, and OD@A resources (using the Oracle/OD@A examples). [docs.oracle.com]
• Pipelines: CI/CD (GitHub Actions/Azure DevOps) for promotion of infra changes, parameterized deployments, and post provision validation.
-
- Monitoring, Capacity & Performance
Must have
• Monitoring: Azure Monitor metrics/logs for network and VM cluster connectivity; OD@A monitoring from Oracle side; alerting on latency/throughput; change windows and patch orchestration awareness. [docs.oracle.com]
• Capacity & performance: Read/interpret AWR and workload characteristics to size OD@A shapes/VM clusters and storage; know inherited region/AZ constraints and VM cluster limits per Exadata infrastructure.
-
- Project & Risk Management (Cutover critical)
Must have
• Runbook ownership: Dry runs for migration, back out plan, checkpoint criteria, and incident handling during DNS/app switchover.
• Stakeholder alignment: App owners, network, security, DBA, and business sign off on RPO/RTO and the minimal downtime objective (e.g., ZDM with Data Guard).