Revenue Operations System Administrator

We need to output HTML fragment with sections: h3 headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections with real content. The posting includes description (About the role) at start: "The Revenue Operations System Administrator is responsible for supporting..." That's about the role. Then there is a "Responsibilities" heading in the posting. Then there is "Experience" (which could be Requirements/Qualifications). There's "Knowledge, Skills, And Abilities" (Skills). There's "Education" (Qualifications). There's "What We Offer" includes salary range and benefits (Pay, Benefits). There's no explicit Schedule. So we will include sections: About the role, Responsibilities, Requirements (maybe combine Experience and Education?), Qualifications (maybe Education), Skills, Benefits, Pay. But we must not duplicate. The instruction: Prefer a few substantive sections over many thin ones. Could combine Experience and Education into Requirements/Qualifications. But we have separate headings allowed: Requirements, Qualifications, Skills. We could put Experience under Requirements, Education under Qualifications. Skills under Skills. Benefits and Pay separate. We must not repeat job title as heading. No Job ID etc. We must use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to parse the posting content. Let's extract sections: About the role: first paragraph(s) before "Responsibilities". It says: "The Revenue Operations System Administrator is responsible for supporting, administering, and enhancing Salesforce and related business systems that enable OTAVA’s sales, quoting, ordering, deployment, billing, and partner processes. As a member of the Revenue Operations team, this role helps maintain and improve the Salesforce platform while partnering with teams across the organization to deliver scalable, efficient business solutions. The Revenue Operations System Administrator serves as a key technical resource for the company’s quoting systems, administering the current Salesforce CPQ environment while playing an active role in the evaluation, implementation, transition, and ongoing administration of a new quoting solution." That's the about role. Responsibilities: after "Responsibilities" heading, there is a list of bullet-like sentences separated by periods. Let's capture each as list item. Responsibilities list: - Administer and maintain Salesforce, including configuration, user access, security, data management, reporting, and ongoing platform enhancements. - Administer and support Salesforce CPQ through end of life. - Support the evaluation, implementation, testing, and rollout of a new quoting platform. - Provide ongoing administration and support for the new quoting platform following implementation. - Support the end-to-end revenue lifecycle across Sales, Quoting, Ordering, Deployment, Customer, Contract, and Billing processes. - Troubleshoot system and process issues and support user requests. - Coordinate testing of system enhancements and new functionality. - Salesforce & Quoting Administration - Configure and maintain Salesforce, including security, access, users, data, reporting, and platform functionality. - Configure and support Salesforce CPQ products, pricing, quoting processes, approvals, and proposal generation. - Troubleshoot Salesforce CPQ issues and support users throughout the quoting process. - Participate in the transition from Salesforce CPQ to a new quoting solution. - Configure, enhance, and support the new quoting platform following implementation. - Maintain reliable and scalable quoting processes that support business requirements. - Systems & Automation - Design, build, and maintain Salesforce Flows and other automations to improve business processes and operational efficiency. - Manage and troubleshoot integrations between Salesforce, quoting tools, billing platforms, and other business systems. - Maintain accurate and reliable data flow across integrated platforms. - Identify opportunities to automate manual processes and improve system efficiency. - Support configuration and administration of business systems beyond Salesforce as required. - Revenue Lifecycle Support - Support the end-to-end revenue lifecycle across: Sales Quoting Ordering Deployment Customer Management Contract Management Billing Partner Processes - Help ensure systems and processes support accurate and efficient handoffs between teams throughout the customer lifecycle. - Documentation - Develop and maintain system documentation. - Document Salesforce configurations, workflows, integrations, and business processes. - Develop and maintain training materials and user resources. - Document system changes and enhancements. - Maintain resources that support ongoing administration and knowledge sharing. - Cross Functional Collaboration - Work Closely With Sales Finance Billing Deployment Marketing Revenue Operations Other business and technical teams - Partner with stakeholders to understand business requirements and translate them into scalable system and process solutions. - Coordinate testing and validation of system enhancements and new functionality. - Support users and teams as new processes, automations, and platforms are introduced. - Continuous Improvement - Identify opportunities to improve Salesforce and the broader Revenue Operations technology stack. - Recommend automation and process improvements. - Support the transition from legacy systems and processes to more scalable solutions. - Assist with development of system administration standards and best practices. - Participate in ongoing optimization of quoting, ordering, deployment, billing, and related revenue processes. We need to preserve all substantive info. Could flatten into list items but maintain hierarchy? Probably just list items. Requirements: Experience section bullet list: - 2+ years of relevant experience administering Salesforce in a professional environment. - Experience with Salesforce CPQ configuration and administration. - Experience managing and configuring quoting tools or similar sales technology platforms. - Experience managing integrations between Salesforce and other business systems or platforms. - Experience with billing platforms and related sales-to-billing processes. - Experience or working knowledge of cloud and hosted solution environments. - Experience supporting cross-functional business processes and system users. Qualifications: Education bullet: - Bachelor’s degree in Business Administration, Information Technology, a related technical field, or equivalent professional experience. Skills: Knowledge, Skills, And Abilities list (many items). We'll list each as

• . Benefits: from "What We Offer": Competitive base salary ($65K–$85K depending on experience and qualifications) plus bonus, 401(k) match, health insurance, generous PTO, paid volunteer time off, and working with world-class co-workers who are just as dedicated and as awesome as you are. We need separate Pay and Benefits sections. Pay: base salary range plus bonus maybe. Benefits: 401(k) match, health insurance, generous PTO, paid volunteer time off, working with world-class co-workers. We must not include filler like "commensurate with experience". The posting includes "depending on experience and qualifications" which is okay. We need to output only HTML fragment. Structure:

  About the role

  ... (the about role paragraph(s)).

  Responsibilities

  • ... each responsibility.
  ...

  Requirements

  • ... experience items.

  Qualifications

  • ... education.

  Skills

  • ... each skill.

  Pay

  Competitive base salary ($65K–$85K depending on experience and qualifications) plus bonus.

  Benefits

  • 401(k) match
  • health insurance
  • generous PTO
  • paid volunteer time off
  • working with world-class co-workers
  We should also maybe include the "What about Otava?" description? That's boilerplate? It's about company description; maybe considered boilerplate but could be considered substantive? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "What about Otava?" is company overview; not explicitly prohibited but could be considered boilerplate? It's not EEO etc. Might be okay to keep? However they said preserve ALL substantive information; company description could be considered substantive. But they also said prefer few substantive sections over many thin ones. Adding another section "About Otava" could be okay but not listed as allowed heading? Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list "About Otava". So we should not create a section not in list. So we omit that. Thus output only those sections. Now ensure we don't repeat content. For Responsibilities we have many items; we need to ensure we include all from the posting. Let's extract precisely. From posting: "Responsibilities Administer and maintain Salesforce, including configuration, user access, security, data management, reporting, and ongoing platform enhancements.Administer and support Salesforce CPQ through end of life.Support the evaluation, implementation, testing, and rollout of a new quoting platform.Provide ongoing administration and support for the new quoting platform following implementation.Support the end-to-end revenue lifecycle across Sales, Quoting, Ordering, Deployment, Customer, Contract, and Billing processes.Troubleshoot system and process issues and support user requests.Coordinate testing of system enhancements and new functionality.Salesforce & Quoting AdministrationConfigure and maintain Salesforce, including security, access, users, data, reporting, and platform functionality.Configure and support Salesforce CPQ products, pricing, quoting processes, approvals, and proposal generation.Troubleshoot Salesforce CPQ issues and support users throughout the quoting process.Participate in the transition from Salesforce CPQ to a new quoting solution.Configure, enhance, and support the new quoting platform following implementation.Maintain reliable and scalable quoting processes that support business requirements.Systems & AutomationDesign, build, and maintain Salesforce Flows and other automations to improve business processes and operational efficiency.Manage and troubleshoot integrations between Salesforce, quoting tools, billing platforms, and other business systems.Maintain accurate and reliable data flow across integrated platforms.Identify opportunities to automate manual processes and improve system efficiency.Support configuration and administration of business systems beyond Salesforce as required. Revenue Lifecycle Support Support the end-to-end revenue lifecycle across:SalesQuotingOrderingDeploymentCustomer ManagementContractManagementBillingPartner ProcessesHelp ensure systems and processes support accurate and efficient handoffs between teams throughout the customer lifecycle. Documentation Develop and maintain system documentation.Document Salesforce configurations, workflows, integrations, and business processes.Develop and maintain training materials and user resources.Document system changes and enhancements.Maintain resources that support ongoing administration and knowledge sharing. Cross Functional Collaboration Work Closely With SalesFinanceBillingDeploymentMarketingRevenue OperationsOther business and technical teamsPartner with stakeholders to understand business requirements and translate them into scalable system and process solutions.Coordinate testing and validation of system enhancements and new functionality.Support users and teams as new processes, automations, and platforms are introduced. Continuous Improvement Identify opportunities to improve Salesforce and the broader Revenue Operations technology stack.Recommend automation and process improvements.Support the transition from legacy systems and processes to more scalable solutions.Assist with development of system administration standards and best practices.Participate in ongoing optimization of quoting, ordering, deployment, billing, and related revenue processes." We need to split into sensible list items. Some headings like "Salesforce & Quoting Administration" are subheadings; we could treat them as list items as well, but they are not actions; they are categories. Could include them as list items but maybe better to treat them as subheadings? But we only allowed
  • for list; we could still include them as
  • with bold? But we cannot add extra tags besides

    ,

    ,

    ,
    • . We could embed inside
    • but that's extra tag not prohibited? The instruction only says use those tags for sections; doesn't forbid other tags