Sales Enablement Engineer
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must include only sections with real specific content. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, legal, navigation, cookie, duplicated lines, application instructions. Also remove "Job ID / requisition numbers". Must not create sections like Pay/Schedule/Benefits unless posting actually states them. The posting includes pay range: "For this U.S. based position, the expected pay range is USD 86,400 - USD 129,600 per year." So we can include Pay section. Benefits: there is a "Local Benefits (English)" section describing benefits. So we can include Benefits. Schedule: not mentioned explicitly; it's full-time but not schedule details like hours. Probably we should not create Schedule section because no specific schedule content. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we can create Pay and Benefits but not Schedule.
We need sections: About the role (maybe from first paragraph). Responsibilities (What You'll Do). Requirements (Experience (External) maybe). Qualifications (Education). Skills (Technical Skills, Mindset). Benefits (Local Benefits). Pay (expected pay range). Possibly also "Experience" as separate? But we have Requirements and Qualifications; we can combine experience under Requirements, education under Qualifications. Skills under Skills.
We must not repeat job title as heading. So headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We need to use - for any list of duties/requirements/benefits. For prose use
. Must preserve all substantive info; do not invent or summarize away detail. So we need to include details from the posting.
We need to extract content.
Let's parse the posting:
- About This Role Job Description: The Application Design Engineer – Sales Enablement is a hands‑on technical specialist who owns the US EAE demo portfolio and ensures customers, partners, and sales teams can effectively experience the value of EcoStruxure Automation Expert. The person is responsible for defining what demos are needed, building and maintaining them, and ensuring they remain relevant, reliable, and impactful over time. Demos may be hardware‑based, software‑based, or fully simulated, and are used to support customer meetings, workshops, events, briefing centers, training activities, and strategic opportunities. This role manages the complete demo lifecycle, from identifying needs and defining concepts to development, testing, deployment, maintenance, usage tracking, and continuous improvement. The person also creates the technical materials required to support each demo, enables teams to use them independently, and serves as the go‑to technical resource for demo‑related activities across the organization. By combining engineering expertise, creativity, and a strong understanding of customer needs, the Application Design Engineer – Sales Enablement helps accelerate EAE adoption through compelling technical demonstrations, reusable assets, and a scalable demo strategy.
That's the "About the role" content.
- What You'll Do: Build & Develop Demos (list of bullet points). Own & Execute the Demo Strategy (list). Create Demo‑Specific Content & Tools (list). Own the Complete Demo Lifecycle (list). Enable Teams to Use the Demos (list). Support Events & Share Knowledge (list). So we need to capture these as list items under Responsibilities.
We must not lose any bullet details.
Let's extract bullet points:
Under "Build & Develop Demos":
- Design and develop hardware‑based, software‑based, or simulated demos that showcase EAE's core value propositions, including IEC 61499 portability, scalability, IT/OT convergence, and ease of integration.
- Build application‑specific demos for target verticals such as Food & Beverage, Water & Wastewater, Mining, and Data Centers.
- Create reusable demo modules, function block libraries, and CAT elements that can be adapted quickly for customers, events, and different sales stages.
- Prototype and validate new concepts before investing in full builds.
Under "Own & Execute the Demo Strategy":
- Develop and own the US EAE demo strategy and roadmap, defining what demos are needed, for whom, when, and why, in alignment with Marketing, Offer Management, the CoE, and sales leadership.
- Map the demo portfolio against target verticals, use cases, buyer personas, events, and key opportunities to identify gaps.
- Prioritize new demos, upgrades, replication, and retirement based on field demand, business impact, reuse potential, feasibility, cost, and maintenance effort.
- Track demo readiness, reliability, usage, trained users, field feedback, customer reactions, and follow‑up actions.
- Coordinate with the global EAE CoE and local teams to reuse assets, share best practices, and avoid duplication.
Under "Create Demo‑Specific Content & Tools":
- Create the technical materials required to use each demo effectively, including scripts, architecture diagrams, setup guides, operator instructions, technical deep dives, videos, FAQs, and troubleshooting guidance.
- Translate messaging defined by Marketing and Offer Management into clear demo flows, technical proof points, and audience‑appropriate explanations.
- Adapt demo materials for customer meetings, workshops, trade shows, briefing centers, webinars, and internal enablement.
- Keep demo content technically accurate and aligned with current EAE releases and approved positioning.
Under "Own the Complete Demo Lifecycle":
- Own requirements, architecture, design, sourcing, assembly, software development, simulation, testing, validation, documentation, deployment, version control, maintenance, and retirement.
- Keep demos current with relevant EAE software and hardware releases and validate their performance before use.
- Maintain a searchable registry covering each demo's location, configuration, version, purpose, audience, readiness, usage history, and maintenance needs.
- Coordinate shipping, setup, teardown, storage, and readiness for customer engagements and events.
- Use field feedback and usage evidence to improve, consolidate, replicate, or retire demos.
Under "Enable Teams to Use the Demos":
- Train sales engineers, Business Development Managers, Application Design Engineers, and partners to deliver consistent EAE demonstrations independently.
- Develop playbooks, cheat sheets, facilitator guides, setup checklists, and modular technical materials.
- Coach presenters before important customer meetings, workshops, and events.
- Act as the go‑to technical resource for demo selection, setup, operation, troubleshooting, and adaptation.
Under "Support Events & Share Knowledge":
- Lead or support the technical demo experience for trade shows, conferences, briefing centers, webinars, partner events, and customer engagements.
- Capture demo feedback, recurring questions, reliability issues, lessons learned, and recommended actions.
- Maintain a structured SharePoint library of demo source files, architectures, configurations, scripts, guides, videos, and playbooks.
- Share US demo innovations and customer feedback with the global EAE organization.
Now Requirements: "Experience (External)" section:
- 2–5 years of experience in industrial automation, embedded software engineering, or a technical pre‑sales / application engineering role.
- Proven track record of building and delivering technical demonstrations or proof‑of‑concept systems — in a lab, on a trade show floor, or both.
- Experience presenting to technical and non‑technical audiences; comfort with live, unscripted Q&A.
Qualifications: Education: Master/Bachelor's degree in Electrical/Electronic Engineering, Computer Science, Software Engineering, or equivalent technical field.
Skills: Technical Skills list:
- Experience developing software for control systems — PLC, IEC 61499/61131‑3 function blocks, or equivalent embedded/industrial programming frameworks.
- Software development: C/C++, Python, JavaScript, C# (HMI integration).
- Linux and Windows development environments; Docker/Kubernetes/Swarm; virtualization.
- Industrial networking: LAN/WAN/VLAN, managed switches, Modbus, EthernetIP, Profinet, MQTT, OPC UA.
- Hardware integration: I/O wiring, panel assembly, PLC/drive configuration, sensor commissioning.
- Familiarity with IIoT platforms, edge computing, and IT/OT convergence concepts.
Mindset Builder mentality etc:
- Builder mentality — you are most satisfied when something works that didn't exist before.
- High ownership: you treat demo assets as products, not one‑offs. You care about quality, reliability, and longevity.
- Storyteller: you instinctively translate technical facts into compelling narratives that move people.
- Organized and rigorous — you can manage a complex inventory of hardware and software across multiple locations without things slipping.
- Energized by live events and customer contact; you perform well under pressure and recover fast when things go sideways.
We could include these under Skills or maybe a separate "Mindset" but instruction says use headings like Skills; we can include mindset under Skills as part of list.
Benefits: Local Benefits (English) section includes a paragraph about Total Rewards, then bullet-like sentences: "Care for Yourself and Your Family. We ensure you feel secure with benefits that help you and your family thrive: medical (with member reward points), dental, vision, and basic life insurance, Benefit Bucks, flexible work arrangements, paid family leaves, well‑being programs, 12 holidays per year, and 15 days of paid time off per year." Then "Invest and Plan Your Future. We help you plan and invest for the future with competitive pay and programs including base salary, incentives, company share ownership, and 401(k) with match." Then "Grow Your Skills and Career. We support development through performance discussions, global opportunities, the Schneider Career Hub, and learning platforms like Coursera." Then "Team Up in the Workplace. We encourage collaboration, recognition, sharing your voice, and an inclusive workplace." Then "Support Your Community. We make a difference through volunteer leave, programs with the Schneider Electric Foundation, youth education initiatives, and military leave benefits."
We need to preserve all substantive info; we can turn each sentence into list items or keep as prose. The instruction: use
- for any list of duties/requirements/benefits. So we should convert benefits into list items.
Pay: "For this U.S. based position, the expected pay range is USD 86,400 - USD 129,600 per year. This pay range includes base pay and short‑term incentives. The compensation range for this full‑time position applies to candidates located within the United States. Our pay ranges are determined by reviewing roles of similar responsibility and level. Within the pay range, individual pay is determined by several factors including performance, knowledge, job‑related skills, experience, and relevant education or training."
We need to include that as Pay section. Should we list as
- ? It's not a list but could be prose. The instruction: use
- for any list of duties/requirements/benefits. Pay is not a list; we can use
. But we could also break into list items for clarity but not required. We'll use
.
Now we must remove boilerplate: EEO, legal, navigation, cookie, duplicated lines, application instructions. Also remove "Job Posting Compliance Form.* (External) English Company Boiler Plate:" and all that following. Also remove "If you believe this job posting is not compliant..." etc. Also remove "You must submit an online application..." etc. Also remove the company boilerplate about IMPACT etc. Also remove the Trust Charter etc. Also remove the Equal Opportunity Employer statement. Also remove the "€40 billion global revenue +9% organic growth 150 000+ employees in 100+ countries". Also remove "Schneider Electric aspires to be the most inclusive..." etc. All that is boilerplate.
We must keep only substantive content: About the role, Responsibilities (What You'll Do), Requirements (Experience), Qualifications (Education), Skills (Technical Skills + Mindset), Benefits, Pay.
We must not repeat job title as heading. So we will not include heading "Application
. Must preserve all substantive info; do not invent or summarize away detail. So we need to include details from the posting. We need to extract content. Let's parse the posting: - About This Role Job Description: The Application Design Engineer – Sales Enablement is a hands‑on technical specialist who owns the US EAE demo portfolio and ensures customers, partners, and sales teams can effectively experience the value of EcoStruxure Automation Expert. The person is responsible for defining what demos are needed, building and maintaining them, and ensuring they remain relevant, reliable, and impactful over time. Demos may be hardware‑based, software‑based, or fully simulated, and are used to support customer meetings, workshops, events, briefing centers, training activities, and strategic opportunities. This role manages the complete demo lifecycle, from identifying needs and defining concepts to development, testing, deployment, maintenance, usage tracking, and continuous improvement. The person also creates the technical materials required to support each demo, enables teams to use them independently, and serves as the go‑to technical resource for demo‑related activities across the organization. By combining engineering expertise, creativity, and a strong understanding of customer needs, the Application Design Engineer – Sales Enablement helps accelerate EAE adoption through compelling technical demonstrations, reusable assets, and a scalable demo strategy. That's the "About the role" content. - What You'll Do: Build & Develop Demos (list of bullet points). Own & Execute the Demo Strategy (list). Create Demo‑Specific Content & Tools (list). Own the Complete Demo Lifecycle (list). Enable Teams to Use the Demos (list). Support Events & Share Knowledge (list). So we need to capture these as list items under Responsibilities. We must not lose any bullet details. Let's extract bullet points: Under "Build & Develop Demos": - Design and develop hardware‑based, software‑based, or simulated demos that showcase EAE's core value propositions, including IEC 61499 portability, scalability, IT/OT convergence, and ease of integration. - Build application‑specific demos for target verticals such as Food & Beverage, Water & Wastewater, Mining, and Data Centers. - Create reusable demo modules, function block libraries, and CAT elements that can be adapted quickly for customers, events, and different sales stages. - Prototype and validate new concepts before investing in full builds. Under "Own & Execute the Demo Strategy": - Develop and own the US EAE demo strategy and roadmap, defining what demos are needed, for whom, when, and why, in alignment with Marketing, Offer Management, the CoE, and sales leadership. - Map the demo portfolio against target verticals, use cases, buyer personas, events, and key opportunities to identify gaps. - Prioritize new demos, upgrades, replication, and retirement based on field demand, business impact, reuse potential, feasibility, cost, and maintenance effort. - Track demo readiness, reliability, usage, trained users, field feedback, customer reactions, and follow‑up actions. - Coordinate with the global EAE CoE and local teams to reuse assets, share best practices, and avoid duplication. Under "Create Demo‑Specific Content & Tools": - Create the technical materials required to use each demo effectively, including scripts, architecture diagrams, setup guides, operator instructions, technical deep dives, videos, FAQs, and troubleshooting guidance. - Translate messaging defined by Marketing and Offer Management into clear demo flows, technical proof points, and audience‑appropriate explanations. - Adapt demo materials for customer meetings, workshops, trade shows, briefing centers, webinars, and internal enablement. - Keep demo content technically accurate and aligned with current EAE releases and approved positioning. Under "Own the Complete Demo Lifecycle": - Own requirements, architecture, design, sourcing, assembly, software development, simulation, testing, validation, documentation, deployment, version control, maintenance, and retirement. - Keep demos current with relevant EAE software and hardware releases and validate their performance before use. - Maintain a searchable registry covering each demo's location, configuration, version, purpose, audience, readiness, usage history, and maintenance needs. - Coordinate shipping, setup, teardown, storage, and readiness for customer engagements and events. - Use field feedback and usage evidence to improve, consolidate, replicate, or retire demos. Under "Enable Teams to Use the Demos": - Train sales engineers, Business Development Managers, Application Design Engineers, and partners to deliver consistent EAE demonstrations independently. - Develop playbooks, cheat sheets, facilitator guides, setup checklists, and modular technical materials. - Coach presenters before important customer meetings, workshops, and events. - Act as the go‑to technical resource for demo selection, setup, operation, troubleshooting, and adaptation. Under "Support Events & Share Knowledge": - Lead or support the technical demo experience for trade shows, conferences, briefing centers, webinars, partner events, and customer engagements. - Capture demo feedback, recurring questions, reliability issues, lessons learned, and recommended actions. - Maintain a structured SharePoint library of demo source files, architectures, configurations, scripts, guides, videos, and playbooks. - Share US demo innovations and customer feedback with the global EAE organization. Now Requirements: "Experience (External)" section: - 2–5 years of experience in industrial automation, embedded software engineering, or a technical pre‑sales / application engineering role. - Proven track record of building and delivering technical demonstrations or proof‑of‑concept systems — in a lab, on a trade show floor, or both. - Experience presenting to technical and non‑technical audiences; comfort with live, unscripted Q&A. Qualifications: Education: Master/Bachelor's degree in Electrical/Electronic Engineering, Computer Science, Software Engineering, or equivalent technical field. Skills: Technical Skills list: - Experience developing software for control systems — PLC, IEC 61499/61131‑3 function blocks, or equivalent embedded/industrial programming frameworks. - Software development: C/C++, Python, JavaScript, C# (HMI integration). - Linux and Windows development environments; Docker/Kubernetes/Swarm; virtualization. - Industrial networking: LAN/WAN/VLAN, managed switches, Modbus, EthernetIP, Profinet, MQTT, OPC UA. - Hardware integration: I/O wiring, panel assembly, PLC/drive configuration, sensor commissioning. - Familiarity with IIoT platforms, edge computing, and IT/OT convergence concepts. Mindset Builder mentality etc: - Builder mentality — you are most satisfied when something works that didn't exist before. - High ownership: you treat demo assets as products, not one‑offs. You care about quality, reliability, and longevity. - Storyteller: you instinctively translate technical facts into compelling narratives that move people. - Organized and rigorous — you can manage a complex inventory of hardware and software across multiple locations without things slipping. - Energized by live events and customer contact; you perform well under pressure and recover fast when things go sideways. We could include these under Skills or maybe a separate "Mindset" but instruction says use headings like Skills; we can include mindset under Skills as part of list. Benefits: Local Benefits (English) section includes a paragraph about Total Rewards, then bullet-like sentences: "Care for Yourself and Your Family. We ensure you feel secure with benefits that help you and your family thrive: medical (with member reward points), dental, vision, and basic life insurance, Benefit Bucks, flexible work arrangements, paid family leaves, well‑being programs, 12 holidays per year, and 15 days of paid time off per year." Then "Invest and Plan Your Future. We help you plan and invest for the future with competitive pay and programs including base salary, incentives, company share ownership, and 401(k) with match." Then "Grow Your Skills and Career. We support development through performance discussions, global opportunities, the Schneider Career Hub, and learning platforms like Coursera." Then "Team Up in the Workplace. We encourage collaboration, recognition, sharing your voice, and an inclusive workplace." Then "Support Your Community. We make a difference through volunteer leave, programs with the Schneider Electric Foundation, youth education initiatives, and military leave benefits." We need to preserve all substantive info; we can turn each sentence into list items or keep as prose. The instruction: use
- for any list of duties/requirements/benefits. So we should convert benefits into list items.
Pay: "For this U.S. based position, the expected pay range is USD 86,400 - USD 129,600 per year. This pay range includes base pay and short‑term incentives. The compensation range for this full‑time position applies to candidates located within the United States. Our pay ranges are determined by reviewing roles of similar responsibility and level. Within the pay range, individual pay is determined by several factors including performance, knowledge, job‑related skills, experience, and relevant education or training."
We need to include that as Pay section. Should we list as
- ? It's not a list but could be prose. The instruction: use
- for any list of duties/requirements/benefits. Pay is not a list; we can use
. But we could also break into list items for clarity but not required. We'll use
. Now we must remove boilerplate: EEO, legal, navigation, cookie, duplicated lines, application instructions. Also remove "Job Posting Compliance Form.* (External) English Company Boiler Plate:" and all that following. Also remove "If you believe this job posting is not compliant..." etc. Also remove "You must submit an online application..." etc. Also remove the company boilerplate about IMPACT etc. Also remove the Trust Charter etc. Also remove the Equal Opportunity Employer statement. Also remove the "€40 billion global revenue +9% organic growth 150 000+ employees in 100+ countries". Also remove "Schneider Electric aspires to be the most inclusive..." etc. All that is boilerplate. We must keep only substantive content: About the role, Responsibilities (What You'll Do), Requirements (Experience), Qualifications (Education), Skills (Technical Skills + Mindset), Benefits, Pay. We must not repeat job title as heading. So we will not include heading "Application
- for any list of duties/requirements/benefits. Pay is not a list; we can use
- ? It's not a list but could be prose. The instruction: use