Lead Principal Platform Software Engineer

The Lead Principal Platform Architect is the customer-facing program lead for a portfolio of large enterprise managed-cloud customers. The role owns the operating pulse of each account: customer priorities, active projects and enhancements, service risks, major incidents, delivery dependencies, and follow-through across Oracle teams.

This is not an implementation or product-configuration role. Product, application, integration, and infrastructure SMEs provide deep specialist expertise. The Service Architect brings those teams together, keeps the customer informed, drives decisions to closure, and ensures that service and project commitments produce the intended business outcome.

Own the customer program: Serve as the primary operating counterpart for customer business and IT leaders. Establish the cadence for service reviews, project updates, risks, decisions, and executive communications.

Drive run-and-maintain outcomes: Maintain a clear view of service health, open issues, risks, dependencies, and customer priorities across Oracle applications, PaaS/integrations, and supporting infrastructure.

Lead projects and enhancements: Turn customer priorities into an executable plan; coordinate scope, milestones, owners, dependencies, change readiness, testing, customer communication, and delivery follow-through.

Coordinate incident and continuity response: Lead customer-facing coordination during significant incidents. Establish impact, communication cadence, escalation, recovery tracking, and corrective-action follow-up with the appropriate Oracle and customer teams.

Orchestrate the right expertise: Engage functional, product, integration, infrastructure, security, and operations SMEs at the right point; resolve cross-team blockers and maintain end-to-end accountability without trying to be the specialist in every domain.

Translate across business and technology: Understand the business effect of issues and changes; help customer and Oracle stakeholders make informed priorities and trade-offs.

Improve the service: Identify recurring delivery or operational friction and help introduce practical automation, AI-enabled capabilities, or process improvements when they have clear customer value and appropriate controls.

Scope boundary

The Service Architect owns the customer program and operating outcome. Product configuration, engineering build, technical diagnosis, and specialist remediation remain with the appropriate SMEs and delivery teams.