Publishing Success Manager, API Network
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/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- Who Are We? (company description) - could be "About the company" maybe not required but we can include as a section? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should only use those headings if content matches. But we could also include "About the company" as a heading? Not listed. Safer to stick to those headings only when appropriate. However we need to convey company info; maybe we can put it under "About the role"? Not exactly. Could combine into a brief intro paragraph before sections. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings besides those examples, but they gave examples. Probably we should follow the pattern: include sections only if we have content for them. Likely sections: About the role (maybe a summary), Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. We need to see what content we have.
From posting:
- About The Team: description of role, goal, etc. Could be "About the role".
- What you’ll be doing: list of duties -> Responsibilities.
- About You: experience, skills -> Requirements/Qualifications/Skills.
- What Else?: benefits description -> Benefits.
- Hybrid work model: schedule -> Schedule.
- Pay: mention "pay-on-performance philosophy" but no specific salary. It says "In addition to Postman's pay-on-performance philosophy, and a flexible schedule...". No explicit pay range. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, we have only "pay-on-performance philosophy" which is vague but still states something about pay philosophy. Is that enough? It says "pay-on-performance philosophy" - that is a statement about pay. Could be considered stating pay philosophy. However they said avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "pay-on-performance philosophy" is not a specific number but it's a statement. Might be okay to include Pay section with that statement. But better to avoid if it's too vague. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state a philosophy, so we could include. However they also say "Prefer a few substantive sections over many thin ones." So maybe combine Pay into Benefits or About the role? But they want separate sections if content exists. I'd include Pay with that statement.
Schedule: they describe hybrid work model: expected to come into office 3 days a week for certain locations. That's specific. So Schedule section.
Benefits: they list full medical coverage, flexible PTO, wellness reimbursement, monthly lunch stipend, wellness programs, creche allowance, team-building events, donation-matching program. That's substantive.
Now we need to format.
We must not include boilerplate: EEO, headhunter etc. Remove those lines.
Also remove "Learn more at postman.com or connect with Postman on X via @getpostman." That's maybe navigation? It's not boilerplate but could be considered external link; but it's not a duty/requirement. It's company info. Might keep as part of About the company? But we may not have a section for that. Could include in a brief intro paragraph before sections. The instruction: output only HTML fragment; we can have a
intro then sections.
We must not repeat job title as heading. Job title is "Publisher Success Manager (PSM)". Not to use as heading.
We must not put Job ID/requisition numbers as headings - none present.
Now craft HTML.
We'll start with maybe a
describing company: "Postman is the world’s leading API platform..." etc. That's from Who Are We? and About The Team? Actually "Who Are We?" is company description. We'll include that as intro.
Then
About the role
with a paragraph summarizing role: maybe from About The Team: "Postman is looking for a Publisher Success Manager (PSM) to join our team within the Postman API Network..." etc. Could be a couple sentences.
Then Responsibilities
with - list each duty from "What you’ll be doing". Need to preserve all substantive info; not summarize away detail. So each bullet should be a duty as written.
List:
- Act as the primary point of contact for key publishers on the Postman API Network, providing strategic and hands-on support to drive their success and engagement.
- Collaborate with publishers to help them build and optimize high-quality public workspaces, leveraging metrics to deliver growth.
- Lead Quarterly Workspace Reviews (QWRs) and participate in Publisher Connect Meetups (PCMs) to deepen relationships and create opportunities for collaboration and feedback.
- Work closely with internal teams (Product, Marketing, DevRel) to provide publishers with the resources and tools they need to succeed, from custom onboarding workflows to co-marketing opportunities to support their launches.
- Identify and track key performance indicators like Quality Scores, Forks, Watchers, and error metrics to proactively address publisher challenges.
- Advocate for publishers’ needs within Postman, synthesizing feedback to drive platform improvements and future product development.
- Support publishers in adopting Postman’s latest features (like Flows and custom RIP buttons) and integrate these features into their workflows for maximum impact.
- Own various internal projects that benefit Publishers and the Network overall.
Make sure to keep punctuation.
Then
Requirements
maybe combine About You: "Have 5+ years of experience in customer success, account management, or similar roles in a B2B SaaS or developer-focused company." etc. Could be a list.
But we also have Skills separate? The instruction includes Skills heading. We could split: Requirements for experience, Skills for abilities. Let's parse About You:
- Have 5+ years of experience in customer success, account management, or similar roles in a B2B SaaS or developer-focused company.
- Possess excellent communication and relationship-building skills.
- Are proactive and resourceful, with a knack for solving problems creatively while maintaining a customer-centric mindset.
- Have a good understanding of API concepts and workflows, and experience working with developer tools or platforms.
- Demonstrate strong analytical skills with the ability to interpret metrics and data, translating them into actionable insights for external partners.
- Are excited by the opportunity to help shape and scale a fast-growing network, taking ownership of key initiatives and driving continuous improvements.
We could treat first as Requirements (experience) and the rest as Skills. Or combine all into Requirements. Since they gave Skills heading, we can separate: Requirements: experience (5+ years). Skills: communication, proactive, API understanding, analytical, excitement.
But also "Are excited by the opportunity..." maybe more of a motivation; could be under Skills or Requirements. We'll put under Skills.
Thus:
Requirements
Have 5+ years of experience in customer success, account management, or similar roles in a B2B SaaS or developer-focused company.
Skills
- Excellent communication and relationship-building skills.
- Proactive and resourceful, with a knack for solving problems creatively while maintaining a customer-centric mindset.
- Good understanding of API concepts and workflows, and experience working with developer tools or platforms.
- Strong analytical skills with the ability to interpret metrics and data, translating them into actionable insights for external partners.
- Excited by the opportunity to help shape and scale a fast-growing network, taking ownership of key initiatives and driving continuous improvements.
Now Benefits:
Benefits
- Full medical coverage.
- Flexible PTO.
- Wellness reimbursement.
- Monthly lunch stipend.
- Wellness programs to support physical and mental health.
- Creche allowance for employees with little ones.
- Frequent and fascinating team-building events.
- Donation-matching program to support causes you care about.
Pay:
Pay
Pay-on-performance philosophy.
Schedule:
Schedule
Hybrid remote/in-person role based in the United States. For roles based out of San Francisco Bay Area, Boston, Bangalore, Noida, Hyderabad, and New York, employees are expected to come into the office 3 days a week.
We also have mention "As a standalone business with Postman, we build fast, learn while doing it, and most importantly, have fun!" Could be part of About the role intro.
Now we need to ensure we didn't include boilerplate: EEO lines, headhunter lines, etc. Remove them.
Check for duplicated lines: none.
Now output only HTML fragment.
We'll start with an intro maybe combining Who Are We? and About The Team? Let's craft:
Postman is the world’s leading API platform, used by more than 35 million developers and 500,000 organizations, including 98% of the Fortune 500. Postman helps developers and professionals build the API-first world by simplifying each step of the API lifecycle and streamlining collaboration. The Postman API Network is the world’s largest repository of APIs, serving developers from companies like AWS, Salesforce, Stripe, Zoom, Discord, and many more. As a Publisher Success Manager (PSM) you’ll work with key publishers on the Network to help them optimize their presence, drive growth and adoption of their APIs, ensure they leverage the latest platform features, and synthesize product feedback across Postman.
That covers company description and role summary.
Now sections.
Make sure not to repeat job title as heading; we didn't.
Now output.
Check for any leftover boilerplate: "P.S: We highly recommend reading The "API-First World" graphic novel..." That's maybe not boilerplate but could be considered extra; it's not a duty/requirement/benefit. It's a suggestion. Should we keep? It's not in the sections we defined; we could include it in intro as a sentence. But it's not essential. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that P.S. It's substantive? It's a recommendation to read a graphic novel. Might be considered extra but still part of posting. We could add a after intro:
P.S: We highly recommend reading the "API-First World" graphic novel to understand the bigger picture and our vision at Postman.
But note the quotes inside; we need to escape? In HTML we can just include as is; but we need to ensure proper quoting. Use straight quotes.
Now also "Learn more at postman.com or connect with Postman on X via @getpostman." That's also substantive?
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - Who Are We? (company description) - could be "About the company" maybe not required but we can include as a section? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should only use those headings if content matches. But we could also include "About the company" as a heading? Not listed. Safer to stick to those headings only when appropriate. However we need to convey company info; maybe we can put it under "About the role"? Not exactly. Could combine into a brief intro paragraph before sections. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings besides those examples, but they gave examples. Probably we should follow the pattern: include sections only if we have content for them. Likely sections: About the role (maybe a summary), Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. We need to see what content we have. From posting: - About The Team: description of role, goal, etc. Could be "About the role". - What you’ll be doing: list of duties -> Responsibilities. - About You: experience, skills -> Requirements/Qualifications/Skills. - What Else?: benefits description -> Benefits. - Hybrid work model: schedule -> Schedule. - Pay: mention "pay-on-performance philosophy" but no specific salary. It says "In addition to Postman's pay-on-performance philosophy, and a flexible schedule...". No explicit pay range. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, we have only "pay-on-performance philosophy" which is vague but still states something about pay philosophy. Is that enough? It says "pay-on-performance philosophy" - that is a statement about pay. Could be considered stating pay philosophy. However they said avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "pay-on-performance philosophy" is not a specific number but it's a statement. Might be okay to include Pay section with that statement. But better to avoid if it's too vague. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state a philosophy, so we could include. However they also say "Prefer a few substantive sections over many thin ones." So maybe combine Pay into Benefits or About the role? But they want separate sections if content exists. I'd include Pay with that statement. Schedule: they describe hybrid work model: expected to come into office 3 days a week for certain locations. That's specific. So Schedule section. Benefits: they list full medical coverage, flexible PTO, wellness reimbursement, monthly lunch stipend, wellness programs, creche allowance, team-building events, donation-matching program. That's substantive. Now we need to format. We must not include boilerplate: EEO, headhunter etc. Remove those lines. Also remove "Learn more at postman.com or connect with Postman on X via @getpostman." That's maybe navigation? It's not boilerplate but could be considered external link; but it's not a duty/requirement. It's company info. Might keep as part of About the company? But we may not have a section for that. Could include in a brief intro paragraph before sections. The instruction: output only HTML fragment; we can have a
intro then sections. We must not repeat job title as heading. Job title is "Publisher Success Manager (PSM)". Not to use as heading. We must not put Job ID/requisition numbers as headings - none present. Now craft HTML. We'll start with maybe a
describing company: "Postman is the world’s leading API platform..." etc. That's from Who Are We? and About The Team? Actually "Who Are We?" is company description. We'll include that as intro. Then
About the role
with a paragraph summarizing role: maybe from About The Team: "Postman is looking for a Publisher Success Manager (PSM) to join our team within the Postman API Network..." etc. Could be a couple sentences. ThenResponsibilities
with- list each duty from "What you’ll be doing". Need to preserve all substantive info; not summarize away detail. So each bullet should be a duty as written.
List:
- Act as the primary point of contact for key publishers on the Postman API Network, providing strategic and hands-on support to drive their success and engagement.
- Collaborate with publishers to help them build and optimize high-quality public workspaces, leveraging metrics to deliver growth.
- Lead Quarterly Workspace Reviews (QWRs) and participate in Publisher Connect Meetups (PCMs) to deepen relationships and create opportunities for collaboration and feedback.
- Work closely with internal teams (Product, Marketing, DevRel) to provide publishers with the resources and tools they need to succeed, from custom onboarding workflows to co-marketing opportunities to support their launches.
- Identify and track key performance indicators like Quality Scores, Forks, Watchers, and error metrics to proactively address publisher challenges.
- Advocate for publishers’ needs within Postman, synthesizing feedback to drive platform improvements and future product development.
- Support publishers in adopting Postman’s latest features (like Flows and custom RIP buttons) and integrate these features into their workflows for maximum impact.
- Own various internal projects that benefit Publishers and the Network overall.
Make sure to keep punctuation.
Then
Requirements
maybe combine About You: "Have 5+ years of experience in customer success, account management, or similar roles in a B2B SaaS or developer-focused company." etc. Could be a list. But we also have Skills separate? The instruction includes Skills heading. We could split: Requirements for experience, Skills for abilities. Let's parse About You: - Have 5+ years of experience in customer success, account management, or similar roles in a B2B SaaS or developer-focused company. - Possess excellent communication and relationship-building skills. - Are proactive and resourceful, with a knack for solving problems creatively while maintaining a customer-centric mindset. - Have a good understanding of API concepts and workflows, and experience working with developer tools or platforms. - Demonstrate strong analytical skills with the ability to interpret metrics and data, translating them into actionable insights for external partners. - Are excited by the opportunity to help shape and scale a fast-growing network, taking ownership of key initiatives and driving continuous improvements. We could treat first as Requirements (experience) and the rest as Skills. Or combine all into Requirements. Since they gave Skills heading, we can separate: Requirements: experience (5+ years). Skills: communication, proactive, API understanding, analytical, excitement. But also "Are excited by the opportunity..." maybe more of a motivation; could be under Skills or Requirements. We'll put under Skills. Thus:Requirements
Have 5+ years of experience in customer success, account management, or similar roles in a B2B SaaS or developer-focused company.
Skills
- Excellent communication and relationship-building skills.
- Proactive and resourceful, with a knack for solving problems creatively while maintaining a customer-centric mindset.
- Good understanding of API concepts and workflows, and experience working with developer tools or platforms.
- Strong analytical skills with the ability to interpret metrics and data, translating them into actionable insights for external partners.
- Excited by the opportunity to help shape and scale a fast-growing network, taking ownership of key initiatives and driving continuous improvements.
Benefits
- Full medical coverage.
- Flexible PTO.
- Wellness reimbursement.
- Monthly lunch stipend.
- Wellness programs to support physical and mental health.
- Creche allowance for employees with little ones.
- Frequent and fascinating team-building events.
- Donation-matching program to support causes you care about.
Pay
Pay-on-performance philosophy.
Schedule:Schedule
Hybrid remote/in-person role based in the United States. For roles based out of San Francisco Bay Area, Boston, Bangalore, Noida, Hyderabad, and New York, employees are expected to come into the office 3 days a week.
We also have mention "As a standalone business with Postman, we build fast, learn while doing it, and most importantly, have fun!" Could be part of About the role intro. Now we need to ensure we didn't include boilerplate: EEO lines, headhunter lines, etc. Remove them. Check for duplicated lines: none. Now output only HTML fragment. We'll start with an intromaybe combining Who Are We? and About The Team? Let's craft:
Postman is the world’s leading API platform, used by more than 35 million developers and 500,000 organizations, including 98% of the Fortune 500. Postman helps developers and professionals build the API-first world by simplifying each step of the API lifecycle and streamlining collaboration. The Postman API Network is the world’s largest repository of APIs, serving developers from companies like AWS, Salesforce, Stripe, Zoom, Discord, and many more. As a Publisher Success Manager (PSM) you’ll work with key publishers on the Network to help them optimize their presence, drive growth and adoption of their APIs, ensure they leverage the latest platform features, and synthesize product feedback across Postman.
That covers company description and role summary. Now sections. Make sure not to repeat job title as heading; we didn't. Now output. Check for any leftover boilerplate: "P.S: We highly recommend reading The "API-First World" graphic novel..." That's maybe not boilerplate but could be considered extra; it's not a duty/requirement/benefit. It's a suggestion. Should we keep? It's not in the sections we defined; we could include it in intro as a sentence. But it's not essential. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that P.S. It's substantive? It's a recommendation to read a graphic novel. Might be considered extra but still part of posting. We could add aafter intro:
P.S: We highly recommend reading the "API-First World" graphic novel to understand the bigger picture and our vision at Postman.
But note the quotes inside; we need to escape? In HTML we can just include as is; but we need to ensure proper quoting. Use straight quotes. Now also "Learn more at postman.com or connect with Postman on X via @getpostman." That's also substantive?