Oracle Integration Cloud (OIC) connects Oracle Cloud ERP, SCM and HCM to everything else a manufacturer runs: plant systems, warehouses, EDI partners, banks and legacy applications. Many resumes list "integrations." Far fewer candidates can design, secure and support OIC integrations that hold up under live transaction volumes. The difference rarely shows in an interview that sticks to tool names. It shows at go-live.
- An OIC architect is responsible for integration design, error handling, security and supportability, not just building flows that work in testing.
- Deep knowledge of how Oracle Fusion applications exchange data, through REST and SOAP services, file-based data import (FBDI), BI Publisher extracts and business events, matters as much as knowledge of OIC itself.
- In manufacturing, the hardest integrations are with MES, WMS, EDI partners and on-premises systems, which usually require the connectivity agent.
- Interview with real scenarios: a failed inbound load at 2 a.m., a partner sending malformed files, or a volume spike at month-end.
What the role actually covers
An OIC developer builds integrations. An OIC architect decides how integrations should be built across the program and owns the consequences. That includes choosing the integration pattern for each flow, setting standards for naming, versioning and error handling, designing security, and making sure the support team can monitor and recover failures after go-live.
In practice, the architect is often the person who connects the functional teams. When finance needs bank statements loaded, supply chain needs advance ship notices from a 3PL, and the plant needs production orders sent to MES, the architect turns those needs into a consistent design rather than a collection of one-off flows.
Six capabilities to look for
1. Integration patterns and when to use each
A strong candidate can explain when an app-driven orchestration triggered by an event is the right choice, when a scheduled integration fits better, and when a file-based bulk load is the only sensible option. Ask why they chose a pattern on a past program and what they would change.
2. Fluency in how Oracle Fusion moves data
OIC skill is only half the job. The architect must know the Fusion side: REST and SOAP services, FBDI for high-volume imports, BI Publisher reports for extracts, scheduled processes, and business events. Someone who only knows OIC will design flows that fight the application instead of working with it.
3. Error handling and recovery designed in from the start
Integrations fail. Files arrive late, records are rejected, endpoints time out. Look for someone who designs for that: fault handlers, clear error notifications, safe resubmission, and a way for support staff to see what failed and why without reading code.
4. Security and connectivity
Ask how they handled authentication (such as OAuth and certificates), credential management, and connections to on-premises systems through the OIC connectivity agent. In manufacturing, many critical systems still sit on-premises behind the plant firewall.
5. Performance at real volumes
An integration that works for ten test records can fail for ten thousand at month-end. Strong candidates talk about batching, paging, parallel processing, payload size and the limits of the services they call.
6. Supportability and lifecycle
Ask how they managed versions, promoted integrations between environments, documented interfaces and used lookups and connections so that a change of endpoint did not mean editing dozens of flows. The best architects leave behind something the support team can run.
Ask a candidate about the worst integration failure they handled after go-live. The answer tells you more than any list of adapters.
Manufacturing-specific integrations
- MES: sending work orders and receiving completions, scrap and labor back into Oracle Fusion Manufacturing.
- WMS and 3PLs: receipts, shipments and inventory adjustments, often with partner-specific file formats.
- EDI: purchase orders, advance ship notices and invoices with customers and suppliers, typically through an EDI provider.
- Engineering and PLM: item and bill-of-material changes flowing into the ERP without breaking planning.
- Legacy and on-premises ERP: during a phased rollout, plants on the old system and plants on Oracle Cloud must exchange data reliably.
Interview questions that separate architects from builders
- Walk me through an integration you designed for high-volume inbound data. Why that pattern, and how did you handle rejected records?
- An inbound FBDI load failed overnight and the plant needs the data by 6 a.m. What do you check first, and how is the design built to make that fast?
- How did you connect OIC to a system behind a plant firewall, and what did you have to agree with the network and security teams?
- How did you manage versions and promotion of integrations from development to production?
- What standards did you set for other developers on the program, and how did you enforce them?
Red flags
- Describes every integration as "point-to-point" with no reusable design.
- Cannot explain how errors were monitored or resubmitted after go-live.
- Knows OIC screens but not the Oracle Fusion services they were calling.
- Has only worked in test environments, never supported a live production cutover.
Maxary places OIC architects and Oracle Cloud specialists for manufacturers, scored by VeriTalent.ai and reviewed by practitioners who have run Oracle Cloud programs. See what we staff or how VeriTalent.ai scores candidates.