Cybersecurity & Technology Audit Internship (Summer 2027)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings if content exists. It doesn't require us to use all; we can pick those that match.
Thus we can map:
- About the role: description paragraph.
- Responsibilities: bullet list.
- Qualifications: the list under "Qualifications What you've got".
- Benefits: paragraph about benefits.
- Pay: paragraph about Pay Philosophy.
- Schedule: mention of full-time 11 weeks (maybe we can include in Qualifications but better separate). Since schedule is mentioned, we can create Schedule section.
We might not need Requirements or Skills separately if they are covered in Qualifications. But we could still include them if we want to split. However we must not create sections with filler. If we split, we need to ensure each section has substantive content. We could put education/experience in Requirements, and soft/technical skills in Skills. That would be substantive.
Let's extract:
Requirements:
- 0-2 years of professional experience.
- Pursuing a Bachelors degree in Business Management, Management Information Systems (MIS), Computer Science, or equivalent training.
- Minimum 3.0 cumulative GPA.
- Able to commit to a full-time internship for the 11 weeks.
Skills:
- Detail-oriented and thrive in a fast-paced work environment.
- Strong interpersonal, communication, organizational, and leadership skills.
- Experience with technical programs, including a working knowledge of Excel.
That seems good.
Now Benefits: paragraph about benefits and link.
Pay: paragraph about Pay Philosophy.
Schedule: maybe we already included commitment in Requirements; but we could still have Schedule section stating "Full-time internship for 11 weeks." However that would duplicate. Better to keep schedule in Requirements (or separate). Since we already have commitment in Requirements, we could omit Schedule section to avoid duplication. But the instruction says include a section ONLY when posting has real specific content for it. If we already covered schedule in Requirements, we could still have Schedule but it'd be duplicate. Better to not include Schedule if we already covered it. However we might still include Schedule as a short sentence: "Full-time internship for 11 weeks." That's still specific. But duplication is not prohibited explicitly, but we should avoid redundancy? Not mentioned. It says preserve ALL substantive information; do not invent or summarize away detail. Duplication is okay if it's present in posting? The posting mentions commitment to full-time internship for 11 weeks only once. If we put it in both Requirements and Schedule, we are duplicating but not adding new info. Might be okay but could be considered unnecessary. I'd keep it only in Requirements.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay.
Check if any other sections: Qualifications? We split into Requirements and Skills, so we might not need Qualifications heading. But the posting had a Qualifications heading; we could keep Qualifications as a section containing the same list, but then we would have duplicate content. Better to follow the instruction: use headings only when posting has real specific content for it. The posting has a Qualifications section with specific content. So we should include Qualifications. But we already have Requirements and Skills which together cover the same content. However we could keep Qualifications as a section and not have Requirements/Skills. But then we lose the split. The instruction says we can use those headings; we can choose which to include. It doesn't require us to use all. So we could include Qualifications only, and not Requirements/Skills. That would preserve all info (the list). That seems simpler and avoids duplication.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
We need to check if there is any content for Skills separate from Qualifications? The Qualifications list includes skills already. So we can just use Qualifications.
Now we need to format:
About the role
... prose ...
Responsibilities
- ... ...
Qualifications
- ... ...
Benefits
... benefits paragraph ...
Pay
... pay philosophy paragraph ...
We need to ensure we preserve all substantive information: location, posted on maybe we can fold into a short p at top? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." So we can include a short p for location and posted date. Not required but we can include. We should not include boilerplate like EEO, scam warning, etc. Let's extract the prose for About the role: The description paragraph(s) before "Qualifications". It starts: "A career in finance at Liberty Mutual is more than just balancing assets and liabilities. You'll be using innovative tools and problem-solving skills to fuel your growth and successand ours. Were dedicated to helping industry-leading finance talent realize their dreamsstraight out of college. Sound like you? Read on! The details When you take on the role of summer intern with Liberty Mutuals Cybersecurity & Technology Audit department, youre signing on to a collaborative team thats responsible for auditing all of our internal control systems. Your key responsibilities during this rewarding 11-week internship program will include interviewing personnel, performing testwork, analyzing results, and communicating issues with managers. Youll also participate in audit project teams to complete risk assessments and control evaluations for IT areas under review. The ultimate goal is to provide a positive summer experience filled with real-world projects that give you the opportunity to thrive through challenging work. Best of all, at the close of the three-month period, you may have the opportunity to explore a future career with Liberty Mutual, a global Fortune 100 company" We need to fix typos: "successand" should be "success and". "Were" should be "We're". "straight out of college." maybe missing space. But we should preserve as is? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Should we correct obvious typos? Probably we should keep the text as given, but we could fix minor punctuation? It's ambiguous. Safer to keep exactly as given, but we can fix obvious missing spaces? Might be considered altering. I'd keep as is but maybe add spaces where missing? The instruction says do not invent or summarize away detail. Changing punctuation could be considered inventing? It's minor. I'd keep original text. Thus About the role paragraph includes all that. Now Responsibilities: bullet list from that paragraph: "interviewing personnel, performing testwork, analyzing results, and communicating issues with managers." and "participate in audit project teams to complete risk assessments and control evaluations for IT areas under review." Also maybe "provide a positive summer experience filled with real-world projects that give you the opportunity to thrive through challenging work." That's more of goal. But we can include as responsibility. We'll create list items: - Interviewing personnel - Performing testwork - Analyzing results - Communicating issues with managers - Participate in audit project teams to complete risk assessments and control evaluations for IT areas under review - Provide a positive summer experience filled with real-world projects that give you the opportunity to thrive through challenging work But note the last is more of goal; still okay. Now Qualifications: list from "What you've got". Items: - You have 0-2 years of professional experience. - You are pursuing a Bachelors degree in Business Management, Management Information Systems (MIS), Computer Science, or