Senior Product Manager, Acuity Scheduling, Payments

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. The posting includes: description of role (About the role?), responsibilities list, qualifications (Who We're Looking For), benefits & perks, cash compensation range, hybrid schedule (1-3 days a week in NYC). Also maybe "About Squarespace" but that's company description, not needed? Could be part of About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. We need to preserve all substantive info. Remove boilerplate: EEO, scam warning, application instructions, etc. Also remove duplicated lines. We need to decide which sections to include. - About the role: we have a paragraph describing role: "At Squarespace, we empower product teams... leading product management across Acuity's payments and mobile surfaces...". That's about the role. So we can put that in

About the role

with

. - Responsibilities: bullet list under "What You'll Do". So we can create

Responsibilities

with

• each bullet. - Requirements: maybe "Who We're Looking For" includes experience requirements. Could be Requirements or Qualifications. The instruction includes both Requirements and Qualifications as possible headings. We need to decide which to use. The posting has "Who We're Looking For" with bullet points of experience. That could be Requirements. Also there is "Nice to Have" which could be Skills? Or Qualifications? The instruction says we can have Skills section. We could put "Nice to Have" under Skills. Or we could combine Requirements (must-have) and Qualifications (nice-to-have). Let's map: Requirements (must-have): 6–8+ years product management experience in SaaS or consumer software, track record shipping products driving measurable outcomes; deep experience with payments, fintech, transaction products; experience leading mobile product development across iOS and Android; strong data and financial analysis skills; high technical fluency; proven ability to define right problem; excellent communication; customer-obsessed; comfortable challenging default approaches. Nice to Have: experience with in-person payments, POS integrations, hardware-adjacent product work; familiarity with scheduling, booking, or operational tools for SMBs. Thus we can have

  Requirements

  with must-have bullets, and

  Skills

  with nice-to-have bullets (or maybe Qualifications). But the instruction includes Qualifications as a possible heading. Could treat Requirements as must-have, Qualifications as nice-to-have. However they said "Prefer a few substantive sections over many thin ones." Might combine Requirements and Qualifications into one section? But they gave examples of headings; we can include both if they have content. Let's include Requirements (must-have) and Skills (nice-to-have). Or we could include Qualifications (nice-to-have). Let's decide: Use Requirements for must-have, Skills for nice-to-have. That seems logical. Benefits: we have "Benefits & Perks" list. So

  Benefits

  with
  . Pay: we have cash compensation range: $153,500 - $247,000 USD, plus note about base salary varying, plus eligibility for stock options. So we can include Pay section with that info. Schedule: hybrid role requiring 1–3 days a week in NYC office. So Schedule section. We must not include sections with filler like "commensurate with experience". Not present. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate: EEO, scam warning, application instructions, AI policy, etc. Also remove "About Squarespace" maybe? It's company description but not required; could be considered part of About the role? But we already have About the role describing the role. The "About Squarespace" paragraph is generic company info; could be omitted as not specific to role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The About Squarespace is substantive but maybe not needed for role? It's about company. Could be considered part of About the role? But we already have role description. The instruction says we can include sections only when posting has real specific content for it. The About Squarespace is generic but still specific to Squarespace. However it's not about the role. Might be considered boilerplate? It's not navigation/legal/EEO. It's about the company. Might be okay to keep but maybe not needed. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." About Squarespace is not those. So we could keep it as part of About the role? But we already have About the role describing the role; we could add a paragraph about Squarespace after that. However the instruction says "Prefer a few substantive sections over many thin ones." Might be okay to include About Squarespace as part of About the role section. Thus About the role section could contain two paragraphs: role description and company description. Let's extract the role description paragraph: "At Squarespace, we empower product teams to solve meaningful customer and business problems. We're looking for a Senior Product Manager to join the Acuity Scheduling team, leading product management across Acuity's payments and mobile surfaces for one of Squarespace's core scheduling products. Acuity Scheduling helps service businesses run their operations end-to-end: booking, client management, and getting paid. Payments is central to that value proposition, and it's one of Acuity's most significant growth opportunities. This role owns the strategy and execution for expanding how and where Acuity sellers collect revenue, building the payment experiences, defaults, and integrations that make on-platform collection the obvious choice across web, mobile, and emerging booking channels. This is a hybrid role, requiring 1–3 days a week in our New York City office. You will report to the Product Director on the Acuity Scheduling team." Note: The hybrid role sentence also belongs to Schedule maybe. But we can keep it in About the role or move to Schedule. Since Schedule section is separate, we might move the hybrid sentence to Schedule. However the instruction says we should not duplicate content. If we put hybrid in Schedule, we should not repeat it elsewhere. So we should extract that sentence for Schedule section. So About the role paragraph should exclude the hybrid sentence. Let's separate. Thus About the role paragraph: "At Squarespace, we empower product teams to solve meaningful customer and business problems. We're looking for a Senior Product Manager to join the Acuity Scheduling team, leading product management across Acuity's payments and mobile surfaces for one of Squarespace's core scheduling products. Acuity Scheduling helps service businesses run their operations end-to-end: booking, client management, and getting paid. Payments is central to that value proposition, and it's one of Acuity's most significant growth opportunities. This role owns the strategy and execution for expanding how and where Acuity sellers collect revenue, building the payment experiences, defaults, and integrations that make on-platform collection the obvious choice across web, mobile, and emerging booking channels. You will report to the Product Director on the Acuity Scheduling team." Now Schedule section: "This is a hybrid role, requiring 1–3 days a week in our New York City office." Now Responsibilities: list from "What You'll Do". Let's extract each bullet: - Own the long-term strategy and roadmap for payments, transactions, and mobile on Acuity - Lead rigorous problem discovery, deeply understanding customer, business, and market dynamics before pursuing major investments - Develop evidence-based problem statements grounded in user research, competitive analysis, and financial data - Define target segments, primary use cases, and expansion opportunities across web, mobile, and in-person payment contexts - Balance partner, build, buy, and deprecate decisions to accelerate GPV growth and customer impact - Drive payment integrations and checkout UX across Acuity's web and mobile surfaces - Leverage relationships with external partners to address areas of opportunity where Acuity can serve customers in a distinctive way - Partner with marketing to launch new products, with customer operations to develop excellent merchant support, and with analytics to monitor engagement and evaluate success - Own the key metrics for your business area, explain trends, and build shared understanding across teams and stakeholders - Create alignment across stakeholders through clear narratives, documentation, and prioritization frameworks Now Requirements (must-have): list from "Who We're Looking For" before "Nice to Have". Let's extract: - 6–8+ years of product management experience in SaaS or consumer software, with a track record of shipping products that drive measurable business outcomes - Deep experience with payments, fintech, or transaction products, including third-party integrations, checkout UX, and payment infrastructure - Experience leading mobile product development across iOS and Android surfaces - Strong data and financial analysis skills, with experience sizing opportunities and validating demand - High technical fluency; comfortable partnering on complex workflows, data models, and platform integrations - Proven ability to define the right problem before designing solutions, resistant to premature solutioning - Excellent communication and interpersonal skills, with demonstrated ability to align cross-functional teams around business goals - Customer-obsessed, with a history of conducting research, customer interviews, and usability testing to inform decisions - Comfortable challenging default approaches when they conflict with user or commercial outcomes Now Skills (nice-to-have): list: - Experience with in-person payments, POS integrations, or hardware-adjacent product work - Familiarity with scheduling, booking, or operational tools for SMBs Now Benefits: list from "Benefits & Perks". Let's extract each bullet: - A choice between medical plans with an option for 100% covered premiums - Fertility and adoption benefits - Access to supplemental insurance plans for additional coverage - Headspace mindfulness app subscription - Global Employee Assistance Program - Retirement benefits with employer match - Flexible paid time off - 12 weeks paid parental leave and family care leave - Pretax commuter benefit - Education reimbursement - Employee donation match to community organizations - 7 Global Employee Resource Groups (ERGs) - Dog-friendly workplace - Free lunch and snacks - Private rooftop - Hack week twice per year Now Pay: we have "Cash Compensation Range: $153,500 - $247,000 USD The base salary for this position will vary based on job-related criteria including relevant skills, experience, and location, among other factors. In addition to the cash compensation above (which includes base salary and, where applicable for eligible roles, may include overtime pay), Squarespace employees are eligible to be granted an option to purchase our common stock. Sales positions generally offer a competitive On Target Earnings (OTE) incentive structure in addition to base salary." We need to preserve all substantive info. So we can put that in Pay section as a paragraph. Now we must not include sections like "About Squarespace" (we omitted). Also remove "Our Commitment" EEO etc. Also remove "Thank you in advance for providing the following details..." etc. Also remove "Squarespace will never solicit your personal banking information..." etc. Also remove "If you plan to use AI..." etc. Now produce HTML fragment with

  headings and appropriate

  or

  • . Ensure no extra text outside. Let's craft:

    About the role

    At Squarespace, we empower product teams to solve meaningful customer and business problems. We're looking for a Senior Product Manager to join the Acuity Scheduling team, leading product management across Acuity's payments and mobile surfaces for one of Squarespace's core