Artemis Technology Alliances Manager at Artemis to own end-to-end technology alliances including hyperscalers and security platforms. Manage relationships and partnerships critical to product integrations and go-to-market.
Responsibilities
Most companies treat technology alliances as a nice-to-have. At Artemis, alliances are closer to how the product works. Our platform runs on AWS and reasons over telemetry that lives in other vendors' systems: EDR, SIEM, identity, cloud, and the pipelines that move security data between them. Every one of those vendors is simultaneously an integration, a channel, and a reason a customer picks us. The companies we plug into are the companies we go to market with.
We're hiring a Technology Alliances Manager to own that motion end to end, with three tracks front and center:
Hyperscalers. AWS first: we build on it and our customers run on it. Own the relationship end to end: Marketplace transactability and private offers, co-sell through ISV Accelerate, competency milestones, and the AWS field teams who can put us in front of their accounts.
Security platforms. The largest vendors in security (CrowdStrike, Palo Alto Networks, and their peers) already collect the telemetry we investigate. Build the alliances that position Artemis as a multiplier on their platforms: partnership agreements, store listings, certified integrations, and field-level co-sell.
ISVs. The vendors that shape and route security data (Cribl and its peers) as well as domain specific security companies helps us secure customers together. Build the reference architectures and joint plays that helps customers stay safe.
Many of these relationships are already in motion at the executive level. Your job is to take them from conversations to signed, integrated, revenue-producing partnerships, and to decide what we pursue next.
We're not collecting logos. A partnership counts when it produces something measurable: sourced pipeline, marketplace revenue, an integration customers actually turn on, a partner seller who pulls us into a deal. You'll be measured on those outcomes, and you'll have the product, engineering, and executive support to hit them.
Own the technology partner map: which partners, in what order, for what outcome; double down on what performs and kill what doesn't
Run the AWS motion end to end: Marketplace listing and private offers, co-sell pipeline, program and competency milestones, and joint content with AWS field and specialist teams
Build and negotiate alliances with the major security platforms: agreements, integration roadmaps, marketplace listings, and better-together assets (solution briefs, reference architectures, joint demos) that sales actually uses
Drive integrations from scoping to launch with product and engineering on both sides, and make sure every launch ships with a go-to-market moment, not just a docs page
Turn partnerships into revenue: joint account mapping, co-sell registrations, warm intros, MDF, and partner events (RSA, re:Invent, Fal.Con, Black Hat), with tracking of alliance-sourced and alliance-influenced pipeline
Qualification
5+ years in technology alliancesHands-on hyperscaler experienceFluency in the security ecosystemRangeJudgment for coopetitionComfort with ambiguity
Required
5+ years in technology alliances, partnerships, or business development at a cybersecurity or enterprise infrastructure company
At least one partnership you built from zero and can walk us through in numbers: what it sourced, influenced, or unlocked
Hands-on hyperscaler experience: you've listed and transacted on a cloud marketplace, worked programs like AWS ISV Accelerate, and know how co-sell and partner funding actually operate
Fluency in the security ecosystem: the major platforms across EDR/XDR, SIEM, identity, and data pipeline, how they interoperate, and what their partner organizations optimize for
Range: technical enough to whiteboard an integration with partner engineers, commercial enough to negotiate the agreement behind it, credible with partner executives
Judgment for coopetition: some of our most important partners also ship competing products, and you know how to build the better-together lane anyway
Comfort with ambiguity, building from scratch, and moving fast without dropping details
Preferred
Time inside the partner organization of a hyperscaler or major security platform: you know how AWS, CrowdStrike, or Palo Alto Networks evaluate ISV partners from the inside
Existing relationships across the security partner ecosystem
Experience as a company's first alliances hire
Familiarity with partner ecosystem tooling (Crossbeam, Tackle, WorkSpan, and similar)
