Senior Engineer, Cyber Defense Engineering
Deloitte · Hermitage, TN · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections only if real content. Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which content fits each.
We have:
- Intro: "Deloitte Global is the engine of the Deloitte network..." That's about the team maybe.
- "Work you'll do" bullet list of duties.
- "The team Deloitte Technology works at the forefront..." description of team.
- "Qualifications Required:" list.
- "Education and experience:" list.
- "Preferred:" list.
- "Our culture" paragraph.
- "Professional development" paragraph.
- "Benefits" paragraph.
We need to map to sections.
Probably:
- About the role: combine intro and team description? Could be "About the role" includes overview of role and team.
- Responsibilities: the "Work you'll do" list.
- Requirements: maybe the "Qualifications Required:" list.
- Qualifications: maybe the "Education and experience:" plus "Preferred:"? But we have both Qualifications and Skills sections. Could treat Qualifications as required qualifications, Skills as preferred or skills.
But we need to avoid filler. Let's extract concrete content.
Let's list 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.
That's responsibilities.
Qualifications Required list:
- 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
Culture etc not needed for sections unless we map to About the role or Benefits.
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."
That's benefits content.
Professional development paragraph: maybe could be part of Benefits? But we have no separate section for professional development unless we treat as Benefits? But we should only include sections with real content. Benefits we have. Professional development could be considered part of Benefits but we don't have a heading for it; we could include under Benefits as additional detail. However instruction: Use sections only when posting has real, specific content for it. We have benefits content, so we can include Benefits section with that paragraph. Professional development could be omitted or included under Benefits? Might be better to include as part of Benefits, but we could also create a separate section "Professional development" but not in allowed headings list. The allowed headings are only those listed; we should not create other headings. So we should incorporate professional development into Benefits or maybe About the role? Probably better to include under Benefits as additional detail.
Pay and Schedule: not provided, so omit.
Skills: we could list skills from qualifications? But we already have Qualifications and Requirements sections. Might be redundant. However we need to decide which sections to include.
We have:
- About the role: could contain overview paragraphs (Deloitte Global is the engine..., The team Deloitte Technology works...). That's substantive.
- Responsibilities: the list.
- Requirements: maybe the "Qualifications Required:" list.
- Qualifications: maybe the "Education and experience:" plus "Preferred:"? But we already used Requirements for required qualifications; Qualifications could be for education/certifications. However the instruction says we can use Qualifications heading; we need to avoid filler. We have education and certifications content, so we can include Qualifications section.
- Skills: maybe we could list specific technical skills like Splunk, Azure, AWS, etc. But those are already in qualifications. Could combine.
Better to follow typical job posting: About the role (overview), Responsibilities (duties), Requirements (mandatory), Qualifications (education/certifications), Skills (preferred or technical), Benefits.
Let's assign:
About the role: paragraphs about Deloitte Global and team.
Responsibilities: the bullet list.
Requirements: the "Qualifications Required:" list (the 2+ years Splunk etc).
Qualifications: Education and experience (Bachelor's degree, certifications).
Skills: Preferred items (Cribl, large global org) maybe also mention communication etc but those already in requirements. We'll put preferred as Skills.
Benefits: the benefits paragraph.
We must not repeat job title as heading. We'll not include.
We need to output HTML fragment only.
Let's craft:
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. First, remove boilerplate: "Senior Engineer, Cyber Defense EngineeringReference Code 4290 Country: US Locations: USA - Hermitage; USA - Nashville; USA - Tampa" maybe treat as metadata; we can put in a short
. Also "Recruiting for this role ends on ." is incomplete; we can drop. We need sections: - About the role: maybe the paragraph after "Work you'll do". Actually "Work you'll do" is a heading but we need to map to About the role? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which content fits each.
We have:
- Intro: "Deloitte Global is the engine of the Deloitte network..." That's about the team maybe.
- "Work you'll do" bullet list of duties.
- "The team Deloitte Technology works at the forefront..." description of team.
- "Qualifications Required:" list.
- "Education and experience:" list.
- "Preferred:" list.
- "Our culture" paragraph.
- "Professional development" paragraph.
- "Benefits" paragraph.
We need to map to sections.
Probably:
- About the role: combine intro and team description? Could be "About the role" includes overview of role and team.
- Responsibilities: the "Work you'll do" list.
- Requirements: maybe the "Qualifications Required:" list.
- Qualifications: maybe the "Education and experience:" plus "Preferred:"? But we have both Qualifications and Skills sections. Could treat Qualifications as required qualifications, Skills as preferred or skills.
But we need to avoid filler. Let's extract concrete content.
Let's list 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.
That's responsibilities.
Qualifications Required list:
- 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
Culture etc not needed for sections unless we map to About the role or Benefits.
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."
That's benefits content.
Professional development paragraph: maybe could be part of Benefits? But we have no separate section for professional development unless we treat as Benefits? But we should only include sections with real content. Benefits we have. Professional development could be considered part of Benefits but we don't have a heading for it; we could include under Benefits as additional detail. However instruction: Use sections only when posting has real, specific content for it. We have benefits content, so we can include Benefits section with that paragraph. Professional development could be omitted or included under Benefits? Might be better to include as part of Benefits, but we could also create a separate section "Professional development" but not in allowed headings list. The allowed headings are only those listed; we should not create other headings. So we should incorporate professional development into Benefits or maybe About the role? Probably better to include under Benefits as additional detail.
Pay and Schedule: not provided, so omit.
Skills: we could list skills from qualifications? But we already have Qualifications and Requirements sections. Might be redundant. However we need to decide which sections to include.
We have:
- About the role: could contain overview paragraphs (Deloitte Global is the engine..., The team Deloitte Technology works...). That's substantive.
- Responsibilities: the list.
- Requirements: maybe the "Qualifications Required:" list.
- Qualifications: maybe the "Education and experience:" plus "Preferred:"? But we already used Requirements for required qualifications; Qualifications could be for education/certifications. However the instruction says we can use Qualifications heading; we need to avoid filler. We have education and certifications content, so we can include Qualifications section.
- Skills: maybe we could list specific technical skills like Splunk, Azure, AWS, etc. But those are already in qualifications. Could combine.
Better to follow typical job posting: About the role (overview), Responsibilities (duties), Requirements (mandatory), Qualifications (education/certifications), Skills (preferred or technical), Benefits.
Let's assign:
About the role: paragraphs about Deloitte Global and team.
Responsibilities: the bullet list.
Requirements: the "Qualifications Required:" list (the 2+ years Splunk etc).
Qualifications: Education and experience (Bachelor's degree, certifications).
Skills: Preferred items (Cribl, large global org) maybe also mention communication etc but those already in requirements. We'll put preferred as Skills.
Benefits: the benefits paragraph.
We must not repeat job title as heading. We'll not include.
We need to output HTML fragment only.
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.
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.
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.
Requirements
- 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
Qualifications
- 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
Skills
- Experience with Cribl administration and data onboarding
- Experience in working in a large global organization
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 should not include empty sections. All have content. Check for any boilerplate: we removed Reference Code, Locations, Recruiting ends on. Could include location metadata in a short p maybe but instruction says fold minor metadata into a shortor drop it. We could include a short p with locations. But we already have About the role; we could add a p after About the role with location info. However we must not repeat job title. Location is minor metadata; we could add a short p. Let's add after About the role maybe a p: "Locations: Hermitage, Nashville, Tampa (USA)." But we need to ensure not to create filler. It's real info. Let's add a p after About the role paragraphs. Thus:
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