Product Application Engineer

The Product Application Engineer (PAE) – Drives serves as the technical owner for motor control and variable frequency drive (VFD) solutions, supporting opportunities from pre-sales through early project execution. This role ensures Drive system architectures are safe, compliant, properly sized, and executable, acting as the technical bridge between Sales, Project Management, and Engineering.

The PAE protects the customer, project execution, and Drives portfolio by ensuring only buildable, technically defensible solutions progress into execution.

Key Accountabilities Drives Technical Ownership
· Own end-to-end Drives system architecture, including:o LV and MV VFDso Transformers, line reactors, and filterso Bypass schemes and control architectures
· Validate application suitability based on process conditions, environment, and duty cycle
· Own technical assumptions, risks, exclusions, and deviations related to Drives scope
· Ensure compliance with:o Customer specification so IEC / IEEE standards (harmonics, EMC, insulation, etc.)o Schneider Electric Drives application and portfolio rules

Primary Responsibilities Pre-Sales Technical Support
· Review customer technical specifications and process requirements
· Validate:o Drive and motor compatabilityo Constant/variable torque duty cycleso Environmental conditions (ambient temperature, altitude, enclosure type)
· Assess application-specific risks, including:o Harmonic so Motor compatibilityo Bypass, redundancy, and cooling requirements
· Support Sales during technical discussions with customers

Outcome:
Only technically sound and executable Drives solutions are offered.

Solution Design & Architecture Ownership
· Define overall Drives solution architecture, including:o Drive topologyo Input/output filteringo Control philosophy and communication approach
· Ensure alignment with standard and approved Schneider Electric Drives offerings
· Review and approve concept-level documentation:o Functional description so Single-line and concept diagramso Control and interlock philosophies

Outcome:
Engineering receives clear technical intent with minimal ambiguity.

Handover to Project Execution
· Lead or support the technical handover for Drives scope
· Document and communicate:o Application constraintso Technical assumptions and exclusion so Known risks (harmonics, motor stress, cooling, bypass design)
· Support early execution phases to prevent rework and late-stage changes

Outcome:
Project Managers and Engineering teams begin execution with clarity and confidence.

Cross-Functional Collaboration & Governance
· Collaborate closely with:o Sales:
Enable feasible, win-ready technical solution so Project Managers:
Provide clear scope definition and risk visibilityo Engineering & Factories:
Promote standard, repeatable Designs
· Challenge non-standard or high-risk Drive applications
· Capture and share lessons learned within the Drives community

Out of Scope / Not Accountable For
· Detailed electrical schematics or CAD drafting
· Day-to-day project management
· Commercial negotiations, pricing, or margin ownership
· Factory expediting or order management(The PAE provides guidance and technical ownership; execution is performed by delivery teams.)Success Metrics
· Reduction in Drives-related execution changes
· Fewer technical escalations during commissioning
· Positive feedback from Project Management and Engineering
· Adherence to Drives standards and best practices

First 90 Days Expectations
· 0–30 Days:
Learn product ranges, standards, and common Drive applications
· 31–60 Days:
Support opportunities with increasing technical ownership
· 61–90 Days:
Independently own Drives solutions end-to-end for assigned scope
· LV and/or MV VFD systems and motor control applications
· Industrial…