Director of Marketing Operations

About this role

OPSWAT , a global leader in IT, OT , and ICS critical infrastructure cybersecurity, delivers an end-to-end platform that gives public and private sector organizations and enterprises the critical advantage needed to protect their complex networks, secure their devices, and ensure compliance. Over the last 20 years our commitment to innovative technology has earned the trust of more than 1,700 organizations, governments, and institutions globally, solidifying our role in protecting the world’s critical infrastructure and securing our way of life.

A Personal Note from Kat, CMO of OPSWAT I'm Kat, CMO at OPSWAT. We protect the world's most critical infrastructure, and our marketing team is in the middle of a real transformation to match that mission. Here is the honest picture. Our growth is outpacing the way we work. The demand is there, the market is moving toward us, and the thing that will limit us is not budget or headcount. It is how well our systems, our data, and our people connect to each other.

That is the problem I want to solve, and it is why this role exists. I am not looking for someone to maintain our martech stack. I am looking for the person who makes this team work differently. Someone who sees where marketing, SDR, and Sales are handing work back and forth inefficiently and redesigns it. Someone who looks at the twenty manual tasks eating this team's week and gets rid of them. AI is central to how we are approaching this, and I want to be specific about what that means here, because the phrase gets thrown around a lot.

You will not be doing it alone. We are hiring an AI engineer on the team, and a big part of this role is partnering with them and me to build the integration tools and automations we need. You bring the marketing and revenue context, the process design, and the sharp instinct for what is actually worth building. They bring the engineering . Together you will build things that are innovative and efficient. You do not need to be an engineer.

You do need to be technical enough to be a real partner in that conversation, curious enough to keep up with where this is going, and grounded enough to know the difference between a tool that helps and a tool that demos well. The other half of this job is people. The best systems in the world do not matter if the team does not adopt them. I want someone who teaches, documents what works, and makes AI fluency something this whole organization has rather than something one person is good at.