Jobs · Business Development · Washington

Pacific Northwest Enterprise Go-To-Market Leader

Slalom · Seattle, WA · 1 mo ago
Business Development$238k–$255k/yrFull-time
We need to output HTML fragment only, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. The posting includes: - Who You Are: description of role, location requirement (Seattle or Portland metro). This is about the role. - About Slalom’s Enterprise Capability: description of company. - What You’ll Do: list of responsibilities (Capability Vision & Strategy, Business Development & Sales, Delivery, Resource Pipeline, People Development, Financial Management). This is responsibilities. - What You’ll Bring: list of qualifications/experience/skills (8+ years experience, deep understanding of Technology, Retail, Manufacturing, expert business development, etc). This could be Requirements/Qualifications/Skills. - About Us: company description (maybe not needed as separate section? Could be part of About the role? But we have About the role heading; we could put company description there? The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections that have real specific content. We have content for About the role (description of role, location). Responsibilities (What You'll Do). Requirements/Qualifications/Skills (What You'll Bring). Benefits (Compensation and Benefits). Pay (Compensation and Benefits includes salary range). Schedule not mentioned. So we should not include Schedule. We need to decide how to split Requirements, Qualifications, Skills. The posting lumps them together; we could put them under Requirements or Qualifications or Skills. The instruction says we can use those headings if we have content. We could combine them into one section, maybe "Requirements". Or we could separate into Qualifications and Skills if we can discern. But better to avoid thin sections; we can put all under "Requirements". Or we could have "Qualifications" and "Skills" as separate if we can parse. The posting includes: "8+ years’ experience in a large consulting environment", "Deep understanding of the Technology, Retail, and Manufacturing space...", "Expert business development and client management skills...", "Track record of successfully implementing Salesforce cloud solutions", "Technical understanding of Salesforce...", "Active Salesforce certifications or ability to achieve relevant certifications upon hire", "Exposure to Software Development Life Cycle methodologies", "Expert at program management and delivery", "Expert communication (verbal and written)", "Expert business operations (e.g., proposal development, SOWs, price modeling, margins, utilization)", "Skilled at managing multiple complex pursuits at once", "Excellent mentoring and leadership skills", "Track record for being detail-oriented...", "Strong work ethic...". These are a mix of qualifications and skills. We could put them under "Requirements". That seems fine. Benefits: The posting includes "Compensation and Benefits" paragraph describing benefits: meaningful time off and paid holidays, parental leave, 401(k) with a match, a range of choices for highly subsidized health, dental, & vision coverage, adoption and fertility assistance, short/long-term disability, yearly $350 reimbursement account for well-being related expenses, discounted home, auto, and pet insurance. Also compensation: base salary pay range $238,000-$255,000, annual discretionary bonus. So we need Benefits section (list of benefits) and Pay section (salary range). The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we can include both Pay and Benefits. We need to output HTML fragment only, no /, no markdown fences. We must use

    for section headings. Use
    • for any list of duties/requirements/benefits, and

      for prose. Thus:

      About the role

      Slalom Consulting is looking for an experienced, entrepreneurial, and progressive leader to drive Salesforce services and client success with our Pacific Northwest (Seattle, Portland, Hawaii, Alaska) clients within the Manufacturing space. The Salesforce leader will provide thought leadership to our enterprise and mid-market clients, set strategic direction for the “Go-to-Market” practitioners, and generally be accountable for ensuring the overall quality execution of business and technology consulting across all Salesforce pursuits and engagements. The candidate for this position must be located in the Seattle or Portland metropolitan area.

      Maybe also include About Slalom’s Enterprise Capability? That could be part of About the role or maybe separate? But we have only About the role heading; we could incorporate that description as prose under About the role. However the instruction: "Prefer a few substantive sections over many thin ones." So we could combine About Slalom’s Enterprise Capability and About Us into About the role? But About the role heading is supposed to be about the role, not company. However we could still include company description under About the role as it's relevant. But maybe better to have a separate section like "About Slalom" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those. So we put company description under About the role? Might be odd but acceptable. However we could also put it under Responsibilities? No. Alternatively, we could treat "About Slalom’s Enterprise Capability" and "About Us" as part of "About the role" as background. That seems okay. Thus About the role paragraph(s) could be multiple

      elements. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them as lists. Let's extract sections: About the role: includes the "Who You Are" paragraph and maybe also the "About Slalom’s Enterprise Capability" and "About Us". We'll include them as prose. Responsibilities: from "What You’ll Do". It includes several bullet-like paragraphs each with a heading (Capability Vision & Strategy, Business Development & Sales, Delivery, Resource Pipeline, People Development, Financial Management). Under each there are subpoints. We need to turn these into

      • for any list of duties/requirements/benefits. So we can treat each main heading as a list item? Or we could nest lists? The instruction: Use
        • for any list of duties/requirements/benefits. It doesn't forbid nested lists, but we can just make a flat list of duties. However we need to preserve all substantive information; we could keep the headings as part of list item text. Simplify: create a
            with each duty as
          • containing the description. Thus list items: - Capability Vision & Strategy: Connects and drives regional or country-wide Capability strategy to the Market based on client portfolio, market maturity, and geographic makeup; Works with regional and company leaders to bring the Vision of our Enterprise Capability to life, driving connection between our local markets and regions to our global strategy; Tailors the market GTM strategy to align with local industries, clients and communities. - Business Development & Sales: Partners with industry-aligned client partners and sales executives to identify and pursue potential opportunities related to Capability; Individually acts as a Solution Lead or SME in the pursuit process, identifying appropriate SME from the broader Capability team as needed; Focuses on specific Customers aligned GTM strategy, driving targeted and bespoke sales motions; Participates in multi-Capability solutioning and client outcome-based selling motions with the GTM team; Driving overall growth of the Pacific Northwest Salesforce and overall Enterprise Business Applications Capability through a combination of business development, solutioning, talent management, oversight of delivery work, and thought leadership; Driving business development and solutioning complex deals, cultivating and nurturing key relationships within Slalom and Salesforce, and passionate about attracting and growing industry-specific talent; Building and developing relationships with our Account and Industry teams, as well as Salesforce teams to drive account planning and joint pursuits; Developing leading practice for GTM activities and focus, sales solutioning, and reusable collateral for sales accelerators; Maximizing team performance through an effective team approach that increases productivity and job satisfaction; Maintaining awareness of industry-leading practices and business levers for Enterprise Business Applications offerings and understanding how Slalom pursuit teams interact; Proactively seeking out speaking opportunities within the geographic Market as a Capability SME and thought leader at external conferences and events to generate net-new opportunities; Identifies and works with Marketing and Operations to plan Slalom-led thought leadership events, in the context of Capability and related Client Outcomes; Works to proactively ignite awareness and generate demand for Capability and related client outcomes in the market; Participates in Campaigns, RFIs, RFPs, workshops and POCs to ignite specific opportunities; Research client portfolio needs and adjust focus to topics of resonance; Focuses on building client relationships at the target and active client portfolio. - Delivery: Providing engagement oversight and governance of Salesforce projects in market to ensure delivery quality; Mentoring and upskilling delivery team members through practice leadership and the establishment of best practices. - Resource Pipeline: Participates in market-specific and capability-specific rhythm of business for hiring, staffing, workforce planning; participates in the planning process for the Market dedicated Capability pool. - People Development: Supports the development of the small team of direct reports due to GTM focus, including leading other market or office Capability GTM Leads within the same Capability or who are focused on a specific sub-Capability/discipline; Acts as a mentor to other practitioners in the area of Capability working to serve the Market’s portfolio; Participates in performance management by providing Feedback on the Capability of team members assigned to Market’s pursuits and delivery. - Financial Management: Works with Market’s GTM team and broader Capability leadership to create Capability-specific growth and cost projections; Works to achieve forecast against revenue and works with Market GTM leadership to identify when a Capability is unhealthy at the Market level and agrees to escalation of dedicated team members to next geo tier for staffing. We need to ensure we don't lose any details. The above captures most. Now Requirements/Qualifications/Skills: from "What You’ll Bring". We'll create a
            • list. List items: - 8+ years’ experience in a large consulting environment - Deep understanding of the Technology, Retail, and Manufacturing space, including current trends, growth opportunities, technology enablement, and regulations - Expert business development and client management skills, including C-level relationships - Track record of successfully implementing Salesforce cloud solutions - Technical understanding of Salesforce with demonstrated understanding and experience with Salesforce architecture - Active Salesforce certifications or ability to achieve relevant certifications upon hire - Exposure to Software Development Life Cycle methodologies - Expert at program management and delivery - Expert communication (verbal and written) - Expert business operations (e.g., proposal development, SOWs, price modeling, margins, utilization) - Skilled at managing multiple complex pursuits at once - Excellent mentoring and leadership skills - Track record

Similar jobs