Product Manager II - Agentic Platform
Toshiba Global Commerce Solutions · Durham, NC · 3 wk ago
MarketingFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarized away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove EEO statements etc. Also remove generic filler like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting mentions "Toshiba Global Commerce Solutions, Inc. offers a competitive salary and generous benefits package including the following:" then lists benefits. So Benefits section is present. Pay? It says competitive salary but no specific numbers; we should not create Pay section because it's not specific (just "competitive salary" is vague). The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits is stated with list, so include Benefits. Pay not specific enough, so omit Pay section. Schedule not mentioned, omit.
We need sections: About the role (maybe intro paragraph), Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly also "Preferred Qualifications" could go under Qualifications or separate? The instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Qualifications (maybe required) and Preferred Qualifications could be under Qualifications or separate? Probably combine under Qualifications (both required and preferred). But we need to preserve all substantive info; we can include both required and preferred under Qualifications heading with sub-lists? The instruction says use
- for any list of duties/requirements/benefits. So we can have separate lists for Required Skills & Experience and Preferred Qualifications under Qualifications heading.
Also Skills: The posting has "Required Skills & Experience" and also "Preferred Qualifications". There's also a "Skills" section maybe we can include skills like "Ability to write clear product requirements..." etc. Those are under Required Skills & Experience. So we could treat that as Skills section. But we already have Required Skills & Experience; maybe we map that to Skills heading. However the instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. So we need to decide mapping.
We have content:
- Intro paragraph about role: "Toshiba Global Commerce Solutions is seeking a Product Manager to help unify and scale our agentic AI platform..." That's about the role.
- "What Success Looks Like" paragraph: could be part of About the role or separate? Could be included in About the role.
- "Key Responsibilities" list: bullet points.
- "Required Skills & Experience" list: bullet points.
- "Preferred Qualifications" list: bullet points.
- Benefits list.
Thus we can map:
About the role: intro + What Success Looks Like.
Responsibilities: Key Responsibilities.
Requirements: maybe we treat Required Skills & Experience as Requirements? But there is also a "Requirements" heading expected. Could put Required Skills & Experience under Requirements.
Qualifications: Preferred Qualifications under Qualifications.
Skills: maybe we could split out some skill-specific items from Required Skills & Experience into Skills, but that would duplicate. Better to put Required Skills & Experience under Skills heading, and Requirements maybe empty? But we must not create empty sections. So we need to decide which headings to include based on actual content.
We have content for: About the role, Responsibilities, Required Skills & Experience, Preferred Qualifications, Benefits.
We could map:
- About the role: intro + success.
- Responsibilities: Key Responsibilities.
- Requirements: Required Skills & Experience (makes sense as requirements).
- Qualifications: Preferred Qualifications.
- Skills: maybe we could extract specific skill bullets from Required Skills & Experience? But that would be splitting; we could also omit Skills section if we don't have distinct skill list beyond requirements. However the instruction says prefer a few substantive sections over many thin ones. So we could omit Skills if not needed. But we have to include sections only when posting has real specific content for it. If we don't have a distinct Skills section, we omit it.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits.
Check if any content for Pay or Schedule: none, omit.
Now we need to format.
Use
for each section heading. Inside each section, use
for prose,
- for lists.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given (or close). Must not omit any detail.
We need to be careful not to include boilerplate like EEO statements, diversity, etc. Also remove duplicated lines, application instructions. The posting includes "Eeo Toshiba Global Commerce Solutions is an equal opportunity/affirmative action employer..." and diversity statements. Remove those.
Also remove lines like "Toshiba Global Commerce Solutions, Inc. offers a competitive salary and generous benefits package including the following:" maybe keep as intro to Benefits section? The benefits list follows. We can keep that sentence as part of Benefits section preamble.
Now let's extract content.
Intro paragraph:
"Toshiba Global Commerce Solutions is seeking a Product Manager to help unify and scale our agentic AI platform, the shared foundation that grounds every solution built on it in two decades of accumulated retail expertise. The near-term work is getting the platform's first capabilities launched and consolidating what exists today onto a common core across intelligence and knowledge services, the developer platform, and the fleet of agents that runs on both. It serves teams across Toshiba and the customers and partners who build on it. This is a build-and-ship role: writing specs, working alongside engineering to get capability out, putting it in front of the teams who use it, and bringing back what you learn. You will work closely with platform and engineering leadership on direction, own turning it into well-defined, shipped work, and supply the evidence from real use that shapes what comes next."
What Success Looks Like paragraph:
"Toshiba's twenty years of retail expertise lives in its products, its architecture, and the judgment behind both. The platform brings that together in one place and puts it to work for anyone who needs it, whether they are building something, answering a question, or delivering for a customer. Success is how far that reaches: engineers shipping faster, expertise available without waiting on the expert, people doing work that used to need a specialist, and customers and partners building on the same foundation."
Key Responsibilities bullet points (as given):
- Own the shared platform backlog across intelligence and knowledge services, the developer platform, and the agent fleet.
- Write clear product requirements and specs, translating business use cases from internal stakeholder teams into actionable work.
- Partner day to day with Engineering/Architecture on platform structure, flagging feasibility issues and trade-offs.
- Support execution of the governance model for agent build, review, and release: registry entries and ownership, risk tiers, human-in-the-loop review, evaluation thresholds, promotion criteria, and the data access and customer data protections that apply at every step.
- Ship the curated workflows, skills, and reference patterns that make the platform faster to use and more reliable in what it produces, along with the onboarding documentation that lets a team get going without the platform team in the room.
- Operate with a builder mindset: use the platform yourself, prototype what you are asking for, and drive adoption directly with the teams rather than only through documentation.
- Close the loop: gather feedback and usage signals from the teams on the platform, turn friction into concrete backlog items, and bring the evidence that informs the roadmap.
- Build the instrumentation and reporting behind the platform's KPIs, so progress is visible to the teams and to leadership: adoption and breadth of use across teams, onboarding time, the share of portal usage that reaches merged and deployed code, developer experience, agent and retrieval quality, and usage cost and attribution.
Required Skills & Experience bullet points:
- Bachelor’s degree with 10+ years of experience, or equivalent combination.
- 5-8 years of product management experience, ideally including some exposure to platform, developer-tools, or infrastructure products.
- Working familiarity with agentic AI concepts (tool use, retrieval/RAG, multi-agent orchestration, agent evaluation) and genuine interest in building deeper hands-on fluency.
- Ability to write clear product requirements and specs, and to prioritize a backlog.
- Enough technical fluency to work day-to-day with engineering on APIs and platform architecture, comfortable asking questions and following trade-off discussions without necessarily driving architecture decisions.
- A builder's instinct: you use the tools you manage, try things yourself before writing the spec, and can show what you mean rather than only describe it.
- Experience supporting an internal-facing product, or a strong interest in internal/platform product work over pure customer-facing feature work.
- Comfortable operating with ambiguity and escalating appropriately rather than needing fully defined requirements.
Preferred Qualifications bullet points:
- Prior exposure to RAG, LLM-based assistants, or agent frameworks in a shipped product.
- Familiarity with evaluation, tracing, or observability for LLM and agent systems.
- Familiarity with DORA metrics or platform-engineering measurement concepts (deployment frequency, lead time, developer satisfaction/NPS).
- Experience instrumenting a shared service and building the reporting people actually use.
- Experience with a platform serving both internal teams and external customers: multi-tenancy, self-service onboarding, packaging, or support-model work.
- Exposure to usage metering, cost attribution, or internal chargeback for a shared service.
- Experience in retail technology or another vertical with SaaS/on-prem hybrid constraints.
- Exposure to working with Legal/Compliance on data-rights or AI risk questions.
- Experience supporting an internal tool or platform used by other teams rather than end customers.
Benefits list (after "Toshiba Global Commerce Solutions, Inc. offers a competitive salary and generous benefits package including the following:"):
- Group health coverage (medical, dental, & vision)
- Employee Assistance Programs
- Pre-tax spending accounts
- 401(k) plan (with company match)
- Company provided life insurance
- Pet Insurance
- Employee discounts
- Generous paid holiday schedule, paid vacation & sick/personal days
We should keep that sentence as preamble maybe in a
before the list. Now we need to output HTML fragment only. We'll produce:
About the role
... intro ...
... What Success Looks Like ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
Toshiba Global Commerce Solutions, Inc. offers a competitive salary and generous benefits package including the following:
- ... ...
- for lists.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given (or close). Must not omit any detail.
We need to be careful not to include boilerplate like EEO statements, diversity, etc. Also remove duplicated lines, application instructions. The posting includes "Eeo Toshiba Global Commerce Solutions is an equal opportunity/affirmative action employer..." and diversity statements. Remove those.
Also remove lines like "Toshiba Global Commerce Solutions, Inc. offers a competitive salary and generous benefits package including the following:" maybe keep as intro to Benefits section? The benefits list follows. We can keep that sentence as part of Benefits section preamble.
Now let's extract content.
Intro paragraph:
"Toshiba Global Commerce Solutions is seeking a Product Manager to help unify and scale our agentic AI platform, the shared foundation that grounds every solution built on it in two decades of accumulated retail expertise. The near-term work is getting the platform's first capabilities launched and consolidating what exists today onto a common core across intelligence and knowledge services, the developer platform, and the fleet of agents that runs on both. It serves teams across Toshiba and the customers and partners who build on it. This is a build-and-ship role: writing specs, working alongside engineering to get capability out, putting it in front of the teams who use it, and bringing back what you learn. You will work closely with platform and engineering leadership on direction, own turning it into well-defined, shipped work, and supply the evidence from real use that shapes what comes next."
What Success Looks Like paragraph:
"Toshiba's twenty years of retail expertise lives in its products, its architecture, and the judgment behind both. The platform brings that together in one place and puts it to work for anyone who needs it, whether they are building something, answering a question, or delivering for a customer. Success is how far that reaches: engineers shipping faster, expertise available without waiting on the expert, people doing work that used to need a specialist, and customers and partners building on the same foundation."
Key Responsibilities bullet points (as given):
- Own the shared platform backlog across intelligence and knowledge services, the developer platform, and the agent fleet.
- Write clear product requirements and specs, translating business use cases from internal stakeholder teams into actionable work.
- Partner day to day with Engineering/Architecture on platform structure, flagging feasibility issues and trade-offs.
- Support execution of the governance model for agent build, review, and release: registry entries and ownership, risk tiers, human-in-the-loop review, evaluation thresholds, promotion criteria, and the data access and customer data protections that apply at every step.
- Ship the curated workflows, skills, and reference patterns that make the platform faster to use and more reliable in what it produces, along with the onboarding documentation that lets a team get going without the platform team in the room.
- Operate with a builder mindset: use the platform yourself, prototype what you are asking for, and drive adoption directly with the teams rather than only through documentation.
- Close the loop: gather feedback and usage signals from the teams on the platform, turn friction into concrete backlog items, and bring the evidence that informs the roadmap.
- Build the instrumentation and reporting behind the platform's KPIs, so progress is visible to the teams and to leadership: adoption and breadth of use across teams, onboarding time, the share of portal usage that reaches merged and deployed code, developer experience, agent and retrieval quality, and usage cost and attribution.
Required Skills & Experience bullet points:
- Bachelor’s degree with 10+ years of experience, or equivalent combination.
- 5-8 years of product management experience, ideally including some exposure to platform, developer-tools, or infrastructure products.
- Working familiarity with agentic AI concepts (tool use, retrieval/RAG, multi-agent orchestration, agent evaluation) and genuine interest in building deeper hands-on fluency.
- Ability to write clear product requirements and specs, and to prioritize a backlog.
- Enough technical fluency to work day-to-day with engineering on APIs and platform architecture, comfortable asking questions and following trade-off discussions without necessarily driving architecture decisions.
- A builder's instinct: you use the tools you manage, try things yourself before writing the spec, and can show what you mean rather than only describe it.
- Experience supporting an internal-facing product, or a strong interest in internal/platform product work over pure customer-facing feature work.
- Comfortable operating with ambiguity and escalating appropriately rather than needing fully defined requirements.
Preferred Qualifications bullet points:
- Prior exposure to RAG, LLM-based assistants, or agent frameworks in a shipped product.
- Familiarity with evaluation, tracing, or observability for LLM and agent systems.
- Familiarity with DORA metrics or platform-engineering measurement concepts (deployment frequency, lead time, developer satisfaction/NPS).
- Experience instrumenting a shared service and building the reporting people actually use.
- Experience with a platform serving both internal teams and external customers: multi-tenancy, self-service onboarding, packaging, or support-model work.
- Exposure to usage metering, cost attribution, or internal chargeback for a shared service.
- Experience in retail technology or another vertical with SaaS/on-prem hybrid constraints.
- Exposure to working with Legal/Compliance on data-rights or AI risk questions.
- Experience supporting an internal tool or platform used by other teams rather than end customers.
Benefits list (after "Toshiba Global Commerce Solutions, Inc. offers a competitive salary and generous benefits package including the following:"):
- Group health coverage (medical, dental, & vision)
- Employee Assistance Programs
- Pre-tax spending accounts
- 401(k) plan (with company match)
- Company provided life insurance
- Pet Insurance
- Employee discounts
- Generous paid holiday schedule, paid vacation & sick/personal days
We should keep that sentence as preamble maybe in a