Associate Customer Success Manager
Conga · United States · 2 wk ago
RemoteRemoteOTHR$69k–$110k/yrFull-time
We need to output only HTML fragment, using for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- About the role: description of Conga, mission, etc. Probably we can put a paragraph summarizing.
- Responsibilities: list of duties: manage book of global complex customers, adoption analysis, joint planning, value realization activities, drive customer advocacy, ensure technical issues resolved, facilitator, coach, consultant, ask questions, etc. Also drive adoption, identify expansion, own mitigation of risk, improve health and sentiment, ensure successful renewal.
- Requirements: Education: Bachelor's degree or equivalent hands‑on experience. Experience: 2–4 years in a customer-facing role (Customer Success, Sales, SDR/BDR, or Technical Support). Consideration will be given to candidates who may not have direct experience but can clearly articulate outcomes, autonomy, impact, and leadership in other capacities.
- Qualifications: maybe same as requirements? But we can treat "What We’re Looking For...." as qualifications/skills. The bullet list includes consultative mindset, proactive collaborator, communication & delivery, technical proficiency, high-growth adaptability, customer retention focus, customer engagement & adoption, cross-functional collaboration, data driven, problem solver. Also "Here’s What Will Give You An Edge Experience with SaaS/cloud solutions; CLM, CPQ, Salesforce, or Conga experience highly desirable." That could be under Skills or Qualifications.
- Skills: maybe list technical proficiency: Salesforce, Microsoft tools, AI, etc.
- Benefits: The posting mentions variable incentive pay component, perks such as flexible work options, full range of benefits including medical and dental insurance. Also "In the spirit of the Conga Way, we strive to design easy-to-understand compensation programs...". Also "Travel Requirements Includes approximately 4x per year for quarterly Conga events and as-needed travel to customer onsite meetings." Travel could be under Schedule? Not exactly schedule. But we have a Schedule section only if posting actually states schedule. It mentions remote highly preferred Eastern or Central Time Zone. That's location/time zone, not schedule. No explicit schedule like full-time, hours. Could infer full-time but not explicit. Probably we should not create Schedule section unless explicit. The posting does not give schedule like "Monday-Friday 9-5". So we skip Schedule.
- Pay: The posting includes U.S Base Salary Range $68,742—$109,989 USD. Also mentions variable incentive pay component. So we can include Pay section with that info.
- Benefits: we have medical and dental insurance, flexible work options, variable incentive pay (though that's compensation). Also maybe "perks such as flexible work options". We'll include Benefits.
We must not include boilerplate like EEO, Equal Opportunity Employer, privacy statement, etc. Also remove "Did we pique your interest? If this sounds like the kind of job you would love..." etc. Also remove "Preferred Resume Format", "Additional Information", etc.
We need to preserve all substantive information. So we need to include the location: Remote- Highly preferred Eastern or Central Time Zone. Where to put? Could be under About the role or maybe a separate section? There's no heading for location; we could embed in a paragraph under About the role or maybe under Responsibilities? Probably best to put in About the role as a sentence.
Also "Reports to: Senior Manager, Customer Success" - could be included in About the role.
We need to not repeat job title as heading. So we won't have heading "Associate Customer Success Manager". We'll just have sections.
We must output only HTML fragment, no or . Use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- About the role: description of Conga, mission, etc. Probably we can put a paragraph summarizing.
- Responsibilities: list of duties: manage book of global complex customers, adoption analysis, joint planning, value realization activities, drive customer advocacy, ensure technical issues resolved, facilitator, coach, consultant, ask questions, etc. Also drive adoption, identify expansion, own mitigation of risk, improve health and sentiment, ensure successful renewal.
- Requirements: Education: Bachelor's degree or equivalent hands‑on experience. Experience: 2–4 years in a customer-facing role (Customer Success, Sales, SDR/BDR, or Technical Support). Consideration will be given to candidates who may not have direct experience but can clearly articulate outcomes, autonomy, impact, and leadership in other capacities.
- Qualifications: maybe same as requirements? But we can treat "What We’re Looking For...." as qualifications/skills. The bullet list includes consultative mindset, proactive collaborator, communication & delivery, technical proficiency, high-growth adaptability, customer retention focus, customer engagement & adoption, cross-functional collaboration, data driven, problem solver. Also "Here’s What Will Give You An Edge Experience with SaaS/cloud solutions; CLM, CPQ, Salesforce, or Conga experience highly desirable." That could be under Skills or Qualifications.
- Skills: maybe list technical proficiency: Salesforce, Microsoft tools, AI, etc.
- Benefits: The posting mentions variable incentive pay component, perks such as flexible work options, full range of benefits including medical and dental insurance. Also "In the spirit of the Conga Way, we strive to design easy-to-understand compensation programs...". Also "Travel Requirements Includes approximately 4x per year for quarterly Conga events and as-needed travel to customer onsite meetings." Travel could be under Schedule? Not exactly schedule. But we have a Schedule section only if posting actually states schedule. It mentions remote highly preferred Eastern or Central Time Zone. That's location/time zone, not schedule. No explicit schedule like full-time, hours. Could infer full-time but not explicit. Probably we should not create Schedule section unless explicit. The posting does not give schedule like "Monday-Friday 9-5". So we skip Schedule.
- Pay: The posting includes U.S Base Salary Range $68,742—$109,989 USD. Also mentions variable incentive pay component. So we can include Pay section with that info.
- Benefits: we have medical and dental insurance, flexible work options, variable incentive pay (though that's compensation). Also maybe "perks such as flexible work options". We'll include Benefits.
We must not include boilerplate like EEO, Equal Opportunity Employer, privacy statement, etc. Also remove "Did we pique your interest? If this sounds like the kind of job you would love..." etc. Also remove "Preferred Resume Format", "Additional Information", etc.
We need to preserve all substantive information. So we need to include the location: Remote- Highly preferred Eastern or Central Time Zone. Where to put? Could be under About the role or maybe a separate section? There's no heading for location; we could embed in a paragraph under About the role or maybe under Responsibilities? Probably best to put in About the role as a sentence.
Also "Reports to: Senior Manager, Customer Success" - could be included in About the role.
We need to not repeat job title as heading. So we won't have heading "Associate Customer Success Manager". We'll just have sections.
We must output only HTML fragment, no or . Use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide which sections to include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also "Travel" but not a standard heading; maybe we can include under Benefits or Responsibilities? Travel is a requirement? It's a travel requirement. Could be under Responsibilities? Not exactly. Could be under Benefits? Not really. Could be under a separate section "Travel" but not in allowed headings list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use for section headings (e.g. ...)". Likely they expect only those headings. So we should map content to those headings. Travel could be placed under Benefits? Not ideal. Could be under Responsibilities as a duty? Travel is not a duty but a requirement. Could be under Requirements? Not exactly. Could be under Pay? No. Could be under Schedule? Not schedule. Could be under About the role? Might be okay to mention travel expectation there.
We'll include travel in About the role or maybe under Responsibilities as a bullet: "Travel approximately 4 times per year for quarterly Conga events and as-needed customer onsite meetings."
Now, we need to avoid filler like "commensurate with experience". Not present.
We need to ensure we don't create sections with placeholder text. So we will only include sections where we have substantive content.
Let's draft:
About the role
Conga builds a community where colleagues can thrive, aligning pricing, quoting, contracting, rebates, and communications so companies run as connected, smarter businesses. Over 10,000 customers worldwide, including over 50% of the Fortune 100, trust Conga when commercial complexity is high. This full‑time, remote‑preferred role (Eastern or Central Time Zone) reports to the Senior Manager, Customer Success. The Associate Customer Success Manager manages a book of global, complex customers who have invested in Conga to power their revenue operations.
Responsibilities
- Manage a book of global, complex customers.
- Perform detailed adoption analysis and engage customers in joint planning to increase adoption.
- Lead value realization activities such as customer stakeholder alignment and roadmap reviews.
- Drive customer advocacy by ensuring technical issues are resolved quickly and efficiently with internal Conga partners.
- Act as a facilitator, coach, and consultant, continuously asking questions to deeply understand customers.
- Drive product adoption, identify expansion opportunities, own risk mitigation using cross‑functional teams.
- Improve health and sentiment of Conga’s customers to ensure successful and growing renewals.
- Travel approximately four times per year for quarterly Conga events and as‑needed customer onsite meetings.
Requirements
- Bachelor’s degree or equivalent hands‑on experience.
- 2–4 years in a customer‑facing role (Customer Success, Sales, SDR/BDR, or Technical Support).
- Consideration given to candidates without direct experience who can articulate outcomes, autonomy, impact, and leadership in other capacities.
Qualifications
- Consultative mindset: builds trust and credibility by actively listening, understanding needs, and tailoring solutions for a wide range of stakeholders.
- Proactive collaborator: self‑starter who takes initiative while working effectively with others to achieve shared goals.
- Communication & delivery: strong written, verbal, presentation, and project management skills to influence, align, and execute.
- Technical proficiency: confident using Salesforce and Microsoft tools (Outlook, Word, Excel, PowerPoint) as well as AI to manage work efficiently.
- High‑growth adaptability: thrives in fast‑paced environments, juggling multiple priorities with a structured, data‑driven approach.
- Customer retention focus: proven track record of strengthening relationships and driving long‑term customer retention.
- Customer engagement & adoption: comfortable working with customers at varying levels of engagement and adoption; demonstrates urgency, persistence, and creativity in re‑engaging customers, driving product adoption, mitigating risk, and helping customers realize value.
- Cross‑functional collaboration: effectively aligns cross‑functional teams to deliver strong customer outcomes.
- Data driven: uses data‑driven insights to identify growth opportunities and accelerate value realization across accounts.
- Problem solver: sees a problem as a creative opportunity rather than a blocker and uses curiosity, creativity, and persistence to address uncertainty and ambiguity.
Skills
- Experience with SaaS/cloud solutions; CLM, CPQ, Salesforce, or Conga experience highly desirable.
- Proficiency with Salesforce and Microsoft Office suite (Outlook, Word, Excel, PowerPoint).
- Ability to leverage AI tools for efficient work management.
Benefits
- Variable incentive pay component.
- Flexible work options.
- Full range of benefits including medical and dental insurance.
Pay
U.S. base salary range: $68,742 – $109,989 USD (full‑time). Individual pay determined by job‑related skills, experience, and relevant education or training.
We should not include Schedule section because no explicit schedule.
Check for any duplicated content: We have covered responsibilities, requirements, qualifications, skills, benefits, pay. Ensure we didn't miss any substantive info: The posting also mentions "In the spirit of the Conga Way, we strive to design easy-to-understand compensation programs that are fair and free from any type of discrimination." That's somewhat boilerplate; we could omit as it's more about compensation philosophy but maybe considered substantive? It's about compensation programs; but we already have Pay and Benefits. Could be omitted as it's somewhat generic. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly EEO but it's about compensation philosophy; could be considered boilerplate? It's somewhat generic but still part of compensation description. Might be okay to keep but we already have Pay and Benefits. It's not required. Safer to omit.
Also "We are often open to a wide variety of profiles and sometimes have flexibility within our organizational structure to adjust the role responsibilities up or down should we select a candidate that is less or more experienced than the posted job requirements. In these occasional cases, we will communicate the revised salary range to the candidate during the selection process." This is also somewhat generic but could be considered substantive about flexibility. Might be okay to include under Pay or Requirements? Could be under Pay as a note. But it's somewhat generic; but it's about salary range flexibility. Might be considered substantive. However, the instruction says prefer a few substantive sections over many thin ones. We could incorporate that into Pay section as a note.
Let's add a sentence in Pay: "Conga may adjust responsibilities and salary range based on candidate experience; any revised range would be communicated during selection."
Now check for any other substantive info: "Preferred Resume Format We accept resumes in any format, we suggest using PDF or plain text." That's application instruction; remove.
"Did we pique your interest? If this sounds like the kind of job you would love in the kind of environment where you would thrive, please click apply. We'd love to hear from you!" Remove.
"Additional Information Conga is proud to be an Equal Opportunity Employer..." Remove EEO.
"Conga is not open to third party solic
- for any list of duties/requirements/benefits. Use
for prose. We need to decide which sections to include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also "Travel" but not a standard heading; maybe we can include under Benefits or Responsibilities? Travel is a requirement? It's a travel requirement. Could be under Responsibilities? Not exactly. Could be under Benefits? Not really. Could be under a separate section "Travel" but not in allowed headings list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use
for section headings (e.g. ...)". Likely they expect only those headings. So we should map content to those headings. Travel could be placed under Benefits? Not ideal. Could be under Responsibilities as a duty? Travel is not a duty but a requirement. Could be under Requirements? Not exactly. Could be under Pay? No. Could be under Schedule? Not schedule. Could be under About the role? Might be okay to mention travel expectation there. We'll include travel in About the role or maybe under Responsibilities as a bullet: "Travel approximately 4 times per year for quarterly Conga events and as-needed customer onsite meetings." Now, we need to avoid filler like "commensurate with experience". Not present. We need to ensure we don't create sections with placeholder text. So we will only include sections where we have substantive content. Let's draft:
About the role
Conga builds a community where colleagues can thrive, aligning pricing, quoting, contracting, rebates, and communications so companies run as connected, smarter businesses. Over 10,000 customers worldwide, including over 50% of the Fortune 100, trust Conga when commercial complexity is high. This full‑time, remote‑preferred role (Eastern or Central Time Zone) reports to the Senior Manager, Customer Success. The Associate Customer Success Manager manages a book of global, complex customers who have invested in Conga to power their revenue operations.
Responsibilities
- Manage a book of global, complex customers.
- Perform detailed adoption analysis and engage customers in joint planning to increase adoption.
- Lead value realization activities such as customer stakeholder alignment and roadmap reviews.
- Drive customer advocacy by ensuring technical issues are resolved quickly and efficiently with internal Conga partners.
- Act as a facilitator, coach, and consultant, continuously asking questions to deeply understand customers.
- Drive product adoption, identify expansion opportunities, own risk mitigation using cross‑functional teams.
- Improve health and sentiment of Conga’s customers to ensure successful and growing renewals.
- Travel approximately four times per year for quarterly Conga events and as‑needed customer onsite meetings.
Requirements
- Bachelor’s degree or equivalent hands‑on experience.
- 2–4 years in a customer‑facing role (Customer Success, Sales, SDR/BDR, or Technical Support).
- Consideration given to candidates without direct experience who can articulate outcomes, autonomy, impact, and leadership in other capacities.
Qualifications
- Consultative mindset: builds trust and credibility by actively listening, understanding needs, and tailoring solutions for a wide range of stakeholders.
- Proactive collaborator: self‑starter who takes initiative while working effectively with others to achieve shared goals.
- Communication & delivery: strong written, verbal, presentation, and project management skills to influence, align, and execute.
- Technical proficiency: confident using Salesforce and Microsoft tools (Outlook, Word, Excel, PowerPoint) as well as AI to manage work efficiently.
- High‑growth adaptability: thrives in fast‑paced environments, juggling multiple priorities with a structured, data‑driven approach.
- Customer retention focus: proven track record of strengthening relationships and driving long‑term customer retention.
- Customer engagement & adoption: comfortable working with customers at varying levels of engagement and adoption; demonstrates urgency, persistence, and creativity in re‑engaging customers, driving product adoption, mitigating risk, and helping customers realize value.
- Cross‑functional collaboration: effectively aligns cross‑functional teams to deliver strong customer outcomes.
- Data driven: uses data‑driven insights to identify growth opportunities and accelerate value realization across accounts.
- Problem solver: sees a problem as a creative opportunity rather than a blocker and uses curiosity, creativity, and persistence to address uncertainty and ambiguity.
Skills
- Experience with SaaS/cloud solutions; CLM, CPQ, Salesforce, or Conga experience highly desirable.
- Proficiency with Salesforce and Microsoft Office suite (Outlook, Word, Excel, PowerPoint).
- Ability to leverage AI tools for efficient work management.
Benefits
- Variable incentive pay component.
- Flexible work options.
- Full range of benefits including medical and dental insurance.
Pay
U.S. base salary range: $68,742 – $109,989 USD (full‑time). Individual pay determined by job‑related skills, experience, and relevant education or training.
We should not include Schedule section because no explicit schedule. Check for any duplicated content: We have covered responsibilities, requirements, qualifications, skills, benefits, pay. Ensure we didn't miss any substantive info: The posting also mentions "In the spirit of the Conga Way, we strive to design easy-to-understand compensation programs that are fair and free from any type of discrimination." That's somewhat boilerplate; we could omit as it's more about compensation philosophy but maybe considered substantive? It's about compensation programs; but we already have Pay and Benefits. Could be omitted as it's somewhat generic. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly EEO but it's about compensation philosophy; could be considered boilerplate? It's somewhat generic but still part of compensation description. Might be okay to keep but we already have Pay and Benefits. It's not required. Safer to omit. Also "We are often open to a wide variety of profiles and sometimes have flexibility within our organizational structure to adjust the role responsibilities up or down should we select a candidate that is less or more experienced than the posted job requirements. In these occasional cases, we will communicate the revised salary range to the candidate during the selection process." This is also somewhat generic but could be considered substantive about flexibility. Might be okay to include under Pay or Requirements? Could be under Pay as a note. But it's somewhat generic; but it's about salary range flexibility. Might be considered substantive. However, the instruction says prefer a few substantive sections over many thin ones. We could incorporate that into Pay section as a note. Let's add a sentence in Pay: "Conga may adjust responsibilities and salary range based on candidate experience; any revised range would be communicated during selection." Now check for any other substantive info: "Preferred Resume Format We accept resumes in any format, we suggest using PDF or plain text." That's application instruction; remove. "Did we pique your interest? If this sounds like the kind of job you would love in the kind of environment where you would thrive, please click apply. We'd love to hear from you!" Remove. "Additional Information Conga is proud to be an Equal Opportunity Employer..." Remove EEO. "Conga is not open to third party solic