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.