Founding Product Marketing Manager
Synthpop - Healthcare AI · United States · 1 mo ago
RemoteRemoteMarketing$135k–$150k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Synthpop (company description), Why this role is exciting, What you'll own, What success looks like, Qualifications, Nice to have (maybe as part of Qualifications?), Work environment and lifestyle, Compensation, Benefits, Why Synthpop? We need to follow rules: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must include a section only when posting has real, specific content. We must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Compensation (Base compensation: $135,000 - $150,000, Equity: Competitive early-stage equity.) That's pay info. So we can have a Pay section. Benefits are listed: Health Coverage, Retirement, FSA & HSA, Disability & Life Insurance, Dependent Care, Flexible Work, Paid Time Off, Parental leave, Professional Growth. So Benefits section. Schedule: The posting includes "Our core collaboration hours are generally 9 AM-6 PM Eastern." That's schedule info. Also "On-site collaboration: This role is based in the Boston/Cambridge area. The steady-state expectation is at least three days per week in the office". That's work environment and lifestyle. So we can have a Schedule section with core hours. Also maybe a Work environment section? The rules only list specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content to these headings. About the role: could be the "Why this role is exciting" and maybe "About Synthpop"? But "About the role" heading should contain description of role. We can combine "Why this role is exciting" and "What you'll own" as responsibilities? Actually responsibilities are duties. The posting includes "What you'll own" which lists responsibilities. So we can put that under Responsibilities. Requirements: Qualifications section. Skills: maybe "Nice to have" could be Skills? But we have Qualifications (required) and Nice to have (preferred). Could treat Qualifications as Requirements, and Skills as Nice to have? Or we could have Skills section for nice-to-have. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings. We need to include sections only when posting has real content. So we need to decide which headings to use.
We have content for:
- About the role: Could be the introductory paragraph about Synthpop and why role exciting? Might be okay.
- Responsibilities: "What you'll own" list.
- Requirements: Qualifications (required) list.
- Skills: Nice to have list.
- Benefits: list.
- Pay: compensation.
- Schedule: core collaboration hours and maybe on-site expectation.
We should not include sections like "About the role" if it's just company description? But we have content: "About Synthpop" and "Why this role is exciting". That's about the role and company. So we can put that under About the role.
We must not repeat job title as heading. Not needed.
We must not include boilerplate like EEO etc. Not present.
We must not include application instructions. Not present.
We must preserve all substantive information. So we need to include all details from the posting, but we can reorganize under headings.
We must not invent or summarize away detail. So we need to keep specifics like bullet points.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must include a section only when posting has real, specific content. We must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Compensation (Base compensation: $135,000 - $150,000, Equity: Competitive early-stage equity.) That's pay info. So we can have a Pay section. Benefits are listed: Health Coverage, Retirement, FSA & HSA, Disability & Life Insurance, Dependent Care, Flexible Work, Paid Time Off, Parental leave, Professional Growth. So Benefits section. Schedule: The posting includes "Our core collaboration hours are generally 9 AM-6 PM Eastern." That's schedule info. Also "On-site collaboration: This role is based in the Boston/Cambridge area. The steady-state expectation is at least three days per week in the office". That's work environment and lifestyle. So we can have a Schedule section with core hours. Also maybe a Work environment section? The rules only list specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content to these headings. About the role: could be the "Why this role is exciting" and maybe "About Synthpop"? But "About the role" heading should contain description of role. We can combine "Why this role is exciting" and "What you'll own" as responsibilities? Actually responsibilities are duties. The posting includes "What you'll own" which lists responsibilities. So we can put that under Responsibilities. Requirements: Qualifications section. Skills: maybe "Nice to have" could be Skills? But we have Qualifications (required) and Nice to have (preferred). Could treat Qualifications as Requirements, and Skills as Nice to have? Or we could have Skills section for nice-to-have. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings. We need to include sections only when posting has real content. So we need to decide which headings to use.
We have content for:
- About the role: Could be the introductory paragraph about Synthpop and why role exciting? Might be okay.
- Responsibilities: "What you'll own" list.
- Requirements: Qualifications (required) list.
- Skills: Nice to have list.
- Benefits: list.
- Pay: compensation.
- Schedule: core collaboration hours and maybe on-site expectation.
We should not include sections like "About the role" if it's just company description? But we have content: "About Synthpop" and "Why this role is exciting". That's about the role and company. So we can put that under About the role.
We must not repeat job title as heading. Not needed.
We must not include boilerplate like EEO etc. Not present.
We must not include application instructions. Not present.
We must preserve all substantive information. So we need to include all details from the posting, but we can reorganize under headings.
We must not invent or summarize away detail. So we need to keep specifics like bullet points.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
At Synthpop, we're rebuilding the reality of what patient care can be... (the About Synthpop paragraph and Why this role is exciting paragraph). Might need to combine two paragraphs. Then
Responsibilities
- ... each bullet from "What you'll own"
Requirements
- ... each bullet from Qualifications (required)
Skills
- ... each bullet from Nice to have
Benefits
- ... each bullet from Benefits list
Pay
Base compensation: $135,000 - $150,000. Equity: Competitive early-stage equity.
ThenSchedule
Our core collaboration hours are generally 9 AM-6 PM Eastern. The role is based in the Boston/Cambridge area with an expectation of at least three days per week in the office (steady state), with some flexibility during onboarding or as business needs evolve. Occasional travel may be required for customer visits, industry events, or team gatherings.
We need to ensure we didn't miss any content: Also "Work environment and lifestyle" includes on-site collaboration, travel, core hours, physical requirements, accommodations. We incorporated those into Schedule and maybe also a note about physical requirements? We could add a sentence about physical requirements: "This role involves extended computer work and may include travel. We are happy to provide reasonable accommodations to support team members of all abilities." Could add to Schedule section or maybe a separate section? But we only have allowed headings; we could add to Schedule or About the role. Probably add to Schedule. Also "Why Synthpop?" section: we haven't included that. That's substantive content about company culture, mission, etc. Could be placed under About the role as well. So we can incorporate that paragraph into About the role. Thus About the role will include: About Synthpop paragraph, Why this role is exciting paragraph, Why Synthpop? paragraph. We must not repeat content; we need to ensure we include all. Let's extract the exact text blocks: About Synthpop: "At Synthpop, we're rebuilding the reality of what patient care can be. We believe every patient deserves a journey that is unexpectedly simple, effective, and attentive. We tackle complex administrative tasks such as referral processing and insurance verification, helping to lower costs, reduce errors, and ensure patients receive the coverage they need. Backed by decades of healthcare and tech experience, our team knows how to build scalable, reliable products for manufacturers, suppliers, and software solutions. By seamlessly integrating with existing infrastructure, our platform leverages AI agents, smart workflows, and adaptive communication strategies to ensure no patient falls through the cracks. If you're passionate about transforming healthcare operations and creating meaningful outcomes for patients, we'd love to have you join our team." Why this role is exciting: "This is Synthpop's first dedicated product marketing hire. You will build the function from zero to one and shape how the market understands a new category of healthcare AI. You will work directly with company leadership and partner closely with Engineering, Sales, Solutions Engineering, Customer Success, Design, and Brand to turn complex technology and healthcare workflows into crisp, credible narratives that move customers to action. The role is both strategic and hands-on. You will own positioning and go-to-market strategy for products and features, then roll up your sleeves to create the landing page, campaign brief, demo story, sales deck, and enablement materials needed to launch. If you thrive in ambiguity, learn through customer conversations, and love making complicated products feel obvious, this role offers rare scope and impact." What you'll own (list): - Positioning and messaging. Own the messaging architecture for Synthpop's platform, solutions, and priority healthcare workflows. Translate technical capabilities into differentiated value for clinical, operational, financial, and executive buyers. - Campaigns and launches. Build a repeatable launch engine for focused product campaigns, from audience insight and narrative development through landing pages, demos, content, enablement, and post-launch learning. - Customer and market intelligence. Develop a deep understanding of health systems, health plans, provider organizations, DME/HME operators, partners, competitors, and market dynamics. Turn customer evidence into sharper positioning, roadmap input, and go-to-market priorities. - Product storytelling and demos. Create compelling product narratives, demo flows, use-case pages, solution briefs, and customer-facing content that connect Synthpop's AI agents to concrete operational and patient outcomes. - Sales and customer enablement. Equip revenue teams with pitch decks, talk tracks, objection handling, proof points, ROI stories, competitive guidance, and training that improve consistency and confidence in complex sales cycles. - Cross-functional orchestration. Partner with Product and Engineering on roadmap context; with Sales and Customer Success on field insight; and with Design, Brand, and Demand Generation to ship cohesive campaigns quickly. - Measurement and iteration. Define success metrics for launches and assets, evaluate performance and qualitative feedback, and continuously improve messaging, channel strategy, and campaign execution. - The product marketing foundation. Establish the operating rhythms, templates, research practices, launch tiers, content standards, and source-of-truth materials that will scale with the company. What success looks like (list): - Synthpop has a clear, differentiated messaging that customers and internal teams can repeat consistently. - Priority campaigns move from concept to market quickly, with strong narratives, high-quality assets, and accountable launch plans. - Marketing, Sales, Solutions Engineering, and Customer Success have the tools and training to connect product capabilities to measurable healthcare outcomes. - Customer and market insight becomes a reliable input to product strategy, campaign priorities, and the company narrative. - A durable product marketing function is in place - rigorous enough to scale, lightweight enough to match an early-stage company. Qualifications (required): - 5+ years of product marketing experience in B2B software, including meaningful ownership of positioning, messaging, launches, and sales enablement. - Direct healthcare experience working with health systems, health plans, provider organizations, or healthcare operations teams; you understand how care delivery, reimbursement, and administrative workflows shape buying decisions. - Demonstrated zero-to-one experience building product marketing capabilities, launching a new product or category, or operating as an early marketing hire in a startup or high-growth environment. - Exceptional writing and storytelling skills, with a portfolio of messaging, launch, content, or enablement work that makes complex products clear and compelling. - Ability to move fluidly between strategy and execution - from market segmentation and positioning to drafting a landing page, structuring a demo, or polishing a sales deck. - Strong customer discovery and synthesis skills; you can identify patterns across interviews, field feedback, product data, and competitive research. - Strong cross-functional judgment and influence, especially with Product, Sales, Sales Engineering, Customer Success, Design, and executive stakeholders. - High ownership, urgency, attention to detail, and comfort making progress with incomplete information in a continually changing environment. - Ability to work from the Boston/Cambridge office at least three days per week in steady state. - High level experience using Coding agents Nice to have: - Experience marketing healthcare AI, workflow automation, enterprise SaaS, or another technically complex product in a regulated environment. - Knowledge of patient access, referral intake, eligibility and benefits, prior authorization, claims follow-up, revenue cycle, DME/HME, or payer operations. - Experience marketing to multiple buyer personas across operations, clinical leadership, finance, IT, compliance, and the C-suite. - Experience building high-fidelity demos, ROI tools, customer proof, competitive programs, or analyst-facing narratives. - Familiarity with modern content, design, analytics, and AI-assisted product marketing workflows. Work environment and lifestyle: - On-site collaboration: This role is based in the Boston/Cambridge area. The steady-state expectation is at least three days per week in the office, with some flexibility during onboarding or as business needs evolve. - Travel: Occasional travel may be required for customer visits, industry events, or team gatherings. - Schedule: Our core collaboration hours are generally 9 AM-6 PM Eastern. Success is defined by ownership - meeting responsibilities, goals, and commitments with flexibility in