寻找你的下一个职业机会

按职位、技能和地点搜索招聘信息。准备申请前,先仔细了解职位要求。

找到一个吸引人的职位名称只是求职的起点。请将工作职责、招聘要求和工作条件与你的实际经历进行比较。本指南帮助你筛选机会、准备有针对性的申请材料,并确认每份申请应该在哪里提交。

此界面为简体中文。雇主发布的职位名称和描述保留原文,可能为英文。

清除筛选

搜索结果: 13,642

← 返回搜索结果

Director of Partnerships

Buzz Solutions

远程工作

地点
Remote (Canada, United States)
工作安排
Full Time
发布日期
2026年10月13日

申请前,请在雇主网站确认职位仍在招聘,并检查完整要求和条件。

职位描述

此界面为简体中文。雇主发布的职位名称和描述保留原文,可能为英文。

About Buzz Solutions Buzz Solutions builds PowerAI, a computer vision platform that finds hardware defects in utility transmission and distribution infrastructure and delivers those findings straight into the systems where utilities actually make asset decisions. Our customers include Dominion, AEP, NYPA, and Ameren. We integrate today with Esri's ArcGIS and IBM Maximo, and we work alongside capture partners such as Skydio. We are at the stage where the direct sales motion works and the next order of magnitude has to come from somewhere else. That is what this role is for. The role Design and execute our go-to-market partner strategy and execution — and own the revenue it generates. Over the next 18–24 months that means building a repeatable partner motion in the United States, opening Canada as our first international market, and scoping the markets that follow. You will define our partnership categories (and priorities), evaluate partners in each of those categories, sign them, make them technically viable, enable partner sellers and delivery teams to carry Buzz without our hand on their shoulder, and be accountable for the pipeline and closed ARR that results. This is deliberately a hybrid charter. It requires someone who can sit in a commercial negotiation in the morning, walk an integration architecture with a partner's solutions team in the afternoon, and run a certification workshop for that partner's field engineers the following week. Candidates who can only do one or two of those three will not succeed here. You will be an individual contributor at hire, with an expected path to building a partner organization in year two. Responsibilities Pipeline and revenue through partnershipYou carry a partner-sourced and partner-influenced number. This is not a support function that hands leads to account executives and reports on activity. You will work opportunities alongside our direct sellers and alongside partner sellers, from first qualification through close, and you own the forecast for that motion. You will also define the rules of engagement, deal registration, and margin structure that keep the channel from colliding with direct sales and then enforce them. Technical integration and joint solutions designYou own the commercial and technical shape of how PowerAI plugs into a partner's world and how it drives joint value. First order of business: turn our existing Esri integration from a working piece of engineering into a formal, listed, jointly sold alliance, then do the same for Maximo, then prioritize what follows against real pipeline rather than a wish list. You'll also own the hyperscaler track — marketplace transactability and co-sell — which is as much a commercial unlock as a technical one. Throughout, you build the reference architectures and joint solution briefs that let a partner's pre-sales team position us credibly without us in the room. You are not expected to write production code. You are expected to hold your own in a conversation about API orchestration, data flow, GIS conflation, and where a given integration will break at enterprise scale — and to know when to pull Product and Engineering into the conversation. Partner enablement and certificationA signed agreement is not a partnership. You'll build the layer that turns signatures into revenue: the sales narrative and objection handling a partner rep can deliver without us, the business case and ROI tooling they need to get a utility's capital committee to yes, the demo certification that lets them run their own discovery, and the technical curriculum that lets their engineers implement and support PowerAI deployments. Over time this becomes a tiered certification program and the basis for a services multiplier on every dollar of software we sell International market entryYou own how Buzz goes international and in what order — the subject of its own section below. The short version: expansion is partner-led by design, and the sequencing judgment is as much a part of this role as the partnerships themselves. Qualifications Built a partner ecosystem from near zero at an early-stage or scaling B2B software company — not inherited and grown a mature program. You've done the unglamorous first version: the first agreement template, the first rules of engagement, the first certification deck. Carried and hit a number through partners. You can walk through specific partner-sourced pipeline and closed revenue you were personally accountable for, how it was measured, and the quarters you missed as well as the ones you made. Sold into slow, regulated, procurement-heavy enterprises. Utilities specifically is a strong advantage; adjacent regulated infrastructure — energy, telecom, transportation, public sector — translates. A career selling exclusively to fast-moving commercial buyers does not. Technical fluency sufficient to be credible without an engineer in the room. You can explain how data moves between a capture provider, our platform, and a customer's GIS and EAM; you can spot where an integration will fail at enterprise scale; you know the difference between a demo integration and a supportable one. Built sales and technical enablement material yourself — partner pitch narratives, ROI models, demo certification, delivery curriculum. Written, not commissioned. Negotiated real partner commercial terms — referral, resell, white-label, and OEM structures, margin and discount frameworks, deal registration, data rights, and liability — in partnership with legal. Comfortable as an individual contributor in an ambiguous, resource-constrained environment. For the first year, you are the partner organization Buzz Solutions does not provide sponsorship for work authorization in the United States at this time. Buzz Solutions is an Equal Employment Opportunity employer. All qualified applicants will receive consideration for employment without regard to any protected classification as defined by law. Originally posted on Himalayas

查找职位、比较要求,再准备申请

从你希望从事的职位或运用的技能开始搜索。调整地点和职业筛选,打开职位比较工作职责。如果没有结果,可以使用更短的关键词,或逐一移除筛选条件。

区分必备要求和优先条件,检查已列出的工作安排、薪资和地点。远程职位也可能要求特定居住国家、工作许可或工作时间重合。请向雇主确认职位信息和完整条件。

选择能够回应职位要求的真实经历,说明你的贡献,只使用能够证实的数字。遵循雇主的申请说明,并在提交前检查联系方式、文档内容和 PDF。

提交申请前的检查清单

求职常见问题

为什么有些职位使用英文?

职位名称和描述由招聘企业撰写。为避免改变招聘要求或工作条件,我们保留原文。操作界面和本指南使用简体中文。如果中文搜索没有结果,可以尝试使用职位发布语言中的名称或技能,例如“software engineer”。搜索词不会自动翻译,界面语言也不代表企业要求的申请语言。

远程职位是否允许从任何国家工作?

不一定。企业可能对居住国家、工作许可或工作时段有要求。请查看原始招聘页面中的具体条件。如果未说明,应先向企业确认,再判断能否从你所在的地区工作。“远程”标签本身并不代表没有地点限制。

搜索没有结果时应该怎么办?

尝试更通用的职位名称或单个技能,并逐一移除筛选条件。不同企业可能用不同名称描述相似工作。如果某个职位已经消失,请在企业招聘页面搜索其职位编号。扩大搜索范围不会让已经关闭的职位重新开放。

申请会通过 ResumizeAI 直接提交吗?

申请按钮会打开外部网站。请按照企业或招聘服务的说明,在该网站完成并确认提交。在 ResumizeAI 中准备简历并不等于已经申请职位。如果链接只打开企业网站,请先找到对应职位,再继续申请流程。

如何针对职位调整简历和求职信?

将招聘要求与能够解释清楚的项目、任务和成果联系起来。突出相关经历,不要添加未经实际掌握的技能或虚构成绩。在求职信中用具体例子说明申请动机,并遵守企业要求的语言和文件格式。提交前检查两份文件,确保内容准确、联系方式正确、链接可用。