Senior Sales Operations Analyst

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We need to extract content. From posting: Company: Flow Control Group About Us: ... (company description). Then "We are seeking a highly analytical and detail-oriented Sales Operations Specialist to support our sales organization through Salesforce CRM administration, reporting, data analysis, and operational support." Thus "About the role" could be the description of role. We can put that as a paragraph under

About the role

. Responsibilities: list of bullet points under "Key Responsibilities". We'll output

• each. Requirements/Qualifications: There's "Required Qualifications" and "Preferred Qualifications". Also "Key Competencies". We need to decide sections: maybe "Qualifications" for required, "Preferred Qualifications" maybe as part of Qualifications? But we have limited headings: Qualifications, Skills, Benefits, Pay, Schedule. We can put Required Qualifications under

  Qualifications

  . Preferred Qualifications could be under

  Skills

  or maybe also Qualifications. But we need to avoid filler. We have content for Skills: maybe list of technical skills (Power BI, etc.) but those are in qualifications. Could treat "Skills" as the list of tools and competencies. However we already have Key Competencies list. Could map that to Skills. We need to include Benefits section: posting mentions "Competitive Benefits: Enjoy an attractive benefits package that includes Medical, Dental and Vision insurance (among other plans), competitive 401(k) matching program, career growth opportunities, employee referral program, paid time off and holidays, as well as parental leave." Also "Training: FCG University learning and training platform..." and "Career Growth Opportunities". So we have benefits content. Pay and Schedule: not mentioned. So we should NOT include Pay or Schedule sections. We must not include boilerplate like EEO etc. Remove that. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from sections we include. We need to format as HTML fragment only, no or . Use

  for headings,

  for prose,

  • for lists. We must not repeat job title as heading. So no heading for "Sales Operations Specialist". Good. We need to include About Us? The instruction: use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). About Us is not in list, but we could incorporate company description into About the role? Probably we should include a brief About the role that includes company description and role summary. The "About Us" is company overview; could be part of About the role. We'll include that as prose under About the role. Thus:

    About the role

    Flow Control Group (FCG) is a leading provider of fluid handling, process, and industrial automation solutions across North America. We are a 100% employee-owned organization made up of over 2,000 team members and 95+ entrepreneurial brands—each empowered to think big, move fast, and bring innovative ideas to life. Our ownership mindset fuels a culture of pride, accountability, and exceptional customer service. At FCG, we believe in the power of partnership and entrepreneurship. We work collaboratively across our brands to drive growth, unlock new opportunities, and deliver real impact for our customers. This unique model allows us to combine local expertise with national strength, creating a dynamic environment where creativity meets practicality. We are seeking a highly analytical and detail-oriented Sales Operations Specialist to support our sales organization through Salesforce CRM administration, reporting, data analysis, and operational support.

    Then Responsibilities:

    Responsibilities

    • Develop, maintain, and enhance Salesforce.com reports, dashboards, and reporting solutions to support sales leadership and field sales teams.
    • Analyze sales, customer, pipeline, activity, and operational data to identify trends, opportunities, and areas for improvement.
    • Support sales operations across multiple divisions, business units, or companies, ensuring consistent processes, reporting, and data management.
    • Partner with sales leaders, sales representatives, service teams, and other stakeholders to understand reporting and operational requirements.
    • Create and maintain reporting and analytics using tools such as Power BI, Microsoft Access, Microsoft SQL, Tableau, Excel, or other business intelligence platforms.
    • Assist with data validation, cleansing, analysis, and reconciliation to ensure the accuracy and integrity of sales and customer information.
    • Develop recurring and ad-hoc reports to support forecasting, pipeline management, sales performance, customer activity, and other business initiatives.
    • Identify opportunities to improve sales processes, reporting capabilities, data quality, and operational efficiency.
    • Support Salesforce CRM and Service Cloud processes and reporting.
    • Assist with Salesforce data management, including identifying data-quality issues and working with appropriate teams to resolve them.
    • Support lead management and marketing/sales processes, including lead tracking, assignment, conversion, and campaign reporting.
    • Work with marketing automation platforms such as HubSpot or similar systems to support lead and campaign reporting and analytics.
    • Create documentation and provide training or guidance to users on reporting, Salesforce processes, and sales operations tools.
    • Handle multiple projects and priorities while maintaining a high level of accuracy and responsiveness.
    Then Qualifications (Required):

    Qualifications

    • 3+ years of experience in Sales Operations, Sales Support, Business Operations, or a related field.
    • Several years of hands-on experience creating Salesforce.com reports and dashboards.
    • Demonstrated experience working with Salesforce CRM, with experience in Salesforce Service Cloud strongly preferred.
    • Direct experience supporting sales organizations across multiple divisions, business units, or companies.
    • Strong analytical and problem-solving skills with the ability to work with large amounts of data.
    • Experience with one or more business intelligence and reporting tools such as: Microsoft Power BI, Microsoft Access, Microsoft SQL / SQL Server, Tableau, Advanced Microsoft Excel, other data analytics or reporting platforms.
    • Excellent written and verbal communication skills.
    • Ability to work effectively with sales leadership, field sales teams, technical teams, and other business stakeholders.
    • Strong attention to detail and a commitment to data accuracy.
    • Ability to translate business requirements into practical reporting and analytical solutions.
    Then Skills (Preferred Qualifications + Key Competencies maybe). We need to decide what to put under Skills. Could combine Preferred Qualifications and Key Competencies as skills. But we must not invent or summarize away detail; we need to preserve all substantive information. So we need to include Preferred Qualifications bullet list and Key Competencies bullet list. We could put them under Skills as two separate lists or combine. Probably better to have a single
    with all items from Preferred Qualifications and Key Competencies. However we risk losing distinction but still preserving content. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine them into Skills. Thus:

    Skills

    • Experience with HubSpot or another marketing automation platform.
    • Experience with Lead Management and Campaign Management.
    • Experience integrating or reconciling data between Salesforce and other business systems.
    • Salesforce reporting and analytics experience across multiple Salesforce objects and business processes.
    • Experience supporting sales forecasting, pipeline management, sales performance reporting, or territory/account management.
    • Experience developing Power BI or Tableau dashboards for executive and sales leadership.
    • Experience with SQL queries and relational databases.
    • Salesforce certifications are a plus.
    • Salesforce Expertise – Strong practical knowledge of Salesforce reporting, dashboards, CRM processes, and data.
    • Data & Analytics – Ability to analyze complex data and turn it into clear, actionable business information.
    • Business Acumen – Understanding of how sales organizations operate and how sales operations can support revenue growth and productivity.
    • Communication – Excellent written and verbal communication skills, with the ability to communicate effectively with both technical and non-technical audiences.
    • Problem Solving – Ability to investigate data and process issues, identify root causes, and develop effective solutions.
    • Collaboration – Ability to work across multiple divisions, teams, and levels of the organization.
    • Attention to Detail – Strong focus on accuracy, consistency, and data integrity.
    • Continuous Improvement – Ability to identify opportunities to improve processes, reporting, systems, and the overall effectiveness of sales operations.
    Then Benefits:

    Benefits

    • Medical, Dental and Vision insurance (among other plans)
    • Competitive 401(k) matching program
    • Career growth opportunities
    • Employee referral program
    • Paid time off and holidays
    • Parental leave
    • FCG University learning and training platform available to all employees offering over 80k courses
    • Custom training programs, mentorship, and supportive environment for professional development
    We should not include Pay or Schedule. Check that we didn't include any boilerplate like EEO etc. We removed that. We need to ensure we didn't include any filler like "commensurate with experience". Not present. Check that we preserved all substantive information: Did we miss any details? Let's review original. About Us: we included all. Role summary: we included. Responsibilities: we included all bullet points. Required Qualifications: we included all bullet points. Preferred Qualifications: we included all bullet points. Key Competencies: we included all bullet points. What Success Looks Like: we omitted! That's a section with substantive content. Should we include? The headings list does not have a "Success" heading, but we could incorporate into About the role or maybe under Qualifications? However it's substantive; we need to preserve all substantive information. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must include the "What Success Looks Like" content somewhere. Since we don't have a heading for it, we could incorporate it under a heading like "About the role" or maybe create a new heading? But the instruction says use headings 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. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the allowed headings? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests examples, not exhaustive list. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a heading for "What Success Looks Like" if we want, but the instruction didn't forbid. However they gave a list of possible headings; maybe they expect us to use only those headings. Safer to stick to those headings. But we need to preserve the success content; we could embed it under "About the role" or "Responsibilities" or "Qualifications". Probably best to add a paragraph under About the role after the role summary, describing what success looks like. That would preserve the content. Thus under About the role we can add a <