Snowflake Partner Manager, West

The Regional Cloud Data Platform Partner Manager is where an ecosystem partnership with a cloud / data platform turns into revenue and consumption in one patch of the map. This is an individual contributor who owns the relationship with a single cloud / data-platform ecosystem partner across one region, and does the specific work that platform co-sell requires: aligning the platform partner's field reps with the company's sellers on real accounts, running the marketplace and private-offer motion on live deals, growing the partner-sourced consumption and committed-spend the joint solution drives on the platform, and enabling the partner's reps in-territory so the company is the ISV they reach for. The book here is one ecosystem in one geography - the deliverable is joint pipeline in the patch, marketplace transactions and private offers closed, honest partner-sourced consumption in the platform's systems and the CRM, and a territory business review with the partner's regional team that tells the truth about what is moving. It reports up to the cloud alliance / partnerships owner who runs the program, and it works shoulder to shoulder with the platform partner's regional field and the company's regional sales team every week. It is not a Senior Cloud Alliance Manager, who carries the senior, broader-scope cloud-alliance seat - multiple platforms or the national / global motion - and sets the program this seat executes in one region; not an Alliance Manager, who owns the HQ strategic-alliance program and the global joint plan for a named partner (this seat executes co-sell in a region, it does not design the program); not a Field Alliance Manager, whose remit is general field co-sell across whatever partners are in the patch (this seat is specific to a cloud / data-platform ecosystem and native to its marketplace, consumption, and committed-spend mechanics); not a Technology Alliance and Enablement Lead, who owns the technical relationship and the enablement program for a platform partner (this seat owns the regional commercial co-sell, not the technical alliance); not a Channel Partner Manager, who runs resellers, deal registration, tiers and margins for indirect volume (this seat runs marketplace co-sell / sell-with, not the channel program); and not a Partner Engineer, who builds the integration behind a joint deal (this seat owns the commercial motion, not the build). Performance is visible in regional joint pipeline, marketplace and consumption growth, and platform-rep engagement in the patch, so sharper platform judgment shows up as consumption and revenue on the ground. What separates great from average is treating consumption as the currency of the partnership and earning the platform's field one rep at a time, rather than collecting badges and reporting activity. A mediocre partner manager forwards the global co-sell deck, waits for the platform's field to send leads, claims consumption the joint solution never drove, and reports "engagement" no seller can point to. A great one knows the platform's marketplace mechanics and its field comp model cold, so they line the company's co-sell up with the deal that grows the customer's committed-spend drawdown - which is exactly what the partner's rep is paid on - runs a clean private offer when it lands, holds a hard line between consumption the company genuinely sourced and consumption it merely touched, and spends finite field time where a live deal and real usage can actually move. The great one also knows the line: when the friction is the program itself (the wrong tier, a marketplace-listing gap, missing regional enablement), that is an escalation up with field evidence, not a redesign to freelance from the territory.