Senior Procurement Analyst - PWB Substrates
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to parse the job description.
Content:
- Intro: "The New Hampshire procurement team is looking for a candidate to assume a Buyer/Planner role. The Buyer/Planner's role is to provide the best value procurement consistent with cost, quality and service requirements while maintaining excellent supplier relationships. This position interfaces with many internal and external stakeholders including but not limited to supply chain management, supplier quality, manufacturing, and programs. This position will be responsible for the planning and executing of requisitions, ensuring that purchase orders get placed in a timely manner, and expediting any orders to meet our program needs."
That's prose about the role. Could be "About the role" section.
- Responsibilities: list bullet points after "Responsibilities". Let's extract:
"Strong business acumen with excellent written, verbal, and listening skills.
Ability to successfully interface with supplier leadership teams.
Data driven decision maker; ensures compliance with policies and procedures.
Strong communication skills with an assertive and forthcoming professional demeanor.
Ability to operate in a demanding and dynamic culture.
Support supplier development, negotiations, administration, supplier improvement and management.
Help to prepare metrics on a weekly basis, and at Monthly Business Reviews (MBR’s).
Manage and report on supplier requisitions and purchase orders.
Track and report on Supplier delivery dates.
Resolve receiving and invoice issues.
Manage non-conforming material returns to suppliers and close non-conformances within 14 days.
Resolve master schedules and production problems and negotiates lead times."
These are responsibilities.
- Required Education, Experience, & Skills: list:
"Typically a Bachelor's Degree and 4 years work experience or equivalent experience
Ability to execute/ oversee the planning and procurement of electronic components
Strong communication, organizational and analytical skills
Work effectively in a team environment
Proven problem solving capabilities"
- Preferred Education, Experience, & Skills:
"Have hands-on experience with MRP systems (preferably Oracle)
Prior Procurement experience
Familiarity with FAR/DFAR regulations and Export Control requirements
Microsoft Office tools (Excel, Word, PowerPoint)"
- Data View Pay Information: "Full-Time Salary Range: $82779 - $140723 Please note: This range is based on our market pay structures. However, individual salaries are determined by a variety of factors including, but not limited to: business considerations, local market conditions, and internal equity, as well as candidate qualifications, such as skills, education, and experience."
Thus Pay section.
- Employee Benefits: long paragraph describing benefits.
Thus Benefits section.
- About BAE Systems Electronic Systems: description of company. Could be "About the company" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company". Should we include? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples but we should use those headings when appropriate. Probably we should stick to those headings only. The "About BAE Systems Electronic Systems" could be considered "About the role"? No, it's about company. Might be omitted as not matching allowed headings. However we need to preserve ALL substantive information; we cannot drop company description if it's substantive. But we could incorporate it into "About the role" maybe? But that would be inaccurate. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. Likely they expect us to use those headings only. However they also say "Prefer a few substantive sections over many thin ones." So we could combine company description into "About the role" or maybe omit as not required? But they said preserve ALL substantive information. So we need to include it somewhere. Could create a section "About the company" but not in list; maybe they'd accept as it's still a heading. But they said use for section headings (e.g. About the role, Responsibilities...). The "e.g." suggests those are examples, not exclusive. So we can use other headings if needed, but better to stick to given ones. However "About BAE Systems Electronic Systems" is substantive; we could put it under "About the role" as a paragraph describing the company context. That might be acceptable.
Alternatively we could create a section "About the company" but risk not following instruction. I'd go with using "About the role" for the introductory paragraph and also include company description there? Might be mixing.
Better: Use "About the role" for the role description intro. Then maybe add another section "About the company" but it's not in the list; risk.
Given the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." I think they want us to use those exact headings when applicable. If a section doesn't match, we could omit heading and just use
. But they said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to decide which sections have content.
We have content for:
- About the role: yes (intro paragraph)
- Responsibilities: yes (list)
- Requirements: maybe we can treat "Required Education, Experience, & Skills" as Requirements.
- Qualifications: maybe "Preferred Education, Experience, & Skills" as Qualifications? Or Skills? Actually they have separate headings for Qualifications and Skills. We could split: Required as Requirements, Preferred as Qualifications, and maybe Skills separate? But we have skills listed in both required and preferred. Could combine.
Simplify: Use Requirements for required, Qualifications for preferred, Skills maybe not needed separately. But we have a Skills heading in examples; we could put technical skills like MRP, Office tools under Skills. However the preferred list includes those. Could treat them as Skills.
Pay: yes.
Benefits: yes.
Schedule: not mentioned (no schedule info). So omit Schedule.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We need to ensure we don't repeat job title as heading. Good.
Now format:
About the role
... intro paragraph ... plus maybe company description? We'll include company description in About the role? Might be too long but okay.
Better: Keep intro paragraph only in About the role, and add a separate paragraph for company description maybe under same heading? Could be two
under same heading.
Let's craft:
About the role:
The New Hampshire procurement team is looking for a candidate to assume a Buyer/Planner role. The Buyer/Planner's role is to provide the best value procurement consistent with cost, quality and service requirements while maintaining excellent supplier relationships. This position interfaces with many internal and external stakeholders including but not limited to supply chain management, supplier quality, manufacturing, and programs. This position will be responsible for the planning and executing of requisitions, ensuring that purchase orders get placed in a timely manner, and expediting any orders to meet our program needs.
BAE Systems Electronic Systems is a defense, aerospace, and security company headquartered in Falls Church, Virginia, with more than 40,000 employees worldwide. We serve, supply, and protect those who protect us. As one of the most geographically diverse international defense companies, we deliver a full range of products and services spanning air, land, maritime, space, and cyber, including advanced electronics, intelligence solutions, and dedicated customer support. Our culture is performance-driven and values-led, built on curiosity, creativity, and collaboration. Purpose isn't a tagline here. It's what drives us. We're developing breakthrough technologies that defend national security and make a lasting impact on our communities and our planet. When you join BAE Systems, you're not just building a career. You're contributing to a mission that truly matters.
That seems fine.
Responsibilities: Responsibilities
- ... each bullet
Requirements: Requirements
- ... required list
Qualifications: Qualifications
- ... preferred list
Skills: maybe we could extract specific skills like MRP systems, Office tools, FAR/DFAR, Export Control. But those are already in Qualifications. Could still have Skills section for technical skills: "Hands-on experience with MRP systems (preferably Oracle)", "Prior Procurement experience", "Familiarity with FAR/DFAR regulations and Export Control requirements", "Microsoft Office tools (Excel, Word, PowerPoint)". However those are also in Qualifications. To avoid duplication, maybe we skip Skills section. But we have a heading for Skills in examples; we could still include if we have content not covered elsewhere. However we already covered those in Qualifications. Could combine Qualifications and Skills? But better to follow instruction: Prefer a few substantive sections over many thin ones. So we could omit Skills if its content overlaps with Qualifications. However the instruction says "include a section ONLY when the posting has real, specific content for it". If we put Skills, we need specific content not already covered. Could we treat Skills as "Strong communication, organizational and analytical skills" etc? Those are in Required. But again overlapping.
Thus maybe we omit Skills.
But the examples list includes Skills; maybe they expect us to use it for skill-based items like "Strong communication, organizational and analytical skills", "Proven problem solving capabilities", "Ability to execute/oversee the planning and procurement of electronic components", "Work effectively in a team environment". Those are more like skills. However they also appear in Required. Could split: Requirements = education/experience; Skills = abilities; Qualifications = preferred experience. Let's try.
We have:
Required Education, Experience, & Skills (the heading includes Skills). Actually the posting lumps education, experience, & skills together. So we could treat that as Requirements (includes education, experience, skills). Then Preferred Education, Experience, & Skills as Qualifications (includes preferred education, experience, skills). Then we might not need separate Skills.
Thus we will have Requirements and Qualifications only.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Check if any other sections: Schedule none.
Now we need to ensure we don't include boilerplate like "This position will be posted for at least 5 calendar days..." etc. That's boilerplate; remove.
Also remove "Please note: This range is based on our market pay structures..." Actually that's part of Pay info; we can keep as prose under Pay.
Now format.
Let's craft the lists.
Responsibilities list items:
- Strong business acumen with excellent written, verbal, and listening skills.
- Ability to successfully interface with supplier leadership teams.
- Data driven decision maker; ensures compliance with policies and procedures.
- Strong communication skills with an assertive and forthcoming professional demeanor.
- Ability to operate in a demanding and dynamic culture.
- Support supplier development, negotiations, administration, supplier improvement and management.
- Help to prepare metrics on a weekly basis, and at Monthly Business Reviews (MBR’s).
- Manage and report on supplier requisitions and purchase orders.
- Track and report on Supplier delivery dates.
- Resolve receiving and invoice issues.
- Manage non-conforming material returns to suppliers and close non-conformances within 14 days.
- Resolve master
for prose. We need to parse the job description. Content: - Intro: "The New Hampshire procurement team is looking for a candidate to assume a Buyer/Planner role. The Buyer/Planner's role is to provide the best value procurement consistent with cost, quality and service requirements while maintaining excellent supplier relationships. This position interfaces with many internal and external stakeholders including but not limited to supply chain management, supplier quality, manufacturing, and programs. This position will be responsible for the planning and executing of requisitions, ensuring that purchase orders get placed in a timely manner, and expediting any orders to meet our program needs." That's prose about the role. Could be "About the role" section. - Responsibilities: list bullet points after "Responsibilities". Let's extract: "Strong business acumen with excellent written, verbal, and listening skills. Ability to successfully interface with supplier leadership teams. Data driven decision maker; ensures compliance with policies and procedures. Strong communication skills with an assertive and forthcoming professional demeanor. Ability to operate in a demanding and dynamic culture. Support supplier development, negotiations, administration, supplier improvement and management. Help to prepare metrics on a weekly basis, and at Monthly Business Reviews (MBR’s). Manage and report on supplier requisitions and purchase orders. Track and report on Supplier delivery dates. Resolve receiving and invoice issues. Manage non-conforming material returns to suppliers and close non-conformances within 14 days. Resolve master schedules and production problems and negotiates lead times." These are responsibilities. - Required Education, Experience, & Skills: list: "Typically a Bachelor's Degree and 4 years work experience or equivalent experience Ability to execute/ oversee the planning and procurement of electronic components Strong communication, organizational and analytical skills Work effectively in a team environment Proven problem solving capabilities" - Preferred Education, Experience, & Skills: "Have hands-on experience with MRP systems (preferably Oracle) Prior Procurement experience Familiarity with FAR/DFAR regulations and Export Control requirements Microsoft Office tools (Excel, Word, PowerPoint)" - Data View Pay Information: "Full-Time Salary Range: $82779 - $140723 Please note: This range is based on our market pay structures. However, individual salaries are determined by a variety of factors including, but not limited to: business considerations, local market conditions, and internal equity, as well as candidate qualifications, such as skills, education, and experience." Thus Pay section. - Employee Benefits: long paragraph describing benefits. Thus Benefits section. - About BAE Systems Electronic Systems: description of company. Could be "About the company" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company". Should we include? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples but we should use those headings when appropriate. Probably we should stick to those headings only. The "About BAE Systems Electronic Systems" could be considered "About the role"? No, it's about company. Might be omitted as not matching allowed headings. However we need to preserve ALL substantive information; we cannot drop company description if it's substantive. But we could incorporate it into "About the role" maybe? But that would be inaccurate. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. Likely they expect us to use those headings only. However they also say "Prefer a few substantive sections over many thin ones." So we could combine company description into "About the role" or maybe omit as not required? But they said preserve ALL substantive information. So we need to include it somewhere. Could create a section "About the company" but not in list; maybe they'd accept as it's still a heading. But they said use for section headings (e.g. About the role, Responsibilities...). The "e.g." suggests those are examples, not exclusive. So we can use other headings if needed, but better to stick to given ones. However "About BAE Systems Electronic Systems" is substantive; we could put it under "About the role" as a paragraph describing the company context. That might be acceptable.
Alternatively we could create a section "About the company" but risk not following instruction. I'd go with using "About the role" for the introductory paragraph and also include company description there? Might be mixing.
Better: Use "About the role" for the role description intro. Then maybe add another section "About the company" but it's not in the list; risk.
Given the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." I think they want us to use those exact headings when applicable. If a section doesn't match, we could omit heading and just use
for section headings (e.g. About the role, Responsibilities...). The "e.g." suggests those are examples, not exclusive. So we can use other headings if needed, but better to stick to given ones. However "About BAE Systems Electronic Systems" is substantive; we could put it under "About the role" as a paragraph describing the company context. That might be acceptable.
Alternatively we could create a section "About the company" but risk not following instruction. I'd go with using "About the role" for the introductory paragraph and also include company description there? Might be mixing.
Better: Use "About the role" for the role description intro. Then maybe add another section "About the company" but it's not in the list; risk.
Given the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." I think they want us to use those exact headings when applicable. If a section doesn't match, we could omit heading and just use
. But they said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to decide which sections have content. We have content for: - About the role: yes (intro paragraph) - Responsibilities: yes (list) - Requirements: maybe we can treat "Required Education, Experience, & Skills" as Requirements. - Qualifications: maybe "Preferred Education, Experience, & Skills" as Qualifications? Or Skills? Actually they have separate headings for Qualifications and Skills. We could split: Required as Requirements, Preferred as Qualifications, and maybe Skills separate? But we have skills listed in both required and preferred. Could combine. Simplify: Use Requirements for required, Qualifications for preferred, Skills maybe not needed separately. But we have a Skills heading in examples; we could put technical skills like MRP, Office tools under Skills. However the preferred list includes those. Could treat them as Skills. Pay: yes. Benefits: yes. Schedule: not mentioned (no schedule info). So omit Schedule. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to ensure we don't repeat job title as heading. Good. Now format:
About the role
... intro paragraph ... plus maybe company description? We'll include company description in About the role? Might be too long but okay. Better: Keep intro paragraph only in About the role, and add a separate paragraph for company description maybe under same heading? Could be two
under same heading. Let's craft: About the role:
The New Hampshire procurement team is looking for a candidate to assume a Buyer/Planner role. The Buyer/Planner's role is to provide the best value procurement consistent with cost, quality and service requirements while maintaining excellent supplier relationships. This position interfaces with many internal and external stakeholders including but not limited to supply chain management, supplier quality, manufacturing, and programs. This position will be responsible for the planning and executing of requisitions, ensuring that purchase orders get placed in a timely manner, and expediting any orders to meet our program needs.
BAE Systems Electronic Systems is a defense, aerospace, and security company headquartered in Falls Church, Virginia, with more than 40,000 employees worldwide. We serve, supply, and protect those who protect us. As one of the most geographically diverse international defense companies, we deliver a full range of products and services spanning air, land, maritime, space, and cyber, including advanced electronics, intelligence solutions, and dedicated customer support. Our culture is performance-driven and values-led, built on curiosity, creativity, and collaboration. Purpose isn't a tagline here. It's what drives us. We're developing breakthrough technologies that defend national security and make a lasting impact on our communities and our planet. When you join BAE Systems, you're not just building a career. You're contributing to a mission that truly matters.
That seems fine. Responsibilities:Responsibilities
- ... each bullet
Requirements
- ... required list
Qualifications
- ... preferred list