Senior Product Marketing Manager [REMOTE]
Base Career · North Salt Lake, UT · 1 mo ago
RemoteRemoteMarketing$69/hrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting.
The posting text: "In this role you will... Positioning and messaging for our AI inference portfolio. The message architecture, the value framework, and the proof behind every claim we make. Competitive and market strategy. You track the AI inference and infrastructure landscape, arm the field, and hold a defensible point of view on where the category is going. Launches, end to end. Narrative and press through analyst briefings through sales enablement, on a release cadence measured in weeks rather than quarters. Enterprise buyer fluency. Persona and journey work for CIOs, VPs of Engineering, VPs of AI, and the platform teams who evaluate us. Sales enablement sellers actually use. Sales plays, discovery questions, objection handling, cost and ROI models, customer stories. Pricing and packaging input, grounded in how enterprises actually buy and budget for AI infrastructure. The open source to commercial path. The relationship between what the project does and what the product does, and the narrative that differentiates each. Customer obsessed. You are a named spokesperson. You brief analysts, prep executives, and show up on stage, on podcasts, and in the community. You are a good fit if you have... 8+ years in B2B enterprise software product marketing, with meaningful time on infrastructure, developer, or data platform products sold to technical buyers. Enterprise go-to-market that closed real revenue. You can describe deals your messaging influenced, the buyer roles in the room, and what changed because of the work you did. Genuine technical depth. Working knowledge of AI and Inference, cloud infrastructure, and how modern software gets deployed and operated, with awareness of the Kubernetes ecosystem. Open source and commercial experience in the same organization. You have marketed a project and a product side by side. You understand community trust, the open core line, contributor and maintainer dynamics. Zero to one in an emerging category. You have taken a new, technically ambitious product to market before the analysts had a name for it. Writing you did yourself. You ship copy. Comfort with speed and ambiguity. Our releases ship in weeks. The AI infrastructure market is moving quickly. Trust with engineers, and senior sales leaders. A plus if you... Direct experience marketing AI or ML infrastructure, including inference serving, GPU capacity, or MLOps. Fluency in the CNCF and/or PyTorch ecosystem Hyperscaler or cloud marketplace route-to-market experience (AWS, Azure, GCP). Training in a value messaging discipline such as Command of the Message, or an equivalent framework you have actually operationalized. You have been the first or only PMM on a product and built the function from nothing. Why Upbound? At Upbound, you’ll help shape the systems and strategies that drive predictable, scalable growth in a product-led company embracing usage-based models. If you're excited to build from the ground up, work with cutting-edge cloud technologies, and directly impact how revenue is generated and scaled—this is your seat at the table. About Upbound Upbound is pioneering infrastructure platforms for the Agentic AI Era, serving Fortune 500 companies and platform engineers across more than 100 countries. The company empowers infrastructure and platform teams with Intelligent Control Planes - based on Kubernetes and Crossplane - that provision, operate, and adapt so platforms are ready for both humans and AI agents. Upbound is the creator and primary maintainer of Crossplane, the popular open-source framework for building cloud-native control planes, with over 100 million downloads and adoption by more than 1,000 teams worldwide. A Series B startup backed by GV (formerly Google Ventures), Altimeter Capital, and Intel Capital, Upbound has raised $69M to date. For more information, visit www.upbound.io."
We need to extract sections: About the role (intro description), Responsibilities (list of duties), Requirements (must-have), Qualifications (maybe plus?), Skills (maybe plus?), Benefits, Pay, Schedule.
We need to see if any specific content for Benefits, Pay, Schedule is present. The posting does not mention benefits, pay, schedule. So we should NOT include those sections.
We need to include sections only when there is real specific content. So we can have About the role, Responsibilities, Requirements, Qualifications, Skills maybe.
We need to decide what goes where.
The posting includes: "In this role you will..." then a paragraph of responsibilities. Then "You are a good fit if you have..." then list of requirements/qualifications. Then "A plus if you..." then plus items (nice-to-have). Then "Why Upbound?" and "About Upbound" which is company description.
We need to map to headings: About the role (maybe the intro paragraph about role?), Responsibilities (the duties), Requirements (must-have), Qualifications (maybe the plus? Actually qualifications could be the must-have; skills could be plus? Or we could treat Requirements as must-have, Qualifications as plus? But we need to follow typical sections: Responsibilities, Requirements, Qualifications, Skills. However we can combine if content thin.
We need to preserve all substantive info. Let's extract:
Responsibilities bullet list:
- Positioning and messaging for our AI inference portfolio.
- The message architecture, the value framework, and the proof behind every claim we make.
- Competitive and market strategy.
- You track the AI inference and infrastructure landscape, arm the field, and hold a defensible point of view on where the category is going.
- Launches, end to end.
- Narrative and press through analyst briefings through sales enablement, on a release cadence measured in weeks rather than quarters.
- Enterprise buyer fluency.
- Persona and journey work for CIOs, VPs of Engineering, VPs of AI, and the platform teams who evaluate us.
- Sales enablement sellers actually use.
- Sales plays, discovery questions, objection handling, cost and ROI models, customer stories.
- Pricing and packaging input, grounded in how enterprises actually buy and budget for AI infrastructure.
- The open source to commercial path.
- The relationship between what the project does and what the product does, and the narrative that differentiates each.
- Customer obsessed.
- You are a named spokesperson.
- You brief analysts, prep executives, and show up on stage, on podcasts, and in the community.
That's responsibilities.
Requirements (must-have):
- 8+ years in B2B enterprise software product marketing, with meaningful time on infrastructure, developer, or data platform products sold to technical buyers.
- Enterprise go-to-market that closed real revenue.
- You can describe deals your messaging influenced, the buyer roles in the room, and what changed because of the work you did.
- Genuine technical depth.
- Working knowledge of AI and Inference, cloud infrastructure, and how modern software gets deployed and operated, with awareness of the Kubernetes ecosystem.
- Open source and commercial experience in the same organization.
- You have marketed a project and a product side by side.
- You understand community trust, the open core line, contributor and maintainer dynamics.
- Zero to one in an emerging category.
- You have taken a new, technically ambitious product to market before the analysts had a name for it.
- Writing you did yourself. You ship copy.
- Comfort with speed and ambiguity.
- Our releases ship in weeks. The AI infrastructure market is moving quickly.
- Trust with engineers, and senior sales leaders.
Qualifications (maybe plus?):
- Direct experience marketing AI or ML infrastructure, including inference serving, GPU capacity, or MLOps.
- Fluency in the CNCF and/or PyTorch ecosystem
- Hyperscaler or cloud marketplace route-to-market experience (AWS, Azure, GCP).
- Training in a value messaging discipline such as Command of the Message, or an equivalent framework you have actually operationalized.
- You have been the first or only PMM on a product and built the function from nothing.
Skills maybe could be overlapping; but we could treat the plus as Skills.
About the role: maybe a brief summary: "Positioning and messaging for our AI inference portfolio..." Actually that's part of responsibilities. Could have an "About the role" paragraph summarizing the role: maybe the first sentence: "In this role you will..." but that's already responsibilities. Could still have an About the role section with a short paragraph describing the role purpose: maybe combine the first few sentences: "Positioning and messaging for our AI inference portfolio. The message architecture, the value framework, and the proof behind every claim we make. Competitive and market strategy." But that's also responsibilities.
We need to avoid duplication. Perhaps we can put About the role as a brief overview: "You will drive positioning and messaging for the AI inference portfolio, develop message architecture, value framework, competitive strategy, track market, arm field, lead launches, enable sales, work with enterprise buyers, create spokesperson content." That's basically responsibilities but we can keep it concise.
But we must preserve ALL substantive information; we cannot invent or summarize away detail. However we can rephrase but must keep meaning. Summarizing is allowed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details; we can rephrase but must keep all details. So we need to keep each bullet point. So we cannot compress responsibilities into a short paragraph; we need to list them.
Thus we can have About the role maybe just a short intro that doesn't omit details? But if we put About the role separate, we risk duplicating content. Better to not have About the role if it would duplicate. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can include those headings if we have content. It doesn't forbid overlapping content, but we should avoid duplication? Not explicitly forbidden, but we should preserve all info; duplication is okay as long as we don't lose info. However we should avoid filler. Duplicating the same bullet points under two headings would be redundant but not losing info. Might be considered unnecessary but not prohibited. However they say "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections with little content. Duplicating would increase sections but not thin? It would be same content repeated; maybe better to not duplicate.
Thus we can have sections: Responsibilities, Requirements, Qualifications, Skills. And maybe About the role omitted because its content is covered in Responsibilities. But we need to check if there is any content that is not responsibilities but about the role overview: The first sentence "In this role you will..." is basically responsibilities. So we can skip About the role.
Thus output: