Senior Engineer, Cyber Defense Engineering

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate like EEO, etc. Also remove recruiting end date line? It says "Recruiting for this role ends on ." That's empty date; it's boilerplate, remove. We need to preserve all substantive info. Let's parse content: - Reference Code 4290 Country: US Locations: USA - Hermitage; USA - Nashville; USA - Tampa That's metadata; we can fold into short p. - Deloitte Global is the engine... (intro) maybe part of About the role? Could be "About the role" section. - Work you'll do: bullet list of responsibilities. - The team: description maybe part of About the role or separate? Could be "About the team". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put team description under About the role or maybe under Responsibilities? Probably About the role includes overview. - Qualifications Required: list of qualifications. - Education and experience: part of qualifications. - Preferred: list of preferred qualifications. - Our culture: maybe not a standard heading; could be omitted? It's not in allowed headings; but we could put under About the role? It's about culture; maybe we can include as a paragraph under About the role. - Professional development: maybe also under About the role or Benefits? Not exactly benefits. Could be omitted? But we need to preserve all substantive info; we could include under About the role as a paragraph. - Benefits: there is a Benefits paragraph. - Pay and Schedule: not present; do not create. - Skills: maybe we can extract skills from qualifications? Could create Skills section summarizing technical skills: Splunk, Azure, AWS, etc. But we must not invent; we can create Skills section if posting actually states them. The posting lists qualifications which are essentially skills. Could treat as Skills section. But we also have Qualifications section. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Qualifications and Skills. However we need to avoid duplication. The posting has "Qualifications Required:" list; also "Preferred:" list. Could treat those as Qualifications. Skills could be derived but maybe better to put technical skills under Skills. But we must not invent; we can list the skills explicitly mentioned: Splunk engineering, managing Splunk engineers, Cloud Services Azure/AWS, Splunk data onboarding, App/TA config, CIM validation, Universal/Heavy Forwarder config, encryption/compression, change control Azure DevOps, large scale Splunk env, Windows/Linux admin CLI, networking, firewalls, load balancers, enterprise applications security, IT ops best practices, communication, influencing, reasoning, conflict resolution, problem solving, etc. Those are indeed qualifications/skills. Could split: Qualifications for education/experience/certifications; Skills for technical abilities. But we need to ensure we don't lose info. Simplify: Use sections: About the role (intro + team + culture + professional development), Responsibilities (work you'll do), Qualifications (required + preferred + education), Skills (maybe we can omit if we think it's redundant). But we need to include all substantive info; if we omit Skills section, we still have the info in Qualifications. That's okay because we preserve all info. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine. Thus sections: About the role, Responsibilities, Qualifications, Benefits. We need to include metadata (Reference Code, Locations) as short p maybe under About the role or separate? Could be a p at top. We must not include Job ID/requisition numbers as headings; we can fold into short p. Let's craft:

Reference Code: 4290. Locations: Hermitage, TN; Nashville, TN; Tampa, FL.

Then

About the role

with paragraphs: Deloitte Global is the engine... The team... Our culture... Professional development... We need to keep the content exactly, not summarizing. We'll copy sentences. Let's extract paragraphs: Intro: "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." Team: "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." Culture: "Our culture At Deloitte Global people are valued and respected for who they are - with opportunities to bring their unique perspectives, talents and passions to business challenges. Our global workspace creates room for individuality and collaboration. Ours is an inclusive, supportive, connected culture with a focus on development, flexibility, and well-being. This culture makes Deloitte Global one of the most rewarding places to work, and to transform your career." Professional development: "Professional development From entry-level employees to senior leaders, we believe in investing in you, helping you identify and hone your unique strengths at every step of your career. We offer opportunities to build new skills, take on leadership opportunities, and connect and grow through mentorship. From on-the-job learning experiences to formal development programs, our professionals have a variety of opportunities to continue to grow throughout their career." We need to ensure no duplicated lines. The text includes "At Deloitte Global people are valued..." etc. We'll keep. Now Responsibilities: list from "Work you'll do". Items: - Partner with development and operations teams to develop practical automation solutions and custom modules. - Co-lead team initiatives to continuously refine our deployment practices for improved reliability, repeatability, and security. - Creating plans and collaborating with other GEMS Engineering team members, while coordinating with development and business teams. - Develop requirements for data ingestion methods based on input from stakeholders/leadership. - Clearly document and diagram deployment-specific aspects of architectures and environments, working closely with various teams to create application runbooks, playbooks, and knowledge base documents. - Troubleshoot issues in production and other environments, applying debugging and problem-solving techniques (e.g., log analysis, non-invasive tests). - Suggest deployment patterns & practices improvements based on learnings from past deployments and production issues, collaborate with GEMS Engineering team members to implement these. - After hours on-call support occasionally required. We need to preserve bullet points as

• . Now Qualifications: includes Required list, Preferred list, Education and experience. Let's extract Required qualifications (bulleted): - 2+ years Splunk engineering experience - 1+ years managing other Splunk engineers or projects - Strong understanding of Cloud Services - Azure, AWS - Strong understanding of Splunk data onboarding including Splunk App/TA configuration and CIM validation - Universal/Heavy Forwarder configuration experience, including encryption and compression settings - Experience working with a strict change control process utilizing tools such as Azure DevOps - Management/deployment experience with large scale/distributed Splunk environments - A solid understanding of Windows and Linux administration utilizing Command Line Interface (CLI) - Knowledge of networking, firewalls, load balancers etc. - Demonstrate understanding of common enterprise applications (especially in the area of security) - Knowledge of best practices for IT operations in an always-on, always-available service model - Excellent communication skills and the ability to communicate appropriately with/manage technical teams - Excellent influencing and reasoning skills; good at conflict resolution and consensus building - Ability to quickly explore, examine and understand complex problems Education and experience: - Bachelor's degree in Computer Science, Computer Engineering, Finance, Mathematics, Business Information Systems or other bachelor's degree combined with relevant experience and accomplishments. - One or more of the following: Splunk Certified Admin, Splunk Certified Architect, Splunk Certified Consultant Preferred: - Experience with Cribl administration and data onboarding - Experience in working in a large global organization We'll put all under Qualifications section, maybe separate Required and Preferred as subheadings? But we only allowed headings list; we could still use

  ? Not allowed. Better to keep as

  with items, and maybe add a note "Required:" and "Preferred:" as plain text inside

  before lists. That's okay. Now Benefits: paragraph: "Benefits 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 need to keep that exactly. Now we must not include recruiting line. Now produce HTML fragment:

  Reference Code: 4290. Locations: Hermitage, TN; Nashville, TN; Tampa, FL.

  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.

  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.

  Our culture At Deloitte Global people are valued and respected for who they are - with opportunities to bring their unique perspectives, talents and passions to business challenges. Our global workspace creates room for individuality and collaboration. Ours is an inclusive, supportive, connected culture with a focus on development, flexibility, and well-being. This culture makes Deloitte Global one of the most rewarding places to work, and to transform your career.

  Professional development From entry-level employees to senior leaders, we believe in investing in you, helping you identify and hone your unique strengths at every step of your career. We offer opportunities to build new skills, take on leadership opportunities, and connect and grow through mentorship. From on-the-job learning experiences to formal development programs, our professionals have a variety of opportunities to continue to grow throughout their career.

  Responsibilities

  • Partner with development and operations teams to develop practical automation solutions and custom modules.
  • Co-lead team initiatives to continuously refine our deployment practices for improved reliability, repeatability, and security.
  • Creating plans and collaborating with other GEMS Engineering team members, while coordinating with development and business teams.
  • Develop requirements for data ingestion methods based on input from stakeholders/leadership.
  • Clearly document and diagram deployment-specific aspects of architectures and environments, working closely with various teams to create application runbooks, playbooks, and knowledge base documents.
  • Troubleshoot issues in production and other environments, applying debugging and problem-solving techniques (e.g., log analysis, non-invasive tests).
  • Suggest deployment patterns & practices improvements based on learnings from past deployments and production issues, collaborate with GEMS Engineering team members to implement these.
  • After hours on-call support occasionally required.

  Qualifications

  Required:

  • 2+ years Splunk engineering experience
  • 1+ years managing other Splunk engineers or projects
  • Strong understanding of Cloud Services - Azure, AWS
  • Strong understanding of Splunk data onboarding including Splunk App/TA configuration and CIM validation
  • Universal/Heavy Forwarder configuration experience, including encryption and compression