Enterprise Geo Hunter Account Executive - Financial Services
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content.
We need to parse the job posting.
Key parts:
- Title: Enterprise Geo Hunter Account Executive at Databricks (but we don't repeat as heading).
- The posting includes:
**Impact You Will Have** (list of duties). That's responsibilities.
**What We Look For** (requirements/qualifications/skills). Could be split.
**Pay Range Transparency** (pay range). Provide pay.
**Benefits** (benefits section).
**About Databricks** (company description). Could be "About the role"? Actually "About Databricks" is company overview; could be placed under "About the role"? Usually "About the role" is description of role; but we have "Impact You Will Have" as responsibilities. "About Databricks" is company info; maybe we can put under "About the role"? But guidelines: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings.
We have:
- Responsibilities: Impact You Will Have (list of duties). So Responsibilities
with - items.
- Requirements/Qualifications/Skills: What We Look For (list of qualifications). Could be combined into Requirements or Qualifications. We'll decide: maybe
Requirements
with list.
- Pay: Pay Range Transparency with zones. Provide Pay
with details.
- Benefits: Benefits section. Provide Benefits
with maybe a describing benefits and link.
- About the role: Could be the introductory paragraph: "As an Enterprise Geo Hunter Account Executive at Databricks, you are a seasoned sales professional..." That's role description. So
About the role
with .
- Schedule: Not mentioned; skip.
- Skills: Could be separate but we can incorporate into Requirements.
We must not include boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to remove sections like "Our Commitment to Diversity and Inclusion", "Compliance", maybe also "About Databricks" (company overview) is not required but could be considered "About the role"? Actually "About Databricks" is company overview, not role. The instruction says include a section ONLY when the posting has real, specific content for it. We have "About Databricks" content; but we don't have a heading for that in allowed list. Could we put it under "About the role"? Might be okay but it's not exactly role. However we could treat "About Databricks" as "About the role" content? Might be stretching. Better to include a section "About the role" with the initial description, and maybe also include a short paragraph about Databricks under same section? Could combine.
But we must not invent sections. We have allowed headings list; we can use any of them. We'll include:
- About the role (intro paragraph)
- Responsibilities (Impact You Will Have)
- Requirements (What We Look For)
- Pay (Pay Range Transparency)
- Benefits (Benefits)
We'll omit Schedule.
Now we need to preserve all substantive information, not invent or summarize away detail. So we need to keep the details from each section.
Let's extract.
**About the role** (first paragraph):
"As an Enterprise Geo Hunter Account Executive at Databricks, you are a seasoned sales professional with experience selling to Financial Services accounts. 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. Always looking for new opportunities, you will be asked to hunt after net new logos. Along with the chance to close an exciting deal, we also offer accelerators above 100% quota attainment."
That's the role description.
**Responsibilities** (Impact You Will Have):
List:
- Meet with CIOs, IT executives, LOB executives, Program Managers, and other important partners
- Close both new accounts and existing accounts
- Identify and close quick, small wins while managing longer, complex sales cycles
- 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 customers
- Promote Databricks' enterprise cloud data platform powered by Apache Spark™
- Ensure 100% satisfaction among all customers
- Prioritize opportunities and applying appropriate resources
- Build a plan for success internally at Databricks and externally with your accounts
We need to keep each as
- .
**Requirements** (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
- Prior customer relationships with CIOs, program managers, and essential decision makers
- Simply articulate intricate cloud technologies
- 4+ years experience exceeding sales quotas
- Expertise with financial services institutions preferable
- Success closing net new business
- Understanding of Spark and big data preferable
- Passion for cloud technologies
- Bachelor's Degree
We need to keep each as
- . Note: "Simply articulate intricate cloud technologies" maybe missing verb; but keep as is.
**Pay** (Pay Range Transparency):
Paragraph: "Databricks is committed to fair and equitable compensation practices. The pay range(s) for this role is listed below and represents the expected base salary range for non-commissionable roles or on-target earnings for commissionable roles. Actual compensation packages are based on several factors that are unique to each candidate, including but not limited to job-related skills, depth of experience, relevant certifications and training, and specific work location. Based on the factors above, Databricks anticipated utilizing the full width of the range. The total compensation package for this position may also include eligibility for annual performance bonus, equity, and the benefits listed above. For more information regarding which range your location is in visit our page here."
Then zones:
- Zone 1 Pay Range $220,100—$302,600 USD
- Zone 2 Pay Range $220,100—$302,600 USD
- Zone 3 Pay Range $220,100—$302,600 USD
- Zone 4 Pay Range $220,100—$302,600 USD
We need to preserve all. Could present as
- each zone.
**Benefits**:
Paragraph: "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."
We keep that.
We should not include the "Our Commitment to Diversity and Inclusion", "Compliance", etc.
Now produce HTML fragment:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Pay
Databricks is committed to fair and equitable compensation practices. The pay range(s) for this role is listed below and represents the expected base salary range for non-commissionable roles or on-target earnings for commissionable roles. Actual compensation packages are based on several factors that are unique to each candidate, including but not limited to job-related skills, depth of experience, relevant certifications and training, and specific work location. Based on the factors above, Databricks anticipated utilizing the full width of the range. The total compensation package for this position may also include eligibility for annual performance bonus, equity, and the benefits listed above. For more information regarding which range your location is in visit our page here.
- Zone 1 Pay Range $220,100—$302,600 USD
- Zone 2 Pay Range $220,100—$302,600 USD
- Zone 3 Pay Range $220,100—$302,600 USD
- Zone 4 Pay Range $220,100—$302,600 USD
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.
We must not include any extra text like explanations. Only HTML.
Check for any duplicated lines: we haven't repeated.
Check for any boilerplate: we removed diversity, compliance, etc.
Check for any placeholders: none.
Now ensure we didn't miss any substantive info: The initial paragraph also mentions "Along with the chance to close an exciting deal, we also offer accelerators above 100% quota attainment." That's included.
Also "You love understanding a product in depth and are passionate about communicating its value to Customers and System Integrators." included.
Now ensure we didn't miss any responsibilities: we captured all.
Check responsibilities list: we have 10 items. Let's verify each from text:
- Meet with CIOs, IT executives, LOB executives, Program Managers, and other important partners
- Close both new accounts and existing accounts
- Identify and close quick, small wins while managing longer, complex sales cycles
- 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 customers
- Promote Databricks' enterprise cloud data platform powered by Apache Spark™
- Ensure 100% satisfaction among all customers
- Prioritize opportunities and applying appropriate resources
- Build a plan for success internally at Databricks and externally with your accounts
Yes.
Now requirements list: verify each:
- 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
- Prior customer relationships with CIOs, program managers, and essential decision makers
- Simply articulate intricate cloud technologies
- 4+ years experience exceeding sales quotas
- Expertise with financial services institutions preferable
- Success closing net new business
- Understanding of Spark and big data preferable
- Passion for cloud technologies
- Bachelor's Degree
Yes.
Now pay: we included the paragraph and zones.
Now benefits: we included paragraph.
Now ensure we didn't include any extra like "About Databricks" company overview. We omitted that. Is that substantive? It's about the company, not role. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We have content for "About Databricks" but we don't have a heading for that in allowed list. Could we incorporate it under "About the role"? Might be okay but it's not exactly role. However the instruction says we can use headings like About the role, Responsibilities, etc. It didn't forbid adding other content under those headings. So we could add a paragraph about Databricks under About the role after the role description. That would preserve that info. Let's consider: The "About Databricks" paragraph is substantive; we should preserve it. If we omit it, we lose info. So better to include it under About the role.
Thus About the role section will have
Requirements
with list. - Pay: Pay Range Transparency with zones. ProvidePay
with details. - Benefits: Benefits section. ProvideBenefits
with maybe adescribing benefits and link. - About the role: Could be the introductory paragraph: "As an Enterprise Geo Hunter Account Executive at Databricks, you are a seasoned sales professional..." That's role description. So
About the role
with. - Schedule: Not mentioned; skip. - Skills: Could be separate but we can incorporate into Requirements. We must not include boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to remove sections like "Our Commitment to Diversity and Inclusion", "Compliance", maybe also "About Databricks" (company overview) is not required but could be considered "About the role"? Actually "About Databricks" is company overview, not role. The instruction says include a section ONLY when the posting has real, specific content for it. We have "About Databricks" content; but we don't have a heading for that in allowed list. Could we put it under "About the role"? Might be okay but it's not exactly role. However we could treat "About Databricks" as "About the role" content? Might be stretching. Better to include a section "About the role" with the initial description, and maybe also include a short paragraph about Databricks under same section? Could combine. But we must not invent sections. We have allowed headings list; we can use any of them. We'll include: - About the role (intro paragraph) - Responsibilities (Impact You Will Have) - Requirements (What We Look For) - Pay (Pay Range Transparency) - Benefits (Benefits) We'll omit Schedule. Now we need to preserve all substantive information, not invent or summarize away detail. So we need to keep the details from each section. Let's extract. **About the role** (first paragraph): "As an Enterprise Geo Hunter Account Executive at Databricks, you are a seasoned sales professional with experience selling to Financial Services accounts. 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. Always looking for new opportunities, you will be asked to hunt after net new logos. Along with the chance to close an exciting deal, we also offer accelerators above 100% quota attainment." That's the role description. **Responsibilities** (Impact You Will Have): List: - Meet with CIOs, IT executives, LOB executives, Program Managers, and other important partners - Close both new accounts and existing accounts - Identify and close quick, small wins while managing longer, complex sales cycles - 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 customers - Promote Databricks' enterprise cloud data platform powered by Apache Spark™ - Ensure 100% satisfaction among all customers - Prioritize opportunities and applying appropriate resources - Build a plan for success internally at Databricks and externally with your accounts We need to keep each as
- each zone.
**Benefits**:
Paragraph: "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."
We keep that.
We should not include the "Our Commitment to Diversity and Inclusion", "Compliance", etc.
Now produce HTML fragment:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Pay
Databricks is committed to fair and equitable compensation practices. The pay range(s) for this role is listed below and represents the expected base salary range for non-commissionable roles or on-target earnings for commissionable roles. Actual compensation packages are based on several factors that are unique to each candidate, including but not limited to job-related skills, depth of experience, relevant certifications and training, and specific work location. Based on the factors above, Databricks anticipated utilizing the full width of the range. The total compensation package for this position may also include eligibility for annual performance bonus, equity, and the benefits listed above. For more information regarding which range your location is in visit our page here.
- Zone 1 Pay Range $220,100—$302,600 USD
- Zone 2 Pay Range $220,100—$302,600 USD
- Zone 3 Pay Range $220,100—$302,600 USD
- Zone 4 Pay Range $220,100—$302,600 USD
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.
We must not include any extra text like explanations. Only HTML. Check for any duplicated lines: we haven't repeated. Check for any boilerplate: we removed diversity, compliance, etc. Check for any placeholders: none. Now ensure we didn't miss any substantive info: The initial paragraph also mentions "Along with the chance to close an exciting deal, we also offer accelerators above 100% quota attainment." That's included. Also "You love understanding a product in depth and are passionate about communicating its value to Customers and System Integrators." included. Now ensure we didn't miss any responsibilities: we captured all. Check responsibilities list: we have 10 items. Let's verify each from text: - Meet with CIOs, IT executives, LOB executives, Program Managers, and other important partners - Close both new accounts and existing accounts - Identify and close quick, small wins while managing longer, complex sales cycles - 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 customers - Promote Databricks' enterprise cloud data platform powered by Apache Spark™ - Ensure 100% satisfaction among all customers - Prioritize opportunities and applying appropriate resources - Build a plan for success internally at Databricks and externally with your accounts Yes. Now requirements list: verify each: - 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 - Prior customer relationships with CIOs, program managers, and essential decision makers - Simply articulate intricate cloud technologies - 4+ years experience exceeding sales quotas - Expertise with financial services institutions preferable - Success closing net new business - Understanding of Spark and big data preferable - Passion for cloud technologies - Bachelor's Degree Yes. Now pay: we included the paragraph and zones. Now benefits: we included paragraph. Now ensure we didn't include any extra like "About Databricks" company overview. We omitted that. Is that substantive? It's about the company, not role. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We have content for "About Databricks" but we don't have a heading for that in allowed list. Could we incorporate it under "About the role"? Might be okay but it's not exactly role. However the instruction says we can use headings like About the role, Responsibilities, etc. It didn't forbid adding other content under those headings. So we could add a paragraph about Databricks under About the role after the role description. That would preserve that info. Let's consider: The "About Databricks" paragraph is substantive; we should preserve it. If we omit it, we lose info. So better to include it under About the role. Thus About the role section will have