2026 Information Security Operations Center Analyst Technical Intern (Jan and May 2027 hires)
The Church of Jesus Christ of Latter-day Saints · Riverton, UT · 1 mo ago
HybridFull-time
We need to produce HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Application And Interview Process" maybe considered application instructions, we should drop it. Also drop "Qualifications" maybe we keep but need to ensure content. The posting includes "Qualifications" list. Also "Skills" maybe not explicit separate; but we can combine. The posting includes "Benefits" (Full time interns do get the option to enroll in a high deductible medical plan). Also "Pay" maybe not explicit; there is "Great pay" mentioned under bullet list but not specific amount. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It says "Great pay" but not specific amount; that might be considered vague. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Great pay" is vague but maybe considered filler? It's not a specific number. Safer to omit Pay section because not specific. Schedule is given: "This is a 40 hour per week internship that is expected to last approximately 4 months. Our SOC operates 24/7, so our analysts work 12-hour shifts 3 consecutive days a week, plus 4 hours to call into meetings and work on training (total 40 hours). We have found that this schedule is especially useful for students, who can often schedule around classes during the week. The office is located in Riverton, UT . Remote and hybrid options are available." That's specific enough. So include Schedule section.
Benefits: "Full time interns do get the option to enroll in a high deductible medical plan". That's specific enough. So include Benefits.
About the role: we have "About This internship position represents an exciting opportunity to work for one of the largest information technology centers in the Wasatch front. This individual works with divine guidance to provide or support technology that furthers the mission of the Church and reflects the eternal impact of the gospel." Also earlier description: "The Church of Jesus Christ of Latter-day Saints is looking for Information Security Operations Center Analyst interns to work in the Church’s 24/7 Information Security Operations Center (ISOC) to identify, analyze, and respond to cyber threats to Church networks, systems, and data across the globe." That's about role. So we can put About the role.
Responsibilities: The posting includes "A Day In The Life" describing tasks: defending from cyber threats, analyzing threats, responding to incidents, shift work, investigating events, performing technical analysis, using tools, etc. Also "An Average Shift Can Range From a Phishing Attack Against Church Leaders To Malware Events On An Employee’s Work Computer." So we can extract responsibilities.
Requirements: Might be similar to Qualifications. The posting includes "Qualifications" list: currently enrolled or within one year of graduation, temple worthy member, solid business presentation skills, technology background desired, excellent communication skills, security certifications bonus, IP networking fundamentals, some understanding of system admin Linux/Windows, attention to detail, ability to handle multiple priorities, technical analysis skills. Also maybe "Internship is for current temple worthy members". That's a requirement.
Skills: Could be separate but we may combine with Qualifications. However we need to decide sections: we can have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. But we must avoid thin sections. Perhaps combine Requirements and Qualifications into one? But the instruction says use headings for those categories if content exists. We have content for both Requirements and Qualifications; they may overlap but we can keep both if they have distinct content. However the posting only has a "Qualifications" section; not separate "Requirements". So we could treat that as Qualifications. Could also treat "Requirements" as same as Qualifications but we shouldn't create empty headings. So we will not include Requirements heading if no distinct content. We'll include Qualifications.
Skills: The posting mentions "Solid business presentation skills", "Excellent communication skills", "IP networking fundamentals", "Some understanding of system administration including Linux and Windows", "Attention to detail", "Ability to effectively handle multiple priorities and deadlines", "Technical analysis skills". Those could be considered skills. But they are already in Qualifications. To avoid duplication, we could have Skills section listing those, and Qualifications section listing enrollment, temple worthy, etc. Let's split: Qualifications: enrollment status, temple worthy member. Skills: presentation, communication, networking, sysadmin, attention to detail, multitasking, technical analysis. Also security certifications bonus maybe skill.
We need to ensure we don't repeat content. We'll extract.
Now Benefits: "Full time interns do get the option to enroll in a high deductible medical plan". Also maybe other benefits like "Great pay" but we omitted Pay. Also "We are committed to the well-being of our employees..." but that's generic; maybe not specific benefit. We'll keep only the medical plan.
Schedule: as described.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Application And Interview Process" maybe considered application instructions, we should drop it. Also drop "Qualifications" maybe we keep but need to ensure content. The posting includes "Qualifications" list. Also "Skills" maybe not explicit separate; but we can combine. The posting includes "Benefits" (Full time interns do get the option to enroll in a high deductible medical plan). Also "Pay" maybe not explicit; there is "Great pay" mentioned under bullet list but not specific amount. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It says "Great pay" but not specific amount; that might be considered vague. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Great pay" is vague but maybe considered filler? It's not a specific number. Safer to omit Pay section because not specific. Schedule is given: "This is a 40 hour per week internship that is expected to last approximately 4 months. Our SOC operates 24/7, so our analysts work 12-hour shifts 3 consecutive days a week, plus 4 hours to call into meetings and work on training (total 40 hours). We have found that this schedule is especially useful for students, who can often schedule around classes during the week. The office is located in Riverton, UT . Remote and hybrid options are available." That's specific enough. So include Schedule section.
Benefits: "Full time interns do get the option to enroll in a high deductible medical plan". That's specific enough. So include Benefits.
About the role: we have "About This internship position represents an exciting opportunity to work for one of the largest information technology centers in the Wasatch front. This individual works with divine guidance to provide or support technology that furthers the mission of the Church and reflects the eternal impact of the gospel." Also earlier description: "The Church of Jesus Christ of Latter-day Saints is looking for Information Security Operations Center Analyst interns to work in the Church’s 24/7 Information Security Operations Center (ISOC) to identify, analyze, and respond to cyber threats to Church networks, systems, and data across the globe." That's about role. So we can put About the role.
Responsibilities: The posting includes "A Day In The Life" describing tasks: defending from cyber threats, analyzing threats, responding to incidents, shift work, investigating events, performing technical analysis, using tools, etc. Also "An Average Shift Can Range From a Phishing Attack Against Church Leaders To Malware Events On An Employee’s Work Computer." So we can extract responsibilities.
Requirements: Might be similar to Qualifications. The posting includes "Qualifications" list: currently enrolled or within one year of graduation, temple worthy member, solid business presentation skills, technology background desired, excellent communication skills, security certifications bonus, IP networking fundamentals, some understanding of system admin Linux/Windows, attention to detail, ability to handle multiple priorities, technical analysis skills. Also maybe "Internship is for current temple worthy members". That's a requirement.
Skills: Could be separate but we may combine with Qualifications. However we need to decide sections: we can have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. But we must avoid thin sections. Perhaps combine Requirements and Qualifications into one? But the instruction says use headings for those categories if content exists. We have content for both Requirements and Qualifications; they may overlap but we can keep both if they have distinct content. However the posting only has a "Qualifications" section; not separate "Requirements". So we could treat that as Qualifications. Could also treat "Requirements" as same as Qualifications but we shouldn't create empty headings. So we will not include Requirements heading if no distinct content. We'll include Qualifications.
Skills: The posting mentions "Solid business presentation skills", "Excellent communication skills", "IP networking fundamentals", "Some understanding of system administration including Linux and Windows", "Attention to detail", "Ability to effectively handle multiple priorities and deadlines", "Technical analysis skills". Those could be considered skills. But they are already in Qualifications. To avoid duplication, we could have Skills section listing those, and Qualifications section listing enrollment, temple worthy, etc. Let's split: Qualifications: enrollment status, temple worthy member. Skills: presentation, communication, networking, sysadmin, attention to detail, multitasking, technical analysis. Also security certifications bonus maybe skill.
We need to ensure we don't repeat content. We'll extract.
Now Benefits: "Full time interns do get the option to enroll in a high deductible medical plan". Also maybe other benefits like "Great pay" but we omitted Pay. Also "We are committed to the well-being of our employees..." but that's generic; maybe not specific benefit. We'll keep only the medical plan.
Schedule: as described.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce:
About the role
...
Responsibilities
- ... ...
Qualifications
- Currently enrolled in or within one year of graduation from an accredited college or university.
- Must be a current temple‑worthy member of The Church of Jesus Christ of Latter‑day Saints.
Skills
- Solid business presentation skills – able to articulate technical concepts clearly, visually and verbally.
- Excellent communication skills for interacting with and providing information to management levels.
- IP networking fundamentals.
- Some understanding of system administration including Linux and Windows.
- Strong attention to detail.
- Ability to effectively handle multiple priorities and deadlines.
- Technical analysis skills.
- Security certifications are a bonus.
Benefits
- Option to enroll in a high deductible medical plan (for full‑time interns).
Schedule
This is a 40‑hour per week internship expected to last approximately 4 months. The SOC operates 24/7, so analysts work 12‑hour shifts three consecutive days a week, plus 4 hours for meetings and training (total 40 hours). The schedule is designed to accommodate student class schedules. The office is located in Riverton, UT, with remote and hybrid options available.
We must ensure we didn't include any boilerplate like EEO etc. We removed "Application And Interview Process". Also removed duplicated lines like "Only members of the Church who are worthy of a temple recommend qualify for employment." That's part of Qualifications? Actually we included temple worthy member. That's fine. We removed the repeated EEO statements. Check for any leftover boilerplate: The "About Us" paragraph about employees finding joy etc. That's not specific to role; could be considered boilerplate. We should remove it. Also "Only members of the Church who are worthy of a temple recommend qualify for employment." repeated; we used it once in Qualifications; but there is a second occurrence later in "About Us". We should not duplicate. We already have it in Qualifications; we should not repeat again. So we removed. Check for any mention of "Great pay" - we omitted Pay section. Good. Check for any mention of "We hasten the Lord's work in an important way" etc. That's under bullet list near "About This". Actually there is a list: "Work with state-of-the art tools to help develop enterprise solutions Mentor with highly experienced IT professionals We hasten the Lord's work in an important way Great pay Be a member of a creative, spiritual, and highly motivated team and culture You will gain practical experience We are committed to the well-being of our employees..." That's a mix of benefits and culture. We extracted benefits as medical plan; we omitted others as they are vague or duplicate. The rule: never emit a heading followed by filler/placeholder text. Those bullet points are not specific enough for a section; we can incorporate some into About the role or Responsibilities? For example "Work with state-of-the-art tools to help develop enterprise solutions" could be a responsibility. "Mentor with highly experienced IT professionals" could be a responsibility or benefit. "Be a member of a creative, spiritual, and highly motivated team and culture" maybe about role. "You will gain practical experience" maybe about role. We could incorporate them into About the role or Responsibilities. But we already have About the role and Responsibilities sections; we could add some of those as list items under Responsibilities or About. However we must not invent content; we can rephrase but must preserve all substantive information. So we need to ensure we don't lose any substantive info. Let's capture all substantive sentences from the posting. Let's parse the posting thoroughly. Original text: "Job Description Information Security Operations Center Analyst Internship The Church of Jesus Christ of Latter-day Saints is looking for Information Security Operations Center Analyst interns to work in the Church’s 24/7 Information Security Operations Center (ISOC) to identify, analyze, and respond to cyber threats to Church networks, systems, and data across the globe. If you are an energetic and dedicated individual who loves learning, and you’re looking for an internship, keep reading! About This internship position represents an exciting opportunity to work for one of the largest information technology centers in the Wasatch front. This individual works with divine guidance to provide or support technology that furthers the mission of the Church and reflects the eternal impact of the gospel. A Day In The Life This team is a highly technical security team tasked with defending the Church of Jesus Christ of Latter-day Saints from cyber threats day and night. Our team is one of many teams in the Information Security organization. While other teams may focus on system administration, risk analysis, compliance, or penetration testing, our team solely focuses on analyzing threats, responding to incidents, and thwarting cyber adversaries to protect the Church. A position on this team requires shift work and is a highly interactive team environment. An Average Shift Can Range From a Phishing Attack Against Church Leaders To Malware Events On An Employee’s Work Computer . In Every Event We Investigate, We Perform Technical Analysis To Answer The Following Questions is this event malicious? what is the impact? what do we need to do about it? This technical analysis involves logs from networks, applications, security sensors, and endpoints. We use enterprise tools such as Splunk, Palo Alto, Cisco, Microsoft Cloud App Security, Sophos, and many others to aid our investigations. Our interns work under supervision and with clear escalation paths. We also have a mature in-house training plan, so every intern knows from day 1 what items they will need to study and demonstrate proficiency with, all under a trainer’s supervision. Our interns leave our program armed with robust experience in a global SOC, deeper understanding of technical security issues, and confidence in their analytic abilities. Our intern program is also a pipeline for recruitment into our team’s full-time, benefitted contract positions. Work with state-of-the art tools to help develop enterprise solutions Mentor with highly experienced IT professionals We hasten the Lord's work in an important way Great pay Be a member of a creative, spiritual, and highly motivated team and culture You will gain practical experience We are committed to the well-being of our employees and supporting them in becoming their best self. Our focus on physical and mental health, financial security, and personal and professional development helps employees create more energy, purpose, and balance in life. Work Schedule This is a 40 hour per week internship