Co-Op, Contracts Spring 2027

We need to output HTML fragment with sections: h3 headings for sections present: About the role? The description includes "Job Description:" but we shouldn't repeat job title. We need sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. Let's parse content: - About the role: The first paragraph describes mission, opportunity, location, term, function. Could be "About the role". We'll put that as

About the role

then

... content. - Responsibilities: list of duties: Review contract terms, Conduct pre-contract risk analysis, Assist with administration..., Participate in contract reviews..., Support contract closeout activities, Prepare and deliver presentations, Participate in team-building activities, Conduct legal and contractual research, Manage contract databases. Use

• . - Compensation Range: $18.24 - $23.31 per hour. Also sign-on bonus for housing. So we have Pay section. Also maybe Benefits: sign-on bonus? Could be Benefits. But we have Pay and maybe Benefits separate. The instruction: include Pay/Schedule/Benefits only if posting actually states them. We have Pay (compensation range). Benefits: sign-on bonus to offset housing expenses. That's a benefit. So we can have Benefits section. - Schedule: The assignment is for Winter/Spring 2027 term (January through early May, part-time). That's schedule info. So we can have Schedule section. - Requirements/Qualifications/Skills: There's "Skills and Experience: Required Qualifications:" list. Also "Preferred Qualifications:" list. Also Citizenship Requirements, Drug-Free Workplaces. Those could be under Requirements or Qualifications. We need to decide sections: Could combine Requirements and Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple: Requirements, Qualifications, Skills. But we must not create thin sections. We have required qualifications list, preferred qualifications list, skills (like proficiency with MS Office, etc). Could split: Requirements (citizenship, drug screen), Qualifications (required and preferred), Skills (maybe technical skills). However we need to avoid filler. Let's think: The posting includes "Skills and Experience:" then "Required Qualifications:" list, then "Preferred Qualifications:" list. Also "Citizenship Requirements:" and "Drug-Free Workplaces:" which are more like requirements. Could combine all under "Requirements". But we also have "Skills" maybe separate for technical skills like Oracle, SharePoint, JIRA, MS Office. However the required qualifications list includes "Strong attention to detail..." etc which are skills. Might be better to have sections: Requirements (citizenship, drug screen), Qualifications (required and preferred), Skills (technical). But we need to ensure we don't create sections with just placeholder text. Let's extract content: About the role paragraph: "At Saab, Inc., we constantly look ahead and push the boundaries of what is considered technically possible. We collaborate with colleagues around the world who share our mission: to make the world a safer place. Build your resume and enhance your marketability with real-world, hands-on experience through a Co-Op/Internship opportunity! Saab is seeking motivated and enthusiastic business, economics, law, or finance students interested in putting their studies into practice. This Co-Op/Internship opportunity is available at one of our East Syracuse, NY locations. This assignment is for the Winter/Spring 2027 term (January through early May, part-time). As part of the Contracts/Legal function, you will work with our Contracts Professionals to support the provision of products and services to our U.S. Government, commercial, and international customers as part of a larger program execution team." We could split schedule info out, but it's in that paragraph. However schedule section will contain that detail; we could still keep About the role without schedule details, but we might duplicate. Better to keep About the role generic, and schedule separate. Thus About the role: first two sentences about mission, opportunity, seeking students, location, function. We'll exclude schedule sentence. Let's craft About the role: "At Saab, Inc., we constantly look ahead and push the boundaries of what is considered technically possible. We collaborate with colleagues around the world who share our mission: to make the world a safer place. Build your resume and enhance your marketability with real-world, hands-on experience through a Co-Op/Internship opportunity! Saab is seeking motivated and enthusiastic business, economics, law, or finance students interested in putting their studies into practice. This Co-Op/Internship opportunity is available at one of our East Syracuse, NY locations. As part of the Contracts/Legal function, you will work with our Contracts Professionals to support the provision of products and services to our U.S. Government, commercial, and international customers as part of a larger program execution team." Now Responsibilities list as given. Now Requirements: Could include Citizenship Requirements and Drug-Free Workplaces. Also maybe "Must be a U.S. citizen. Applicants selected may be subject to a government security investigation and must meet eligibility requirements for access to classified information." and "As a condition of employment, candidates will be required to pass a pre-employment drug screen." Also maybe "Enrollment in an accredited undergraduate or graduate degree program with a major in Business, Law, or a related discipline." etc are qualifications. But we have Qualifications section for those. Thus Requirements section: citizenship and drug screen. Now Qualifications: Required Qualifications list and Preferred Qualifications list. Now Skills: Could include technical skills: Experience working with Oracle, SharePoint, JIRA, or similar systems. Proficiency with Microsoft Office Suite. Strong written and verbal communication skills (though that's also in required). But we can put those under Skills. But we must avoid duplication. The required qualifications already includes "Strong attention to detail. Ability to prepare, organize, and maintain contract records and files. Strong time management and task prioritization skills. Proactive communication skills. Willingness to learn and take on new challenges. Strong teamwork and communication skills." That's skills. So maybe we should not duplicate. Instead we could have Qualifications (required and preferred) and Skills (technical). Let's see: The posting has "Skills and Experience:" heading then Required Qualifications, Preferred Qualifications. So maybe we treat "Skills and Experience" as Skills section, and within it we have required and preferred qualifications. But the instruction says we can use Skills heading. So we could have

  Skills

  and then list required and preferred qualifications as sub-lists? But we need to use
  • for any list. Could have nested lists? Probably okay to have separate
    for required and preferred. Thus we could have Skills section containing both required and preferred qualifications. Then we might not need separate Qualifications section. But we also have Requirements (citizenship, drug). And Benefits, Pay, Schedule. Thus sections: About the role, Responsibilities, Skills, Requirements, Benefits, Pay, Schedule. Check if any content left: The "About Us" paragraph after "About Us:" includes company description, diversity statement, EEO. That's boilerplate; we should remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The About Us includes EEO statement etc. We should remove that as boilerplate. The "About Us" also includes mission description, but we already have similar in About the role. The "About Us" includes: "Saab is a leading defense and security company with an enduring purpose, to help nations keep their people and society safe. Empowered by its 28,000 talented people, Saab constantly pushes the boundaries of technology to create a safer and more sustainable world. In the U.S., Saab delivers advanced technology and systems, supporting the U.S. Armed Forces and the Federal Aviation Administration, as well as international and commercial partners. Headquartered in Syracuse, New York, the company has business units and local employees in ten U.S. locations. Saab is a company where we see diversity as an asset and offer unlimited opportunities for advancing in your career. We are also a company that respects each person’s needs and encourage employees to lead a balanced, rewarding life beyond work. Saab values diversity and is an Affirmative Action employer for protected veterans and individuals with disabilities. Saab is an Equal Employment Opportunity employer, all qualified individuals are encouraged to apply and will be considered for employment without regard to race, color, religion, national origin, sex (including pregnancy), sexual orientation, gender identity, age, veteran, disability status, or any other federal, state, or locally protected category." We should remove EEO boilerplate. The earlier part about mission, 28k employees, etc might be substantive but could be considered boilerplate? It's about the company. Might be okay to keep some but we already have About the role covering mission. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The About Us includes EEO statement which is boilerplate; we should remove that. The rest about company description may be okay but could be considered duplication of About the role. Safer to omit the About Us entirely, as we already have About the role covering mission and function. So we will not include About Us. Now Benefits: sign-on bonus to offset housing expenses for Co-Op students residing outside typical office commuting distance. Also maybe other benefits not mentioned. So we will include Benefits section with that. Pay: compensation range $18.24 - $23.31 per hour. Also note that compensation range is a general guideline; factors considered. We should preserve all substantive information; we can include that note as part of Pay section. Schedule: assignment for Winter/Spring 2027 term (January through early May, part-time). We'll put that. Now ensure we don't repeat job title as heading. Not needed. Now produce HTML fragment:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Skills

    Maybe we split into Required and Preferred? Could have two
    with headings? But we cannot add extra headings besides h3? The instruction only says use h3 for section headings. It doesn't forbid other headings like h4, but better to stick to h3 only. Could we have

    Required Qualifications

    and

    Preferred Qualifications

    ? Those are also section headings; they'd be okay as they are specific. But we already have Skills heading; maybe better to have Required and Preferred as subheadings under Skills using or

    . But we can also just have one Skills section with two lists: required and preferred, each preceded by a

    describing. Let's do:

    Skills

    Required Qualifications:

    ...

    Preferred Qualifications:

    ...
    That's acceptable. Now Requirements section:

    Requirements

    • Must be a U.S. citizen.
    • Applicants selected may be subject to a government security investigation and must meet eligibility requirements for access to classified information.
    • As a condition of employment, candidates will be required to pass a pre-employment drug screen.
    Now Benefits:

    Benefits

    In addition to a competitive hourly rate, Saab, Inc. offers a sign-on bonus to offset housing expenses for Co-Op students residing outside the typical office commuting distance.

    Pay:

    Pay

    Compensation Range: $18.24 - $23.31 per hour. The compensation range provided is a general guideline. When extending an offer, Sa