Director, Supply Chain Strategy & Analytics
Pursuit Aerospace · Thomasville, GA · 1 mo ago
ManagementFull-time
We need to output HTML fragment with sections only when there is real specific content. Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content.
From posting:
- About Us: description of company. Could be "About the role"? Actually "About The Opportunity" is description of role. So we can put that under
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content.
From posting:
- About Us: description of company. Could be "About the role"? Actually "About The Opportunity" is description of role. So we can put that under About the role
with paragraphs.
- Responsibilities: list of bullet points.
- Required Qualifications: list.
- Preferred Qualifications: could be under Qualifications or Skills? The instruction: Use headings for sections like Qualifications, Skills, Benefits, Pay, Schedule. We have both Required and Preferred qualifications. Could combine under Qualifications
with subpoints? But we need to preserve all info. Could separate Required and Preferred as paragraphs under Qualifications? Or we could have Required Qualifications
and Preferred Qualifications
but those aren't in allowed headings list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings. We have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have no explicit Pay or Schedule info besides location remote and travel 25% (that's schedule? maybe schedule). There's also Working Conditions (sitting, lifting). That could be under Schedule? Not exactly. But we can include Schedule if there is info: location remote, travel 25% => schedule info. Also Working Conditions could be under Schedule? Might be better to put under Schedule: remote, travel 25%, occasional weekend/evening work, prolonged sitting, lift up to 15 lbs, PPE required. That seems schedule/working conditions.
Pay: no salary info given. So we should NOT include Pay section because no specific content.
Benefits: we have benefits paragraph.
Skills: we could put preferred qualifications like Excel, SQL, Python, Snowflake, GitHub, etc. Also cross-functional leadership etc. Could be under Skills.
Requirements: maybe we can put Required Qualifications under Requirements? But we also have Qualifications heading. Could separate: Requirements = mandatory (required). Qualifications = preferred? Or we could put Required under Requirements and Preferred under Qualifications. That seems logical.
Thus:
About the role
: paragraphs from About The Opportunity.
Responsibilities
: ul list of responsibilities.
Requirements
: ul list of Required Qualifications.
Qualifications
: ul list of Preferred Qualifications.
Skills
: maybe we could combine some skills from preferred qualifications? But we already have Qualifications. Could also put technical skills under Skills. But to avoid duplication, maybe we put technical skills under Skills and leadership etc under Qualifications? However we need to preserve all info; duplication is okay if we keep content but not repeat? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. We could split: Requirements = mandatory education/experience/authorization. Qualifications = preferred education/experience. Skills = technical skills (Excel, SQL, Python, Snowflake, GitHub, etc.) and soft skills (cross-functional leadership, communication, stakeholder-management, etc.). That seems reasonable.
Let's extract:
About The Opportunity paragraph(s):
"We are seeking a Director of Supply Chain Strategy & Analytics to join our integrated business planning team. This role will be responsible for the strategy, design, and some execution of our integrated supply chain planning including demand planning, supply planning, master production scheduling (MPS), and Sales, Inventory & Operations Planning (SIOP). This leader pairs deep planning expertise with advanced analytics and a transformation mindset to connect a historically siloed, spreadsheet/ERP hybrid supply chain into one synchronized, data-driven operating system. The Director of Supply Chain Strategy & Analytics will translate strategy and analytics into measurable results including lower inventory, higher on-time delivery, and a better customer experience. At the same time, the Director will build and scale the analytics and automation that make it happen. This is a hands-on leadership role for someone equally comfortable setting strategy, modeling data, building solutions (increasingly with AI), and bringing cross-functional teams along for the change."
That's the core.
Location: "This role will primarily be remote and will travel about 25% of the time." That's schedule/working conditions.
Responsibilities list:
- Design planning strategy & SIOP process and establish “one plan, one set of numbers” as the network-level operating standard, building on the planning strengths already present at each site
- Build and govern demand forecasting and demand sensing capabilities; improve forecast accuracy and reduce bias
- Define leading and lagging KPIs for SIOP, cascade KPIs across sites, programs, customers, build dashboard to track KPIs and drive performance improvement
- Develop data and analytical assets to provide inputs into the monthly and weekly process and accelerate ad-hoc analysis to engage with customers and suppliers
- Partner with cross-functional team to make decisions and drive actions that improve business outcomes
- Coach, develop, and grow the planning organization and analytics talent
Required Qualifications:
- Bachelor’s degree
- 4+ years of supply chain experience, including hands-on leadership across demand planning, supply planning, MPS, and SIOP
- 5+ years of building data and analytical assets such as forecasting models, supply chain analytical tools such as clear-to-build, inventory line of balance, inventory entitlement, and centralized data assets
- Must be authorized to work in the U.S. on a full-time basis without sponsorship now or in the future. The Company cannot offer employment to visa holders who require employer sponsorship in the future or cannot work now on a full-time basis.
- Must be able to perform work subject to ITAR/EAR regulations.
Preferred Qualifications:
- Aerospace and/or manufacturing experience
- Bachelor’s degree in Science, Technology, Engineering and Mathematics
- Experience across a range of ERP systems (e.g., Siteline, Visual, Epicor).
- 5+ years in Excel, SQL, and Python
- Demonstrated track record in leading successful transformation programs or working with cross functional team in transformation programs
- Proficiency in building data assets in Snowflake, running CI/CD via GitHub, developing analytical tools across multiple platforms and supporting data operations
- Excellent cross-functional leadership, communication, and stakeholder-management skills, with experience bringing teams together around a shared plan.
- Highly motivated and proactive, with the ability to manage multiple high-priority projects in a fast-paced environment
Working Conditions (maybe schedule):
- Must be able to have prolonged periods sitting at a desk and working on a computer.
- Must be able to frequently sit, stand and walk.
- Must be able to lift and carry up to 15 pounds.
- Personal protective equipment (e.g., safety glasses and safety shoes) is required on the shop floor
- Occasional weekend and evening work may be required to accommodate priorities, deadlines, and schedules.
Benefits:
- health and disability insurance, 401(k) match, flexible spending accounts, EAP, paid time off, and company-paid holidays. The specific programs and options available to an employee may vary depending on date of hire, schedule type, and the applicability of collective bargaining agreements, among other things.
Now map to headings:
About the role: paragraph(s) from About The Opportunity.
Responsibilities: ul list.
Requirements: ul list of Required Qualifications.
Qualifications: ul list of Preferred Qualifications (education, experience, ERP, etc.) maybe also include aerospace experience etc.
Skills: ul list of technical and soft skills: Excel, SQL, Python, Snowflake, GitHub, analytical tools, cross-functional leadership, communication, stakeholder-management, managing multiple high-priority projects, etc. Also maybe include experience with ERP systems? But that's already in Qualifications. To avoid duplication, we could put ERP experience under Qualifications and technical skills under Skills. Let's decide:
Qualifications: Preferred Qualifications that are about experience/education: Aerospace/manufacturing experience, BS in STEM, ERP experience, 5+ years in Excel, SQL, Python (maybe that's skill though), demonstration of leading transformation programs, proficiency in Snowflake, GitHub, etc. Actually many are skills. But we can still put them under Qualifications as they are preferred qualifications. Then Skills could be empty? But we need to include a section only when posting has real specific content for it. If we put all preferred qualifications under Qualifications, we might not have content for Skills. But we could still create Skills section with some of the items like cross-functional leadership, communication, stakeholder-management, managing multiple high-priority projects, ability to work in fast-paced environment. Those are soft skills. That seems okay.
Thus:
Qualifications: list of preferred qualifications that are more about background/experience: Aerospace/manufacturing experience, Bachelor’s degree in STEM, Experience across ERP systems, Demonstrated track record leading transformation programs, Proficiency in building data assets in Snowflake, running CI/CD via GitHub, developing analytical tools across multiple platforms and supporting data operations.
Skills: list of technical and soft skills: 5+ years in Excel, SQL, Python; Excellent cross-functional leadership, communication, stakeholder-management skills; Highly motivated and proactive; Ability to manage multiple high-priority projects in fast-paced environment.
But note "5+ years in Excel, SQL, and Python" is a skill; we already have that under Skills. Good.
Now Schedule: we have location remote, travel 25%, occasional weekend/evening work, prolonged sitting, stand/walk, lift up to 15 lbs, PPE required. That's schedule/working conditions.
Thus Schedule section: ul list.
Benefits: ul list? The benefits paragraph is a sentence; we can make a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings. We have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have no explicit Pay or Schedule info besides location remote and travel 25% (that's schedule? maybe schedule). There's also Working Conditions (sitting, lifting). That could be under Schedule? Not exactly. But we can include Schedule if there is info: location remote, travel 25% => schedule info. Also Working Conditions could be under Schedule? Might be better to put under Schedule: remote, travel 25%, occasional weekend/evening work, prolonged sitting, lift up to 15 lbs, PPE required. That seems schedule/working conditions.
Pay: no salary info given. So we should NOT include Pay section because no specific content.
Benefits: we have benefits paragraph.
Skills: we could put preferred qualifications like Excel, SQL, Python, Snowflake, GitHub, etc. Also cross-functional leadership etc. Could be under Skills.
Requirements: maybe we can put Required Qualifications under Requirements? But we also have Qualifications heading. Could separate: Requirements = mandatory (required). Qualifications = preferred? Or we could put Required under Requirements and Preferred under Qualifications. That seems logical.
Thus:
About the role
: paragraphs from About The Opportunity.
Responsibilities
: ul list of responsibilities.
Requirements
: ul list of Required Qualifications.
Qualifications
: ul list of Preferred Qualifications.
Skills
: maybe we could combine some skills from preferred qualifications? But we already have Qualifications. Could also put technical skills under Skills. But to avoid duplication, maybe we put technical skills under Skills and leadership etc under Qualifications? However we need to preserve all info; duplication is okay if we keep content but not repeat? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. We could split: Requirements = mandatory education/experience/authorization. Qualifications = preferred education/experience. Skills = technical skills (Excel, SQL, Python, Snowflake, GitHub, etc.) and soft skills (cross-functional leadership, communication, stakeholder-management, etc.). That seems reasonable.
Let's extract:
About The Opportunity paragraph(s):
"We are seeking a Director of Supply Chain Strategy & Analytics to join our integrated business planning team. This role will be responsible for the strategy, design, and some execution of our integrated supply chain planning including demand planning, supply planning, master production scheduling (MPS), and Sales, Inventory & Operations Planning (SIOP). This leader pairs deep planning expertise with advanced analytics and a transformation mindset to connect a historically siloed, spreadsheet/ERP hybrid supply chain into one synchronized, data-driven operating system. The Director of Supply Chain Strategy & Analytics will translate strategy and analytics into measurable results including lower inventory, higher on-time delivery, and a better customer experience. At the same time, the Director will build and scale the analytics and automation that make it happen. This is a hands-on leadership role for someone equally comfortable setting strategy, modeling data, building solutions (increasingly with AI), and bringing cross-functional teams along for the change."
That's the core.
Location: "This role will primarily be remote and will travel about 25% of the time." That's schedule/working conditions.
Responsibilities list:
- Design planning strategy & SIOP process and establish “one plan, one set of numbers” as the network-level operating standard, building on the planning strengths already present at each site
- Build and govern demand forecasting and demand sensing capabilities; improve forecast accuracy and reduce bias
- Define leading and lagging KPIs for SIOP, cascade KPIs across sites, programs, customers, build dashboard to track KPIs and drive performance improvement
- Develop data and analytical assets to provide inputs into the monthly and weekly process and accelerate ad-hoc analysis to engage with customers and suppliers
- Partner with cross-functional team to make decisions and drive actions that improve business outcomes
- Coach, develop, and grow the planning organization and analytics talent
Required Qualifications:
- Bachelor’s degree
- 4+ years of supply chain experience, including hands-on leadership across demand planning, supply planning, MPS, and SIOP
- 5+ years of building data and analytical assets such as forecasting models, supply chain analytical tools such as clear-to-build, inventory line of balance, inventory entitlement, and centralized data assets
- Must be authorized to work in the U.S. on a full-time basis without sponsorship now or in the future. The Company cannot offer employment to visa holders who require employer sponsorship in the future or cannot work now on a full-time basis.
- Must be able to perform work subject to ITAR/EAR regulations.
Preferred Qualifications:
- Aerospace and/or manufacturing experience
- Bachelor’s degree in Science, Technology, Engineering and Mathematics
- Experience across a range of ERP systems (e.g., Siteline, Visual, Epicor).
- 5+ years in Excel, SQL, and Python
- Demonstrated track record in leading successful transformation programs or working with cross functional team in transformation programs
- Proficiency in building data assets in Snowflake, running CI/CD via GitHub, developing analytical tools across multiple platforms and supporting data operations
- Excellent cross-functional leadership, communication, and stakeholder-management skills, with experience bringing teams together around a shared plan.
- Highly motivated and proactive, with the ability to manage multiple high-priority projects in a fast-paced environment
Working Conditions (maybe schedule):
- Must be able to have prolonged periods sitting at a desk and working on a computer.
- Must be able to frequently sit, stand and walk.
- Must be able to lift and carry up to 15 pounds.
- Personal protective equipment (e.g., safety glasses and safety shoes) is required on the shop floor
- Occasional weekend and evening work may be required to accommodate priorities, deadlines, and schedules.
Benefits:
- health and disability insurance, 401(k) match, flexible spending accounts, EAP, paid time off, and company-paid holidays. The specific programs and options available to an employee may vary depending on date of hire, schedule type, and the applicability of collective bargaining agreements, among other things.
Now map to headings:
About the role: paragraph(s) from About The Opportunity.
Responsibilities: ul list.
Requirements: ul list of Required Qualifications.
Qualifications: ul list of Preferred Qualifications (education, experience, ERP, etc.) maybe also include aerospace experience etc.
Skills: ul list of technical and soft skills: Excel, SQL, Python, Snowflake, GitHub, analytical tools, cross-functional leadership, communication, stakeholder-management, managing multiple high-priority projects, etc. Also maybe include experience with ERP systems? But that's already in Qualifications. To avoid duplication, we could put ERP experience under Qualifications and technical skills under Skills. Let's decide:
Qualifications: Preferred Qualifications that are about experience/education: Aerospace/manufacturing experience, BS in STEM, ERP experience, 5+ years in Excel, SQL, Python (maybe that's skill though), demonstration of leading transformation programs, proficiency in Snowflake, GitHub, etc. Actually many are skills. But we can still put them under Qualifications as they are preferred qualifications. Then Skills could be empty? But we need to include a section only when posting has real specific content for it. If we put all preferred qualifications under Qualifications, we might not have content for Skills. But we could still create Skills section with some of the items like cross-functional leadership, communication, stakeholder-management, managing multiple high-priority projects, ability to work in fast-paced environment. Those are soft skills. That seems okay.
Thus:
Qualifications: list of preferred qualifications that are more about background/experience: Aerospace/manufacturing experience, Bachelor’s degree in STEM, Experience across ERP systems, Demonstrated track record leading transformation programs, Proficiency in building data assets in Snowflake, running CI/CD via GitHub, developing analytical tools across multiple platforms and supporting data operations.
Skills: list of technical and soft skills: 5+ years in Excel, SQL, Python; Excellent cross-functional leadership, communication, stakeholder-management skills; Highly motivated and proactive; Ability to manage multiple high-priority projects in fast-paced environment.
But note "5+ years in Excel, SQL, and Python" is a skill; we already have that under Skills. Good.
Now Schedule: we have location remote, travel 25%, occasional weekend/evening work, prolonged sitting, stand/walk, lift up to 15 lbs, PPE required. That's schedule/working conditions.
Thus Schedule section: ul list.
Benefits: ul list? The benefits paragraph is a sentence; we can make a
or
- . Since it's a list of benefits, we can make ul.
Now ensure we don't include Pay section.
Now produce HTML fragment:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
Schedule
- ... ...