Product Application Engineer

Product Application Engineer (PAE) – DrivesThe 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 OwnershipOwn end-to-end Drives system architecture, including: LV and MV VFDs, transformers, line reactors, and filters, bypass schemes and control architecturesValidate application suitability based on process conditions, environment, and duty cycleOwn technical assumptions, risks, exclusions, and deviations related to Drives scopeEnsure compliance with: customer specifications, IEC/IEEE standards (harmonics, EMC, insulation, etc.), Schneider Electric Drives application and portfolio rulesPrimary Responsibilities:Pre-Sales Technical SupportReview customer technical specifications and process requirementsValidate: Drive and motor compatibility, constant/variable torque duty cycles, environmental conditions (ambient temperature, altitude, enclosure type)Assess application-specific risks, including: harmonics, motor compatibility, bypass, redundancy, and cooling requirementsSupport Sales during technical discussions with customersSolution Design & Architecture OwnershipDefine overall Drives solution architecture, including: Drive topology, input/output filtering, control philosophy and communication approachEnsure alignment with standard and approved Schneider Electric Drives offeringsReview and approve concept-level documentation: functional descriptions, single-line and concept diagrams, control and interlock philosophiesHandover to Project ExecutionLead or support the technical handover for Drives scopeDocument and communicate: application constraints, technical assumptions and exclusions, known risks (harmonics, motor stress, cooling, bypass design)Support early execution phases to prevent rework and late-stage changesCross-Functional Collaboration & GovernanceCollaborate closely with: Sales, Project Managers, Engineering & FactoriesChallenge non-standard or high-risk Drive applicationsCapture and share lessons learned within the Drives communityOut of Scope / Not Accountable For:Detailed electrical schematics or CAD draftingDay-to-day project managementCommercial negotiations, pricing, or margin ownershipFactory expediting or order managementSuccess Metrics:Reduction in Drives-related execution changesFewer technical escalations during commissioningPositive feedback from Project Management and EngineeringAdherence to Drives standards and best practicesFirst 90 Days Expectations:0–30 Days: Learn product ranges, standards, and common Drive applications31–60 Days: Support opportunities with increasing technical ownership61–90 Days: Independently own Drives solutions end-to-end for assigned scopeProfessional Mindset: "If the motor, drive, and process don't work together, the solution isn't finished."