GSOC Analyst- Night Shift
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). The duplicated "Information Security" and EEO statements appear twice; we should keep only one instance? The instruction: remove duplicated lines. So we should keep one copy of the Information Security paragraph and one copy of EEO? Actually EEO is boilerplate; we should remove EEO/equal-opportunity/scam-warning boilerplate. So remove the EEO statements entirely. Keep the Information Security paragraph (maybe only once). Also remove duplicated lines like the repeated "Information Security" paragraph appears twice; keep one.
Also remove "More information is available at https://www.crisis24.com/careers" maybe considered navigation? It's a link; but it's not boilerplate; it's substantive? Might be considered a link to careers page; but it's not a duty. Could keep as a
maybe. However instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link is not exactly navigation but could be considered navigation; but it's a link to careers page. Might be considered navigation; safer to remove? The instruction says remove navigation boilerplate. That link is likely a navigation link; we can drop it.
Also "This Job Description is not a comprehensive list..." is a disclaimer; maybe keep? It's not boilerplate but it's a generic statement; could keep as prose.
We need to structure sections:
- About Crisis24 (company overview) maybe heading "About the role"? Actually they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate. But we must only include sections when posting has real, specific content for it. So we can have:
About the role
maybe containing description of role? The posting has "Who We Are Looking For" and "What You Will Work On". Could treat "About the role" as summary of role. But we must not invent headings without content. We could use "Who We Are Looking For" as a heading? But they said use those example headings; but not strictly required to only use those? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should use those headings when appropriate. So we need to map content to those categories.
Let's identify:
- About the role: could include description of SOC Analyst focus on CCTV and alarm monitoring, primary responsibilities overview. Could be a short paragraph.
- Responsibilities: list of duties from "What You Will Work On". That's a list.
- Requirements/Qualifications/Skills: from "What You Will Bring". Could split into Requirements (education/experience) and Skills (technical, soft skills). But we can combine into one section if content is substantive. However they prefer few substantive sections over many thin ones. So maybe we have:
About the role
(paragraph summarizing role)
Responsibilities
(ul list of duties)
Requirements
(ul list of experience/education/etc)
Skills
(ul list of technical and soft skills)
Work Environment
(paragraph)
Information Security
(paragraph) maybe not in list but we can include as its own section.
We must not include Benefits, Pay, Schedule as they are not present.
We must not repeat job title as heading.
We must not include Job ID/requisition numbers.
We must preserve all substantive information.
Let's extract substantive content:
Company description: "About Crisis24 Crisis24 is a global, AI-enhanced provider of travel risk management, mass communications, critical event management, crisis-security consulting, personal protection solutions and global medical concierge capabilities, allowing prominent organizations, disruptive brands and influential people to operate with confidence in an uncertain world. Backed by proprietary AI-enabled SaaS technologies, advanced Global Operations Centers, an extensive global footprint, and the largest team of private-sector intelligence analysts in the world, we deliver localized insights and global perspectives alongside medical, security, crisis response, embedded intelligence, and consultancy services as a preferred partner for Fortune 500 corporations. At Crisis24, we don't just offer jobs – we offer missions. We recruit the very best from the military, intelligence agencies, academia, law enforcement, medicine, or any of our areas of specialty. We protect more than places. We protect people, reputations, and lifestyles, with integrity, discipline, discretion, and purpose. Whether you're stepping into civilian life after service, seeking personal or professional growth, or bringing specialized expertise to a higher calling, we match your ambition with real opportunity. Do the most important work of your career, helping safeguard the world's most important organizations and individuals against risk."
That's substantive; we can put under About the role? Actually that's about company, not role. But we could still put under About the role heading as overview of company and role. Might be okay.
But maybe better to have a section "About Crisis24" but they didn't list that as example; but we can still use for any heading; they gave examples but not exclusive. However instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate, but we could also use other headings if needed? Safer to stick to those examples. So we need to map company description to "About the role". That heading could contain both company and role description.
Now "Who We Are Looking For" is basically describing ideal candidate; could go under Requirements.
"What You Will Work On" is responsibilities list.
"What You Will Bring" includes experience, education, interest, technical skills, soft skills, etc. We'll split.
"Work Environment" is a paragraph.
"Information Security" paragraph.
Now we need to remove duplicated lines: The "Information Security" and EEO appear twice; we keep one InfoSec and remove EEO.
Also remove "More information is available at https://www.crisis24.com/careers". We'll drop.
Also remove the line "This Job Description is not a comprehensive list of all required activities, duties, or responsibilities. Duties, responsibilities, and activities may change at the discretion of the leadership at any time with or without notice". This is a disclaimer; maybe keep? It's not boilerplate but it's generic; could keep as prose under Responsibilities maybe. But it's not a duty; it's a note. Could keep as a
after list.
Now let's extract lists.
Responsibilities (What You Will Work On) bullet points:
- Monitor, assess and acknowledge all daily alerts, reported incidents from client personnel, and site intrusion detection alarms
- Monitor and administer access control, video management, and intrusion detection systems, including dispatch of security officers when needed while meeting the performance criteria
- Monitor events through open-source collection and coordination with local assets
- Respond to inbound calls from employees and security personnel providing customer service focused responses
- Write security incident investigation reports to provide situational awareness and communicate risks to management
- Monitor designated online tools to conduct situational awareness on social media platforms
- Collect, evaluate, and disseminate intelligence to support action plans based on credibility and likelihood
- Perform proactive threat intelligence gathering and response, including but not limited to: event monitoring, persons of interest, execution protection intelligence
- Contribute to procedures and processes to standardize and enhance risk management
- Work closely with various teams responsible for security, operations, and incident management
- Provide emergency and non-emergency security system monitoring, event dispatch, and emergency notification services
- Process and maintain a wide variety of files, logs, reports, and forms
- Responsible for performing, evidencing, and supporting all necessary tasks for audits
- Processing badge requests – Printing, deactivating, adding and removing access levels
- Be cross trained in all Analyst services
That's a list.
Now Requirements/Qualifications: from "What You Will Bring":
- 1–3+ years of experience in a Security Operations Analyst role preferred
- Bachelor’s degree in a related field is strongly preferred. Either bachelor's degree or equivalent military experience
- Have an interest or direct experience in the following: Intelligence, Security Operations, Critical Incident Management or Corporate Security, Emergency Management
- Must be well-versed in current technologies and open-source search methodologies
- Must be a competent user of Microsoft Suite and Google Suite
- Must be willing to sign an NDA and maintain strict confidentiality
- Must be able to communicate effectively, both verbally and in writing
- Ability to maintain a professional demeanor during stressful situations
- Must be able to quickly adapt and excel in dynamic situations
- Demonstrated organizational and time management skills
- Successful client management experience
- A demonstrated history of effective conflict resolution skills
- Maintain composure in dealing with authorities, executives, clients, staff, and the public occasionally under conditions of urgency and in pressure situations
- Ability to attend training events and mandatory meetings that fall outside normal work hours
- Ability to work 8 to 12-hour shifts both days and nights
We could split into Requirements (experience, education, interest) and Skills (technical, soft). But we can combine.
Work Environment paragraph:
"With or without reasonable accommodation, requires the physical and mental capacity to effectively perform all essential functions. In addition to other demands, the demands of the job include: Undergoing and meet company standards for background and reference checks, and drug tests if required Exposure to sensitive and confidential information Regular computer usage Ability to handle multiple tasks concurrently Manual dexterity required for occasional reaching and lifting of small objects and operating office equipment Occasional reaching with hands and arms, stooping, kneeling, crouching and/or crawling Must be flexible with the ability to work evenings, odd hours, and weekends with little notice Frequent sitting and/or standing"
Note there is a missing period after "reference checks," but we keep as is.
Information Security paragraph (only one):
"Protect the data and systems of Crisis24 and its stakeholders by adhering to policies, reporting incidents and potential problems, completing regular training, and identifying opportunities for improvement."
Now we need to output HTML fragment.
Structure:
About the role
... company description ...
Responsibilities
- ... each duty ...
Requirements
- ... each requirement ...
Maybe also Skills
but we could merge.
But we have many items; splitting may create many thin sections. They prefer few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one section "Requirements and Skills". But heading must be from examples; we could use "Requirements" and include both experience and skills. That's okay.
Then Work Environment
...
Information Security
...
We should also include the disclaimer about job description not comprehensive maybe as a after Responsibilities? Could add under Responsibilities as a note.
Let's craft.
Now ensure we don't include any boilerplate like EE
for prose. We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). The duplicated "Information Security" and EEO statements appear twice; we should keep only one instance? The instruction: remove duplicated lines. So we should keep one copy of the Information Security paragraph and one copy of EEO? Actually EEO is boilerplate; we should remove EEO/equal-opportunity/scam-warning boilerplate. So remove the EEO statements entirely. Keep the Information Security paragraph (maybe only once). Also remove duplicated lines like the repeated "Information Security" paragraph appears twice; keep one. Also remove "More information is available at https://www.crisis24.com/careers" maybe considered navigation? It's a link; but it's not boilerplate; it's substantive? Might be considered a link to careers page; but it's not a duty. Could keep as a
maybe. However instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link is not exactly navigation but could be considered navigation; but it's a link to careers page. Might be considered navigation; safer to remove? The instruction says remove navigation boilerplate. That link is likely a navigation link; we can drop it. Also "This Job Description is not a comprehensive list..." is a disclaimer; maybe keep? It's not boilerplate but it's a generic statement; could keep as prose. We need to structure sections: - About Crisis24 (company overview) maybe heading "About the role"? Actually they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate. But we must only include sections when posting has real, specific content for it. So we can have:
About the role
maybe containing description of role? The posting has "Who We Are Looking For" and "What You Will Work On". Could treat "About the role" as summary of role. But we must not invent headings without content. We could use "Who We Are Looking For" as a heading? But they said use those example headings; but not strictly required to only use those? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should use those headings when appropriate. So we need to map content to those categories.
Let's identify:
- About the role: could include description of SOC Analyst focus on CCTV and alarm monitoring, primary responsibilities overview. Could be a short paragraph.
- Responsibilities: list of duties from "What You Will Work On". That's a list.
- Requirements/Qualifications/Skills: from "What You Will Bring". Could split into Requirements (education/experience) and Skills (technical, soft skills). But we can combine into one section if content is substantive. However they prefer few substantive sections over many thin ones. So maybe we have:
About the role
(paragraph summarizing role)
Responsibilities
(ul list of duties)
Requirements
(ul list of experience/education/etc)
Skills
(ul list of technical and soft skills)
Work Environment
(paragraph)
Information Security
(paragraph) maybe not in list but we can include as its own section.
We must not include Benefits, Pay, Schedule as they are not present.
We must not repeat job title as heading.
We must not include Job ID/requisition numbers.
We must preserve all substantive information.
Let's extract substantive content:
Company description: "About Crisis24 Crisis24 is a global, AI-enhanced provider of travel risk management, mass communications, critical event management, crisis-security consulting, personal protection solutions and global medical concierge capabilities, allowing prominent organizations, disruptive brands and influential people to operate with confidence in an uncertain world. Backed by proprietary AI-enabled SaaS technologies, advanced Global Operations Centers, an extensive global footprint, and the largest team of private-sector intelligence analysts in the world, we deliver localized insights and global perspectives alongside medical, security, crisis response, embedded intelligence, and consultancy services as a preferred partner for Fortune 500 corporations. At Crisis24, we don't just offer jobs – we offer missions. We recruit the very best from the military, intelligence agencies, academia, law enforcement, medicine, or any of our areas of specialty. We protect more than places. We protect people, reputations, and lifestyles, with integrity, discipline, discretion, and purpose. Whether you're stepping into civilian life after service, seeking personal or professional growth, or bringing specialized expertise to a higher calling, we match your ambition with real opportunity. Do the most important work of your career, helping safeguard the world's most important organizations and individuals against risk."
That's substantive; we can put under About the role? Actually that's about company, not role. But we could still put under About the role heading as overview of company and role. Might be okay.
But maybe better to have a section "About Crisis24" but they didn't list that as example; but we can still use for any heading; they gave examples but not exclusive. However instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate, but we could also use other headings if needed? Safer to stick to those examples. So we need to map company description to "About the role". That heading could contain both company and role description.
Now "Who We Are Looking For" is basically describing ideal candidate; could go under Requirements.
"What You Will Work On" is responsibilities list.
"What You Will Bring" includes experience, education, interest, technical skills, soft skills, etc. We'll split.
"Work Environment" is a paragraph.
"Information Security" paragraph.
Now we need to remove duplicated lines: The "Information Security" and EEO appear twice; we keep one InfoSec and remove EEO.
Also remove "More information is available at https://www.crisis24.com/careers". We'll drop.
Also remove the line "This Job Description is not a comprehensive list of all required activities, duties, or responsibilities. Duties, responsibilities, and activities may change at the discretion of the leadership at any time with or without notice". This is a disclaimer; maybe keep? It's not boilerplate but it's generic; could keep as prose under Responsibilities maybe. But it's not a duty; it's a note. Could keep as a
About the role
(paragraph summarizing role)Responsibilities
(ul list of duties)Requirements
(ul list of experience/education/etc)Skills
(ul list of technical and soft skills)Work Environment
(paragraph)Information Security
(paragraph) maybe not in list but we can include as its own section. We must not include Benefits, Pay, Schedule as they are not present. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must preserve all substantive information. Let's extract substantive content: Company description: "About Crisis24 Crisis24 is a global, AI-enhanced provider of travel risk management, mass communications, critical event management, crisis-security consulting, personal protection solutions and global medical concierge capabilities, allowing prominent organizations, disruptive brands and influential people to operate with confidence in an uncertain world. Backed by proprietary AI-enabled SaaS technologies, advanced Global Operations Centers, an extensive global footprint, and the largest team of private-sector intelligence analysts in the world, we deliver localized insights and global perspectives alongside medical, security, crisis response, embedded intelligence, and consultancy services as a preferred partner for Fortune 500 corporations. At Crisis24, we don't just offer jobs – we offer missions. We recruit the very best from the military, intelligence agencies, academia, law enforcement, medicine, or any of our areas of specialty. We protect more than places. We protect people, reputations, and lifestyles, with integrity, discipline, discretion, and purpose. Whether you're stepping into civilian life after service, seeking personal or professional growth, or bringing specialized expertise to a higher calling, we match your ambition with real opportunity. Do the most important work of your career, helping safeguard the world's most important organizations and individuals against risk." That's substantive; we can put under About the role? Actually that's about company, not role. But we could still put under About the role heading as overview of company and role. Might be okay. But maybe better to have a section "About Crisis24" but they didn't list that as example; but we can still use for any heading; they gave examples but not exclusive. However instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate, but we could also use other headings if needed? Safer to stick to those examples. So we need to map company description to "About the role". That heading could contain both company and role description.
Now "Who We Are Looking For" is basically describing ideal candidate; could go under Requirements.
"What You Will Work On" is responsibilities list.
"What You Will Bring" includes experience, education, interest, technical skills, soft skills, etc. We'll split.
"Work Environment" is a paragraph.
"Information Security" paragraph.
Now we need to remove duplicated lines: The "Information Security" and EEO appear twice; we keep one InfoSec and remove EEO.
Also remove "More information is available at https://www.crisis24.com/careers". We'll drop.
Also remove the line "This Job Description is not a comprehensive list of all required activities, duties, or responsibilities. Duties, responsibilities, and activities may change at the discretion of the leadership at any time with or without notice". This is a disclaimer; maybe keep? It's not boilerplate but it's generic; could keep as prose under Responsibilities maybe. But it's not a duty; it's a note. Could keep as a
after list. Now let's extract lists. Responsibilities (What You Will Work On) bullet points: - Monitor, assess and acknowledge all daily alerts, reported incidents from client personnel, and site intrusion detection alarms - Monitor and administer access control, video management, and intrusion detection systems, including dispatch of security officers when needed while meeting the performance criteria - Monitor events through open-source collection and coordination with local assets - Respond to inbound calls from employees and security personnel providing customer service focused responses - Write security incident investigation reports to provide situational awareness and communicate risks to management - Monitor designated online tools to conduct situational awareness on social media platforms - Collect, evaluate, and disseminate intelligence to support action plans based on credibility and likelihood - Perform proactive threat intelligence gathering and response, including but not limited to: event monitoring, persons of interest, execution protection intelligence - Contribute to procedures and processes to standardize and enhance risk management - Work closely with various teams responsible for security, operations, and incident management - Provide emergency and non-emergency security system monitoring, event dispatch, and emergency notification services - Process and maintain a wide variety of files, logs, reports, and forms - Responsible for performing, evidencing, and supporting all necessary tasks for audits - Processing badge requests – Printing, deactivating, adding and removing access levels - Be cross trained in all Analyst services That's a list. Now Requirements/Qualifications: from "What You Will Bring": - 1–3+ years of experience in a Security Operations Analyst role preferred - Bachelor’s degree in a related field is strongly preferred. Either bachelor's degree or equivalent military experience - Have an interest or direct experience in the following: Intelligence, Security Operations, Critical Incident Management or Corporate Security, Emergency Management - Must be well-versed in current technologies and open-source search methodologies - Must be a competent user of Microsoft Suite and Google Suite - Must be willing to sign an NDA and maintain strict confidentiality - Must be able to communicate effectively, both verbally and in writing - Ability to maintain a professional demeanor during stressful situations - Must be able to quickly adapt and excel in dynamic situations - Demonstrated organizational and time management skills - Successful client management experience - A demonstrated history of effective conflict resolution skills - Maintain composure in dealing with authorities, executives, clients, staff, and the public occasionally under conditions of urgency and in pressure situations - Ability to attend training events and mandatory meetings that fall outside normal work hours - Ability to work 8 to 12-hour shifts both days and nights We could split into Requirements (experience, education, interest) and Skills (technical, soft). But we can combine. Work Environment paragraph: "With or without reasonable accommodation, requires the physical and mental capacity to effectively perform all essential functions. In addition to other demands, the demands of the job include: Undergoing and meet company standards for background and reference checks, and drug tests if required Exposure to sensitive and confidential information Regular computer usage Ability to handle multiple tasks concurrently Manual dexterity required for occasional reaching and lifting of small objects and operating office equipment Occasional reaching with hands and arms, stooping, kneeling, crouching and/or crawling Must be flexible with the ability to work evenings, odd hours, and weekends with little notice Frequent sitting and/or standing" Note there is a missing period after "reference checks," but we keep as is. Information Security paragraph (only one): "Protect the data and systems of Crisis24 and its stakeholders by adhering to policies, reporting incidents and potential problems, completing regular training, and identifying opportunities for improvement." Now we need to output HTML fragment. Structure:
About the role
... company description ...
Responsibilities
- ... each duty ...
Requirements
- ... each requirement ...
Skills
but we could merge. But we have many items; splitting may create many thin sections. They prefer few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one section "Requirements and Skills". But heading must be from examples; we could use "Requirements" and include both experience and skills. That's okay. ThenWork Environment
...
Information Security
...
We should also include the disclaimer about job description not comprehensive maybe as aafter Responsibilities? Could add under Responsibilities as a note. Let's craft. Now ensure we don't include any boilerplate like EE