Contract Specialist III

Here's a thinking process: 1. **Analyze User Input:** - User wants me to reformat job posting(s) into clean, well-structured semantic HTML. - Rules specified: use `

` for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use `

• ` for lists. Use `

  ` for prose. - Do NOT repeat job title as heading (page already shows it). - Do NOT put Job ID / requisition numbers as headings. - 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. **Identify the Source Material:** The user pasted what appears to be multiple job postings or a combined/messy text. Let me parse it carefully. Text structure: - "Zachary Piper Solutions is seeking a Contracts Specialist III to work in our Arlington, VA office. This role is based in Arlington with a one day per week onsite requirement allowing for the rest of the week to be 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 = 12+ years. Required Skills: Active DoD security clearance required. Bachelor’s degree and a minimum of 12+ years of 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. 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. ECS is seeking a Contracts Specialist III to work in our Arlington, VA office. [Same text repeats]... ECS is seeking a Contracts Specialist III to work in our Arlington, VA office. [Repeats again]... Compensation: $135,000 - $175,000 based on experience Competitive medical, dental, vision and 401K Keywords: Acquisition, DOD, Federal, navy, army, Air force, airforce, AF, FAR, procurement, contracting, negiotation, grants, research, administer, administration, DARPA, excel, analysis, DFAR, D-FAR" Wait, there are three entities mentioned: Zachary Piper Solutions, ECS (appears twice). The job description text is identical for all. The compensation and keywords appear at the very end, likely from the last posting or a combined footer. Let me extract the unique parts: - Company 1: Zachary Piper Solutions - Company 2: ECS (appears 3 times, probably a copy-paste error) - Location: Arlington, VA - Onsite: 1 day per week remote otherwise - Job Description content (repeated verbatim): * Responsibilities: preparing and administering terms and conditions of DoD R&D (FAR Part 35) contracts; assisting in negotiation of contracts; preparing contract modifications; analyzing procurement policies and procedures; analyzing proposed costs and prices; preparing required contract file documentation per FAR, DFARS, and other relevant policies/regulations. * Position: full-time at a DoD research agency. * Min. years of specialized contracting experience = 12+ years. - Required Skills: Active DoD security clearance required. Bachelor’s degree and a minimum of 12+ years of 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. - 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: $135,000 - $175,000 based on experience - Benefits mentioned: Competitive medical, dental, vision and 401K (from the end, likely part of the posting) - Keywords at the end: Acquisition, DOD, Federal, navy, army, Air force, airforce, AF, FAR, procurement, contracting, negiotation, grants, research, administer, administration, DARPA, excel, analysis, DFAR, D-FAR I need to be careful: The user says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." There are duplicated lines here (the same job description repeated 3 times for different companies). I should deduplicate, keeping one instance of each unique section. Also: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text... and never create Pay/Schedule/Benefits sections unless the posting actually states them." Let's check what content is present for each intended section: - About the role: Not explicitly a separate "About the role" heading, but there's company name and location/remote info. I could fold that into a brief intro or "About the role" if there's substance. The rule says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But also: "Do NOT repeat the job title as a heading (the page already shows it)". I should not create an "About the role" heading if there's no specific "About the role" text, but there is company info and role details. I think I can create an "About the role" section with the company name, location, remote info, and job summary. But wait: the rule says "include a section ONLY when the posting has real, specific content for it". There's no explicit "About the role" paragraph, but there is company name and role description. I'll likely fold it into a short intro or handle it carefully. Let me re-read: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists examples, not an exhaustive mandate. I should only create sections that have real content. The posting has: company, location, remote setup, job description, min experience, required skills, desired skills, compensation, benefits (medical, dental, vision, 401k), keywords. I need to map these to the section headings appropriately. Let's list what content maps to what: - Responsibilities: clear -> "Responsibilities" section - Min. years of specialized contracting experience = 12+ years: this is a requirement. Could go under "Requirements" or "Qualifications". The headings listed: Requirements, Qualifications. I'll see. Typically, years of experience is a requirement/qualification. - Required Skills: Active DoD security clearance required. Bachelor’s degree and a minimum of 12+ years of experience... -> This is "Required Skills/Qualifications" - Desired Skills: Experience in government or commercial procurement... -> "Skills" or "Desired Skills" - Compensation: $135,000 - $175,000 based on experience -> "Pay" section (must have real content, which it does) - Competitive medical, dental, vision and 401K -> "Benefits" section (has real content) - Schedule: "This role is based in Arlington with a one day per week onsite requirement allowing for the rest of the week to be remote work." -> "Schedule" section could cover this, but the rule says never create Pay/Schedule/Benefits unless posting actually states them. It does state the onsite requirement, so I can include a Schedule section with that info. Or fold it into Responsibilities or a general intro. The heading "Schedule" is listed as an example. I'll consider if it's needed. The posting specifies "one day per week onsite requirement allowing for the rest of the week to be remote work." That's schedule info. I'll include a Schedule section with that specific info. - Keywords at the end: probably not needed as a section, or could be folded. The rule says remove boilerplate, duplicated lines, application instructions. Keywords might be considered meta, but they have substantive content. I'll likely not create a separate "Keywords" section unless it's requested, but the user didn't list Keywords as a required section heading. The listed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I'll stick to those or similar, but only when there's content. Let's re-evaluate the headings based on actual content present in the posting: - "About the role": Not explicitly stated as a separate section, but we have company name and role summary. I could create an "About the role" section with the company, location, and remote setup. But the rule says "include a section ONLY when the posting has real, specific content for it". There's no formal "About the role" paragraph, but the combination of company name + location + remote description is specific content. I'll probably include it as a brief intro or fold into another section. To be safe, I might not create an "About the role" heading if there's no dedicated "About the role" text. However, the user gave examples of headings. I think I should create sections that directly correspond to the extracted content. Let's map: * Responsibilities -> "Responsibilities" * Min 12+ years experience -> "Requirements" or "Qualifications" * Required Skills -> "Required Skills" (but the heading list has "Skills" and "Qualifications" separate). I'll use "Requirements" for the degree/experience part, and "Skills" for the skill sets. * Desired Skills -> "Skills" (or "Desired Skills" as a subsection, but I'll keep it simple) * Compensation -> "Pay" * Medical, dental, vision, 401K -> "Benefits" * One day per week onsite -> "Schedule" * The company name and job title are already not to be repeated as headings. The job title is "Contracts Specialist III". I won't use it as a heading. Let's structure the HTML fragment carefully. First, deduplicate the content. The same job description appears for Zachary Piper Solutions and ECS three times. I'll take the unique content once. The compensation and benefits seem attached to the last instance. I'll assume it's one posting with multiple company names, but I'll dedupe to the unique content. Extracted content (deduplicated): - Company