Network & Security specialist (Cisco | CheckPoint | F5)

Our client is a global technology and professional services company with a Cyber Center in Prague. The team serves enterprise clients across multiple industries and operates as a mature, production-grade security operation — not a lab, not a pilot. The Prague team is around 270 professionals. The security operations unit has ~80 people, including roughly 27 engineers who own the technical layer — SIEM platforms, detection pipelines, incident response tooling. English is the language of client-facing work; Czech is day-to-day inside the team. Why This Role Exists Now: The security operations team is expanding. Two new engineers are joining — this is one of two roles being filled at the same time. The other role goes deeper on cloud SIEM (separate ad). The team has experienced engineers who know the detection architecture well, and now is a good moment to join — the knowledge transfer opportunity is real and accessible from day one. If you've been in an MSSP environment where detection ownership stays with the vendor or a central content team — this role is built differently. Most MSSP setups give you the SIEM. This one gives you the rules.What Matters Most: We're not looking for someone who ticked every checkbox on a certification list. Three things actually matter: — SIEM hands-on time — you've worked with Splunk (SPL queries, correlation searches) or Microsoft Sentinel (KQL, analytics rules) for at least 2 years in a production environment — Linux system knowledge — you understand how logs are generated, how syslog works, what endpoint telemetry looks like — Detection thinking — you can write a correlation rule from scratch, explain why it's tuned the way it is, and recognize when a low-severity alert is worth investigating English needs to be solid for reading technical documentation and writing client-facing reports. If your background is primarily QRadar or ArcSight — that's a valid starting point. We care more about your engineering instincts than the vendor logo. Nice to Have: — Experience with Chronicle/Google SecOps — YARA-L rules, UDM data model — Familiarity with QRadar or ArcSight from client or previous employer environments — Security certifications: GCIA, CEH, CompTIA Security+, Microsoft SC-200, or Splunk Core Certified — Scripting for automation — Python, PowerShell, or bash for log parsing or playbook triggers Don't let the nice-to-haves stop you. If you have the three core things, the rest can be learned.Role / Mission: Your job is to keep the SIEM infrastructure healthy and make sure the detections it runs actually catch things worth catching. Day-to-day: monitoring and triaging alerts, maintaining log source pipelines, tuning correlation rules, and working with analysts when something escalates. You'll also write and maintain playbooks so the team doesn't reinvent the wheel during incidents. Tech context: the team runs Splunk and Microsoft Sentinel as primary platforms. QRadar and ArcSight in the mix from legacy clients. Chronicle/Google SecOps is present in some environments — knowledge there is a plus. Success in 12 months: you own your detection playbooks, you've added at least one meaningful improvement to the ingestion or detection layer, and when someone has a question about platform behavior, they come to you first. Key Responsibilities: — Monitor, triage, and investigate alerts across SIEM platforms (primarily Splunk and Microsoft Sentinel) — Build, tune, and maintain detection rules and correlation logic — SPL, KQL, or both — Maintain SIEM infrastructure: log sources, ingestion pipelines, platform health, onboarding new data feeds — Write and update incident response playbooks; support L1/L2 analysts during active investigations — Participate in on-call rotation; contribute to post-incident documentation and lessons learned What This Role Is NOT: — Not a pure L1 analyst position — you're here to engineer and improve, not just watch dashboards — Not a client-facing sales or advisory role — this is delivery, inside the engine room — Not a solo build-from-scratch project — you're joining an existing team with live infrastructure Operating Model: Standard working hours, no shift work. On-call is a shared rotation across the engineering team. Hybrid setup in Prague or fully remote is also possible. Reports to: Head of Security Engineering. English for client documentation; Czech for internal team communication. Travel is minimal.Interested? Let's Talk If this sounds like your kind of challenge, apply now — let's build something great together. Throughout the process, you'll be guided by a senior recruiter with hands-on IT experience. Straightforward, technically grounded, without unnecessary recruitment overhead. Send your CV or LinkedIn profile to or reach out via linkedin.com/in/jirisoljak Interview process: — Intro call with SITEQ recruiter — 30 minutes, we'll explain the role and client context — First interview with the team lead — get to know each other, talk about the team and day-to-day — Technical interview with a senior engineer from the security operations team — hands-on discussion, no trick questions — Offer Please note: this position is open only to candidates eligible to work in the EU without visa sponsorship, able to reside and work in the Czech Republic.

International technology group with 30+ years in the market, 800+ professionals, and offices across Central and Eastern Europe. They deliver projects in IT infrastructure, data centres, cloud solutions, and cybersecurity. The company is growing — clients are expanding their demand, new projects are coming in, and there's space for new competencies. The Cyber Security / IAM division currently works heavily with the IdStory platform, but the environment includes other IAM/IDM solutions too. They need someone who can handle the full cycle from analysis to implementation. Why This Role Exists Now: Client demand for identity security is growing. The IAM division is expanding its project portfolio and needs someone who can own the full delivery cycle — from analysis through architecture to go-live. There's space for new competencies and platforms beyond IdStory. The right person can shape what the IAM practice looks like going forward.What Matters Most: — IAM/IDM experience — minimum 3–5 years in IT security / IAM. Real implementation experience, not just operations — IAM platforms — IdStory, SailPoint, One Identity, Entra ID, Okta, or similar. Knowing one superficially isn't enough — Client-facing communication — analysis, consultations, presenting solutions. This is non-negotiable — Integration and APIs — REST, SOAP, GraphQL. You know how to connect systems Fluent Czech or Slovak required. English at a level where you can handle a normal working discussion. Nice to Have: — SQL and databases — you work with data, not just look at GUIs — Scripting (Groovy, PowerShell, Python) — Basic Linux knowledge — Identity governance concepts and identity lifecycle management — Experience with HR systems and their integration with IAM These are nice to have — not hard filters.Role / Mission: You own the full cycle — from the first client workshop through architecture to go-live. You walk into a client's environment, map what's actually there, ask the right questions, pull the data together into a document, and design a new architecture. Then you implement it. You're an analyst and implementer in one — not someone who waits for a spec. After 12 months, this is what good looks like: completed projects, clients who trust you, and working identity integrations in real environments. Key Responsibilities: — You analyse customer requirements and design IAM/IDM architecture — You implement and integrate identity solutions into client environments — You handle incidents and operational support within SLA — not as the core of your work, but as part of it — You create technical documentation — actually useful materials, not formal paperwork — You provide technical consultations to clients — You contribute to presales — solution proposals, presentations, technical input for bids — You work with sales, presales, support, and delivery teams What This Role Is NOT: — Not AD administration — you won't be resetting passwords and creating accounts — Not a pure operations role — SLA tickets are part of the job, but not the core — Not an isolated position — client and team communication is key Operating Model: Prague-based, remote-friendly. More time in the office during onboarding. After that, remote is possible — but you're expected at the office or client sites as needed. Most of the business is in and around Prague, so a reasonable commute matters. No 24/7 on-call. Permanent contract preferred, freelance possible. Czech or Slovak proficiency required. Direct report: Head of Network & Security division.Interested? Apply or get in touch: | linkedin.com/in/jirisoljak No CV needed — a LinkedIn profile and a few sentences about yourself is enough. You'll speak directly with a senior IT recruiter with hands-on IT background — 450+ hires. A relevant conversation without the HR fluff. Process: — Short intro call (15–30 min) — Maximum 2 rounds — if there's a fit, a decision can come after the first one — In-person meeting before the final decision — You'll know where you stand at every step EU work authorization required. No visa sponsorship.