Senior Red Team Operator

We need to output HTML fragment with sections: About the role? The posting includes "Work you'll do" which is responsibilities. Also "Qualifications Required:" and "Preferred:" etc. Also "Benefits" section present. Also maybe "Our culture" and "Professional development" but those are not required headings per list: we can include if they have substantive content. The instruction: Use

for section headings (e.g. 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 have Benefits section present (the paragraph about benefits). No Pay or Schedule specifics. So we should not create Pay or Schedule sections. We need sections: maybe "Responsibilities" (Work you'll do), "Qualifications" (Required and Preferred), "Benefits". Also maybe "About the role" could be the introductory paragraph about Leading a small team etc. But that is essentially responsibilities. Could combine. We need to preserve all substantive info: location list, requisition ID maybe as minor metadata in a short

  . Also mention Deloitte Global description. We need to remove boilerplate: "Our culture", "Professional development" maybe we can keep as sections if they have substantive content. They are not in the list of headings but we could still use

  for them? 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 suggests those as examples. Probably we should stick to those headings only if content matches. "Our culture" and "Professional development" could be considered "About the role" or maybe not needed. To keep few sections, we could combine them into a single "About the role" paragraph. Thus sections: About the role (intro + team description), Responsibilities (detailed list), Qualifications (required and preferred), Benefits. We need to use

  • for any list of duties/requirements/benefits. So responsibilities list should be
    . Qualifications list also
    . Benefits list maybe
    if they list items; but they only have a paragraph describing benefits program. Could keep as

    . We must not repeat job title as heading. So no

    Senior Red Team Operator

    . We need to include minor metadata like Requisition ID and locations in a short

    . Possibly at top. Let's extract content: - Requisition ID: 1864 - Country: United States - US Locations: list of cities. We can put:

    Requisition ID: 1864 | Locations: Atlanta, Chicago, Cincinnati, Dallas, Hermitage, Indianapolis, Kansas City, Nashville, San Antonio, St. Louis, Tampa

    Now About the role: The paragraph starting "Deloitte Global is the engine..." and "Work you'll do Leading a small team..." Actually the "Work you'll do" is responsibilities. The preceding sentences about Deloitte Global and team description could be About the role. Let's craft About the role: "Deloitte Global is the engine of the Deloitte network. Our professionals reach across disciplines and borders to develop and lead global initiatives. We deliver strategic programs and services that unite our organization. In this role you will lead a small team of Red Team Operators in the planning, execution, and reporting of Red Team engagements around the globe." But we must preserve all substantive info; we can't omit details like "The team Deloitte Technology works at the forefront..." etc. That is also part of About the role. So we should include that paragraph. Thus About the role could combine the two paragraphs: "Deloitte Global is the engine..." and "The team Deloitte Technology works at the forefront..." plus the leading team sentence. Let's copy them exactly: "Deloitte Global is the engine of the Deloitte network. Our professionals reach across disciplines and borders to develop and lead global initiatives. We deliver strategic programs and services that unite our organization." "The team Deloitte Technology works at the forefront of technology development and processes to support and protect Deloitte around the world. In this truly global environment, we operate not in what is but rather what can be to help Deloitte deliver and connect with its clients, its communities, and one another in ways not previously conceived." And the leading team sentence: "Work you'll do Leading a small team of Red Team Operators in the planning, execution, and reporting of Red Team engagements around the globe." But "Work you'll do" is heading for responsibilities; we can keep that sentence as start of responsibilities. Thus About the role: first two paragraphs. Responsibilities: list of duties after "Work you'll do Leading a small team..." Actually the sentence "Work you'll do Leading a small team..." is followed by colon? Actually text: "Work you'll do Leading a small team of Red Team Operators in the planning, execution, and reporting of Red Team engagements around the globe. This includes, but is not limited to:" then bullet list. Thus responsibilities list includes all items after that. We need to capture each duty as
    • . Let's extract: - Performing intelligence gathering against target networks, people, processes, and technologies. - Finding creative ways to obtain a foothold in a target network. - Delivering malware and establishing command and control (C2). - Moving stealthily within target networks, satisfying the campaign objectives, while staying undetected by the blue teams. - Establishing persistence and strategically tuning long-haul beacons to maintain long-term footholds where necessary. - Ensuring adherence to the Rules of Engagement during every step of the Red Team engagements. - Maintaining operational oversite of all actions conducted during Red Team engagements. - Ensuring that every action is planned, executed, and logged properly at all times by every operator. - Maintaining in-depth documentation and auditing of actions taken during Red Team operations, at all times, for the purposes of deconfliction and non-repudiation. - Identifying and acting on opportunities to train and mentor other members of the Red Team. - Assisting in the management of the Red Team Attack Network and the implementation of new tools and techniques to improve the team's tradecraft. - Sharing your research within the Deloitte Global Red Team community, and with the broader security organization, by writing blogs, speaking at conferences, or publishing code. - Developing operational processes, field manuals, and attack methodologies to continuously improve the quality of engagements and knowledge sharing amongst the team. - Ensure deliverables meet the quality and timeliness expected of a world-class Red Team. - Working closely with a wide variety of Deloitte's industry leading information security teams to identify and reduce risk around the globe. Note: "Maintaining operational oversite" maybe typo but keep. Now Qualifications Required: list: - 3+ years of Red Team experience. - A deep understanding of threat actor tactics, techniques, and procedures (TTPs). - Experience with, and a deep understanding of, digital forensics and incident response capabilities and procedures. - Experience with leading Red Team Operations against companies and their associated people, processes, and technologies. - The ability to create, update, and maintain documentation ranging from Red Team TTPs to governing documentation as needed. - Experience with enumerating and attacking Windows Active Directory and Azure EntraID environments. - Experience leading the designing, building, maintaining, and utilization of covert C2 infrastructure in various cloud platforms and environments. - Automation experience is a plus! - Experience with modern malware development and obfuscation techniques. - A deep understanding of enterprise security architecture and the associated security controls. - A deep understanding of monitoring, detections, and indicators of compromise/attack, and the implications they have on covert Red Team Operations. - Hands on experience working with industry leading Red Team tools like Cobalt Strike, Nighthawk C2, Bloodhound, Evilginx2, etc... Preferred: list: - Relevant certifications such as OSCP, OSCE, OSEP, OSED, OSEE, CRTP, CRTE, etc. - Public examples of blogs, conference talks, and open-source tooling demonstrating your expertise. - Experience operating against security products such as Microsoft Defender for Endpoint/Identity and CrowdStrike Falcon. - Experience with Social Engineering (physical, phishing). - Experience with Outflank OST. - Experience automating infrastructure deployment with Ansible and Terraform. - Experience leading red teaming efforts. - Experience with fully remote positions. - Limited immigration sponsorship may be available. Note: "Limited immigration sponsorship may be available." is a preference? It's under Preferred? Actually appears after "Experience with fully remote positions." It's a separate sentence but still part of Preferred? We'll include as a bullet. Now Benefits: paragraph: "At Deloitte, we value our people and offer employees a broad range of benefits. Our Total Rewards program reflects our continued commitment to lead from the front in everything we do-that's why we take pride in offering a comprehensive variety of programs and resources to support your health and well-being." We could also include "Professional development" and "Our culture" but maybe not needed. However they contain substantive info about culture and development. Could we include them as separate sections? The instruction says prefer a few substantive sections over many thin ones. Adding two more sections would increase count. Might be okay if they are substantive. But we could incorporate them into About the role or a separate "About Deloitte" section. However the instruction's examples didn't include culture or development. Safer to omit them to keep few sections. But we must preserve ALL substantive information; omitting them would lose info. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot drop the culture and professional development paragraphs. We need to include them somewhere. Could we add a section "About Deloitte" or "Company Overview"? Not in the list but we could still use

      for it? 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 suggests those as examples. It might be okay to add a heading like "About Deloitte". However to be safe, we could incorporate those paragraphs into the About the role section, making it longer but still one section. That would preserve info while not adding extra headings. The About the role section would then contain: Deloitte Global description, team Deloitte Technology description, culture, professional development. That's a lot but still one section. Thus we will have sections: About the role (includes all descriptive paragraphs about Deloitte, team, culture, development), Responsibilities, Qualifications (maybe split Required and Preferred? Could be two subheadings but we can keep as one Qualifications section with two sublists? The instruction says use

      for section headings; we could have

      Qualifications

      and inside we can have

      Required:

      ...

      Preferred:

      ...
      . That's acceptable. Benefits section. We must not create Pay or Schedule sections. Now produce HTML fragment. We'll start with a

      for metadata. Then