Core Client Advocate, Northern California

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 not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, etc. Must preserve substantive info. Let's parse the posting. First paragraph: company description - maybe not needed? It's background but not part of role? Could be part of About the role? The instructions: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. We have: - About the role: description of role: "You’ll be the primary interface between our customers and our team, representing the voice of the customer to our engineers and supporting the customer with new updates, workflows, and features to the platform. This involves interpreting multiple and complex data sources to ensure all users are working in Peregrine to the best of their ability, including dashboards, metrics, and onsite visits to build deep relationships with all agency stakeholders." Also earlier: "We are looking for a Customer Advocate to own all customer relationships throughout the contract." That's also about role. - Responsibilities: The Role section: "Full user adoption and long-term relationships are your top priority in this role. You lend an empathetic ear to solve our customer’s challenging problems and unlock new ways that provide value to their work. It’s important to find creative ways to work through internal roadblocks so Peregrine can create success throughout the entire agency. You’ll also partner with other teams to develop case studies and success stories for Peregrine’s outsized value. This role is critical to customer retention and growth and the right candidate needs to be an active and empathetic listener, a creative value-panhandler, and a proactive problem solver. The position is field-based and while does not have an in-office requirement, you are expected to be on site with customers 50-60% of the time - regions include San Francisco, Sonoma, and Solano Counties." That's responsibilities. - About You: bullet list of personal traits: "You place a high value on maintaining positive customer relationships; you care about their needs and how we can give the best solution in an empathetic wayYou are energized when working directly with customers and crave a role at the intersection of user engagement and product adoptionYou have a passion for uncovering and addressing roadblocks so every user is always satisfiedYou are creative & have adept critical thinking skills to problem-solve barriers at customer agenciesYou have incredible attention to detail, are highly organized, and can manage multiple projects at onceYou bring a curious and humble mindset to collaboratively solving difficult customer challenges with other team members" That could be Qualifications or Skills? It's more about personal attributes. Could be Qualifications. - What We Look For: list of requirements: "3-5 years of direct experience supporting customers to adopt technical software solutionsPrevious work directly or in a vendor relationship with law enforcement, public safety, or the military is strongly preferred, not requiredSignificant experience in the enterprise software space, startup experience also a plusAbility to listen to synthesize user feedback and be the first line of support throughout the contractSuccessful track record of zero churn and positive net revenue retentionExcellent relationship-building skills with the ability to communicate technical and non-technical concepts to a diverse audienceAbility to travel :60% of the time" That's Requirements. - Pay: "Annual Salary + Benefits + Equity (if applicable) + Bonus (if applicable) $110,000—$130,000 USD Actual compensation is influenced by a wide array of factors including but not limited to skill set, level of experience, certifications or licenses, and specific work location." That's Pay. - Benefits: "Information on the benefits offered is here." That's vague, not specific. No actual benefits listed. So we should not create Benefits section because no specific content. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits not stated specifically, just link. So we omit Benefits. - Schedule: Not explicitly given besides travel expectation 50-60% on site. That's maybe schedule? Could be considered schedule but it's about travel. The instruction: include schedule only if posting actually states them. It does state expected to be on site with customers 50-60% of the time. That's schedule/travel expectation. Could be considered Schedule. However they also have Ability to travel :60% of the time in requirements. Might be redundant. We could include Schedule section with that detail. But we need to avoid filler. It's specific: expected to be on site with customers 50-60% of the time; regions include San Francisco, Sonoma, and Solano Counties. That's schedule/travel. So we can include Schedule. We also have "Annual Salary + Benefits + Equity (if applicable) + Bonus (if applicable) $110,000—$130,000 USD". That's Pay. We need to avoid repeating job title. Not include headings for minor metadata. We need to output only HTML fragment, no html/body tags, no markdown fences. We'll produce sections: About the role, Responsibilities, Qualifications (or Skills?), Requirements, Pay, Schedule. But we need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can omit those lacking content. We have content for About the role, Responsibilities, Qualifications (the About You), Requirements, Pay, Schedule. Skills: we could merge some skills into Qualifications or Requirements. But we have no explicit skills list separate. Could omit Skills. Thus output:

About the role

...

Responsibilities

• ...
...

Qualifications

• ...
...

Requirements

• ...
...

Pay

...

Schedule

...

We need to preserve all substantive information, not invent or summarize away detail. Must not lose details. Let's extract each piece precisely. About the role: combine first paragraph and maybe the "We are looking for a Customer Advocate to own all customer relationships throughout the contract." That's part of role description. So About the role text: "We are looking for a Customer Advocate to own all customer relationships throughout the contract. You’ll be the primary interface between our customers and our team, representing the voice of the customer to our engineers and supporting the customer with new updates, workflows, and features to the platform. This involves interpreting multiple and complex data sources to ensure all users are working in Peregrine to the best of their ability, including dashboards, metrics, and onsite visits to build deep relationships with all agency stakeholders." Make sure to keep punctuation. Responsibilities: from "The Role" paragraph. Full user adoption and long-term relationships are your top priority in this role. You lend an empathetic ear to solve our customer’s challenging problems and unlock new ways that provide value to their work. It’s important to find creative ways to work through internal roadblocks so Peregrine can create success throughout the entire agency. You’ll also partner with other teams to develop case studies and success stories for Peregrine’s outsized value. This role is critical to customer retention and growth and the right candidate needs to be an active and empathetic listener, a creative value-panhandler, and a proactive problem solver. The position is field-based and while does not have an in-office requirement, you are expected to be on site with customers 50-60% of the time - regions include San Francisco, Sonoma, and Solano Counties. We could split into list items for readability but not required; we can use

• for any list of duties/requirements/benefits. The responsibilities are a paragraph; we could keep as

  . The instruction: Use

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

    for prose. Since responsibilities are not a list but prose, we can use

    . However we could break into list but not needed. We'll use

    . Qualifications: from "About You". It's a series of statements separated by no punctuation; we need to preserve them. Could make list items each trait. Let's parse: "You place a high value on maintaining positive customer relationships; you care about their needs and how we can give the best solution in an empathetic wayYou are energized when working directly with customers and crave a role at the intersection of user engagement and product adoptionYou have a passion for uncovering and addressing roadblocks so every user is always satisfiedYou are creative & have adept critical thinking skills to problem-solve barriers at customer agenciesYou have incredible attention to detail, are highly organized, and can manage multiple projects at onceYou bring a curious and humble mindset to collaboratively solving difficult customer challenges with other team members" We need to split into sensible items. Could separate by the capitalized "You". Let's do: - You place a high value on maintaining positive customer relationships; you care about their needs and how we can give the best solution in an empathetic way. - You are energized when working directly with customers and crave a role at the intersection of user engagement and product adoption. - You have a passion for uncovering and addressing roadblocks so every user is always satisfied. - You are creative & have adept critical thinking skills to problem-solve barriers at customer agencies. - You have incredible attention to detail, are highly organized, and can manage multiple projects at once. - You bring a curious and humble mindset to collaboratively solving difficult customer challenges with other team members. That preserves all. Requirements: from "What We Look For". Let's extract: "3-5 years of direct experience supporting customers to adopt technical software solutionsPrevious work directly or in a vendor relationship with law enforcement, public safety, or the military is strongly preferred, not requiredSignificant experience in the enterprise software space, startup experience also a plusAbility to listen to synthesize user feedback and be the first line of support throughout the contractSuccessful track record of zero churn and positive net revenue retentionExcellent relationship-building skills with the ability to communicate technical and non-technical concepts to a diverse audienceAbility to travel :60% of the time" We need to split into items. Let's parse: - 3-5 years of direct experience supporting customers to adopt technical software solutions. - Previous work directly or in a vendor relationship with law enforcement, public safety, or the military is strongly preferred, not required. - Significant experience in the enterprise software space; startup experience also a plus. - Ability to listen to synthesize user feedback and be the first line of support throughout the contract. - Successful track record of zero churn and positive net revenue retention. - Excellent relationship-building skills with the ability to communicate technical and non-technical concepts to a diverse audience. - Ability to travel 60% of the time. Note there is a colon after travel: "Ability to travel :60% of the time". We'll format as "Ability to travel 60% of the time." Pay: "Annual Salary + Benefits + Equity (if applicable) + Bonus (if applicable) $110,000—$130,000 USD Actual compensation is influenced by a wide array of factors including but not limited to skill set, level of experience, certifications or licenses, and specific work location." We'll keep as paragraph. Schedule: "The position is field-based and while does not have an in-office requirement, you are expected to be on site with customers 50-60% of the time - regions include San Francisco, Sonoma, and Solano Counties." Also maybe mention travel 60% but that's already in requirements. We'll include schedule: expected to be on site with customers 50-60% of the time; regions include San Francisco, Sonoma, and Solano Counties. We could also mention