Security Analytics & AI Insights Analyst
Citizens · Johnston, RI · 1 mo ago
$90k–$105k/yrFull-time
We need to output HTML fragment with sections: About the role? The description includes Job Summary, Key Responsibilities, Required Qualifications, Preferred Qualifications, Key Competencies, Success Measures, Reports To, Pay Transparency, Benefits, etc. We must not repeat job title as heading. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content accordingly. The instruction: "use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content accordingly. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should include sections only if posting has real specific content. We have content for About the role (Job Summary). Responsibilities (Key Responsibilities). Requirements (maybe Required Qualifications). Qualifications (Preferred Qualifications). Skills (Technical Skills). Benefits (Benefits paragraph). Pay (Pay Transparency). Schedule (Locations & Work Arrangement). Also maybe Reports To? Not required heading but could be included in About the role? Probably not needed. We'll include only those sections with content.
We must not include boilerplate like EEO, legal, etc. Remove duplicated lines. Also remove application instructions, cookie/navigation, etc. The posting includes "Why Work for Us" etc - that's boilerplate? Might be considered fluff but maybe keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why Work for Us" is not exactly those but could be considered fluff; but it's substantive? It's more marketing. Might be okay to keep? Safer to omit as it's not required sections. We'll focus on required sections.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include details from each section.
Let's extract:
Job Summary: "The AI Analytics Analyst supports the Security Insights Program by analyzing cybersecurity, operational, and AI enriched data to deliver actionable insights, automated reporting, and executive level dashboards. This role is responsible for transforming complex data into clear, business focused intelligence that improves risk visibility, supports decision making, and drives operational effectiveness across the cybersecurity organization. The ideal candidate combines strong data analytics, visualization, and reporting skills with the ability to leverage AI enabled tools to accelerate analysis, improve reporting quality, identify trends, and support continuous improvement initiatives. Cybersecurity experience is preferred but not required for candidates with strong analytics and business intelligence backgrounds."
Locations & Work Arrangement: "Remote is NOT an option, candidates must be willing to commute to one of the following hub locations with a hybrid schedule of 4 days onsite and 1 day remote per week with flexibility in one of the following hubs: Johnston, RI Boston, MA Pittsburgh, PA"
Key Responsibilities: bullet list under Security Analytics & Reporting, AI Enabled Analytics, Dashboard Development & Data Visualization, Data Management & Reporting Automation, Security Data Sources, Stakeholder Collaboration. We'll need to capture each bullet.
Required Qualifications: Education, Experience, Technical Skills? Actually Technical Skills separate. Required Qualifications includes Education, Experience. Also maybe "Experience working with cybersecurity data and metrics preferred." We'll include.
Preferred Qualifications: list.
Key Competencies: list.
Success Measures: list.
Reports To: "Reports To Security Insights Manager"
Pay Transparency: salary range $90,000 – $105,000 per year, plus opportunity to earn additional incentive earnings (if applicable). Actual pay based on factors.
Benefits: "We offer competitive pay, comprehensive medical, dental and vision coverage, retirement benefits, maternity/paternity leave, flexible work arrangements, education reimbursement, wellness programs and more. Note, Citizens’ paid time off policy exceeds the mandatory, paid sick or paid time-away policy of every local and state jurisdiction in the United States. For an overview of our benefits, visit https://jobs.citizensbank.com/benefits"
We should not include the link? It's substantive; we can keep as part of benefits paragraph.
We must not include duplicated lines. Ensure no fluff.
Now produce HTML with headings and appropriate
headings and appropriate
or
- .
We need to decide which headings map to which content.
Possible sections:
- About the role (Job Summary)
- Responsibilities (Key Responsibilities)
- Requirements (Required Qualifications)
- Qualifications (Preferred Qualifications)
- Skills (Technical Skills) maybe also include Key Competencies? But Skills heading likely for technical skills. We could put Technical Skills under Skills. Key Competencies could be under Requirements? But we have Requirements heading for qualifications; maybe we can put Key Competencies under Requirements as well? However instruction says use those headings as examples; we can also add other headings if needed? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should stick to those. So we need to fit content into those categories. We have: - About the role: Job Summary. - Responsibilities: Key Responsibilities. - Requirements: Required Qualifications (Education, Experience) plus maybe Key Competencies? Could also include Key Competencies under Requirements. - Qualifications: Preferred Qualifications. - Skills: Technical Skills (SQL, Python, Tableau, etc.) plus maybe also include familiarity with AI assisted analytics workflows. - Benefits: Benefits paragraph. - Pay: Pay Transparency. - Schedule: Locations & Work Arrangement. We also have Reports To and Success Measures. Where to put? Could be part of About the role or Responsibilities? Success Measures could be under About the role? Or maybe we can add a section "Success Measures" but not in list; but instruction says prefer a few substantive sections over many thin ones. Could incorporate Success Measures into About the role or Responsibilities. Probably better to add a separate section? But not in allowed headings; maybe we can put under Requirements? Hmm. We could treat Success Measures as part of About the role (what success looks like). Or we could add a heading "Success Measures" even if not in examples; but instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples, not exhaustive. So we could add other headings if needed. However to be safe, we can incorporate Success Measures into About the role or Responsibilities. Reports To could be a short paragraph under About the role. Let's craft. We'll produce:
About the role
Job Summary ... Reports To Security Insights Manager. Success Measures: Within the first 12 months, the successful candidate will increase automation of security reporting and analytics processes, improve efficiency and reduce manual effort associated with security metrics and reporting, deliver actionable insights that improve risk visibility and prioritization, expand executive dashboard and reporting capabilities, improve stakeholder adoption and utilization of Security Insights reporting products, enhance the quality, timeliness, and consistency of security reporting.
But we need to preserve all detail; we can split into sentences. Better to keep Success Measures as a- maybe under About the role? But we can also make a separate section "Success Measures". I'd rather add a separate heading for clarity; it's substantive. The instruction didn't forbid. I'll include a
- . Requirements: Required Qualifications. Education: Bachelor's degree in Data Analytics, Data Science, Computer Science, Information Systems, Cybersecurity, Statistics, Mathematics, or a related discipline. Master's degree preferred. Experience: 3 to 5 years of experience in data analytics, business intelligence, reporting, or related disciplines. Experience designing dashboards, scorecards, and reporting solutions. Experience using SQL and analytics tools to analyze and interpret large datasets. Experience leveraging AI enabled tools to support analytics, reporting, automation, or decision support. Experience working with cybersecurity data and metrics preferred. Candidates with strong analytics, reporting, and visualization experience who can quickly learn cybersecurity concepts are encouraged to apply. We could also include Key Competencies? But we have Skills heading for technical skills; Key Competencies could be under Requirements as well (soft skills). However we have limited headings; maybe we can put Key Competencies under Requirements as a list. But Requirements already has education and experience; we can add a sublist for Key Competencies. Qualifications: Preferred Qualifications. - Experience supporting cybersecurity, technology, risk, compliance, or operational reporting programs. - Security certifications such as Security+, CISSP, CISM, or equivalent. - Analytics certifications related to Tableau, Power BI, AI, data analytics, or cloud platforms. - Experience with Microsoft Copilot, GenAI tools, or AI enabled reporting environments. Skills: Technical Skills. - SQL and data modeling. - Python, R, or similar analytics and automation tools. - Tableau, Power BI, or equivalent visualization platforms. - Data wrangling, cleansing, and transformation techniques. - Experience with APIs, automated reporting solutions, and data integration concepts. - Familiarity with cloud data platforms and modern analytics environments.
Success Measures
with list. Similarly Reports To could be a short p. But we need to avoid too many thin sections. However we already have many sections: About, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule, Success Measures, Reports To. That's many. Maybe combine Reports To and Success Measures into About the role. Let's combine: About the role includes Job Summary, Reports To, Success Measures. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Now we need to extract content for each. About the role: combine Job Summary, Reports To, Success Measures. Job Summary text as above. Reports To: "Reports To Security Insights Manager" Success Measures list: increase automation..., improve efficiency..., deliver actionable insights..., expand executive dashboard..., improve stakeholder adoption..., enhance quality... We'll write as a- .
Responsibilities: need to capture all bullet points from Key Responsibilities sections.
Let's list them:
Security Analytics & Reporting
- Analyze cybersecurity and operational datasets to identify trends, anomalies, risk indicators, and performance insights.
- Perform trend analysis, root cause analysis, and risk based reporting across multiple security domains.
- Develop and maintain key performance indicators (KPIs) and key risk indicators (KRIs).
- Support executive and operational decision making through data driven insights and reporting.
- Identify opportunities to improve risk visibility, measurement, and reporting effectiveness.
AI Enabled Analytics
- Utilize AI enabled tools to support data analysis, pattern identification, reporting, and insight generation.
- Evaluate AI generated outputs for accuracy, relevance, and business value before incorporating findings into reporting.
- Support AI assisted analytics workflows that improve efficiency and reduce manual effort.
- Analyze and interpret data generated from AI based security solutions and automation platforms.
Dashboard Development & Data Visualization
- Design, develop, and maintain executive level dashboards, scorecards, and reporting products using Tableau, Power BI, or similar visualization platforms.
- Create intuitive visualizations that communicate insights clearly to technical and nontechnical audiences.
- Apply data storytelling techniques to improve understanding of security performance and risk trends.
- Continuously improve dashboard usability, reporting quality, and stakeholder adoption.
Data Management & Reporting Automation
- Aggregate, cleanse, transform, and analyze data from multiple sources.
- Support reporting automation initiatives that improve scalability, consistency, and efficiency.
- Partner with data engineering resources to support data integration and data quality improvements.
- Develop reusable metrics, reporting templates, and analytics frameworks.
Security Data Sources
- Analyze Data From Security Technologies And Programs Including Vulnerability Management Cloud Security Application Security Identity and Access Management IT Service Management Threat Intelligence Security Operations Cyber Risk and Compliance Programs
Stakeholder Collaboration
- Partner with Security, Risk, Compliance, Resilience, Infrastructure, Technology, and Application Development teams.
- Translate technical findings into business focused insights and recommendations.
- Communicate analytics findings to Security Insights leadership and key stakeholders.
- Support strategic initiatives through analytics, reporting, and measurement.
We'll put all these as