The Platform: My OPSWAT

Every OPSWAT customer, partner, and prospect meets us here first.

My OPSWAT is the unified front door to everything OPSWAT delivers, the place where a nuclear plant operator activates an offline license, where a channel partner manages a portfolio of customer deployments, where a security engineer opens a critical support case at 2 a.m., where a new administrator earns their first OPSWAT Academy certification, and where organizations control exactly who inside their walls can do each of those things.

My OPSWAT is where OPSWAT's commercial model, customer experience, partner ecosystem, and product portfolio converge into one system. When it is excellent, every other product in the portfolio feels easier to buy, deploy, and trust. 

About This Role

We are looking for a Director of Software Engineering to own the engineering of the My OPSWAT platform end to end: architecture, delivery, quality, security, and the team that builds it.

This is a hands-on, technically centric leadership role. Not a pure people-management position, and not a role that leads through status decks. You will operate with the rigor of a principal engineer and the clarity of an executive: in the codebase enough to earn your team's respect, in the business enough to make the right trade-offs, and in front of customers and partners enough to know what actually matters.

And you are an AI-native engineering leader. Not someone who has evaluated AI tools, someone who has personally orchestrated fleets of AI agents to specify, build, test, review, and ship production software, and who has shipped real products through a full agentic SDLC. You have opinions about context engineering, evals, and review gates because you have been burned and learned. Product Management defines what to ship; you define how it gets built, and at OPSWAT, "how" increasingly means humans directing AI agents, with humans accountable for every line that ships.

The patterns you establish on My OPSWAT won't stay on My OPSWAT. This platform connects and enables the company’s all products and business functions, which makes it the natural proving ground for AI-native engineering practices at OPSWAT.

What You Will Own

• Lead the AI agentic transformation.
• Stay hands-on, be creative and innovative.
• Own the platform.
• Own delivery.
• Connect business, engineering, product, and people.
• Build a team people want to be on.

What We Need From You

• Full agentic SDLC experience.
• A track record of bringing a team along.
• 10+ years engineering and 5+ years leading teams including managing managers or leads.
• Deep technical fundamentals distributed systems, API design, data modeling. 
• Cloud-native, multi-tenant SaaS experience in build and operation.
• Business and customer instinct.
• Excellent English communication.
   

It Would Be Nice If You Had

• Domain familiarity.
• AI product features, not just AI development experience.
• Cybersecurity background.
• Experience in a global product company with engineering and go-to-market spread across regions.

Why You'll Love Working Here

• My OPSWAT touches every customer, every partner, every business unit, and every product line. The architecture and culture decisions you make now will shape it for years.
• The AI-native patterns you establish here are intended to propagate across OPSWAT's engineering portfolio.
• Leadership is committed to AI agentic engineering and wants a leader who will push further than the mandate, not ask permission to start.
• A stable, growing international company with an exceptional customer base across 50+ countries.
• Attractive compensation with regular performance assessments, and flexibility for the right candidate.

Your First 90 Days

• Day 30 - Credibility and context. Know the architecture, identify the top constraints holding it back, and the health of your team. Working relationships established with Product, Support, Enterprise Applications and Engineering.
• Day 60 - A point of view. Present an architecture and AI-native transformation plan with sequencing and trade-offs. Baseline the metrics below so progress is measurable, not asserted.
• Day 90 - Execution underway. Agentic workflows live on at least one meaningful workstream, with context files, evals, and review gates in place. Delivery commitments made and being met.

Success Metrics (6 - 12 months)

Platform and customers

• Full agentic My OPSWAT platform.
• Improved usability and reliability on the flows customers and partners live in daily.
• Reduced support volume on the friction points you inherited.
• Positive, sustained feedback from executives, product, engineering, support, and other stakeholders.

AI agentic engineering

• A majority of delivery flows through AI agentic workflows, with documented context, evals, and review gates.
• Measurable lead-time reduction from spec to production.

Delivery and quality

• Predictable releases: committed scope and dates met, trade-offs raised early.
• Escaped-defect and production-incident rates down as AI-generated code share rises.
• Zero critical security findings reaching production.

Team and influence

• Strong retention and a visibly rising hiring bar.
• Every engineer on the team working as an AI orchestrator, not an observer.