Director, Engineering - ERP ( Strictly ERP Domain Candidates)

About QAD:

Qualifications

• 12+ years in engineering, with 5+ years leading managers (Director/Senior Director scope) at an ERP product company (SAP, Oracle, Infor, Epicor, IFS, Microsoft Dynamics, Workday, Sage, Unit4 or comparable). Experience at SIs or consultancies alone does not qualify.
• Has owned a substantial module, platform, or product line of an ERP product, covering roadmap, quality, and delivery.
• Leads multiple teams through managers/senior managers. Not primarily a hands-on architect or single-team manager.
• Has worked with Product, Architecture, Services, and Support to turn customer problems into product capabilities.
• ERP Product Engineering: Experience with mature enterprise products: large legacy codebases, long-lived customers, customization/extensions, upgrades, backward compatibility, and modernization.
• AI & Software Engineering: Strong AI experience remains important. In particular, look for leaders who have applied AI to software development, modernization, or engineering transformation.
• Enterprise Software Architecture: Strong understanding of software architecture, system design, APIs, integrations, data, and distributed systems, with the ability to guide technical direction across a large and evolving enterprise product.
• Enterprise Product Evolution: Evidence of leading significant product or engineering transformation while continuing to serve an existing enterprise customer base.
• Cloud & Modern Engineering: Strong understanding of cloud architectures, preferably AWS, modern development practices, CI/CD, automated testing, observability, security, and modern SDLC practices.
• Technical Judgment: Ability to evaluate architectural alternatives and make pragmatic decisions that balance long-term technical direction with customer needs, delivery constraints, cost, risk, and business value.
• Partner Delivery Governance: Proven ability to establish technical direction, quality standards, engineering discipline, and accountability across blended internal and third-party engineering organizations.
• Transformation-Oriented: Sees complexity as something to systematically eliminate rather than permanently accommodate.
• AI-Minded: Has a substantive point of view on how AI is changing software development and actively looks for opportunities to apply it to previously difficult problems.
• Customer-Focused: Understands that successful modernization must solve real customer problems, not simply produce cleaner technology.
• Pragmatic Decision-Maker: Balances future architecture and engineering ideals with the realities of mature enterprise software and existing customers.
• Coach & Multiplier: Develops managers and senior engineers and creates organizations capable of operating effectively without constant intervention.
• Ownership-Oriented: Takes accountability for outcomes, quality, reliability, and delivery.
• Continuous Improver: Consistently challenges existing systems and practices and looks for ways to make them simpler, more scalable, and more effective.