Subcontracts Manager

We need to output HTML fragment with sections: About the role, Responsibilities? Actually the posting includes "About The Role" paragraph describing responsibilities. Also "About You" includes mission statement and qualifications. Then Minimum Qualifications, Preferred Qualifications, Compensation (Pay Range), Benefits (Elevate Your Career includes benefits). Also maybe "Schedule"? Not present. So we include sections: About the role (maybe heading About the role), Responsibilities? The "About The Role" paragraph includes responsibilities; we could treat that as About the role section. Then we could have a Responsibilities section? But we should not create empty sections. The posting includes responsibilities within About The Role. Could also split into Responsibilities and Qualifications. However we have Minimum Qualifications and Preferred Qualifications sections. So we can have sections: About the role (maybe a brief description), Responsibilities (maybe we can extract duties from About The Role). But the instruction: "Prefer a few substantive sections over many thin ones." So we could combine About the role and Responsibilities into one section? But we need headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include headings when there is real specific content. So we need to decide which headings have content. We have content for About the role (the paragraph). We have content for Responsibilities (the same paragraph includes responsibilities). Could we treat About the role as a short intro and Responsibilities as bullet list? But we don't have bullet list; it's prose. Could still put responsibilities under About the role heading. But we need to follow instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose to include About the role and Responsibilities as separate headings if we have content for each. We have content for About the role (the paragraph). For Responsibilities we could extract the duties: "managing the lifecycle of subcontracts from initial solicitation through contract close-out. This role includes developing subcontract agreements, ensuring compliance with regulatory requirements, negotiating contract terms, and managing supplier relationships. They will have an advanced understanding of subcontracting strategies and full lifecycle management, expertise in government and commercial contracting regulations, and strong risk management and dispute resolution techniques. In this role, you will lead the negotiation and administration of complex subcontracts, ensuring favorable terms and alignment with company objectives. You will develop strategies for subcontractor selection, evaluation, and performance management while ensuring compliance with regulatory requirements and company policies. Additionally, you will provide guidance and mentorship to junior subcontract administrators and lead cross-functional teams on subcontracting initiatives. You will also take charge of projects to execute subcontracts and sourcing activities, including project management, risk management, schedule and cost management, and supplier relationship management. Furthermore, you will interact with leadership, suppliers, and external personnel on matters that often require coordination between functional organizations to achieve seamless execution of subcontracting goals." That's a lot of responsibilities. So we can put that under Responsibilities heading as

or

• . Since it's a list of duties, we could convert to
  • . The instruction: Use
    • for any list of duties/requirements/benefits. So we should make a list. Similarly, Requirements/Qualifications: we have Minimum Qualifications and Preferred Qualifications. Could combine into Requirements? But we have separate headings for Qualifications and Skills. We could put Minimum Qualifications under Requirements heading, Preferred Qualifications under Qualifications heading? Or we could have Requirements (minimum) and Qualifications (preferred). The instruction: Use headings as examples; we can choose which to include. We'll include Requirements (minimum) and Qualifications (preferred). Also Skills maybe not needed separately. Benefits: we have "Elevate Your Career" paragraph describing benefits: medical, dental, vision plans, 401(k) with 150% match up to 6%, life insurance, 3 weeks paid time off, and more. So we can make Benefits section with list. Pay: we have Compensation: Pay Range: $100,291.00 - $137,921.50 plus note. So we include Pay section. Schedule: not present, so omit. Also we might include About the company? Not needed. We must not include boilerplate like EEO, application deadline, etc. Remove those. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact numbers, etc. We need to output only HTML fragment, no /, no markdown. We'll structure:

      About the role

      Sierra Space team members share a spirit of innovation and collaboration and a belief that we can deliver on the boldest missions in space today. Together with our customers, we aim to safeguard our nation, sustain human presence in space, and secure the freedom of operations in low Earth orbit and beyond. Our success is measured by the trust of those who rely on what we build and deliver, and our technologies keep the United States and its allies mission-ready throughout space. We are mission-driven, and together, we are an extraordinary team.

      But that's actually the introductory paragraph before About The Role. The posting starts with a paragraph about Sierra Space mission. That is substantive; we could include it under About the role or maybe a separate section like "About Sierra Space". But we only have headings list; we could put that under About the role as context. However the instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It's okay. But we also have "About The Role" heading in the posting. So we could have About the role section with that paragraph describing the role responsibilities? Actually the "About The Role" heading is followed by description of responsibilities. So we could put that under About the role heading. Thus we might not need the earlier mission paragraph; but it's substantive about company mission. Could we include it under About the role? It's not about the role but about company. Might be better to have a separate section like "About Sierra Space" but not in allowed headings. Since we must only use those headings, we could incorporate it into About the role as introductory text. That's okay. But we must preserve ALL substantive information; we cannot drop the mission paragraph. So we need to include it somewhere. We'll put it in About the role section as a

      before the responsibilities list. Now Responsibilities: we will create

      • items each duty. We need to extract each duty as separate list items. Let's parse: - Managing the lifecycle of subcontracts from initial solicitation through contract close-out. - Developing subcontract agreements. - Ensuring compliance with regulatory requirements. - Negotiating contract terms. - Managing supplier relationships. - Leading the negotiation and administration of complex subcontracts, ensuring favorable terms and alignment with company objectives. - Developing strategies for subcontractor selection, evaluation, and performance management while ensuring compliance with regulatory requirements and company policies. - Providing guidance and mentorship to junior subcontract administrators. - Leading cross-functional teams on subcontracting initiatives. - Taking charge of projects to execute subcontracts and sourcing activities, including project management, risk management, schedule and cost management, and supplier relationship management. - Interacting with leadership, suppliers, and external personnel on matters that often require coordination between functional organizations to achieve seamless execution of subcontracting goals. We could combine some but keep as separate items. Now Requirements (minimum qualifications): list: - Bachelor's degree in a related field (or equivalent work experience in lieu of degree or Masters +3 yrs experience). - Typically 5+ years of related experience. - Skilled in Microsoft suite of products. - EPR/MRP experience. - Advanced understanding of subcontracting strategies and full lifecycle management. - Expertise in government and commercial contracting regulations and compliance (e.g., FAR/DFAR). - Strong understanding of risk management and dispute resolution techniques. - Advanced project management and strategic sourcing skills, including negotiations. - Familiarity with cost and fixed price contracting. Now Qualifications (preferred): - Advanced degree in Business Administration, Supply Chain Management, or a related field. - Certifications: SCM-related certifications. - Extensive experience with SAP. - Proven track record of managing high-value and complex subcontract agreements. - Strong organizational and time management skills. - Ability to work independently and as part of a team. - Strong problem-solving skills and ability to handle multiple tasks simultaneously. - Experience with advanced subcontracting strategies and best practices. - Demonstrated leadership skills and experience in mentoring junior team members. Now Benefits: list: - Medical, dental, and vision plans. - 401(k) with 150% match up to 6%. - Life insurance. - 3 weeks paid time off. - More (we can keep "and more" as item? Might be vague; but we can include as "Additional benefits"). We should not invent; we can keep "and more" as part of the description maybe as a

        after list. But instruction: Use

        • for any list of benefits. So we list the specific ones; we could add an item "Additional benefits" but that's vague. Better to keep as a

          after list: "and more". But that would be prose not list. Might be okay. Pay: we need to include Pay Range: $100,291.00 - $137,921.50 and note: "Your actual base compensation will be determined on a case-by-case basis and may vary based on job-related knowledge and skills, education, experience, internal equity and market competitiveness." We'll put that in a

          . Now we must not include boilerplate like Application Deadline, EEO, etc. We'll output HTML. Check for any repeated lines: we must not duplicate. Now produce final HTML. Let's craft:

          About the role

          Sierra Space team members share a spirit of innovation and collaboration and a belief that we can deliver on the boldest missions in space today. Together with our customers, we aim to safeguard our nation, sustain human presence in space, and secure the freedom of operations in low Earth orbit and beyond. Our success is measured by the trust of those who rely on what we build and deliver, and our technologies keep the United States and its allies mission-ready throughout space. We are mission-driven, and together, we are an extraordinary team.

          The Subcontracts Manager is responsible for managing the lifecycle of subcontracts from initial solicitation through contract close-out. This role includes developing subcontract agreements, ensuring compliance with regulatory requirements, negotiating contract terms, and managing supplier relationships. They will have an advanced understanding of subcontracting strategies and full lifecycle management, expertise in government and commercial contracting regulations, and strong risk management and dispute resolution techniques. In this role, you will lead the negotiation and administration of complex subcontracts, ensuring favorable terms and alignment with company objectives. You will develop strategies for subcontractor selection, evaluation, and performance management while ensuring compliance with regulatory requirements and company policies. Additionally, you will provide guidance and mentorship to junior subcontract administrators and lead cross-functional teams on subcontracting initiatives. You will also take charge of projects to execute subcontracts and sourcing activities, including project management, risk management, schedule and cost management, and supplier relationship management. Furthermore, you will interact with leadership, suppliers, and external personnel on matters that often require coordination between functional organizations to achieve seamless execution of subcontracting goals.

          But we said we should use
          • for list of duties. So better to convert responsibilities to list. However we also have introductory paragraph about role; we could keep that as

            then list. Thus:

            About the role

            Sierra Space team members share a spirit of innovation and collaboration and a belief that we can deliver on the boldest missions in space today. Together with our customers, we aim to safeguard our nation, sustain human presence in space, and secure the freedom of operations in low Earth orbit and beyond.