Senior Director Contracts - D&I
for section headings
- Use - for lists
- Use
for prose
- Don't repeat job title as heading
- Don't put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (EEO, cookie/navigation/legal/scam-warning)
- Include section ONLY when real specific content exists
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment, no html/body, no markdown fences
Looking at the content:
- The summary is substantive prose
- Key Responsibilities has four sub-sections with bullet points - these should be lists
- Required Qualifications has a list of items
- Required Experience has a list
- Benefits are mentioned specifically
- Pay is mentioned but with disclaimer - the posting says "The salary offered will depend on several factors..." and "Posted pay ranges are a general guideline only" - this is substantive enough to include as a Pay section? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state benefits and pay information, so I should include them.
But wait: "Posted pay ranges are a general guideline only and are not a guarantee of compensation or salary." This is not a specific pay range, but it does discuss pay. The rule says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". This is similar - it's saying pay depends on factors and ranges are guidelines. However, the posting does have a paragraph about pay and benefits. I think I should include both as sections since they have actual content.
The EEO statement should be removed as boilerplate.
The company description at the top ("ASRC Federal is a leading government contractor...") - this is about the company, not the role. The rule says "About the role" as a heading example. Should I include company description? The summary section seems to be the "About the role" part. The first paragraph is company boilerplate. I'll include the summary paragraph under an "About the role" heading.
Work location: "Hybrid/Onsite in Reston, VA" - this could go in a Schedule section or just as a paragraph. The rule says Schedule section only if posting states it. It states work location. I could include a "Work location" heading or fold into summary. Since it's a specific detail, maybe include as a short paragraph under summary or separate. The rule says "fold minor metadata into a short
or drop it." Work location is not minor metadata. But there's no "Schedule" heading example that matches. The examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". Work location could be under Schedule. But the posting doesn't discuss schedule details (hours, shift). Just location. I'll include it as a paragraph in the summary or separate "Work location" heading? The rule says use h3 for section headings like Schedule. I'll create a "Work location" heading? But the examples don't include "Work location". The rule says "e.g." so not exhaustive. However, "fold minor metadata into a short
or drop it." Work location is important. I'll include it as a paragraph under the summary heading.
Let me structure:
About the role
ASRC Federal is a leading government contractor furthering missions in space, public health and defense. As an Alaska Native owned corporation, our work helps secure an enduring future for our shareholders. Join our team and discover why we are a top veteran employer and Certified Great Place to Work™
ASRC Federal is seeking an accomplished Senior Director of Contracts to lead the contracts function for a major operating group supporting Defense & Intel customers. This role is responsible for shaping contracting strategy, managing change, and ensuring compliance across a diverse portfolio of complex programs.
Work location: Hybrid/Onsite in Reston, VA
Summary: The Senior Director will serve as a trusted advisor to the Operating Group leadership, partnering closely with Business Development, Program Management, Finance, Legal, and other functional leaders supporting Defense customers. This is a high‑visibility leadership position requiring strategic insight, sound judgment, and the ability to guide a team through a dynamic and fast‑paced environment.
Responsibilities
Then sub-sections? The rule says use h3 for section headings. The responsibilities have sub-headings. Should I use h3 for each sub-heading? The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say to use h4 for sub-sections. But the responsibilities are grouped into four categories. I could make each a separate h3? That would be many h3s. Or I could keep Responsibilities as h3 and then use sub-lists with bold labels? But the rule says use ul li for any list of duties. The duties are grouped. I think I should create separate h3 for each responsibility area? But the example headings are top-level sections. The posting has "Key Responsibilities" as a heading, then four sub-headings. I'll make "Responsibilities" as h3, then for each sub-area, maybe use a paragraph with strong text and then a list? But the rule says use ul li for any list of duties/requirements/benefits. The sub-headings are not duties themselves, they are categories. I could do:
Responsibilities
Strategic Leadership & Business Partnership
but rule says only h3 for section headings. It doesn't forbid h4, but says "use for section headings". Might be okay to use h4 for sub-sections. However, to be safe, I'll keep only h3 for main sections. I'll combine all responsibilities under one Responsibilities section with categorized lists. But the rule says "Prefer a few substantive sections over many thin ones." So maybe keep Responsibilities as one section with multiple lists, each preceded by a bold label in a paragraph.
Let me see: The responsibilities are distinct areas. I'll create an h3 for each? That would be four h3s: Strategic Leadership & Business Partnership, Contracts Management & Execution, Team Leadership & Talent Development, Governance, Compliance & Risk Management. But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists "Responsibilities" as a section heading, not the sub-categories. So I should have one Responsibilities section. I'll structure it with sub-headings as paragraphs with strong text, then lists.
Similarly, Required Qualifications and Required Experience could be combined under "Qualifications" or separate. The posting has "Required Qualifications" and "Required Experience" as separate headings. I'll make two sections: "Qualifications" and "Experience" or "Requirements". The example includes "Requirements" and "Qualifications". I'll use "Qualifications" for the first list (degree, years, citizenship) and "Experience" for the second list.
Benefits and Pay are separate.
Now, remove EEO statement.
Let's write the HTML.
I'll start with About the role, then Responsibilities, then Qualifications, then Experience, then Benefits, then Pay.
For Responsibilities, I'll do:
Responsibilities
Strategic Leadership & Business Partnership
- Serve as the principal contracts advisor to Operating Group executives, providing strategic counsel on terms, conditions, proposal and execution risks and mitigation.
- Shape and execute contract strategies that support business objectives, competitive positioning, and long‑term growth.
- Partner with senior leadership to drive performance standards that result in strong CPARs, customer satisfaction, and achievement of annual operating plans.
- Develop and implement customer engagement strategies to expand on‑contract growth and strengthen customer relationships.
Contracts Management & Execution
- Oversee a portfolio of complex federal contracts across multiple contract types, ensuring compliance with FAR, DFARS, agency supplements, and corporate policies.
- Lead the review, negotiation, and execution of contracts, subcontracts, teaming agreements, NDAs, OCI mitigation plans, and other contractual instruments.
- Provide authoritative interpretation of terms and conditions, identifying risk areas and recommending mitigation strategies.
- Support or lead major capture efforts, including shaping opportunities, reviewing RFPs, advising on technical and pricing risks, and guiding proposal development.
- Ensure timely and accurate preparation of proposal volumes, model contracts, and partner with Proposal organization to ensure compliant and timely proposal submissions.
Team Leadership & Talent Development
- Lead, mentor, and develop a high‑performing team of contracts professionals across multiple locations.
- Drive a culture of accountability, integrity, and continuous improvement.
- Oversee workforce planning, recruiting, performance management, and professional development initiatives.
- Promote operational excellence by ensuring adherence to standardized processes, tools, and best practices.
Governance, Compliance & Risk Management
- Ensure compliance with all contractual, regulatory, and corporate requirements.
- Proactively identify emerging risks and develop mitigation strategies to protect the company’s interests.
- Collaborate with Legal, Finance, and other stakeholders to resolve complex contractual issues.
- Support corporate initiatives related to business optimization, process improvement, and technology adoption.
- Deep knowledge of FAR/DFARS, OCI mitigation, IP considerations, and other key contracting frameworks.
Note: The last bullet "Deep knowledge of FAR/DFARS..." is actually under Governance but seems like a qualification. It's listed under Governance in the posting. I'll keep it there.
Qualifications:
Qualifications
- Bachelor’s degree
- 15+ years of relevant Contracts work experience.
- U.S. Citizenship required to obtain and maintain a Top Secret security clearance if necessary.
Experience:
Experience
- Demonstrated expertise with a wide range of contract types and acquisition strategies.
- Proven success negotiating large, complex federal contracts and leading proposal efforts.
- Strong business acumen with the ability to think critically and develop practical, innovative solutions.
- Exceptional communication, interpersonal, and relationship‑building skills.
- Ability to thrive in a fast‑moving environment and manage multiple priorities with precision.
- Unwavering commitment to integrity, professionalism, and mission support.
- Contracting leadership experience on major competitive procurements.
- Experience supporting Defense and Intelligence Community customers.
- Experience leading contracts for an operating group or business unit.
Benefits:
Benef
for prose - Don't repeat job title as heading - Don't put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (EEO, cookie/navigation/legal/scam-warning) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no html/body, no markdown fences Looking at the content: - The summary is substantive prose - Key Responsibilities has four sub-sections with bullet points - these should be lists - Required Qualifications has a list of items - Required Experience has a list - Benefits are mentioned specifically - Pay is mentioned but with disclaimer - the posting says "The salary offered will depend on several factors..." and "Posted pay ranges are a general guideline only" - this is substantive enough to include as a Pay section? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state benefits and pay information, so I should include them. But wait: "Posted pay ranges are a general guideline only and are not a guarantee of compensation or salary." This is not a specific pay range, but it does discuss pay. The rule says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". This is similar - it's saying pay depends on factors and ranges are guidelines. However, the posting does have a paragraph about pay and benefits. I think I should include both as sections since they have actual content. The EEO statement should be removed as boilerplate. The company description at the top ("ASRC Federal is a leading government contractor...") - this is about the company, not the role. The rule says "About the role" as a heading example. Should I include company description? The summary section seems to be the "About the role" part. The first paragraph is company boilerplate. I'll include the summary paragraph under an "About the role" heading. Work location: "Hybrid/Onsite in Reston, VA" - this could go in a Schedule section or just as a paragraph. The rule says Schedule section only if posting states it. It states work location. I could include a "Work location" heading or fold into summary. Since it's a specific detail, maybe include as a short paragraph under summary or separate. The rule says "fold minor metadata into a short
or drop it." Work location is not minor metadata. But there's no "Schedule" heading example that matches. The examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". Work location could be under Schedule. But the posting doesn't discuss schedule details (hours, shift). Just location. I'll include it as a paragraph in the summary or separate "Work location" heading? The rule says use h3 for section headings like Schedule. I'll create a "Work location" heading? But the examples don't include "Work location". The rule says "e.g." so not exhaustive. However, "fold minor metadata into a short
or drop it." Work location is important. I'll include it as a paragraph under the summary heading. Let me structure:
About the role
ASRC Federal is a leading government contractor furthering missions in space, public health and defense. As an Alaska Native owned corporation, our work helps secure an enduring future for our shareholders. Join our team and discover why we are a top veteran employer and Certified Great Place to Work™
ASRC Federal is seeking an accomplished Senior Director of Contracts to lead the contracts function for a major operating group supporting Defense & Intel customers. This role is responsible for shaping contracting strategy, managing change, and ensuring compliance across a diverse portfolio of complex programs.
Work location: Hybrid/Onsite in Reston, VA
Summary: The Senior Director will serve as a trusted advisor to the Operating Group leadership, partnering closely with Business Development, Program Management, Finance, Legal, and other functional leaders supporting Defense customers. This is a high‑visibility leadership position requiring strategic insight, sound judgment, and the ability to guide a team through a dynamic and fast‑paced environment.
Responsibilities
Then sub-sections? The rule says use h3 for section headings. The responsibilities have sub-headings. Should I use h3 for each sub-heading? The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say to use h4 for sub-sections. But the responsibilities are grouped into four categories. I could make each a separate h3? That would be many h3s. Or I could keep Responsibilities as h3 and then use sub-lists with bold labels? But the rule says use ul li for any list of duties. The duties are grouped. I think I should create separate h3 for each responsibility area? But the example headings are top-level sections. The posting has "Key Responsibilities" as a heading, then four sub-headings. I'll make "Responsibilities" as h3, then for each sub-area, maybe use a paragraph with strong text and then a list? But the rule says use ul li for any list of duties/requirements/benefits. The sub-headings are not duties themselves, they are categories. I could do:
Responsibilities
Strategic Leadership & Business Partnership
but rule says only h3 for section headings. It doesn't forbid h4, but says "use for section headings". Might be okay to use h4 for sub-sections. However, to be safe, I'll keep only h3 for main sections. I'll combine all responsibilities under one Responsibilities section with categorized lists. But the rule says "Prefer a few substantive sections over many thin ones." So maybe keep Responsibilities as one section with multiple lists, each preceded by a bold label in a paragraph.
Let me see: The responsibilities are distinct areas. I'll create an h3 for each? That would be four h3s: Strategic Leadership & Business Partnership, Contracts Management & Execution, Team Leadership & Talent Development, Governance, Compliance & Risk Management. But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists "Responsibilities" as a section heading, not the sub-categories. So I should have one Responsibilities section. I'll structure it with sub-headings as paragraphs with strong text, then lists.
Similarly, Required Qualifications and Required Experience could be combined under "Qualifications" or separate. The posting has "Required Qualifications" and "Required Experience" as separate headings. I'll make two sections: "Qualifications" and "Experience" or "Requirements". The example includes "Requirements" and "Qualifications". I'll use "Qualifications" for the first list (degree, years, citizenship) and "Experience" for the second list.
Benefits and Pay are separate.
Now, remove EEO statement.
Let's write the HTML.
I'll start with About the role, then Responsibilities, then Qualifications, then Experience, then Benefits, then Pay.
For Responsibilities, I'll do:
Responsibilities
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists "Responsibilities" as a section heading, not the sub-categories. So I should have one Responsibilities section. I'll structure it with sub-headings as paragraphs with strong text, then lists.
Similarly, Required Qualifications and Required Experience could be combined under "Qualifications" or separate. The posting has "Required Qualifications" and "Required Experience" as separate headings. I'll make two sections: "Qualifications" and "Experience" or "Requirements". The example includes "Requirements" and "Qualifications". I'll use "Qualifications" for the first list (degree, years, citizenship) and "Experience" for the second list.
Benefits and Pay are separate.
Now, remove EEO statement.
Let's write the HTML.
I'll start with About the role, then Responsibilities, then Qualifications, then Experience, then Benefits, then Pay.
For Responsibilities, I'll do:
Responsibilities
Strategic Leadership & Business Partnership
- Serve as the principal contracts advisor to Operating Group executives, providing strategic counsel on terms, conditions, proposal and execution risks and mitigation.
- Shape and execute contract strategies that support business objectives, competitive positioning, and long‑term growth.
- Partner with senior leadership to drive performance standards that result in strong CPARs, customer satisfaction, and achievement of annual operating plans.
- Develop and implement customer engagement strategies to expand on‑contract growth and strengthen customer relationships.
Contracts Management & Execution
- Oversee a portfolio of complex federal contracts across multiple contract types, ensuring compliance with FAR, DFARS, agency supplements, and corporate policies.
- Lead the review, negotiation, and execution of contracts, subcontracts, teaming agreements, NDAs, OCI mitigation plans, and other contractual instruments.
- Provide authoritative interpretation of terms and conditions, identifying risk areas and recommending mitigation strategies.
- Support or lead major capture efforts, including shaping opportunities, reviewing RFPs, advising on technical and pricing risks, and guiding proposal development.
- Ensure timely and accurate preparation of proposal volumes, model contracts, and partner with Proposal organization to ensure compliant and timely proposal submissions.
Team Leadership & Talent Development
- Lead, mentor, and develop a high‑performing team of contracts professionals across multiple locations.
- Drive a culture of accountability, integrity, and continuous improvement.
- Oversee workforce planning, recruiting, performance management, and professional development initiatives.
- Promote operational excellence by ensuring adherence to standardized processes, tools, and best practices.
Governance, Compliance & Risk Management
- Ensure compliance with all contractual, regulatory, and corporate requirements.
- Proactively identify emerging risks and develop mitigation strategies to protect the company’s interests.
- Collaborate with Legal, Finance, and other stakeholders to resolve complex contractual issues.
- Support corporate initiatives related to business optimization, process improvement, and technology adoption.
- Deep knowledge of FAR/DFARS, OCI mitigation, IP considerations, and other key contracting frameworks.
Qualifications
- Bachelor’s degree
- 15+ years of relevant Contracts work experience.
- U.S. Citizenship required to obtain and maintain a Top Secret security clearance if necessary.
Experience
- Demonstrated expertise with a wide range of contract types and acquisition strategies.
- Proven success negotiating large, complex federal contracts and leading proposal efforts.
- Strong business acumen with the ability to think critically and develop practical, innovative solutions.
- Exceptional communication, interpersonal, and relationship‑building skills.
- Ability to thrive in a fast‑moving environment and manage multiple priorities with precision.
- Unwavering commitment to integrity, professionalism, and mission support.
- Contracting leadership experience on major competitive procurements.
- Experience supporting Defense and Intelligence Community customers.
- Experience leading contracts for an operating group or business unit.