VP of Platform

The Position

Every MetaDefender product runs on a common foundation which is this role’s domain. The VP of Platform will transform it into the definitive substrate that every product team builds on top of, every customer deploys with confidence, and every enterprise buyer trusts to meet their most demanding requirements.

This is not a maintenance role and it directly shapes how every product in the MetaDefender portfolio ships, deploys, and operates. You will own the most horizontally impactful technology in the company, few platform roles touch this much surface area. Product leaders at OPSWAT stay close to the technology. You’ll work alongside peers who read code, challenge architectures, and ship.

What You Will be Doing

1. MetaDefender Core — Product Strategy & Technical Direction

MetaDefender Core is at the center of OPSWAT’s file security ecosystem — performing Deep Content Disarm & Reconstruction (CDR), multi-scanning, file-based vulnerability assessment, dynamic analysis with next-gen sandbox and many other layers of technologies across billions of files for the world’s most security-conscious organizations.

• Own the technical vision for Core’s evolution: modular design for supporting multi-engine orchestration, processing throughput, format coverage, and API extensibility.
• Drive the product strategy to serve growing file analysis demands across new modalities — archives, encrypted containers, firmware, ML model files.
• Understand Core’s role as the nucleus of the MetaDefender ecosystem and ensure its architecture enables, rather than constrains, adjacent products.
• Shape the growth trajectory with a path toward full P&L ownership as the role and platform mature.

1. Enterprise Shared Services — The Foundational Platform Layer

This is the highest-leverage work at OPSWAT. Enterprise Shared Services is the unified platform that every mature MetaDefender product adopts to deliver a consistent, enterprise-grade experience. Your mandate: make this platform so compelling that product teams choose to adopt it.

• Installer & Deployment: Unified installation framework supporting online, offline/airgapped, headless, and automated deployment scenarios.
• Configuration & Policy Management: Centralized configuration, policy engines, and tenant-aware settings across the product portfolio.
• Identity & Access: SSO, RBAC, SAML/OIDC integration, and enterprise identity federation.
• Notifications & Reporting: Shared notification framework, audit logging, scheduled and ad-hoc reporting.
• Observability: Telemetry, health monitoring, and operational dashboards.
• Scalability & Architecture: Horizontal scaling patterns, zero-downtime upgrades, HA/DR design, and performance benchmarking.
• Internal Adoption: Build a developer experience so compelling that peer PMs and their engineering teams actively want to integrate. Evangelize, document, support, and iterate.
• UI framework: Build and maintain brand-compatible, language-agnostic UI components so that other teams will not need to reimplement their own

1. Enterprise Deployment & Infrastructure Expertise

OPSWAT’s customers operate in some of the most constrained and regulated environments on Earth. This role requires deep understanding of how enterprise software is deployed, operated, and maintained:

• On-Premises: Traditional server deployments, both internet-connected and fully air-gapped, across Windows and Linux.
• Cloud & IaaS: AWS, Azure, GCP deployment models including marketplace offerings, reference architectures, and cloud-native integrations.
• Kubernetes & Containers: Helm charts, operators, container orchestration, and cloud-agnostic deployment patterns.
• Hybrid & Edge: Architectures spanning multiple environments with centralized management and distributed processing.

What You’ll Do in the First 12 Months

• Audit & Roadmap (Months 1–3): Deep-dive into Enterprise Shared Services adoption, Core architecture, and deployment tooling. Deliver a prioritized platform roadmap with clear adoption milestones.
• Internal Evangelism (Months 3–6): Establish the platform team as an internal product organization. Build relationships with every product PM and engineering lead. Ship quick wins that demonstrate value and earn trust.
• Accelerate Adoption (Months 6–12): Drive measurable Shared Services adoption across the MetaDefender portfolio. Modernize Core’s architecture for next-generation scale. Establish deployment patterns that reduce customer time-to-value.
• Directly collaborate with 2 dedicated engineering teams (over 40 headcounts) while influencing platform adoption across 12+ peer engineering teams globally.

What We Need from You 

Must Have

• 15+ years in platform engineering, developer platforms, or infrastructure product management, with at least 5 years in a senior leadership role owning platform strategy.
• Deep experience building products deployed in customer environments (not purely SaaS) — you understand the pain of on-prem upgrades, air-gapped installations, and enterprise change management.
• Architectural fluency across Kubernetes, containerization, IaaS (AWS/Azure/GCP), and traditional on-prem server deployments. You don’t need to debug Helm charts, but you must evaluate architectural trade-offs and challenge engineering decisions.
• Proven track record of building internal platforms that other teams willingly adopt. You know the difference between mandating adoption and earning it.
• Enterprise software acumen: SSO/SAML/OIDC, RBAC, multi-tenancy, audit logging, zero-downtime deployments, observability — you’ve shipped these capabilities and understand what enterprise buyers demand.
• Strong communicator and internal seller: Ability to align peer PMs, convince skeptical engineering leads, and present platform strategy to executive leadership.
• Metrics-Driven Product Leadership: Define clear KPIs for platform adoption, performance, scalability, and customer impact. Use dashboards and qualitative feedback to prioritize roadmap decisions and hold teams accountable for measurable outcomes.
• Curiosity, Ownership, and Bias for Action: Demonstrate intellectual curiosity and proactive ownership, embracing emerging technologies (including AI-driven development) to move quickly while maintaining architectural rigor. Balance speed with resilience to build long-lived platform capabilities trusted by enterprise customers.

Strong Differentiators

• Background in data pipeline products: ETL, iPaaS, RPA, or file processing systems that handle large-volume, mission-critical workloads.
• Cybersecurity or critical infrastructure experience: Understanding of compliance frameworks (FedRAMP, NIST, Common Criteria), regulated deployments, and security-first architecture.
• Experience scaling a platform from partial to full adoption across a multi-product portfolio. You’ve navigated the technical debt, org politics, and prioritization battles this requires.
• Open-source or inner-source model experience: Building contribution frameworks that enable distributed teams to extend platform capabilities.

This Role is NOT For You If…

• You’ve only worked in pure SaaS with no exposure to on-prem or air-gapped deployment complexity.
• You think “platform” means building internal tools nobody asked for. This requires obsessive customer empathy — your customers are internal product teams AND end-user enterprises.
• You want a pure people-management role. This is hands-on-strategy: you’ll be in the architecture, the specs, and the trade-off discussions daily.