AS

ERP Technical Architect

ascendion
Pune Posted 18 Nov 2026
FULL TIME
Oracle Ebs
Integration Architecture
Ai
Cloud

Job Description

About Ascendion

Ascendion delivers AI-Native software engineering services that help Global 2000 organizations accelerate innovation. Our applied AI, software engineering, cloud, data, experience design, and talent transformation capabilities enable scalable, real-world outcomes. Ascendion is headquartered in New Jersey. Along with a remote/hybrid workforce, the company maintains operations in 12 countries and 40+ global offices across North America, Europse, and APAC. Ascendion is committed to building technology powered by Generative AI, supported by an inclusive workforce, service to communities, and a vibrant culture. Learn more at www.ascendion.com.

Experience a community of change makers!

Join a culture of high-performing innovators driven by endless ideas and a passion for technology. At Ascendion, culture is the foundation of how we work—fueling uniqueness, diversity, and continuous improvement. By sharing ideas, learning, experiences, successes, and joy, everyone has the opportunity to do their best work at Ascendion.

Job Description

The ERP Technical Architect is a key leadership role focused on securing, stabilizing, and simplifying our legacy Oracle EBS environments (12.1.3 and 12.2.3). The Architect acts as the essential link between day-to-day tactical maintenance, risk mitigation, and forward-looking strategic delivery.

Role

This role is critical to reducing technical debt and defining the strategic roadmap toward Cloud and AI adoption. The Architect will partner closely with cross-functional teams, including:

  • The ERP Strategist
  • Enterprise Architects
  • Agile Fusion Teams
  • Tier 2 (T2) Support and Tier 3 (T3) Lead Technical Developers
  • DBA and Infrastructure Groups
  • Our Managed Resource Partner

Key Responsibilities

  • Strategic Focus Areas & Core Responsibilities

The Architect’s responsibilities are structured around the same outcome pillars to maintain a clear line of sight from responsibilities to measurable results, governance expectations, and business value.

1.1 Security, Patching & Technology Lifecycle

Security and lifecycle management for our legacy environments are immediate priorities. The Architect owns the technology stack lifecycle, including planning for patches and critical upgrades for both the application and the underlying infrastructure.

  • 12.1 Environments: Immediately develop and drive a validated upgrade plan for 12.1 databases and operating systems, including a detailed risk assessment focused on application security vulnerabilities.
  • 12.2 Environments: Lead immediate execution of outstanding security patches (e.g., June updates) and complete the HTTPS implementation.
  • Playbook & Governance: Create a repeatable approach for analyzing, testing, and applying Critical Patch Updates (CPUs). Define, audit, and own the technical processes for environment cloning, backups, and disaster recovery restores.

1.2 Operational Reliability & Performance

The Architect owns proactive reliability engineering, performance management, service expectations, and workload automation planning across the ERP environment.

  • Performance KPIs & Monitoring: Establish, implement, and continuously improve EBS performance KPIs, monitoring standards, alerting thresholds, and reporting cadence to identify risks early and maintain system stability.
  • Performance Remediation: Own the end-to-end monitoring and remediation workflow using tools such as AWR, Oracle Enterprise Manager, EBS Analyzers, workflow monitoring, and related solutions.
  • System Health: Lead ongoing monitoring and tuning of SQL, batch jobs, workflows, and system components, directing T2 resources to execute remediation activities that sustain performance and reliability.
  • Service Reliability & SLAs: Define measurable support and performance SLAs, track results against targets, and drive continuous improvements that strengthen the user experience and operational stability.
  • Enterprise Job Scheduling: Provide architectural leadership for enterprise job scheduling and workload automation, guiding the transition from current-state tools such as Oracle Concurrent Manager and Automic to future-state platforms aligned with enterprise architecture standards.

1.3 Integration Architecture & Decoupling

To maintain operational agility, EBS must modernize how it interacts with the customer’s broader digital ecosystem.

  • Modernization: Define and own integration standards, replacing legacy point-to-point integrations with a modern reference architecture.
  • Decoupling: Decouple core EBS from critical plant-floor business processes (e.g., code date printing, production scheduling) to maximize manufacturing uptime.
  • Governance and oversight of integrations service. Demonstrate a deep understanding of common Oracle integration methods, architecture, and other relevant approaches.

1.4 Development Standards, Documentation & Knowledge Management

The Architect governs technical development standards, documentation practices, knowledge transfer, and quality expectations to improve consistency, supportability, and readiness for Cloud adoption.

  • Development Standards: Review, maintain, and govern EBS development standards in Confluence, ensuring standards stay current, practical, and aligned with Oracle best practices and future Fusion Cloud expectations.
  • Quality Gates: Define expectations for code review, test automation, documentation, and Cloud readiness for all new or modified technical solutions.
  • AAVA Leadership: Lead the deployment and execution of AAVA for process discovery, technical documentation, auditing, and enforcement of development standards.
  • Knowledge Management: Maintain up-to-date EBS technical documentation and ensure critical knowledge is organized, accessible, and actively used by support and delivery teams within Confluence.
  • Training & Mentorship: Develop, organize, and lead Oracle development and integration fundamentals training, offering ongoing guidance to T2 and T3 teams.

1.5 Architecture Discovery, Customization Clean-Up & Cloud Readiness

The Architect delivers a data-driven view of the Oracle EBS landscape and leads technical simplification initiatives that reduce complexity, improve supportability, and prepare for future ERP modernization.

  • EBS Architecture Profile: Build and maintain a detailed Oracle EBS landscape profile, including environment inventory, customization mapping, integration dependencies, and insights from current-to-future architecture.
  • Architectural Discovery: Convert profiling insights into actionable recommendations to enable faster decisions, reduce complexity, improve supportability, and accelerate ERP modernization.
  • Customization Clean-Up: Own identification and remediation of legacy customizations by evaluating business value, prioritizing retirement candidates, and partnering with development teams to remove obsolete code.
  • Cloud Readiness: Ensure current design decisions and technical standards support future ERP modernization and align with Fusion Cloud principles where applicable.

1.6 Fusion Cloud Release Governance, AI & Automation

The Architect governs Fusion Cloud release impacts and identifies practical opportunities for AI and automation that simplify ERP operations, reduce manual effort, and improve business value.

  • Fusion Release Governance: Lead technical governance for Oracle Fusion Cloud releases and platform changes, collaborating with Fusion teams to assess impacts from monthly and quarterly technical updates (e.g., IAM upgrades, region moves, and other infrastructure changes).
  • AI & Simplification: Lead governance and adoption of AI and automation capabilities across the Oracle ERP ecosystem to simplify operations, reduce manual work, and maximize business value.

1.7 Technical Governance & Escalation

The Architect serves as the technical ERP governance and escalation lead, enabling teams to make informed decisions, resolve complex issues, and engage the appropriate internal or external stakeholders.

  • Technical Point of Contact: Act as the primary technical contact for ERP platform questions, risks, standards, and issue resolution.
  • Decision Support: Assess technical risks, clarify decision rights, and guide cross-functional teams toward outcomes that are supportable and strategically aligned.
  • Escalation Leadership: Escalate complex issues to the appropriate internal teams, enterprise architecture partners, managed resource partners, or vendors to ensure timely and effective resolution.

Join Ascendion

Join a team building next-generation AI solutions and helping enterprises accelerate innovation through Generative AI.
foundit: Feeling underpaid? Find jobs that pay you what you are worth. Find jobsSponsored
Join WhatsApp Channel