Founding Product Marketer, Commercial
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented summary. Remove boilerplate like EEO, legal, etc. Also remove application instructions. The posting includes sections: The Role (description), What you'll bring (requirements/qualifications), What success looks like (maybe responsibilities?), You might thrive in this role if... (maybe skills or traits). Also there is compensation: Annual Salary + Benefits + Equity + Bonus (if applicable) $200,000—$240,000 USD. Also mention benefits link but we should not include link? It says "Information on the benefits offered is here." That's a reference; we could include Benefits section with note that details are available via link? But we should not invent. We can include Benefits section with placeholder? The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state salary range and mentions benefits, equity, bonus. It says "Annual Salary + Benefits + Equity (if applicable) + Bonus (if applicable) $200,000—$240,000 USD". Also "Information on the benefits offered is here." So we have some benefits info but not detailed. We can still include Benefits section with that statement? It's not filler; it's actual statement that benefits info is available via link. That's okay. Pay section: we have salary range. Schedule: not mentioned. So we should not include Schedule.
We need sections: About the role (maybe The Role description), Responsibilities (maybe what you'll do: list of duties), Requirements/Qualifications (what you'll bring), Skills (maybe what success looks like or you might thrive...), Benefits, Pay.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. So we need to capture the bullet points from "In this role, you will…" and "What you'll bring", "What success looks like", "You might thrive in this role if…". Also the description about Peregrine at top (maybe About the role). Also the compensation line.
We must not include boilerplate like EEO, legal, equal opportunity, etc. Also remove duplicated lines.
Let's extract content.
First paragraph: "Backed by leading Silicon Valley investors, Peregrine helps public safety organizations, state and local and governments, federal agencies, and private-sector institutions address society’s challenges with unprecedented speed and accuracy. Our AI-enabled platform turns siloed and disconnected data into operational intelligence — instantly surfacing mission-critical information to empower better, faster decisions that improve outcomes at every touchpoint. Today Peregrine supports hundreds of customers across 30+ states and two countries, serving more than 125 million people — and we’re amplifying our impact as we expand into the enterprise and internationally."
That's about the company; could be part of About the role? Probably "About the role" includes company context. We'll put that as prose under About the role.
Then "The Role" heading: description of role. We'll treat that as About the role? Actually we have separate sections: About the role (company + role overview), Responsibilities (duties), Requirements/Qualifications (what you'll bring), Skills (maybe success looks like + you might thrive), Benefits, Pay.
We need to avoid duplication.
Let's parse:
Under "The Role": after heading, there is paragraph: "The private sector is Peregrine's next frontier, and you will be its founding product marketer, reporting to the VP of Product Marketing. Peregrine's platform takes the data an organization already has, scattered across dozens of systems, integrates it into one place, and puts AI to work on it. It runs in production across hundreds of public safety agencies. The problems it solves there exist in the private sector too: messy data spread across dozens of systems, and slow paths from question to decision to action. This role figures out where that's true and which industries Peregrine should prioritize. You'll be embedded in an integrated pod alongside product, deployment strategists, and sales, working to find product-market fit in industries beyond our core public safety business. That means deep customer discovery, rapid positioning iteration, and figuring out what resonates, what doesn't, and why. There is no commercial marketing foundation yet. You will build it, in the field, inside live deals."
Then bullet list: "In this role, you will…" with items:
- Run customer discovery as your core work: significant time with prospects and early customers in target industries, understanding their workflows, pain points, and decision criteria until you are the expert on how these buyers evaluate solutions.
- Build commercial positioning and messaging from the ground up, including translating proven public sector deployments into evidence commercial buyers accept, and a clear articulation of how we earn trust: auditability, access controls, and accountable AI.
- Test messaging in live deals, watching what holds up in a first call, then refine it through win-loss reviews and buyer research.
- Arm the pod with first-call narratives, demo storylines, competitive intelligence, and objection handling for buyers in unfamiliar industries.
- Build market expertise quickly: who the incumbents are, what analysts say, how buying works, and where the white space is in each target vertical.
- Establish feedback loops from sales calls, demos, and lost deals back into positioning and product direction.
- Package deployment proof into commercial-ready evidence: case studies, references, and outcome data buyers outside government will credit.
- As product-market fit emerges, codify the repeatable motions: messaging frameworks, enablement assets, and the GTM foundation that supports scale.
That's responsibilities.
Then "What you'll bring": list:
- Authorship that changed an outcome: a positioning document that moved a deal, a roadmap decision, or a market entry call.
- Technical fluency: Peregrine is a data platform, and marketing it means understanding how data integration, data modeling, and AI on sensitive data work, well enough to explain them, defend them, and know when a claim outruns them.
- 7+ years in product marketing or adjacent go-to-market roles, including experience taking a product into a new market, launching a new product, or building in an early-stage environment.
- Discovery craft: you ask the right questions, hear what goes unsaid, and turn messy qualitative input into clear strategic direction.
- Range across the full product marketing stack: positioning, deal support, enablement, and campaign execution.
- Comfort treating an unmapped market as a research problem with a deadline.
- Judgment to tell the difference between a vertical where Peregrine is transformational and one where it's a nice-to-have.
- Judgment on when a claim is proven versus promising, built working alongside technical field teams.
- Adept at operating across two registers: technical depth for evaluators, plain language for the operators who live in the product.
Then "What success looks like": list:
- You can make the commercial case yourself: in a first call with a skeptical buyer, you deliver the argument for why their industry needs what Peregrine builds, in their terms, and it holds when they push back.
- The pod reaches for your positioning unprompted. The language in first-call decks, demo storylines, and proposals traces back to you.
- Vertical discovery ends in decisions: documented pursue-or-pass calls grounded in win-loss and buyer research.
- Commercial claims survive procurement, security review, and legal without being walked back.
- Deployment proof is commercial-ready: case studies and references the pod uses without a scramble on every send.
- Sales pulls you into deals early, and the public safety teams open their deployment proof to you.
Then "You might thrive in this role if…": list:
- You've built a marketing motion from nothing and want to do it again.
- You go to the source: buyers, users, the people running the workflow today. Reports come second.
- You form a point of view from thin data and revise it when the evidence moves.
- You don't stretch claims to move a deal forward.
- You want to be in the pod: in the discovery calls, the demos, the deal reviews.
- The zero-to-one challenge is the draw.
Then compensation: "Annual Salary + Benefits + Equity (if applicable) + Bonus (if applicable) $200,000—$240,000 USD Actual compensation is influenced by a wide array of factors including but not limited to skill set, level of experience, certifications or licenses, and specific work location. Information on the benefits offered is here."
We need Benefits section: we have mention of benefits but no details; we could include a short paragraph: "Benefits information is available via the provided link." That's not filler; it's actual statement. We'll include that.
Pay section: include salary range and note about factors.
We must not include Schedule.
Now produce HTML.
Structure:
About the role
Backed by leading Silicon Valley investors, Peregrine helps public safety organizations, state and local and governments, federal agencies, and private-sector institutions address society’s challenges with unprecedented speed and accuracy. Our AI-enabled platform turns siloed and disconnected data into operational intelligence — instantly surfacing mission-critical information to empower better, faster decisions that improve outcomes at every touchpoint. Today Peregrine supports hundreds of customers across 30+ states and two countries, serving more than 125 million people — and we’re amplifying our impact as we expand into the enterprise and internationally. The private sector is Peregrine's next frontier, and you will be its founding product marketer, reporting to the VP of Product Marketing. Peregrine's platform takes the data an organization already has, scattered across dozens of systems, integrates it into one place, and puts AI to work on it. It runs in production across hundreds of public safety agencies. The problems it solves there exist in the private sector too: messy data spread across dozens of systems, and slow paths from question to decision to action. This role figures out where that's true and which industries Peregrine should prioritize. You'll be embedded in an integrated pod alongside product, deployment strategists, and sales, working to find product-market fit in industries beyond our core public safety business. That means deep customer discovery, rapid positioning iteration, and figuring out what resonates, what doesn't, and why. There is no commercial marketing foundation yet. You will build it, in the field, inside live deals.
But we might split About the role to just company overview; but it's okay to include role overview there. However we also have Responsibilities separate. To avoid duplication, we could keep About the role as company overview only, and Responsibilities as the bullet list. But the instructions: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we could have both Requirements and Qualifications separate, but we can combine if content overlaps. However we have "What you'll bring" which is qualifications/requirements. We could make a Requirements section with those bullet points. Qualifications maybe not needed separately. But we could also have Skills section for "What success looks like" and "You might thrive in this role if…" maybe combine.
We need to avoid filler headings. So we need to decide which sections have real specific content.
We have:
- About the role: company overview + role context (substantive)
- Responsibilities: the bullet list under "In this role, you will…" (substantive)
- Requirements: the bullet list under "What you'll bring" (substantive)
- Skills: maybe combine "What success
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to capture the bullet points from "In this role, you will…" and "What you'll bring", "What success looks like", "You might thrive in this role if…". Also the description about Peregrine at top (maybe About the role). Also the compensation line. We must not include boilerplate like EEO, legal, equal opportunity, etc. Also remove duplicated lines. Let's extract content. First paragraph: "Backed by leading Silicon Valley investors, Peregrine helps public safety organizations, state and local and governments, federal agencies, and private-sector institutions address society’s challenges with unprecedented speed and accuracy. Our AI-enabled platform turns siloed and disconnected data into operational intelligence — instantly surfacing mission-critical information to empower better, faster decisions that improve outcomes at every touchpoint. Today Peregrine supports hundreds of customers across 30+ states and two countries, serving more than 125 million people — and we’re amplifying our impact as we expand into the enterprise and internationally." That's about the company; could be part of About the role? Probably "About the role" includes company context. We'll put that as prose under About the role. Then "The Role" heading: description of role. We'll treat that as About the role? Actually we have separate sections: About the role (company + role overview), Responsibilities (duties), Requirements/Qualifications (what you'll bring), Skills (maybe success looks like + you might thrive), Benefits, Pay. We need to avoid duplication. Let's parse: Under "The Role": after heading, there is paragraph: "The private sector is Peregrine's next frontier, and you will be its founding product marketer, reporting to the VP of Product Marketing. Peregrine's platform takes the data an organization already has, scattered across dozens of systems, integrates it into one place, and puts AI to work on it. It runs in production across hundreds of public safety agencies. The problems it solves there exist in the private sector too: messy data spread across dozens of systems, and slow paths from question to decision to action. This role figures out where that's true and which industries Peregrine should prioritize. You'll be embedded in an integrated pod alongside product, deployment strategists, and sales, working to find product-market fit in industries beyond our core public safety business. That means deep customer discovery, rapid positioning iteration, and figuring out what resonates, what doesn't, and why. There is no commercial marketing foundation yet. You will build it, in the field, inside live deals." Then bullet list: "In this role, you will…" with items: - Run customer discovery as your core work: significant time with prospects and early customers in target industries, understanding their workflows, pain points, and decision criteria until you are the expert on how these buyers evaluate solutions. - Build commercial positioning and messaging from the ground up, including translating proven public sector deployments into evidence commercial buyers accept, and a clear articulation of how we earn trust: auditability, access controls, and accountable AI. - Test messaging in live deals, watching what holds up in a first call, then refine it through win-loss reviews and buyer research. - Arm the pod with first-call narratives, demo storylines, competitive intelligence, and objection handling for buyers in unfamiliar industries. - Build market expertise quickly: who the incumbents are, what analysts say, how buying works, and where the white space is in each target vertical. - Establish feedback loops from sales calls, demos, and lost deals back into positioning and product direction. - Package deployment proof into commercial-ready evidence: case studies, references, and outcome data buyers outside government will credit. - As product-market fit emerges, codify the repeatable motions: messaging frameworks, enablement assets, and the GTM foundation that supports scale. That's responsibilities. Then "What you'll bring": list: - Authorship that changed an outcome: a positioning document that moved a deal, a roadmap decision, or a market entry call. - Technical fluency: Peregrine is a data platform, and marketing it means understanding how data integration, data modeling, and AI on sensitive data work, well enough to explain them, defend them, and know when a claim outruns them. - 7+ years in product marketing or adjacent go-to-market roles, including experience taking a product into a new market, launching a new product, or building in an early-stage environment. - Discovery craft: you ask the right questions, hear what goes unsaid, and turn messy qualitative input into clear strategic direction. - Range across the full product marketing stack: positioning, deal support, enablement, and campaign execution. - Comfort treating an unmapped market as a research problem with a deadline. - Judgment to tell the difference between a vertical where Peregrine is transformational and one where it's a nice-to-have. - Judgment on when a claim is proven versus promising, built working alongside technical field teams. - Adept at operating across two registers: technical depth for evaluators, plain language for the operators who live in the product. Then "What success looks like": list: - You can make the commercial case yourself: in a first call with a skeptical buyer, you deliver the argument for why their industry needs what Peregrine builds, in their terms, and it holds when they push back. - The pod reaches for your positioning unprompted. The language in first-call decks, demo storylines, and proposals traces back to you. - Vertical discovery ends in decisions: documented pursue-or-pass calls grounded in win-loss and buyer research. - Commercial claims survive procurement, security review, and legal without being walked back. - Deployment proof is commercial-ready: case studies and references the pod uses without a scramble on every send. - Sales pulls you into deals early, and the public safety teams open their deployment proof to you. Then "You might thrive in this role if…": list: - You've built a marketing motion from nothing and want to do it again. - You go to the source: buyers, users, the people running the workflow today. Reports come second. - You form a point of view from thin data and revise it when the evidence moves. - You don't stretch claims to move a deal forward. - You want to be in the pod: in the discovery calls, the demos, the deal reviews. - The zero-to-one challenge is the draw. Then compensation: "Annual Salary + Benefits + Equity (if applicable) + Bonus (if applicable) $200,000—$240,000 USD Actual compensation is influenced by a wide array of factors including but not limited to skill set, level of experience, certifications or licenses, and specific work location. Information on the benefits offered is here." We need Benefits section: we have mention of benefits but no details; we could include a short paragraph: "Benefits information is available via the provided link." That's not filler; it's actual statement. We'll include that. Pay section: include salary range and note about factors. We must not include Schedule. Now produce HTML. Structure:
About the role
Backed by leading Silicon Valley investors, Peregrine helps public safety organizations, state and local and governments, federal agencies, and private-sector institutions address society’s challenges with unprecedented speed and accuracy. Our AI-enabled platform turns siloed and disconnected data into operational intelligence — instantly surfacing mission-critical information to empower better, faster decisions that improve outcomes at every touchpoint. Today Peregrine supports hundreds of customers across 30+ states and two countries, serving more than 125 million people — and we’re amplifying our impact as we expand into the enterprise and internationally. The private sector is Peregrine's next frontier, and you will be its founding product marketer, reporting to the VP of Product Marketing. Peregrine's platform takes the data an organization already has, scattered across dozens of systems, integrates it into one place, and puts AI to work on it. It runs in production across hundreds of public safety agencies. The problems it solves there exist in the private sector too: messy data spread across dozens of systems, and slow paths from question to decision to action. This role figures out where that's true and which industries Peregrine should prioritize. You'll be embedded in an integrated pod alongside product, deployment strategists, and sales, working to find product-market fit in industries beyond our core public safety business. That means deep customer discovery, rapid positioning iteration, and figuring out what resonates, what doesn't, and why. There is no commercial marketing foundation yet. You will build it, in the field, inside live deals.
But we might split About the role to just company overview; but it's okay to include role overview there. However we also have Responsibilities separate. To avoid duplication, we could keep About the role as company overview only, and Responsibilities as the bullet list. But the instructions: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we could have both Requirements and Qualifications separate, but we can combine if content overlaps. However we have "What you'll bring" which is qualifications/requirements. We could make a Requirements section with those bullet points. Qualifications maybe not needed separately. But we could also have Skills section for "What success looks like" and "You might thrive in this role if…" maybe combine. We need to avoid filler headings. So we need to decide which sections have real specific content. We have: - About the role: company overview + role context (substantive) - Responsibilities: the bullet list under "In this role, you will…" (substantive) - Requirements: the bullet list under "What you'll bring" (substantive) - Skills: maybe combine "What success