Engagement Lead
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information, not invent or summarize away detail.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Apply now Please let sable know you found this job on Job Vista. This helps us grow! Apply now". Also remove "Job Overview Company sable Location ..."? That's metadata but we might keep location? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include location, job type, etc as a short
maybe under About the role? Or we could drop. Probably better to include a short paragraph with location and job type etc. But we need to avoid duplication.
Let's extract substantive prose:
About The Job paragraph:
"Sable built Aidan, the first AI employee who can lead customer calls using realtime voice, vision, and browser use. Aidan runs a live, two-way conversation inside a real product environment, clicking through the product like a human, watching the user's screen, and adapting the journey on the fly. Every conversation... The Engagement Lead owns the deployment of Aidan into a customer's workflows. You lead customer engagements from the first conversation through renewal and expansion; the person who scopes the pilot is the same person the customer's executive team calls a year later when they need advice on where to apply Aidan next... We're in person, but expanding to regional offices soon. Everyone spends their first month in San Francisco with the founders and engineers, then works from San Francisco or New York."
We need to preserve all substantive information; we can't omit details like "Every conversation..." truncated? The original had ellipsis. We should keep as is? Probably keep the text exactly as given, but we can remove ellipsis? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The ellipsis indicates omitted text; we should keep it as is? It's part of the posting. We'll keep it.
Key Responsibilities: multiple sentences, some duplicated. We need to deduplicate.
Let's list responsibilities from the text:
- The Engagement Lead owns the deployment of Aidan into a customer's workflows.
- You lead customer engagements from the first conversation through renewal and expansion; the person who scopes the pilot is the same person the customer's executive team calls a year later when they need advice on where to apply Aidan next.
- You'll inherit live accounts on day one, plus new companies as they come to us.
- A team of deployment strategists and FDEs will be there to support you with the execution; you build the business case, hold the relationship, and decide with the customer what gets built next and what doesn't.
- We're in person, but expanding to regional offices soon. Everyone spends their first month in San Francisco with the founders and engineers, then works from San Francisco or New York. (This appears also in About The Job; duplicate.)
- Lead first conversations with companies that come to us and decide which ones we should take on. Many companies want Aidan; your job is to pick the ones where it will work.
- Scope new deployments: one use case, which metrics get moved, what kind of impact should be expected.
- Own the continued deployment and delivery of results for our customers.
- During the deployment, own the executive relationships and the business case while the Deployment Strategist runs delivery.
- Expand the engagement: find the next team and the next use case, understand time/value tradeoffs, and present it to the customer decisions for them to make.
- Say no well: to use cases that won't be value-add for the customers and to requirements that won't move the needle on the goals they care about.
- Be an ambassador for Sable: build and develop relationships that lead to the next deployment, map the companies we should be working with, draw on our founders', investors', and customers' networks for warm introductions, show up where those leaders are, and turn your wins into case studies.
We need to remove duplicated lines: The "We're in person..." appears twice; we can keep once.
Required Skills & Abilities:
- 2–3+ years somewhere with a very high bar: MBB firms; Palantir; a top AI company; high finance; or a company you started. Years matter less than what you did there.
- You have presented to C-level executives, been challenged by them, and held the room.
- You have scoped a project with a written deliverable and a success metric, and you were held to it.
- You have worked in or around software or AI.
- You don't need to be an engineer, but you need to be fluent: you'll understand how Aidan is built, analyze his performance, and be credible with the customer's engineers and operations leads.
- You are a relationship person. Past clients still text you. Executives can count on you.
- You are hungry in a way that shows. You want the responsibility that usually arrives ten years later, and you challenge yourself to own that responsibility today.
- Bonus points if you understand how sales, marketing, and growth teams measure themselves; Aidan's KPIs come from there.
We need to separate Bonus points maybe as Skills section.
Now, we need to decide sections:
- About the role: combine About The Job paragraph plus maybe location/job type? But location/job type is minor metadata; we could include a short p after About the role.
- Responsibilities: list.
- Requirements: maybe combine Required Skills & Abilities (excluding Bonus points) as Requirements.
- Skills: Bonus points.
- Pay: Salary Negotiable.
We should not create Qualifications if we already have Requirements; but we could have both Requirements and Qualifications if we split. However the instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Required Skills & Abilities into Requirements and skip Qualifications. Skills section for Bonus points.
Thus sections: About the role, Responsibilities, Requirements, Skills, Pay.
Now we need to output HTML fragment only.
Structure:
About the role
... prose ...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Pay
Salary Negotiable
We need to ensure we don't include any extra text like markdown fences.
Now we need to craft the prose for About the role: combine the About The Job paragraph and maybe location/job type? Let's include location and job type as a short p after the main prose? Could be part of About the role.
But we must not repeat content. The About The Job paragraph already includes "We're in person, but expanding to regional offices soon. Everyone spends their first month in San Francisco with the founders and engineers, then works from San Francisco or New York." That's location info. So we can keep that.
Thus About the role prose: The paragraph(s) from About The Job.
Let's copy exactly:
"Sable built Aidan, the first AI employee who can lead customer calls using realtime voice, vision, and browser use. Aidan runs a live, two-way conversation inside a real product environment, clicking through the product like a human, watching the user's screen, and adapting the journey on the fly. Every conversation... The Engagement Lead owns the deployment of Aidan into a customer's workflows. You lead customer engagements from the first conversation through renewal and expansion; the person who scopes the pilot is the same person the customer's executive team calls a year later when they need advice on where to apply Aidan next... We're in person, but expanding to regional offices soon. Everyone spends their first month in San Francisco with the founders and engineers, then works from San Francisco or New York."
We need to ensure we keep the ellipsis as is.
Now Responsibilities list: we need to deduplicate and ensure each item is a distinct responsibility.
Let's craft list items:
- The Engagement Lead owns the deployment of Aidan into a customer's workflows.
- You lead customer engagements from the first conversation through renewal and expansion; the person who scopes the pilot is the same person the customer's executive team calls a year later when they need advice on where to apply Aidan next.
- You'll inherit live accounts on day one, plus new companies as they come to us.
- A team of deployment strategists and FDEs will be there to support you with the execution; you build the business case, hold the relationship, and decide with the customer what gets built next and what doesn't.
- Lead first conversations with companies that come to us and decide which ones we should take on; many companies want Aidan, your job is to pick the ones where it will work.
- Scope new deployments: define one use case, identify which metrics will be moved, and estimate the expected impact.
- Own the continued deployment and delivery of results for our customers.
- During the deployment, own the executive relationships and the business case while the Deployment Strategist runs delivery.
- Expand the engagement: find the next team and the next use case, understand time/value tradeoffs, and present it to the customer for them to make a decision.
- Say no to use cases that won't add value for the customer and to requirements that won't
for prose. We need to preserve all substantive information, not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Apply now Please let sable know you found this job on Job Vista. This helps us grow! Apply now". Also remove "Job Overview Company sable Location ..."? That's metadata but we might keep location? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include location, job type, etc as a short
maybe under About the role? Or we could drop. Probably better to include a short paragraph with location and job type etc. But we need to avoid duplication. Let's extract substantive prose: About The Job paragraph: "Sable built Aidan, the first AI employee who can lead customer calls using realtime voice, vision, and browser use. Aidan runs a live, two-way conversation inside a real product environment, clicking through the product like a human, watching the user's screen, and adapting the journey on the fly. Every conversation... The Engagement Lead owns the deployment of Aidan into a customer's workflows. You lead customer engagements from the first conversation through renewal and expansion; the person who scopes the pilot is the same person the customer's executive team calls a year later when they need advice on where to apply Aidan next... We're in person, but expanding to regional offices soon. Everyone spends their first month in San Francisco with the founders and engineers, then works from San Francisco or New York." We need to preserve all substantive information; we can't omit details like "Every conversation..." truncated? The original had ellipsis. We should keep as is? Probably keep the text exactly as given, but we can remove ellipsis? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The ellipsis indicates omitted text; we should keep it as is? It's part of the posting. We'll keep it. Key Responsibilities: multiple sentences, some duplicated. We need to deduplicate. Let's list responsibilities from the text: - The Engagement Lead owns the deployment of Aidan into a customer's workflows. - You lead customer engagements from the first conversation through renewal and expansion; the person who scopes the pilot is the same person the customer's executive team calls a year later when they need advice on where to apply Aidan next. - You'll inherit live accounts on day one, plus new companies as they come to us. - A team of deployment strategists and FDEs will be there to support you with the execution; you build the business case, hold the relationship, and decide with the customer what gets built next and what doesn't. - We're in person, but expanding to regional offices soon. Everyone spends their first month in San Francisco with the founders and engineers, then works from San Francisco or New York. (This appears also in About The Job; duplicate.) - Lead first conversations with companies that come to us and decide which ones we should take on. Many companies want Aidan; your job is to pick the ones where it will work. - Scope new deployments: one use case, which metrics get moved, what kind of impact should be expected. - Own the continued deployment and delivery of results for our customers. - During the deployment, own the executive relationships and the business case while the Deployment Strategist runs delivery. - Expand the engagement: find the next team and the next use case, understand time/value tradeoffs, and present it to the customer decisions for them to make. - Say no well: to use cases that won't be value-add for the customers and to requirements that won't move the needle on the goals they care about. - Be an ambassador for Sable: build and develop relationships that lead to the next deployment, map the companies we should be working with, draw on our founders', investors', and customers' networks for warm introductions, show up where those leaders are, and turn your wins into case studies. We need to remove duplicated lines: The "We're in person..." appears twice; we can keep once. Required Skills & Abilities: - 2–3+ years somewhere with a very high bar: MBB firms; Palantir; a top AI company; high finance; or a company you started. Years matter less than what you did there. - You have presented to C-level executives, been challenged by them, and held the room. - You have scoped a project with a written deliverable and a success metric, and you were held to it. - You have worked in or around software or AI. - You don't need to be an engineer, but you need to be fluent: you'll understand how Aidan is built, analyze his performance, and be credible with the customer's engineers and operations leads. - You are a relationship person. Past clients still text you. Executives can count on you. - You are hungry in a way that shows. You want the responsibility that usually arrives ten years later, and you challenge yourself to own that responsibility today. - Bonus points if you understand how sales, marketing, and growth teams measure themselves; Aidan's KPIs come from there. We need to separate Bonus points maybe as Skills section. Now, we need to decide sections: - About the role: combine About The Job paragraph plus maybe location/job type? But location/job type is minor metadata; we could include a short p after About the role. - Responsibilities: list. - Requirements: maybe combine Required Skills & Abilities (excluding Bonus points) as Requirements. - Skills: Bonus points. - Pay: Salary Negotiable. We should not create Qualifications if we already have Requirements; but we could have both Requirements and Qualifications if we split. However the instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Required Skills & Abilities into Requirements and skip Qualifications. Skills section for Bonus points. Thus sections: About the role, Responsibilities, Requirements, Skills, Pay. Now we need to output HTML fragment only. Structure:
About the role
... prose ...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Pay
Salary Negotiable
We need to ensure we don't include any extra text like markdown fences. Now we need to craft the prose for About the role: combine the About The Job paragraph and maybe location/job type? Let's include location and job type as a short p after the main prose? Could be part of About the role. But we must not repeat content. The About The Job paragraph already includes "We're in person, but expanding to regional offices soon. Everyone spends their first month in San Francisco with the founders and engineers, then works from San Francisco or New York." That's location info. So we can keep that. Thus About the role prose: The paragraph(s) from About The Job. Let's copy exactly: "Sable built Aidan, the first AI employee who can lead customer calls using realtime voice, vision, and browser use. Aidan runs a live, two-way conversation inside a real product environment, clicking through the product like a human, watching the user's screen, and adapting the journey on the fly. Every conversation... The Engagement Lead owns the deployment of Aidan into a customer's workflows. You lead customer engagements from the first conversation through renewal and expansion; the person who scopes the pilot is the same person the customer's executive team calls a year later when they need advice on where to apply Aidan next... We're in person, but expanding to regional offices soon. Everyone spends their first month in San Francisco with the founders and engineers, then works from San Francisco or New York." We need to ensure we keep the ellipsis as is. Now Responsibilities list: we need to deduplicate and ensure each item is a distinct responsibility. Let's craft list items: - The Engagement Lead owns the deployment of Aidan into a customer's workflows. - You lead customer engagements from the first conversation through renewal and expansion; the person who scopes the pilot is the same person the customer's executive team calls a year later when they need advice on where to apply Aidan next. - You'll inherit live accounts on day one, plus new companies as they come to us. - A team of deployment strategists and FDEs will be there to support you with the execution; you build the business case, hold the relationship, and decide with the customer what gets built next and what doesn't. - Lead first conversations with companies that come to us and decide which ones we should take on; many companies want Aidan, your job is to pick the ones where it will work. - Scope new deployments: define one use case, identify which metrics will be moved, and estimate the expected impact. - Own the continued deployment and delivery of results for our customers. - During the deployment, own the executive relationships and the business case while the Deployment Strategist runs delivery. - Expand the engagement: find the next team and the next use case, understand time/value tradeoffs, and present it to the customer for them to make a decision. - Say no to use cases that won't add value for the customer and to requirements that won't