Enterprise Select Implementation Consultant (West)

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. We must parse the job posting. First, there is a "Who We Are" description – not a heading we need; we can ignore or maybe include as prose? The instruction: Use

for section headings (e.g. 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 (the page already shows it) and 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. We need to extract sections: - About the role: There's a paragraph after "About the role:" describing the role. We'll put that under

  About the role

  with

  content. - Responsibilities: There's a list starting with "In this role, you will:" then bullet points. We'll put under

  Responsibilities

  with
  • items. - Requirements: There's "Minimum requirements for the role:" with bullet list. We'll put under

    Requirements

    with
    . - Qualifications: There's "An ideal candidate also has:" bullet list. Could be considered Qualifications or Skills. The instruction includes Qualifications and Skills sections. We can treat "An ideal candidate also has:" as Qualifications (maybe also Skills). We'll decide: Qualifications: bullet list of ideal candidate attributes. Skills: maybe not separate; but we could put skills under Skills if there is explicit skill list. There's not a separate skill list besides those bullet points. Could combine Qualifications and Skills? But we need to follow instruction: prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one section called Qualifications (or Skills). However we have both headings allowed; we can include Qualifications and maybe not Skills if no distinct skill list. Let's see: The bullet list under "An ideal candidate also has:" includes: Strong bias for action, ability to think big, insistence on high standards. Experience serving and supporting large-scale business solutions at Fortune 500 companies. That's more qualifications/skills. We'll put under

    Qualifications

    . - Benefits: There's a section "Total Rewards" describing benefits: flexible remote model, professional development stipend, comprehensive health and parental leave plans, etc. Also mention base salary range. Benefits section should include those. We'll put under

    Benefits

    with
    items. - Pay: There's salary range: Annual Base Salary $100,406—$151,875 USD. Also note that base pay offered may vary depending on factors. We'll put under

    Pay

    with

    containing that info. - Schedule: There's mention of remote position, time zones, travel up to 10%, work in local time zone hours. That's schedule info. We'll put under

    Schedule

    with

    . We must not include boilerplate like EEO, accommodations, fraud detection, etc. Remove those. Also need to remove duplicated lines. Ensure we preserve all substantive info. Let's extract content precisely. First, "Who We Are" paragraph: Could be considered introductory but not a required heading. We could include as a

    before sections? The instruction says output only HTML fragment; we can include a

    for that description as it's substantive. It's not a heading; we can just put it as a paragraph. But we need to avoid repeating job title; we don't have job title. Let's craft:

    Samsara (NYSE: IOT) is the pioneer of the Connected Operations™ Cloud, which is a platform that enables organizations that depend on physical operations to harness Internet of Things (IoT) data to develop actionable insights and improve their operations. At Samsara, we are helping improve the safety, efficiency and sustainability of the physical operations that power our global economy. Representing more than 40% of global GDP, these industries are the infrastructure of our planet, including agriculture, construction, field services, transportation, and manufacturing — and we are excited to help digitally transform their operations at scale. Working at Samsara means you’ll help define the future of physical operations and be on a team that’s shaping an exciting array of product solutions, including Video-Based Safety, Vehicle Telematics, Apps and Driver Workflows, and Equipment Monitoring. As part of a recently public company, you’ll have the autonomy and support to make an impact as we build for the long term.

    Then About the role heading. Extract About the role paragraph: After "About the role:" we have: "Samsara’s Select Customer Success team advises and guides our largest customers, ensuring they adopt Samsara and continuously gain business value from our products. We are the trusted point of contact for Samsara’s strategic customers throughout their lifecycle: onboarding, adoption, advocacy, and renewal. In this role, you will be part of our Implementation team, responsible for helping Enterprise customers deploy and adopt our IoT solutions for their fleet and industrial assets. Picking up where our sales teams leave off, you will own the customer relationship and ensure a successful deployment of Samsara's solution. Your customers span the entire range of businesses that power our economy, including trucking and transportation, food and beverage, passenger transit, utilities, school buses, and many others. All the while building relationships with the customer, helping them learn our system, and overall ensuring a successful customer relationship. Your role will be cross-functional in nature, working alongside and connecting Sales, Support, Sales Engineering and Product, enabling you to experience multiple aspects of a fast growing company from within. This role requires exceptional customer-facing communication skills, the ability to quickly understand a customer's business, and comfort explaining technology products to both executives and day-to-day users. In addition to this, you will champion, role model, and embed Samsara’s cultural principles (Focus on Customer Success, Build for the Long Term, Adopt a Growth Mindset, Be Inclusive, Win as a Team) as we scale globally and across new offices. This is a remote position open to candidates residing in the US except the San Francisco Bay Metro Area and Washington, D.C. Metro Area. Candidates can be from either PST or MST time zones and will be required to work in their local time zone hours. May require travel to customer sites up to 10% of the time, including overnight stays." We need to avoid duplication: Some of that appears also later under Responsibilities etc. But we must preserve all substantive info; duplication is okay? The instruction says remove duplicated lines. So we should avoid repeating same sentences. The About the role section includes some info that also appears later under Responsibilities (like champion cultural principles, remote position, travel). To avoid duplication, we could keep About the role as a high-level summary, and then Responsibilities list specifics. But we must not duplicate identical sentences. Let's see overlapping sentences: - "In addition to this, you will champion, role model, and embed Samsara’s cultural principles (Focus on Customer Success, Build for the Long Term, Adopt a Growth Mindset, Be Inclusive, Win as a Team) as we scale globally and across new offices." This appears also later under Responsibilities list: "Champion, role model, and embed Samsara’s cultural principles (Focus on Customer Success, Build for the Long Term, Adopt a Growth Mindset, Be Inclusive, Win as a Team) as we scale globally and across new offices." That's duplicate. We should keep only one occurrence. Which section is more appropriate? The Responsibilities list is a list of duties; that sentence fits there. So we can omit it from About the role. - Remote position info: "This is a remote position open to candidates residing in the US except the San Francisco Bay Metro Area and Washington, D.C. Metro Area. Candidates can be from either PST or MST time zones and will be required to work in their local time zone hours. May require travel to customer sites up to 10% of the time, including overnight stays." This also appears later under Schedule? Actually schedule section we will include remote, time zones, travel. So we should not duplicate that in About the role. We'll move those details to Schedule section. Thus About the role paragraph should be trimmed to exclude those duplicated bits. Let's craft About the role paragraph without those duplicates: "Samsara’s Select Customer Success team advises and guides our largest customers, ensuring they adopt Samsara and continuously gain business value from our products. We are the trusted point of contact for Samsara’s strategic customers throughout their lifecycle: onboarding, adoption, advocacy, and renewal. In this role, you will be part of our Implementation team, responsible for helping Enterprise customers deploy and adopt our IoT solutions for their fleet and industrial assets. Picking up where our sales teams leave off, you will own the customer relationship and ensure a successful deployment of Samsara's solution. Your customers span the entire range of businesses that power our economy, including trucking and transportation, food and beverage, passenger transit, utilities, school buses, and many others. All the while building relationships with the customer, helping them learn our system, and overall ensuring a successful customer relationship. Your role will be cross-functional in nature, working alongside and connecting Sales, Support, Sales Engineering and Product, enabling you to experience multiple aspects of a fast growing company from within. This role requires exceptional customer-facing communication skills, the ability to quickly understand a customer's business, and comfort explaining technology products to both executives and day-to-day users." That seems good. Now Responsibilities: list from "In this role, you will:" bullet points. Let's extract bullet points exactly as they appear: - Be on the front-lines and ensure our customers increase the safety, efficiency, and sustainability of their operations with our IoT platform. - Manage the deployment of Samsara technology to large-scale customers, enabling customers to achieve quick time to value in their investment. - Create launch plans and a roadmap to increase product usage. - Track implementation progress, participation, product adoption, and account health. - Run training sessions, demonstrate Samsara’s technology, and work through challenges with executives and day-to-day users of the system across numerous use cases. - Juggle multiple customer engagements in parallel and work cross-functionally to deliver an exceptional experience for our customers. - Serve as a mentor to the wider Customer Success and Support teams. - Deeply understand the Samsara platform’s capabilities and explain them to customers of all types. - Champion, role model, and embed Samsara’s cultural principles (Focus on Customer Success, Build for the Long Term, Adopt a Growth Mindset, Be Inclusive, Win as a Team) as we scale globally and across new offices. We need to ensure we didn't miss any. Also earlier there was "You should apply if:" but that's more motivational; not responsibilities. We'll ignore as not required. Now Requirements: Minimum requirements for the role bullet list: - 6+ years of experience in a senior Customer Success, account management, or strategic consulting role. - Enterprise SaaS experience preferred. - This is a demanding position with high internal visibility, that requires strong priority management and high emotional intelligence. - Experience supporting or working with technical products. - Solutions-oriented with strong problem solving skills. - Excellent consultative skills with experience in end to end system implementations. - Proven track record of building trust and communicating effectively with a wide variety of stakeholders: executives, Product and Engineering leadership, day-to-day users of our software. - Passion for going above and beyond the call of duty, taking initiative, and thriving in a fast-paced, change-heavy environment. - Diplomacy, tact, and poise under pressure when working through customer issues. - Bachelor’s degree from a 4-year institution