Splunk Reporting & Monitoring Analyst

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse job description. Given text includes: Job#: 3053203 Job Description: Splunk Reporting & Monitoring Analyst Location: Plano, Texas (Onsite) Employment Type: Contract Contract Duration: 12 Months Role Overview We are seeking a Splunk Reporting & Monitoring Analyst to design, build, and maintain advanced Splunk dashboards, reports, and alerts. This role supports proactive and reactive operational support for enterprise collaboration and productivity platforms within a financial services environment. The ideal candidate will translate technical data into actionable insights for various stakeholders. Key Responsibilities (list) Design, develop, and maintain custom Splunk dashboards, reports, and visualizations. Build optimized SPL queries to analyze large-scale log, event, and metric data. Develop real-time and near-real-time alerts to detect service degradation and abnormal behavior. Partner with Operations and Support teams to define meaningful KPIs and SLIs. Leverage Microsoft Graph APIs to ingest, correlate, and analyze M365 telemetry. Operate within a regulated financial services environment, ensuring reporting aligns with security and compliance requirements. Translate complex technical data into clear narratives and recommendations for technical and non-technical teams. Document dashboards, reports, alert logic, and data sources. Required Qualifications Technical Skills: Advanced experience with Splunk Enterprise (search, dashboards, reports, alerts). Strong proficiency in SPL (Search Processing Language). Hands-on knowledge of Microsoft 365 services and Microsoft Graph APIs. Experience integrating external data sources and APIs into Splunk. Proficiency with Python, PowerShell, Power BI, and Excel. Experience: Experience supporting Operations and Support monitoring for enterprise applications. Strong understanding of incident management, problem management, and service monitoring. Experience working in a financial institution or other highly regulated environment. Familiarity with SLAs, SLOs, and service reliability concepts. Professional Qualities: Exceptional written and verbal communication skills. Ability to explain complex technical insights in simple, actionable terms. Strong problem-solving mindset with the ability to identify patterns and trends in data. A strong sense of ownership and accountability for deliverables. Ability to work independently while collaborating effectively across teams. Preferred Qualifications Splunk certifications (Power User, Admin, Architect). Experience supporting collaboration platforms at an enterprise scale. Background in SRE, NOC, or production support environments. Experience building executive dashboards and operational scorecards. Then there is a paragraph about Everforth Apex company description, benefits overview, etc. Benefits: medical, dental, vision, life, disability, other insurance plans, ESPP, 401K with company match after 12 months, HSA, SupportLinc EAP, corporate discount savings program, on-demand training program, certification prep, library of technical and leadership courses/books/seminars after 6+ months tenure, certification discounts, perks to associations (CompTIA and IIBA), dedicated customer service team, certified Career Coach, Welcome Packet. Pay: Not mentioned. Schedule: Not mentioned (though contract duration 12 months, location onsite). No explicit schedule like full-time, part-time, shift. So we should not include Pay or Schedule sections because they are not stated. We need sections: About the role (role overview), Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly combine Requirements and Qualifications? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have separate sections for Requirements and Qualifications. However the posting lumps Required Qualifications (Technical Skills, Experience, Professional Qualities) and Preferred Qualifications. We could put Required Qualifications under Requirements, and Preferred Qualifications under Qualifications? Or maybe Requirements = Required Qualifications, Qualifications = Preferred Qualifications. We'll follow that. Skills: Could be extracted from Required Qualifications Technical Skills and maybe Professional Qualities? But we already have Skills heading; we could list technical skills (Splunk, SPL, Microsoft 365, Graph APIs, Python, PowerShell, Power BI, Excel) and maybe professional qualities as separate? But we already have Professional Qualities under Requirements. Might be okay to put Skills as a list of technical proficiencies. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can reorganize into headings. We must not repeat job title as heading. Must not put Job ID/requisition numbers as headings; we can drop them or fold into short p. We'll drop them. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip the long EEO statements, virtual recruiter stuff, privacy policy, benefits overview? Wait benefits overview is substantive; we need to keep benefits. But the benefits overview includes a lot of detail; we should keep it. However the benefits overview includes some boilerplate like "Everforth Apex Benefits Overview:" but that's okay as it's part of benefits. We'll keep the benefits details. We need to remove the duplicated EEO paragraphs (there are two). Also remove the virtual recruiter paragraph, the "By applying for this job..." etc. Also remove the "Everforth Apex Systems is an equal opportunity employer..." repeated. Also remove the "UnitedHealthcare creates..." etc. Also remove the address and NYSE ticker? That's maybe not boilerplate but could be considered metadata; but it's not specifically requested to keep. It's not part of job description; it's company info. Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The address and ticker might be considered company info not required; but it's not explicitly prohibited. However it's not substantive to the role; but we could keep it as part of About the role? Probably better to drop it as it's not directly about the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The address is not substantive to the role; but it's not prohibited. However it's not part of the job description content; it's company footer. Safer to drop it. Thus we will produce sections:

About the role

We are seeking a Splunk Reporting & Monitoring Analyst to design, build, and maintain advanced Splunk dashboards, reports, and alerts. This role supports proactive and reactive operational support for enterprise collaboration and productivity platforms within a financial services environment. The ideal candidate will translate technical data into actionable insights for various stakeholders.

Responsibilities

• Design, develop, and maintain custom Splunk dashboards, reports, and visualizations.
• Build optimized SPL queries to analyze large-scale log, event, and metric data.
• Develop real-time and near-real-time alerts to detect service degradation and abnormal behavior.
• Partner with Operations and Support teams to define meaningful KPIs and SLIs.
• Leverage Microsoft Graph APIs to ingest, correlate, and analyze M365 telemetry.
• Operate within a regulated financial services environment, ensuring reporting aligns with security and compliance requirements.
• Translate complex technical data into clear narratives and recommendations for technical and non-technical teams.
• Document dashboards, reports, alert logic, and data sources.

Requirements

• Advanced experience with Splunk Enterprise (search, dashboards, reports, alerts).
• Strong proficiency in SPL (Search Processing Language).
• Hands-on knowledge of Microsoft 365 services and Microsoft Graph APIs.
• Experience integrating external data sources and APIs into Splunk.
• Proficiency with Python, PowerShell, Power BI, and Excel.
• Experience supporting Operations and Support monitoring for enterprise applications.
• Strong understanding of incident management, problem management, and service monitoring.
• Experience working in a financial institution or other highly regulated environment.
• Familiarity with SLAs, SLOs, and service reliability concepts.
• Exceptional written and verbal communication skills.
• Ability to explain complex technical insights in simple, actionable terms.
• Strong problem-solving mindset with the ability to identify patterns and trends in data.
• A strong sense of ownership and accountability for deliverables.
• Ability to work independently while collaborating effectively across teams.

Qualifications

• Splunk certifications (Power User, Admin, Architect).
• Experience supporting collaboration platforms at an enterprise scale.
• Background in SRE, NOC, or production support environments.
• Experience building executive dashboards and operational scorecards.

Skills

• Advanced Splunk Enterprise (search, dashboards, reports, alerts)
• SPL (Search Processing Language)
• Microsoft 365 services and Microsoft Graph APIs
• Integrating external data sources and APIs into Splunk
• Python, PowerShell, Power BI, Excel

Benefits

• Medical, dental, vision, life, disability, and other insurance plans (optional layer of financial protection)
• ESPP (employee stock purchase program)
• 401K program with company match after 12 months of tenure
• HSA (Health Savings Account on the HDHP plan)
• SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions
• Corporate discount savings program and other discounts
• On-demand training program
• Access to certification prep and a library of technical and leadership courses/books/seminars after 6+ months tenure
• Certification discounts and other perks to associations including CompTIA and IIBA
• Dedicated customer service team for consultants
• Certified Career Coach
• Welcome Packet containing full list of benefits, programs, support teams and resources

We should not include Pay or Schedule sections. Make sure no extra text outside HTML. Output only HTML fragment. Check for any duplicated content: we have not included the location, employment type, contract duration. Those are substantive? They are location, employment type, contract duration. Should we include them? The instruction says preserve ALL substantive information. Location, employment type, contract duration are substantive. Where to put them? Could be part of About the role or a separate section like Job Details, but not in the prescribed headings. We could add a short paragraph under About the role that includes location, employment type, contract duration. The About the role currently only has role overview. We can extend it to include those details. Thus modify About the role paragraph: "We are seeking a Splunk Reporting & Monitoring Analyst to design, build, and maintain advanced Splunk dashboards, reports, and alerts. This role supports proactive and reactive operational support for enterprise collaboration and productivity platforms within a financial services environment. The ideal candidate will translate technical data into actionable insights for various stakeholders. Location: Plano, Texas (Onsite). Employment Type: Contract. Contract Duration: 12 Months." That preserves those details. Check for any other substantive info: Job#: 3053203 - we can drop as per instruction not to put Job ID as heading; we could fold into short p but we can drop entirely as it's not substantive to role? It's an identifier but maybe not needed. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short <