Program Manager - AI Transformation & Workforce Strategy
Schneider Electric · Boston, MA · 1 mo ago
HybridFull-time
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 need to extract content from posting.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate.
We need to preserve all substantive info.
Let's parse.
The posting includes:
- Role intent paragraph: "Be the transformation engine that helps Schneider Electric anticipate, adopt and scale agentic AI across software product engineering work, skills, teams, economics and operating models."
- About Schneider Electric And The Transformation: paragraphs about Schneider Electric, transformation.
- The opportunity: description of role.
- Key responsibilities: bullet list (actually sentences separated by line breaks). We need to turn into
- .
- Success after 12 months: measurement & value, enablement & adoption, governance & operating model. Could be part of responsibilities or separate? Might be considered as "Success metrics". Could be part of responsibilities or maybe "Requirements"? Not exactly. Might be considered as "Success criteria". Could be part of "Responsibilities" or separate "Success metrics". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
"About the role" likely includes role intent and about Schneider Electric and the opportunity.
"Responsibilities" includes key responsibilities bullet list.
"Requirements" maybe includes required qualifications and experience.
"Qualifications" maybe includes preferred experience? Actually they have "Required Qualifications and experience" and "Preferred Experience". Could treat Required as Requirements, Preferred as Qualifications? Or we could combine.
"Skills" maybe include leadership profile bullet list.
"Benefits": they have a paragraph about Total Rewards, benefits description, and pay range. So Benefits section can include description of benefits (medical, dental, vision, basic life insurance, Benefit Bucks, flexible work arrangements). Also maybe mention "Total Rewards package outlines all the benefits and support". We'll include that.
"Pay": they give expected pay range USD 168,800 - USD 253,200 per year. Also mention includes base pay and short-term incentives. So Pay section.
"Schedule": maybe flexible work options mentioned: "Flexible work options designed to help you thrive both professionally and personally". Also "flexible work arrang" (cut off). So we can include Schedule: flexible work options.
We must not include sections with placeholder or vague like "commensurate with experience". Not present.
We must not repeat job title.
We must not include boilerplate like EEO etc. At end they have "At Schneider, we believe that every employee is a talent who deserves equal opportunities..." That's EEO boilerplate; we should remove.
Also remove "Bring your project leadership expertise to a team that's ready to welcome you — apply now!" That's application instruction; remove.
Also remove "Our Total Rewards is our way of saying: “We see you. We value you”." That's part of benefits but maybe keep? It's somewhat boilerplate but still substantive about benefits. We can keep but maybe it's okay. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Total Rewards description is not exactly boilerplate; it's describing benefits. We'll keep.
Now produce HTML.
Structure:
About the role
... content ...
Responsibilities
- ... each responsibility ...
Requirements
... required qualifications ...
Qualifications
... preferred experience ...
Skills
- ... leadership profile bullets ...
Benefits
... benefits description ...
Pay
... pay range ...
Schedule
... flexible work options ...
We need to ensure we don't include empty sections. Now extract precise text. About the role: combine role intent, about Schneider Electric And The Transformation, The opportunity. Let's craft a concise paragraph preserving all substantive info. Role intent: "Be the transformation engine that helps Schneider Electric anticipate, adopt and scale agentic AI across software product engineering work, skills, teams, economics and operating models." About Schneider Electric And The Transformation: "Schneider Electric is accelerating the transformation of Energy Management through software, services, digital capabilities and AI-powered innovation. Within Energy Management, the Software & Services Division brings together a large global software product engineering population and plays a central role in shaping the next generation of connected, intelligent and software-defined offers. Generative AI and agentic AI are now reshaping how software is designed, developed, tested, secured, operated and continuously improved. The opportunity is broader than individual productivity: it requires rethinking software product engineering workflows, team composition, skills, career paths, governance, economics and value realization. To address this strategic shift, Schneider Electric is launching a transversal program hosted in the Software & Services Division, with a mandate to understand and anticipate the impact of agentic AI on software product engineering jobs and ways of working across Energy Management. The program will be supported by BCG and sponsored by the Software & Services CTO leadership." The opportunity: "We are seeking a strategic and execution-oriented transformation leader to establish and drive Schneider Electric's AI Transformation and Workforce Strategy agenda for software product engineering. This role will act as the central orchestrator of a multi-year transformation across technology, people, operating model and value realization. The successful candidate will work closely with CTOs, engineering leaders, product leaders, HR, Schneider Digital, Finance and external partners (consultants) to move the organization from AI-assisted development toward AI-enabled and agentic software product delivery. The role requires the ability to connect technology strategy with workforce transformation: understanding how software product engineering work changes, how teams evolve, which capabilities need to be built, what value is created, and how adoption can be scaled sustainably across a diverse global software product engineering population." Combine into a paragraph. Now Responsibilities: list each bullet from "Key responsibilities". They are sentences separated by line breaks. Let's extract: - Define the future of AI-powered software product development lifecycle at Schneider Electric (inputs from EM CTO, S&S CTO, Strategy teams) - Contribute to develop and operationalize the vision, ambition and roadmap for AI-powered software product engineering across Energy Management. - Assess how Generative AI and agentic AI will reshape software product engineering work, team structures, governance, decision rights and workforce requirements. - Translate external technology trends and benchmarks into pragmatic transformation choices for Schneider Electric. - Support executive recommendations on future software product engineering operating models, including maturity stages from AI-assisted development to agentic and autonomous delivery models. - Orchestrate the workforce transformation - Map the baseline of software product engineering roles, skills, capabilities, personas and team structures. - Identify roles and activities that will be augmented, recombined, created or significantly redesigned as AI adoption matures. - Partner with leaders and HR to build workforce scenarios, talent implications and capability development plans. - Define upskilling and reskilling pathways for software product engineers, architects, technical leads, engineering managers and product roles, while leveraging the internal resources (Schneider Digital, Digital Academy) - Anticipate impacts on career paths, recruiting needs, talent segmentation and future workforce planning. - Identify & empower AI champions in current teams to become trainers of next enablement waves - Accelerate AI adoption across software product engineering teams - Design and execute adoption programs that move beyond tool access and training to sustained changes in software product engineering behaviors and workflows. - Lead pilot teams, adoption sprints and scaling approaches, including squad-by-squad activation where relevant. - Create repeatable playbooks for AI adoption, maturity progression, leadership activation and local change networks. - Build a clear change narrative by persona, including “what is in it for me” for software engineers, product managers, software product engineering leaders and HR stakeholders, leveraging company/EM position papers and narrative. - Ensure adoption efforts measure depth and breadth of usage, not only license activation or superficial tool engagement. - Drive value realization and transformation economics - Define and operate a robust measurement framework covering adoption, productivity, quality, developer experience, workforce impact, cost and business value. - Track AI consumption economics, including token usage, tool spend, productivity benefits and return on investment. - Build executive dashboards and governance routines to steer decisions, funding allocation and scaling priorities. - Translate pilot outcomes into value cases, investment recommendations and scale-up roadmaps. - Ensure productivity improvement is balanced with software quality, security, reliability, developer experience and ethical AI guardrails. - Shape the future software product engineering operating model - Assess how team composition, squad structures and software product engineering practices evolve as AI agents absorb more execution work. - Define future collaboration models between software engineers, product managers, architects, testers, AI agents and platform/tooling teams. - Support the design of human-in-the-loop and human-over-the-loop models, including escalation, review and accountability principles. - Partner with software product engineering leadership to ensure the transformation improves speed, simplicity, predictability and strategic value creation. - Lead transformation governance and partner orchestration - Establish and operate the transformation office, governance model, steering committee cadence and reporting drumbeat. - Coordinate workstreams across Software Engineering, Product, HR, Finance, Schneider Digital, AI platform teams and external partners. - Manage the day-to-day interaction with BCG and ensure consulting support translates into Schneider Electric-owned capabilities and outcomes. - Prepare executive decision materials, strategic recommendations, progress reviews and communication packages for senior leadership. - Act as trusted advisor to the CTO leading the transversal effort and to the executive sponsor. We need to flatten into- items. Could keep sub-bullets as separate
- but maintain hierarchy? Probably just list each as separate
- . We'll keep each bullet as
- . Might be long but okay.
Now Requirements: "Required Qualifications and experience" paragraph:
"10+ years of experience in technology transformation, software engineering, management consulting, digital transformation, strategy, product/engineering operations or related fields.
Proven track record leading complex, cross-functional transformation programs in a global environment.
Strong understanding of software product engineering organizations, SDLC, Agile/DevOps practices, developer productivity and software product engineering operating models.
Ability to engage credibly with CTOs, senior engineering leaders, product leaders, HR leaders and external partners.
Excellent analytical, problem-solving, synthesis and executive communication skills.
Demonstrated ability to translate strategic ambition into practical roadmaps, governance, metrics and measurable outcomes."
We'll put as
with line breaks? Could be
- but spec says use
- for any list of duties/requirements/benefits. So Requirements is a list of requirements; we should use
- . Similarly Qualifications (preferred) also list.
Thus Requirements:
- each bullet.
Now Qualifications (Preferred Experience): bullet list:
"Preferred Experience in a leading strategy consulting firm, technology company, software business, platform organization or CTO office.
Exposure to Generative AI, agentic AI, developer tools, AI-enabled SDLC, developer experience or engineering productivity initiatives.
Experience with workforce transformation, organization design, capability building, change management or future-of-work programs.
Experience building business cases and value measurement frameworks for technology-enabled transformations."
We'll put as
- . Now Skills: Leadership profile bullet list: "Strong systems thinker able to connect technology, organization, economics and workforce implications. Credible with both technical and business audiences, from software engineers to executive committees. Highly structured, analytical and outcome-driven, with strong program execution discipline. Comfortable operating in ambiguity, rapid technological change and decentralized environments. Able to influence without direct authority and mobilize senior stakeholders around a shared transformation agenda. Passionate about shaping the future of software product engineering work in the age
- each bullet.
Now Qualifications (Preferred Experience): bullet list:
"Preferred Experience in a leading strategy consulting firm, technology company, software business, platform organization or CTO office.
Exposure to Generative AI, agentic AI, developer tools, AI-enabled SDLC, developer experience or engineering productivity initiatives.
Experience with workforce transformation, organization design, capability building, change management or future-of-work programs.
Experience building business cases and value measurement frameworks for technology-enabled transformations."
We'll put as
- . Similarly Qualifications (preferred) also list.
Thus Requirements:
- for any list of duties/requirements/benefits. So Requirements is a list of requirements; we should use