Account Executive, Enterprise Platforms, Tier 2 Grower
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections to include based on content.
We have:
- Intro: "Who we are About Stripe ..." This is about company. Could be "About the role"? Actually "About the role" is typical heading for role description. But we have "What you’ll do" which is responsibilities. We have "Responsibilities" heading already. We have "Who you are" which could be "Requirements" or "Qualifications". We have "Minimum Requirements". We have "In office locations include: San Francisco & New York" and "In-office expectations" which could be "Schedule"? Actually schedule refers to remote/in-office expectations. Could be "Schedule". We have "Pay and benefits" and "Additional benefits". Could combine into Benefits and Pay sections.
We need to avoid empty sections. Use only those with real content.
We need to use - for any list of duties/requirements/benefits.
We need to use
for prose.
We must not repeat job title as heading. The job title is "Account Executive, Existing Business". Not to be used as heading.
We must not put Job ID/requisition numbers as headings (none present).
We must preserve all substantive info.
Let's extract substantive content:
Intro paragraph: "Who we are About Stripe Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world’s largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities. Our mission is to increase the GDP of the internet, and we have a staggering amount of work ahead. That means you have an unprecedented opportunity to put the global economy within everyone’s reach while doing the most important work of your career."
That's about company; could be placed under a heading like "About the role"? Actually "About the role" is more about the role, but we could use "About Stripe" as heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict list; we can use those headings if appropriate. We could use "About the role" for company overview? Might be okay. Or we could skip a heading and just put paragraph? But they want sections when posting has real specific content. The intro is substantive; we could put under About the role
and then a
.
Next: "What you’ll do As an Account Executive, Existing Business, you’ll be managing existing relationships and identifying new opportunities to expand Stripe’s footprint within existing accounts. Specifically, we’re looking for someone who can execute on long-term sales strategies, engage with internal and external stakeholders, align on technical and business requirements with product teams, build value in competitive situations, lead commercial negotiations, and close deals."
That's a prose description; could be under "About the role" as well, but we already used that. Maybe better to have "About the role" for company intro, and "What you’ll do" could be under "Responsibilities"? Actually responsibilities section follows.
Next we have a heading "Responsibilities" then a list of bullet points (though not formatted as bullet list in text but each line starts with a verb). We need to convert to
- .
Responsibilities content:
- Work with existing Stripe customers to develop and execute long-term sales strategies to expand Stripe’s revenue
- Own the full sales cycle, from business case development, to deal structuring and negotiating, to close
- Develop account plans and cross sell into your list of strategic customers, driving growth through expansion and new revenue streams
- Drive deal strategy and commercial negotiations for large, complex renewals
- Develop relationships with executive stakeholders within your book of business, deeply understanding problems they are solving and helping drive to solutions
- Be responsible for account mapping and coordinating effective meetings with the appropriate external stakeholders expanding the customer relationship
- Lead and contribute to team projects to develop and refine our sales process and help shape the Stripe sales culture
Next: "Who you are We’re looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply."
That's intro to requirements.
Then "Minimum Requirements" heading and list:
- 8+ years of sales experience, preferably selling a technical product, with a track record of top performance
- 5+ years leading complex sales cycles with Enterprise organizations required
- Ability to understand technical requirements and craft solutions across multiple products
- Ability to develop and execute account plans spanning multiple business units across complex organizations
- A knack for working well with a wide range of people, both internally and externally
- Strong presentation skills, particularly for in-person meetings with multiple stakeholders
- Proven ability to lead complex negotiations involving bespoke commercial agreements
- Superior verbal and written communication skills
- Ability to operate in a highly ambiguous and fast-paced environment
- Strong interest in technology and a deep understanding of the space
Next: "In office locations include: San Francisco & New York"
Then "In-office expectations" paragraph describing expectations.
We could treat location and expectations under "Schedule" heading (since it's about in-office expectations). Or we could have a "Location" heading but not in examples. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use Schedule for location/in-office expectations.
Thus we can have Schedule
with content: In office locations include: San Francisco & New York. In-office expectations Office-assigned Stripes in most of our locations are currently expected to spend at least 50% of the time in a given month in their local office or with users. This expectation may vary depending on role, team and location. For example, Stripes in Stripe Delivery Center roles in Mexico City, Mexico, Bengaluru, India, and Dublin, Ireland work 100% from the office. Also, some teams have greater in-office attendance requirements, to appropriately support our users and workflows, which the hiring manager will discuss. This approach helps strike a balance between bringing people together for in-person collaboration and learning from each other, while supporting flexibility when possible.
We need to preserve all that.
Next: "Pay and benefits" heading with paragraph: The annual US base salary range for this role is $262,900 - $394,300. For sales roles, the range provided is the role’s On Target Earnings ("OTE") range, meaning that the range includes both the sales commissions/sales bonuses target and annual base salary for the role. This salary range may be inclusive of several career levels at Stripe and will be narrowed during the interview process based on a number of factors, including the candidate’s experience, qualifications, and location. Applicants interested in this role and who are not located in the US may request the annual salary range for their location during the interview process.
Then "Additional benefits for this role may include: equity, company bonus or sales commissions/bonuses; 401(k) plan; medical, dental, and vision benefits; and wellness stipends."
We could combine Pay and Benefits sections: maybe Pay
for salary range, and Benefits
for additional benefits. Or we could have one Benefits section that includes both pay and benefits. The instruction says use headings like Benefits, Pay, Schedule. So we can split.
Thus:
Pay
... salary range ...
Benefits
- equity
- company bonus or sales commissions/bonuses
- 401(k) plan
- medical, dental, and vision benefits
- wellness stipends
We need to ensure we don't include boilerplate like "We look forward to hearing from you..." etc. Remove.
Also remove duplicated lines: The intro "Who we are About Stripe" maybe duplicated? Not sure.
We must not include "At Stripe, we're looking for people with passion, grit, and integrity..." etc. Remove.
Now construct HTML.
We need to decide order: About the role (company intro + What you’ll do?), Responsibilities, Requirements (or Minimum Requirements), Schedule, Pay, Benefits.
We could also have a "Requirements" section for Minimum Requirements. Use heading Requirements
with list.
We could also have "Qualifications" but we already have Requirements; we can stick to Requirements.
We need to avoid empty sections.
Let's draft:
About the role
Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world’s largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities. Our mission is to increase the GDP of the internet, and we have a staggering amount of work ahead. That means you have an unprecedented opportunity to put the global economy within everyone’s reach while doing the most important work of your career.
As an Account Executive, Existing Business, you’ll be managing existing relationships and identifying new opportunities to expand Stripe’s footprint within existing accounts. Specifically, we’re looking for someone who can execute on long-term sales strategies, engage with internal and external stakeholders, align on technical and business requirements with product teams, build value in competitive situations, lead commercial negotiations, and close deals.
Responsibilities
- Work with existing Stripe customers to develop and execute long-term sales strategies to expand Stripe’s revenue
- Own the full sales cycle, from business case development, to deal structuring and negotiating, to close
- Develop account plans and cross sell into your list of strategic customers, driving growth through expansion and new revenue streams
- Drive deal strategy and commercial negotiations for large, complex renewals
- Develop relationships with executive stakeholders within your book of business, deeply understanding problems they are solving and helping drive to solutions
- Be responsible for account mapping and coordinating effective meetings with the appropriate external stakeholders expanding the customer relationship
- Lead and contribute to team projects to develop and refine our sales process and help shape the Stripe sales culture
Requirements
- 8+ years of sales experience, preferably selling a technical product, with a track record of top performance
- 5+ years leading complex sales cycles with Enterprise organizations required
- Ability to understand technical requirements and craft solutions across multiple products
- Ability to develop and execute account plans spanning multiple business units across complex organizations
- A knack for working well with a wide range of people, both internally and externally
- Strong presentation skills, particularly for in-person meetings with multiple stakeholders
- Proven ability to lead complex negotiations involving bespoke commercial agreements
- Superior verbal
for prose. We must not repeat job title as heading. The job title is "Account Executive, Existing Business". Not to be used as heading. We must not put Job ID/requisition numbers as headings (none present). We must preserve all substantive info. Let's extract substantive content: Intro paragraph: "Who we are About Stripe Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world’s largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities. Our mission is to increase the GDP of the internet, and we have a staggering amount of work ahead. That means you have an unprecedented opportunity to put the global economy within everyone’s reach while doing the most important work of your career." That's about company; could be placed under a heading like "About the role"? Actually "About the role" is more about the role, but we could use "About Stripe" as heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict list; we can use those headings if appropriate. We could use "About the role" for company overview? Might be okay. Or we could skip a heading and just put paragraph? But they want sections when posting has real specific content. The intro is substantive; we could put under About the role
and then a
. Next: "What you’ll do As an Account Executive, Existing Business, you’ll be managing existing relationships and identifying new opportunities to expand Stripe’s footprint within existing accounts. Specifically, we’re looking for someone who can execute on long-term sales strategies, engage with internal and external stakeholders, align on technical and business requirements with product teams, build value in competitive situations, lead commercial negotiations, and close deals." That's a prose description; could be under "About the role" as well, but we already used that. Maybe better to have "About the role" for company intro, and "What you’ll do" could be under "Responsibilities"? Actually responsibilities section follows. Next we have a heading "Responsibilities" then a list of bullet points (though not formatted as bullet list in text but each line starts with a verb). We need to convert to
- .
Responsibilities content:
- Work with existing Stripe customers to develop and execute long-term sales strategies to expand Stripe’s revenue
- Own the full sales cycle, from business case development, to deal structuring and negotiating, to close
- Develop account plans and cross sell into your list of strategic customers, driving growth through expansion and new revenue streams
- Drive deal strategy and commercial negotiations for large, complex renewals
- Develop relationships with executive stakeholders within your book of business, deeply understanding problems they are solving and helping drive to solutions
- Be responsible for account mapping and coordinating effective meetings with the appropriate external stakeholders expanding the customer relationship
- Lead and contribute to team projects to develop and refine our sales process and help shape the Stripe sales culture
Next: "Who you are We’re looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply."
That's intro to requirements.
Then "Minimum Requirements" heading and list:
- 8+ years of sales experience, preferably selling a technical product, with a track record of top performance
- 5+ years leading complex sales cycles with Enterprise organizations required
- Ability to understand technical requirements and craft solutions across multiple products
- Ability to develop and execute account plans spanning multiple business units across complex organizations
- A knack for working well with a wide range of people, both internally and externally
- Strong presentation skills, particularly for in-person meetings with multiple stakeholders
- Proven ability to lead complex negotiations involving bespoke commercial agreements
- Superior verbal and written communication skills
- Ability to operate in a highly ambiguous and fast-paced environment
- Strong interest in technology and a deep understanding of the space
Next: "In office locations include: San Francisco & New York"
Then "In-office expectations" paragraph describing expectations.
We could treat location and expectations under "Schedule" heading (since it's about in-office expectations). Or we could have a "Location" heading but not in examples. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use Schedule for location/in-office expectations. Thus we can have
Schedule
with content: In office locations include: San Francisco & New York. In-office expectations Office-assigned Stripes in most of our locations are currently expected to spend at least 50% of the time in a given month in their local office or with users. This expectation may vary depending on role, team and location. For example, Stripes in Stripe Delivery Center roles in Mexico City, Mexico, Bengaluru, India, and Dublin, Ireland work 100% from the office. Also, some teams have greater in-office attendance requirements, to appropriately support our users and workflows, which the hiring manager will discuss. This approach helps strike a balance between bringing people together for in-person collaboration and learning from each other, while supporting flexibility when possible. We need to preserve all that. Next: "Pay and benefits" heading with paragraph: The annual US base salary range for this role is $262,900 - $394,300. For sales roles, the range provided is the role’s On Target Earnings ("OTE") range, meaning that the range includes both the sales commissions/sales bonuses target and annual base salary for the role. This salary range may be inclusive of several career levels at Stripe and will be narrowed during the interview process based on a number of factors, including the candidate’s experience, qualifications, and location. Applicants interested in this role and who are not located in the US may request the annual salary range for their location during the interview process. Then "Additional benefits for this role may include: equity, company bonus or sales commissions/bonuses; 401(k) plan; medical, dental, and vision benefits; and wellness stipends." We could combine Pay and Benefits sections: maybePay
for salary range, andBenefits
for additional benefits. Or we could have one Benefits section that includes both pay and benefits. The instruction says use headings like Benefits, Pay, Schedule. So we can split. Thus:Pay
... salary range ...
Benefits
- equity
- company bonus or sales commissions/bonuses
- 401(k) plan
- medical, dental, and vision benefits
- wellness stipends
Requirements
with list. We could also have "Qualifications" but we already have Requirements; we can stick to Requirements. We need to avoid empty sections. Let's draft:About the role
Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world’s largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities. Our mission is to increase the GDP of the internet, and we have a staggering amount of work ahead. That means you have an unprecedented opportunity to put the global economy within everyone’s reach while doing the most important work of your career.
As an Account Executive, Existing Business, you’ll be managing existing relationships and identifying new opportunities to expand Stripe’s footprint within existing accounts. Specifically, we’re looking for someone who can execute on long-term sales strategies, engage with internal and external stakeholders, align on technical and business requirements with product teams, build value in competitive situations, lead commercial negotiations, and close deals.
Responsibilities
- Work with existing Stripe customers to develop and execute long-term sales strategies to expand Stripe’s revenue
- Own the full sales cycle, from business case development, to deal structuring and negotiating, to close
- Develop account plans and cross sell into your list of strategic customers, driving growth through expansion and new revenue streams
- Drive deal strategy and commercial negotiations for large, complex renewals
- Develop relationships with executive stakeholders within your book of business, deeply understanding problems they are solving and helping drive to solutions
- Be responsible for account mapping and coordinating effective meetings with the appropriate external stakeholders expanding the customer relationship
- Lead and contribute to team projects to develop and refine our sales process and help shape the Stripe sales culture
Requirements
- 8+ years of sales experience, preferably selling a technical product, with a track record of top performance
- 5+ years leading complex sales cycles with Enterprise organizations required
- Ability to understand technical requirements and craft solutions across multiple products
- Ability to develop and execute account plans spanning multiple business units across complex organizations
- A knack for working well with a wide range of people, both internally and externally
- Strong presentation skills, particularly for in-person meetings with multiple stakeholders
- Proven ability to lead complex negotiations involving bespoke commercial agreements
- Superior verbal