Principal Technical Product Manager, AgentCore
About the role
and thenwith that content (maybe split into paragraphs). Keep all info. Next: "Key job responsibilities Lead Product Definition – Own and drive the customer working backwards strategy, tenets, long-term goals and working backwards documents (press release, FAQ) including customer and market feedback, competitive analysis and business metrics to inform direction. Define Product Vision – Including all aspects to future roadmap, investment, innovation and experimentation. Execution of Product Planning and Development – Including customer goals and business requirements for product release, ensuring implementation is aligned with product goals and requirements, and ownership of product positioning. Lead Product Launch – Own the GTM plan to deliver results that ensure the customer and business goals are met in operational launch plans. Lead Operations – Including monitoring and response to customer feedback, continuous improvement and business growth Lead interaction with Technical Team – Including helping the technical team make tradeoffs based on customer requirements, QA/testing of the product. Business reporting - Track revenue and adoption on a daily basis. Own writing business reports on a weekly and monthly basis and review with leadership." That's responsibilities. Use
- for each bullet. We need to split each responsibility as separate
- . The text includes dash after each heading. We'll parse.
List items:
- Lead Product Definition – Own and drive the customer working backwards strategy, tenets, long-term goals and working backwards documents (press release, FAQ) including customer and market feedback, competitive analysis and business metrics to inform direction.
- Define Product Vision – Including all aspects to future roadmap, investment, innovation and experimentation.
- Execution of Product Planning and Development – Including customer goals and business requirements for product release, ensuring implementation is aligned with product goals and requirements, and ownership of product positioning.
- Lead Product Launch – Own the GTM plan to deliver results that ensure the customer and business goals are met in operational launch plans.
- Lead Operations – Including monitoring and response to customer feedback, continuous improvement and business growth
- Lead interaction with Technical Team – Including helping the technical team make tradeoffs based on customer requirements, QA/testing of the product.
- Business reporting - Track revenue and adoption on a daily basis. Own writing business reports on a weekly and monthly basis and review with leadership.
We'll output
Responsibilities
then- with those
- .
Next: "About The Team Amazon Bedrock AgentCore enables developers to deploy and operate highly capable AI agents securely, at scale. It offers infrastructure purpose-built for dynamic agent workloads, tools to enhance agents, and essential controls for real-world deployment. AgentCore services can be used together or independently and work with any framework including CrewAI, LangGraph, LlamaIndex, and Strands Agents, as well as any foundation model in or outside of Amazon Bedrock, giving you ultimate flexibility. AgentCore eliminates the undifferentiated heavy lifting of building specialized agent infrastructure, so you can accelerate agents to production."
That could be part of About the role or maybe a separate section like "About the Team". The instructions only list certain headings; we can include "About the Team" only if it's one of the allowed headings? The allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the Team" is not listed, so we should not create a heading for it. Instead we could incorporate that content into About the role section (since it's about the team). But we must not invent headings. So we can merge that paragraph into About the role
. However we already have About the role content; we can add this as additional paragraph. Next: "Basic Qualifications 7+ years of working as a Technical Product Manager experience 5+ years of technical (software development, network development, IT, other related) experience 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) Preferred Qualifications Experience developing, deploying and managing AI products at scale" We need to separate Requirements and Qualifications sections. The instructions: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have Requirements and Qualifications separate. We have "Basic Qualifications" and "Preferred Qualifications". Usually Basic Qualifications are requirements. Preferred Qualifications are qualifications (or skills). We'll treat Basic Qualifications as Requirements, Preferred Qualifications as Qualifications (or maybe Skills). But we also have Skills section separate. The posting didn't list explicit skills beyond those. We could put Preferred Qualifications under Qualifications. If we have no explicit Skills, we may omit Skills section. Thus:
Requirements
- 7+ years of working as a Technical Product Manager experience
- 5+ years of technical (software development, network development, IT, other related) experience
- 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)
Qualifications
- Experience developing, deploying and managing AI products at scale
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
- Sign-on payments and restricted stock units (RSUs)
- for any list of duties/requirements/benefits. So we should list benefits as items. The link maybe not needed. Pay: The posting includes multiple location salary ranges. We need to include Pay section with those ranges. Should we list each location as separate
- ? Probably yes.
Thus:
Pay
- USA, CA, Santa Clara: $208,300.00 - $281,800.00 USD annually
- USA, NY, New York City: $199,200.00 - $269,500.00 USD annually
- USA, WA, Seattle: $181,100.00 - $245,000.00 USD annually
or drop. Since it's not required, we can drop it. Now we need to output only HTML fragment, no /, no markdown fences. Thus final HTML:
About the role
In this role, you will be owning one or more products that are in production and getting in on the ground floor of new projects to bring Agentic AI to more developers worldwide. You will be responsible for revenue and adoption of the services. You'll use your passion for technology and solving customer problems to develop and drive product plans to develop an exciting offering for customers. As a Principal Technical Product Manager, you will be part of the larger product leadership community at AWS. This community plays a critical role in the broad business planning, working closely with senior management to develop business targets and resource requirements, influences our long-term technical and business strategy, helps us hire talented team of PMs and ultimately enables us to deliver innovative new solutions rapidly. You will be seen as the subject matter expert for your area of focus within AWS Agentic AI services. A successful candidate will bring a passion for technology services, strong business acumen and judgment, proven experience of launching products and building business around them, ability to define innovative, ground breaking products, desire to have an industry wide impact and ability to work within a fast moving environment in a large company to rapidly deliver services that have a broad business impact. You will manage and be responsible for understanding customer needs and delivering some of our most strategic technical projects, and have a significant bottom-line impact on our business and competitive position. Amazon Bedrock AgentCore enables developers to deploy and operate highly capable AI agents securely, at scale. It offers infrastructure purpose-built for dynamic agent workloads, tools to enhance agents, and essential controls for real-world deployment. AgentCore services can be used together or independently and work with any framework including CrewAI, LangGraph, LlamaIndex, and Strands Agents, as well as any foundation model in or outside of Amazon Bedrock, giving you ultimate flexibility. AgentCore eliminates the undifferentiated heavy lifting of building specialized agent infrastructure, so you can accelerate agents to production.
Responsibilities
- .
Next: "About The Team Amazon Bedrock AgentCore enables developers to deploy and operate highly capable AI agents securely, at scale. It offers infrastructure purpose-built for dynamic agent workloads, tools to enhance agents, and essential controls for real-world deployment. AgentCore services can be used together or independently and work with any framework including CrewAI, LangGraph, LlamaIndex, and Strands Agents, as well as any foundation model in or outside of Amazon Bedrock, giving you ultimate flexibility. AgentCore eliminates the undifferentiated heavy lifting of building specialized agent infrastructure, so you can accelerate agents to production."
That could be part of About the role or maybe a separate section like "About the Team". The instructions only list certain headings; we can include "About the Team" only if it's one of the allowed headings? The allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the Team" is not listed, so we should not create a heading for it. Instead we could incorporate that content into About the role section (since it's about the team). But we must not invent headings. So we can merge that paragraph into About the role