Customer Engagement Specialist (San Francisco)
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide which content goes where.
Sections present: About You (paragraph about personal traits). About Us (company description). What You Will Do (list of duties). What You Bring To The Table (requirements/qualifications). Benefits (list). Pay (salary range). Possibly also "Schedule"? Not mentioned. So we omit Schedule.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
We need to preserve all substantive info: include location? The posting says "Customer Engagement Specialist San Francisco, CA" and later "This position is located in downtown San Francisco, in-office, conveniently adjacent to public transit." That's substantive. We can include that in a short
maybe under a heading? There's no heading for location; we can just put a
after the title? Since we cannot add a heading for location unless we have a section like "Location". Not required but we could include a short p after the title before sections. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Location is not minor metadata; it's substantive. Could be placed as a
before sections. Probably okay.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft:
Location: Downtown San Francisco, in-office, adjacent to public transit.
Then sections:
About You
You love to tackle problems and build solutions. When intrigued by an idea, you focus your energy and dedicate your mind to learn everything you can about it, quickly! Then, you figure out how to apply what you’ve learned to the issue at hand and propel it forward. Facing big challenges head on inspires you. You chart the process and you own the outcome. You love helping people. You enjoy sharing knowledge and get energized by smart people navigating complicated problems together. Reaching milestones motivates you. You believe quick iteration and immediate customer feedback are keys to developing disruptive software. You’re an early riser. And, you're ready for your next adventure.
About Us
Levelpath is the modern AI procurement platform for global enterprises. Since our founding in 2022, we have been on a mission to make procurement delightful. Uniquely intuitive, Levelpath makes procurement more nimble in days and unlocks savings in weeks, while delivering clarity, control and intelligence for all stakeholders. Levelpath provides a complete view of spend for procurement, finance, legal and IT - from intake and sourcing to contracting and payment. Built in AI delivers contextually relevant and genuinely helpful answers, uncovering valuable opportunities and dramatically increasing efficiency. Global brands trust Levelpath’s deep procurement expertise to transform their business outcomes and drive value from their supplier relationships.
What You Will Do
- Drive impact by focusing on customer experience.
- Answer support tickets.
- Provide users guidance when they are stuck.
- Generate product documentation.
- Report bugs to product & engineering.
- Be the first touch point for users encountering difficulties with the product and a reliable resource to resolve their questions and issues.
- Learn the intricacies of a cutting edge enterprise product and be a Levelpath product expert for our customer base to drive product adoption and satisfaction.
- Interact directly with Product and Engineering teams to identify areas where we can better serve our customer base.
- Build best practice guides and playbooks to ensure our customers and their users are set up for success.
- Act as a trusted advisor & support customer health by understanding their users’ friction points when using Levelpath.
- Partner with the executive team to help build, optimize, and scale our processes, assets, & systems (Zendesk & Salesforce).
What You Bring To The Table
- Empathy, patience, and a sense of urgency when supporting customers.
- 4+ years of experience in a direct customer-facing/customer management role.
- B2B SaaS experience in a fast-paced environment.
- BA or BS.
- Demonstrated experience problem-solving with attention to detail.
- Stellar organizational skills and experience improving processes.
- Strong written and verbal communication skills.
- Adaptability and ability to flourish in a fast-paced environment.
- Comfort in managing multiple workstreams.
- Ability to communicate with stakeholders across product and engineering.
- Effective collaboration and self-starter mindset.
- Availability for some travel - when the time comes to visit your customers!
Benefits
- 100% Medical, dental, and vision insurance.
- Flexible PTO, Parental Leave, Sick Leave.
- Competitive compensation and equity package.
- 401k.
- Commuter benefits.
- In-office snacks and Friday team lunches.
- Team-driven happy hours and celebrations.
Pay
The estimated annual OTE for this role is $90,000 - $132,000.
We must ensure no duplicate lines. Also ensure we didn't include EEO etc. We removed that.
Check for any leftover boilerplate: At end there is EEO statement; we removed. Also "Pathfinders Wanted - Join Us!" maybe considered a heading? It's not a standard heading; we could treat as part of About Us? But we already have About Us. The line "Pathfinders Wanted - Join Us!" is a call to action; we could incorporate into About Us paragraph or drop as minor. Since it's not substantive detail about role, we can drop it. It's not required to preserve all? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Is "Pathfinders Wanted - Join Us!" substantive? It's more of a marketing tagline; maybe considered boilerplate. I'd drop it.
Also "We’re looking for a Customer Engagement Specialist to join our team." That's basically the job title; we already have title outside; we can drop.
Also "Reporting into Product, you will not only get a front row seat..." That's part of About Us? Actually it's about the role. Could be included in About Us or maybe a separate section like "About the role". But we don't have a heading for About the role; we could incorporate into About Us or What You Will Do. The sentence: "Reporting into Product, you will not only get a front row seat to what it takes to scale a successful product from the early days, but you will play a critical role in developing strong relationships with our customers and users, and advocating on their behalf to continuously improve our platform. We are building a world class support team – obsessed with helping our customers, and focused on getting them back on the right path when challenges arise. This is a rewarding opportunity to drive meaningful impact and build from the ground up alongside a leadership team passionate about making a difference in the procurement world." This is substantive about the role. Could be placed under a section like "About the role". But we don't have that heading in the list of allowed headings? The list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could use About the role
for that content. However we already have About You and About Us. The role description could be About the role. Let's consider: The posting includes "About You", "About Us", then "What You Will Do", "What You Bring To The Table". The role description paragraph after "We’re looking for a Customer Engagement Specialist..." could be considered "About the role". Since we have a heading for About the role allowed, we should use it to avoid losing substantive info. However we must not create a heading with filler. This paragraph is substantive.
Thus we should add a section About the role
with that paragraph.
But we already have About You and About Us. The instructions say: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use About the role.
Thus we need to incorporate that paragraph.
Let's extract that paragraph:
"We’re looking for a Customer Engagement Specialist to join our team. Reporting into Product, you will not only get a front row seat to what it takes to scale a successful product from the early days, but you will play a critical role in developing strong relationships with our customers and users, and advocating on their behalf to continuously improve our platform. We are building a world class support team – obsessed with helping our customers, and focused on getting them back on the right path when challenges arise. This is a rewarding opportunity to drive meaningful impact and build from the ground up alongside a leadership team passionate about making a difference in the procurement world."
We should remove the first sentence about looking for a Customer Engagement Specialist as it's redundant with title; but we can keep it as part of About the role. However we might consider it minor metadata; but it's still substantive. We'll keep it.
Now we need to ensure we don't duplicate content elsewhere. The "What You Will Do" already covers duties. The About the role is more about opportunity.
Thus final sections order: About You, About Us, About the role, What You Will Do, What You Bring To The Table, Benefits, Pay.
We also have location p at top.
Let's craft final HTML.
Check for any other substantive info: "This position is located in downtown San Francisco, in-office, conveniently adjacent to public transit." We used location p.
Also "While a startup, we offer most standard benefits you’d expect from a mature organization - even transportation and 401k!" That's covered in benefits but we might want to mention transportation and 401k already in benefits list. We have commuter benefits and 401k. Good.
"You may leverage any devices and tools that allow you to do your best work." That's a substantive detail about tools. Not covered elsewhere. Could be added to What You Will Do or maybe a separate line. We could add a bullet under What You Will Do: "Leverage any devices and tools that allow you to do your best work." Or incorporate into Benefits? It's more about work environment. Could add to What You Will Do as a bullet.
Also "You’ll be a part of a spirited international team, in an agile environment with short decision paths and quick delivery." That's about team environment. Could be added to About Us or maybe a bullet under About Us. We'll add to About Us paragraph.
Let's incorporate these.
Update About Us paragraph to include: "You’ll be a part of a spirited international team, in an agile environment with short decision paths and quick delivery." Also "While a startup, we offer most standard benefits you’d expect from a mature organization - even transportation and 40
for prose. We need to decide which content goes where. Sections present: About You (paragraph about personal traits). About Us (company description). What You Will Do (list of duties). What You Bring To The Table (requirements/qualifications). Benefits (list). Pay (salary range). Possibly also "Schedule"? Not mentioned. So we omit Schedule. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. We need to preserve all substantive info: include location? The posting says "Customer Engagement Specialist San Francisco, CA" and later "This position is located in downtown San Francisco, in-office, conveniently adjacent to public transit." That's substantive. We can include that in a short
maybe under a heading? There's no heading for location; we can just put a
after the title? Since we cannot add a heading for location unless we have a section like "Location". Not required but we could include a short p after the title before sections. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Location is not minor metadata; it's substantive. Could be placed as a
before sections. Probably okay. We need to output only HTML fragment, no /, no markdown fences. Let's craft:
Location: Downtown San Francisco, in-office, adjacent to public transit.
Then sections:About You
You love to tackle problems and build solutions. When intrigued by an idea, you focus your energy and dedicate your mind to learn everything you can about it, quickly! Then, you figure out how to apply what you’ve learned to the issue at hand and propel it forward. Facing big challenges head on inspires you. You chart the process and you own the outcome. You love helping people. You enjoy sharing knowledge and get energized by smart people navigating complicated problems together. Reaching milestones motivates you. You believe quick iteration and immediate customer feedback are keys to developing disruptive software. You’re an early riser. And, you're ready for your next adventure.
About Us
Levelpath is the modern AI procurement platform for global enterprises. Since our founding in 2022, we have been on a mission to make procurement delightful. Uniquely intuitive, Levelpath makes procurement more nimble in days and unlocks savings in weeks, while delivering clarity, control and intelligence for all stakeholders. Levelpath provides a complete view of spend for procurement, finance, legal and IT - from intake and sourcing to contracting and payment. Built in AI delivers contextually relevant and genuinely helpful answers, uncovering valuable opportunities and dramatically increasing efficiency. Global brands trust Levelpath’s deep procurement expertise to transform their business outcomes and drive value from their supplier relationships.
What You Will Do
- Drive impact by focusing on customer experience.
- Answer support tickets.
- Provide users guidance when they are stuck.
- Generate product documentation.
- Report bugs to product & engineering.
- Be the first touch point for users encountering difficulties with the product and a reliable resource to resolve their questions and issues.
- Learn the intricacies of a cutting edge enterprise product and be a Levelpath product expert for our customer base to drive product adoption and satisfaction.
- Interact directly with Product and Engineering teams to identify areas where we can better serve our customer base.
- Build best practice guides and playbooks to ensure our customers and their users are set up for success.
- Act as a trusted advisor & support customer health by understanding their users’ friction points when using Levelpath.
- Partner with the executive team to help build, optimize, and scale our processes, assets, & systems (Zendesk & Salesforce).
What You Bring To The Table
- Empathy, patience, and a sense of urgency when supporting customers.
- 4+ years of experience in a direct customer-facing/customer management role.
- B2B SaaS experience in a fast-paced environment.
- BA or BS.
- Demonstrated experience problem-solving with attention to detail.
- Stellar organizational skills and experience improving processes.
- Strong written and verbal communication skills.
- Adaptability and ability to flourish in a fast-paced environment.
- Comfort in managing multiple workstreams.
- Ability to communicate with stakeholders across product and engineering.
- Effective collaboration and self-starter mindset.
- Availability for some travel - when the time comes to visit your customers!
Benefits
- 100% Medical, dental, and vision insurance.
- Flexible PTO, Parental Leave, Sick Leave.
- Competitive compensation and equity package.
- 401k.
- Commuter benefits.
- In-office snacks and Friday team lunches.
- Team-driven happy hours and celebrations.
Pay
The estimated annual OTE for this role is $90,000 - $132,000.
We must ensure no duplicate lines. Also ensure we didn't include EEO etc. We removed that. Check for any leftover boilerplate: At end there is EEO statement; we removed. Also "Pathfinders Wanted - Join Us!" maybe considered a heading? It's not a standard heading; we could treat as part of About Us? But we already have About Us. The line "Pathfinders Wanted - Join Us!" is a call to action; we could incorporate into About Us paragraph or drop as minor. Since it's not substantive detail about role, we can drop it. It's not required to preserve all? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Is "Pathfinders Wanted - Join Us!" substantive? It's more of a marketing tagline; maybe considered boilerplate. I'd drop it. Also "We’re looking for a Customer Engagement Specialist to join our team." That's basically the job title; we already have title outside; we can drop. Also "Reporting into Product, you will not only get a front row seat..." That's part of About Us? Actually it's about the role. Could be included in About Us or maybe a separate section like "About the role". But we don't have a heading for About the role; we could incorporate into About Us or What You Will Do. The sentence: "Reporting into Product, you will not only get a front row seat to what it takes to scale a successful product from the early days, but you will play a critical role in developing strong relationships with our customers and users, and advocating on their behalf to continuously improve our platform. We are building a world class support team – obsessed with helping our customers, and focused on getting them back on the right path when challenges arise. This is a rewarding opportunity to drive meaningful impact and build from the ground up alongside a leadership team passionate about making a difference in the procurement world." This is substantive about the role. Could be placed under a section like "About the role". But we don't have that heading in the list of allowed headings? The list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could use