Sr. Global Alliance Director, OEM, Storage and ISV

As Sr. Global Alliance Director at vCluster Labs , you aren’t just shipping integrations; you are deciding which stack the world’s AI factories get built out of. Every AI factory ships as a stack: servers from an OEM, a validated design, a scheduler, an observability layer, a data platform, a management plane. The tenant isolation layer is the part nobody has solved. Your job is to make sure that layer is already in the OEM’s reference architecture, already in the price book, and already integrated with the ISVs sitting next to us before the customer ever runs a bake-off. Being in the design is worth more than winning the deal, because you win every deal that design produces.

This is a founding, zero-to-one role on a first-year partner program. There is no partner channel to inherit and no team underneath you. You own the number, the agreements behind it, and the product that ships inside someone else’s box.

As Sr. Global Alliance Director your role will include:

-
Owning the OEM alliance strategy: You will own the server and systems vendors building validated AI infrastructure designs end to end: strategy, executive alignment, program agreements, and business reviews. You will design and stand up the OEM commercial model (embedded SKUs, unit economics, tiered pricing for bundled and embedded distribution, royalty and per-node constructs, and a standard OEM order template that lets legal review once and the field move fast), then negotiate and close the orders. You will monitor each OEM’s AI factory roadmap to spot the design cycle before it closes, not after.

-
Building the ISV portfolio: You will scope, prioritize, and drive integrations with the storage, network, scheduler, observability, security, data, MLOps, and inference vendors whose customers overlap with ours, running it as a portfolio with explicit thresholds, not a queue of requests. You will land vCluster inside ISV and SaaS platforms as the tenant isolation layer, whether the ISV embeds it, resells it, or co-sells it. You will kill integrations that will not produce, and say so early. An ISV embed that does not change the partner’s own roadmap is a logo, not a route.

-
Building the sell-with motion: A shipped integration with no joint motion behind it is a cost, not an asset. You will design repeatable co-sell plays on top of every integration that earns one (account mapping, joint solution briefs, field-to-field engagement, deal registration the partner’s sellers actually use), then connect the resulting opportunities to vCluster’s regional sellers, channel partners, and the NVIDIA alliance to close. You take bundles to market through the partner’s own sales motion, not around it.

-
Driving technical alignment on both sides: You will represent partner technology requirements inside vCluster Product and Engineering with evidence attached (which accounts, what revenue, what happens if we do nothing), through one front door: licensing, telemetry, air-gapped operation, support boundaries, and lifecycle. You will write the integration specifications and acceptance criteria yourself. Integration work fails on unclear criteria far more often than on technical difficulty, and that clarity is yours to own.

-
Building the technology alliance program: You will design and launch the program itself: tiers, technical certification requirements, joint solution briefs, marketplace and private offer paths, and a self-serve path so a small ISV can integrate without you in the loop. The program has to scale past the partners you personally manage.

-
Owning the partnership number: You will report partner-influenced pipeline, integration and certification milestones, joint bookings contribution, and field activation to vCluster leadership, with MEDDPICC on every joint opportunity and weekly pipeline inspection. This is a first-year partner program with team MBOs and OKRs; you show up to the weekly inspection with your own numbers, your own forecast, and your o