Jobs · Engineering

Lead Cyber Threat Intelligence Data Architect

Humana · Washington, DC · 1 mo ago
RemoteRemoteEngineering$129k–$178k/yrFull-time
We need to output HTML fragment with sections: About the role (maybe "About the role" or similar). The posting includes description: "Become a part of our caring community (remote in location) The Lead Intelligence Data Architect serves as the subject matter expert...". We need to reformat into semantic HTML: use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: - Intro paragraph about role (maybe "About the role"). - Key Responsibilities (list of responsibilities). - Qualifications (Required and Preferred). - Work at Home Requirements (maybe schedule? Not exactly schedule; but we have "Scheduled Weekly Hours 40" and "Pay Range". So we have Pay and Schedule sections. - Benefits description. - About Us (maybe not needed? Could be "About the company"? Not in list of allowed headings but we could include "About Us" as maybe not required; but we can include if we want but they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those. "About Us" maybe not needed; but we could incorporate into "About the role"? Probably not. The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also include other headings if needed, but better to stick to those. The posting includes "About Us" and "Equal Opportunity Employer" which we should remove as boilerplate. So we will omit those. We need to preserve all substantive information: intro description, responsibilities list, qualifications (required and preferred), work at home requirements (maybe part of Schedule? Actually it's about remote work requirements: internet speed, dedicated space, travel). Could be part of "Schedule" or maybe a separate section like "Work Arrangements". But not in allowed headings; maybe we can incorporate into "Schedule" or "About the role". However schedule heading is for weekly hours; we have "Scheduled Weekly Hours 40". Also we have Pay Range. So we will have sections: About the role (intro), Responsibilities (list), Qualifications (maybe split into Required and Preferred but we can combine), Benefits, Pay, Schedule. We also have "Work at Home Requirements" which is substantive; we need to include it somewhere. Could be part of "Schedule" or maybe a separate section like "Work Arrangements". Since not in list, but we could still include a heading if we think it's needed. The instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says "Prefer a few substantive sections over many thin ones." So we could add a section like "Work Arrangements" if needed. However we could also fold those details into "Schedule" or "About the role". The schedule section is about weekly hours; we could add a paragraph about remote work requirements under Schedule or maybe a new section "Work Arrangements". I'd lean to add a section "Work Arrangements" to keep clarity, but it's not in the examples; but it's not prohibited. However they said "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies those are the expected headings; maybe they want us to only use those. Safer to stick to those. Then we need to place work-from-home details somewhere. Could be under "Schedule" as additional info, or under "About the role". I'd put under "Schedule" as it's about work arrangement. Thus sections: - About the role: intro paragraph(s) describing role. - Responsibilities: list of responsibilities (key responsibilities bullet points). - Qualifications: list of required and preferred qualifications (maybe separate subheadings? But we can just list all as
    • ). - Benefits: paragraph describing benefits. - Pay: paragraph with pay range and bonus info. - Schedule: paragraph with weekly hours, remote work requirements (internet speed, dedicated space, travel). We must not repeat the job title as heading. So no

      Lead Intelligence Data Architect

      . Good. We must not include Job ID/requisition numbers. We must remove duplicated lines: The intro had repeated sentences; we need to preserve substance but not duplicate. We'll write a concise paragraph capturing the role's purpose. We must preserve all substantive information: ensure we don't lose any details. Let's extract substantive content: Intro: "Become a part of our caring community (remote in location) The Lead Intelligence Data Architect serves as the subject matter expert and functional owner for how Humana's cyber threat intelligence is collected, organized, kept current, and made usable across enterprise information security teams and tools. This role ensures Humana's threat intelligence is structured and maintained so it can be reliably referenced by both analysts and the AI-driven and automated systems that leverage it. The Lead sets the standards, drives continuous improvement in how threat intelligence is structured and made usable, and shapes how threat intelligence supports Humana's information security focused AI and automation initiatives." That's the core. Duplicate later same sentences; we just keep once. Responsibilities: Under "Key Responsibilities" we have several bullet-like paragraphs: - Threat Intelligence Platform (TIP) Ownership - Own Anomali ThreatStream administration, configuration, and platform strategy - Manage feeds, integrations, data quality, and platform governance - Serve as the subject matter expert to CTI analysts and stakeholder teams on threat intelligence data structure, integration, and delivery - Structure and Organize Threat Intelligence - Set and evolve the standards, methods, and best practices for how Humana's cyber threat intelligence is structured, maintained, and delivered so it is usable by both analysts and AI systems - Design and maintain how Humana's cyber threat intelligence is organized so it is consistent, searchable, and reusable — structuring it so AI agents and automated systems can reliably query and consume it - Build the workflows and pipelines that turn analytical work into structured intelligence records optimized for both human use and AI consumption - Integrate Threat Intelligence with Stakeholder AI and Automation - Own the technical relationship with stakeholders that consume CTI data through AI agents, automated systems, and other tools - Manage API access, data versioning, and analytics on how CTI data is being used by downstream systems - Work with consuming teams to understand what threat intelligence their AI and automation workflows need, and ensure it is available in a form those systems can use - Identify opportunities to improve tools, workflows, and processes that impact how CTI supports security operations, detection engineering, and vulnerability management - Collection Management - Own the collection plan and ensure sources are aligned to intelligence requirements and stakeholder information needs - Evaluate source quality, timeliness, and value to ensure intelligence meets stakeholder needs We need to output as
      • for any list of duties/requirements/benefits. So we can flatten all responsibilities into a single list, or we could keep subheadings? But we cannot use headings inside list? We could have

        Responsibilities

        then
        • each responsibility. That's fine. Qualifications: Required and Preferred. Required: - 7+ years of related experience across cyber threat intelligence, security data platforms, or intelligence infrastructure, including experience leading projects or functional initiatives - Demonstrated understanding of how AI and automated systems consume structured data, and the ability to organize threat intelligence so it is usable by both analysts and AI-driven tools - Bachelor's degree or equivalent experience - Strong understanding of CTI workflows, collection management, and intelligence requirements - Demonstrated intellectual curiosity and adaptability - Firm understanding of the cyber threat landscape - Experience administering a threat intelligence platform, ideally Anomali ThreatStream - Experience structuring threat intelligence data, designing schemas, and building API-based integrations - Demonstrated ability to own a technical function independently and drive standards across stakeholders Preferred: - Familiarity with MITRE ATT&CK, STIX/TAXII, and other structured intelligence frameworks - Experience integrating threat intelligence with detection engineering, SOC, or vulnerability management workflows We'll list all as
        • under Qualifications. Benefits: Paragraph: "Humana, Inc. and its affiliated subsidiaries (collectively, “Humana”) offers competitive benefits that support whole-person well-being. Associate benefits are designed to encourage personal wellness and smart healthcare decisions for you and your family while also knowing your life extends outside of work. Among our benefits, Humana provides medical, dental and vision benefits, 401(k) retirement savings plan, time off (including paid time off, company and personal holidays, paid parental and caregiver leave), short-term and long-term disability, life insurance and many other opportunities." Pay: Paragraph: "The compensation range below reflects a good faith estimate of starting base pay for full time (40 hours per week) employment at the time of posting. The pay range may be higher or lower based on geographic location and individual pay will vary based on demonstrated job related skills, knowledge, experience, education, certifications, etc. $129,300 - $177,800 per year This job is eligible for a bonus incentive plan. This incentive opportunity is based upon company and/or individual performance." Schedule: Paragraph: "Scheduled Weekly Hours 40" plus work-at-home requirements: "Work at Home Requirements: To ensure Home or Hybrid Home/Office employees’ ability to work effectively, the self-provided internet service of Home or Hybrid Home/Office employees must meet the following criteria: At minimum, a download speed of 25 Mbps and an upload speed of 10 Mbps is required; wireless, wired cable or DSL connection is suggested. In certain roles, the minimum recommended internet speed required by Humana may not be sufficient for business needs. Humana reserves the right to require associates to upgrade their internet service if necessary. Work from a dedicated space lacking ongoing interruptions to protect member PHI / HIPAA information. Travel: While this is a remote position, occasional travel to Humana's offices for training or meetings may be required." We need to combine into a paragraph or maybe separate sentences. We must not include boilerplate like Equal Opportunity Employer, etc. Now produce HTML fragment:

          About the role

          ...

          Responsibilities

          • ...
          • ...

          Qualifications

          • ...
          • ...

          Benefits

          ...

          Pay

          ...

          Schedule

          ...

          Make sure no extra whitespace? It's fine. Check for any duplicated content: we removed duplicate intro sentences. Check for any placeholder text: none. Check for any mention of "commensurate with experience" etc: not present.

Similar jobs