Sr Project Manager - IT
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all bullet points from Essential Job Functions, Skills/Education..., Desired Experience, Total Compensation Package.
We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings (none present). Remove boilerplate: EEO etc. Remove duplicated lines, application instructions.
We need to output only HTML fragment.
Let's extract content.
Intro paragraph: "We are seeking a Senior Project Manager (Technical) to lead the delivery of complex, cross-functional technology projects that support our retail business spanning eCommerce, supply chain, store systems, infrastructure, and enterprise technology. As a Senior Project Manager, you will own projects end to end: partnering with engineering, product, business, and other Technology teams to define scope and delivery plans, manage schedules and budgets, coordinate resources and dependencies, mitigate risks and issues, and drive projects through implementation. You will operate in a fast-paced environment where you'll need technical fluency to engage engineering and Technology teams credibly, strong project leadership to bring structure to complex work, and the influence skills to align teams around shared project outcomes. This is an on-site position located in Springfield, MO. Remote work is not an option for this role."
That's About the role.
Essential Job Functions list (each bullet starts with a verb). We'll put under Responsibilities.
List items:
- Own end-to-end delivery of complex technology projects across Technology and business functions, from initiation through implementation and closure, ensuring delivery of intended business outcomes.
- Develop and maintain detailed project plans, including scope, schedules, milestones, resources, dependencies, budgets, and success criteria, using the methodology best suited to the work.
- Drive cross-functional execution across engineering, infrastructure, QA, security, data, architecture, and business teams, keeping teams aligned on priorities, deliverables, and commitments.
- Proactively identify, track, and mitigate project risks, issues, and dependencies; escalate with clarity and drive issues toward resolution.
- Engage with Technology teams to understand how architecture, integrations, networking, hardware, infrastructure, security, and other technical considerations affect project delivery.
- Coordinate owning and executing teams to ensure cross-team resource needs, deliverables, and dependencies are identified and incorporated into project plans.
- Establish and report project health metrics and provide clear, concise written and verbal status communications to stakeholders and leadership.
- Develop and manage project budgets, monitor actuals and forecasts against plan, and communicate financial status and impacts.
- Facilitate project meetings and working sessions, including planning, cross-team coordination, risk/issue resolution, decision-making, and project governance forums.
- Partner with Technology and business stakeholders to adapt project plans when priorities, requirements, or constraints change while maintaining focus on intended outcomes.
- Coordinate with QA and delivery teams to ensure test strategy, release readiness, implementation planning, and acceptance criteria are incorporated into the project plan.
- Coordinate third-party vendor participation, including deliverables, timelines, dependencies, risks, issues, and resolution of blockers.
- Drive technical and operational readiness by ensuring architecture, environments, security, testing, observability, implementation, and production support needs are identified and completed before key milestones.
- Coordinate projects through architecture and technical governance reviews, ensuring required reviews and approvals are incorporated into the delivery plan.
- Apply Agile, Waterfall, hybrid, or other delivery approaches based on the characteristics and needs of the project, focusing on outcomes over process.
- Support portfolio planning through project estimation, scheduling, resource planning, financial planning, and identification of cross-project dependencies.
- Contribute to improving project management standards, practices, and processes across the Technology organization.
- Mentor Project Managers and project team members and share project management best practices.
Now Skills/Education/Knowledge/Experience/Abilities Required: list.
We need to decide sections: Could have Requirements (education/experience) and Skills (technical). But we can combine into one Requirements section with sublists? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple headings. We need to decide what content goes where.
We have:
- Bachelor's degree in any field, or equivalent practical experience; a degree in Computer Science, Engineering, Information Systems, or a related technical discipline is a plus.
- 5+ years of project management experience leading complex, cross-functional technology projects.
- Demonstrated experience independently managing large or complex technology projects from initiation through implementation.
- Experience delivering projects using multiple methodologies, including Agile (Scrum, Kanban) and Waterfall/hybrid approaches.
- Working knowledge of software application development concepts and the software development lifecycle.
- Working knowledge of information technology concepts, including integrations, networking, hardware, infrastructure, and security.
- Familiarity with quality assurance concepts and practices, including testing, release management, and production readiness.
- Experience managing project risks, issues, dependencies, and stakeholder escalations across multiple Technology teams.
- Experience coordinating technical governance, engineering readiness, operational readiness, and vendor activities as part of project delivery.
- Experience developing and managing project schedules, resource plans, budgets, forecasts, and financial reporting.
- Proficiency with project management tools such as Jira, Confluence, Smartsheet, Azure DevOps, or similar.
- Excellent written and verbal communication skills, with the ability to communicate effectively with technical and non-technical audiences and leadership.
- Strong facilitation, relationship-building, problem-solving, and decision-making skills.
- Demonstrated ability to lead through influence and drive accountability across teams without direct authority.
- Proven track record of bringing structure to complex work and successfully delivering technology projects
Then Desired Experience (bullet list):
- Desired Experience in retail store operations, eCommerce, omnichannel, supply chain, infrastructure, data, or enterprise technology.
- Experience managing projects involving multiple Technology disciplines and significant cross-team dependencies.
- Experience with scaled delivery frameworks and practices such as SAFe, DevOps, and ITIL.
- Experience supporting organizational change, process improvement, or Technology transformation initiatives.
- PMP, CSM, SAFe, or equivalent certification.
- Experience in the automotive aftermarket, auto parts, or retail industry.
We could treat the first block as Requirements/Qualifications, and the Desired Experience as Skills? Or maybe Skills section includes technical skills like tools, methodologies, etc. But we already have many skill-like items in the required list. Could split: Requirements: education, years experience, etc. Skills: technical knowledge, tools, communication, etc. Qualifications maybe similar.
Given we want few substantive sections, we could combine Required and Desired into a single "Requirements" section, but we need to preserve all detail. Could have two subheadings? Not allowed; only h3 headings. Could have separate sections: Requirements and Qualifications and Skills. But that may be many thin sections. However we have enough content for each.
Let's think: Requirements could be education and experience. Qualifications could be specific experiences like managing large projects, methodologies, risk management, etc. Skills could be tools, communication, facilitation, etc. Desired Experience could be separate but maybe we can incorporate into Qualifications as "Preferred" but we need to keep it.
Given the instruction: "Prefer a few substantive sections over many thin ones." So maybe we should have three sections: About the role, Responsibilities, Requirements (which includes education, experience, skills, desired). Benefits separate.
Thus we will have:
About the role
...
Responsibilities
...
Requirements
...
(including education, experience, skills, desired)
Benefits
...
We must not include Pay or Schedule.
Now we need to ensure we preserve all substantive information. Let's list all items for Requirements.
We'll combine:
- Bachelor's degree in any field, or equivalent practical experience; a degree in Computer Science, Engineering, Information Systems, or a related technical discipline is a plus.
- 5+ years of project management experience leading complex, cross-functional technology projects.
- Demonstrated experience independently managing large or complex technology projects from initiation through implementation.
- Experience delivering projects using multiple methodologies, including Agile (Scrum, Kanban) and Waterfall/hybrid approaches.
- Working knowledge of software application development concepts and the software development lifecycle.
- Working knowledge of information technology concepts, including integrations, networking, hardware, infrastructure, and security.
- Familiarity with quality assurance concepts and practices, including testing, release management, and production readiness.
- Experience managing project risks, issues, dependencies, and stakeholder escalations across multiple Technology teams.
- Experience coordinating technical governance, engineering readiness, operational readiness, and vendor activities as part of project delivery.
- Experience developing and managing project schedules, resource plans, budgets, forecasts, and financial reporting.
- Proficiency with project management tools such as Jira, Confluence, Smartsheet, Azure DevOps, or similar.
- Excellent written and verbal communication skills, with the ability to communicate effectively with technical and non-technical audiences and leadership.
- Strong facilitation, relationship-building, problem-solving, and decision-making skills.
- Demonstrated ability to
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all bullet points from Essential Job Functions, Skills/Education..., Desired Experience, Total Compensation Package. We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings (none present). Remove boilerplate: EEO etc. Remove duplicated lines, application instructions. We need to output only HTML fragment. Let's extract content. Intro paragraph: "We are seeking a Senior Project Manager (Technical) to lead the delivery of complex, cross-functional technology projects that support our retail business spanning eCommerce, supply chain, store systems, infrastructure, and enterprise technology. As a Senior Project Manager, you will own projects end to end: partnering with engineering, product, business, and other Technology teams to define scope and delivery plans, manage schedules and budgets, coordinate resources and dependencies, mitigate risks and issues, and drive projects through implementation. You will operate in a fast-paced environment where you'll need technical fluency to engage engineering and Technology teams credibly, strong project leadership to bring structure to complex work, and the influence skills to align teams around shared project outcomes. This is an on-site position located in Springfield, MO. Remote work is not an option for this role." That's About the role. Essential Job Functions list (each bullet starts with a verb). We'll put under Responsibilities. List items: - Own end-to-end delivery of complex technology projects across Technology and business functions, from initiation through implementation and closure, ensuring delivery of intended business outcomes. - Develop and maintain detailed project plans, including scope, schedules, milestones, resources, dependencies, budgets, and success criteria, using the methodology best suited to the work. - Drive cross-functional execution across engineering, infrastructure, QA, security, data, architecture, and business teams, keeping teams aligned on priorities, deliverables, and commitments. - Proactively identify, track, and mitigate project risks, issues, and dependencies; escalate with clarity and drive issues toward resolution. - Engage with Technology teams to understand how architecture, integrations, networking, hardware, infrastructure, security, and other technical considerations affect project delivery. - Coordinate owning and executing teams to ensure cross-team resource needs, deliverables, and dependencies are identified and incorporated into project plans. - Establish and report project health metrics and provide clear, concise written and verbal status communications to stakeholders and leadership. - Develop and manage project budgets, monitor actuals and forecasts against plan, and communicate financial status and impacts. - Facilitate project meetings and working sessions, including planning, cross-team coordination, risk/issue resolution, decision-making, and project governance forums. - Partner with Technology and business stakeholders to adapt project plans when priorities, requirements, or constraints change while maintaining focus on intended outcomes. - Coordinate with QA and delivery teams to ensure test strategy, release readiness, implementation planning, and acceptance criteria are incorporated into the project plan. - Coordinate third-party vendor participation, including deliverables, timelines, dependencies, risks, issues, and resolution of blockers. - Drive technical and operational readiness by ensuring architecture, environments, security, testing, observability, implementation, and production support needs are identified and completed before key milestones. - Coordinate projects through architecture and technical governance reviews, ensuring required reviews and approvals are incorporated into the delivery plan. - Apply Agile, Waterfall, hybrid, or other delivery approaches based on the characteristics and needs of the project, focusing on outcomes over process. - Support portfolio planning through project estimation, scheduling, resource planning, financial planning, and identification of cross-project dependencies. - Contribute to improving project management standards, practices, and processes across the Technology organization. - Mentor Project Managers and project team members and share project management best practices. Now Skills/Education/Knowledge/Experience/Abilities Required: list. We need to decide sections: Could have Requirements (education/experience) and Skills (technical). But we can combine into one Requirements section with sublists? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple headings. We need to decide what content goes where.
We have:
- Bachelor's degree in any field, or equivalent practical experience; a degree in Computer Science, Engineering, Information Systems, or a related technical discipline is a plus.
- 5+ years of project management experience leading complex, cross-functional technology projects.
- Demonstrated experience independently managing large or complex technology projects from initiation through implementation.
- Experience delivering projects using multiple methodologies, including Agile (Scrum, Kanban) and Waterfall/hybrid approaches.
- Working knowledge of software application development concepts and the software development lifecycle.
- Working knowledge of information technology concepts, including integrations, networking, hardware, infrastructure, and security.
- Familiarity with quality assurance concepts and practices, including testing, release management, and production readiness.
- Experience managing project risks, issues, dependencies, and stakeholder escalations across multiple Technology teams.
- Experience coordinating technical governance, engineering readiness, operational readiness, and vendor activities as part of project delivery.
- Experience developing and managing project schedules, resource plans, budgets, forecasts, and financial reporting.
- Proficiency with project management tools such as Jira, Confluence, Smartsheet, Azure DevOps, or similar.
- Excellent written and verbal communication skills, with the ability to communicate effectively with technical and non-technical audiences and leadership.
- Strong facilitation, relationship-building, problem-solving, and decision-making skills.
- Demonstrated ability to lead through influence and drive accountability across teams without direct authority.
- Proven track record of bringing structure to complex work and successfully delivering technology projects
Then Desired Experience (bullet list):
- Desired Experience in retail store operations, eCommerce, omnichannel, supply chain, infrastructure, data, or enterprise technology.
- Experience managing projects involving multiple Technology disciplines and significant cross-team dependencies.
- Experience with scaled delivery frameworks and practices such as SAFe, DevOps, and ITIL.
- Experience supporting organizational change, process improvement, or Technology transformation initiatives.
- PMP, CSM, SAFe, or equivalent certification.
- Experience in the automotive aftermarket, auto parts, or retail industry.
We could treat the first block as Requirements/Qualifications, and the Desired Experience as Skills? Or maybe Skills section includes technical skills like tools, methodologies, etc. But we already have many skill-like items in the required list. Could split: Requirements: education, years experience, etc. Skills: technical knowledge, tools, communication, etc. Qualifications maybe similar.
Given we want few substantive sections, we could combine Required and Desired into a single "Requirements" section, but we need to preserve all detail. Could have two subheadings? Not allowed; only h3 headings. Could have separate sections: Requirements and Qualifications and Skills. But that may be many thin sections. However we have enough content for each.
Let's think: Requirements could be education and experience. Qualifications could be specific experiences like managing large projects, methodologies, risk management, etc. Skills could be tools, communication, facilitation, etc. Desired Experience could be separate but maybe we can incorporate into Qualifications as "Preferred" but we need to keep it.
Given the instruction: "Prefer a few substantive sections over many thin ones." So maybe we should have three sections: About the role, Responsibilities, Requirements (which includes education, experience, skills, desired). Benefits separate.
Thus we will have:
About the role
...
Responsibilities
- ...
Requirements
- ...
Benefits
- ...