IT Associate TS/SCI with Security Clearance

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections that have real, specific content. The rules say: - Use

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

• for lists,

  for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Fold minor metadata into short

  or drop it - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content for it - Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's parse the job posting: 1. Company description/values: "We believe that every person... And we're looking for motivated people who share those values!" - This could be "About the role" or "About the company". But the rule says "About the role" is a heading. However, this seems more like company description. Might fit under "About the role" or maybe a general intro paragraph. 2. "ACTIVE TS/SCI CLEARANCE REQUIRED TO BE CONSIDERED FOR THIS POSITION" - This is a requirement, could be in Requirements or Qualifications. 3. "As an IT Associate TS/SCI, you will be responsible for providing guidance and developing, and maintaining IT strategy and tasks to support the Government Customer. Approximately 100 open positions available. Salary can range from $80K-$160K dependent on experience and skill level." - This is about the role, includes pay info. Pay is mentioned: "Salary can range from $80K-$160K dependent on experience and skill level." That's specific, so we can include a Pay section. 4. Responsibilities: "Various, depending on specific position Interact with clients at all levels and perform duties under rigid deadlines; perform work with excellent interpersonal and communication skills Please visit TENICA’s website for specific job descriptions and responsibilities" - This is a list of responsibilities, but note "Various, depending on specific position" and "Please visit TENICA’s website..." The latter is an application instruction? Actually it's directing to website for specific job descriptions. That might be considered application instruction or just a note. The rule says remove application instructions. But "Please visit TENICA’s website for specific job descriptions and responsibilities" could be considered a note about where to find more details. Might be considered boilerplate? I think we should keep the responsibilities that are listed: "Interact with clients at all levels and perform duties under rigid deadlines; perform work with excellent interpersonal and communication skills". The "Various, depending on specific position" is vague but still content. We'll include as list items. 5. Qualifications: "Education and/or Experience : Junior to Senior level positions available, depending on experience Bachelor’s Degree Active TS/SCI w/CI Poly" - This is qualifications. 6. Requirements/Abilities: "Strong background in IT Familiarity with IC ITE a plus Strong analytic skills Excellent customer-facing skills" - This is requirements/skills. 7. Job Type: Full-time - This is schedule? Could be Schedule section. 8. Job Location: Chantilly, VA - Location, could be in a short p or maybe Schedule? Not a heading. 9. Required education: Bachelor's or equivalent experience - Already in qualifications. 10. Required experience: list of skills with years - This is requirements. 11. Required license or certification: MUST HAVE Active TS/SCI w/CI Poly - Already mentioned. 12. Company description: "TENICA and Associates LLC is a provider..." - This is company boilerplate, maybe we can include as "About the company" but the rule says "About the role" heading. The company description is not about the role. Might be considered boilerplate? The rule says remove EEO/equal-opportunity boilerplate. The last paragraph is EEO statement: "TENICA is an Equal Opportunity Employer..." That should be removed. Also "www.TENICA.biz." is a website, maybe not needed. We need to decide which sections to include. The posting has: - About the role (description, clearance requirement, number of positions, salary range) - Responsibilities (list) - Qualifications (education, clearance) - Requirements/Abilities (skills) - Pay (salary range) - Schedule (Job Type: Full-time) - Location (Chantilly, VA) - maybe include in a short p under About the role or separate? Not a heading. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Pay is stated: "Salary can range from $80K-$160K dependent on experience and skill level." So include Pay section. Schedule: "Job Type: Full-time" is stated, so include Schedule section. Benefits: not mentioned, so no Benefits section. Also "Approximately 100 open positions available." That's metadata, maybe include in About the role. Now, we must not repeat job title as heading. The job title is "IT Associate TS/SCI" (implied). The page already shows it, so we don't need an h3 for that. We'll structure:

  About the role

  ... description ...

  ACTIVE TS/SCI CLEARANCE REQUIRED TO BE CONSIDERED FOR THIS POSITION

  Approximately 100 open positions available.

  Responsibilities

  • Various, depending on specific position
  • Interact with clients at all levels and perform duties under rigid deadlines
  • Perform work with excellent interpersonal and communication skills

  Qualifications

  • Junior to Senior level positions available, depending on experience
  • Bachelor’s Degree
  • Active TS/SCI w/CI Poly

  Requirements

  • Strong background in IT
  • Familiarity with IC ITE a plus
  • Strong analytic skills
  • Excellent customer-facing skills
  • Customer-facing skills: 2 years
  • Strong analytical skills: 2 years
  • Familiarity with IC ITE: 2 years
  • Strong background in IT: 2 years
  But note: The "Required experience" list duplicates some of the requirements. We should preserve all substantive information. The posting has "Requirements/Abilities:" and then "Required experience:" with years. We can combine or keep separate. The rule says preserve ALL substantive information. So we should include both. However, the "Requirements/Abilities" list includes "Strong background in IT", "Familiarity with IC ITE a plus", "Strong analytic skills", "Excellent customer-facing skills". The "Required experience" list adds years. We can merge them into one Requirements section with sub-lists? But we only have
  • . Could do nested lists? The rule doesn't forbid nested lists, but it says use
    • for any list. Could do a list with sub-items. But simpler: combine into one list with each item including years where specified. However, the "Requirements/Abilities" doesn't have years, but "Required experience" does. They are separate sections in the posting. We could have two subsections: "Requirements" and "Experience Requirements". But the rule says prefer few substantive sections over many thin ones. Maybe combine into one Requirements section with two lists? But we can't have two
      under same heading without separation. Could do:

      Requirements

      Abilities:

      • Strong background in IT
      • Familiarity with IC ITE a plus
      • Strong analytic skills
      • Excellent customer-facing skills

      Required experience:

      • Customer-facing skills: 2 years
      • Strong analytical skills: 2 years
      • Familiarity with IC ITE: 2 years
      • Strong background in IT: 2 years
      That's acceptable. Now Pay section:

      Pay

      Salary range: $80K–$160K, dependent on experience and skill level.

      Schedule section:

      Schedule

      Full-time

      Location: Could be included in About the role or a separate short p. Not a heading. Company description: The paragraph about TENICA is company info. Could be under "About the company" but the rule only lists specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the company" is not listed. Might be considered boilerplate? The rule says remove boilerplate. The company description is marketing, but it's part of the posting. However, the rule says "Preserve ALL substantive information". The company description is substantive? It describes the employer. But the rule also says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The company description is not exactly boilerplate, but it's not about the role. The user might expect it to be included? The example headings don't include "About the company". I think we can include it as a paragraph under "About the role" or maybe a separate "About the company" heading? But the rule says 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 exhaustive. But we should stick to those. The company description could be folded into a short

      at the top. However, the rule says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it." Company description is not minor metadata. But it's not about the role. I'll include it as a paragraph under "About the role" maybe. Also the EEO statement at the end should be removed. Now, the "Please visit TENICA’s website for specific job descriptions and responsibilities" is an application instruction? It's directing to website for more details. That could be considered application instruction. The rule says remove application instructions. So we should drop that line. Also "Job Type: Full-time" and "Job Location: Chantilly, VA" are metadata. We'll include Job Type in Schedule, Location in About the role. Now, let's write the HTML. We'll start with About the role:

      About the role

      We believe that every person, given the opportunity and the tools, is capable of achieving great things. Our team members focus on our customers and assisting them achieve their mission and goals. Our leadership nurtures our team’s potential by treating each employee with honesty, integrity, respect, dignity, compassion and fairness. And we’re looking for motivated people who share those values!

      ACTIVE TS/SCI CLEARANCE REQUIRED TO BE CONSIDERED FOR THIS POSITION

      As an