Strategic Enterprise Account Executive, State and Local
for headings. Use - for lists. Use
for prose. No markdown fences. No extra html/body.
We need to parse the posting.
Let's extract content:
Job title: Strategic Enterprise Account Executive covering NYS and New York City.
We should not repeat job title as heading.
We need sections:
- About the role: likely the paragraph describing dual mandate etc.
- Responsibilities: bullet list of duties.
- Requirements: maybe experience etc.
- Qualifications: maybe education etc.
- Skills: maybe specific abilities.
- Benefits: listed.
- Pay: pay range.
- Schedule: not mentioned; likely not present, so omit.
We must not create empty.
We need to preserve all substantive info.
Let's extract sections.
First, after title line: "As a Strategic Enterprise Account Executive covering NYS and New York City, you will carry a dual mandate: grow and protect a large high consumption install base while simultaneously building new business and acquiring net new logos across the region. This position requires someone who can operate with equal discipline in two fundamentally different motions and manage their time with intention. The account management side of this role demands deep domain fluency and multi-stakeholder orchestration within complex, high-value customers. The new business side demands prospecting rigor, pipeline generation and the ability to open doors in agencies where Databricks has no existing footprint. The ideal candidate is a strategic sales professional with 15+ years of experience selling to this market. You are based there, you know how to sell innovation and change through customer vision expansion and can guide deals forward to compress decision cycles. You love understanding a product in depth and are passionate about communicating its value to customers and system integrators. Databricks operates at the leading edge of the Unified Data Analytics and AI space. Our customers turn to us to lead the accelerated innovation that their agencies need to gain first-mover advantage in today’s landscape. As we continue our rapid expansion, we are looking for a creative, execution-oriented Strategic Enterprise Account Executive to join the Databricks team and maximize the phenomenal market opportunity that exists for Databricks in New York.. Along with the chance to close exciting deals, we also offer accelerators above 100% quota attainment."
That's about the role.
Then "The Impact You Will Have" list:
- Manage complex sales cycles and present to C-level executives.
- Exceed activity, pipeline, and revenue targets
- Track all customer details including use case, purchase time frames, next steps, and forecasting in Salesforce
- Use a solution-based approach to selling and creating value for your customer
- Promote Databricks' enterprise cloud data platform powered by Apache Spark™
- Ensure 100% satisfaction among your existing customer base
- Prioritize strategic opportunities and apply appropriate resources
That's responsibilities.
Then "What We Look For" list:
- You have previously worked in an early-stage company, and you know how to navigate and be successful
- Field sales experience within big data, Cloud, or SaaS sales
- Experience managing large, complex State and Local accounts is preferred.
- Prior customer relationships in the region
- Strong executive presence and the ability to engage credibly with Commissioners, CFO’s, CIOs and Program Leaders.
- 15+ years experience exceeding sales quotas
- Success closing new accounts while working existing accounts
- Understanding of Spark and big data preferable
- Passion for cloud technologies
- Bachelor's Degree
That's qualifications/requirements/skills.
Then "Pay Range Transparency" paragraph about pay range, then "Zone 1 Pay Range $311,600—$428,450 USD". Also mention total compensation may include annual performance bonus, equity, benefits.
Then "Benefits" heading: "At Databricks, we strive to provide comprehensive benefits and perks that meet the needs of all of our employees. For specific details on the benefits offered in your region click here."
No specific benefits listed; just generic statement. According to rules: we should include a section only when posting has real, specific content for it. The Benefits section currently only has generic statement with link; no specific benefits enumerated. Might be considered not specific enough. However they said "Benefits At Databricks, we strive to provide comprehensive benefits and perks that meet the needs of all of our employees. For specific details on the benefits offered in your region click here." That's not specific. So maybe we should omit Benefits section because no specific content. But they said "Prefer a few substantive sections over many thin ones." So we could omit Benefits if not specific.
Pay: we have specific pay range, so include Pay section.
Schedule: none, omit.
Now we need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can combine some: maybe Requirements and Qualifications overlap. We could have Requirements (experience, etc.) and Qualifications (education). Skills could be specific abilities like Spark, cloud tech, executive presence.
Let's extract:
Requirements: 15+ years experience exceeding sales quotas, success closing new accounts while working existing accounts, field sales experience within big data, Cloud, or SaaS sales, experience managing large, complex State and Local accounts preferred, prior customer relationships in the region, strong executive presence and ability to engage credibly with Commissioners, CFO’s, CIOs and Program Leaders.
Qualifications: Bachelor's Degree, previously worked in an early-stage company, understanding of Spark and big data preferable, passion for cloud technologies.
Skills: maybe solution-based selling, multi-stakeholder orchestration, prospecting rigor, pipeline generation, ability to open doors, deep domain fluency, etc. But many are in responsibilities.
We could keep Skills as list of specific abilities: solution-based selling, deep domain fluency, multi-stakeholder orchestration, prospecting rigor, pipeline generation, ability to open doors, executive presence, understanding of Spark, passion for cloud tech.
But we need to avoid duplication. However we must preserve all substantive info; duplication is okay if it's present in posting. But we should not invent.
Better to follow the natural sections: About the role (the initial paragraph). Responsibilities (The Impact You Will Have). Requirements (What We Look For). Qualifications (maybe Bachelor's Degree). Skills (maybe understanding of Spark, passion for cloud tech). Benefits (maybe we could include the generic statement? Might be considered not specific; but we could still include as it's the only benefit info. The rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The benefits statement is generic but not placeholder like "not specified". It's a statement about benefits but not specific. Might be considered filler? It's not a placeholder; it's actual content but vague. I'd lean to include Benefits section with that paragraph.
Pay: include pay range.
Schedule: none, omit.
Now produce HTML.
Structure:
About the role
... paragraph ...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- Bachelor's Degree
- Previously worked in an early-stage company
- Understanding of Spark and big data preferable
- Passion for cloud technologies
Skills
- Solution-based selling approach
- Deep domain fluency and multi-stakeholder orchestration
- Prospecting rigor and pipeline generation
- Ability to open doors in agencies where Databricks has no existing footprint
- Strong executive presence and ability to engage credibly with Commissioners, CFOs, CIOs, Program Leaders
- Understanding of Spark and big data
- Passion for cloud technologies
But note some overlap with qualifications; but okay.
Alternatively we could merge Qualifications and Skills into one but we need headings only if content.
We could also omit Skills if we think it's too thin. But we have some specific skills.
Let's decide to include Skills.
Now Pay:
Pay
Zone 1 Pay Range $311,600—$428,450 USD
Optionally mention total compensation may include annual performance bonus, equity, benefits. That's also substantive. So include that sentence.
Thus Pay section paragraph: "Zone 1 Pay Range $311,600—$428,450 USD. The total compensation package may also include eligibility for annual performance bonus, equity, and the benefits listed above."
Now Benefits:
Benefits
At Databricks, we strive to provide comprehensive benefits and perks that meet the needs of all of our employees. For specific details on the benefits offered in your region click here.
Now ensure we removed boilerplate: removed Job ID, requisition numbers, cookie/navigation/legal/EEO etc. Also removed "About Databricks" paragraph? That is company description; could be considered part of About the role? It's not about the role but about company. Should we include? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The About Databricks paragraph is substantive but not about role. However we have no heading for company overview. Could we include it under About the role? Might be okay to add a paragraph after the role description. But the instruction says use headings for sections like About the role, Responsibilities, etc. It didn't forbid adding extra paragraphs not under headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. It doesn't say we cannot have other headings, but we should follow those headings. Probably we should include the About Databricks paragraph under About the role or maybe as a separate section like "About Databricks". But not in list of allowed headings. Safer to incorporate it into About the role paragraph.
Thus About the role paragraph will include the initial description plus the Databricks description.
Let's craft About the role paragraph:
"As a Strategic Enterprise Account Executive covering NYS and New York City, you will carry a dual mandate: grow and protect a large high consumption install base while simultaneously building new business and acquiring net new logos across the region. This position requires someone who can operate with equal discipline in two fundamentally different motions and manage their time with intention. The account management side of this role demands deep domain fluency and multi-stakeholder orchestration within complex, high-value customers. The new business side demands prospecting rigor, pipeline generation and the ability to open doors in agencies where Databricks has no existing footprint. The ideal candidate is a strategic sales professional with 15+ years of experience selling to this market. You are based there, you know how to sell innovation and change through customer vision expansion and can guide deals forward to compress decision cycles. You love understanding a product in depth and are passionate about communicating its value to customers and system integrators. Databricks operates at the leading edge of the Unified Data Analytics and AI space. Our customers turn to us to lead the accelerated innovation that their agencies need to gain first-mover advantage in today’s landscape. As we continue our rapid expansion, we are looking for a creative, execution-oriented Strategic Enterprise Account Executive to join the Databricks team and maximize the phenomenal market opportunity that exists for Databricks in New York. Along with the chance to close exciting deals, we also offer acceler
for prose. No markdown fences. No extra html/body. We need to parse the posting. Let's extract content: Job title: Strategic Enterprise Account Executive covering NYS and New York City. We should not repeat job title as heading. We need sections: - About the role: likely the paragraph describing dual mandate etc. - Responsibilities: bullet list of duties. - Requirements: maybe experience etc. - Qualifications: maybe education etc. - Skills: maybe specific abilities. - Benefits: listed. - Pay: pay range. - Schedule: not mentioned; likely not present, so omit. We must not create empty. We need to preserve all substantive info. Let's extract sections. First, after title line: "As a Strategic Enterprise Account Executive covering NYS and New York City, you will carry a dual mandate: grow and protect a large high consumption install base while simultaneously building new business and acquiring net new logos across the region. This position requires someone who can operate with equal discipline in two fundamentally different motions and manage their time with intention. The account management side of this role demands deep domain fluency and multi-stakeholder orchestration within complex, high-value customers. The new business side demands prospecting rigor, pipeline generation and the ability to open doors in agencies where Databricks has no existing footprint. The ideal candidate is a strategic sales professional with 15+ years of experience selling to this market. You are based there, you know how to sell innovation and change through customer vision expansion and can guide deals forward to compress decision cycles. You love understanding a product in depth and are passionate about communicating its value to customers and system integrators. Databricks operates at the leading edge of the Unified Data Analytics and AI space. Our customers turn to us to lead the accelerated innovation that their agencies need to gain first-mover advantage in today’s landscape. As we continue our rapid expansion, we are looking for a creative, execution-oriented Strategic Enterprise Account Executive to join the Databricks team and maximize the phenomenal market opportunity that exists for Databricks in New York.. Along with the chance to close exciting deals, we also offer accelerators above 100% quota attainment." That's about the role. Then "The Impact You Will Have" list: - Manage complex sales cycles and present to C-level executives. - Exceed activity, pipeline, and revenue targets - Track all customer details including use case, purchase time frames, next steps, and forecasting in Salesforce - Use a solution-based approach to selling and creating value for your customer - Promote Databricks' enterprise cloud data platform powered by Apache Spark™ - Ensure 100% satisfaction among your existing customer base - Prioritize strategic opportunities and apply appropriate resources That's responsibilities. Then "What We Look For" list: - You have previously worked in an early-stage company, and you know how to navigate and be successful - Field sales experience within big data, Cloud, or SaaS sales - Experience managing large, complex State and Local accounts is preferred. - Prior customer relationships in the region - Strong executive presence and the ability to engage credibly with Commissioners, CFO’s, CIOs and Program Leaders. - 15+ years experience exceeding sales quotas - Success closing new accounts while working existing accounts - Understanding of Spark and big data preferable - Passion for cloud technologies - Bachelor's Degree That's qualifications/requirements/skills. Then "Pay Range Transparency" paragraph about pay range, then "Zone 1 Pay Range $311,600—$428,450 USD". Also mention total compensation may include annual performance bonus, equity, benefits. Then "Benefits" heading: "At Databricks, we strive to provide comprehensive benefits and perks that meet the needs of all of our employees. For specific details on the benefits offered in your region click here." No specific benefits listed; just generic statement. According to rules: we should include a section only when posting has real, specific content for it. The Benefits section currently only has generic statement with link; no specific benefits enumerated. Might be considered not specific enough. However they said "Benefits At Databricks, we strive to provide comprehensive benefits and perks that meet the needs of all of our employees. For specific details on the benefits offered in your region click here." That's not specific. So maybe we should omit Benefits section because no specific content. But they said "Prefer a few substantive sections over many thin ones." So we could omit Benefits if not specific. Pay: we have specific pay range, so include Pay section. Schedule: none, omit. Now we need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine some: maybe Requirements and Qualifications overlap. We could have Requirements (experience, etc.) and Qualifications (education). Skills could be specific abilities like Spark, cloud tech, executive presence. Let's extract: Requirements: 15+ years experience exceeding sales quotas, success closing new accounts while working existing accounts, field sales experience within big data, Cloud, or SaaS sales, experience managing large, complex State and Local accounts preferred, prior customer relationships in the region, strong executive presence and ability to engage credibly with Commissioners, CFO’s, CIOs and Program Leaders. Qualifications: Bachelor's Degree, previously worked in an early-stage company, understanding of Spark and big data preferable, passion for cloud technologies. Skills: maybe solution-based selling, multi-stakeholder orchestration, prospecting rigor, pipeline generation, ability to open doors, deep domain fluency, etc. But many are in responsibilities. We could keep Skills as list of specific abilities: solution-based selling, deep domain fluency, multi-stakeholder orchestration, prospecting rigor, pipeline generation, ability to open doors, executive presence, understanding of Spark, passion for cloud tech. But we need to avoid duplication. However we must preserve all substantive info; duplication is okay if it's present in posting. But we should not invent. Better to follow the natural sections: About the role (the initial paragraph). Responsibilities (The Impact You Will Have). Requirements (What We Look For). Qualifications (maybe Bachelor's Degree). Skills (maybe understanding of Spark, passion for cloud tech). Benefits (maybe we could include the generic statement? Might be considered not specific; but we could still include as it's the only benefit info. The rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The benefits statement is generic but not placeholder like "not specified". It's a statement about benefits but not specific. Might be considered filler? It's not a placeholder; it's actual content but vague. I'd lean to include Benefits section with that paragraph. Pay: include pay range. Schedule: none, omit. Now produce HTML. Structure:
About the role
... paragraph ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- Bachelor's Degree
- Previously worked in an early-stage company
- Understanding of Spark and big data preferable
- Passion for cloud technologies
Skills
- Solution-based selling approach
- Deep domain fluency and multi-stakeholder orchestration
- Prospecting rigor and pipeline generation
- Ability to open doors in agencies where Databricks has no existing footprint
- Strong executive presence and ability to engage credibly with Commissioners, CFOs, CIOs, Program Leaders
- Understanding of Spark and big data
- Passion for cloud technologies
Pay
Zone 1 Pay Range $311,600—$428,450 USD
Optionally mention total compensation may include annual performance bonus, equity, benefits. That's also substantive. So include that sentence. Thus Pay section paragraph: "Zone 1 Pay Range $311,600—$428,450 USD. The total compensation package may also include eligibility for annual performance bonus, equity, and the benefits listed above." Now Benefits:Benefits
At Databricks, we strive to provide comprehensive benefits and perks that meet the needs of all of our employees. For specific details on the benefits offered in your region click here.
Now ensure we removed boilerplate: removed Job ID, requisition numbers, cookie/navigation/legal/EEO etc. Also removed "About Databricks" paragraph? That is company description; could be considered part of About the role? It's not about the role but about company. Should we include? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The About Databricks paragraph is substantive but not about role. However we have no heading for company overview. Could we include it under About the role? Might be okay to add a paragraph after the role description. But the instruction says use headings for sections like About the role, Responsibilities, etc. It didn't forbid adding extra paragraphs not under headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. It doesn't say we cannot have other headings, but we should follow those headings. Probably we should include the About Databricks paragraph under About the role or maybe as a separate section like "About Databricks". But not in list of allowed headings. Safer to incorporate it into About the role paragraph.
Thus About the role paragraph will include the initial description plus the Databricks description.
Let's craft About the role paragraph:
"As a Strategic Enterprise Account Executive covering NYS and New York City, you will carry a dual mandate: grow and protect a large high consumption install base while simultaneously building new business and acquiring net new logos across the region. This position requires someone who can operate with equal discipline in two fundamentally different motions and manage their time with intention. The account management side of this role demands deep domain fluency and multi-stakeholder orchestration within complex, high-value customers. The new business side demands prospecting rigor, pipeline generation and the ability to open doors in agencies where Databricks has no existing footprint. The ideal candidate is a strategic sales professional with 15+ years of experience selling to this market. You are based there, you know how to sell innovation and change through customer vision expansion and can guide deals forward to compress decision cycles. You love understanding a product in depth and are passionate about communicating its value to customers and system integrators. Databricks operates at the leading edge of the Unified Data Analytics and AI space. Our customers turn to us to lead the accelerated innovation that their agencies need to gain first-mover advantage in today’s landscape. As we continue our rapid expansion, we are looking for a creative, execution-oriented Strategic Enterprise Account Executive to join the Databricks team and maximize the phenomenal market opportunity that exists for Databricks in New York. Along with the chance to close exciting deals, we also offer acceler
for prose. It doesn't say we cannot have other headings, but we should follow those headings. Probably we should include the About Databricks paragraph under About the role or maybe as a separate section like "About Databricks". But not in list of allowed headings. Safer to incorporate it into About the role paragraph. Thus About the role paragraph will include the initial description plus the Databricks description. Let's craft About the role paragraph: "As a Strategic Enterprise Account Executive covering NYS and New York City, you will carry a dual mandate: grow and protect a large high consumption install base while simultaneously building new business and acquiring net new logos across the region. This position requires someone who can operate with equal discipline in two fundamentally different motions and manage their time with intention. The account management side of this role demands deep domain fluency and multi-stakeholder orchestration within complex, high-value customers. The new business side demands prospecting rigor, pipeline generation and the ability to open doors in agencies where Databricks has no existing footprint. The ideal candidate is a strategic sales professional with 15+ years of experience selling to this market. You are based there, you know how to sell innovation and change through customer vision expansion and can guide deals forward to compress decision cycles. You love understanding a product in depth and are passionate about communicating its value to customers and system integrators. Databricks operates at the leading edge of the Unified Data Analytics and AI space. Our customers turn to us to lead the accelerated innovation that their agencies need to gain first-mover advantage in today’s landscape. As we continue our rapid expansion, we are looking for a creative, execution-oriented Strategic Enterprise Account Executive to join the Databricks team and maximize the phenomenal market opportunity that exists for Databricks in New York. Along with the chance to close exciting deals, we also offer acceler