Sales Operations Lead
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, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. 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 content:
- Intro: "We're looking for a Sales Operations Lead to lead our Sales Operations for AMER at Coder, with a strong focus on the systems and processes supporting our Customer Success organization. This remote role matters because reliable workflows, clean data, and clear reporting help our teams improve retention, expansion, and customer health. You’ll work across Customer Success, Sales, and Sales Engineering to improve how we manage the customer lifecycle from closed-won through renewal. You’ll own key CS workflows in Pylon and Salesforce, build useful reporting, and partner with the Global Director of Sales Operations and CS leadership to turn operational needs into scalable systems."
That's prose.
Then "What You’ll Do Here" with bullet list of duties.
Then "What We’re Looking For" with bullet list of requirements.
Then "About Coder" paragraph.
Then "Interview process" etc. That is likely boilerplate (application instructions, interview process). Should be removed.
Also "AI use during the interview process", "Our use of AI in hiring", "Your data is not used...", "In accordance with New York City Local Law 144", "Coder is a proud Equal Opportunity Employer" - all boilerplate to remove.
Thus we keep: intro, responsibilities, requirements, about Coder.
We need sections: maybe "About the role" (intro), "Responsibilities", "Requirements", maybe "About the company". Could also include "Qualifications" but we have requirements. The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which sections have content.
We have:
- About the role: intro paragraph.
- Responsibilities: bullet list from "What You’ll Do Here".
- Requirements: bullet list from "What We’re Looking For".
- About the company: "About Coder" paragraph.
We should not include Benefits, Pay, Schedule because not specified.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
About Coder
...
Make sure to preserve all substantive information, not invent or summarize away detail. Must keep all bullet points exactly as in posting (maybe minor wording). Need to ensure we don't include filler like "commensurate with experience". Not present.
Let's extract bullet points.
From "What You’ll Do Here":
List:
- Serve as the operational point person for the AMER Customer Success organization, partnering closely with CSMs and CS leadership.
- Own and continuously improve Pylon workflows, configurations, and automations supporting customer communication, ticketing, and CS processes.
- Build and maintain reporting and dashboards for customer health, renewal risk, NRR, GRR, and CSM productivity.
- Manage the systems and workflows supporting Customer Success, including Pylon, Salesforce, integrations, and data hygiene.
- Design and improve playbooks, SOPs, and workflows for onboarding, QBRs, renewals, escalations, and other key customer lifecycle moments.
- Partner with Sales to create smooth, consistent handoffs from closed-won through onboarding and ongoing customer management.
- Support deal desk and sales operations processes where they intersect with customer onboarding, renewals, expansion, and post-sale commitments.
- Analyze CS and revenue data to identify trends, risks, and opportunities, then translate those findings into clear recommendations for leadership.
- Support renewal forecasting, customer health reporting, and capacity planning for the Customer Success team.
- Troubleshoot day-to-day operational issues and act as a go-to resource for Pylon and related CS workflows.
- Own and optimize Salesforce workflows that connect Sales and Customer Success, keeping data accurate, processes practical, and reporting useful.
- Improve enablement and documentation so distributed teams understand how to use systems, follow processes, and find the information they need.
- Partner with Sales Engineering and other teams to improve handoffs, reduce operational friction, and maintain clear customer context.
- Work closely with the Director of Sales Operations to support AMER priorities and improve how our revenue teams operate.
That's 14 bullet points.
Now "What We’re Looking For":
List:
- 2+ years of experience in Sales Operations, Revenue Operations, Customer Success Operations, or a related go-to-market operations role.
- Hands-on experience administering and optimizing Pylon.
- Strong experience with Salesforce, including managing workflows, reporting, data quality, or process improvements.
- Experience supporting a Customer Success organization and understanding the operational needs of CSM teams.
- Familiarity with customer health, renewals, retention, expansion, NRR, and GRR.
- Strong analytical and problem-solving skills, with the ability to turn ambiguous problems into practical, scalable processes.
- Experience building dashboards, reporting, and operational insights for teams and leadership.
- Strong written and verbal communication skills, especially in a remote environment.
- A self-starter who can work independently, manage competing priorities, and follow through without needing constant direction.
- Comfort partnering across Customer Success, Sales, Sales Engineering, and leadership.
- Strong organizational skills and attention to detail.
- Ability to provide reliable coverage for AMER working hours.
- Bonus tacos if you have (Tacos? If you need an ice-breaker, ask how we say thanks by giving tacos!) – This is a quirky line but still content? It's a bonus tacos note. Should we keep? It's substantive? It's a bit informal but it's part of posting. Probably keep as a bullet? It's not a requirement but a fun note. It says "Bonus tacos if you have (Tacos? If you need an ice-breaker, ask how we say thanks by giving tacos!)". It's not a requirement but a fun note. We could keep as a bullet but it's not a requirement. Might be considered filler? It's specific content though. I'd keep it as a bullet under Requirements maybe.
- Experience with Customer Success platforms such as Pylon, Totango, Gainsight, Vitally, or similar tools.
- Working knowledge of Clari, Gong, Nooks, Dealhub, DocuSign, ZoomInfo, and 6sense.
- Experience building or improving customer health scoring models.
- Experience with renewal forecasting, capacity planning, or CSM portfolio design.
- Experience managing integrations between CRM, Customer Success, support, and revenue tools.
- Experience developing enablement, SOPs, and documentation for distributed teams.
- Experience working in high-growth SaaS or developer-focused companies.
Thus many bullet points.
We need to ensure we don't include duplicated lines. There's no duplication.
Now "About Coder" paragraph:
"Coder is the leading platform for AI development Infrastructure, enabling enterprises to securely run human and AI-driven development workflows in consistent, governed environments. Coder provides self-hosted, agent-ready workspaces that unify developer productivity and platform governance. With Coder, enterprises can confidently evolve from human-only development to AI-assisted and autonomous workflows, without sacrificing security, compliance, or performance. Learn more at coder.com."
We keep that.
Now we need to output HTML.
We must not include any extra text outside HTML.
Thus final answer:
About the role
We're looking for a Sales Operations Lead to lead our Sales Operations for AMER at Coder, with a strong focus on the systems and processes supporting our Customer Success organization. This remote role matters because reliable workflows, clean data, and clear reporting help our teams improve retention, expansion, and customer health. You’ll work across Customer Success, Sales, and Sales Engineering to improve how we manage the customer lifecycle from closed-won through renewal. You’ll own key CS workflows in Pylon and Salesforce, build useful reporting, and partner with the Global Director of Sales Operations and CS leadership to turn operational needs into scalable systems.
Responsibilities
- Serve as the operational point person for the AMER Customer Success organization, partnering closely with CSMs and CS leadership.
- Own and continuously improve Pylon workflows, configurations, and automations supporting customer communication, ticketing, and CS processes.
- Build and maintain reporting and dashboards for customer health, renewal risk, NRR, GRR, and CSM productivity.
- Manage the systems and workflows supporting Customer Success, including Pylon, Salesforce, integrations, and data hygiene.
- Design and improve playbooks, SOPs, and workflows for onboarding, QBRs, renewals, escalations, and other key customer lifecycle moments.
- Partner with Sales to create smooth, consistent handoffs from closed-won through onboarding and ongoing customer management.
- Support deal desk and sales operations processes where they intersect with customer onboarding, renewals, expansion, and post-sale commitments.
- Analyze CS and revenue data to identify trends, risks, and opportunities, then translate those findings into clear recommendations for leadership.
- Support renewal forecasting, customer health reporting, and capacity planning for the Customer Success team.
- Troubleshoot day-to-day operational issues and act as a go-to resource for Pylon and related CS workflows.
- Own and optimize Salesforce workflows that connect Sales and Customer Success, keeping data accurate, processes practical, and reporting useful.
- Improve enablement and documentation so distributed teams understand how to use systems, follow processes, and find the information they need.
- Partner with Sales Engineering and other teams to improve handoffs, reduce operational friction, and maintain clear customer context.
- Work closely with the Director of Sales Operations to support AMER priorities and improve how our revenue teams operate.
Requirements
- 2+ years of experience in Sales Operations, Revenue Operations, Customer Success Operations, or a related go-to-market operations role.
- Hands-on experience administering and optimizing Pylon.
- Strong experience with Salesforce, including managing workflows, reporting, data quality, or process improvements.
- Experience supporting a Customer Success organization and understanding the operational needs of CSM teams.
- Familiarity with customer health, renewals, retention, expansion, NRR, and GRR.
- Strong analytical and problem-solving skills, with the ability to turn ambiguous problems into practical, scalable processes.
- Experience building dashboards, reporting, and operational insights for teams and leadership.
- Strong written and verbal communication skills, especially in a remote environment.
- A self-starter who can work independently, manage competing priorities, and follow through without needing constant direction.
- Comfort partnering across Customer Success, Sales, Sales Engineering, and leadership.
- Strong organizational skills and attention to detail.
- Ability to provide reliable coverage for AMER working hours.
- Bonus tacos if you have (Tacos? If you need an ice-breaker, ask how we say thanks by giving tacos!)
- Experience with Customer Success platforms such as Pylon, Totango, Gainsight, Vit
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. 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 content: - Intro: "We're looking for a Sales Operations Lead to lead our Sales Operations for AMER at Coder, with a strong focus on the systems and processes supporting our Customer Success organization. This remote role matters because reliable workflows, clean data, and clear reporting help our teams improve retention, expansion, and customer health. You’ll work across Customer Success, Sales, and Sales Engineering to improve how we manage the customer lifecycle from closed-won through renewal. You’ll own key CS workflows in Pylon and Salesforce, build useful reporting, and partner with the Global Director of Sales Operations and CS leadership to turn operational needs into scalable systems." That's prose. Then "What You’ll Do Here" with bullet list of duties. Then "What We’re Looking For" with bullet list of requirements. Then "About Coder" paragraph. Then "Interview process" etc. That is likely boilerplate (application instructions, interview process). Should be removed. Also "AI use during the interview process", "Our use of AI in hiring", "Your data is not used...", "In accordance with New York City Local Law 144", "Coder is a proud Equal Opportunity Employer" - all boilerplate to remove. Thus we keep: intro, responsibilities, requirements, about Coder. We need sections: maybe "About the role" (intro), "Responsibilities", "Requirements", maybe "About the company". Could also include "Qualifications" but we have requirements. The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which sections have content. We have: - About the role: intro paragraph. - Responsibilities: bullet list from "What You’ll Do Here". - Requirements: bullet list from "What We’re Looking For". - About the company: "About Coder" paragraph. We should not include Benefits, Pay, Schedule because not specified. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
About Coder
...
Make sure to preserve all substantive information, not invent or summarize away detail. Must keep all bullet points exactly as in posting (maybe minor wording). Need to ensure we don't include filler like "commensurate with experience". Not present. Let's extract bullet points. From "What You’ll Do Here": List: - Serve as the operational point person for the AMER Customer Success organization, partnering closely with CSMs and CS leadership. - Own and continuously improve Pylon workflows, configurations, and automations supporting customer communication, ticketing, and CS processes. - Build and maintain reporting and dashboards for customer health, renewal risk, NRR, GRR, and CSM productivity. - Manage the systems and workflows supporting Customer Success, including Pylon, Salesforce, integrations, and data hygiene. - Design and improve playbooks, SOPs, and workflows for onboarding, QBRs, renewals, escalations, and other key customer lifecycle moments. - Partner with Sales to create smooth, consistent handoffs from closed-won through onboarding and ongoing customer management. - Support deal desk and sales operations processes where they intersect with customer onboarding, renewals, expansion, and post-sale commitments. - Analyze CS and revenue data to identify trends, risks, and opportunities, then translate those findings into clear recommendations for leadership. - Support renewal forecasting, customer health reporting, and capacity planning for the Customer Success team. - Troubleshoot day-to-day operational issues and act as a go-to resource for Pylon and related CS workflows. - Own and optimize Salesforce workflows that connect Sales and Customer Success, keeping data accurate, processes practical, and reporting useful. - Improve enablement and documentation so distributed teams understand how to use systems, follow processes, and find the information they need. - Partner with Sales Engineering and other teams to improve handoffs, reduce operational friction, and maintain clear customer context. - Work closely with the Director of Sales Operations to support AMER priorities and improve how our revenue teams operate. That's 14 bullet points. Now "What We’re Looking For": List: - 2+ years of experience in Sales Operations, Revenue Operations, Customer Success Operations, or a related go-to-market operations role. - Hands-on experience administering and optimizing Pylon. - Strong experience with Salesforce, including managing workflows, reporting, data quality, or process improvements. - Experience supporting a Customer Success organization and understanding the operational needs of CSM teams. - Familiarity with customer health, renewals, retention, expansion, NRR, and GRR. - Strong analytical and problem-solving skills, with the ability to turn ambiguous problems into practical, scalable processes. - Experience building dashboards, reporting, and operational insights for teams and leadership. - Strong written and verbal communication skills, especially in a remote environment. - A self-starter who can work independently, manage competing priorities, and follow through without needing constant direction. - Comfort partnering across Customer Success, Sales, Sales Engineering, and leadership. - Strong organizational skills and attention to detail. - Ability to provide reliable coverage for AMER working hours. - Bonus tacos if you have (Tacos? If you need an ice-breaker, ask how we say thanks by giving tacos!) – This is a quirky line but still content? It's a bonus tacos note. Should we keep? It's substantive? It's a bit informal but it's part of posting. Probably keep as a bullet? It's not a requirement but a fun note. It says "Bonus tacos if you have (Tacos? If you need an ice-breaker, ask how we say thanks by giving tacos!)". It's not a requirement but a fun note. We could keep as a bullet but it's not a requirement. Might be considered filler? It's specific content though. I'd keep it as a bullet under Requirements maybe. - Experience with Customer Success platforms such as Pylon, Totango, Gainsight, Vitally, or similar tools. - Working knowledge of Clari, Gong, Nooks, Dealhub, DocuSign, ZoomInfo, and 6sense. - Experience building or improving customer health scoring models. - Experience with renewal forecasting, capacity planning, or CSM portfolio design. - Experience managing integrations between CRM, Customer Success, support, and revenue tools. - Experience developing enablement, SOPs, and documentation for distributed teams. - Experience working in high-growth SaaS or developer-focused companies. Thus many bullet points. We need to ensure we don't include duplicated lines. There's no duplication. Now "About Coder" paragraph: "Coder is the leading platform for AI development Infrastructure, enabling enterprises to securely run human and AI-driven development workflows in consistent, governed environments. Coder provides self-hosted, agent-ready workspaces that unify developer productivity and platform governance. With Coder, enterprises can confidently evolve from human-only development to AI-assisted and autonomous workflows, without sacrificing security, compliance, or performance. Learn more at coder.com." We keep that. Now we need to output HTML. We must not include any extra text outside HTML. Thus final answer:About the role
We're looking for a Sales Operations Lead to lead our Sales Operations for AMER at Coder, with a strong focus on the systems and processes supporting our Customer Success organization. This remote role matters because reliable workflows, clean data, and clear reporting help our teams improve retention, expansion, and customer health. You’ll work across Customer Success, Sales, and Sales Engineering to improve how we manage the customer lifecycle from closed-won through renewal. You’ll own key CS workflows in Pylon and Salesforce, build useful reporting, and partner with the Global Director of Sales Operations and CS leadership to turn operational needs into scalable systems.
Responsibilities
- Serve as the operational point person for the AMER Customer Success organization, partnering closely with CSMs and CS leadership.
- Own and continuously improve Pylon workflows, configurations, and automations supporting customer communication, ticketing, and CS processes.
- Build and maintain reporting and dashboards for customer health, renewal risk, NRR, GRR, and CSM productivity.
- Manage the systems and workflows supporting Customer Success, including Pylon, Salesforce, integrations, and data hygiene.
- Design and improve playbooks, SOPs, and workflows for onboarding, QBRs, renewals, escalations, and other key customer lifecycle moments.
- Partner with Sales to create smooth, consistent handoffs from closed-won through onboarding and ongoing customer management.
- Support deal desk and sales operations processes where they intersect with customer onboarding, renewals, expansion, and post-sale commitments.
- Analyze CS and revenue data to identify trends, risks, and opportunities, then translate those findings into clear recommendations for leadership.
- Support renewal forecasting, customer health reporting, and capacity planning for the Customer Success team.
- Troubleshoot day-to-day operational issues and act as a go-to resource for Pylon and related CS workflows.
- Own and optimize Salesforce workflows that connect Sales and Customer Success, keeping data accurate, processes practical, and reporting useful.
- Improve enablement and documentation so distributed teams understand how to use systems, follow processes, and find the information they need.
- Partner with Sales Engineering and other teams to improve handoffs, reduce operational friction, and maintain clear customer context.
- Work closely with the Director of Sales Operations to support AMER priorities and improve how our revenue teams operate.
Requirements
- 2+ years of experience in Sales Operations, Revenue Operations, Customer Success Operations, or a related go-to-market operations role.
- Hands-on experience administering and optimizing Pylon.
- Strong experience with Salesforce, including managing workflows, reporting, data quality, or process improvements.
- Experience supporting a Customer Success organization and understanding the operational needs of CSM teams.
- Familiarity with customer health, renewals, retention, expansion, NRR, and GRR.
- Strong analytical and problem-solving skills, with the ability to turn ambiguous problems into practical, scalable processes.
- Experience building dashboards, reporting, and operational insights for teams and leadership.
- Strong written and verbal communication skills, especially in a remote environment.
- A self-starter who can work independently, manage competing priorities, and follow through without needing constant direction.
- Comfort partnering across Customer Success, Sales, Sales Engineering, and leadership.
- Strong organizational skills and attention to detail.
- Ability to provide reliable coverage for AMER working hours.
- Bonus tacos if you have (Tacos? If you need an ice-breaker, ask how we say thanks by giving tacos!)
- Experience with Customer Success platforms such as Pylon, Totango, Gainsight, Vit