Contract Specialist II
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for lists of duties/requirements/benefits
- Use `
` for prose
- Do NOT repeat job title as heading (already shown)
- Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `
` or drop it
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them
- Prefer a few substantive sections over many thin ones
- Output ONLY the HTML fragment — no `/`, no markdown code fences
2. **Extract/Analyze Input Data:**
Let's parse the input text:
- "Zachary Piper Solutions is seeking a Contracts Specialist II to work in our Arlington, VA office. This role is based in Arlington with only a one day per week requirement to be onsite with the rest of the week allowing for remote work."
- "Job Description: Responsibilities will include preparing and administering terms and conditions of Department of Defense Research & Development (FAR Part 35) contracts; Assisting in the negotiation of contracts; Preparing contract modifications; Analyzing procurement policies and procedures; Analyzing proposed costs and prices; Preparing required contract file documentation per the FAR, DFARS, and other relevant policies/regulations."
- "Position is full-time at a Department of Defense research agency."
- "Min. years of specialized contracting experience = 6+ years."
- "Required Skills: Active DoD security clearance required. Bachelor’s degree6 years’ experience in government procurement including preparing cost proposals, negotiating terms and conditions of contracts, preparing contract modifications, administering contracts or subcontracts, and analyzing cost and prices." (Note: "Bachelor’s degree6 years’ experience" seems like a formatting glitch, probably "Bachelor’s degree" + "6 years’ experience")
- "Desired Skills: Experience in government or commercial procurement (government preferred); contract administration and negotiation; cost and pricing analysis. DoD, Procurement Desktop Defense (PD2) contractual software, and R&D contracting experience a plus. Experience with Non-FAR based instruments such as Other Transaction Agreements, Grants, and/or Cooperative Agreements a plus but not required."
- "Compensation: $120,000 - $140,000 dependant on experience"
- "Competititve medical, dental, vision and 401K" (typo "Competititve")
- "Keywords: DARPA, DOD, navy, intel, air force, acquisition, contracts, DFAR, contract specialist, procurement, secret clearance, top secret, TS/SCI, remote, hybrid"
Now, I need to map these to the requested sections, following strict rules:
- Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule
- Must NOT create a section unless there's real specific content
- Pay section only if posting actually states them → "$120,000 - $140,000 dependant on experience" → YES, create Pay
- Schedule section only if stated → "full-time" and "one day per week requirement to be onsite with the rest of the week allowing for remote work" → Schedule info is there, but the heading options include "Schedule". I need to be careful: the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." Schedule is stated: full-time, one day onsite remote. I'll include Schedule if it has specific content. But let's see the exact headings allowed: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I should use what fits. I'll probably use: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But I need to check each:
- Responsibilities: yes, detailed list
- Requirements: the min 6+ years, bachelor's degree + 6 years exp, active DoD security clearance → I'll structure as Requirements or split into Qualifications/Skills. The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I need to decide mapping. Probably: Responsibilities, Requirements (combining min years, clearance, degree/experience), Qualifications (maybe overlap), Skills (desired skills). But rules: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So I must only create sections that have real content. I'll likely use: Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Or maybe Qualifications instead of Requirements? Let's see the input: "Min. years of specialized contracting experience = 6+ years. Required Skills: Active DoD security clearance required. Bachelor’s degree6 years’ experience in government procurement..." This is a mix of requirements and skills. I'll map: Responsibilities, Requirements (for the mandatory stuff: 6+ years, clearance, degree+exp), Skills (for desired skills), Benefits (medical, dental, vision, 401K), Pay (salary range), Schedule (full-time, 1 day onsite remote). I'll avoid creating a "Qualifications" section if it's redundant with Requirements, but the allowed headings include both. I'll pick one or the other, or split logically. Let's look at typical job posting structure: Responsibilities, Requirements/Qualifications, Skills, Benefits, Pay, Schedule. I'll use: Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. But I need to ensure each has real content and no placeholders.
Let's parse each section's content:
**Responsibilities** (from "Job Description:"):
- Preparing and administering terms and conditions of Department of Defense Research & Development (FAR Part 35) contracts
- Assisting in the negotiation of contracts
- Preparing contract modifications
- Analyzing procurement policies and procedures
- Analyzing proposed costs and prices
- Preparing required contract file documentation per the FAR, DFARS, and other relevant policies/regulations
**Requirements** (mandatory):
- 6+ years of specialized contracting experience
- Active DoD security clearance required
- Bachelor’s degree + 6 years’ experience in government procurement (the text says "Bachelor’s degree6 years’ experience" - I'll parse as Bachelor’s degree and 6 years’ experience)
- Position is full-time at a Department of Defense research agency
- Only one day per week onsite, rest remote (this is more about schedule/location, but I can include in Requirements or Schedule)
**Skills** (desired/optional):
- Experience in government or commercial procurement (government preferred)
- Contract administration and negotiation
- Cost and pricing analysis
- DoD Procurement Desktop Defense (PD2) contractual software
- R&D contracting experience
- Experience with Non-FAR based instruments such as Other Transaction Agreements, Grants, and/or Cooperative Agreements
**Benefits**:
- Competitive medical, dental, vision and 401K
**Pay**:
- $120,000 - $140,000 dependant on experience
**Schedule**:
- Full-time
- One day per week onsite, rest remote
Now, check rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them" → all three are stated, so I can include them. "Prefer a few substantive sections over many thin ones." I'll include: Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. That's 6 sections. Could I drop Schedule? It has specific content: full-time, 1 day onsite remote. I'll include it. Could I drop Qualifications? I'm not using a Qualifications heading; I'll use Requirements for mandatory, Skills for desired. The allowed headings list includes "Qualifications", but I don't have to use it if I use Requirements. The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It's not exhaustive but those are examples. I'll stick to the ones I have content for.
Important: "Do NOT repeat the job title as a heading (the page already shows it)" → I won't include a heading for the job title.
"Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." → No job ID in input, but there's company name and location info at top. I'll fold company/location into a
maybe, or just start with sections. The rule says output ONLY the HTML fragment, no /. I can have top-level text outside sections? Probably better to include the introductory sentence about company/role as a
before sections, but careful: "Do NOT repeat the job title as a heading (the page already shows it)" - the job title is "Contracts Specialist II". I won't use an
for it. I might include the company/location as a
at the top, but the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't explicitly say to remove company/location, but "fold minor metadata into a short
or drop it." I'll put company and location in a brief
at the start, or maybe just start with sections. Let's see: "Zachary Piper Solutions is seeking a Contracts Specialist II to work in our Arlington, VA office. This role is based in Arlington with only a one day per week requirement to be onsite with the rest of the week allowing for remote work." This is introductory. I'll put it as a
at the top, maybe without the job title repeated. Actually, the job title is "Contracts Specialist II". I won't wrap it in a heading. I'll just have the prose.
Let's structure:
Zachary Piper Solutions is seeking a Contracts Specialist II to work in our Arlington, VA office. This role is based in Arlington with only a one day per week requirement to be onsite with the rest of the week allowing for remote work.
Then sections:
Responsibilities
- Preparing and administering terms and conditions of Department of Defense Research & Development (FAR Part 35) contracts
- Assisting in the negotiation of contracts
- Preparing contract modifications
- Analyzing procurement policies and procedures
- Analyzing proposed costs and prices
- Preparing required contract file documentation per the FAR, DFARS, and other relevant policies/regulations
Requirements
` for prose - Do NOT repeat job title as heading (already shown) - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `
` or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Extract/Analyze Input Data:** Let's parse the input text: - "Zachary Piper Solutions is seeking a Contracts Specialist II to work in our Arlington, VA office. This role is based in Arlington with only a one day per week requirement to be onsite with the rest of the week allowing for remote work." - "Job Description: Responsibilities will include preparing and administering terms and conditions of Department of Defense Research & Development (FAR Part 35) contracts; Assisting in the negotiation of contracts; Preparing contract modifications; Analyzing procurement policies and procedures; Analyzing proposed costs and prices; Preparing required contract file documentation per the FAR, DFARS, and other relevant policies/regulations." - "Position is full-time at a Department of Defense research agency." - "Min. years of specialized contracting experience = 6+ years." - "Required Skills: Active DoD security clearance required. Bachelor’s degree6 years’ experience in government procurement including preparing cost proposals, negotiating terms and conditions of contracts, preparing contract modifications, administering contracts or subcontracts, and analyzing cost and prices." (Note: "Bachelor’s degree6 years’ experience" seems like a formatting glitch, probably "Bachelor’s degree" + "6 years’ experience") - "Desired Skills: Experience in government or commercial procurement (government preferred); contract administration and negotiation; cost and pricing analysis. DoD, Procurement Desktop Defense (PD2) contractual software, and R&D contracting experience a plus. Experience with Non-FAR based instruments such as Other Transaction Agreements, Grants, and/or Cooperative Agreements a plus but not required." - "Compensation: $120,000 - $140,000 dependant on experience" - "Competititve medical, dental, vision and 401K" (typo "Competititve") - "Keywords: DARPA, DOD, navy, intel, air force, acquisition, contracts, DFAR, contract specialist, procurement, secret clearance, top secret, TS/SCI, remote, hybrid" Now, I need to map these to the requested sections, following strict rules: - Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule - Must NOT create a section unless there's real specific content - Pay section only if posting actually states them → "$120,000 - $140,000 dependant on experience" → YES, create Pay - Schedule section only if stated → "full-time" and "one day per week requirement to be onsite with the rest of the week allowing for remote work" → Schedule info is there, but the heading options include "Schedule". I need to be careful: the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." Schedule is stated: full-time, one day onsite remote. I'll include Schedule if it has specific content. But let's see the exact headings allowed: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I should use what fits. I'll probably use: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But I need to check each: - Responsibilities: yes, detailed list - Requirements: the min 6+ years, bachelor's degree + 6 years exp, active DoD security clearance → I'll structure as Requirements or split into Qualifications/Skills. The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I need to decide mapping. Probably: Responsibilities, Requirements (combining min years, clearance, degree/experience), Qualifications (maybe overlap), Skills (desired skills). But rules: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So I must only create sections that have real content. I'll likely use: Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Or maybe Qualifications instead of Requirements? Let's see the input: "Min. years of specialized contracting experience = 6+ years. Required Skills: Active DoD security clearance required. Bachelor’s degree6 years’ experience in government procurement..." This is a mix of requirements and skills. I'll map: Responsibilities, Requirements (for the mandatory stuff: 6+ years, clearance, degree+exp), Skills (for desired skills), Benefits (medical, dental, vision, 401K), Pay (salary range), Schedule (full-time, 1 day onsite remote). I'll avoid creating a "Qualifications" section if it's redundant with Requirements, but the allowed headings include both. I'll pick one or the other, or split logically. Let's look at typical job posting structure: Responsibilities, Requirements/Qualifications, Skills, Benefits, Pay, Schedule. I'll use: Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. But I need to ensure each has real content and no placeholders.
Let's parse each section's content:
**Responsibilities** (from "Job Description:"):
- Preparing and administering terms and conditions of Department of Defense Research & Development (FAR Part 35) contracts
- Assisting in the negotiation of contracts
- Preparing contract modifications
- Analyzing procurement policies and procedures
- Analyzing proposed costs and prices
- Preparing required contract file documentation per the FAR, DFARS, and other relevant policies/regulations
**Requirements** (mandatory):
- 6+ years of specialized contracting experience
- Active DoD security clearance required
- Bachelor’s degree + 6 years’ experience in government procurement (the text says "Bachelor’s degree6 years’ experience" - I'll parse as Bachelor’s degree and 6 years’ experience)
- Position is full-time at a Department of Defense research agency
- Only one day per week onsite, rest remote (this is more about schedule/location, but I can include in Requirements or Schedule)
**Skills** (desired/optional):
- Experience in government or commercial procurement (government preferred)
- Contract administration and negotiation
- Cost and pricing analysis
- DoD Procurement Desktop Defense (PD2) contractual software
- R&D contracting experience
- Experience with Non-FAR based instruments such as Other Transaction Agreements, Grants, and/or Cooperative Agreements
**Benefits**:
- Competitive medical, dental, vision and 401K
**Pay**:
- $120,000 - $140,000 dependant on experience
**Schedule**:
- Full-time
- One day per week onsite, rest remote
Now, check rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them" → all three are stated, so I can include them. "Prefer a few substantive sections over many thin ones." I'll include: Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. That's 6 sections. Could I drop Schedule? It has specific content: full-time, 1 day onsite remote. I'll include it. Could I drop Qualifications? I'm not using a Qualifications heading; I'll use Requirements for mandatory, Skills for desired. The allowed headings list includes "Qualifications", but I don't have to use it if I use Requirements. The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It's not exhaustive but those are examples. I'll stick to the ones I have content for.
Important: "Do NOT repeat the job title as a heading (the page already shows it)" → I won't include a heading for the job title.
"Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." → No job ID in input, but there's company name and location info at top. I'll fold company/location into a
maybe, or just start with sections. The rule says output ONLY the HTML fragment, no /. I can have top-level text outside sections? Probably better to include the introductory sentence about company/role as a
before sections, but careful: "Do NOT repeat the job title as a heading (the page already shows it)" - the job title is "Contracts Specialist II". I won't use an
for it. I might include the company/location as a
at the top, but the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't explicitly say to remove company/location, but "fold minor metadata into a short
or drop it." I'll put company and location in a brief
at the start, or maybe just start with sections. Let's see: "Zachary Piper Solutions is seeking a Contracts Specialist II to work in our Arlington, VA office. This role is based in Arlington with only a one day per week requirement to be onsite with the rest of the week allowing for remote work." This is introductory. I'll put it as a
at the top, maybe without the job title repeated. Actually, the job title is "Contracts Specialist II". I won't wrap it in a heading. I'll just have the prose. Let's structure:
Zachary Piper Solutions is seeking a Contracts Specialist II to work in our Arlington, VA office. This role is based in Arlington with only a one day per week requirement to be onsite with the rest of the week allowing for remote work.
Then sections:Responsibilities
- Preparing and administering terms and conditions of Department of Defense Research & Development (FAR Part 35) contracts
- Assisting in the negotiation of contracts
- Preparing contract modifications
- Analyzing procurement policies and procedures
- Analyzing proposed costs and prices
- Preparing required contract file documentation per the FAR, DFARS, and other relevant policies/regulations