Customer Success Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have content for Responsibilities (What You'll Do). For Requirements/Qualifications (What You'll Bring). For Skills (Tools we use maybe). For Benefits (What We Provide). Possibly also About the role could be a brief summary? The role description includes "The role You'll manage customer onboarding..." That's more like overview. Could be "About the role". Might be okay. But we must not repeat job title as heading. No job title given explicitly. So we can include About the role as a short paragraph summarizing the role. Ensure we preserve all substantive info; we must not invent or summarize away detail. We need to keep details.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to remove boilerplate etc. There's none.
We need to output only HTML fragment.
Let's extract content:
Company description: "About Dots Dots (usedots.com) is a Series A fintech backed by Y Combinator and DCM, building payout infrastructure for marketplaces and digital platforms. In the past year, we have grown our revenues by over 400%, and have built a deep base of loyal customers. Since our founding 4 years ago, we’ve moved nearly $3 billion per year to more than 1 million payees across 190+ countries, helping businesses onboard, pay and manage recipients around the world."
That's about company, not role. Could be placed maybe as a preamble before sections? Not required but we can include as a
before sections. The instruction: output only HTML fragment; we can include that as a
before headings.
Then sections:
About the role: maybe a short paragraph summarizing: "You'll manage customer onboarding, retention and growth, while also running our full-time and contract support team. You'll carry your own accounts, help customers navigate complex payout issues and decide which recurring problems should be solved through better process, automation or product. You'll own the process of taking customers from signing a contract to going live, and beyond. You report directly to the founders."
That's from "The role" paragraph.
Responsibilities: from "What You'll Do" bullet points (though not bullet list originally but paragraphs). We need to turn into
- . Let's list each duty:
- Onboarding & implementation: Own customers from signed contract through their first successful payouts. Understand what each customer is trying to build, help them choose the right Dots implementation and coordinate verification, integration, testing and launch. Keep implementations moving, unblock customers and shorten the path from signature to first transaction.
- Retention & growth: Own a portfolio of customers after launch and build strong, ongoing relationships with them. Identify retention risk early, improve adoption and make sure customers continue getting value from Dots. Look for opportunities to grow accounts through increased payout volume, additional products or expansion into new parts of a customer's business.
- Support: Run our support function, including our full-time and contract support team. Set a high bar for response quality, escalation and follow-through. Get technical when something breaks: use our docs, logs and internal tools to understand payout issues before escalating to engineering.
- Systems & customer voice: Build the customer success systems we don't have yet: onboarding processes, account-health signals, escalation paths and playbooks. Identify recurring customer problems and decide what we should automate, document or ask product and engineering to eliminate. Bring customer feedback, patterns and opportunities back to the founders and product team.
We'll make each as
- containing the prose (maybe multiple sentences). Could also split each bullet into separate
- for each subpoint but instruction: use
- for any list of duties/requirements/benefits. So we can treat each major heading as a list item.
Requirements/Qualifications: from "What You'll Bring". It lists:
- 3+ years in customer success, implementation or account management at a B2B software, fintech company, or marketplace.
- Experience owning enterprise onboarding and shortening the path from signature to first transaction.
- Experience managing customers after launch, including retention, adoption and account growth.
- The ability to build strong customer relationships while still pushing projects forward.
- Enough technical fluency to read API docs, dig through logs and investigate why a payout failed before escalating.
- Experience building onboarding, customer health or escalation processes from scratch.
- The ability and desire to run a support team while carrying your own accounts.
Bonus points: Worked in fintech or finance, ideally in payments or payouts. Managed a mixed team of full-time employees and contractors. Scaled support from a shared inbox into a more structured function.
We can include bonus as part of qualifications maybe as separate list items marked as bonus? But we should preserve all info. Could include them as list items with note "(Bonus)".
Skills: "Tools we use": Intercom and Pylon for support, Linear for engineering escalations, Slack and Notion.
We can list as
- Intercom and Pylon for support
etc.
Benefits: "What We Provide": Private medical insurance, including dental and vision, Unlimited vacation policy, Regular team off-sites, 401k plan.
We'll list as - .
No Pay or Schedule.
Now produce HTML.
We need to wrap sections in
headings.
Order: maybe About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. But Requirements and Qualifications could be combined? The instruction list includes both; we can have both if content distinct. We have qualifications (what you'll bring) and maybe requirements similar. Could treat "What You'll Bring" as Requirements and Qualifications combined. But we need to decide. To avoid thin sections, we could have Requirements (including qualifications) and Skills separate. But we have both Requirements and Qualifications headings; we could put the list under Requirements and leave Qualifications empty? Not allowed: cannot emit heading followed by filler. So we should only include headings that have real content. So we need to decide which headings to use.
We have content for: About the role (overview), Responsibilities (What You'll Do), Requirements (What You'll Bring), Skills (Tools we use), Benefits (What We Provide). Qualifications maybe same as Requirements; we could omit Qualifications heading. Pay and Schedule omitted.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits.
Check if we need to separate Requirements and Qualifications? The instruction says use those headings as examples, but we can omit if not needed. We'll include Requirements for the experience list, and maybe Qualifications for the bonus points? Could split: Requirements = core requirements, Qualifications = bonus points. That would give both headings content. Let's do that.
Thus:
- Requirements: core requirements (first 7 bullet points).
- Qualifications: bonus points (3 items).
Skills: Tools we use.
Now produce HTML.
We'll start with a
for company description maybe.
Then
About the role
...
Then Responsibilities
- ...
...
Then Requirements
- ...
...
Then Qualifications
- ...
...
Then Skills
- ...
...
Then Benefits
- ...
...
Make sure to preserve all details exactly.
Let's copy the text.
Company description paragraph: "About Dots Dots (usedots.com) is a Series A fintech backed by Y Combinator and DCM, building payout infrastructure for marketplaces and digital platforms. In the past year, we have grown our revenues by over 400%, and have built a deep base of loyal customers. Since our founding 4 years ago, we’ve moved nearly $3 billion per year to more than 1 million payees across 190+ countries, helping businesses onboard, pay and manage recipients around the world."
We'll output as About Dots Dots (usedots.com) is a Series A fintech backed by Y Combinator and DCM, building payout infrastructure for marketplaces and digital platforms. In the past year, we have grown our revenues by over 400%, and have built a deep base of loyal customers. Since our founding 4 years ago, we’ve moved nearly $3 billion per year to more than 1 million payees across 190+ countries, helping businesses onboard, pay and manage recipients around the world.
Now About the role paragraph: "You'll manage customer onboarding, retention and growth, while also running our full-time and contract support team. You'll carry your own accounts, help customers navigate complex payout issues and decide which recurring problems should be solved through better process, automation or product. You'll own the process of taking customers from signing a contract to going live, and beyond. You report directly to the founders."
We'll put in .
Now Responsibilities list items:
We need to keep the exact phrasing.
Item 1: "Onboarding & implementation Own customers from signed contract through their first successful payouts.Understand what each customer is trying to build, help them choose the right Dots implementation and coordinate verification, integration, testing and launch.Keep implementations moving, unblock customers and shorten the path from signature to first transaction."
Note there is missing spaces after periods? In original: "Own customers from signed contract through their first successful payouts.Understand what each customer is trying to build, help them choose the right Dots implementation and coordinate verification, integration, testing and launch.Keep implementations moving, unblock customers and shorten the path from signature to first transaction." We'll keep as is but maybe add a space after periods for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Adding spaces is not changing substantive info, it's just formatting. Probably okay. But to be safe, keep exactly as original? The original lacks spaces; we could keep that. However readability not required. I'll keep original string.
Item 2: "Retention & growth Own a portfolio of customers after launch and build strong, ongoing relationships with them.Identify retention risk early, improve adoption and make sure customers continue getting value from Dots.Look for opportunities to grow accounts through increased payout volume, additional products or expansion into new parts of a customer's business."
Item 3: "Support Run our support function, including our full-time and contract support team.Set a high bar for response quality, escalation and follow-through.Get technical when something breaks: use our docs, logs and internal tools to understand payout issues before escalating to engineering."
Item 4: "Systems & customer voice Build the customer success systems we don't have yet: onboarding processes, account-health signals, escalation paths and playbooks.Identify recurring customer problems and decide what we should automate, document or ask product and engineering to eliminate.Bring customer feedback, patterns and opportunities back to the founders and product team."
Now Requirements list (core):
- "3+ years in customer success, implementation or account management at a
for prose. We need to remove boilerplate etc. There's none. We need to output only HTML fragment. Let's extract content: Company description: "About Dots Dots (usedots.com) is a Series A fintech backed by Y Combinator and DCM, building payout infrastructure for marketplaces and digital platforms. In the past year, we have grown our revenues by over 400%, and have built a deep base of loyal customers. Since our founding 4 years ago, we’ve moved nearly $3 billion per year to more than 1 million payees across 190+ countries, helping businesses onboard, pay and manage recipients around the world." That's about company, not role. Could be placed maybe as a preamble before sections? Not required but we can include as a
before sections. The instruction: output only HTML fragment; we can include that as a
before headings. Then sections: About the role: maybe a short paragraph summarizing: "You'll manage customer onboarding, retention and growth, while also running our full-time and contract support team. You'll carry your own accounts, help customers navigate complex payout issues and decide which recurring problems should be solved through better process, automation or product. You'll own the process of taking customers from signing a contract to going live, and beyond. You report directly to the founders." That's from "The role" paragraph. Responsibilities: from "What You'll Do" bullet points (though not bullet list originally but paragraphs). We need to turn into
- . Let's list each duty: - Onboarding & implementation: Own customers from signed contract through their first successful payouts. Understand what each customer is trying to build, help them choose the right Dots implementation and coordinate verification, integration, testing and launch. Keep implementations moving, unblock customers and shorten the path from signature to first transaction. - Retention & growth: Own a portfolio of customers after launch and build strong, ongoing relationships with them. Identify retention risk early, improve adoption and make sure customers continue getting value from Dots. Look for opportunities to grow accounts through increased payout volume, additional products or expansion into new parts of a customer's business. - Support: Run our support function, including our full-time and contract support team. Set a high bar for response quality, escalation and follow-through. Get technical when something breaks: use our docs, logs and internal tools to understand payout issues before escalating to engineering. - Systems & customer voice: Build the customer success systems we don't have yet: onboarding processes, account-health signals, escalation paths and playbooks. Identify recurring customer problems and decide what we should automate, document or ask product and engineering to eliminate. Bring customer feedback, patterns and opportunities back to the founders and product team. We'll make each as
- containing the prose (maybe multiple sentences). Could also split each bullet into separate
- for each subpoint but instruction: use
- for any list of duties/requirements/benefits. So we can treat each major heading as a list item.
Requirements/Qualifications: from "What You'll Bring". It lists:
- 3+ years in customer success, implementation or account management at a B2B software, fintech company, or marketplace.
- Experience owning enterprise onboarding and shortening the path from signature to first transaction.
- Experience managing customers after launch, including retention, adoption and account growth.
- The ability to build strong customer relationships while still pushing projects forward.
- Enough technical fluency to read API docs, dig through logs and investigate why a payout failed before escalating.
- Experience building onboarding, customer health or escalation processes from scratch.
- The ability and desire to run a support team while carrying your own accounts.
Bonus points: Worked in fintech or finance, ideally in payments or payouts. Managed a mixed team of full-time employees and contractors. Scaled support from a shared inbox into a more structured function.
We can include bonus as part of qualifications maybe as separate list items marked as bonus? But we should preserve all info. Could include them as list items with note "(Bonus)".
Skills: "Tools we use": Intercom and Pylon for support, Linear for engineering escalations, Slack and Notion.
We can list as
- Intercom and Pylon for support etc. Benefits: "What We Provide": Private medical insurance, including dental and vision, Unlimited vacation policy, Regular team off-sites, 401k plan. We'll list as
- .
No Pay or Schedule.
Now produce HTML.
We need to wrap sections in
headings. Order: maybe About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. But Requirements and Qualifications could be combined? The instruction list includes both; we can have both if content distinct. We have qualifications (what you'll bring) and maybe requirements similar. Could treat "What You'll Bring" as Requirements and Qualifications combined. But we need to decide. To avoid thin sections, we could have Requirements (including qualifications) and Skills separate. But we have both Requirements and Qualifications headings; we could put the list under Requirements and leave Qualifications empty? Not allowed: cannot emit heading followed by filler. So we should only include headings that have real content. So we need to decide which headings to use. We have content for: About the role (overview), Responsibilities (What You'll Do), Requirements (What You'll Bring), Skills (Tools we use), Benefits (What We Provide). Qualifications maybe same as Requirements; we could omit Qualifications heading. Pay and Schedule omitted. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits. Check if we need to separate Requirements and Qualifications? The instruction says use those headings as examples, but we can omit if not needed. We'll include Requirements for the experience list, and maybe Qualifications for the bonus points? Could split: Requirements = core requirements, Qualifications = bonus points. That would give both headings content. Let's do that. Thus: - Requirements: core requirements (first 7 bullet points). - Qualifications: bonus points (3 items). Skills: Tools we use. Now produce HTML. We'll start with a
for company description maybe. Then
About the role
...
ThenResponsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
About Dots Dots (usedots.com) is a Series A fintech backed by Y Combinator and DCM, building payout infrastructure for marketplaces and digital platforms. In the past year, we have grown our revenues by over 400%, and have built a deep base of loyal customers. Since our founding 4 years ago, we’ve moved nearly $3 billion per year to more than 1 million payees across 190+ countries, helping businesses onboard, pay and manage recipients around the world.
Now About the role paragraph: "You'll manage customer onboarding, retention and growth, while also running our full-time and contract support team. You'll carry your own accounts, help customers navigate complex payout issues and decide which recurring problems should be solved through better process, automation or product. You'll own the process of taking customers from signing a contract to going live, and beyond. You report directly to the founders." We'll put in. Now Responsibilities list items: We need to keep the exact phrasing. Item 1: "Onboarding & implementation Own customers from signed contract through their first successful payouts.Understand what each customer is trying to build, help them choose the right Dots implementation and coordinate verification, integration, testing and launch.Keep implementations moving, unblock customers and shorten the path from signature to first transaction." Note there is missing spaces after periods? In original: "Own customers from signed contract through their first successful payouts.Understand what each customer is trying to build, help them choose the right Dots implementation and coordinate verification, integration, testing and launch.Keep implementations moving, unblock customers and shorten the path from signature to first transaction." We'll keep as is but maybe add a space after periods for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Adding spaces is not changing substantive info, it's just formatting. Probably okay. But to be safe, keep exactly as original? The original lacks spaces; we could keep that. However readability not required. I'll keep original string. Item 2: "Retention & growth Own a portfolio of customers after launch and build strong, ongoing relationships with them.Identify retention risk early, improve adoption and make sure customers continue getting value from Dots.Look for opportunities to grow accounts through increased payout volume, additional products or expansion into new parts of a customer's business." Item 3: "Support Run our support function, including our full-time and contract support team.Set a high bar for response quality, escalation and follow-through.Get technical when something breaks: use our docs, logs and internal tools to understand payout issues before escalating to engineering." Item 4: "Systems & customer voice Build the customer success systems we don't have yet: onboarding processes, account-health signals, escalation paths and playbooks.Identify recurring customer problems and decide what we should automate, document or ask product and engineering to eliminate.Bring customer feedback, patterns and opportunities back to the founders and product team." Now Requirements list (core): - "3+ years in customer success, implementation or account management at a
- for any list of duties/requirements/benefits. So we can treat each major heading as a list item.
Requirements/Qualifications: from "What You'll Bring". It lists:
- 3+ years in customer success, implementation or account management at a B2B software, fintech company, or marketplace.
- Experience owning enterprise onboarding and shortening the path from signature to first transaction.
- Experience managing customers after launch, including retention, adoption and account growth.
- The ability to build strong customer relationships while still pushing projects forward.
- Enough technical fluency to read API docs, dig through logs and investigate why a payout failed before escalating.
- Experience building onboarding, customer health or escalation processes from scratch.
- The ability and desire to run a support team while carrying your own accounts.
Bonus points: Worked in fintech or finance, ideally in payments or payouts. Managed a mixed team of full-time employees and contractors. Scaled support from a shared inbox into a more structured function.
We can include bonus as part of qualifications maybe as separate list items marked as bonus? But we should preserve all info. Could include them as list items with note "(Bonus)".
Skills: "Tools we use": Intercom and Pylon for support, Linear for engineering escalations, Slack and Notion.
We can list as