At a Glance
- Tasks: Manage and enhance SIEM solutions, onboard data, and automate responses.
- Company: FNZ makes wealth management accessible for over 20 million people worldwide.
- Benefits: Join a global team with opportunities for remote work and professional growth.
- Why this job: Be part of a mission-driven company that values security and innovation in finance.
- Qualifications: 4+ years of SIEM experience, strong skills in Splunk/Sentinel, and relevant certifications required.
- Other info: Collaborate with cross-functional teams across different time zones.
The predicted salary is between 48000 - 72000 £ per year.
Role Description
At FNZ, our purpose is to make wealth management more accessible, bringing easier, fairer and more inclusive solutions to people worldwide. Here in the Global Information Security team, we work to protect the platforms that support investment solutions for over 20 million people. We are looking for an experienced SIEM Engineer, reporting to the Cyber Security Engineering Manager (SIEM). You will have a strong background in designing and developing monitoring solutions and will be familiar with onboarding data from varied sources. You will have strong experience of different SIEM architectures and be adaptable in your approach. Your role in FNZ will be to manage and enhance the SIEM solutions for the FNZ Group, supporting the lifecycle of data onboarding, use cases and automating responses.
Specific Role Responsibilities
- Support the creation and delivery of the roadmap and architecture for the SIEM solutions in FNZ
- Deploy, manage and enhance the SIEM technology in FNZ
- Managing the SIEM infrastructure
- Log onboarding
- Rules and Use case development
- Schema management
- Threat Intelligence integration
- Maintain up-to-date knowledge of emerging security threats and trends and build this into the SIEM strategy
- Support the Incident Response team in FNZ to identify, manage and respond to incidents
- Collaborate effectively with cross-functional teams across different time zones.
Experience Required
Primary Requirements
- Significant (4+ years) experience of design/administering/managing SIEM (Splunk/Sentinel) in a large, distributed environment
- Strong experience with Microsoft Sentinel administration
- Experience with Splunk Enterprise Security administration
- Significant experience of the creation of rules and use cases to support business incident response
- Strong experience of data onboarding and schema management
- Strong understanding of multiple technologies:
- Windows
- Linux
- Network devices (WAF, Firewalls, Switches)
- Cloud
- Application Logging
- Advanced automation and scripting capabilities, with hands-on knowledge of development best practices.
- Knowledge of Security Frameworks (NIST, MITRE etc)
- Relevant security certifications (e.g., SSCP, Vendor Certifications)
- Experience of working with tools like Jira, Planner and Confluence
#J-18808-Ljbffr
SIEM Engineer employer: FNZ (Uk) Ltd
Contact Detail:
FNZ (Uk) Ltd Recruiting Team
StudySmarter Expert Advice 🤫
We think this is how you could land SIEM Engineer
✨Tip Number 1
Make sure to highlight your experience with SIEM technologies like Splunk and Microsoft Sentinel. Be prepared to discuss specific projects where you designed or managed SIEM solutions, as this will demonstrate your hands-on expertise.
✨Tip Number 2
Familiarize yourself with the latest security threats and trends. Being able to discuss how these can impact SIEM strategies will show that you are proactive and knowledgeable in your field.
✨Tip Number 3
Prepare examples of how you've collaborated with cross-functional teams, especially in different time zones. This is crucial for the role, and showcasing your teamwork skills will set you apart.
✨Tip Number 4
Brush up on your automation and scripting skills. Be ready to talk about how you've used these capabilities in past roles to enhance SIEM solutions, as this is a key requirement for the position.
We think you need these skills to ace SIEM Engineer
Some tips for your application 🫡
Understand the Role: Take the time to thoroughly read the job description for the SIEM Engineer position at FNZ. Make sure you understand the specific responsibilities and requirements, especially regarding SIEM technologies like Splunk and Microsoft Sentinel.
Highlight Relevant Experience: In your application, emphasize your significant experience (4+ years) in managing and administering SIEM solutions. Be specific about your familiarity with data onboarding, rule creation, and schema management, as these are crucial for the role.
Showcase Technical Skills: Clearly outline your technical skills related to Windows, Linux, network devices, and cloud application logging. Mention any relevant security frameworks you are familiar with, such as NIST or MITRE, to demonstrate your comprehensive understanding of the field.
Tailor Your Application: Customize your CV and cover letter to reflect the language and key phrases used in the job description. This shows that you have a genuine interest in the position and understand what FNZ is looking for in a candidate.
How to prepare for a job interview at FNZ (Uk) Ltd
✨Showcase Your SIEM Expertise
Be prepared to discuss your hands-on experience with SIEM tools like Splunk and Microsoft Sentinel. Highlight specific projects where you designed or managed SIEM solutions, focusing on the impact of your work.
✨Demonstrate Your Problem-Solving Skills
Prepare examples of how you've tackled complex security incidents in the past. Discuss your approach to developing rules and use cases that enhance incident response, showcasing your analytical thinking.
✨Stay Updated on Security Trends
Familiarize yourself with the latest security threats and trends. Be ready to discuss how you would integrate this knowledge into the SIEM strategy at FNZ, demonstrating your proactive approach to cybersecurity.
✨Emphasize Collaboration and Communication
Since the role involves working with cross-functional teams across different time zones, highlight your experience in collaborating effectively. Share examples of how you've communicated technical information to non-technical stakeholders.