Sr. Account Executive - Amazon Business , Commercial Sector - Corporate Team
Amazon · Austin, TX · 2 wk ago
Advertising$60/hrFull-time
We need to output HTML fragment with sections: About the role? The description includes "Description" paragraph, then "Key job responsibilities", "A day in the life", "About The Team", "Basic Qualifications", "Preferred Qualifications". Also pay info: base salary range listed for multiple locations. Also benefits description. Also maybe "Benefits" section. Also "Pay" section. Also "Schedule"? Not present. So we include sections where content exists.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, accommodation, etc. Remove duplicated lines. Remove application instructions. Remove cookie/navigation/legal etc.
We need to preserve all substantive info. So we need to include description paragraph, responsibilities list, day in the life list? Actually "A day in the life" is prose with bullet-like sentences. Could be
. Could also be
- if list. The text: "A day in the life 2+ customer facing meetings/day to support with any and all account related questions, while uncovering opportunities to grow our partnership. Responding to emails and following up on support tickets on behalf of our customers. Heavy prospecting (phone, email, social media platforms) with the goal to book meetings to pitch AB as a solution for procurement needs." That's a paragraph; we can put as
. About The Team: paragraph. Basic Qualifications: list of items. Should be
- .
Preferred Qualifications: list.
Pay: we have base salary ranges for multiple locations. Should we include as
- each location? Or a paragraph summarizing. The instruction: include Pay section only if posting actually states them. Yes. So we create
Pay
then maybe- each location line.
Benefits: there is a paragraph describing benefits. So include
Benefits
with. We should not include sections like Schedule (none). Also not include "Qualifications" separate? We have Basic and Preferred; could combine but better separate as they are distinct headings. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use others if appropriate. We have "Basic Qualifications" and "Preferred Qualifications". Could map to "Qualifications" heading with sub? But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should use those headings when applicable. So we need to map content to those headings. Let's see: - About the role: could include description paragraph. - Responsibilities: key job responsibilities + day in the life? Could combine. - Requirements: maybe basic qualifications. - Qualifications: maybe preferred qualifications? Or skills? Hmm. - Skills: maybe not present. - Benefits: benefits. - Pay: pay. - Schedule: none. We need to decide mapping. The instruction: "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 they match content. Probably safest to use those exact headings where we have content. Thus:
About the role
description paragraph
Responsibilities
- ... from Key job responsibilities and day in the life? Might combine both.
Requirements
- Basic Qualifications
Qualifications
- Preferred Qualifications Benefits
- each location line
- each location line
- High activity and strategic prospecting into decision makers within territory to drive discovery meetings and identify selling opportunities
- Deliver accurate weekly reporting on pipeline and customer spend adoption, including account status updates and insights learned during deployment
- Provide strategic account engagement that helps customers implement solutions that solve industry-specific procurement challenges
- Drive and accelerate spend adoption by advising customers on best practices for using Amazon Business solutions
- Focus on
benefits paragraph
Pay:Pay
The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location.
thenAbout the role
Come be a part of a rapidly expanding $60 billion-dollar global business. At Amazon Business, a fast-growing startup passionate about building solutions, we set out every day to innovate and disrupt the status quo. We stand at the intersection of tech & retail in the B2B space developing innovative purchasing and procurement solutions to help businesses and organizations thrive. At Amazon Business, we strive to be the most recognized and preferred strategic partner for smart business buying. Bring your insight, imagination and a healthy disregard for the impossible. Join us in building and celebrating the value of Amazon Business to buyers and sellers of all sizes and industries. Unlock your career potential.
Responsibilities
- each location line.
Benefits: there is a paragraph describing benefits. So include
- each location? Or a paragraph summarizing. The instruction: include Pay section only if posting actually states them. Yes. So we create
- .
Preferred Qualifications: list.
Pay: we have base salary ranges for multiple locations. Should we include as