Platform Engineer - Oracle

Must have Oracle DBA experience in Financial Environments( patching, backup/recovery, tuning, PL/SQL)

Must be a strong communicator they will be point of contact for production issues

Platform Engineer - Oracle

Remote (looking for offshore resources)

Shift: 3 PM to 12 AM

Rate: 1.8 Lakh/Month

Mode: Contract - 6 Month and extendable

• Relius platform ownership
• Own Dev / UAT / Prod Relius environments: upgrades and service packs (e.g., Relius SP releases), environment
• refreshes, configuration, and capacity (disk, tablespaces, audit log management).
• Manage FIS support cases end to end and coordinate with our managed database services vendor and internal
• infrastructure teams.
• Keep the Relius application/web tier healthy day to day (service restarts, config changes, deploy-related checks),
• with our infrastructure team owning the underlying servers, networking, and certificates.
• Oracle database engineering (the deep skill)
• OS and Oracle DB patching in OCI across environments; backup/restore and refresh operations between
• environments.
• Performance triage and tuning: long-running queries, problem stored procedures, batch/report run times.
• PL/SQL development for data fixes, corrective scripts, and integrations.
• Deployment gatekeeping & release engineering
• Review SQL/PL/SQL scripts written by application developers before they touch UAT or production.
• Execute scheduled releases and hotfix deployments; confirm and document deploys in Jira.
• Improve the path to production over time (repeatability, safety, auditability).
• Production support & data triage
• Serve as the escalation point for Relius production issues: transaction posting problems, statement and report
• generation, plan/participant data anomalies, inbound/outbound file feed failures.
• Read the Relius data model fluently enough to diagnose issues at the data level and write safe corrective scripts in
• a regulated environment.
• Platform & data integration
• Support data movement off the platform (e.g., Oracle data lake pipelines, CDC-based replication) and
• integrations with custodians, advisors, and downstream systems.
• Monitoring and observability for the estate (server/event-log monitoring, alert triage).
• Database access management: grant, review, and revoke access as part of onboarding/offboarding.

Must-Haves

• Deep, hands-on Oracle DBA experience (12c/19c era) running production databases: patching, backup/recovery,
• refreshes, performance tuning, capacity management.
• Strong PL/SQL able to read a large legacy schema and write safe, reviewed corrective scripts against live
• financial data.
• A track record of debugging, then developing in, legacy systems within heavily regulated, brownfield
• financial environments comfort operating where the safest change wins.
• Production support temperament: methodical triage and disciplined change control.
• Strong communication: clear, proactive written updates on tickets and email, comfortable leading vendor calls and
• being the visible point of contact for production issues, effective async collaboration across time zones.
• Effective, habitual use of AI development tools as part of daily work.
• Experience running databases in a public cloud (OCI strongly preferred; equivalent AWS/Azure DB operations
• experience considered).

Nice-to-Haves

• FIS Relius Administration experience (schema, service packs, environment management) a significant
• differentiator.
• Retirement/recordkeeping or broader financial services domain knowledge (plans, participants, contributions,
• distributions, loans).
• SQL Server familiarity (we run a mixed estate; cross-cover with the TSM platform owner is valuable).
• Experience with CDC/replication into data lakes (Databricks or similar).
• Modernization experience (migrations, re-platforming) nice-to-have, not required.

How We’ll Evaluate

• Practical Oracle depth: walk us through a production patching cycle, a recovery you’ve run, and a performance
• problem you’ve chased to root cause.
• Legacy debugging: given an unfamiliar schema and a data anomaly, show us how you’d isolate it and what a safe
• fix looks like.
• Judgment at the prod gate: what you’d push back on in a developer’s script, and why