Technical Partner Manager

About This Role

Our Alliance partners (AWS, Azure, GCP, Nvidia) are our most important go-to-market partners. You will own the relationships across the Rest of World, covering EMEA, APJ, and Israel, as well as the technical side of the partnership globally. This role will lead building product integrations and initiatives with our cloud partners alongside our internal engineering teams. 

You will report to the Director of Alliances and work daily with our sales team, our Partner Development Managers, Partner SAs, and ScaleOps R&D.

What You Will Be Doing

Own the co-build agenda with AWS & GCP

• Drive our active co-build initiatives with AWS/GCP product and engineering teams from scoping through launch. 
• Own the technical relationship with AWS/GCP product managers and engineers on the EKS/GKE, Karpenter, and container services teams. Be the person they call, and the person who can answer without scheduling a follow-up.
• Track the EKS/GKE and AI/ML roadmap closely enough to tell us what it means. Dynamic Resource Allocation, MIG and time-slicing landing in Karpenter and Auto Mode/Auto Pilot, managed control plane work, and pod isolation all move the ground under our product. You will be the first person at ScaleOps to see it coming.
• Continuously validate that ScaleOps runs on where AWS/GCP are going, not just where it is. As AWS/GCP abstracts the node further, our agent, our scheduler, and especially our GPU device plugin need to keep working. Confirming that, early, is a standing part of the job.
• Bring AWS/GCP requirements and constraints back into R&D as real engineering input, and represent our architecture back to AWS/GCP accurately enough that they design around it.
• Look for opportunities to be a design partner and later a launch partner. 

Technical depth on ScaleOps and EKS/GKE

• Be the person who can explain how ScaleOps works on EKS/GKE to any technical audience, without an SE in the room: real-time pod right-sizing, HPA and replica management, intelligent pod placement, Karpenter and node optimization, Spot, and GPU fractionalization and right-sizing for inference workloads.
• Hold your own with AWS/GKE Solutions Architects and customer platform engineers on scheduling, autoscaling, resource management, and where our approach differs from static MIG and time-slicing.
• Build the reference architectures, technical content, demos, and hands-on material that make ScaleOps easy for an AWS/GKE TAM to recommend and easy for a customer to try.
• Run technical enablement for AWS/GCP Solutions Architects and Technical Account Managers. SA-to-SA credibility is what gets ScaleOps into technical conversations, and building it is part of this role.

Marketplace and program engineering

• Own the technical side of AWS/GCP Marketplace: listing requirements, container and Helm chart delivery, metering and entitlement integration, free trial and free tier mechanics, and private offer support.
• Make sure our listings and technical content are complete and specific enough that AWS/GCP's partner discovery systems can match us to the right customer opportunities.
• Support the technical requirements behind AWS/GCP partner programs, competencies, and validation processes, including the evidence and architecture artifacts they ask for.
• Represent our self-hosted and air-gapped deployment models clearly. We run entirely inside the customer's environment, which is an advantage in security review and a thing AWS/GCP teams consistently need explained.

Working across ScaleOps

• Work daily with R&D. Sit in design discussions, understand the constraints, and turn AWS-driven requirements into scoped work our engineers can act on.
• Support ScaleOps sales engineers and AWS/GCP account teams on the hardest technical conversations, especially GPU capacity and inference workloads.
• Represent ScaleOps at re:Invent, AWS Summits, Google Next, KubeCon, and technical briefings.
• Travel as needed to meet AWS/GCP product, engineering, and field teams.

What You Bring

• 5+ years in a customer-facing or partner-facing technical role: Solutions Architect, Solutions Engineer, Partner Solutions Architect, Technical Account Manager, or platform engineering with significant external exposure. Time inside AWS/GCP in an SA, PSA, or TAM role is ideal.
• Deep, current Kubernetes expertise. Not conceptual. You have run or architected production Kubernetes, and you can go deep on scheduling, autoscaling, requests and limits, resource contention, and what Karpenter does and does not solve. If your hands-on work was a decade ago, this is not the role.
• Strong working knowledge of EKS/GKE specifically, and of the AWS/GKE compute stack around it: EC2, instance families, Spot, and GPU instances.
• Real experience with the cloud-native ecosystem: containers, Helm, operators, GitOps, observability, and the operational realities of running Kubernetes at scale.
• Demonstrated ability to work directly with software engineers as a peer. You can hold a design conversation, understand a trade-off, and carry it accurately to a third party.
• Ability to translate in both directions: engineering constraints into partner-facing language, and partner requirements into scoped engineering work.
• Excellent written and spoken English, including with executive audiences. 
• Self-starter with strong ownership and follow-through. This role succeeds or fails on things actually shipping.

Nice to Have

• Hands-on experience with GPU workloads on Kubernetes: inference serving, vLLM, MIG, time-slicing, device plugins, or Dynamic Resource Allocation.
• Experience taking a product through AWS technical validation, a Foundational Technical Review, or a service integration with an AWS service team.
• Familiarity with AWS/GCP Marketplace mechanics: container and SaaS listings, the metering and entitlement APIs, private offers, and free trials.
• Experience as a launch partner on a cloud provider product release.
• Contributions to Kubernetes or CNCF projects, or a public technical presence such as talks, blog posts, or open source work.
• Familiarity with AWS competency requirements.

Location

This role is based in our Tel Aviv office five days a week. Being on-site with R&D is central to the job, since the technical integration work with the hyperscalers depends on daily proximity to our engineering team.