Technical Enablement Manager for Customer Team
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Include a section only when posting has real, specific content. Remove boilerplate etc.
We need to parse the posting.
Company Description: description about ServiceNow. Could be "About the role"? Actually "Company Description" is about the company, not role. Could be "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content.
We have:
- Company Description: description of ServiceNow. Could be placed under "About the role"? Or maybe we can have a section "About the role" containing that description? Usually "About the role" is description of role, but we have "Job Description" which details responsibilities. The "Company Description" is about the company. Could we put it under "About the role"? Might be okay but not exactly. However we need to include substantive info; we can include a section "About the role" with the company description? Might be odd but acceptable. Alternatively we could omit that section if not matching headings. But we need to preserve all substantive info; we cannot drop company description. So we need to include it somewhere. Perhaps we can create a section "About the role" and put the company description there, even though it's about company. Or we could create a custom heading? Not allowed; only those headings. So we must fit into one of those.
We have "Job Description" which contains responsibilities etc. That could go under "Responsibilities". Also there is "Qualifications" section with "What You’ll Do" and "What You Bring". That includes responsibilities and qualifications. Actually "What You’ll Do" is responsibilities/duties. "What You Bring" is qualifications/requirements.
Also there is pay info: "For positions in this location, we offer a base pay of $126,800 - $221,900, plus equity (when applicable), variable/incentive compensation and benefits." Also mention benefits: health plans, 401(k) etc. So we have Pay and Benefits sections.
Schedule? Not mentioned. So we should not create Schedule section.
Skills? Not explicitly listed; maybe we can infer from qualifications but better not to create Skills unless explicit. The posting mentions "Tooling Proficiency", "Leadership & Cross-Functional Alignment". Those could be skills. But we need to decide if we create a Skills section. The instruction: prefer a few substantive sections over many thin ones. We could combine skills into Qualifications or Requirements. Probably better to have Qualifications section covering both "What You Bring" (requirements) and maybe skills. But we also have Responsibilities from "What You’ll Do". So we can have:
- About the role: Company Description (maybe also brief role overview? Not given)
- Responsibilities: list from "What You’ll Do"
- Requirements/Qualifications: list from "What You Bring"
- Pay: base pay range plus equity etc.
- Benefits: health plans, 401(k) etc.
We should not repeat job title. No metadata like Job ID.
We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists.
Let's extract details.
Company Description paragraph:
"It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing people from busywork so they could focus on meaningful work. Today, ServiceNow is the AI control tower for business reinvention. Our ServiceNow AI platform brings together any AI, any data, and any workflow— helping 85% of the Fortune 500® work smarter, faster, and better. We're building an AI-native culture where technology and talent are unstoppable together. And we're just getting started. Join us to put AI to work for people."
That's the company description.
Job Description (the role) includes responsibilities: "As the Cybersecurity Technical Enablement Manager for Customer Team, you will play a critical role in driving the success of our Post-Sales and technical field teams by developing and executing strategic enablement initiatives that enhance time-to-value, customer adoption, retention, and account expansion. In this role, you will leverage your deep technical cybersecurity background to bridge the gap between complex product architecture and field execution. In this role, you’ll collaborate closely with leaders across Customer Success, Delivery Assurance, Global Support, Product, and other cross-functional teams to refine and scale enablement programs that drive measurable business impact. You will take ownership of global post-sales technology enablement, ensuring alignment with company objectives while continuously optimizing programs based on data, customer telemetry, and field insights. Additionally, you will spearhead the evolution of technical onboarding and adoption frameworks, ensuring consistent and compelling execution throughout the post-implementation customer journey. This is a highly hands-on role. You won’t just design enablement strategies—you’ll be rolling up your sleeves and executing them. Success in this role means being in the trenches with post-sales teams, leading by doing, and demonstrating a deep personal ownership of both strategy and execution. This role requires a strategic mindset, technical credibility, strong leadership, and a passion for customer excellence. The ideal candidate is proactive, highly adaptable, and thrives in a fast-paced environment where field feedback fuels continuous improvement."
That is a prose description of role and expectations. Could be part of Responsibilities or About the role. But we already have About the role as company description. Maybe we should put this under "About the role" as role overview, and company description maybe not needed? But we need to preserve company description; we could put it under "About the role" as well, but that would mix company and role. Could we have two sections: "About the role" (role overview) and maybe "About the company"? Not allowed headings. Could we put company description in a
without heading? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having paragraphs outside headings? It says output ONLY the HTML fragment. Likely they expect sections with headings. But we could include a
before first heading? Not sure. Safer to include company description under a heading like "About the role". Even though it's about company, it's still descriptive.
But we also have the role description paragraph that could also go under "About the role". That would duplicate heading. Better to split: maybe "About the role" includes role overview (the Job Description paragraph). And we could add another heading like "About the company"? Not allowed. Could we put company description under "Benefits"? No.
Maybe we can treat "Company Description" as part of "About the role" but also include the role description there. That would be mixing but still preserving all info. The instruction: "Prefer a few substantive sections over many thin ones." So having one "About the role" section containing both company description and role overview is okay.
Then Responsibilities: we have detailed list of duties under "What You’ll Do". That's a list of bullet points. We'll output as
- .
Qualifications/Requirements: we have "What You Bring" list. We'll output as
- .
Pay: we have base pay range plus equity etc. Also mention that sales positions generally offer OTE etc. We'll output as
maybe with details.
Benefits: health plans, 401(k) Plan with company match, ESPP, matching donations, flexible time away plan and family leave programs. Also mention flexible spending accounts. We'll output as
- .
We should not include boilerplate like Equal Opportunity Employer, Accommodations, Export Control Regulations, etc. Remove those.
Also remove "Additional Information Work Personas" etc.
Now craft HTML.
Structure:
About the role
Company description paragraph + role description paragraph? Might be too long but okay.
But we need to ensure we don't repeat content. Let's combine:
Company description: "It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing people from busywork so they could focus on meaningful work. Today, ServiceNow is the AI control tower for business reinvention. Our ServiceNow AI platform brings together any AI, any data, and any workflow— helping 85% of the Fortune 500® work smarter, faster, and better. We're building an AI-native culture where technology and talent are unstoppable together. And we're just getting started. Join us to put AI to work for people."
Role description: "As the Cybersecurity Technical Enablement Manager for Customer Team, you will play a critical role in driving the success of our Post-Sales and technical field teams by developing and executing strategic enablement initiatives that enhance time-to-value, customer adoption, retention, and account expansion. In this role, you will leverage your deep technical cybersecurity background to bridge the gap between complex product architecture and field execution. In this role, you’ll collaborate closely with leaders across Customer Success, Delivery Assurance, Global Support, Product, and other cross-functional teams to refine and scale enablement programs that drive measurable business impact. You will take ownership of global post-sales technology enablement, ensuring alignment with company objectives while continuously optimizing programs based on data, customer telemetry, and field insights. Additionally, you will spearhead the evolution of technical onboarding and adoption frameworks, ensuring consistent and compelling execution throughout the post-implementation customer journey. This is a highly hands-on role. You won’t just design enablement strategies—you’ll be rolling up your sleeves and executing them. Success in this role means being in the trenches with post-sales teams, leading by doing, and demonstrating a deep personal ownership of both strategy and execution. This role requires a strategic mindset, technical credibility, strong leadership, and a passion for customer excellence. The ideal candidate is proactive, highly adaptable, and thrives in a fast-paced environment where field feedback fuels continuous improvement."
We can combine into one
maybe two paragraphs. It's okay to have multiple
inside section? The instruction: Use
for prose. Could have multiple
. We'll do two
elements.
Then Responsibilities:
Responsibilities
- Design, scope, and deliver deep-dive technical enablement motions—including lab environments, advanced architectural workflows, integrations, and live technical demos—for technical customer-facing roles.
- Assist with the Armis Ignite onboarding program for roles under the Customer Success organization to ensure new hires hit major technical and operational learning milestones by their 30th day.
- Design and organize training content using tools like PowerPoint, Word, Excel, Articulate Rise, and Camtasia, covering Armis product architecture, technical methodologies, systems, and tools.
- Partner with Subject Matter Experts, leadership, and the enablement team to create technical agendas, assign speakers, run event logistics, survey attendees, build proof of knowledge components (e.g., live demo evaluations, exams), and present outcome readouts to leadership.
- Deliver skillful public speaking, training, and technical workshop facilitation, including stage presentations to audiences of up to 400 attendees.
- Build and run targeted enablement motions around product releases and time-sensitive technical initiatives based on evolving
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Include a section only when posting has real, specific content. Remove boilerplate etc. We need to parse the posting. Company Description: description about ServiceNow. Could be "About the role"? Actually "Company Description" is about the company, not role. Could be "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have: - Company Description: description of ServiceNow. Could be placed under "About the role"? Or maybe we can have a section "About the role" containing that description? Usually "About the role" is description of role, but we have "Job Description" which details responsibilities. The "Company Description" is about the company. Could we put it under "About the role"? Might be okay but not exactly. However we need to include substantive info; we can include a section "About the role" with the company description? Might be odd but acceptable. Alternatively we could omit that section if not matching headings. But we need to preserve all substantive info; we cannot drop company description. So we need to include it somewhere. Perhaps we can create a section "About the role" and put the company description there, even though it's about company. Or we could create a custom heading? Not allowed; only those headings. So we must fit into one of those. We have "Job Description" which contains responsibilities etc. That could go under "Responsibilities". Also there is "Qualifications" section with "What You’ll Do" and "What You Bring". That includes responsibilities and qualifications. Actually "What You’ll Do" is responsibilities/duties. "What You Bring" is qualifications/requirements. Also there is pay info: "For positions in this location, we offer a base pay of $126,800 - $221,900, plus equity (when applicable), variable/incentive compensation and benefits." Also mention benefits: health plans, 401(k) etc. So we have Pay and Benefits sections. Schedule? Not mentioned. So we should not create Schedule section. Skills? Not explicitly listed; maybe we can infer from qualifications but better not to create Skills unless explicit. The posting mentions "Tooling Proficiency", "Leadership & Cross-Functional Alignment". Those could be skills. But we need to decide if we create a Skills section. The instruction: prefer a few substantive sections over many thin ones. We could combine skills into Qualifications or Requirements. Probably better to have Qualifications section covering both "What You Bring" (requirements) and maybe skills. But we also have Responsibilities from "What You’ll Do". So we can have: - About the role: Company Description (maybe also brief role overview? Not given) - Responsibilities: list from "What You’ll Do" - Requirements/Qualifications: list from "What You Bring" - Pay: base pay range plus equity etc. - Benefits: health plans, 401(k) etc. We should not repeat job title. No metadata like Job ID. We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists.
Let's extract details.
Company Description paragraph:
"It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing people from busywork so they could focus on meaningful work. Today, ServiceNow is the AI control tower for business reinvention. Our ServiceNow AI platform brings together any AI, any data, and any workflow— helping 85% of the Fortune 500® work smarter, faster, and better. We're building an AI-native culture where technology and talent are unstoppable together. And we're just getting started. Join us to put AI to work for people."
That's the company description.
Job Description (the role) includes responsibilities: "As the Cybersecurity Technical Enablement Manager for Customer Team, you will play a critical role in driving the success of our Post-Sales and technical field teams by developing and executing strategic enablement initiatives that enhance time-to-value, customer adoption, retention, and account expansion. In this role, you will leverage your deep technical cybersecurity background to bridge the gap between complex product architecture and field execution. In this role, you’ll collaborate closely with leaders across Customer Success, Delivery Assurance, Global Support, Product, and other cross-functional teams to refine and scale enablement programs that drive measurable business impact. You will take ownership of global post-sales technology enablement, ensuring alignment with company objectives while continuously optimizing programs based on data, customer telemetry, and field insights. Additionally, you will spearhead the evolution of technical onboarding and adoption frameworks, ensuring consistent and compelling execution throughout the post-implementation customer journey. This is a highly hands-on role. You won’t just design enablement strategies—you’ll be rolling up your sleeves and executing them. Success in this role means being in the trenches with post-sales teams, leading by doing, and demonstrating a deep personal ownership of both strategy and execution. This role requires a strategic mindset, technical credibility, strong leadership, and a passion for customer excellence. The ideal candidate is proactive, highly adaptable, and thrives in a fast-paced environment where field feedback fuels continuous improvement."
That is a prose description of role and expectations. Could be part of Responsibilities or About the role. But we already have About the role as company description. Maybe we should put this under "About the role" as role overview, and company description maybe not needed? But we need to preserve company description; we could put it under "About the role" as well, but that would mix company and role. Could we have two sections: "About the role" (role overview) and maybe "About the company"? Not allowed headings. Could we put company description in a
without heading? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having paragraphs outside headings? It says output ONLY the HTML fragment. Likely they expect sections with headings. But we could include a
before first heading? Not sure. Safer to include company description under a heading like "About the role". Even though it's about company, it's still descriptive.
But we also have the role description paragraph that could also go under "About the role". That would duplicate heading. Better to split: maybe "About the role" includes role overview (the Job Description paragraph). And we could add another heading like "About the company"? Not allowed. Could we put company description under "Benefits"? No.
Maybe we can treat "Company Description" as part of "About the role" but also include the role description there. That would be mixing but still preserving all info. The instruction: "Prefer a few substantive sections over many thin ones." So having one "About the role" section containing both company description and role overview is okay.
Then Responsibilities: we have detailed list of duties under "What You’ll Do". That's a list of bullet points. We'll output as
- .
Qualifications/Requirements: we have "What You Bring" list. We'll output as
- .
Pay: we have base pay range plus equity etc. Also mention that sales positions generally offer OTE etc. We'll output as
maybe with details.
Benefits: health plans, 401(k) Plan with company match, ESPP, matching donations, flexible time away plan and family leave programs. Also mention flexible spending accounts. We'll output as
- .
We should not include boilerplate like Equal Opportunity Employer, Accommodations, Export Control Regulations, etc. Remove those.
Also remove "Additional Information Work Personas" etc.
Now craft HTML.
Structure:
About the role
Company description paragraph + role description paragraph? Might be too long but okay.
But we need to ensure we don't repeat content. Let's combine:
Company description: "It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing people from busywork so they could focus on meaningful work. Today, ServiceNow is the AI control tower for business reinvention. Our ServiceNow AI platform brings together any AI, any data, and any workflow— helping 85% of the Fortune 500® work smarter, faster, and better. We're building an AI-native culture where technology and talent are unstoppable together. And we're just getting started. Join us to put AI to work for people."
Role description: "As the Cybersecurity Technical Enablement Manager for Customer Team, you will play a critical role in driving the success of our Post-Sales and technical field teams by developing and executing strategic enablement initiatives that enhance time-to-value, customer adoption, retention, and account expansion. In this role, you will leverage your deep technical cybersecurity background to bridge the gap between complex product architecture and field execution. In this role, you’ll collaborate closely with leaders across Customer Success, Delivery Assurance, Global Support, Product, and other cross-functional teams to refine and scale enablement programs that drive measurable business impact. You will take ownership of global post-sales technology enablement, ensuring alignment with company objectives while continuously optimizing programs based on data, customer telemetry, and field insights. Additionally, you will spearhead the evolution of technical onboarding and adoption frameworks, ensuring consistent and compelling execution throughout the post-implementation customer journey. This is a highly hands-on role. You won’t just design enablement strategies—you’ll be rolling up your sleeves and executing them. Success in this role means being in the trenches with post-sales teams, leading by doing, and demonstrating a deep personal ownership of both strategy and execution. This role requires a strategic mindset, technical credibility, strong leadership, and a passion for customer excellence. The ideal candidate is proactive, highly adaptable, and thrives in a fast-paced environment where field feedback fuels continuous improvement."
We can combine into one
maybe two paragraphs. It's okay to have multiple
inside section? The instruction: Use
for prose. Could have multiple
. We'll do two
elements.
Then Responsibilities:
Responsibilities
- Design, scope, and deliver deep-dive technical enablement motions—including lab environments, advanced architectural workflows, integrations, and live technical demos—for technical customer-facing roles.
- Assist with the Armis Ignite onboarding program for roles under the Customer Success organization to ensure new hires hit major technical and operational learning milestones by their 30th day.
- Design and organize training content using tools like PowerPoint, Word, Excel, Articulate Rise, and Camtasia, covering Armis product architecture, technical methodologies, systems, and tools.
- Partner with Subject Matter Experts, leadership, and the enablement team to create technical agendas, assign speakers, run event logistics, survey attendees, build proof of knowledge components (e.g., live demo evaluations, exams), and present outcome readouts to leadership.
- Deliver skillful public speaking, training, and technical workshop facilitation, including stage presentations to audiences of up to 400 attendees.
- Build and run targeted enablement motions around product releases and time-sensitive technical initiatives based on evolving
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists. Let's extract details. Company Description paragraph: "It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing people from busywork so they could focus on meaningful work. Today, ServiceNow is the AI control tower for business reinvention. Our ServiceNow AI platform brings together any AI, any data, and any workflow— helping 85% of the Fortune 500® work smarter, faster, and better. We're building an AI-native culture where technology and talent are unstoppable together. And we're just getting started. Join us to put AI to work for people." That's the company description. Job Description (the role) includes responsibilities: "As the Cybersecurity Technical Enablement Manager for Customer Team, you will play a critical role in driving the success of our Post-Sales and technical field teams by developing and executing strategic enablement initiatives that enhance time-to-value, customer adoption, retention, and account expansion. In this role, you will leverage your deep technical cybersecurity background to bridge the gap between complex product architecture and field execution. In this role, you’ll collaborate closely with leaders across Customer Success, Delivery Assurance, Global Support, Product, and other cross-functional teams to refine and scale enablement programs that drive measurable business impact. You will take ownership of global post-sales technology enablement, ensuring alignment with company objectives while continuously optimizing programs based on data, customer telemetry, and field insights. Additionally, you will spearhead the evolution of technical onboarding and adoption frameworks, ensuring consistent and compelling execution throughout the post-implementation customer journey. This is a highly hands-on role. You won’t just design enablement strategies—you’ll be rolling up your sleeves and executing them. Success in this role means being in the trenches with post-sales teams, leading by doing, and demonstrating a deep personal ownership of both strategy and execution. This role requires a strategic mindset, technical credibility, strong leadership, and a passion for customer excellence. The ideal candidate is proactive, highly adaptable, and thrives in a fast-paced environment where field feedback fuels continuous improvement." That is a prose description of role and expectations. Could be part of Responsibilities or About the role. But we already have About the role as company description. Maybe we should put this under "About the role" as role overview, and company description maybe not needed? But we need to preserve company description; we could put it under "About the role" as well, but that would mix company and role. Could we have two sections: "About the role" (role overview) and maybe "About the company"? Not allowed headings. Could we put company description in a
without heading? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having paragraphs outside headings? It says output ONLY the HTML fragment. Likely they expect sections with headings. But we could include a
before first heading? Not sure. Safer to include company description under a heading like "About the role". Even though it's about company, it's still descriptive. But we also have the role description paragraph that could also go under "About the role". That would duplicate heading. Better to split: maybe "About the role" includes role overview (the Job Description paragraph). And we could add another heading like "About the company"? Not allowed. Could we put company description under "Benefits"? No. Maybe we can treat "Company Description" as part of "About the role" but also include the role description there. That would be mixing but still preserving all info. The instruction: "Prefer a few substantive sections over many thin ones." So having one "About the role" section containing both company description and role overview is okay. Then Responsibilities: we have detailed list of duties under "What You’ll Do". That's a list of bullet points. We'll output as
- .
Qualifications/Requirements: we have "What You Bring" list. We'll output as
- .
Pay: we have base pay range plus equity etc. Also mention that sales positions generally offer OTE etc. We'll output as
maybe with details. Benefits: health plans, 401(k) Plan with company match, ESPP, matching donations, flexible time away plan and family leave programs. Also mention flexible spending accounts. We'll output as
- .
We should not include boilerplate like Equal Opportunity Employer, Accommodations, Export Control Regulations, etc. Remove those.
Also remove "Additional Information Work Personas" etc.
Now craft HTML.
Structure:
About the role
Company description paragraph + role description paragraph? Might be too long but okay. But we need to ensure we don't repeat content. Let's combine: Company description: "It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing people from busywork so they could focus on meaningful work. Today, ServiceNow is the AI control tower for business reinvention. Our ServiceNow AI platform brings together any AI, any data, and any workflow— helping 85% of the Fortune 500® work smarter, faster, and better. We're building an AI-native culture where technology and talent are unstoppable together. And we're just getting started. Join us to put AI to work for people." Role description: "As the Cybersecurity Technical Enablement Manager for Customer Team, you will play a critical role in driving the success of our Post-Sales and technical field teams by developing and executing strategic enablement initiatives that enhance time-to-value, customer adoption, retention, and account expansion. In this role, you will leverage your deep technical cybersecurity background to bridge the gap between complex product architecture and field execution. In this role, you’ll collaborate closely with leaders across Customer Success, Delivery Assurance, Global Support, Product, and other cross-functional teams to refine and scale enablement programs that drive measurable business impact. You will take ownership of global post-sales technology enablement, ensuring alignment with company objectives while continuously optimizing programs based on data, customer telemetry, and field insights. Additionally, you will spearhead the evolution of technical onboarding and adoption frameworks, ensuring consistent and compelling execution throughout the post-implementation customer journey. This is a highly hands-on role. You won’t just design enablement strategies—you’ll be rolling up your sleeves and executing them. Success in this role means being in the trenches with post-sales teams, leading by doing, and demonstrating a deep personal ownership of both strategy and execution. This role requires a strategic mindset, technical credibility, strong leadership, and a passion for customer excellence. The ideal candidate is proactive, highly adaptable, and thrives in a fast-paced environment where field feedback fuels continuous improvement." We can combine into one
maybe two paragraphs. It's okay to have multiple
inside section? The instruction: Use
for prose. Could have multiple
. We'll do two
elements. Then Responsibilities:
Responsibilities
- Design, scope, and deliver deep-dive technical enablement motions—including lab environments, advanced architectural workflows, integrations, and live technical demos—for technical customer-facing roles.
- Assist with the Armis Ignite onboarding program for roles under the Customer Success organization to ensure new hires hit major technical and operational learning milestones by their 30th day.
- Design and organize training content using tools like PowerPoint, Word, Excel, Articulate Rise, and Camtasia, covering Armis product architecture, technical methodologies, systems, and tools.
- Partner with Subject Matter Experts, leadership, and the enablement team to create technical agendas, assign speakers, run event logistics, survey attendees, build proof of knowledge components (e.g., live demo evaluations, exams), and present outcome readouts to leadership.
- Deliver skillful public speaking, training, and technical workshop facilitation, including stage presentations to audiences of up to 400 attendees.
- Build and run targeted enablement motions around product releases and time-sensitive technical initiatives based on evolving
- .
We should not include boilerplate like Equal Opportunity Employer, Accommodations, Export Control Regulations, etc. Remove those.
Also remove "Additional Information Work Personas" etc.
Now craft HTML.
Structure:
- .
Pay: we have base pay range plus equity etc. Also mention that sales positions generally offer OTE etc. We'll output as