Technical Program Manager - Client Delivery
for each section that has content. Use - for lists,
for prose. No job title heading. No Job ID etc. Remove boilerplate: EEO, legal, etc. Also remove navigation, cookie, etc. Keep substantive info: responsibilities, required skills & experience, success metrics, about the company, benefits (they listed benefits). Also maybe "Program Strategy & Reporting" is part of responsibilities. The posting includes sections: Responsibilities (with sub-bullets), Required Skills & Experience, Success Metrics, About The Company, Benefits (list). Also maybe "Program Delivery & Execution" etc are subheadings inside responsibilities; but we only need to output sections for major headings: Responsibilities, Required Skills & Experience, Success Metrics, About The Company, Benefits. Possibly also "Program Strategy & Reporting" is under responsibilities; we can keep as part of responsibilities list.
We must not create sections with filler like "Pay" or "Schedule" because not specified. Travel mentioned: up to 10% travel. That's a detail; could be included in Responsibilities or maybe a separate section? Not required to create a section unless content. Could add a
under Responsibilities about travel. But better to keep within Responsibilities prose.
We must preserve all substantive info; not invent or summarize away detail. So we need to include all bullet points.
Let's extract responsibilities bullet points:
From text:
Responsibilities
Program Delivery & Execution:
- Lead the end-to-end execution of client projects, ensuring they meet scope, schedule, and budget requirements.
- Manage risks, dependencies, milestones, and deliverables across projects.
- Oversee the delivery of client-facing technical solutions, ensuring they are aligned with business objectives and client needs.
Cross-Functional Alignment & Collaboration
- Align product requirements and technical architecture into integrated project plans, ensuring smooth collaboration across engineering, product, and business teams.
- Facilitate communication between technical teams and client stakeholders, ensuring clarity and shared understanding of project goals, timelines, and deliverables.
- Promote a culture of ownership, accountability, and collaboration across all teams involved in the program.
Technical Oversight & Leadership
- Provide leadership to technical project managers and cross-functional teams, driving program outcomes and ensuring technical excellence.
- Maintain oversight of quality standards, ensuring adherence to SDLC processes, engineering best practices, and quality checkpoints.
- Drive root cause analysis for defects and lead corrective actions to prevent future issues.
Client Engagement & Satisfaction
- Engage directly with clients to define project scope, gather requirements, and set expectations.
- Ensure regular and transparent communication with clients regarding project progress, risks, and outcomes.
- Proactively address client concerns and deliver solutions that exceed client expectations.
Process Improvement & Tools
- Continuously refine project management processes, tools, and methodologies to improve efficiency and effectiveness.
- Ensure consistent use of project management tools to track progress, manage risks, and maintain quality throughout the project lifecycle.
Program Strategy & Reporting
- Define and track key performance indicators (KPIs) to measure the success of programs.
- Provide executive-level status updates, highlighting progress, risks, and mitigation strategies.
- Lead retrospective reviews and promote a culture of continuous improvement across teams.
That's responsibilities.
Required Skills & Experience:
- Bachelor’s degree in a technical field or equivalent combination of education and experience.
- 12+ years of experience in program and project management, with at least 7 years of experience managing client-facing technical solutions.
- Proven experience in retail technology, Point of Sale (POS) systems, or custom software delivery.
- Technical expertise in system architecture, software development practices, and an understanding of embedded systems, AI, or other relevant technologies.
- PMP, SAFe, Scrum, or similar certifications or demonstrated plan to achieve one or more.
- Proficiency in Jira, Confluence, MS Project, Smartsheet, and other project management tools.
- Expertise in managing complex, multi-team projects with a focus on both technical execution and client satisfaction.
- Strong interpersonal skills with the ability to foster collaboration and drive consensus across cross-functional teams.
- Customer-facing experience with proven ability to translate client requirements into executable plans.
- Results-driven, with a focus on delivering high-quality solutions within scope, time, and budget.
Success Metrics:
- Effective program delivery, with adherence to key milestones and client satisfaction.
- Achievement of KPIs related to program success, including delivery timelines, budget adherence, and quality outcomes.
- Continuous improvement in team processes, leading to enhanced efficiency, fewer defects, and faster delivery times.
About The Company:
Paragraph: Toshiba Global Commerce Solutions is a dynamic billion-dollar global company based in Research Triangle Park, NC, providing retail store solutions to your favorite brands. Have you ever been in a hurry and made use of the self-checkout at Lowe’s Foods, earned fuel rewards at Kroger, or just paid for purchases at retailers such as Walmart, Michaels, Carrefour, The Gap, Calvin Klein, Boots, Cencosud, BJ’s, or Costco? These are just a few examples of our in-store solutions and impressive customer base that made us the world's installed market share leader. The nature of retail is changing quickly, so if you share our 'Together Commerce' vision of a seamless two-way, participatory shopping experience, let’s get together to drive the new economy.
Benefits:
- Group health coverage (medical, dental, & vision)
- Employee Assistance Programs
- Pre-tax spending accounts
- 401(k) plan (with company match)
- Company provided life insurance
- Pet Insurance
- Employee discounts
- Generous paid holiday schedule, paid vacation & sick/personal days
We should not include EEO etc.
Now produce HTML: Use
for each section heading. Inside each, use - for lists,
for prose.
For Responsibilities, we have subheadings inside? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not create subheadings inside responsibilities; just list all responsibilities as a list. Could we keep the subheadings as part of list items? Probably better to keep as list items; we could include the subheading text as part of the item, but that may lose structure. However we must preserve all substantive information; we can keep the subheadings as part of list items (like "Program Delivery & Execution: Lead the end-to-end execution...").
Thus responsibilities list items each start with the subheading.
Similarly for Required Skills & Experience: list.
Success Metrics: list.
About The Company: paragraph(s). Could be multiple
but we can combine into one
with line breaks? Better to keep as one
containing the whole paragraph.
Benefits: list.
We must not repeat job title. No extra sections.
Let's craft HTML.
Check for any other substantive info: up to 10% travel mentioned earlier in description before responsibilities. That's a detail not captured elsewhere. Should we include it? It's under the initial description: "This role requires extensive customer interaction and up to 10% travel." That's substantive. We should include it somewhere, maybe in Responsibilities as a bullet or in a
under Responsibilities. Since we have a Responsibilities section, we can add a bullet: "Requires extensive customer interaction and up to 10% travel." That preserves info.
Also mention "The TPgM is responsible for overseeing end-to-end delivery of complex retail solutions, ensuring alignment between business requirements, product strategy, and technical execution. This role drives cross-functional coordination, mitigates risks, and ensures that projects stay within scope, budget, and timeline while maintaining high-quality standards across all phases of development." That's also substantive description of role; could be included as a introductory paragraph under Responsibilities or as a separate section like "About the role". But we are not to create extra sections unless needed; we could add a
before the list inside Responsibilities to capture that overview.
Thus Responsibilities section:
overview
then - ... bullets.
Similarly for Required Skills & Experience: maybe an introductory sentence? Not needed.
Now produce final HTML.
Be careful to not include any markdown fences.
Let's write:
Responsibilities
The TPgM is responsible for overseeing end-to-end delivery of complex retail solutions, ensuring alignment between business requirements, product strategy, and technical execution. This role drives cross-functional coordination, mitigates risks, and ensures that projects stay within scope, budget, and timeline while maintaining high-quality standards across all phases of development. The role requires extensive customer interaction and up to 10% travel.
- Program Delivery & Execution: Lead the end-to-end execution of client projects, ensuring they meet scope, schedule, and budget requirements.
- Program Delivery & Execution: Manage risks, dependencies, milestones, and deliverables across projects.
- Program Delivery & Execution: Oversee the delivery of client-facing technical solutions, ensuring they are aligned with business objectives and client needs.
- Cross-Functional Alignment & Collaboration: Align product requirements and technical architecture into integrated project plans, ensuring smooth collaboration across engineering, product, and business teams.
- Cross-Functional Alignment & Collaboration: Facilitate communication between technical teams and client stakeholders, ensuring clarity and shared understanding of project goals, timelines, and deliverables.
- Cross-Functional Alignment & Collaboration: Promote a culture of ownership, accountability, and collaboration across all teams involved in the program.
- Technical Oversight & Leadership: Provide leadership to technical project managers and cross-functional teams, driving program outcomes and ensuring technical excellence.
- Technical Oversight & Leadership: Maintain oversight of quality standards, ensuring adherence to SDLC processes, engineering best practices, and quality checkpoints.
- Technical Oversight & Leadership: Drive root cause analysis for defects and lead corrective actions to prevent future issues.
- Client Engagement & Satisfaction: Engage directly with clients to define project scope, gather requirements, and set expectations.
- Client Engagement & Satisfaction: Ensure regular and transparent communication with clients regarding project progress, risks, and outcomes.
- Client Engagement & Satisfaction: Proactively address client concerns and deliver solutions that exceed client expectations.
- Process Improvement & Tools: Continuously refine project management processes, tools, and methodologies to improve efficiency and effectiveness.
- Process Improvement & Tools: Ensure consistent use of project management tools to track progress, manage risks, and maintain quality throughout the project lifecycle.
- Program Strategy & Reporting: Define and track key performance indicators (KPIs) to measure the success of programs.
- Program Strategy & Reporting: Provide executive-level status updates, highlighting progress, risks, and mitigation strategies.
- Program Strategy & Reporting: Lead retrospective reviews and promote a culture of continuous improvement across teams.
Required Skills & Experience
- Bachelor’s degree in a technical field or equivalent combination of education and experience.
- 12+ years of experience in program and project management, with at least 7 years of experience managing client-facing technical solutions.
- Proven experience in retail technology, Point of Sale (POS) systems, or custom software delivery.
- Technical expertise in system architecture, software development practices, and an understanding of embedded systems, AI, or other relevant technologies.
- PMP, SAFe, Scrum, or similar certifications or demonstrated plan to achieve one or more.
- Proficiency in Jira, Confluence, MS Project, Smartsheet, and other project management tools.
- Expertise in managing complex, multi-team projects with a focus on both technical execution and client satisfaction.
- Strong interpersonal skills with the ability to foster collaboration and drive consensus across cross-functional teams.
- Customer-facing experience with proven ability to translate client requirements into executable plans.
- Results-driven, with a focus on delivering high
for prose. No job title heading. No Job ID etc. Remove boilerplate: EEO, legal, etc. Also remove navigation, cookie, etc. Keep substantive info: responsibilities, required skills & experience, success metrics, about the company, benefits (they listed benefits). Also maybe "Program Strategy & Reporting" is part of responsibilities. The posting includes sections: Responsibilities (with sub-bullets), Required Skills & Experience, Success Metrics, About The Company, Benefits (list). Also maybe "Program Delivery & Execution" etc are subheadings inside responsibilities; but we only need to output sections for major headings: Responsibilities, Required Skills & Experience, Success Metrics, About The Company, Benefits. Possibly also "Program Strategy & Reporting" is under responsibilities; we can keep as part of responsibilities list. We must not create sections with filler like "Pay" or "Schedule" because not specified. Travel mentioned: up to 10% travel. That's a detail; could be included in Responsibilities or maybe a separate section? Not required to create a section unless content. Could add a
under Responsibilities about travel. But better to keep within Responsibilities prose. We must preserve all substantive info; not invent or summarize away detail. So we need to include all bullet points. Let's extract responsibilities bullet points: From text: Responsibilities Program Delivery & Execution: - Lead the end-to-end execution of client projects, ensuring they meet scope, schedule, and budget requirements. - Manage risks, dependencies, milestones, and deliverables across projects. - Oversee the delivery of client-facing technical solutions, ensuring they are aligned with business objectives and client needs. Cross-Functional Alignment & Collaboration - Align product requirements and technical architecture into integrated project plans, ensuring smooth collaboration across engineering, product, and business teams. - Facilitate communication between technical teams and client stakeholders, ensuring clarity and shared understanding of project goals, timelines, and deliverables. - Promote a culture of ownership, accountability, and collaboration across all teams involved in the program. Technical Oversight & Leadership - Provide leadership to technical project managers and cross-functional teams, driving program outcomes and ensuring technical excellence. - Maintain oversight of quality standards, ensuring adherence to SDLC processes, engineering best practices, and quality checkpoints. - Drive root cause analysis for defects and lead corrective actions to prevent future issues. Client Engagement & Satisfaction - Engage directly with clients to define project scope, gather requirements, and set expectations. - Ensure regular and transparent communication with clients regarding project progress, risks, and outcomes. - Proactively address client concerns and deliver solutions that exceed client expectations. Process Improvement & Tools - Continuously refine project management processes, tools, and methodologies to improve efficiency and effectiveness. - Ensure consistent use of project management tools to track progress, manage risks, and maintain quality throughout the project lifecycle. Program Strategy & Reporting - Define and track key performance indicators (KPIs) to measure the success of programs. - Provide executive-level status updates, highlighting progress, risks, and mitigation strategies. - Lead retrospective reviews and promote a culture of continuous improvement across teams. That's responsibilities. Required Skills & Experience: - Bachelor’s degree in a technical field or equivalent combination of education and experience. - 12+ years of experience in program and project management, with at least 7 years of experience managing client-facing technical solutions. - Proven experience in retail technology, Point of Sale (POS) systems, or custom software delivery. - Technical expertise in system architecture, software development practices, and an understanding of embedded systems, AI, or other relevant technologies. - PMP, SAFe, Scrum, or similar certifications or demonstrated plan to achieve one or more. - Proficiency in Jira, Confluence, MS Project, Smartsheet, and other project management tools. - Expertise in managing complex, multi-team projects with a focus on both technical execution and client satisfaction. - Strong interpersonal skills with the ability to foster collaboration and drive consensus across cross-functional teams. - Customer-facing experience with proven ability to translate client requirements into executable plans. - Results-driven, with a focus on delivering high-quality solutions within scope, time, and budget. Success Metrics: - Effective program delivery, with adherence to key milestones and client satisfaction. - Achievement of KPIs related to program success, including delivery timelines, budget adherence, and quality outcomes. - Continuous improvement in team processes, leading to enhanced efficiency, fewer defects, and faster delivery times. About The Company: Paragraph: Toshiba Global Commerce Solutions is a dynamic billion-dollar global company based in Research Triangle Park, NC, providing retail store solutions to your favorite brands. Have you ever been in a hurry and made use of the self-checkout at Lowe’s Foods, earned fuel rewards at Kroger, or just paid for purchases at retailers such as Walmart, Michaels, Carrefour, The Gap, Calvin Klein, Boots, Cencosud, BJ’s, or Costco? These are just a few examples of our in-store solutions and impressive customer base that made us the world's installed market share leader. The nature of retail is changing quickly, so if you share our 'Together Commerce' vision of a seamless two-way, participatory shopping experience, let’s get together to drive the new economy. Benefits: - Group health coverage (medical, dental, & vision) - Employee Assistance Programs - Pre-tax spending accounts - 401(k) plan (with company match) - Company provided life insurance - Pet Insurance - Employee discounts - Generous paid holiday schedule, paid vacation & sick/personal days We should not include EEO etc. Now produce HTML: Use
for each section heading. Inside each, use - for lists,
for prose.
For Responsibilities, we have subheadings inside? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not create subheadings inside responsibilities; just list all responsibilities as a list. Could we keep the subheadings as part of list items? Probably better to keep as list items; we could include the subheading text as part of the item, but that may lose structure. However we must preserve all substantive information; we can keep the subheadings as part of list items (like "Program Delivery & Execution: Lead the end-to-end execution...").
Thus responsibilities list items each start with the subheading.
Similarly for Required Skills & Experience: list.
Success Metrics: list.
About The Company: paragraph(s). Could be multiple
but we can combine into one
with line breaks? Better to keep as one
containing the whole paragraph.
Benefits: list.
We must not repeat job title. No extra sections.
Let's craft HTML.
Check for any other substantive info: up to 10% travel mentioned earlier in description before responsibilities. That's a detail not captured elsewhere. Should we include it? It's under the initial description: "This role requires extensive customer interaction and up to 10% travel." That's substantive. We should include it somewhere, maybe in Responsibilities as a bullet or in a
under Responsibilities. Since we have a Responsibilities section, we can add a bullet: "Requires extensive customer interaction and up to 10% travel." That preserves info.
Also mention "The TPgM is responsible for overseeing end-to-end delivery of complex retail solutions, ensuring alignment between business requirements, product strategy, and technical execution. This role drives cross-functional coordination, mitigates risks, and ensures that projects stay within scope, budget, and timeline while maintaining high-quality standards across all phases of development." That's also substantive description of role; could be included as a introductory paragraph under Responsibilities or as a separate section like "About the role". But we are not to create extra sections unless needed; we could add a
before the list inside Responsibilities to capture that overview.
Thus Responsibilities section:
overview
then - ... bullets.
Similarly for Required Skills & Experience: maybe an introductory sentence? Not needed.
Now produce final HTML.
Be careful to not include any markdown fences.
Let's write:
Responsibilities
The TPgM is responsible for overseeing end-to-end delivery of complex retail solutions, ensuring alignment between business requirements, product strategy, and technical execution. This role drives cross-functional coordination, mitigates risks, and ensures that projects stay within scope, budget, and timeline while maintaining high-quality standards across all phases of development. The role requires extensive customer interaction and up to 10% travel.
- Program Delivery & Execution: Lead the end-to-end execution of client projects, ensuring they meet scope, schedule, and budget requirements.
- Program Delivery & Execution: Manage risks, dependencies, milestones, and deliverables across projects.
- Program Delivery & Execution: Oversee the delivery of client-facing technical solutions, ensuring they are aligned with business objectives and client needs.
- Cross-Functional Alignment & Collaboration: Align product requirements and technical architecture into integrated project plans, ensuring smooth collaboration across engineering, product, and business teams.
- Cross-Functional Alignment & Collaboration: Facilitate communication between technical teams and client stakeholders, ensuring clarity and shared understanding of project goals, timelines, and deliverables.
- Cross-Functional Alignment & Collaboration: Promote a culture of ownership, accountability, and collaboration across all teams involved in the program.
- Technical Oversight & Leadership: Provide leadership to technical project managers and cross-functional teams, driving program outcomes and ensuring technical excellence.
- Technical Oversight & Leadership: Maintain oversight of quality standards, ensuring adherence to SDLC processes, engineering best practices, and quality checkpoints.
- Technical Oversight & Leadership: Drive root cause analysis for defects and lead corrective actions to prevent future issues.
- Client Engagement & Satisfaction: Engage directly with clients to define project scope, gather requirements, and set expectations.
- Client Engagement & Satisfaction: Ensure regular and transparent communication with clients regarding project progress, risks, and outcomes.
- Client Engagement & Satisfaction: Proactively address client concerns and deliver solutions that exceed client expectations.
- Process Improvement & Tools: Continuously refine project management processes, tools, and methodologies to improve efficiency and effectiveness.
- Process Improvement & Tools: Ensure consistent use of project management tools to track progress, manage risks, and maintain quality throughout the project lifecycle.
- Program Strategy & Reporting: Define and track key performance indicators (KPIs) to measure the success of programs.
- Program Strategy & Reporting: Provide executive-level status updates, highlighting progress, risks, and mitigation strategies.
- Program Strategy & Reporting: Lead retrospective reviews and promote a culture of continuous improvement across teams.
Required Skills & Experience
- Bachelor’s degree in a technical field or equivalent combination of education and experience.
- 12+ years of experience in program and project management, with at least 7 years of experience managing client-facing technical solutions.
- Proven experience in retail technology, Point of Sale (POS) systems, or custom software delivery.
- Technical expertise in system architecture, software development practices, and an understanding of embedded systems, AI, or other relevant technologies.
- PMP, SAFe, Scrum, or similar certifications or demonstrated plan to achieve one or more.
- Proficiency in Jira, Confluence, MS Project, Smartsheet, and other project management tools.
- Expertise in managing complex, multi-team projects with a focus on both technical execution and client satisfaction.
- Strong interpersonal skills with the ability to foster collaboration and drive consensus across cross-functional teams.
- Customer-facing experience with proven ability to translate client requirements into executable plans.
- Results-driven, with a focus on delivering high
for prose. For Responsibilities, we have subheadings inside? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not create subheadings inside responsibilities; just list all responsibilities as a list. Could we keep the subheadings as part of list items? Probably better to keep as list items; we could include the subheading text as part of the item, but that may lose structure. However we must preserve all substantive information; we can keep the subheadings as part of list items (like "Program Delivery & Execution: Lead the end-to-end execution..."). Thus responsibilities list items each start with the subheading. Similarly for Required Skills & Experience: list. Success Metrics: list. About The Company: paragraph(s). Could be multiple
but we can combine into one
with line breaks? Better to keep as one
containing the whole paragraph. Benefits: list. We must not repeat job title. No extra sections. Let's craft HTML. Check for any other substantive info: up to 10% travel mentioned earlier in description before responsibilities. That's a detail not captured elsewhere. Should we include it? It's under the initial description: "This role requires extensive customer interaction and up to 10% travel." That's substantive. We should include it somewhere, maybe in Responsibilities as a bullet or in a
under Responsibilities. Since we have a Responsibilities section, we can add a bullet: "Requires extensive customer interaction and up to 10% travel." That preserves info. Also mention "The TPgM is responsible for overseeing end-to-end delivery of complex retail solutions, ensuring alignment between business requirements, product strategy, and technical execution. This role drives cross-functional coordination, mitigates risks, and ensures that projects stay within scope, budget, and timeline while maintaining high-quality standards across all phases of development." That's also substantive description of role; could be included as a introductory paragraph under Responsibilities or as a separate section like "About the role". But we are not to create extra sections unless needed; we could add a
before the list inside Responsibilities to capture that overview. Thus Responsibilities section:
overview
then- ... bullets.
Similarly for Required Skills & Experience: maybe an introductory sentence? Not needed.
Now produce final HTML.
Be careful to not include any markdown fences.
Let's write:
Responsibilities
The TPgM is responsible for overseeing end-to-end delivery of complex retail solutions, ensuring alignment between business requirements, product strategy, and technical execution. This role drives cross-functional coordination, mitigates risks, and ensures that projects stay within scope, budget, and timeline while maintaining high-quality standards across all phases of development. The role requires extensive customer interaction and up to 10% travel.
- Program Delivery & Execution: Lead the end-to-end execution of client projects, ensuring they meet scope, schedule, and budget requirements.
- Program Delivery & Execution: Manage risks, dependencies, milestones, and deliverables across projects.
- Program Delivery & Execution: Oversee the delivery of client-facing technical solutions, ensuring they are aligned with business objectives and client needs.
- Cross-Functional Alignment & Collaboration: Align product requirements and technical architecture into integrated project plans, ensuring smooth collaboration across engineering, product, and business teams.
- Cross-Functional Alignment & Collaboration: Facilitate communication between technical teams and client stakeholders, ensuring clarity and shared understanding of project goals, timelines, and deliverables.
- Cross-Functional Alignment & Collaboration: Promote a culture of ownership, accountability, and collaboration across all teams involved in the program.
- Technical Oversight & Leadership: Provide leadership to technical project managers and cross-functional teams, driving program outcomes and ensuring technical excellence.
- Technical Oversight & Leadership: Maintain oversight of quality standards, ensuring adherence to SDLC processes, engineering best practices, and quality checkpoints.
- Technical Oversight & Leadership: Drive root cause analysis for defects and lead corrective actions to prevent future issues.
- Client Engagement & Satisfaction: Engage directly with clients to define project scope, gather requirements, and set expectations.
- Client Engagement & Satisfaction: Ensure regular and transparent communication with clients regarding project progress, risks, and outcomes.
- Client Engagement & Satisfaction: Proactively address client concerns and deliver solutions that exceed client expectations.
- Process Improvement & Tools: Continuously refine project management processes, tools, and methodologies to improve efficiency and effectiveness.
- Process Improvement & Tools: Ensure consistent use of project management tools to track progress, manage risks, and maintain quality throughout the project lifecycle.
- Program Strategy & Reporting: Define and track key performance indicators (KPIs) to measure the success of programs.
- Program Strategy & Reporting: Provide executive-level status updates, highlighting progress, risks, and mitigation strategies.
- Program Strategy & Reporting: Lead retrospective reviews and promote a culture of continuous improvement across teams.
Required Skills & Experience
- Bachelor’s degree in a technical field or equivalent combination of education and experience.
- 12+ years of experience in program and project management, with at least 7 years of experience managing client-facing technical solutions.
- Proven experience in retail technology, Point of Sale (POS) systems, or custom software delivery.
- Technical expertise in system architecture, software development practices, and an understanding of embedded systems, AI, or other relevant technologies.
- PMP, SAFe, Scrum, or similar certifications or demonstrated plan to achieve one or more.
- Proficiency in Jira, Confluence, MS Project, Smartsheet, and other project management tools.
- Expertise in managing complex, multi-team projects with a focus on both technical execution and client satisfaction.
- Strong interpersonal skills with the ability to foster collaboration and drive consensus across cross-functional teams.
- Customer-facing experience with proven ability to translate client requirements into executable plans.
- Results-driven, with a focus on delivering high