Senior Field Marketing Manager
Cyberhaven · Los Angeles Metropolitan Area · 1 mo ago
RemoteRemoteMarketing$250/hrFull-time
We need to output HTML fragment with sections for headings that have content. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. The posting includes "About The Role" (which is like About the role). Then responsibilities: "What You’ll Do" list. Then "Who You Are" includes experience, qualifications, skills. There's no explicit Benefits, Pay, Schedule. So we should not include those sections. Also we should not repeat job title. No metadata like Job ID. Remove boilerplate: EEO, AI Tools Disclosure, etc. Also remove "Joining Cyberhaven means..." maybe that's about company description; could be considered part of About the role? It's not a responsibility or requirement. It's more about company. Could be included in About the role as prose. We need to preserve all substantive information. So we include About the role paragraph(s). Then Responsibilities (What You’ll Do) as a list. Then Requirements/Qualifications/Skills: The "Who You Are" includes experience, regional expertise, track record, demand generation knowledge, budget management, cross-functional confidence, tool familiarity, communication, ownership, location and travel. Those could be split into Requirements (experience, regional expertise, track record, demand generation knowledge, budget management, cross-functional confidence, tool familiarity, communication, ownership) and Skills (maybe tool familiarity, communication). But we can combine into one section "Requirements" or "Qualifications". The instruction says use headings for those categories if content exists. We have content for Experience, etc. Could make a single "Requirements" section with a list. Or split into "Qualifications" and "Skills". Let's decide: "Who You Are" includes experience, regional expertise, track record, demand generation knowledge, budget management, cross-functional confidence, tool familiarity, communication, ownership, location and travel. That's a mix of qualifications and skills. We could put them under "Requirements" as a list. Or we could have "Qualifications" for experience, regional expertise, track record, demand generation knowledge, budget management, cross-functional confidence, ownership; and "Skills" for tool familiarity, communication. But we need to avoid thin sections. Better to have one "Requirements" section with a list covering all. That's substantive.
We must not include Benefits, Pay, Schedule because not stated.
We must output only HTML fragment, no /, no markdown fences.
Thus:
. Use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. The posting includes "About The Role" (which is like About the role). Then responsibilities: "What You’ll Do" list. Then "Who You Are" includes experience, qualifications, skills. There's no explicit Benefits, Pay, Schedule. So we should not include those sections. Also we should not repeat job title. No metadata like Job ID. Remove boilerplate: EEO, AI Tools Disclosure, etc. Also remove "Joining Cyberhaven means..." maybe that's about company description; could be considered part of About the role? It's not a responsibility or requirement. It's more about company. Could be included in About the role as prose. We need to preserve all substantive information. So we include About the role paragraph(s). Then Responsibilities (What You’ll Do) as a list. Then Requirements/Qualifications/Skills: The "Who You Are" includes experience, regional expertise, track record, demand generation knowledge, budget management, cross-functional confidence, tool familiarity, communication, ownership, location and travel. Those could be split into Requirements (experience, regional expertise, track record, demand generation knowledge, budget management, cross-functional confidence, tool familiarity, communication, ownership) and Skills (maybe tool familiarity, communication). But we can combine into one section "Requirements" or "Qualifications". The instruction says use headings for those categories if content exists. We have content for Experience, etc. Could make a single "Requirements" section with a list. Or split into "Qualifications" and "Skills". Let's decide: "Who You Are" includes experience, regional expertise, track record, demand generation knowledge, budget management, cross-functional confidence, tool familiarity, communication, ownership, location and travel. That's a mix of qualifications and skills. We could put them under "Requirements" as a list. Or we could have "Qualifications" for experience, regional expertise, track record, demand generation knowledge, budget management, cross-functional confidence, ownership; and "Skills" for tool familiarity, communication. But we need to avoid thin sections. Better to have one "Requirements" section with a list covering all. That's substantive.
We must not include Benefits, Pay, Schedule because not stated.
We must output only HTML fragment, no /, no markdown fences.
Thus:
About the role
... paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
for prose. Thus final output:
About the role
We are looking for an experienced, autonomous field marketing manager to lead and execute all field marketing initiatives across the West Region. This is not an entry-level field role: it requires someone who brings deep B2B cybersecurity experience, understands partner ecosystems, and operates independently, with minimal day-to-day direction. The ideal candidate will own the full spectrum of regional marketing strategy and execution, from live and virtual events to partner programs, pipeline acceleration, and alignment with sales teams and executive stakeholders. You will have a proven track record of influencing the pipeline, championing creative programs, and using advanced tools to measure impact and iterate.
Joining Cyberhaven means joining the team building Data Security for the Agentic Enterprise. Traditional tools fall short. Cyberhaven traces the full lifecycle of your data, adapting protection to changing context, so protection moves with the way people actually work, not against it. AI Changed Work. We Protect It. Backed by $250M from leading investors like Khosla and Redpoint, our team includes leaders who built industry-defining technologies at CrowdStrike, Palo Alto Networks, Meta, Google, and more. This role lets you shape the future of data security, working alongside people driven to protect workflows, not just data, for customers who cannot afford to slow down to stay safe.
Responsibilities
- Own the West Region marketing strategy: Develop and execute a 12-month integrated plan aligned to sales priorities, go-to-market strategy, and regional opportunities.
- Translate business goals into actionable, persona-informed programs that address key buyer pain points across the customer lifecycle.
- Design and deliver high-impact events and experiences: Plan and execute CISO dinners, roadshows, roundtables, golf outings, sporting events and show activations.
- Own all logistics, contracts, vendor management, and follow-up.
- Lead pre-event preparation and coordinate communications with sales, SDRs (sales development representatives), executives, and partners.
- Upload leads, work with marketing operations to confirm proper tracking, and report on pipeline influence and outcomes.
- Align closely with sales and channel teams: Collaborate with account executives and channel account managers to connect field marketing with sales motions.
- Participate in pipeline reviews, QBRs, and planning sessions.
- Proactively identify whitespace opportunities and activate programs that accelerate deals.
- Understand and support ABM strategies.
- Develop and manage channel and partner marketing: Create co-branded programs with VARs and alliance partners that align with joint sales goals.
- Execute channel-specific campaigns and events while tracking shared KPIs.
- Use account mapping, segmentation, and competitive insights to prioritize efforts.
- Use advanced digital tools and analytics: Apply business intelligence platforms, predictive analytics, and marketing automation to optimize campaign performance.
- Analyze funnel performance, forecast demand, and deliver actionable insights to leadership.
- Contribute to dashboards and executive-level reporting.
- Own budget and performance metrics: Plan and manage regional budgets.
- Track spend against outcomes and adjust tactics based on real-time results.
- Understand demand waterfall performance and conversion velocity to improve program outcomes.
- Partner with sales leadership to review data and results regularly, drive continual improvement, and share key insights with the regional and national teams.
- Contribute to campaign ideation and content strategy: Collaborate with global and product marketing on persona development, messaging, and localized content.
- Recommend program themes based on buyer insights, behavior, and market trends.
Requirements
- Experience: 6+ years of field marketing experience in B2B technology, cybersecurity experience strongly preferred.
- Regional expertise: Experience working with West Region enterprise accounts and their buying committees.
- Track record: A history of building and executing integrated field programs that influence pipeline and accelerate deals, owning a full calendar of regional events each quarter, including executive dinners, regional conferences, partner activations, and thought leadership programs.
- Demand generation knowledge: Strong understanding of the buyer's journey, customer lifecycle, and demand generation best practices.
- Budget management: Skilled in