We're not looking for someone who fits neatly into a box. We're looking for someone who finds neat boxes a little underwhelming.
You're a builder, not just an advisor – analysis without artifacts isn't enough.
You close loops. You ship things – You leave systems better than you found them.
You're customer-obsessed – you understand that what happens in enterprise POVs isn't a distraction from the real work. It is the real work. You run toward hard customer problems rather than away from them.
You're opinionated and direct – you push back when something is wrong, change your mind when shown better evidence, and write and speak clearly without filler.
You move without waiting to be told – when something is broken or missing, you identify it, own it, and fix it. You don't need a clean scope to start. You operate well under ambiguity and produce clarity for everyone around you.
You have a hacker mentality – you find the path through, you're comfortable in ambiguous and underdocumented systems, and you debug by instinct as much as by method.
You're technically deep and contextually wide – you can go deep on a data pipeline, a detection rule, a query engine, or a cloud architecture, then explain any of it to an executive the same afternoon.
You're a builder, not just an advisor – analysis without artifacts isn't enough.
You close loops. You ship things – You leave systems better than you found them.
You're customer-obsessed – you understand that what happens in enterprise POVs isn't a distraction from the real work. It is the real work. You run toward hard customer problems rather than away from them.
You're opinionated and direct – you push back when something is wrong, change your mind when shown better evidence, and write and speak clearly without filler.
You move without waiting to be told – when something is broken or missing, you identify it, own it, and fix it. You don't need a clean scope to start. You operate well under ambiguity and produce clarity for everyone around you.
You have a hacker mentality – you find the path through, you're comfortable in ambiguous and underdocumented systems, and you debug by instinct as much as by method.
You're technically deep and contextually wide – you can go deep on a data pipeline, a detection rule, a query engine, or a cloud architecture, then explain any of it to an executive the same afternoon.
Requirements:
8+ years of hands-on technical experience in security research, systems engineering, or a combination. Academic credentials matter less than what you've actually built and broken.
Strong security domain knowledge – threat detection, SecOps workflows, SIEM architecture, detection engineering, or offensive security research. You know this space from the inside.
Fluency in cloud environments (AWS, GCP, or Azure). You understand how data flows through cloud-native architectures and have operated in them.
Comfortable writing and shipping code – scripts, pipelines, tooling. You don't need to be a software engineer by title, but you build things that work. Fluent with LLMs and AI-assisted development tools (Claude Code or equivalent). You use them as a force multiplier, not a novelty.
Experience with enterprise technical engagements – POVs, architecture reviews, or field engineering. You're not learning how to handle a skeptical CISO on the job. Strong written and verbal English. You produce external-quality technical content and you're credible in front of a US enterprise audience.
8+ years of hands-on technical experience in security research, systems engineering, or a combination. Academic credentials matter less than what you've actually built and broken.
Strong security domain knowledge – threat detection, SecOps workflows, SIEM architecture, detection engineering, or offensive security research. You know this space from the inside.
Fluency in cloud environments (AWS, GCP, or Azure). You understand how data flows through cloud-native architectures and have operated in them.
Comfortable writing and shipping code – scripts, pipelines, tooling. You don't need to be a software engineer by title, but you build things that work. Fluent with LLMs and AI-assisted development tools (Claude Code or equivalent). You use them as a force multiplier, not a novelty.
Experience with enterprise technical engagements – POVs, architecture reviews, or field engineering. You're not learning how to handle a skeptical CISO on the job. Strong written and verbal English. You produce external-quality technical content and you're credible in front of a US enterprise audience.
This position is open to all candidates.
