Lead Principal Field Systems Engineer

Oracle Cloud Infrastructure is building the next generation of cloud and AI infrastructure at global scale. As demand for GPU capacity, cloud regions, and strategic infrastructure delivery continues to grow, OCI needs hands-on systems thinkers who can operate close to the field, understand where deployment execution is breaking down, and help turn recurring friction into durable improvements. The Field Systems Engineer is a senior individual contributor role focused on improving deployment readiness, commissioning, and production handoff across complex technical and operational environments. This person will partner closely with Delivery, Engineering, Networking, Data Center Operations, Construction, Supply Chain, Finance, and other cross-functional teams to establish ground truth, identify systemic misses, and close the loop so OCI is not solving the same deployment problems repeatedly. The ideal candidate does not necessarily need direct GPU or cloud infrastructure experience, but must bring strong field execution instincts, technical curiosity, operational discipline, and the ability to dive deep into ambiguous problems and drive practical, scalable solutions.

• Partner with Delivery org as a hands-on technical and operational counterpart while Delivery continues to own end-to-end execution.

• Establish ground truth when readiness, commissioning, or handoff issues are unclear or not reflected in status reporting.

• Identify recurring deployment pain points across site readiness, hardware, networking, cabling, power/cooling, validation, commissioning, and operational handoff.

• Translate Delivery pain points into clear requirements, process fixes, escalation paths, or playbook updates for the right vertical owners.

• Build readiness gates, go/no-go criteria, validation mechanisms, and handoff standards that improve the path from planned capacity to production-ready capacity.

• Close the loop on recurring issues by driving systemic fixes back into process and preventing repeat problems across regions, metros, and programs.

• Convert field learnings into repeatable mechanisms, operating rhythms, dashboards, executive narratives, and deployment-readiness improvements.

• Travel to deployment sites and partner locations as needed.

• Turn ambiguity into structure in complex environments with unclear ownership and shifting priorities.

• Apply systems thinking across people, process, data, tools, technical dependencies, and organizational handoffs.

• Separate signal from noise and identify what requires escalation, intervention, or executive decision-making.

• Use data, field observations, and stakeholder input to clarify problems, test assumptions, and guide decisions.

• Communicate clearly with executive, technical, and field stakeholders without losing nuance or credibility.

• Influence cross-functional teams through facts, clarity, urgency, and trust rather than formal authority.

• Improve execution without adding unnecessary bureaucracy.

• Remain resilient in high-pressure delivery environments where decisions must be made with imperfect information.

• Travel approximately 25–50% based on deployment needs and business priorities.

• Delivery teams have stronger visibility into recurring pain points, systemic blockers, readiness gaps, and handoff risks that affect deployment execution.

• Critical GPU and cloud infrastructure initiatives have clearer readiness gates, go/no-go criteria, risk signals, ownership paths, and decision mechanisms.

• Deployment blockers are identified earlier, understood more accurately, and converted into durable process or playbook improvements.

• Field learnings are consistently translated into actionable requirements for Engineering, Networking, Construction, Operations, Supply Chain, tooling, or other vertical owners.

• Executive stakeholders have a clearer, more accurate view of deployment health, blocked capacity, commissioning risk, customer impact, and decisions required.

• Operational handoffs between planning, Delivery, Engineering, deployment teams, and site operations become cleaner, more accountable, and more repeatable.

• OCI improves deployment predictability, reduces avoidable slippage, and strengthens readiness for high-priority AI and cloud infrastructure programs.

• The mechanisms you build continue to create value beyond a single escalation, launch, region, customer commitment, or executive review cycle.