Operational Project Support

We need to output HTML fragment with sections: headings

for each section present: About the role? The posting starts with description: "Schneider Electric has an exciting opportunity for an Operational Project Support professional supporting our Secure Power Division. This role provides operational and transaction support throughout the project lifecycle..." That's about the role. Then "What Will You Do?" is responsibilities. Then "What Skills and Capabilities Will Make You Successful?" is skills. Then "Experience And Qualifications" is qualifications. Then "Technical Skills" maybe part of qualifications or separate? Could be part of Skills. But we can treat as part of Skills or separate heading "Technical Skills". However rule: include a section ONLY when posting has real, specific content for it. There is content for Technical Skills. So we can have a heading "Technical Skills". Then "What's in it for me?" includes benefits and maybe pay? Actually after that there is pay range and benefits. So we need sections: Benefits, Pay, Schedule? Schedule not mentioned. So we should not create Schedule. Benefits: we have description of Total Rewards package. Pay: we have pay range. So include Pay and Benefits sections. Also maybe "About the role" as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings. We need to map content. - About the role: first paragraph(s) describing role. - Responsibilities: "What Will You Do?" bullet list. - Skills: "What Skills and Capabilities Will Make You Successful?" plus maybe Technical Skills? Could combine but better separate: Skills heading for soft skills, Technical Skills heading for technical. But they said we can use Skills heading; we could include both under Skills. However they gave example list includes Skills, Benefits, Pay, Schedule. They didn't list Technical Skills separately. But we can still include a heading Technical Skills if content exists. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. So we can add Technical Skills as heading if appropriate. - Qualifications: "Experience And Qualifications" plus maybe education etc. - Benefits: description of Total Rewards. - Pay: pay range. We must not include boilerplate like EEO, application instructions, etc. Remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to preserve all substantive information. So we need to keep details like managing project-support requests, shared inboxes, etc. Also details about coordinating invoicing, etc. Also details about skills, qualifications, technical skills, benefits, pay. We must not repeat the job title as a heading. The job title is "Operational Project Support". Not to be used as heading. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

About the role

Schneider Electric has an exciting opportunity for an Operational Project Support professional supporting our Secure Power Division. This role provides operational and transaction support throughout the project lifecycle. Working with Project Managers, Project Controllers, and cross-functional teams, the position coordinates project requests, maintains accurate records, resolves exceptions, and supports efficient project execution. Project and financial decision authority remains with designated Project Managers, Project Controllers, and approvers.

Responsibilities

• Manage project-support requests, shared inboxes, and work queues; prioritize activities, monitor aging, and report on service levels and unresolved items.
• Validate project and transaction information, maintain accurate system records, and ensure required approvals and supporting documentation are complete.
• Coordinate customer invoicing and payment applications, including AIA documentation and customer-specific submission, tax, lien-waiver, and formatting requirements.
• Support purchase orders, vendor commitments, receiving, and invoice exceptions in coordination with project teams and supporting functions.
• Identify incomplete, inconsistent, duplicate, blocked, or overdue transactions and coordinate resolution or escalation.
• Support project closeout by confirming final billing, clearing open commitments, resolving aged items, and organizing project records.
• Maintain standard work and identify opportunities to improve controls, automate repetitive activities, and reduce errors, turnaround time, and backlog.

Skills

• Strong analytical thinking, sound judgment, attention to detail, and practical problem‑solving skills.
• Excellent organization and prioritization skills, with the ability to manage competing deadlines and high transaction volumes.
• Ability to identify exceptions, take appropriate action, and communicate escalations clearly.
• Strong digital literacy and an operational mindset focused on controls, service levels, and continuous improvement.
• Clear, professional communication and reliable follow‑through with internal teams, customers, and vendors.

Technical Skills

• Proficiency with Microsoft Office, including Excel, Outlook, Teams, and SharePoint.
• Experience with Microsoft Dynamics or a comparable business system, along with reporting, workflow, data‑management, or low‑code automation tools, is preferred.

Qualifications

• Bachelor’s degree in Business Administration, Finance, Accounting, a related field, or equivalent related experience.
• Two or more years of experience in project administration, billing, order management, financial operations, shared services, or a related support role.
• Experience with project invoicing, construction payment applications, purchase orders, customer or vendor documentation, and transaction or workflow management.
• Knowledge of project lifecycles and operational handoffs across booking, purchasing, receiving, billing, collections, and closeout; construction or other project‑based industry experience is preferred.
• Experience applying documentation controls, maintaining standard work, or supporting workflow improvement and automation is preferred.
• Applicants must be authorized to work in the United States on a full‑time, ongoing basis. The company does not provide immigration sponsorship now or in the future.

Pay

For this U.S. based position, the expected pay range is USD 68,000 - USD 102,000 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. Within the pay range, individual pay is determined by several factors including performance, knowledge, job‑related skills, experience, and relevant education or training.

Benefits

Schneider Electric’s Total Rewards package includes: 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. It also provides competitive pay and programs including base salary, incentives, company share ownership, and 401(k) with match; supports development through performance discussions, global opportunities, the Schneider Career Hub, and learning platforms like Coursera; encourages collaboration, recognition, sharing your voice, and an inclusive workplace; and makes a difference through volunteer leave, programs with the Schneider Electric Foundation, youth education initiatives, and military leave benefits.

We must ensure we didn't include any boilerplate like "If you believe this job posting is not compliant..." etc. Also removed "Ready to launch your career..." etc. Also removed "At Schneider, we believe that every employee is a talent..." etc. Also removed "Looking to make an IMPACT..." etc. Also removed the Euro revenue line etc. Also removed "You must submit an online application..." etc. Also removed EEO statements etc. Check that we kept all substantive info: The description about role, responsibilities, skills, technical skills, qualifications, pay, benefits. Did we miss any details like "Diverse project portfolio that accelerates your skills and career development", "Collaborative culture with access to mentorship and learning opportunities", "Meaningful work that directly impacts customer success and satisfaction", "Clear pathways for advancement within project management and operations". Those are under "What's in it for me?" which we might consider as part of Benefits or maybe a separate section like "What's in it for me?" but we already captured benefits. Those statements are more about career development etc. They could be considered part of Benefits or maybe a separate "What's in it for me?" but we didn't include a heading for that. The instruction says include a section ONLY when posting has real, specific content for it. There is content under "What's in it for me?" that is not covered elsewhere. Should we create a section like "What's in it for me?" or incorporate into Benefits? The example headings list includes Benefits, Pay, Schedule. Not "What's in it for me?" but we could treat those as part of Benefits. However the statements about diverse project portfolio, collaborative culture, meaningful work, clear pathways for advancement are more about career development and culture, which could be considered part of Benefits or maybe a separate "Career Development" section. But we don't have a heading for that in examples. However we could include a heading "What's in it for me?" as it's a specific section heading in the posting. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to. So we can use "What's in it for me?" as heading if we want. But we already have Benefits covering many of those points. However the "What's in it for me?" includes items like "Diverse project portfolio that accelerates your skills and career development", "Collaborative culture with access to mentorship and learning opportunities", "Meaningful work that directly impacts customer success and satisfaction", "Clear pathways for advancement within project management and operations". Those are not strictly benefits but could be considered part of Benefits or maybe a separate "Career Development". Since we have Benefits heading already, we could incorporate those statements into Benefits paragraph. That would preserve all substantive info. Let's add them to Benefits paragraph. Thus Benefits paragraph: include all those points. Let's rewrite Benefits paragraph to include: - Diverse project portfolio that accelerates your skills and career development - Collaborative culture with access to mentorship and learning opportunities - Meaningful work that directly impacts customer success and satisfaction - Clear pathways for advancement within project management and operations - Plus the Total Rewards details. We'll combine. Now ensure we didn't include any boilerplate like "Our Total Rewards is our way of saying: “We see you. We value you”." That's substantive? It's part of benefits description; we can keep it but it's somewhat fluff. However it's part of the posting; we should preserve all substantive information. It's not boilerplate like EEO; it's part of the benefits description. We can keep it. But we need to avoid duplication. We'll include a concise paragraph. Let's craft final HTML. Check for any leftover boilerplate: we removed lines about "If you believe this job posting is not compliant..." etc. Also removed "Looking to make an IMPACT..." etc. Also removed "Schneider Electric is an Equal Opportunity Employer..." etc. Also removed "You must submit an online application..." etc. Also removed "This position will be posted until filled." etc. Also removed the Euro revenue line etc. Also removed "At Schneider, we believe that every employee is a talent..." etc. Also removed "Our Total Rewards is our way of saying: “We see you. We value you”." Actually that is part of the benefits description; we could keep it but it's somewhat marketing. It's not boilerplate legal