Staff SOC Engineer - Security Telemetry & Detection Platforms

We need to output HTML fragment with sections: About the role? The posting includes introductory paragraph about RGA and role description. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. We have content: description of role (intro) could be "About the role". Then "Principle Duties" list -> Responsibilities. Then "Qualifications" section includes Education, Work Experience, Licenses & Certifications. Then "Skills & Abilities" -> Skills. Then "What you can expect from RGA" maybe Benefits? Actually that's more about culture; could be Benefits? But we have explicit Compensation Range and benefits mention: "RGA also maintains a full range of health, retirement, and other employee benefits." Also mention annual bonus plan, long-term equity incentive plan. So we can have Benefits section. Pay section: Compensation Range. Schedule: not mentioned. So we omit Schedule. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, AI screening, etc. Also remove application instructions (none). Remove duplicated lines. We need to preserve all substantive information. So include details: role purpose, duties list, qualifications details, skills, benefits, pay. We must not include filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /. Use

headings,

• for lists,

  for prose. We need to decide which content goes into which section. About the role: introductory paragraph(s) describing RGA and role purpose. Could combine first two paragraphs: "You desire impactful work...". Actually the posting starts: "You desire impactful work. You’re RGA ready RGA is a purpose-driven organization..." We'll paraphrase? Must preserve all substantive information, not invent or summarize away detail. We can keep the sentences as is, but we need to format as prose in

  . We must not omit any substantive info. So we need to include all sentences from the intro up to "Principle Duties". Let's extract: "You desire impactful work. You’re RGA ready RGA is a purpose-driven organization working to solve today’s challenges through innovation and collaboration. A Fortune 200 Company and listed among its World’s Most Admired Companies, we’re the only global reinsurance company to focus primarily on life- and health-related solutions. Join our multinational team of intelligent, motivated, and collaborative people, and help us make financial protection accessible to all. The Staff SOC Engineer - Security Telemetry & Detection Platforms is a hands-on security engineering role responsible for building, operating, and continuously improving enterprise security telemetry and detection platforms. This role ensures high-quality visibility and detection are embedded throughout operations and delivery lifecycles - applying secure by design principles to data collection, transformation, storage, and alerting across hybrid, cloud native, and on premises environments. The Staff SOC Engineer proactively anticipates telemetry gaps, translates detection requirements into actionable engineering work, and operationalizes controls that are scalable, resilient, and measurable. Through close collaboration with security operations, architecture, infrastructure, and product teams, this role advances SOC maturity and enables adaptive defenses that support business growth and regulatory compliance." That's the intro. We'll put that in About the role

  . Responsibilities: list of duties under "Principle Duties". Each bullet starts with a verb. We'll put each as

• . Qualifications: includes Education, Work Experience, Licenses & Certifications. We'll maybe combine into one Qualifications section with sublists? But we need to use
  • for any list of duties/requirements/benefits. So we can have a
    for qualifications items. However we have subcategories; we could just list each qualification as separate
    • preserving details. But we might lose grouping. Could also have nested lists? Not prohibited but we should keep simple. We'll create a
      with each qualification item as
      • containing the details. Education: "Bachelor’s degree in arts/sciences (BA/BS) or equivalent experience – RequiredMaster’s degree in Arts/Sciences (MA/MS) or professional industry certification Preferred". Note there is missing space between RequiredMaster’s. We'll keep as is. Work Experience: "6+ years of progressive experience in security/infrastructure engineering or SOC engineering focused on SIEM/EDR, telemetry pipelines, and detection content Demonstrated success deploying and operating SIEM, EDR, SOAR, and data pipeline solutions at enterprise scale, including RBAC, API integrations, and platform hygieneHands‑on experience engineering data ingestion pipelines and normalizing logs from operating systems, AWS, Azure, and network sources Strong technical background and tacit understanding of detection engineering, OCSF modeling, SPL optimization, CIM mapping, and content tuning to reduce ingest volume and improve signal to noise". We'll keep. Licenses & Certifications: "Relevant platform certifications (e.g., Splunk Core/Cloud, Cribl Certified Observability Engineer, CrowdStrike CCFA/CCFR) – Preferred Security certifications (e.g., CISSP, GSEC, GCDA, Cloud+) – Preferred". We'll keep. Skills: "Skills & Abilities" list: Proven ability to collaborate..., Ability to map..., Familiarity with NIST..., Experience supporting 24/7 SOC..., Advanced analytical..., Experience integrating security telemetry into CI/CD..., Proficiency in automation and scripting... We'll separate required vs preferred? We'll just list each as
      • . Benefits: "Gain valuable knowledge from and experience with diverse, caring colleagues around the world.Enjoy a respectful, welcoming environment that fosters individuality and encourages pioneering thought.Join the bright and creative minds of RGA, and experience vast, endless career potential. We’re excited to get to know you and connect your unique skills with our global opportunities." plus "RGA also maintains a full range of health, retirement, and other employee benefits." plus "annual bonus plan that includes all roles and some positions are eligible for participation in our long-term equity incentive plan." We'll combine into Benefits

        maybe with

        for bullet points? The benefits are not a list but we can keep as prose. Pay: "Compensation Range $126,710.00 - $188,840.00 Annual Base pay varies depending on job-related knowledge, skills, experience and market location. In addition, RGA provides an annual bonus plan that includes all roles and some positions are eligible for participation in our long-term equity incentive plan." Actually bonus plan already mentioned in benefits; but we can still include in Pay. We'll avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include both mentions. Might duplicate but okay. We'll include Pay section with that sentence. We must not include Schedule. Now produce HTML:

        About the role

        ...intro...

        Responsibilities

        • Administer and engineer improvements to enterprise security telemetry and detection platforms- including SIEM, EDR, SOAR, and data pipeline solutions - ensuring reliability, performance, and cost efficiency.
        ... etc each bullet. We need to ensure we keep hyphens etc. Let's list all duties exactly as in posting: "Administer and engineer improvements to enterprise security telemetry and detection platforms- including SIEM, EDR, SOAR, and data pipeline solutions - ensuring reliability, performance, and cost efficiency." "Implement secure by default telemetry patterns and logging standards across operating systems, cloud, and network data sources." "Design, build, and maintain data pipelines (Routes, Pipelines, Packs) for secure, cost managed, and high throughput log routing, enrichment, filtering, and transformation into SIEM, archive, and other destinations." "Engineer SIEM content (SPL searches, correlation rules, alerts, dashboards, data models, CIM mapping, RBA where applicable) with an emphasis on signal quality, performance, and SLO/KPI driven cost control" "Define and maintain role-based access controls (RBAC), least privilege models, and user provisioning across telemetry and detection platforms to enable auditable operations." "Contribute to integration and automation across SOC tooling and enterprise systems (e.g., Tines, cloud native logging in AWS/Azure/GCP, threat intel feeds, ticketing/ITSM) to streamline detection, enrichment, and response workflows." "Author and maintain explicit documentation - including system design documents, reference implementations, runbooks, and technical decision records capturing rationale, architecture, and operational procedures." "Apply tacit understanding of SIEM/EDR behavior, data schemas, and pipeline constraints to troubleshoot complex issues, reduce noise, and close visibility gaps." "Participate in incident response by developing targeted searches, conducting log analysis, identifying root causes, and providing platform/tooling expertise during high severity events." "Implement and continuously improve control validation (data quality checks, parsing/field extraction tests, content regression tests) and observability (health monitors, capacity, latency, backlog, and error metrics)." "Evaluate emerging telemetry sources, detection approaches, and vendor capabilities; build proofs of concept to assess fit, security posture, and operational impact." "Support identity, access, and privilege strategies within SOC platforms (API tokens, service accounts, secrets management, SSO/SAML/OIDC) aligned to enterprise guardrails." "Collaborate in post incident reviews and resilience improvements, translating findings into backlog items for pipeline hardening, new log sources, or content tuning." "Contribute to responsible logging and monitoring for AI enabled applications and platforms (e.g., model/service telemetry, prompt/audit logs), integrating risks and controls into detection strategy." "Serve as the security telemetry and detection engineering representative for Global Security Office in technical forums, ensuring platform considerations are aligned with enterprise strategies and governance." "Perform other duties as assigned." Now Qualifications: we need to list each bullet maybe as separate
        • . We'll include Education, Work Experience, Licenses & Certifications as separate items. Education: "Bachelor’s degree in arts/sciences (BA/BS) or equivalent experience – RequiredMaster’s degree in Arts/Sciences (MA/MS) or professional industry certification Preferred" Work Experience: "6+ years of progressive experience in security/infrastructure engineering or SOC engineering focused on SIEM/EDR, telemetry pipelines, and detection content Demonstrated success deploying and operating SIEM, EDR, SOAR, and data pipeline solutions at enterprise scale, including RBAC, API integrations, and platform hygieneHands‑on experience engineering data ingestion pipelines and normalizing logs from operating systems, AWS, Azure, and network sources Strong technical background and tacit understanding of detection engineering, OCSF modeling, SPL optimization, CIM mapping, and content tuning to reduce ingest volume and improve signal to noise" Licenses & Certifications: "Relevant platform certifications (e.g., Splunk Core/Cloud, Cribl Certified Observability Engineer, CrowdStrike CCFA/CCFR) – Preferred Security certifications (e.g., CISSP, GSEC, GCDA, Cloud+) – Preferred" We could split into two items for platform certs and security certs but it's okay. Skills: list each bullet: "Proven ability to collaborate across security operations, architecture, infrastructure, and product teams; strong stakeholder communication and documentation skills – Required" "Ability to map and document complex systems and processes, including data lineage and schema/field mappings – Required" "Familiarity with NIST frameworks, MITRE ATT&CK, and secure by design practices; experience with control validation and metrics/KPIs for continuous improvement – Required" "Experience supporting 24/7 SOC operations, including on call participation and multi region ingestion scenarios – Required" "Advanced analytical and problem-solving skills; competency with analysis and diagramming tools (e.g., Lucidcharts, Visio, Excel) – Required" "Experience integrating security telemetry into CI/CD pipelines and applying version control, testing, and staged releases for detections and pipeline changes – Preferred" "Proficiency in