Senior Engagement Manager, Worldwide Public Sector Professional Services, State and Local Government & Education
Amazon Web Services (AWS) · Herndon, VA · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections: About the role (maybe from description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We must not repeat job title as heading. No Job ID.
We need to extract content.
Let's parse the description.
First paragraph: "AWS Engagement Managers seek to understand our customers’ needs, their missions, how success is defined, and ensure that we are exceeding expectations in developing and delivering solutions. As an Engagement Manager, you will collaborate across roles to understand a customer’s mission objectives and define project goals. You will lead peers, small teams, or groups of teams made up of AWS members, customer Stakeholders/SMEs, and potentially other vendors to create and execute a plan to achieve project goals by understanding AWS technologies, best practices, as well as the client environment. You will identify and mitigate limitations to execution. You will guide customers through their cloud journey to transform their business. You will leverage AWS mechanisms to help customers envision strategic goals and requirements. You will use agile delivery methodology to lead project teams consisting of business and technical resources while managing scope, schedule, and cost. You will use your management and leadership capabilities to successfully execute project plans, remain sensitive to customer needs, resolve issues, escalate when appropriate. You will work to exceed customer expectations by enabling stakeholder capabilities and increasing cloud adoption."
That's about role. Could be "About the role" section.
Then "Key job responsibilities" heading then bullet list? Actually after that there is paragraph: "Work with State Local Government and Education customers to help them envision transformational cloud initiatives. Deliver deliver business objectives by managing a matrixed team across multi-stream, agile, technical engagements for customers. Plan, organize, and manage all phases of a project lifecycle to ensure successful delivery. This includes capturing and validating requirements, developing and managing project governance plans, project schedules and milestones, budgets, team goals, and defining success criteria. Ensure goal alignment across stakeholder groups which may include customers, internal teams, and partners. Create and deliver communication tailored to the audience, ranging from executive level project updates to detailed sprint plans and financial reports. You will apply judgement and tact to challenge, recommend, and redirect teams as well as manage client expectations during the engagement. You are a strategic thinker who can demonstrate understanding of requirements, foresee risks, make decisions guided by policies, procedures and a business plan with limited guidance. This is a customer-facing role, required to travel to client locations and deliver professional services as needed."
That's responsibilities.
Then "About The Team About AWS" etc. That's generic fluff; we need to remove boilerplate like EEO, etc. The "About The Team About AWS" includes statements about AWS values, inclusive culture, mentorship, work/life balance. Those could be considered "Benefits"? Actually they are more about culture, not benefits. The instructions: include sections only when posting has real specific content. Benefits: we have benefits described later: "Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave." That's specific benefits. So we should include Benefits section.
Pay: we have salary ranges for multiple locations. That's specific pay info. So include Pay section.
Schedule: not mentioned explicitly. No schedule info. So omit Schedule.
Skills: maybe we can extract from qualifications: technical specialist, design and architecture experience, database experience, serverless distributed solutions, software development with OO language, cloud based solution experience. Also preferred qualifications: degree, AWS certification, knowledge of AWS services, security standards, performance optimization, cost management, communicating technical concepts. Those could be Skills or Requirements. The instructions: Use sections like Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where.
We have "Basic Qualifications" list and "Preferred Qualifications". Those could go under Requirements (basic) and Qualifications (preferred) or Skills. The spec: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (basic qualifications) and Qualifications (preferred qualifications). Skills could be separate if we have skill list not covered. But we could merge skills into Qualifications. However we need to avoid thin sections. Let's see if we have enough for Skills separate: maybe we can extract "Knowledge of AWS services including compute, storage, networking, security, databases, machine learning, and serverless technologies", "Knowledge of security and compliance standards including HIPAA and GDPR", "Experience in performance optimization and cost management for cloud environments", "Experience communicating technical concepts to diverse audiences in pre-sales environments". Those are skills. Could be Skills section.
But we also have "Basic Qualifications" which are years of experience; those are more like Requirements. So we can have Requirements (basic) and Qualifications (preferred) and Skills (specific knowledge). However that may be many sections; but we can combine if needed. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid too many thin sections. Perhaps combine Requirements and Qualifications into one "Requirements" section that includes both basic and preferred? But they ask for separate headings examples; but we can decide to include only those with substantive content. We have substantive content for Basic Qualifications (specific years) and Preferred Qualifications (specific knowledge). That's enough for two sections. Skills could be derived from Preferred Qualifications; maybe we can omit Skills to avoid thinness. But we need to include Skills only if there is real specific content not already covered. Since Preferred Qualifications already list knowledge and experience, we could treat that as Skills. But the heading "Skills" is separate; we could put the knowledge/skills there and move years of experience to Requirements. Let's think.
Better: Use Requirements for basic qualifications (years). Use Skills for the knowledge/experience list (AWS services, security standards, performance optimization, communication). Use Qualifications for preferred qualifications like degree, certification. But the preferred qualifications also include degree and certification plus knowledge etc. Might be overlapping.
Simplify: Use Requirements for basic qualifications (years). Use Qualifications for preferred qualifications (degree, certification, knowledge, experience). Omit Skills section. That yields two sections plus About the role, Responsibilities, Benefits, Pay. That's five sections, substantive.
Check if we have any content for "About the role": yes first paragraph.
Responsibilities: yes.
Benefits: yes.
Pay: yes.
Now we need to format.
We must not include boilerplate like EEO, equal opportunity, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove "About The Team About AWS" etc? That includes culture statements; but we might consider that as part of Benefits? Not exactly. It's more about company culture; but we already have Benefits covering compensation and benefits. The culture statements could be considered part of "About the team" but not requested as a section. Since we don't have a section for culture, we should omit that content. So we will drop the paragraphs about AWS values, inclusive team culture, mentorship, work/life balance, etc. Also drop "Why AWS?" etc.
Also drop "Los Angeles County applicants:" etc (legal). Also drop "If you have a disability..." etc. Also drop "If the country/region you’re applying in isn’t listed..." etc. Also drop "Learn more about our benefits at ..."? That's a link; we can keep benefits description but drop the link? The instruction: remove boilerplate, navigation, legal, EEO, equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to learn more about benefits might be considered application instruction? It's more a reference; but it's not substantive content about benefits; we already listed benefits. So we can drop that sentence.
Also drop "Company - Amazon Web Services, Inc." and "Job ID: A10521957". Also drop location lines? Actually we need Pay section includes salary ranges per location. So we need to keep those lines.
Now construct HTML.
We'll have:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (basic qualifications) and Qualifications (preferred qualifications). Skills could be separate if we have skill list not covered. But we could merge skills into Qualifications. However we need to avoid thin sections. Let's see if we have enough for Skills separate: maybe we can extract "Knowledge of AWS services including compute, storage, networking, security, databases, machine learning, and serverless technologies", "Knowledge of security and compliance standards including HIPAA and GDPR", "Experience in performance optimization and cost management for cloud environments", "Experience communicating technical concepts to diverse audiences in pre-sales environments". Those are skills. Could be Skills section.
But we also have "Basic Qualifications" which are years of experience; those are more like Requirements. So we can have Requirements (basic) and Qualifications (preferred) and Skills (specific knowledge). However that may be many sections; but we can combine if needed. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid too many thin sections. Perhaps combine Requirements and Qualifications into one "Requirements" section that includes both basic and preferred? But they ask for separate headings examples; but we can decide to include only those with substantive content. We have substantive content for Basic Qualifications (specific years) and Preferred Qualifications (specific knowledge). That's enough for two sections. Skills could be derived from Preferred Qualifications; maybe we can omit Skills to avoid thinness. But we need to include Skills only if there is real specific content not already covered. Since Preferred Qualifications already list knowledge and experience, we could treat that as Skills. But the heading "Skills" is separate; we could put the knowledge/skills there and move years of experience to Requirements. Let's think.
Better: Use Requirements for basic qualifications (years). Use Skills for the knowledge/experience list (AWS services, security standards, performance optimization, communication). Use Qualifications for preferred qualifications like degree, certification. But the preferred qualifications also include degree and certification plus knowledge etc. Might be overlapping.
Simplify: Use Requirements for basic qualifications (years). Use Qualifications for preferred qualifications (degree, certification, knowledge, experience). Omit Skills section. That yields two sections plus About the role, Responsibilities, Benefits, Pay. That's five sections, substantive.
Check if we have any content for "About the role": yes first paragraph.
Responsibilities: yes.
Benefits: yes.
Pay: yes.
Now we need to format.
We must not include boilerplate like EEO, equal opportunity, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove "About The Team About AWS" etc? That includes culture statements; but we might consider that as part of Benefits? Not exactly. It's more about company culture; but we already have Benefits covering compensation and benefits. The culture statements could be considered part of "About the team" but not requested as a section. Since we don't have a section for culture, we should omit that content. So we will drop the paragraphs about AWS values, inclusive team culture, mentorship, work/life balance, etc. Also drop "Why AWS?" etc.
Also drop "Los Angeles County applicants:" etc (legal). Also drop "If you have a disability..." etc. Also drop "If the country/region you’re applying in isn’t listed..." etc. Also drop "Learn more about our benefits at ..."? That's a link; we can keep benefits description but drop the link? The instruction: remove boilerplate, navigation, legal, EEO, equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to learn more about benefits might be considered application instruction? It's more a reference; but it's not substantive content about benefits; we already listed benefits. So we can drop that sentence.
Also drop "Company - Amazon Web Services, Inc." and "Job ID: A10521957". Also drop location lines? Actually we need Pay section includes salary ranges per location. So we need to keep those lines.
Now construct HTML.
We'll have:
About the role
... (the paragraph about AWS Engagement Managers)
Responsibilities
- Work with State Local Government and Education customers to help them envision transformational cloud initiatives.
- Deliver business objectives by managing a matrixed team across multi-stream, agile, technical engagements for customers.
- Plan, organize, and manage all phases of a project lifecycle to ensure successful delivery. This includes capturing and validating requirements, developing and managing project governance plans, project schedules and milestones, budgets, team goals, and defining success criteria.
- Ensure goal alignment across stakeholder groups which may include customers, internal teams, and partners.
- Create and deliver communication tailored to the audience, ranging from executive level project updates to detailed sprint plans and financial reports.
- Apply judgement and tact to challenge, recommend, and redirect teams as well as manage client expectations during the engagement.
- Demonstrate strategic thinking: understand requirements, foresee risks, make decisions guided by policies, procedures and a business plan with limited guidance.
- Act as a customer-facing role, required to travel to client locations and deliver professional services as needed.
Requirements
- 7+ years of technical specialist, design and architecture experience
- 5+ years of database (e.g. SQL, NoSQL, Hadoop, Spark, Kafka, Kinesis) experience
- 7+ years of consulting, design and implementation of serverless distributed solutions experience
- 5+ years of software development with object oriented language experience
- 3+ years of cloud based solution (AWS or equivalent), system, network and operating system experience
Qualifications
- Degree in advanced technology, or AWS Professional level certification
- Knowledge of AWS services including compute, storage, networking, security, databases, machine learning, and serverless technologies
- Knowledge of security and compliance standards including HIPAA and GDPR
- Experience in performance optimization and cost management for cloud environments
- Experience communicating technical concepts to diverse audiences in pre-sales environments
Benefits
- Health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans)
- EAP, Mental Health Support, Medical Advice Line
- Flexible Spending Accounts
- Adoption and Surrogacy Reimbursement coverage
- 401(k) matching
- Paid time off
- Parental leave
Pay
- USA, CA, San Francisco: $176,600.00 - $239,000.00 annually
- USA, NJ, Jersey City: $169,000.00 - $228,600.00 annually
- USA, NY, New York: $169,000.00 - $228,600.00 annually
- USA, TX, Austin: $153,600.00 - $207,800.00 annually