Jobs · Business Development

Senior Manager, Mid-Market Sales

Muck Rack · United States · 1 mo ago
RemoteRemoteBusiness Development$120k–$130k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: description of Muck Rack, mission, platform, etc. Also maybe "Founder-controlled, fully distributed...". This is about the company and role context. We'll put in

About the role

with paragraphs. - Responsibilities: bullet list of duties from "What you'll do:" and subsequent bullet-like sentences. We'll list each as
  • . - Requirements: maybe "If the details below describe you, you could be a great fit for this role:" includes experience, etc. Also earlier "You should be excited about leading...". We'll treat as Requirements. - Qualifications: maybe overlapping with Requirements. But we need to decide: The posting includes "What you'll do" (responsibilities), then "How success will be measured", then "If the details below describe you..." (requirements). Also earlier bullet about "You should be excited...". Could combine into Requirements and Skills. - Skills: maybe list of skills like pipeline management, forecasting, communication, coaching, data-driven, AI tools, etc. - Benefits: list of benefits under "Why Muck Rack?" includes remote work, home office stipend, etc. Also health & wellness, time off, learning & development, inclusive culture. - Pay: Salary section: base salary $120k-$130k, target earnings $250k, geo-neutral, etc. - Schedule: maybe travel expectations: up to 10% travel, attendance at annual offsite expected. Also maybe remote work forever. Could be schedule. We must not include sections with placeholder like "commensurate with experience". Not present. We must not include duplicated lines. We must not include application instructions, interview overview, etc. So we should omit Interview Overview, Travel & Team Engagement Expectations? Actually travel expectations are part of schedule/benefits? The posting includes "Travel & Team Engagement Expectations" which we can incorporate into Schedule or Benefits. Since it's substantive, we can include under Schedule (travel) or maybe Benefits (team engagement). We'll include travel under Schedule. We must not include EEO boilerplate, scam warning, legal notes, etc. So remove those at end. Now craft HTML. We'll need to ensure we use

    for each section heading, then content: either

    for prose or

    • for lists. We must not output markdown fences. Let's draft. First, About the role: combine description of Muck Rack, mission, platform, founder-controlled, values, and the role context: looking for adaptable metrics-driven people leader to train, coach, support, manage a team of salespeople focused on winning new customers in Mid-Market segment. Also excitement about leading team in fast-paced remote environment with diverse agency and brand prospects. We'll put as paragraphs. Second, Responsibilities: list items from "What you'll do:" and subsequent bullet-like sentences. Let's extract each bullet: - Lead and develop a team of 8 Account Executives, owning team quota attainment while coaching, inspiring, and motivating individuals with a team-first, winning mindset to achieve ambitious sales goals - Proven ability to lead and scale a high-velocity sales team, driving consistent productivity and performance across a high-volume sales motion. - Demonstrated ability to elevate deal size and complexity, coaching reps to expand use cases, multi-thread, engage senior stakeholders, and turn Mid-Market opportunities into larger, more strategic deals. - Track record of scaling pipeline and revenue while moving a business up-market, balancing the speed and efficiency of a velocity motion with increasing ACV and more sophisticated selling. - Own pipeline health and forecast accuracy through disciplined weekly inspection, clear deal narratives, and consistent CRM hygiene, leveraging tools like Salesforce, Gong, and Outreach to identify trends, mitigate risk, and surface opportunities - Communicate goals, expectations, and feedback with clarity and consistency, navigating tough conversations professionally and holding the team accountable to agreed-upon standards, KPIs, and follow-through - Run a consistent operating rhythm including weekly 1:1s, pipeline reviews, forecast calls, Gong call coaching, and team syncs that reinforce accountability, execution, and performance standards. With an aptitude for leveraging data intelligence to inform coaching and running the business - Develop and coach the team through weekly, structured coaching and deal inspection, with a focus on discovery quality, qualification rigor, deal strategy, and account progression - Hire, onboard, and develop new team members to build and sustain a high-performing, collaborative sales team - Execute sales strategy and contribute to its evolution, partnering with Sales Leadership, RevOps, and Enablement to improve processes, policies, and go-to-market execution - Join prospect conversations strategically to coach, inspect deal quality, and influence outcomes — not to carry deals personally, but to develop rep capability and deal judgment. - Build deep expertise in the PR industry, PR software landscape, and Muck Rack’s value proposition, enabling strong coaching, credible deal support, and effective market positioning That's many items; we can keep them as list. Third, Requirements: from "If the details below describe you, you could be a great fit for this role:" plus earlier "You should be excited about leading...". Let's list: - 4+ years of professional experience, including 2+ years of people management and hands-on SaaS sales experience in a closing role, with a clear transition from individual contributor to people leader - A team-first, winning mindset - you consistently set a high bar, lead with energy and ownership, and motivate others to exceed goals through clarity, discipline, and belief - Strong command of pipeline management and forecasting, with the ability to inspect deal quality, maintain CRM rigor, and leverage tools like Salesforce, Gong, Outreach, Slack, and Zoom (or equivalent) to drive predictable outcomes - Clear, confident communicator who can articulate goals, expectations, and feedback to both team members and leadership, including navigating difficult conversations professionally in a remote-first environment - Skilled coach and people developer, able to tailor your approach to individual reps while building core competencies in discovery, qualification, deal strategy, negotiation, and account progression - Detail-oriented and action-focused, with a track record of using sales data to identify trends, surface risk, prioritize the right actions, and follow through - Willingness to travel up to 15% as needed to support the team and business - Proactively incorporate AI tools into day to day work to improve productively and accelerate delivery Also earlier: "You should be excited about leading and developing a team working in a fast-paced remote environment with a diverse range of agency and brand prospects." Could be part of Requirements or About the role. We'll include in Requirements maybe as a bullet. Fourth, Qualifications: maybe we can treat "How success will be measured in this role:" as Qualifications? Actually that's metrics of success, not qualifications. Could be a separate section "Performance Metrics" but not in allowed headings. We could put under Requirements or Skills. But we need to follow allowed headings only. We could put under "Qualifications" the success metrics? Might be odd. Better to treat "How success will be measured" as part of Requirements or maybe as a separate section "Performance Expectations" but not allowed. Since we must only use allowed headings, we could incorporate those metrics into Requirements or Skills. However the instruction: "include a section ONLY when the posting has real, specific content for it". So we can create a section for "Qualifications" if there is content. The posting does have qualifications: maybe the earlier bullet "You should be excited about leading..." is more like qualifications. Also the "If the details below describe you..." is requirements. There's overlap. We could separate: Requirements = experience and baseline; Qualifications = skills and attributes like team-first mindset, communication, coaching, data-driven, etc. But we already used those in Requirements. Let's think: The posting includes "What you'll do" (responsibilities). Then "How success will be measured". Then "If the details below describe you..." (requirements). Then earlier "You should be excited about leading..." (maybe also qualifications). There's no explicit "Qualifications" heading. But we can still create a Qualifications section with content like "team-first mindset, strong communicator, skilled coach, detail-oriented, AI tool usage, willingness to travel". That seems like qualifications. Meanwhile Requirements could be the experience and people management SaaS sales. Let's split: - Requirements: 4+ years professional experience, including 2+ years people management and hands-on SaaS sales experience in a closing role, clear transition from IC to people leader. - Qualifications: team-first mindset, strong command of pipeline management and forecasting, clear communicator, skilled coach, detail-oriented, willingness to travel up to 15%, proactively incorporate AI tools. But we also have "You should be excited about leading and developing a team working in a fast-paced remote environment with a diverse range of agency and brand prospects." Could be part of Qualifications. We'll decide. Skills: maybe list of specific skills like pipeline management, forecasting, CRM tools (Salesforce, Gong, Outreach, Slack, Zoom), communication, coaching, data intelligence, deal strategy, negotiation, account progression, AI tools, etc. Could be separate. But we already used many in Qualifications. To avoid duplication, we could make Skills a list of tools and technical abilities: Salesforce, Gong, Outreach, Slack, Zoom, CRM hygiene, data intelligence, AI tools. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Skills into Qualifications or Requirements. But we need to follow allowed headings; we can omit Skills if not enough distinct content. However we have distinct content about tools and AI. Could be a Skills section. Benefits: from "Why Muck Rack?" includes remote work, home office stipend, phone and internet reimbursement, coworking membership, virtual and in-person team bonding, transparent & fair compensation, 401(k) with employer contributions, equity opportunities, health & wellness (medical, dental, vision, disability, life insurance, 100% premium coverage for high-deductible, 24/7 virtual care, EAP, employer-funded HSA contributions, quarterly wellness stipend, free Headspace), time off (4+ weeks PTO, paid sick and mental health days, 13 paid holidays option to swap, up to 16 weeks fully paid parental leave), learning and development (transparent pathways, bi-annual reviews, team workshops, leadership training, unlimited Coursera and O'Reilly, 2 additional PTO days for L&D), inclusive culture. We'll list as bullet points. Pay: Salary section: base salary $120k-$130k, target earnings $250k, geo-neutral approach, etc. Schedule: Travel expectations: up to 10% travel for team collaboration, customer engagements, company events; attendance at annual company offsite (typically held in Mexico) expected. Also remote work forever (maybe part of Benefits). We'll put travel under Schedule. Now we must ensure we don't include boilerplate like EEO, scam warning, legal notes, etc. Remove those. Now produce HTML. We'll need to wrap each section in

      heading then content. For lists, use
      • . For prose, use

        . Let's craft. Check for duplication: Ensure we don't repeat same bullet in multiple sections. We'll allocate: About the role: paragraphs about Muck Rack mission, platform, founder-controlled, values, and the role purpose. Responsibilities: list of duties. Requirements: experience baseline (4+ years professional, 2+ years people management, hands-on SaaS sales closing role, transition from IC to people leader). Qualifications: list of attributes: team-first mindset, strong command of pipeline management and forecasting

  • Similar jobs

    Sales Manager

    HRCap, Inc.United States· 1 mo ago
    RemoteSales$90k–$125k/yrapply on goace.hrcap.com

    Sales Manager

    ALIGN PRECISIONGarden Grove, CA· 1 mo ago
    Salesapply on recruiting2.ultipro.com