Power System Solution Architect

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, application instructions, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - Intro paragraph about Data Center industry transformation and role description: that could be "About the role". We'll put that in

. - "What will you do?" list of responsibilities: bullet list. - "What qualifications will make you successful?" list of qualifications: bullet list. - Then there is "Bring your architectural vision to a team that values innovation and excellence — apply today!" (application instruction) we should drop. - Then "At Schneider, we believe that every employee is a talent..." etc: that's about benefits and total rewards. We need to extract Benefits and Pay. - Pay: "For this U.S. based position, the expected pay range is USD 168,800 - USD 253,200 per year. This pay range includes base pay and short-term incentives." That's pay. - Benefits: list of benefits: medical, dental, vision, basic life insurance, Benefit Bucks, flexible work arrangements, paid family leaves, well-being programs, 12 holidays per year, 20 days of paid time off per year (pro-rated...), invest and plan future: base salary, short-term incentives, opportunities to own company shares, 401(k)+match. Grow skills: ongoing performance and development conversations, Senior Talent Program, global career opportunities, access to Schneider Career Hub, learning platforms like Coursera. Team up: project opportunities, smart ways to collaborate, recognition program, engagement survey, inclusive workplace. Support community: volunteer leave, programs through Schneider Electric Foundation, initiatives that support youth education, military leave benefits. We need to capture all that as Benefits section. - Schedule: maybe travel requirement: "Ability to travel approximately 40%, primarily within the U.S. and North America, with international travel as needed." That could be schedule? Not exactly schedule but maybe we can put under Schedule? The instruction says include Schedule section only if posting actually states them. Travel is not schedule but maybe we can treat as Schedule? However they said "Schedule" heading for schedule info like work hours, shift, etc. Travel is not schedule. Probably we should not create Schedule section because no explicit schedule (like full-time, hours). There's mention "full-time position". That's schedule: full-time. So we could include Schedule: Full-time. But they said only include if posting actually states them. It does state "full-time position". So we can include Schedule with Full-time. But also travel 40% could be considered under Schedule? Might be better to put under Benefits? Not really. Could add a separate "Travel" but not allowed headings. We could incorporate travel into Responsibilities or Requirements? Probably better to include under Requirements as "Ability to travel approximately 40%...". That is a qualification. So we can add that to Requirements list. Thus sections: - About the role: intro paragraph(s) describing role and context. - Responsibilities: bullet list from "What will you do?" (the list after that heading). Need to capture each bullet. - Requirements: bullet list from "What qualifications will make you successful?" plus travel ability. - Qualifications: maybe separate? The instruction says we can have both Requirements and Qualifications sections. But we need to avoid duplication. The posting lumps qualifications together. Could split: Requirements = mandatory experience/education; Qualifications = preferred skills, certifications, languages. But we need to follow instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have both Requirements and Qualifications. We need to decide what goes where. We have: Bachelor’s or Master’s degree in Electrical, Mechanical, Computer Science, Electronics Engineering, or a related discipline. 8+ years of technical experience within Data Centers, critical facilities, power systems, system engineering, product/system development, or solution architecture. 5+ years of customer-facing technical experience, with demonstrated ability to lead complex technical discussions and influence solutions. Proven experience developing Data Center architectures, reference designs, and technical workstreams. Strong knowledge of Data Center electrical infrastructure from grid to chip, including: MV/LV distribution and transformers, Backup generation, UPS/power conversion and battery systems, Power system protection, automation, and controls, IT-room power infrastructure, including PSUs, rack PDUs, busway, PDUs/RPPs, and racks. Experience with power system modeling and simulation tools such as ETAP, MATLAB, or equivalent tools. Understanding of AI infrastructure and high-density Data Center applications is strongly preferred. Strong analytical, problem-solving, project management, and decision-making capabilities. Demonstrated ability to simplify and communicate complex technical concepts to both technical and business audiences. Ability to collaborate and influence across a global, matrixed organization and build strong relationships with customers and technology partners. Innovative and entrepreneurial mindset with a strong customer and results orientation. System architecture methodology certification is a plus. Professional fluency in English required; additional languages are a plus. Ability to travel approximately 40%, primarily within the U.S. and North America, with international travel as needed. We could treat the first bullet points (degree, years experience) as Requirements. The rest as Qualifications or Skills. But we also have a Skills section possible. Let's allocate: - Requirements: degree, 8+ years experience, 5+ years customer-facing, proven experience developing DC architectures, strong knowledge of DC electrical infrastructure (list), experience with power system modeling tools. - Qualifications: understanding of AI infrastructure (strongly preferred), strong analytical/problem-solving/project management/decision-making, ability to simplify/communicate complex concepts, ability to collaborate/influence globally, innovative/entrepreneurial mindset, system architecture methodology certification (plus), professional fluency in English (required), additional languages (plus), ability to travel 40%. - Skills: maybe we could separate technical skills like power system modeling tools, but we already put that in Requirements. Could also have Skills for things like "Strong analytical, problem-solving, project management, and decision-making capabilities." but that's more ability. Might be okay to not have Skills section if content thin. But we have enough for Qualifications. We also have Benefits and Pay and Schedule. Now we need to strip boilerplate: EEO, legal, application instructions, etc. Also remove duplicated lines. Also remove the "If you believe this job posting is not compliant..." etc. Also remove the "Looking to make an IMPACT..." etc. Also remove the "€40 billion global revenue +9% organic growth 150 000+ employees in 100+ countries". Also remove the "You must submit an online application..." etc. Also remove the "Schneider Electric aspires to be the most inclusive..." etc. Also remove the "At Schneider Electric, we uphold the highest standards..." etc. Also remove the "Schneider Electric is an Equal Opportunity Employer..." etc. We must preserve all substantive information: that includes the description of Total Rewards benefits, pay range, etc. Also the "IMPACT values" maybe considered substantive? It's about culture; could be considered part of Benefits? Might be considered part of company culture but not explicitly benefits. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The IMPACT values section is not boilerplate; it's about culture and values. Might be considered substantive. However it's somewhat generic but still part of posting. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the IMPACT values description? It's about culture and values. It's not a standard heading like Benefits, but we could include it under Benefits? Not exactly. Could we add a section "Culture"? Not allowed headings list only those given. So we must fit into allowed headings. If we cannot fit, we might need to drop it because it's not covered by allowed headings. But we could incorporate into Benefits? Not really. Could incorporate into About the role? Might be okay to include a paragraph about culture in About the role. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings? It says use those for section headings. Likely we should only use those headings. So we need to map all content into those sections. Culture/values could go under About the role (maybe as a paragraph). Or we could omit if it's not essential? But it's substantive. I'd include a paragraph about IMPACT values in About the role. Now we need to output only HTML fragment, no /, no markdown. Let's craft:

About the role

The Data Center industry is undergoing significant transformation driven by AI infrastructure deployment, increasing power density, energy availability challenges, and growing sustainability expectations. These trends are creating new requirements for Data Center power architectures, technologies, and solutions. The Data Center Power System Solution Architect will play a key role in Schneider Electric’s Data Center of the Future innovation program, translating emerging industry trends and customer needs into future power system architectures and solutions. This highly technical and strategic role will engage customers, technology partners, industry organizations, and Schneider Electric teams to explore and qualify new architectures and technologies that address the evolving needs of Data Centers and AI infrastructure.

At Schneider Electric, we believe that our IMPACT values – Inclusion, Mastery, Purpose, Action, Curiosity, Teamwork – start with us. IMPACT is also your invitation to join Schneider Electric where you can contribute to turning sustainability ambition into actions, no matter what role you play. It is a call to connect your career with the ambition of achieving a more resilient, efficient, and sustainable world. We are looking for IMPACT Makers; exceptional people who turn sustainability ambitions into actions at the intersection of automation, electrification, and digitization. We celebrate IMPACT Makers and believe everyone has the potential to be one.

Then Responsibilities:

Responsibilities

• Translate Data Center and AI infrastructure trends into requirements for current and future power system architectures and solutions.
• Engage with customers, hyperscalers, technology partners, GPU/server manufacturers, and industry organizations to understand and qualify emerging use cases and technical requirements.
• Evaluate and benchmark power architecture options and develop application positioning, selection criteria, and technical recommendations.
• Develop power system models and technical specifications for new architectures and solutions, helping identify portfolio gaps and future development opportunities.
• Lead or contribute to exploration studies that evaluate new technologies, capabilities, and future electrical architectures.
• Position and communicate Schneider Electric’s technical expertise and differentiation through customer engagements and industry collaboration.
• Partner across Strategy, Innovation, Secure Power, Digital Energy, Power Products, Power Systems, and other technical teams to align priorities and advance strategic projects.
• Develop technical playbooks and support training for pre-sales and technical communities.
• Contribute to Schneider Electric’s technical thought leadership through white papers, industry presentations, and technical discussions.

Requirements:

Requirements

• Bachelor’s or Master’s degree in Electrical, Mechanical, Computer Science, Electronics Engineering, or a related discipline.
• 8+ years of technical experience within Data Centers, critical facilities, power systems, system engineering, product/system development, or solution architecture.
• 5+ years of customer-facing technical experience, with demonstrated ability to lead complex technical discussions and influence solutions.
• Proven experience developing Data Center architectures, reference designs, and technical workstreams.
• Strong knowledge of Data Center electrical infrastructure from grid to chip, including: MV/LV distribution and transformers, Backup generation, UPS/power conversion and battery systems,