Head of Contracts

We need to output HTML fragment with sections: About the role? The posting includes "Position Overview" which is like overview. Could map to "About the role". Then sections: Responsibilities, Requirements (maybe combine Required Qualifications and Preferred Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have content for About the role (Position Overview). Responsibilities (list). Requirements: we have Required Qualifications (Experience, Education/Certification, Skills). Also Preferred Qualifications. Could combine into Requirements and Preferred Qualifications? But headings list includes Requirements, Qualifications, Skills. We could have Requirements (Experience/Education), Qualifications (Preferred), Skills (maybe separate). However we have Skills listed under Required Qualifications. Could put Skills as separate section. But we must not create thin sections. Let's see: We have Responsibilities (multiple bullet points). We have Required Qualifications (Experience, Education/Certification, Skills). We have Preferred Qualifications (list). We have Benefits (What We Offer). We have Location & Commitments (maybe Schedule? Not exactly schedule but location and work arrangement). We have Clearance Level (maybe part of Requirements). We have Work Hours (maybe Schedule). The instruction: include Pay/Schedule/Benefits sections only if posting actually states them. We have Benefits (What We Offer) includes competitive salary, health benefits, PTO, etc. So Benefits section is appropriate. Pay: they mention competitive salary and discretionary bonuses but not specific numbers. That's still mention of pay. Should we include Pay? The instruction: 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. They do state competitive salary and discretionary bonuses, which is specific enough? It's not a number but it's stating they offer competitive salary and bonuses. That's still stating pay. I'd include Pay section with that sentence. Schedule: they mention Work Hours: typical workday eight hours, forty-hour workweek, flexibility. That's schedule info. So we can include Schedule section. We also have Location & Commitments: could be part of Schedule or separate? Not in headings list. Could fold into Schedule or maybe omit. But we have location info; maybe we can include under Schedule? Not ideal. Could create a separate section like "Location" but not in allowed headings. 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, not exclusive? Probably we should stick to those headings. So we need to map content to those headings. Location could go under Schedule? Not great. Could omit location? But we must preserve ALL substantive information. So we need to include location info somewhere. Could put under About the role? Or under Responsibilities? Not appropriate. Maybe we can create a section "Location" but not in list; risk. However instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It may be okay to use other headings if needed, but they gave examples. Safer to stick to those. Could we incorporate location into Schedule? Schedule includes work arrangement (hybrid) and location preference. Could combine. Thus sections: - About the role (Position Overview) - Responsibilities - Requirements (maybe include Required Qualifications: Experience, Education/Certification, Clearance) - Qualifications (Preferred Qualifications) - Skills (maybe separate but we already have skills under Required; could move skills to Skills section) - Benefits (What We Offer) - Pay (competitive salary and discretionary bonuses) - Schedule (Work Hours, Hybrid arrangement, location preference, travel) We must not repeat job title as heading. Good. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to keep details like specific contract types, FAR, DFARS, etc. We must remove boilerplate: EEO, equal opportunity, scam warning, navigation, cookie, legal, duplicated lines, application instructions. At end there is EEO statement, E-Verify, accommodation contact. Remove those. Also remove "Note: To obtain a security clearance, you must be a U.S. citizen and meet the 13 adjudicative guidelines." That's part of Clearance Level; keep clearance requirement but maybe drop note? It's substantive? It's about clearance; we can keep clearance requirement but maybe drop the note as it's explanatory but still substantive? Might be okay to keep. But we can keep the clearance line. We must not include duplicated lines. Now craft HTML. Structure:

  About the role

  Position Overview ...

  Responsibilities

  • ...
  ...

  Requirements

  Maybe combine Experience and Education/Certification and Clearance.

  But we need lists for duties/requirements/benefits. For Requirements we could list experience items as
  . Education/Certification as
  . Could also separate. Better: Use
  for each list. Thus:

  Requirements

  • Minimum of 10 years of progressively responsible experience in federal government contracts.
  • Experience supporting Department of Defense and/or other federal government contracting organizations.
  • Demonstrated experience with federal prime contracts, subcontracts, teaming agreements, NDAs, and related agreements.
  • Experience working with multiple federal contract types, including FFP, T&M, cost-reimbursement, IDIQ, and task-order environments.
  • Bachelor’s degree or equivalent combination of education and relevant experience.
  • Current or ability to obtain a Department of Defense (DoD) clearance.
  Then Skills section:

  Skills

  • Strong working knowledge of FAR, DFARS, and federal procurement requirements.
  • Strong contract review, interpretation, drafting, and negotiation skills.
  • Ability to identify contractual and compliance risks and provide practical recommendations.
  • Ability to work independently and manage complex contractual matters with appropriate judgment.
  • Strong written and verbal communication skills, including the ability to explain complex contractual and acquisition matters clearly to business leaders and other stakeholders.
  • Ability to work effectively across Business Development, Delivery, Finance, Technology, and other areas of the business.
  Qualifications (Preferred):

  Qualifications

  • 15 or more years of federal government contracts or acquisition experience.
  • Juris Doctor (JD) or prior experience supporting government contracts in a legal capacity.
  • Prior experience with a federal government contractor, federal agency, or law firm supporting government contractors.
  • Prior experience as a federal Contracting Officer, acquisition professional, government contracts attorney, or senior contracts professional.
  • DAWIA certification, NCMA credential, or comparable federal acquisition certification.
  • Navy and/or Department of Defense contracting experience.
  • Experience supporting small businesses participating in federal socioeconomic programs.
  • Experience supporting contract-related due diligence, novation's, organizational conflicts of interest, or other complex federal contracting matters.
  • Experience with intellectual property, technical data rights, software licensing, SaaS, or commercial technology agreements.
  • Familiarity with CMMC and federal cybersecurity contractual requirements.
  • Experience establishing or improving Contracts processes, systems, and procedures.
  Benefits:

  Benefits

  • Competitive salary and discretionary bonuses.
  • Comprehensive health benefits, including medical, dental, and vision insurance.
  • Flexible Paid Time Off (PTO) and holidays to help you maintain a healthy work-life balance.
  • Opportunities for professional development and continued learning.
  • Hybrid/remote work arrangement with flexible hours.
  • 401(k) retirement plan with company match.
  • Employee recognition programs and company events.
  Pay: Actually we already included competitive salary in Benefits. But we could separate Pay. However Benefits already includes that line. To avoid duplication, maybe we keep Pay separate with just competitive salary and discretionary bonuses, and Benefits without that line. But Benefits list includes many items; we could keep Pay separate and Benefits without salary line. Let's do that. Thus Pay:

  Pay

  • Competitive salary and discretionary bonuses.
  Benefits (excluding salary):

  Benefits

  • Comprehensive health benefits, including medical, dental, and vision insurance.
  • Flexible Paid Time Off (PTO) and holidays to help you maintain a healthy work-life balance.
  • Opportunities for professional development and continued learning.
  • Hybrid/remote work arrangement with flexible hours.
  • 401(k) retirement plan with company match.
  • Employee recognition programs and company events.
  Schedule:

  Schedule

  • Position: Full Time
  • Work Arrangement: Hybrid – Employees who live more than 50 miles from JMA’s Mechanicsburg, Pennsylvania headquarters are required to work onsite one week per month.
  • Travel Requirements: May be required
  • Location Preference: Prefer candidates within a 50-mile radius of Mechanicsburg, Pennsylvania.
  • Work Hours: A typical workday consists of eight hours, totaling a forty-hour workweek. We understand that there may be times when employees will need to adjust their work hours due to client needs or personal reasons. To help balance these demands, we offer some flexibility in work schedules.
  We need to ensure we didn't repeat job title. Good. Now check for any boilerplate left: We removed EEO, E-Verify, accommodation contact. Also removed "Note: To obtain a security clearance, you must be a U.S. citizen and meet the 13 adjudicative guidelines." We kept clearance line but maybe we should keep the note? It's part of clearance requirement; but it's not essential. Might be okay to keep but it's extra detail. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The note is substantive about clearance eligibility. I'd keep it as part of clearance bullet maybe: "Current or ability to obtain a Department of Defense (DoD) clearance (Note: To obtain a security clearance, you must be a U.S. citizen and meet the 13 adjudicative guidelines)." That preserves detail. Thus adjust clearance bullet. Now ensure we didn't include any duplicated lines. Look at responsibilities list: we need to copy all responsibilities from posting. Let's extract responsibilities bullet points from posting: - Serve as JMA’s primary contracts resource for significant contractual matters involving federal customers, prime contractors, subcontractors, and teaming partners. - Review solicitations and proposal terms and identify contractual requirements and risks before submission. - Draft, review, negotiate, and administer prime contracts, subcontracts, task orders, modifications, teaming agreements, NDAs, and related agreements. - Manage contract activities throughout the lifecycle, including award, funding, scope changes, options, amendments, disputes, and closeout. - Provide guidance on FAR, DFARS, agency supplements, flow-down requirements, cost and pricing requirements, and other federal contracting requirements. - Support audits, fact-finding, government reviews, and contract-related compliance inquiries while maintaining complete and