Cybersecurity Engineer
- Opened · 30d
- +0
- Closed · 30d
- −0
- Opened · 7d
- +50812% of open
- All security
- 8,298open
EVOCS OVERVIEW
EVOCS’s journey began with a mission to empower businesses with advisory expertise, empowered with ideal technologies to provide them with comprehensive solutions to grow and prosper.
Founded by a team of passionate experts, EVOCS has grown into a trusted partner to a growing number of leaders across their respective industries. Our roots in employee-managed operations reflect our commitment to quality, consistency, and client success.
If you enjoy working in a hyper-fast-growing company, are eager to be part of an agile team, and want to be part of our success story, then let’s talk!
Cybersecurity Engineer
Contract | Remote, Argentina | Reports to the Director of Cybersecurity
🎯 Role Overview
You'll join a team that's still building -- hands-on work across detection, telemetry, and vulnerability analysis on live client environments, with findings that hold up under review.
You will be responsible for the work behind the work: tuning detections, onboarding log sources, analyzing telemetry and configurations at scale, and turning scanner output and evidence into findings a client's security leadership can act on.
🧩 What You Will Do
- Log source onboarding. Connect, parse, and validate telemetry sources into a SIEM. Confirm what is actually arriving, in what fidelity, and what is silently missing.
- Telemetry and configuration analysis. Extract and analyze firewall configurations, log data, and device state at fleet scale to support security assessments, and pull the evidence that sits behind a finding.
- Detection engineering. Write and tune detection logic, cut false positives on noisy rules, and build content for coverage gaps found during engagements. Platforms vary by client, so what matters is that you have done this somewhere, not that you have done it in one product.
- Vulnerability analysis. Turn scanner output into a prioritized picture using exploitability and asset criticality rather than raw CVSS, and track remediation to closure.
- Evidence and documentation. Assemble the evidence behind findings so each one is traceable and defensible under review.
- First drafts. Draft findings, report sections, and weekly status reports to a standard that needs review rather than rewriting.
- Automation. Build playbooks, scripts, and tooling that take repetitive work out of engagements.
- Research. Advisory and CVE analysis, platform and tooling comparisons, and technical research that feeds client recommendations.
🧠 What You Will Bring
- 3 to 5 years hands-on in cybersecurity: SOC, detection engineering, security engineering, or an MSSP delivery team. Hands on keyboard, not coordination.
- Real SIEM and SOAR experience on any platform, commercial or open source. Splunk, Sentinel, Elastic, Wazuh, Security Onion, Graylog, TheHive, Shuffle: we do not care which. We care that you have built and tuned detections in it, not only watched its dashboards.
- Detection logic you can write from scratch. KQL, SPL, EQL, Lucene, Sigma, or equivalent. You should be able to walk through a rule you wrote, why you wrote it that way, and what it missed.
- Blue team background. Alert triage and investigation experience, and MITRE ATT&CK as something you have applied rather than read about.
- Network literacy. You can read a firewall configuration and rule base and understand zones, segmentation, and what a rule actually permits. You do not need to be a firewall engineer; you need to not be lost in the data.
- Enterprise or data center IT experience: a real production environment with change control and uptime pressure, not only a lab.
- Scripting for analysis and automation (Python, Bash, PowerShell, or equivalent).
- Writing that survives light review. Much of your output becomes material a client's security leadership reads.
- Willingness to say what the data does not support. Overstating a conclusion is the one habit that does not work here.
🛠️ Show Us What You Build
The strongest people in this field tinker. If security is something you work on outside work hours, that counts here as much as anything on your resume, and at this experience level it often counts more.