Sr. Manager, Security Channel & Market Growth (Splunk) (Remote)
maybe. - "Meet the Team Splunk Security is focused on ..." This is description of team. Could be "About the role" or maybe "About the team". We need to decide sections. The posting includes: - "Your Impact" bullet points: define and execute partner market-readiness strategies... etc. That's responsibilities. - "Minimum Qualifications" list. - "Preferred Qualifications" list. - There's also a paragraph about Cisco AI Tools usage, etc. That's boilerplate? It's about AI usage; maybe we can drop as it's not substantive about role? It's about recruitment process; maybe we can drop as it's not role content. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI Tools paragraph might be considered legal/boilerplate? It's about recruitment process; maybe we keep? It's not about role. Safer to drop. - "Why Cisco?" paragraph: about company culture, benefits. Could be considered Benefits? But we have separate Benefits section. The "Why Cisco?" includes benefits description: medical, dental, vision, 401k, parental leave, etc. Also mentions salary range. So we can extract Benefits and Pay from that. - Salary range: "The starting salary range posted for this position is $169,300.00 to $237,200.00 ..." plus location-specific ranges. That's Pay. - Benefits: list of benefits: medical, dental and vision insurance, 401(k) plan with Cisco matching contribution, paid parental leave, short and long-term disability coverage, basic life insurance, grants of Cisco restricted stock units, paid time away details: 10 paid holidays, floating holiday, birthday day off, year-end holiday shutdown, 4 paid days off for personal wellness, vacation time details, sick time, volunteer days, bonuses, etc. That's Benefits. - Schedule? Not explicitly mentioned. There's no schedule info like full-time, remote, etc. So we should not create Schedule section. - Skills? Not explicitly listed; maybe we can infer from qualifications but better not to create Skills unless explicit. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications? But we have separate Minimum Qualifications and Preferred Qualifications. Could put them under Requirements and Qualifications sections. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role, Responsibilities, Requirements (minimum), Qualifications (preferred), Benefits, Pay. No Skills, Schedule.
We must not repeat job title as heading. The job title is not given explicitly in text; but we can ignore.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from Minimum Qualifications, Preferred Qualifications, Responsibilities (Your Impact), Benefits details, Pay details, About the role/team description, and application closing date.
We must not include duplicated lines. Ensure we don't repeat same info.
Let's extract:
About the role/team: "Meet the Team Splunk Security is focused on helping organizations strengthen their security operations through market-leading security products and capabilities. Our Partner Go-to-Market team enables a global ecosystem of resellers, MSPs, MSSPs, GSIs, and other strategic partners to successfully position, sell, deliver, and support Splunk Security solutions. We work at the intersection of Product Management, Channel, Sales, Marketing, Enablement, Finance, and Operations to translate product strategy into scalable partner motions. The team is collaborative, execution-oriented, and energized by solving complex go-to-market challenges that directly accelerate growth. This is an opportunity to shape how Splunk Security brings new capabilities to market through partners around the world."
That's substantive.
Responsibilities (Your Impact): bullet points:
- Define and execute partner market-readiness strategies across the Splunk Security portfolio to reduce time to market and accelerate partner-led growth.
- Drive readiness for new products, major releases, and strategic capabilities by ensuring partners have the programs, enablement, messaging, tools, demos, commercial models, and operational processes required for launch and scale.
- Identify and resolve readiness gaps that affect a partner’s ability to position, transact, demonstrate, deploy, or support Splunk Security solutions.
- Develop repeatable go-to-market motions and partner-specific sales plays across resellers, MSPs, MSSPs, GSIs, and other strategic partner types.
- Measure success through partner activation, productivity, pipeline, customer acquisition, and the adoption of scalable partner motions.
We should keep as - .
Minimum Qualifications: list:
- 7+ years of experience in product go-to-market, channel or partner strategy, sales operations, business operations, product management, or a related field.
- 3+ years of experience supporting product launches, partner programs, sales motions, or market-readiness initiatives.
- Experience working in SaaS, cybersecurity, cloud, data, or another complex enterprise technology market.
- Experience working with one or more partner business models, including resellers, managed service providers, managed security service providers, global systems integrators, or distributors.
- Experience using business metrics and reporting to measure program performance, including partner activation, pipeline, customer acquisition, or revenue growth.
Preferred Qualifications:
- Experience developing and scaling MSP and MSSP go-to-market motions, including commercial models, operational readiness, and partner profitability.
- Experience translating complex technical capabilities into partner messaging, customer outcomes, use cases, competitive positioning, demos, and sales tools.
- Experience partnering cross-functionally with Product Management, Sales, Channel, Marketing, Enablement, Finance, Engineering, and Operations.
- Ability to create clarity and structure in ambiguous, fast-paced environments while balancing strategic planning with hands-on execution.
- Strong communication, analytical, project-management, and stakeholder-influence skills.
Benefits: from "Why Cisco?" and following paragraphs:
- U.S. employees are offered benefits, subject to Cisco’s plan eligibility rules, which include medical, dental and vision insurance, a 401(k) plan with a Cisco matching contribution, paid parental leave, short and long-term disability coverage, and basic life insurance.
- Employees may be eligible to receive grants of Cisco restricted stock units, which vest following continued employment with Cisco for defined periods of time.
- U.S. employees are eligible for paid time away as described below, subject to Cisco’s policies:
- 10 paid holidays per full calendar year, plus 1 floating holiday for non-exempt employees
- 1 paid day off for employee’s birthday
- paid year-end holiday shutdown
- 4 paid days off for personal wellness determined by Cisco
- Non-exempt employees** receive 16 days of paid vacation time per full calendar year, accrued at rate of 4.92 hours per pay period for full-time employees
- Exempt employees participate in Cisco’s flexible vacation time off program, which has no defined limit on how much vacation time eligible employees may use (subject to availability and some business limitations)
- 80 hours of sick time off provided on hire date and each January 1st thereafter, and up to 80 hours of unused sick time carried forward from one calendar year to the next
- Additional paid time away may be requested to deal with critical or emergency issues for family members
- Optional 10 paid days per full calendar year to volunteer
- For non-sales roles, employees are also eligible to earn annual bonuses subject to Cisco’s policies.
- Employees On Sales Plans Earn Performance-based Incentive Pay On Top Of Their Base Salary, Which Is Split Between Quota And Non-quota Components, Subject To The Applicable Cisco Plan. (This is more about compensation; maybe part of Pay.)
Pay: Salary range details:
- The starting salary range posted for this position is $169,300.00 to $237,200.00 and reflects the projected salary range for new hires in this position in U.S. and/or Canada locations, not including incentive compensation*, equity, or benefits.
- Individual pay is determined by the candidate's hiring location, market conditions, job-related skillset, experience, qualifications, education, certifications, and/or training.
- The full salary range for certain locations is listed below.
- U.S. employees are offered benefits... (already in Benefits)
- For locations not listed below, the recruiter can share more details about compensation for the role in your location during the hiring process.
- U.S. employees are offered benefits... (duplicate)
- The applicable full salary ranges for this position, by specific state, are listed below:
- New York City Metro Area $194,600.00 - $328,600.00
- Non-Metro New York State & Washington State $179,000.00 - $294,000.00
- For quota-based sales roles on Cisco’s sales plan, the ranges provided in this posting include base pay and sales target incentive compensation combined.
- Employees in Illinois, whether exempt or non-exempt, will participate in a unique time off program to meet local requirements. (That's more about time off, maybe Benefits.)
We need to avoid duplication. We'll combine Pay details: base salary range, location-specific ranges, note about incentive compensation, determination factors.
We should not include the "Employees On Sales Plans Earn Performance-based Incentive Pay..." as it's more about compensation details; could be part of Pay but it's lengthy. Might be considered substantive. However, the instruction: Prefer a few substantive sections over many thin ones. We could include that under Pay as well.
But we must not invent or summarize away detail. So we need to include that info if it's present. It is present in the "Why Cisco?" section after benefits. It's about compensation for sales roles. Since the role is not a sales role (Partner Go-to-Market), but still it's in the posting. We should include it as part of Pay details.
Also the note about Illinois time off program is more about Benefits (time off). We'll incorporate into Benefits.
We must not include boilerplate like "Cisco may use AI Tools..." etc. We'll drop that.
Also drop "Message to applicants applying to work in the U.S. and/or Canada:"? That's part of Pay description; we can keep the salary range info but drop the introductory sentence? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the sentence that says "Message to applicants applying to work in the U.S. and/or Canada: The starting salary range posted for this position is $169,300.00 to $237,200.00..." That's substantive. We'll keep it.
We also need to include the application closing date: "The application window is expected to close on: 09/28/2026". We'll put that in a short
maybe under a generic metadata? Not a heading. Could be a
at top.
We must not include duplicated lines. Ensure we don't repeat same benefit lines.
Now structure:
The application window is expected to close on: 09/28/2026.
About the role
Meet the Team Splunk Security is focused on helping organizations strengthen their security operations through market-leading security products and capabilities. Our Partner Go-to-Market team enables a global ecosystem of resellers, MSPs
maybe under a generic metadata? Not a heading. Could be a
at top. We must not include duplicated lines. Ensure we don't repeat same benefit lines. Now structure:
The application window is expected to close on: 09/28/2026.
About the role
Meet the Team Splunk Security is focused on helping organizations strengthen their security operations through market-leading security products and capabilities. Our Partner Go-to-Market team enables a global ecosystem of resellers, MSPs