Dear CrowdStrike Talent Acquisition team,
I would like to be considered for the Security Engineer role you have posted on your careers page. For several years my focus has sat in security engineering, and I would be glad to bring that to your team.
Ahead of writing I looked closely at CrowdStrike, and what stood out was your move to a zero-trust model and the security write-ups your team keeps posting on threat detection. It looks like a strong time to join, and I would gladly put my security engineering experience to work there.
Reading the posting, the three needs that stand out most are threat detection and monitoring, incident response and forensics and security architecture and hardening. Those decide whether a security hire works out, and I have real results behind each.
On threat detection and monitoring, I work with SIEM, EDR and threat hunting. As a Security Engineer at Splunk, I handled building the detection rules that caught a live intrusion in minutes instead of days. Beyond that, I cut alert fatigue by tuning the SIEM and clearing thousands of false positives.
For incident response and forensics, I count on incident response, playbooks and forensics. Over my time as a Security Engineer at Splunk, I took on leading incident response on a real breach and bringing containment time under an hour.
On security architecture and hardening, I draw on zero trust, IAM and hardening. Working as a Security Engineer at Splunk, I owned rolling out zero trust so a stolen laptop no longer means a stolen network. On top of that, I ran the red-team exercises that hardened the crown-jewel systems.
I would be glad to walk through this in an interview and show why I fit. I am ready to keep your systems locked down and your team ready for what comes at them, and to grow with the team.
I would be happy to set up a time to talk.
Yours sincerely,
Theo Script
theo.script@gmail.com