Chinese Language Instructor

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Ready to Make an Impact?" etc? That's maybe part of description but not a section heading; we can keep as prose under appropriate section (maybe About the role). We need to decide sections. Let's parse content: - Intro paragraph: "Chinese Instructor Looking for an opportunity to make an impact? Unleash your potential at Leidos..." This is about the role/company. Could be "About the role" or "About Leidos". There's also later "About Leidos" section with description of company. We'll include an "About the role" maybe summarizing the mission-driven environment. But we must not invent filler. We have actual content: "Take Your Expertise to the Next Level – Join Leidos as a Chinese Language Instructor Are you a seasoned Language Instructor ready to elevate your career and make a meaningful impact? The Leidos Intel Sector is actively seeking a highly skilled and motivated Chinese Instructor to support a critical national security mission. This is not just another teaching job—it’s an opportunity to apply your expertise in language, culture, and pedagogy in a dynamic and mission-driven environment. We're looking for a passionate professional with a strong foundation in foreign language instruction, advanced knowledge of adult learning methodologies, and a commitment to excellence. You will play a key role in delivering language training, conducting proficiency testing, and shaping the next generation of linguistically prepared professionals." That's substantive. Could go under "About the role". - "Why Join Leidos?" bullet list: "Be part of a mission-focused team serving national security priorities. Leverage your linguistic and cultural fluency to shape high-impact training. Grow your career in a supportive environment with opportunities for advancement and professional development." That's benefits? Could be under "Benefits" or "Why Join Leidos". But we have a Benefits section later with generic benefits. The "Why Join Leidos" is more like benefits/advantages. We could treat as "Benefits". However we also have a later "Pay And Benefits" section with generic benefits. We need to include only if posting actually states them. The posting does state benefits: "Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." That's specific enough. So we can include Benefits section with that list. - Responsibilities: list after "Responsibilities Include As a Language Instructor, you will:" then bullet points (though not formatted as list but sentences separated by periods). We need to convert to

• . Must preserve all substantive info. Let's extract each responsibility: 1. Deliver 3–5 hours of daily instruction in courses ranging from ILR levels 0–3. 2. Complete training and become a certified language tester, with expectations to conduct 3–4 language proficiency assessments weekly. 3. The position is responsible for instructing students in speaking a foreign language and understanding the culture of the area or country to teach culture through communication. 4. Instructors must be able to develop class materials and training aids to meet customized student needs. 5. The contract linguist instructor(s) shall have strong foreign language skills and will work under the direction of experienced senior trained instructors. 6. It is also important that candidates are familiar with current events in the countries where the foreign languages are spoken. 7. Once on the program, contract linguist instructors are required to receive specific sponsor training focusing on foreign language teaching and foreign language testing in order to become certified according to Sponsor standards. We'll put these as
• . - Required Qualifications: list after "Required Qualifications Bachelor’s degree in education, foreign language, or linguistics with 8– 12 years of prior relevant experience or Master’s degree with 2 – 10 years of prior relevant experience. Additional years of experience may be substituted in lieu of a degree.Minimum of 10 years of adult teaching experience.Team Teaching experience a plus.Must score 90% or higher on the English test.Must score Senior level.Degree must be obtained either in the U.S. or in a country where the target language is natively spoken.Proficient in MS Office and basic internet research.Excellent communication and presentation skills in both English and the foreign language.Travel 0-10%" We need to parse into items. Could be multiple sentences. Let's break: - Bachelor’s degree in education, foreign language, or linguistics with 8–12 years of prior relevant experience or Master’s degree with 2–10 years of prior relevant experience. Additional years of experience may be substituted in lieu of a degree. - Minimum of 10 years of adult teaching experience. - Team Teaching experience a plus. - Must score 90% or higher on the English test. - Must score Senior level. - Degree must be obtained either in the U.S. or in a country where the target language is natively spoken. - Proficient in MS Office and basic internet research. - Excellent communication and presentation skills in both English and the foreign language. - Travel 0-10% We'll put as
  • . - Language Proficiency Requirements: "Must pass a LEIDOS/ accepted commercial testing vendors-administered translation test (3 hours) with a score of 4 or higher. Must achieve a minimum of 5/5/5 in speaking, listening, and reading on standard ILR scale." We could include under Requirements or Qualifications? It's separate. Could be its own section "Language Proficiency Requirements". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Language Proficiency Requirements" could fit under Requirements or Qualifications. Since it's a requirement, we can put under Requirements. We'll create a
    under Requirements for these two items. - Security Clearance Requirement: "An active TS/SCI security clearance with a polygraph. Candidates must also be eligible for a security clearance upgrade.Clearance must be fully adjudicated before starting. Linguists can only begin work on contract with a fully adjudicated security clearance." That's also a requirement. Could be under Requirements as well. - Preferred Qualifications: list after "Preferred Qualifications Experience within the U.S. Intelligence Community, military, or law enforcement.Ability to communicate fluently and professionally in multiple languages is highly desirable.Prior exposure to cryptologic or national security environments a plus.Linguists who are proficient in multiple languages are strongly desired." We could put under Qualifications? Actually "Preferred Qualifications" is a separate heading but not in allowed list; we could incorporate into Qualifications section as part of it, maybe as a sublist? But we must not invent headings not allowed. We could add a
    under Qualifications for preferred qualifications, labeling maybe as "Preferred Qualifications" inside

    ? But we must not create new headings. We could just include them as part of Qualifications

    items, maybe preceded by a

    stating "Preferred qualifications:" but that's extra text not a heading. That's okay as long as we don't create a heading. We'll include them as

    • items under Qualifications, maybe with a note. - Pay Range: "Pay Range Pay Range $92,300.00 - $166,850.00 The Leidos pay range for this job level is a general guideline onlyand not a guarantee of compensation or salary. Additional factors considered in extending an offer include (but are not limited to) responsibilities of the job, education, experience, knowledge, skills, and abilities, as well as internal equity, alignment with market data, applicable bargaining agreement (if any), or other law." We need to include Pay section only if posting actually states them. Yes, they state pay range. So we will create a

      Pay

      with a

      containing that info. We should not repeat "Pay Range" twice. We'll just include the range and note. - Benefits: we have "Pay And Benefits Pay and benefits are fundamental to any career decision. That's why we craft compensation packages that reflect the importance of the work we do for our customers. Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details are available at www.leidos.com/careers/pay-benefits." We'll create Benefits section with a

      of those benefits: competitive compensation, Health and Wellness programs, Income Protection, Paid Leave, Retirement. Also maybe note that more details available at link but we might consider that as boilerplate? It's not navigation/legal; it's a link to more details. Could keep as

      after list. - About Leidos: there is a paragraph about Leidos company. Could be under About the role or maybe a separate "About Leidos" but not in allowed headings. We could incorporate into About the role section as a

      . The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use About the role heading to cover both role description and company overview. That's fine. - Schedule: not mentioned. No schedule info. So we omit Schedule. - Skills: not explicitly listed as a section; we have some skills like MS Office, communication, etc. Those are in qualifications. Could we create a Skills section? The posting does not have a dedicated "Skills" heading, but we could extract skills and put under Skills heading if we want. However instruction: "Prefer a few substantive sections over many thin ones." So we might avoid creating a Skills section if we can fold into Qualifications. We'll keep Qualifications includes skills. - Requirements: we will include language proficiency and security clearance. Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Original Posting September 15, 2026", "For U.S. Positions: While subject to change..." etc. Also remove "Ready to Make an Impact? This is more than a job—it's a mission..." etc? That's maybe part of description but not boilerplate; we can keep as prose under About the role. However the phrase "Ready to Make an Impact? This is more than a job—it's a mission. If you're driven, qualified, and passionate about language education and national service, we want to hear from you. Submit your resume today and embark on a rewarding career that truly matters." That's basically a call to action (application instructions). According to rules, we must remove application instructions. So we should remove that call to action. Also remove "At Leidos, the opportunities are boundless. We challenge our staff with interesting assignments that provide them with an opportunity to thrive, professionally and personally. For us, helping you grow your career is good business. We’re excited to learn more about you, apply today! #MSBA". That's also application encouragement. Remove. Also remove "If you're looking for comfort, keep scrolling. At Leidos, we outthink, outbuild, and outpace the status quo — because the mission demands it. We're not hiring followers. We're recruiting the ones who disrupt, provoke, and refuse to fail. Step 10 is ancient history. We're already at step 30 — and moving faster than anyone else dares." That's fluff but maybe considered boilerplate? It's not navigation/legal/EEO etc. It's still promotional but not a specific section. Might be considered filler; but it's substantive? It's more marketing fluff. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This fluff is not explicitly listed; but it