Customer Success - Enterprise Engagement Manager
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive info, not invent. Remove boilerplate like EEO, etc. The posting includes "About Alloy.ai" intro, "About The Role", "About You", "What You'll Do", "What We're Looking For". Also "Role is a hybrid based in Denver, CO." That's schedule info? It's location/hybrid schedule. Should we include a Schedule section? The rule: include a section ONLY when posting has real, specific content for it. It says "Role is a hybrid based in Denver, CO. Hybrid is defined by our company as 3+ days/week in the office when not on vacation." That's schedule info. So we could create a Schedule section with that content. Also maybe Benefits? Not present. Pay? Not present. Skills? Could be part of requirements but we can embed in Requirements.
We need to not repeat job title as heading. The job title is Engagement Manager. Not to be used as heading.
We need to output only HTML fragment, no /, no markdown fences.
Let's structure:
About the role
... (the paragraph(s) from About The Role)
Responsibilities
- ... each bullet from What You'll Do
Requirements
- ... each bullet from What We're Looking For
Schedule
Role is a hybrid based in Denver, CO. Hybrid is defined by our company as 3+ days/week in the office when not on vacation.
We also might include "About You" as part of Requirements? But we have separate "About You" describing personal traits. Could be part of Requirements or maybe a separate "Qualifications"? The rule: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have About the role, Responsibilities, Requirements (could include What We're Looking For and About You). Could also split into Qualifications and Skills but not needed. Keep few substantive sections.
We must preserve all substantive info. The "About You" paragraph includes personal traits. We'll include that in Requirements section as bullet points? It's prose, not list. Could be a under Requirements. But we need to use
- for any list of duties/requirements/benefits. The "About You" is not a list but prose; we can keep as
. However the rule says use
- for any list of duties/requirements/benefits. It doesn't forbid using
for prose within a section. So we can have a
for About You prose, then a
for What We're Looking For.
But we need to avoid duplication. Let's extract the exact text.
About The Role paragraph(s):
"We are looking for an Engagement Manager for our Client Solutions team. You will lead some of our most strategic customer engagements, with the core objective of delivering business value. At Alloy, we value our customers above everything else. We believe that the success of the companies we work with, and of the individuals within them, is perhaps the single most important and valuable indicator of our product’s performance and our own potential. Every part of the organization works toward this objective, and Client Solutions takes the lead. In this role, you will be the face of the company for some of our key strategic customers. You will understand their needs and priorities, translate them into attainable objectives and successfully execute against them. You’ll get exposed to diverse issues, gaining the experience in supply chain analytics to help lead client engagements. You'll help us build a deep understanding of key metrics used by different retailers and trade partners across the supply chain and with this knowledge, you’ll drive increased profitability for our customers with their ability to make faster and more informed decisions. The knowledge you accumulate as you interact with customers will be foundational to influencing Alloy’s product roadmap, value statement, and market positioning."
That's one paragraph.
About You paragraph:
"You thrive in a small team where you can make a big impact. You are confident in your toolkit and experience, but you also love to pick up new skills and knowledge. You are a fast learner, ready to prove yourself in a challenging role with the expectation that you will rapidly pick up increased responsibilities. You have an innate drive to be successful. You want to take initiative, tackle new obstacles and solve problems we have not encountered before. Each problem you solve will leave a mark, shaping the future of our company’s strategy. You don’t shy away from even the most challenging problems and are relentless in always looking for better solutions. You pursue your personal objectives, but you are also comfortable working with an engineering-oriented team towards common goals. When you know a better way, you voice your opinion. You are naturally drawn to analytical work but also think strategically and foster relationships. You can naturally switch between detail-oriented execution, communication with all involved parties, and prioritization based on added value. You think big and want to change the way an entire industry operates."
That's a paragraph.
What You'll Do list (multiple bullet-like sentences). Let's extract each bullet:
- Lead, manage and grow Alloy’s strategic customers. You will work primarily with large corporations, supporting VP to C-level stakeholders to formulate strategic objectives, deliver against them at a fast pace, execute analytical work to show tangible ROI, while also identifying and training a “core team” of customer users
- Act as the primary point of contact for assigned customers from kickoff through and including renewal
- Collaborate with customers to create long-lasting business connections, strengthening all customer relationships and building them into true business partnerships
- Support customers through implementation, training and onboarding, working closely with cross-functional Alloy.ai teams to ensure reporting and data are accurate and align with customer objectives
- Deliver against valuable short term objectives and keep new and ongoing projects on track
- Monitor customer activity and meet with stakeholders on a recurring basis to improve customer understanding, drive business, and discuss areas of improvement
- Surface and drive expansion opportunities with existing customers through a consultative mindset in partnership with Sales and the Executive team. Work with a group of “core users” through relationship management, training and support, to make Alloy.ai a trusted and integral part of the customer’s regular course of business
- Conduct business value reviews to grow and retain book of business
- Execute and present value-driving analysis in Alloy.ai and, in collaboration with users, turn these into repeatable processes at customer organizations
- Act as the internal “voice of the customer”, gathering and prioritizing user feedback, translating ideas and obstacles into actionable, engineering-friendly development requests
- Work cross-functionally to partner on product and marketing initiatives as well as help drive scale as our business grows. Be a leader to other Customer Success Managers on the team, coaching and mentoring others
We need to preserve all. We'll put each as - .
What We're Looking For list:
- 4+ years of experience in SaaS customer success, management consulting or related analytical, consultative, client-facing fields
- Exceptional analytical problem-solving skills, with the ability to understand technical details while staying focused on business objectives
- Demonstrated senior selling skills within consultative projects
- Superior academic record in a quantitative field
- Outstanding project management, organization, work ethic
- Highly motivated, self-directed, team player
- Ability to build long-lasting relationships with senior executives and functional managers, acting as a trusted outside resource for problem structuring
- Ownership mindset demonstrating drive, initiative, energy and a sense of urgency
- Able to thrive in a small team with a highly dynamic work environment, switching rapidly from strategy to execution
We'll put each as
- .
Schedule section: "Role is a hybrid based in Denver, CO. Hybrid is defined by our company as 3+ days/week in the office when not on vacation."
We'll put as
.
Now produce HTML fragment.
Make sure no extra text. Use proper nesting.
Let's craft:
About the role
We are looking for an Engagement Manager for our Client Solutions team. You will lead some of our most strategic customer engagements, with the core objective of delivering business value. At Alloy, we value our customers above everything else. We believe that the success of the companies we work with, and of the individuals within them, is perhaps the single most important and valuable indicator of our product’s performance and our own potential. Every part of the organization works toward this objective, and Client Solutions takes the lead. In this role, you will be the face of the company for some of our key strategic customers. You will understand their needs and priorities, translate them into attainable objectives and successfully execute against them. You’ll get exposed to diverse issues, gaining the experience in supply chain analytics to help lead client engagements. You'll help us build a deep understanding of key metrics used by different retailers and trade partners across the supply chain and with this knowledge, you’ll drive increased profitability for our customers with their ability to make faster and more informed decisions. The knowledge you accumulate as you interact with customers will be foundational to influencing Alloy’s product roadmap, value statement, and market positioning.
About you
maybe we could include as separate section? The rule allows headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About you" is not in list but could be considered Qualifications? However we can incorporate into Requirements. But we have to preserve all info. Could add a About you
but not in allowed list? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. So we can use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings but not strictly limited. Safer to stick to those. We could put About You content under Requirements or Qualifications. Let's put under Requirements as a
then a
for the bullet list.
Thus:
Requirements
You thrive in a small team where you can make a big impact. You are confident in your toolkit and experience, but you also love to pick up new skills and knowledge. You are a fast learner, ready to prove yourself in a challenging role with the expectation that you will rapidly pick up increased responsibilities. You have an innate drive to be successful. You want to take initiative, tackle new obstacles and solve problems we have not encountered before. Each problem you solve will leave a mark, shaping the future of our company’s strategy. You don’t shy away from even the most challenging problems and are relentless in always looking for better solutions. You pursue your personal objectives, but you are also comfortable working with an engineering-oriented team towards common goals. When you know a better way, you voice your opinion. You are naturally drawn to analytical work but also think strategically and foster relationships. You can naturally switch between detail-oriented execution, communication with all involved parties, and prioritization based on added value. You think big and want to change the way an entire industry operates.
- 4+ years of experience in SaaS customer success, management consulting or related analytical, consultative, client-facing fields
- Exceptional analytical problem-solving skills, with the ability to understand technical details while staying focused on business objectives
- Demonstrated senior selling skills within consultative projects
- Superior academic record in a quantitative field
- Outstanding project management, organization, work ethic
for prose. We must preserve all substantive info, not invent. Remove boilerplate like EEO, etc. The posting includes "About Alloy.ai" intro, "About The Role", "About You", "What You'll Do", "What We're Looking For". Also "Role is a hybrid based in Denver, CO." That's schedule info? It's location/hybrid schedule. Should we include a Schedule section? The rule: include a section ONLY when posting has real, specific content for it. It says "Role is a hybrid based in Denver, CO. Hybrid is defined by our company as 3+ days/week in the office when not on vacation." That's schedule info. So we could create a Schedule section with that content. Also maybe Benefits? Not present. Pay? Not present. Skills? Could be part of requirements but we can embed in Requirements. We need to not repeat job title as heading. The job title is Engagement Manager. Not to be used as heading. We need to output only HTML fragment, no /, no markdown fences. Let's structure:
About the role
... (the paragraph(s) from About The Role)
Responsibilities
- ... each bullet from What You'll Do
Requirements
- ... each bullet from What We're Looking For
Schedule
Role is a hybrid based in Denver, CO. Hybrid is defined by our company as 3+ days/week in the office when not on vacation.
We also might include "About You" as part of Requirements? But we have separate "About You" describing personal traits. Could be part of Requirements or maybe a separate "Qualifications"? The rule: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have About the role, Responsibilities, Requirements (could include What We're Looking For and About You). Could also split into Qualifications and Skills but not needed. Keep few substantive sections. We must preserve all substantive info. The "About You" paragraph includes personal traits. We'll include that in Requirements section as bullet points? It's prose, not list. Could be aunder Requirements. But we need to use
- for any list of duties/requirements/benefits. The "About You" is not a list but prose; we can keep as
. However the rule says use
- for any list of duties/requirements/benefits. It doesn't forbid using
for prose within a section. So we can have a
for About You prose, then a
- for What We're Looking For.
But we need to avoid duplication. Let's extract the exact text.
About The Role paragraph(s):
"We are looking for an Engagement Manager for our Client Solutions team. You will lead some of our most strategic customer engagements, with the core objective of delivering business value. At Alloy, we value our customers above everything else. We believe that the success of the companies we work with, and of the individuals within them, is perhaps the single most important and valuable indicator of our product’s performance and our own potential. Every part of the organization works toward this objective, and Client Solutions takes the lead. In this role, you will be the face of the company for some of our key strategic customers. You will understand their needs and priorities, translate them into attainable objectives and successfully execute against them. You’ll get exposed to diverse issues, gaining the experience in supply chain analytics to help lead client engagements. You'll help us build a deep understanding of key metrics used by different retailers and trade partners across the supply chain and with this knowledge, you’ll drive increased profitability for our customers with their ability to make faster and more informed decisions. The knowledge you accumulate as you interact with customers will be foundational to influencing Alloy’s product roadmap, value statement, and market positioning."
That's one paragraph.
About You paragraph:
"You thrive in a small team where you can make a big impact. You are confident in your toolkit and experience, but you also love to pick up new skills and knowledge. You are a fast learner, ready to prove yourself in a challenging role with the expectation that you will rapidly pick up increased responsibilities. You have an innate drive to be successful. You want to take initiative, tackle new obstacles and solve problems we have not encountered before. Each problem you solve will leave a mark, shaping the future of our company’s strategy. You don’t shy away from even the most challenging problems and are relentless in always looking for better solutions. You pursue your personal objectives, but you are also comfortable working with an engineering-oriented team towards common goals. When you know a better way, you voice your opinion. You are naturally drawn to analytical work but also think strategically and foster relationships. You can naturally switch between detail-oriented execution, communication with all involved parties, and prioritization based on added value. You think big and want to change the way an entire industry operates."
That's a paragraph.
What You'll Do list (multiple bullet-like sentences). Let's extract each bullet:
- Lead, manage and grow Alloy’s strategic customers. You will work primarily with large corporations, supporting VP to C-level stakeholders to formulate strategic objectives, deliver against them at a fast pace, execute analytical work to show tangible ROI, while also identifying and training a “core team” of customer users
- Act as the primary point of contact for assigned customers from kickoff through and including renewal
- Collaborate with customers to create long-lasting business connections, strengthening all customer relationships and building them into true business partnerships
- Support customers through implementation, training and onboarding, working closely with cross-functional Alloy.ai teams to ensure reporting and data are accurate and align with customer objectives
- Deliver against valuable short term objectives and keep new and ongoing projects on track
- Monitor customer activity and meet with stakeholders on a recurring basis to improve customer understanding, drive business, and discuss areas of improvement
- Surface and drive expansion opportunities with existing customers through a consultative mindset in partnership with Sales and the Executive team. Work with a group of “core users” through relationship management, training and support, to make Alloy.ai a trusted and integral part of the customer’s regular course of business
- Conduct business value reviews to grow and retain book of business
- Execute and present value-driving analysis in Alloy.ai and, in collaboration with users, turn these into repeatable processes at customer organizations
- Act as the internal “voice of the customer”, gathering and prioritizing user feedback, translating ideas and obstacles into actionable, engineering-friendly development requests
- Work cross-functionally to partner on product and marketing initiatives as well as help drive scale as our business grows. Be a leader to other Customer Success Managers on the team, coaching and mentoring others
We need to preserve all. We'll put each as
- . What We're Looking For list: - 4+ years of experience in SaaS customer success, management consulting or related analytical, consultative, client-facing fields - Exceptional analytical problem-solving skills, with the ability to understand technical details while staying focused on business objectives - Demonstrated senior selling skills within consultative projects - Superior academic record in a quantitative field - Outstanding project management, organization, work ethic - Highly motivated, self-directed, team player - Ability to build long-lasting relationships with senior executives and functional managers, acting as a trusted outside resource for problem structuring - Ownership mindset demonstrating drive, initiative, energy and a sense of urgency - Able to thrive in a small team with a highly dynamic work environment, switching rapidly from strategy to execution We'll put each as
- .
Schedule section: "Role is a hybrid based in Denver, CO. Hybrid is defined by our company as 3+ days/week in the office when not on vacation."
We'll put as
. Now produce HTML fragment. Make sure no extra text. Use proper nesting. Let's craft:
About the role
We are looking for an Engagement Manager for our Client Solutions team. You will lead some of our most strategic customer engagements, with the core objective of delivering business value. At Alloy, we value our customers above everything else. We believe that the success of the companies we work with, and of the individuals within them, is perhaps the single most important and valuable indicator of our product’s performance and our own potential. Every part of the organization works toward this objective, and Client Solutions takes the lead. In this role, you will be the face of the company for some of our key strategic customers. You will understand their needs and priorities, translate them into attainable objectives and successfully execute against them. You’ll get exposed to diverse issues, gaining the experience in supply chain analytics to help lead client engagements. You'll help us build a deep understanding of key metrics used by different retailers and trade partners across the supply chain and with this knowledge, you’ll drive increased profitability for our customers with their ability to make faster and more informed decisions. The knowledge you accumulate as you interact with customers will be foundational to influencing Alloy’s product roadmap, value statement, and market positioning.
About you
maybe we could include as separate section? The rule allows headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About you" is not in list but could be considered Qualifications? However we can incorporate into Requirements. But we have to preserve all info. Could add aAbout you
but not in allowed list? The instruction: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. So we can use other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings but not strictly limited. Safer to stick to those. We could put About You content under Requirements or Qualifications. Let's put under Requirements as a
then a
- for the bullet list.
Thus:
- 4+ years of experience in SaaS customer success, management consulting or related analytical, consultative, client-facing fields
- Exceptional analytical problem-solving skills, with the ability to understand technical details while staying focused on business objectives
- Demonstrated senior selling skills within consultative projects
- Superior academic record in a quantitative field
- Outstanding project management, organization, work ethic
Requirements
You thrive in a small team where you can make a big impact. You are confident in your toolkit and experience, but you also love to pick up new skills and knowledge. You are a fast learner, ready to prove yourself in a challenging role with the expectation that you will rapidly pick up increased responsibilities. You have an innate drive to be successful. You want to take initiative, tackle new obstacles and solve problems we have not encountered before. Each problem you solve will leave a mark, shaping the future of our company’s strategy. You don’t shy away from even the most challenging problems and are relentless in always looking for better solutions. You pursue your personal objectives, but you are also comfortable working with an engineering-oriented team towards common goals. When you know a better way, you voice your opinion. You are naturally drawn to analytical work but also think strategically and foster relationships. You can naturally switch between detail-oriented execution, communication with all involved parties, and prioritization based on added value. You think big and want to change the way an entire industry operates.
- for any list of duties/requirements/benefits. It doesn't forbid using