Sales Operations Partner
Gambit Security · New York, NY · 3 wk ago
HybridBusiness Development$160k–$190k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications? Actually they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. The posting includes "About Us", "The Opportunity", "About The Role", then a list of responsibilities (the bullet points after "About The Role"? Actually after "About The Role" they list many responsibilities. Then "Requirements:" with bullet list. Then "Benefits — Why Gambit?" with bullet list. Then "Pay Transparency Disclosure" which is about pay but not a specific number; they gave a range earlier: "Competitive OTE of $160K–$190K". That is pay info. So we should include a Pay section with that range. Also Benefits section with the listed benefits. No Schedule info given, so omit Schedule. Also maybe include "About the role" as heading? They said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID etc. They gave example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have sections: About the role (maybe summarizing the opportunity?), Responsibilities (list of duties), Requirements (list), Benefits, Pay. Possibly also Qualifications? But they have Requirements already includes qualifications. Could also have Skills? Not separate. We'll follow.
We need to preserve all substantive information, not invent or summarize away detail. Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. The posting includes "About Us", "The Opportunity", "About The Role", then a list of responsibilities (the bullet points after "About The Role"? Actually after "About The Role" they list many responsibilities. Then "Requirements:" with bullet list. Then "Benefits — Why Gambit?" with bullet list. Then "Pay Transparency Disclosure" which is about pay but not a specific number; they gave a range earlier: "Competitive OTE of $160K–$190K". That is pay info. So we should include a Pay section with that range. Also Benefits section with the listed benefits. No Schedule info given, so omit Schedule. Also maybe include "About the role" as heading? They said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID etc. They gave example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have sections: About the role (maybe summarizing the opportunity?), Responsibilities (list of duties), Requirements (list), Benefits, Pay. Possibly also Qualifications? But they have Requirements already includes qualifications. Could also have Skills? Not separate. We'll follow.
We need to preserve all substantive information, not invent or summarize away detail. Use - for any list of duties/requirements/benefits, and
for prose.
We must remove boilerplate: About Us, The Opportunity? Actually "About Us" and "The Opportunity" are introductory paragraphs; we need to preserve substantive info. The "About Us" describes company; we could put that in a
maybe under a heading? Not required but we could include as a preamble before sections. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." So we can output a series of
and
etc.
We need to not repeat job title as heading. No job title given explicitly, but we can ignore.
We need to include sections only when posting has real specific content. So we will have:
About Us paragraph
The Opportunity paragraph
About the role
maybe we can put a short paragraph summarizing? But the posting already has "About The Role" heading then a list of responsibilities. Actually the responsibilities are listed after "About The Role". So we could treat "About The Role" as a heading and then the responsibilities as a list under it. But they said use for section headings (e.g. About the role, Responsibilities, Requirements...). So we could have About the role
then a
describing the role? But the responsibilities are enumerated; maybe better to have
Responsibilities
with list. And maybe also have About the role
with a short paragraph summarizing the role (the paragraph after "About The Role" before the list?). Actually the text: "About The Role Support the Sales leadership team with timely sales analytics, including weekly pipeline analysis, forecasting, and sales results.Own day-to-day pipeline hygiene - proactively monitor data quality and completeness across the pipeline, and follow up directly with reps to keep information accurate and current.Own the Sales tech stack and Salesforce administration day-to-day: configure and maintain fields, layouts, and workflows (e.g., restructuring the upsell opportunity layout), build new automations, and work directly with our CRM implementor to keep the system scalable and reliable.Build and maintain the reporting and dashboards sales leadership relies on to track performance.Serve as a connective layer across the go-to-market org - helping resolve process and communication gaps between the teams (e.g., define marketing to sales lead handoff).Drive business change by developing a keen understanding of the business, identifying core focus areas through data-driven insights, and building trust with business partners.Partner with the field to craft and establish GTM strategy, and own the modeling and implementation of sales territories and quota setting.Actively identify operational issues and design solutions to make the sales process run better for the sales team.Work closely with GTM team members to share knowledge and methodologies, and help standardize best practices across the field organization.Support deal approvals, structuring, modeling, and proposals to customers.Support the sales compensation plan and monthly commission cycle.Support onboarding and sales enablement."
That is a long paragraph with many responsibilities separated by periods. Could be turned into a list. But we can keep as prose . However they said use
- for any list of duties/requirements/benefits. This is a list of duties, but it's not formatted as list originally. We could convert to list for clarity. But we must preserve all substantive information; converting to list is fine as long as we don't lose info. Probably better to make a
- for each duty. Let's split by the sentences (each starting with a verb). We'll produce list items.
Similarly Requirements: after "Requirements:" there is a paragraph with bullet-like lines but not formatted. We'll split into list items.
Benefits: after "Benefits — Why Gambit?" there is a paragraph with bullet points preceded by em dash or bullet? We'll split.
Pay: we have "Competitive OTE of $160K–$190K — rewarding your contribution as we grow". Also Pay Transparency Disclosure paragraph. We'll include Pay section with that info.
We must not include boilerplate like EEO, etc.
Let's extract.
About Us paragraph: "Gambit is the AI-native resilience platform that ensures digital continuity never expires. It unifies governance across cloud, backups, security tools, and IaC; mapping applications, identifying gaps, and validating recovery paths in real time. Gambit turns resilience assumptions into business certainty before an incident ever occurs."
The Opportunity paragraph: "The ideal candidate has a background in end-to-end sales operations, is comfortable owning Sales tech stack (Salesforce, Gong, Enrichment tools and so on, day-to-day - from system administration to process design - and can move fluidly between granular, operational detail and executive-level insight. You will be able to communicate effectively with leaders across the business while also rolling up your sleeves to fix the process issues that come up week to week."
Now About the role responsibilities: We'll split.
Sentences:
1. Support the Sales leadership team with timely sales analytics, including weekly pipeline analysis, forecasting, and sales results.
2. Own day-to-day pipeline hygiene - proactively monitor data quality and completeness across the pipeline, and follow up directly with reps to keep information accurate and current.
3. Own the Sales tech stack and Salesforce administration day-to-day: configure and maintain fields, layouts, and workflows (e.g., restructuring the upsell opportunity layout), build new automations, and work directly with our CRM implementor to keep the system scalable and reliable.
4. Build and maintain the reporting and dashboards sales leadership relies on to track performance.
5. Serve as a connective layer across the go-to-market org - helping resolve process and communication gaps between the teams (e.g., define marketing to sales lead handoff).
6. Drive business change by developing a keen understanding of the business, identifying core focus areas through data-driven insights, and building trust with business partners.
7. Partner with the field to craft and establish GTM strategy, and own the modeling and implementation of sales territories and quota setting.
8. Actively identify operational issues and design solutions to make the sales process run better for the sales team.
9. Work closely with GTM team members to share knowledge and methodologies, and help standardize best practices across the field organization.
10. Support deal approvals, structuring, modeling, and proposals to customers.
11. Support the sales compensation plan and monthly commission cycle.
12. Support onboarding and sales enablement.
Now Requirements: after "Requirements:" we have:
"Bachelor's degree in business, finance, or a related field.
5+ years of related experience in Sales, Sales Operations, Sales Strategy, Go-to-Market, or an interlinked function, ideally in the software industry.
At least 3 years at an enterprise B2B SaaS company, with a strong preference for candidates coming from early-stage/startup companies, ideally having supported a sales team through a period of change or scaling.
Demonstrable experience in SaaS pricing, deal modeling and structuring, and contract management.
Prior experience in a sales-driven organization; B2B and SaaS experience required. Cybersecurity or AI industry background preferred; fintech welcome; blockchain experience a plus.
Enterprise, complex B2B sales-cycle experience is a strong fit — this role isn't suited to a transactional or consumer sales background.
Comfort working with granular, operational data (e.g., rep activity levels, meeting volume, day-to-day execution metrics), not just high-level, top-line conversion rates.
Advanced Excel skills are a must.
Broad business acumen and strong influencing skills.
Strong planning, organizational, and multitasking skills.
Ability to turn data into insights and action.
A problem solver who identifies and drives solutions to complex business issues.
Tenacious and inquisitive - comfortable asking questions, without a know-it-all attitude.
Must be self-managed, responsive, and able to work in an ambiguous, fast-paced environment.
Intellectual curiosity, a hands-on mentality, and phenomenal attention to detail."
We'll make each line a list item.
Benefits: after "Benefits — Why Gambit?" we have:
"At Gambit, we believe great work starts with great people — and we’re building a team of smart, driven, genuinely great co-workers who enjoy doing big things together. Here’s what you can expect when you join us:
Competitive OTE of $160K–$190K — rewarding your contribution as we grow
Competitive medical, dental, and vision insurance
A $350 work-from-home stipend to create a setup that helps you do your best work
Hybrid work with 3 days per week in our NoMad office
Work alongside smart, supportive, and collaborative co-workers who are excited to build something meaningful together"
Note: The first sentence is prose; we could keep as
. Then list of benefits.
Pay: we have the OTE range already listed in benefits; but they also have a Pay Transparency Disclosure paragraph: "Job level and actual compensation will be decided based on factors including, but not limited to, individual qualifications objectively assessed during the interview process (including skills and prior relevant experience, potential impact, and scope of role), market demands, and specific work location. The listed range is a guideline, and the range for this role may be modified. For roles that are available to be filled remotely, the pay range is localized according to employee work location."
We should include Pay section with that info plus the OTE range maybe. But we must not create Pay section unless posting actually states them. It does state OTE range and Pay Transparency Disclosure. So we can include Pay section with that info.
We should avoid duplication: The OTE range appears both in Benefits list and Pay Transparency. We could keep it in Benefits list as a benefit, and also mention in Pay section? Might be duplicate but okay. However we should preserve all substantive information; duplication is okay if it's present in both places. But we could choose to put OTE range only in Pay section and not duplicate in Benefits. However the Benefits bullet includes "Competitive OTE of $160K–$190K — rewarding your contribution as we grow". That's a benefit. If we omit it from Benefits, we lose that benefit statement. So we should keep it in Benefits list. Then Pay section can include the Pay Transparency Disclosure paragraph (maybe also mention that the range is as listed). We'll not repeat the range again.
Now
for prose. We must remove boilerplate: About Us, The Opportunity? Actually "About Us" and "The Opportunity" are introductory paragraphs; we need to preserve substantive info. The "About Us" describes company; we could put that in a
maybe under a heading? Not required but we could include as a preamble before sections. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." So we can output a series of
and
etc. We need to not repeat job title as heading. No job title given explicitly, but we can ignore. We need to include sections only when posting has real specific content. So we will have:
About Us paragraph
The Opportunity paragraph
About the role
maybe we can put a short paragraph summarizing? But the posting already has "About The Role" heading then a list of responsibilities. Actually the responsibilities are listed after "About The Role". So we could treat "About The Role" as a heading and then the responsibilities as a list under it. But they said use for section headings (e.g. About the role, Responsibilities, Requirements...). So we could have About the role
then a
describing the role? But the responsibilities are enumerated; maybe better to have
Responsibilities
with list. And maybe also haveAbout the role
with a short paragraph summarizing the role (the paragraph after "About The Role" before the list?). Actually the text: "About The Role Support the Sales leadership team with timely sales analytics, including weekly pipeline analysis, forecasting, and sales results.Own day-to-day pipeline hygiene - proactively monitor data quality and completeness across the pipeline, and follow up directly with reps to keep information accurate and current.Own the Sales tech stack and Salesforce administration day-to-day: configure and maintain fields, layouts, and workflows (e.g., restructuring the upsell opportunity layout), build new automations, and work directly with our CRM implementor to keep the system scalable and reliable.Build and maintain the reporting and dashboards sales leadership relies on to track performance.Serve as a connective layer across the go-to-market org - helping resolve process and communication gaps between the teams (e.g., define marketing to sales lead handoff).Drive business change by developing a keen understanding of the business, identifying core focus areas through data-driven insights, and building trust with business partners.Partner with the field to craft and establish GTM strategy, and own the modeling and implementation of sales territories and quota setting.Actively identify operational issues and design solutions to make the sales process run better for the sales team.Work closely with GTM team members to share knowledge and methodologies, and help standardize best practices across the field organization.Support deal approvals, structuring, modeling, and proposals to customers.Support the sales compensation plan and monthly commission cycle.Support onboarding and sales enablement." That is a long paragraph with many responsibilities separated by periods. Could be turned into a list. But we can keep as prose. However they said use
- for any list of duties/requirements/benefits. This is a list of duties, but it's not formatted as list originally. We could convert to list for clarity. But we must preserve all substantive information; converting to list is fine as long as we don't lose info. Probably better to make a
- for each duty. Let's split by the sentences (each starting with a verb). We'll produce list items.
Similarly Requirements: after "Requirements:" there is a paragraph with bullet-like lines but not formatted. We'll split into list items.
Benefits: after "Benefits — Why Gambit?" there is a paragraph with bullet points preceded by em dash or bullet? We'll split.
Pay: we have "Competitive OTE of $160K–$190K — rewarding your contribution as we grow". Also Pay Transparency Disclosure paragraph. We'll include Pay section with that info.
We must not include boilerplate like EEO, etc.
Let's extract.
About Us paragraph: "Gambit is the AI-native resilience platform that ensures digital continuity never expires. It unifies governance across cloud, backups, security tools, and IaC; mapping applications, identifying gaps, and validating recovery paths in real time. Gambit turns resilience assumptions into business certainty before an incident ever occurs."
The Opportunity paragraph: "The ideal candidate has a background in end-to-end sales operations, is comfortable owning Sales tech stack (Salesforce, Gong, Enrichment tools and so on, day-to-day - from system administration to process design - and can move fluidly between granular, operational detail and executive-level insight. You will be able to communicate effectively with leaders across the business while also rolling up your sleeves to fix the process issues that come up week to week."
Now About the role responsibilities: We'll split.
Sentences:
1. Support the Sales leadership team with timely sales analytics, including weekly pipeline analysis, forecasting, and sales results.
2. Own day-to-day pipeline hygiene - proactively monitor data quality and completeness across the pipeline, and follow up directly with reps to keep information accurate and current.
3. Own the Sales tech stack and Salesforce administration day-to-day: configure and maintain fields, layouts, and workflows (e.g., restructuring the upsell opportunity layout), build new automations, and work directly with our CRM implementor to keep the system scalable and reliable.
4. Build and maintain the reporting and dashboards sales leadership relies on to track performance.
5. Serve as a connective layer across the go-to-market org - helping resolve process and communication gaps between the teams (e.g., define marketing to sales lead handoff).
6. Drive business change by developing a keen understanding of the business, identifying core focus areas through data-driven insights, and building trust with business partners.
7. Partner with the field to craft and establish GTM strategy, and own the modeling and implementation of sales territories and quota setting.
8. Actively identify operational issues and design solutions to make the sales process run better for the sales team.
9. Work closely with GTM team members to share knowledge and methodologies, and help standardize best practices across the field organization.
10. Support deal approvals, structuring, modeling, and proposals to customers.
11. Support the sales compensation plan and monthly commission cycle.
12. Support onboarding and sales enablement.
Now Requirements: after "Requirements:" we have:
"Bachelor's degree in business, finance, or a related field.
5+ years of related experience in Sales, Sales Operations, Sales Strategy, Go-to-Market, or an interlinked function, ideally in the software industry.
At least 3 years at an enterprise B2B SaaS company, with a strong preference for candidates coming from early-stage/startup companies, ideally having supported a sales team through a period of change or scaling.
Demonstrable experience in SaaS pricing, deal modeling and structuring, and contract management.
Prior experience in a sales-driven organization; B2B and SaaS experience required. Cybersecurity or AI industry background preferred; fintech welcome; blockchain experience a plus.
Enterprise, complex B2B sales-cycle experience is a strong fit — this role isn't suited to a transactional or consumer sales background.
Comfort working with granular, operational data (e.g., rep activity levels, meeting volume, day-to-day execution metrics), not just high-level, top-line conversion rates.
Advanced Excel skills are a must.
Broad business acumen and strong influencing skills.
Strong planning, organizational, and multitasking skills.
Ability to turn data into insights and action.
A problem solver who identifies and drives solutions to complex business issues.
Tenacious and inquisitive - comfortable asking questions, without a know-it-all attitude.
Must be self-managed, responsive, and able to work in an ambiguous, fast-paced environment.
Intellectual curiosity, a hands-on mentality, and phenomenal attention to detail."
We'll make each line a list item.
Benefits: after "Benefits — Why Gambit?" we have:
"At Gambit, we believe great work starts with great people — and we’re building a team of smart, driven, genuinely great co-workers who enjoy doing big things together. Here’s what you can expect when you join us:
Competitive OTE of $160K–$190K — rewarding your contribution as we grow
Competitive medical, dental, and vision insurance
A $350 work-from-home stipend to create a setup that helps you do your best work
Hybrid work with 3 days per week in our NoMad office
Work alongside smart, supportive, and collaborative co-workers who are excited to build something meaningful together"
Note: The first sentence is prose; we could keep as
. Then list of benefits. Pay: we have the OTE range already listed in benefits; but they also have a Pay Transparency Disclosure paragraph: "Job level and actual compensation will be decided based on factors including, but not limited to, individual qualifications objectively assessed during the interview process (including skills and prior relevant experience, potential impact, and scope of role), market demands, and specific work location. The listed range is a guideline, and the range for this role may be modified. For roles that are available to be filled remotely, the pay range is localized according to employee work location." We should include Pay section with that info plus the OTE range maybe. But we must not create Pay section unless posting actually states them. It does state OTE range and Pay Transparency Disclosure. So we can include Pay section with that info. We should avoid duplication: The OTE range appears both in Benefits list and Pay Transparency. We could keep it in Benefits list as a benefit, and also mention in Pay section? Might be duplicate but okay. However we should preserve all substantive information; duplication is okay if it's present in both places. But we could choose to put OTE range only in Pay section and not duplicate in Benefits. However the Benefits bullet includes "Competitive OTE of $160K–$190K — rewarding your contribution as we grow". That's a benefit. If we omit it from Benefits, we lose that benefit statement. So we should keep it in Benefits list. Then Pay section can include the Pay Transparency Disclosure paragraph (maybe also mention that the range is as listed). We'll not repeat the range again. Now
- for each duty. Let's split by the sentences (each starting with a verb). We'll produce list items.
Similarly Requirements: after "Requirements:" there is a paragraph with bullet-like lines but not formatted. We'll split into list items.
Benefits: after "Benefits — Why Gambit?" there is a paragraph with bullet points preceded by em dash or bullet? We'll split.
Pay: we have "Competitive OTE of $160K–$190K — rewarding your contribution as we grow". Also Pay Transparency Disclosure paragraph. We'll include Pay section with that info.
We must not include boilerplate like EEO, etc.
Let's extract.
About Us paragraph: "Gambit is the AI-native resilience platform that ensures digital continuity never expires. It unifies governance across cloud, backups, security tools, and IaC; mapping applications, identifying gaps, and validating recovery paths in real time. Gambit turns resilience assumptions into business certainty before an incident ever occurs."
The Opportunity paragraph: "The ideal candidate has a background in end-to-end sales operations, is comfortable owning Sales tech stack (Salesforce, Gong, Enrichment tools and so on, day-to-day - from system administration to process design - and can move fluidly between granular, operational detail and executive-level insight. You will be able to communicate effectively with leaders across the business while also rolling up your sleeves to fix the process issues that come up week to week."
Now About the role responsibilities: We'll split.
Sentences:
1. Support the Sales leadership team with timely sales analytics, including weekly pipeline analysis, forecasting, and sales results.
2. Own day-to-day pipeline hygiene - proactively monitor data quality and completeness across the pipeline, and follow up directly with reps to keep information accurate and current.
3. Own the Sales tech stack and Salesforce administration day-to-day: configure and maintain fields, layouts, and workflows (e.g., restructuring the upsell opportunity layout), build new automations, and work directly with our CRM implementor to keep the system scalable and reliable.
4. Build and maintain the reporting and dashboards sales leadership relies on to track performance.
5. Serve as a connective layer across the go-to-market org - helping resolve process and communication gaps between the teams (e.g., define marketing to sales lead handoff).
6. Drive business change by developing a keen understanding of the business, identifying core focus areas through data-driven insights, and building trust with business partners.
7. Partner with the field to craft and establish GTM strategy, and own the modeling and implementation of sales territories and quota setting.
8. Actively identify operational issues and design solutions to make the sales process run better for the sales team.
9. Work closely with GTM team members to share knowledge and methodologies, and help standardize best practices across the field organization.
10. Support deal approvals, structuring, modeling, and proposals to customers.
11. Support the sales compensation plan and monthly commission cycle.
12. Support onboarding and sales enablement.
Now Requirements: after "Requirements:" we have:
"Bachelor's degree in business, finance, or a related field.
5+ years of related experience in Sales, Sales Operations, Sales Strategy, Go-to-Market, or an interlinked function, ideally in the software industry.
At least 3 years at an enterprise B2B SaaS company, with a strong preference for candidates coming from early-stage/startup companies, ideally having supported a sales team through a period of change or scaling.
Demonstrable experience in SaaS pricing, deal modeling and structuring, and contract management.
Prior experience in a sales-driven organization; B2B and SaaS experience required. Cybersecurity or AI industry background preferred; fintech welcome; blockchain experience a plus.
Enterprise, complex B2B sales-cycle experience is a strong fit — this role isn't suited to a transactional or consumer sales background.
Comfort working with granular, operational data (e.g., rep activity levels, meeting volume, day-to-day execution metrics), not just high-level, top-line conversion rates.
Advanced Excel skills are a must.
Broad business acumen and strong influencing skills.
Strong planning, organizational, and multitasking skills.
Ability to turn data into insights and action.
A problem solver who identifies and drives solutions to complex business issues.
Tenacious and inquisitive - comfortable asking questions, without a know-it-all attitude.
Must be self-managed, responsive, and able to work in an ambiguous, fast-paced environment.
Intellectual curiosity, a hands-on mentality, and phenomenal attention to detail."
We'll make each line a list item.
Benefits: after "Benefits — Why Gambit?" we have:
"At Gambit, we believe great work starts with great people — and we’re building a team of smart, driven, genuinely great co-workers who enjoy doing big things together. Here’s what you can expect when you join us:
Competitive OTE of $160K–$190K — rewarding your contribution as we grow
Competitive medical, dental, and vision insurance
A $350 work-from-home stipend to create a setup that helps you do your best work
Hybrid work with 3 days per week in our NoMad office
Work alongside smart, supportive, and collaborative co-workers who are excited to build something meaningful together"
Note: The first sentence is prose; we could keep as