Senior Product Manager -Tech
- for any list of duties/requirements/benefits". So we can make a Skills section with list items extracted from those sentences. That seems acceptable as it's not inventing.
But we must be careful not to create placeholder text. We'll include concrete items.
Now structure:
About the role
with paragraph(s) summarizing the role description (the initial paragraphs). Must preserve all substantive info; we can't omit details. We need to keep all substantive information from the posting. That's a lot. We need to include everything except boilerplate. So we need to include the description about Amazon EC2, the team, etc. We'll need to paraphrase? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details, but we can rephrase? It says do NOT summarize away detail. So we should keep the details, maybe keep them as is, but we can format into HTML. We can copy the sentences intotags. That's preserving detail. Thus we will output sections with
containing the relevant text, possibly broken into multiple paragraphs for readability. We must not include duplicated lines. We'll need to deduplicate repeated sentences. Let's extract substantive content: From description: - "Amazon EC2 (Elastic Compute Cloud) is looking for a dynamic and seasoned product leader to help define and build the future of cloud computing." - "Customers around the world rely on Amazon EC2 to provide elastic, high performance, secure, and cost effective resources to scale their infrastructure to keep up with their changing business needs." - "Within EC2, you will work with a team that delivers one of the broadest portfolio of compute products and services in the cloud, with diverse global customers ranging from startups to well-known Fortune 100 enterprises." - "As a member of the broader EC2 Product Management team, you'll join other highly respected product and engineering leaders to create the future of the computing platform." - "We are looking for a Product manager who will own and drive product management across a range of EC2 products across compute, storage, network and accelerated computing." - "You will be responsible for full lifecycle product management of compute solutions that have an outsized impact on accelerating digital transformation across several customer workloads including AI/ML, generative AI, databases, Big Data analytics, SAP, HPC, Edge, and more." - "This is a unique opportunity to innovate across all layers of the solution stack (ranging from end customer applications all the way down to the core infrastructure including AWS custom chips spanning Nitro and Graviton)." - "You will have strong ownership over portfolio strategy, product definition, feature prioritization, messaging, pricing, adoption, customer interaction, sales enablement, and team development." - "This is a high visibility and high impact role that will interact with all levels of AWS leadership." - "The ideal candidate is excited about the incredible opportunity cloud computing represents and is deeply passionate about working with great teams that deliver the highest quality services." - "You are naturally customer centric and thrive in a fast-paced environment that requires strong technical and business judgment and solid communication skills." Then "Key job responsibilities" heading (but we will not repeat heading as h3? Actually we need to use
for section headings like Responsibilities. So we will have
Responsibilities
and then list. Responsibilities list: - "Lead the definition and execution of the product strategy for the EC2 core compute platforms" - "Define and gather the necessary inputs to make high-quality product and roadmap decisions." - "Work with leaders across AWS, Amazon, and our partners to drive towards our vision." - "Define project requirements, priorities, methods for measurement and track their execution and success." - "Communicate with senior management on project status, strategy, risks, and issues." - "Work closely with multiple engineering teams and designers to deliver results to customer." Then "About The Team" paragraph: - "Our team is dedicated to supporting new members. We have a broad mix of experience levels and tenures, and we’re building an environment that celebrates knowledge sharing and mentorship." - "Our senior members enjoy one-on-one mentoring and thorough." (This sentence seems incomplete; maybe it's a copy error. We'll keep as is? It says "Our senior members enjoy one-on-one mentoring and thorough." That's weird; maybe it's truncated. We'll keep it as is because we must preserve substantive info; but it's incomplete. However it's from posting; we should keep it. Might be a mistake but we keep.) - "We care about your career growth and strive to assign projects based on what will help each team member develop into a better-rounded product manager and enable them to take on more complex tasks in the future." Then "Basic Qualifications" list: - "5+ years of technical product management with internet business experience" - "5+ years of working as a Technical Product Manager experience" (duplicate? Actually first is "5+ years of technical product management with internet business experience", second is "5+ years of working as a Technical Product Manager experience". We'll keep both but note duplication? Might be duplicate; we can deduplicate by merging? But instruction says do NOT put duplicated lines. So we should remove duplicate similar lines. The two are slightly different but essentially same. We'll keep one: "5+ years of technical product management with internet business experience". The second is redundant; we can drop. - "3+ years of technical (software development, network development, IT, other related) experience" - "Experience in taking a product from conception & definition phase through engineering design and taking it to market" - "Experience delivering large-scale SaaS, PaaS or LaaS products where you are responsible for the full product lifecycle, from concept through GTM (go to market)" Then "Preferred Qualifications" list: - "Knowledge of engineering practices and patterns for the full software/hardware/networks development life cycle, including coding standards, code reviews, source control management, build processes, testing, certification, and livesite operations" - "Experience working within teams delivering software products and features using agile methodologies" Then benefits and 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." - Then two salary lines: - "USA, CA, SANTA CLARA - 175,000.00 - 236,800.00 USD annually" - "USA, WA, Seattle - 152,200.00 - 205,900.00 USD annually" - Then benefits description: "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. Learn more about our benefits at https://amazon.jobs/en/benefits." We should not include the link? It's part of benefits description; we can keep as plain text. We must not include boilerplate like EEO, Los Angeles County applicants, etc. Also not include "Company - Amazon Development Center U.S., Inc." maybe that's metadata; we can drop as minor metadata. Also Job ID. We also must not include "If you have a disability..." etc. Now we need to decide sections: - About the role: combine the initial descriptive paragraphs (maybe up to before "Key job responsibilities"). - Responsibilities: list. - Requirements: maybe Basic Qualifications. - Qualifications: Preferred Qualifications. - Skills: we could extract from description about customer centric, technical and business judgment, communication skills, etc. But we already have many details in About the role and Responsibilities. Might be redundant. The instruction says prefer a few substantive sections over many thin ones. So maybe we skip Skills section if not explicitly listed. However there is no explicit Skills heading; but we could still create a Skills section if we have concrete items. But we risk creating a thin section. Let's see if we have enough concrete skill items: "customer centric", "fast-paced environment", "strong technical and business judgment", "solid communication skills", "dynamic and seasoned product leader", "strong ownership over portfolio strategy, product definition, feature prioritization, messaging, pricing, adoption, customer interaction, sales enablement, and team development". Those are more responsibilities/qualifications. Might be better to incorporate them into About the role or Responsibilities. Since we already have About the role covering the role description, we can keep Skills omitted. Thus sections: About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay. We must not include Schedule. Now format:About the role
Amazon EC2 (Elastic Compute Cloud) is looking for a dynamic and seasoned product leader to help define and build the future of cloud computing. Customers around the world rely on Amazon EC2 to provide elastic, high performance, secure, and cost effective resources to scale their infrastructure to keep up with their changing business needs. Within EC2, you will work with a team that delivers one of the broadest portfolio of compute products and services in the cloud, with diverse global customers ranging from startups to well-known Fortune 100 enterprises. As