Sr. Oracle Technical Developer
Sr. Oracle Technical Developer
Posted today
SENIORITY
Lead
About the role
- Develop and maintain RICEW components (Reports, Interfaces, Conversions, Extensions, Workflows) consistent with internal technical design standards.
- Build and optimize PL/SQL programs, including custom packages, procedures, views, and database objects
- Implement and support concurrent programs, validations, and staging-table frameworks for inbound/outbound integrations.
- Support OIC integrations, file-based data pipelines, schedulers, REST/SOAP integrations, and error-handling frameworks consistent with OIC patterns.
- Create OTBI/BIP reports and EBS XML Publisher components. Technical Architecture & Standards
- Ensure compliance with EBS 12.2 online patching (ADOP) requirements and coding standards.
- Conduct performance tuning of SQL, PL/SQL, workflows, and interface programs.
- Maintain custom objects in line with technical governance processes and RICEW development life cycle.
- Adhere to internal environment, migration, and deployment standards. Testing & Release Support
- Build unit test plans, conditions, and test data based on technical specification patterns.
- Perform debugging and root-cause analysis across interfaces, APIs, custom objects, and workflows.
- Support integrated testing, regression cycles, and release validation for quarterly patches and ERP upgrades. Production Support
- Investigate and resolve technical issues involving custom code, integrations, concurrent programs, and database performance.
- Analyze staging-table errors, interface failures, and OIC orchestration logs following the enterprise error-handling framework.
- Provide on-call support for batch failures, data corrections, and system performance issues. Collaboration & Documentation
- Work with functional teams to validate requirements and translate them into detailed technical designs and MD70 documents.
- Provide impact analysis for patches, customizations, SLA changes, table updates, and integrations.
- Maintain code documentation, configuration files, and migration trackers consistent with internal TDD expectations.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
