Solutions Product Marketing Manager
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Preserve all substantive info. Remove boilerplate like cookie/navigation/legal/EEO etc. The posting includes sections: "Our Company", "About The Role", "Who this fits.", "What You’ll Own", "Why This Role", "Qualifications", "Preferred Qualifications", "As required by the equal pay and transparency acts, the expected base salary...", "About Us". Also there is "Our Company" description. We need to decide which sections to include based on content.
We need to include sections only when posting has real specific content. So we can have:
- About the role (maybe combine "About The Role" and "Who this fits." and "What You’ll Own" and "Why This Role"? But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content that maps to responsibilities (What You’ll Own), requirements (Qualifications), preferred qualifications maybe as Skills? Or we could have Skills section for preferred qualifications. Pay section from salary info. Benefits? Not explicit benefits listed besides bonus/variable/commission pay programs. Could include Benefits if there is mention of bonus/variable/commission pay programs. But we need actual content; we can include a Benefits section with that info. Schedule? Not mentioned. So we should not create Schedule section.
We also have "About Us" maybe could be part of About the role? But we could include a separate section? Not in list. Probably we should incorporate into About the role or maybe omit as not required heading. The instruction: use headings for those specific section headings. It doesn't forbid other headings, but says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those.
Thus:
About the role
: include description from "About The Role", "Who this fits.", "What You’ll Own", "Why This Role", maybe also "Our Company"? But "Our Company" is separate but could be part of About the role. We'll include a concise paragraph summarizing role.
Responsibilities: could be the bullet list of what you'll own (domain go-to-market etc). Use - .
Requirements: maybe the Qualifications (mandatory) list.
Skills: maybe Preferred Qualifications.
Pay: include base salary and on-target earnings.
Benefits: mention bonus/variable/commission pay programs.
We must not repeat job title. No metadata.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like bullet points.
Let's extract details.
From posting:
Our Company: description of Hitachi Vantara.
About The Role: paragraph about mission-critical workloads, role owns go-to-market for solutions that help enterprises modernize and manage critical business applications and databases, improve cost and operational performance, strengthen resilience and continuity, meet compliance obligations. Work is translation under pressure: take complex tech and turn into clear market story, differentiated solution narrative, practical tools a seller can use. Done well changes what field leads with, how partners position us, which conversations we get invited into. Structure and scope: report into product marketing leadership, own strategy and execution for Business Applications & Databases domain. Also execute established plans and priority solution plays across Data & Cyber Resilience and Virtualization & Cloud, alongside teammates who own those domains. Cross-domain exposure deliberate; it's how a strong product marketer becomes a go-to-market leader. Who this fits: product marketer with global enterprise B2B experience, strong analytical instincts, confidence to work across product, sales, technical, partner, and marketing teams without waiting to be told what to do next. Fits best if you are the person who asks why we position it that way, goes and gets the customer, analyst, and competitive evidence, and comes back with a better answer — then does it again a quarter later, when the market has moved. Positioning has a shelf life. We are not looking for someone to maintain the current narrative. We are looking for someone to keep sharpening it.
What You’ll Own: bullet list (actually sentences separated by periods). Let's capture each bullet:
- Domain go-to-market. Strategy and execution for Business Applications & Databases: positioning, messaging, target audiences, buyer needs, and the solution narrative. This is yours to define, not to inherit.
- Value propositions that hold up. Translate solution strategy and technical capability into differentiated, outcome-led stories that survive contact with enterprise buyers, sellers, and partners.
- Customer-facing assets that get used. Solution pages, solution profiles, data sheets, sales presentations, and sales tools — accurate, differentiated, and built for how buyers actually evaluate.
- Sales and partner enablement. Assets and readiness that support the buyer journey from awareness through purchase, strengthen field readiness, and activate partners.
- Cross-domain execution. Established go-to-market plans and priority solution plays across Data & Cyber Resilience and Virtualization & Cloud.
- Cross-functional alignment. Work with product, sales, technical, partner, and marketing teams across messaging, content, enablement, campaigns, launches, and solution plays.
- The evidence base. Gather and synthesize customer, market, competitive, analyst, and field input — then use it to sharpen differentiation, validate technical accuracy, and challenge positions that the evidence no longer supports.
- Delivery at pace. Multiple deliverables, stakeholder reviews, and shifting priorities, held to a high bar for quality, consistency, and timeliness.
Why This Role: bullet points (actually sentences). Let's capture:
- You own something real. You will make calls that show up in how a global portfolio goes to market.
- You can change how we do things. Bring a case built on customer, analyst, and competitive evidence and you will get a hearing, whatever the current answer is. The fastest way to earn influence here is to bring the evidence that moves a position forward.
- You build the skill set the market is paying for. Exponential data infrastructure, cloud, AI, and cyber resilience are the categories enterprise buyers are funding, and the ones product marketers are being recruited for. You will develop that fluency here, on real solutions, with real customers.
- Your work reaches buyers whose decisions matter. Regulated industries, mission-critical workloads, and multi-stakeholder buying committees. Sharper positioning, harder proof, higher standard.
- You get coached, not just managed. You will work directly with product marketing leaders who will push your thinking, review your work seriously, and give you the exposure that builds a go-to-market leader.
- There is a path. This role is scoped to grow into broader go-to-market leadership. We hire people we expect to outgrow the job description.
Qualifications: list:
- 3–5 years in product marketing, solutions marketing, product management, technical marketing, or enterprise B2B technology marketing.
- Experience owning or supporting go-to-market strategy and execution — solution launches, campaigns, sales plays, or related commercialization work.
- Proven ability to translate complex technical capability into clear positioning, messaging, value propositions, and customer-facing content.
- Experience building solution-oriented assets and enablement materials: web pages, solution briefs, data sheets, sales presentations, and sales tools.
- Experience supporting sales enablement, partner marketing, channel enablement, or field-readiness programs.
- Experience in a global enterprise technology environment, or supporting complex, multi-stakeholder B2B buying cycles.
- Strong analytical skills. You can read a market, interrogate customer, analyst, and competitive input, and build an evidence-backed case for a position.
- Strong writing and editing, with the judgment to know when a claim needs a proof point behind it.
- Demonstrated ability to work independently and collaborate across product, sales, technical, partner, and marketing stakeholders.
Preferred Qualifications:
- Experience marketing to enterprise technology buyers and influencers across workload, application, or database modernization.
- Familiarity with hybrid cloud, data infrastructure, enterprise data management, data protection, cybersecurity, or governance risk and compliance.
- Experience developing narratives or programs for highly regulated industries.
- Fluency with AI and LLM tools to accelerate research, content development, analysis, and go-to-market workflows.
Pay: "As required by the equal pay and transparency acts, the expected base salary for this position is: $110K to $120K. The expected on-target earnings for this position is: $123K to $134K. The expected pay is determined based on a variety of factors including, but not limited to, depth of experience in the practice area. Employees are eligible to participate in Hitachi Vantara’s bonus/variable/commission pay programs, where applicable, and are subject to the program’s conditions and restrictions."
Benefits: maybe the bonus/variable/commission pay programs count as benefits. Also maybe other benefits not mentioned. We'll include a Benefits section with that sentence.
Schedule: not mentioned, so omit.
Now we need to output HTML fragment only, with
headings and
for prose,
- for lists.
We need to decide which content goes to which section.
About the role: combine the introductory paragraphs (Our Company, About The Role, Who this fits., What You’ll Own, Why This Role?) Actually responsibilities and qualifications are separate. So About the role could be a narrative summary of role purpose and context. We'll include the paragraphs from "Our Company", "About The Role", "Who this fits.", maybe also "Why This Role"? But Why This Role is more about motivations; could be part of About the role or separate. Since we have a Why This Role content, we could put it under About the role as well, but we have no separate heading for Why This Role. Might be okay to include under About the role.
But we also have Responsibilities section: we can put the "What You’ll Own" bullets there.
Requirements: the Qualifications list.
Skills: the Preferred Qualifications list.
Pay: salary info.
Benefits: bonus/variable/commission pay programs.
We must not repeat content. Ensure we preserve all substantive info. Let's check if any info omitted: Our Company description, About The Role paragraph, Who this fits paragraph, What You’ll Own bullets, Why This Role bullets, Qualifications bullets, Preferred Qualifications bullets, Pay paragraph, Bonus info.
We need to ensure we include all.
Let's craft About the role paragraph(s). Could be multiple
under same heading? The instruction: use
for prose. So we can have multiple
elements under the heading.
We'll produce:
About the role
Our CompanyWe're Hitachi Vantara, the data foundation trusted by the world's innovators. Our resilient, high-performance data infrastructure means that customers - from banks to theme parks - can focus on achieving the incredible with data. If you've seen the Las Vegas Sphere, you've seen just one example of how we empower businesses to automate, optimize, innovate - and wow their customers. Right now, we're laying the foundation for our next wave of growth. We're looking for people who love being part of a diverse, global team - and who get excited about making a real-world impact with data.
About The RoleHitachi Vantara’s customers run mission-critical workloads for Fortune 500 enterprises, government agencies, financial institutions, healthcare systems, and critical infrastructure operators. When their business applications and databases are slow, expensive, non-compliant, or unavailable, the consequences are not IT consequences. They are board-level, and in some cases public-safety, consequences. This role owns the go-to-market for the solutions that help enterprises modernize and manage critical business applications and databases, improve cost and operational performance, strengthen resilience and continuity, and meet compliance obligations they increasingly have to prove rather than assert. The work itself is translation under pressure.
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Preserve all substantive info. Remove boilerplate like cookie/navigation/legal/EEO etc. The posting includes sections: "Our Company", "About The Role", "Who this fits.", "What You’ll Own", "Why This Role", "Qualifications", "Preferred Qualifications", "As required by the equal pay and transparency acts, the expected base salary...", "About Us". Also there is "Our Company" description. We need to decide which sections to include based on content. We need to include sections only when posting has real specific content. So we can have: - About the role (maybe combine "About The Role" and "Who this fits." and "What You’ll Own" and "Why This Role"? But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content that maps to responsibilities (What You’ll Own), requirements (Qualifications), preferred qualifications maybe as Skills? Or we could have Skills section for preferred qualifications. Pay section from salary info. Benefits? Not explicit benefits listed besides bonus/variable/commission pay programs. Could include Benefits if there is mention of bonus/variable/commission pay programs. But we need actual content; we can include a Benefits section with that info. Schedule? Not mentioned. So we should not create Schedule section. We also have "About Us" maybe could be part of About the role? But we could include a separate section? Not in list. Probably we should incorporate into About the role or maybe omit as not required heading. The instruction: use headings for those specific section headings. It doesn't forbid other headings, but says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those.
Thus:
About the role
: include description from "About The Role", "Who this fits.", "What You’ll Own", "Why This Role", maybe also "Our Company"? But "Our Company" is separate but could be part of About the role. We'll include a concise paragraph summarizing role.
Responsibilities: could be the bullet list of what you'll own (domain go-to-market etc). Use - .
Requirements: maybe the Qualifications (mandatory) list.
Skills: maybe Preferred Qualifications.
Pay: include base salary and on-target earnings.
Benefits: mention bonus/variable/commission pay programs.
We must not repeat job title. No metadata.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like bullet points.
Let's extract details.
From posting:
Our Company: description of Hitachi Vantara.
About The Role: paragraph about mission-critical workloads, role owns go-to-market for solutions that help enterprises modernize and manage critical business applications and databases, improve cost and operational performance, strengthen resilience and continuity, meet compliance obligations. Work is translation under pressure: take complex tech and turn into clear market story, differentiated solution narrative, practical tools a seller can use. Done well changes what field leads with, how partners position us, which conversations we get invited into. Structure and scope: report into product marketing leadership, own strategy and execution for Business Applications & Databases domain. Also execute established plans and priority solution plays across Data & Cyber Resilience and Virtualization & Cloud, alongside teammates who own those domains. Cross-domain exposure deliberate; it's how a strong product marketer becomes a go-to-market leader. Who this fits: product marketer with global enterprise B2B experience, strong analytical instincts, confidence to work across product, sales, technical, partner, and marketing teams without waiting to be told what to do next. Fits best if you are the person who asks why we position it that way, goes and gets the customer, analyst, and competitive evidence, and comes back with a better answer — then does it again a quarter later, when the market has moved. Positioning has a shelf life. We are not looking for someone to maintain the current narrative. We are looking for someone to keep sharpening it.
What You’ll Own: bullet list (actually sentences separated by periods). Let's capture each bullet:
- Domain go-to-market. Strategy and execution for Business Applications & Databases: positioning, messaging, target audiences, buyer needs, and the solution narrative. This is yours to define, not to inherit.
- Value propositions that hold up. Translate solution strategy and technical capability into differentiated, outcome-led stories that survive contact with enterprise buyers, sellers, and partners.
- Customer-facing assets that get used. Solution pages, solution profiles, data sheets, sales presentations, and sales tools — accurate, differentiated, and built for how buyers actually evaluate.
- Sales and partner enablement. Assets and readiness that support the buyer journey from awareness through purchase, strengthen field readiness, and activate partners.
- Cross-domain execution. Established go-to-market plans and priority solution plays across Data & Cyber Resilience and Virtualization & Cloud.
- Cross-functional alignment. Work with product, sales, technical, partner, and marketing teams across messaging, content, enablement, campaigns, launches, and solution plays.
- The evidence base. Gather and synthesize customer, market, competitive, analyst, and field input — then use it to sharpen differentiation, validate technical accuracy, and challenge positions that the evidence no longer supports.
- Delivery at pace. Multiple deliverables, stakeholder reviews, and shifting priorities, held to a high bar for quality, consistency, and timeliness.
Why This Role: bullet points (actually sentences). Let's capture:
- You own something real. You will make calls that show up in how a global portfolio goes to market.
- You can change how we do things. Bring a case built on customer, analyst, and competitive evidence and you will get a hearing, whatever the current answer is. The fastest way to earn influence here is to bring the evidence that moves a position forward.
- You build the skill set the market is paying for. Exponential data infrastructure, cloud, AI, and cyber resilience are the categories enterprise buyers are funding, and the ones product marketers are being recruited for. You will develop that fluency here, on real solutions, with real customers.
- Your work reaches buyers whose decisions matter. Regulated industries, mission-critical workloads, and multi-stakeholder buying committees. Sharper positioning, harder proof, higher standard.
- You get coached, not just managed. You will work directly with product marketing leaders who will push your thinking, review your work seriously, and give you the exposure that builds a go-to-market leader.
- There is a path. This role is scoped to grow into broader go-to-market leadership. We hire people we expect to outgrow the job description.
Qualifications: list:
- 3–5 years in product marketing, solutions marketing, product management, technical marketing, or enterprise B2B technology marketing.
- Experience owning or supporting go-to-market strategy and execution — solution launches, campaigns, sales plays, or related commercialization work.
- Proven ability to translate complex technical capability into clear positioning, messaging, value propositions, and customer-facing content.
- Experience building solution-oriented assets and enablement materials: web pages, solution briefs, data sheets, sales presentations, and sales tools.
- Experience supporting sales enablement, partner marketing, channel enablement, or field-readiness programs.
- Experience in a global enterprise technology environment, or supporting complex, multi-stakeholder B2B buying cycles.
- Strong analytical skills. You can read a market, interrogate customer, analyst, and competitive input, and build an evidence-backed case for a position.
- Strong writing and editing, with the judgment to know when a claim needs a proof point behind it.
- Demonstrated ability to work independently and collaborate across product, sales, technical, partner, and marketing stakeholders.
Preferred Qualifications:
- Experience marketing to enterprise technology buyers and influencers across workload, application, or database modernization.
- Familiarity with hybrid cloud, data infrastructure, enterprise data management, data protection, cybersecurity, or governance risk and compliance.
- Experience developing narratives or programs for highly regulated industries.
- Fluency with AI and LLM tools to accelerate research, content development, analysis, and go-to-market workflows.
Pay: "As required by the equal pay and transparency acts, the expected base salary for this position is: $110K to $120K. The expected on-target earnings for this position is: $123K to $134K. The expected pay is determined based on a variety of factors including, but not limited to, depth of experience in the practice area. Employees are eligible to participate in Hitachi Vantara’s bonus/variable/commission pay programs, where applicable, and are subject to the program’s conditions and restrictions."
Benefits: maybe the bonus/variable/commission pay programs count as benefits. Also maybe other benefits not mentioned. We'll include a Benefits section with that sentence.
Schedule: not mentioned, so omit.
Now we need to output HTML fragment only, with
headings and
for prose,
- for lists.
We need to decide which content goes to which section.
About the role: combine the introductory paragraphs (Our Company, About The Role, Who this fits., What You’ll Own, Why This Role?) Actually responsibilities and qualifications are separate. So About the role could be a narrative summary of role purpose and context. We'll include the paragraphs from "Our Company", "About The Role", "Who this fits.", maybe also "Why This Role"? But Why This Role is more about motivations; could be part of About the role or separate. Since we have a Why This Role content, we could put it under About the role as well, but we have no separate heading for Why This Role. Might be okay to include under About the role.
But we also have Responsibilities section: we can put the "What You’ll Own" bullets there.
Requirements: the Qualifications list.
Skills: the Preferred Qualifications list.
Pay: salary info.
Benefits: bonus/variable/commission pay programs.
We must not repeat content. Ensure we preserve all substantive info. Let's check if any info omitted: Our Company description, About The Role paragraph, Who this fits paragraph, What You’ll Own bullets, Why This Role bullets, Qualifications bullets, Preferred Qualifications bullets, Pay paragraph, Bonus info.
We need to ensure we include all.
Let's craft About the role paragraph(s). Could be multiple
under same heading? The instruction: use
for prose. So we can have multiple
elements under the heading.
We'll produce:
About the role
Our CompanyWe're Hitachi Vantara, the data foundation trusted by the world's innovators. Our resilient, high-performance data infrastructure means that customers - from banks to theme parks - can focus on achieving the incredible with data. If you've seen the Las Vegas Sphere, you've seen just one example of how we empower businesses to automate, optimize, innovate - and wow their customers. Right now, we're laying the foundation for our next wave of growth. We're looking for people who love being part of a diverse, global team - and who get excited about making a real-world impact with data.
About The RoleHitachi Vantara’s customers run mission-critical workloads for Fortune 500 enterprises, government agencies, financial institutions, healthcare systems, and critical infrastructure operators. When their business applications and databases are slow, expensive, non-compliant, or unavailable, the consequences are not IT consequences. They are board-level, and in some cases public-safety, consequences. This role owns the go-to-market for the solutions that help enterprises modernize and manage critical business applications and databases, improve cost and operational performance, strengthen resilience and continuity, and meet compliance obligations they increasingly have to prove rather than assert. The work itself is translation under pressure.
headings and
for prose,
- for lists.
We need to decide which content goes to which section.
About the role: combine the introductory paragraphs (Our Company, About The Role, Who this fits., What You’ll Own, Why This Role?) Actually responsibilities and qualifications are separate. So About the role could be a narrative summary of role purpose and context. We'll include the paragraphs from "Our Company", "About The Role", "Who this fits.", maybe also "Why This Role"? But Why This Role is more about motivations; could be part of About the role or separate. Since we have a Why This Role content, we could put it under About the role as well, but we have no separate heading for Why This Role. Might be okay to include under About the role.
But we also have Responsibilities section: we can put the "What You’ll Own" bullets there.
Requirements: the Qualifications list.
Skills: the Preferred Qualifications list.
Pay: salary info.
Benefits: bonus/variable/commission pay programs.
We must not repeat content. Ensure we preserve all substantive info. Let's check if any info omitted: Our Company description, About The Role paragraph, Who this fits paragraph, What You’ll Own bullets, Why This Role bullets, Qualifications bullets, Preferred Qualifications bullets, Pay paragraph, Bonus info.
We need to ensure we include all.
Let's craft About the role paragraph(s). Could be multiple
under same heading? The instruction: use
for prose. So we can have multiple
elements under the heading. We'll produce:
About the role
Our CompanyWe're Hitachi Vantara, the data foundation trusted by the world's innovators. Our resilient, high-performance data infrastructure means that customers - from banks to theme parks - can focus on achieving the incredible with data. If you've seen the Las Vegas Sphere, you've seen just one example of how we empower businesses to automate, optimize, innovate - and wow their customers. Right now, we're laying the foundation for our next wave of growth. We're looking for people who love being part of a diverse, global team - and who get excited about making a real-world impact with data.
About The RoleHitachi Vantara’s customers run mission-critical workloads for Fortune 500 enterprises, government agencies, financial institutions, healthcare systems, and critical infrastructure operators. When their business applications and databases are slow, expensive, non-compliant, or unavailable, the consequences are not IT consequences. They are board-level, and in some cases public-safety, consequences. This role owns the go-to-market for the solutions that help enterprises modernize and manage critical business applications and databases, improve cost and operational performance, strengthen resilience and continuity, and meet compliance obligations they increasingly have to prove rather than assert. The work itself is translation under pressure.