Customer Success Engineer
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. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them.
We need to extract content from the posting.
Let's parse the posting:
- "Who We Are" section: description of mission, etc. This is about the company. Could be "About the role"? Actually "Who We Are" is about company. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. "Who We Are" could be considered "About the role"? Not exactly. But we can treat "About the role" as description of the role and company? Usually "About the role" is description of the position. The posting includes "Who You Are", "What You’ll Do", "Role And Responsibilities", "Technical Proficiency", "Individual Skills", "Bonus Skills", "Who You'll Be Working With", "Where You'll Work", "When You'll Work", "What You'll Receive", timeline sections.
We need to decide which headings to include based on actual content.
We have:
- About the role: Could combine "Who We Are" and "Who You Are"? Actually "Who You Are" describes desired candidate. That could be "Requirements" or "Qualifications". "What You’ll Do" is responsibilities. "Role And Responsibilities" also responsibilities. "Technical Proficiency" and "Individual Skills" and "Bonus Skills" are skills/qualifications. "Who You'll Be Working With" maybe not needed. "Where You'll Work" could be Schedule? Actually location. Not Pay/Schedule/Benefits unless stated. "When You'll Work" is schedule info (daytime hours US, synchronous meetings). That's schedule. "What You'll Receive" includes benefits and pay info (travel stipend, productivity stipend, health insurance, equity). Also mentions salary determination but not specific numbers. So we can include Benefits section (travel stipend, productivity stipend, health insurance, equity). Pay section? The posting says "To determine your salary, we use a number of market and data-driven salary sources. We review all salaries every six months to ensure we stay in line with the market." That's not a specific number, but it's about pay. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay (salary determination process). That's enough to include a Pay section? It says "We review all salaries every six months to ensure we stay in line with the market." That's not a specific number but it's about pay. Likely we can include Pay section with that description. However we must avoid filler like "commensurate with experience". This is not filler; it's a description of process. So we can include Pay.
Schedule: "When You'll Work Roboflow primarily operates during the daytime hours in the US and there are some synchronous meetings you’ll be expected to attend each week." That's specific enough for Schedule.
Benefits: "What You'll Receive" includes travel stipend, productivity stipend, health insurance, equity. Also mentions "Within one week, you will..." etc. That's more about onboarding timeline, not benefits. But we can treat the stipends and health insurance and equity as benefits.
We also have timeline sections: "Within one week, you will…", "Within one month, you will…", "Within six months, you will…". Those could be part of Responsibilities or maybe a separate section like "Onboarding & Milestones". But we only have allowed headings list. Could we put them under Responsibilities? Probably better to include them under Responsibilities as they describe what you'll do early on. However they are more like expectations/milestones. Could also be under "Qualifications"? Not really. We'll incorporate them into Responsibilities as bullet points.
Now we need to produce HTML with headings
for each section we include.
We must use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc.
We need to avoid duplication.
Let's extract substantive content sections:
**About the role / Company description**: "Who We Are Our mission is to make the world programmable. Sight is one of the key ways we understand the world, and soon this will be true for the software we use, too. We’re building the tools, community, and resources needed to make the world programmable with artificial intelligence. Roboflow simplifies building and using computer vision models. Today, over 1M+ developers, including those from half the Fortune 100, use Roboflow’s machine learning open source and hosted tools. That includes counting cells to accelerate cancer research, improving construction site safety, digitizing floor plans, preserving coral reef populations, guiding drone flight, and much more. Roboflow is supported by great customers and investors, having raised over 63 million from Y Combinator, Google Ventures, Craft Ventures, Sam Altman, Lachy Groom, amongst other leading software investors. Roboflowers are passionate builders who value ownership, accountability, and a bias toward action. We're curious, hands-on with new tech, and prefer showing our work over talking about it. Many of us have a founder mindset and thrive in our high-autonomy environment."
That's company overview. Could be placed under "About the role". We'll output as
.
**Who You Are (desired candidate)**: "You are technically curious, customer-focused, and get satisfaction from helping people become capable and confident users of complex technology. You may come from Customer Success, technical enablement, Developer Relations, Support, Solutions Engineering, or another customer-facing technical role. You enjoy understanding why customers struggle with a product and turning those insights into better ways of teaching thousands of customers — not simply solving the same problem repeatedly. You are comfortable teaching technical concepts live, creating clear educational content, and guiding customers through unfamiliar workflows. You know when to demonstrate, when to advise, and importantly when to let the customer drive the keyboard. You look for patterns. If several customers ask the same question, your instinct is not simply to answer it again; it is to create the guide, video, workshop, workflow, or program that means the next customer can answer it themselves. Empathetic to customer needs and the importance of communicating in remote relationships, you can provide clear and prescriptive guidance while maintaining the boundaries required for a scalable self-service customer experience. Many Roboflowers have used our tools before joining. One of the best ways to stand out amongst other applicants is to write about something you have built with Roboflow or contribute to one of our open source projects."
That's qualifications/requirements. We'll put under "Requirements" or "Qualifications". The instruction includes both Requirements and Qualifications headings. We need to decide which to use. Could combine? Probably better to have "Qualifications" for desired candidate traits and experience, and "Skills" for technical skills. But we also have separate "Technical Proficiency", "Individual Skills", "Bonus Skills". Those are more specific skill categories. So we can treat "Who You Are" as "Qualifications". Then "Technical Proficiency", "Individual Skills", "Bonus Skills" as "Skills". Or we could have "Requirements" for mandatory qualifications and "Skills" for desired skills. Let's map:
- Qualifications: "Who You Are" (desired background, mindset).
- Skills: combine Technical Proficiency, Individual Skills, Bonus Skills into a list.
But we also have "Responsibilities": "What You’ll Do" and "Role And Responsibilities". We'll combine.
Now "What You’ll Do": description of scalable enablement, targeted 1:1 enablement, objective, teaching customers datasets, annotations, model training/evaluation, identifying recurring friction, turning into programs/assets.
Then "Role And Responsibilities": a long list of bullet-like sentences (but not formatted as list). We need to turn them into
- . The text includes many responsibilities separated by line breaks? Actually it's a paragraph with many sentences separated by spaces. We'll need to split into list items.
Let's extract each responsibility sentence:
"Develop, deliver, and continually improve technical enablement programs for Roboflow's self-serve customer base, covering platform onboarding, annotation strategy and quality, dataset management, model training and evaluation, workflows and deployments and workspace administration"
"Host bi-weekly webinars, technical workshops, office hours, and other live educational sessions"
"Develop learning journeys that guide customers towards increasingly sophisticated use of Roboflow technology"
"Deliver Roboflow's structured 1:1 Targeted Enablement Option Pack for qualifying customers"
"Create reusable technical enablement assets including documentation, videos, walkthroughs, recordings, and reference materials"
"Identify recurring customer questions and turn them into scalable educational programs or assets"
"Monitor customer activation and engagement signals to identify users and cohorts who may benefit from specific enablement programs"
"Measure participation and effectiveness of enablement programs for continual improvement"
"Collaborate with Product to identify and close recurring knowledge and usability gaps"
"Stay current with the latest Roboflow product features, releases, workflows, and recommended best practices"
That's a list.
Now "Technical Proficiency": list of bullet-like sentences:
"Working knowledge of computer vision and machine learning, including datasets, annotation, model training, evaluation, and inference"
"Comfortable using Python and working with APIs, notebooks, and common developer tooling"
"Ability to become highly proficient across the Roboflow platform and demonstrate its workflows confidently to customers"
"Understanding of model evaluation concepts including precision, recall, confidence thresholds, confusion matrices, and common causes of poor model performance"
"Understanding of dataset quality, annotation strategy, dataset versioning, and approaches for identifying difficult or underrepresented examples"
"Ability to translate technical concepts into clear, practical guidance for users with varying levels of ML experience"
Now "Individual Skills": list:
"Technical Teaching: Able to explain unfamiliar technical concepts clearly and adapt the explanation to the customer's level of experience"
"Pattern Recognition: Recognize recurring questions and friction across customer interactions and identify opportunities to solve them systematically"
"Program Delivery: Methodical planning and delivery of structured 1:1 sessions, webinars, workshops, and other customer-facing technical programs"
"Content Creation: Able to create concise, technically accurate educational material across written, recorded, and live formats"
"Workload Management: Manage multiple customers progressing through structured enablement while balancing program delivery and reusable content creation"
"Customer Communication: Communicate clearly and professionally before, during, and after enablement engagements, setting expectations around preparation, outcomes, and next steps"
Now "Bonus Skills": list:
"Experience using the Roboflow platform or contributing to the Roboflow ecosystem"
"Previous experience in Customer Success, technical enablement, Developer Relations, technical education, Solutions Engineering, or technical Support"
"Experience creating technical educational content such as tutorials, videos, workshops, documentation, or developer courses"
"Experience delivering webinars, workshops, technical demonstrations, or customer training"
"Experience working with product-led growth or self-service SaaS customers"
"Experience using product telemetry or customer activation data to inform customer engagement programs"
Now "Who You'll Be Working With": description of team. Could be omitted as not required heading. Not needed.
"Where You'll Work": description of hubs, remote, travel stipend, relocation bonus.
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. We need to extract content from the posting. Let's parse the posting: - "Who We Are" section: description of mission, etc. This is about the company. Could be "About the role"? Actually "Who We Are" is about company. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. "Who We Are" could be considered "About the role"? Not exactly. But we can treat "About the role" as description of the role and company? Usually "About the role" is description of the position. The posting includes "Who You Are", "What You’ll Do", "Role And Responsibilities", "Technical Proficiency", "Individual Skills", "Bonus Skills", "Who You'll Be Working With", "Where You'll Work", "When You'll Work", "What You'll Receive", timeline sections. We need to decide which headings to include based on actual content. We have: - About the role: Could combine "Who We Are" and "Who You Are"? Actually "Who You Are" describes desired candidate. That could be "Requirements" or "Qualifications". "What You’ll Do" is responsibilities. "Role And Responsibilities" also responsibilities. "Technical Proficiency" and "Individual Skills" and "Bonus Skills" are skills/qualifications. "Who You'll Be Working With" maybe not needed. "Where You'll Work" could be Schedule? Actually location. Not Pay/Schedule/Benefits unless stated. "When You'll Work" is schedule info (daytime hours US, synchronous meetings). That's schedule. "What You'll Receive" includes benefits and pay info (travel stipend, productivity stipend, health insurance, equity). Also mentions salary determination but not specific numbers. So we can include Benefits section (travel stipend, productivity stipend, health insurance, equity). Pay section? The posting says "To determine your salary, we use a number of market and data-driven salary sources. We review all salaries every six months to ensure we stay in line with the market." That's not a specific number, but it's about pay. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay (salary determination process). That's enough to include a Pay section? It says "We review all salaries every six months to ensure we stay in line with the market." That's not a specific number but it's about pay. Likely we can include Pay section with that description. However we must avoid filler like "commensurate with experience". This is not filler; it's a description of process. So we can include Pay. Schedule: "When You'll Work Roboflow primarily operates during the daytime hours in the US and there are some synchronous meetings you’ll be expected to attend each week." That's specific enough for Schedule. Benefits: "What You'll Receive" includes travel stipend, productivity stipend, health insurance, equity. Also mentions "Within one week, you will..." etc. That's more about onboarding timeline, not benefits. But we can treat the stipends and health insurance and equity as benefits. We also have timeline sections: "Within one week, you will…", "Within one month, you will…", "Within six months, you will…". Those could be part of Responsibilities or maybe a separate section like "Onboarding & Milestones". But we only have allowed headings list. Could we put them under Responsibilities? Probably better to include them under Responsibilities as they describe what you'll do early on. However they are more like expectations/milestones. Could also be under "Qualifications"? Not really. We'll incorporate them into Responsibilities as bullet points. Now we need to produce HTML with headings
for each section we include.
We must use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc.
We need to avoid duplication.
Let's extract substantive content sections:
**About the role / Company description**: "Who We Are Our mission is to make the world programmable. Sight is one of the key ways we understand the world, and soon this will be true for the software we use, too. We’re building the tools, community, and resources needed to make the world programmable with artificial intelligence. Roboflow simplifies building and using computer vision models. Today, over 1M+ developers, including those from half the Fortune 100, use Roboflow’s machine learning open source and hosted tools. That includes counting cells to accelerate cancer research, improving construction site safety, digitizing floor plans, preserving coral reef populations, guiding drone flight, and much more. Roboflow is supported by great customers and investors, having raised over 63 million from Y Combinator, Google Ventures, Craft Ventures, Sam Altman, Lachy Groom, amongst other leading software investors. Roboflowers are passionate builders who value ownership, accountability, and a bias toward action. We're curious, hands-on with new tech, and prefer showing our work over talking about it. Many of us have a founder mindset and thrive in our high-autonomy environment."
That's company overview. Could be placed under "About the role". We'll output as
.
**Who You Are (desired candidate)**: "You are technically curious, customer-focused, and get satisfaction from helping people become capable and confident users of complex technology. You may come from Customer Success, technical enablement, Developer Relations, Support, Solutions Engineering, or another customer-facing technical role. You enjoy understanding why customers struggle with a product and turning those insights into better ways of teaching thousands of customers — not simply solving the same problem repeatedly. You are comfortable teaching technical concepts live, creating clear educational content, and guiding customers through unfamiliar workflows. You know when to demonstrate, when to advise, and importantly when to let the customer drive the keyboard. You look for patterns. If several customers ask the same question, your instinct is not simply to answer it again; it is to create the guide, video, workshop, workflow, or program that means the next customer can answer it themselves. Empathetic to customer needs and the importance of communicating in remote relationships, you can provide clear and prescriptive guidance while maintaining the boundaries required for a scalable self-service customer experience. Many Roboflowers have used our tools before joining. One of the best ways to stand out amongst other applicants is to write about something you have built with Roboflow or contribute to one of our open source projects."
That's qualifications/requirements. We'll put under "Requirements" or "Qualifications". The instruction includes both Requirements and Qualifications headings. We need to decide which to use. Could combine? Probably better to have "Qualifications" for desired candidate traits and experience, and "Skills" for technical skills. But we also have separate "Technical Proficiency", "Individual Skills", "Bonus Skills". Those are more specific skill categories. So we can treat "Who You Are" as "Qualifications". Then "Technical Proficiency", "Individual Skills", "Bonus Skills" as "Skills". Or we could have "Requirements" for mandatory qualifications and "Skills" for desired skills. Let's map:
- Qualifications: "Who You Are" (desired background, mindset).
- Skills: combine Technical Proficiency, Individual Skills, Bonus Skills into a list.
But we also have "Responsibilities": "What You’ll Do" and "Role And Responsibilities". We'll combine.
Now "What You’ll Do": description of scalable enablement, targeted 1:1 enablement, objective, teaching customers datasets, annotations, model training/evaluation, identifying recurring friction, turning into programs/assets.
Then "Role And Responsibilities": a long list of bullet-like sentences (but not formatted as list). We need to turn them into
- . The text includes many responsibilities separated by line breaks? Actually it's a paragraph with many sentences separated by spaces. We'll need to split into list items.
Let's extract each responsibility sentence:
"Develop, deliver, and continually improve technical enablement programs for Roboflow's self-serve customer base, covering platform onboarding, annotation strategy and quality, dataset management, model training and evaluation, workflows and deployments and workspace administration"
"Host bi-weekly webinars, technical workshops, office hours, and other live educational sessions"
"Develop learning journeys that guide customers towards increasingly sophisticated use of Roboflow technology"
"Deliver Roboflow's structured 1:1 Targeted Enablement Option Pack for qualifying customers"
"Create reusable technical enablement assets including documentation, videos, walkthroughs, recordings, and reference materials"
"Identify recurring customer questions and turn them into scalable educational programs or assets"
"Monitor customer activation and engagement signals to identify users and cohorts who may benefit from specific enablement programs"
"Measure participation and effectiveness of enablement programs for continual improvement"
"Collaborate with Product to identify and close recurring knowledge and usability gaps"
"Stay current with the latest Roboflow product features, releases, workflows, and recommended best practices"
That's a list.
Now "Technical Proficiency": list of bullet-like sentences:
"Working knowledge of computer vision and machine learning, including datasets, annotation, model training, evaluation, and inference"
"Comfortable using Python and working with APIs, notebooks, and common developer tooling"
"Ability to become highly proficient across the Roboflow platform and demonstrate its workflows confidently to customers"
"Understanding of model evaluation concepts including precision, recall, confidence thresholds, confusion matrices, and common causes of poor model performance"
"Understanding of dataset quality, annotation strategy, dataset versioning, and approaches for identifying difficult or underrepresented examples"
"Ability to translate technical concepts into clear, practical guidance for users with varying levels of ML experience"
Now "Individual Skills": list:
"Technical Teaching: Able to explain unfamiliar technical concepts clearly and adapt the explanation to the customer's level of experience"
"Pattern Recognition: Recognize recurring questions and friction across customer interactions and identify opportunities to solve them systematically"
"Program Delivery: Methodical planning and delivery of structured 1:1 sessions, webinars, workshops, and other customer-facing technical programs"
"Content Creation: Able to create concise, technically accurate educational material across written, recorded, and live formats"
"Workload Management: Manage multiple customers progressing through structured enablement while balancing program delivery and reusable content creation"
"Customer Communication: Communicate clearly and professionally before, during, and after enablement engagements, setting expectations around preparation, outcomes, and next steps"
Now "Bonus Skills": list:
"Experience using the Roboflow platform or contributing to the Roboflow ecosystem"
"Previous experience in Customer Success, technical enablement, Developer Relations, technical education, Solutions Engineering, or technical Support"
"Experience creating technical educational content such as tutorials, videos, workshops, documentation, or developer courses"
"Experience delivering webinars, workshops, technical demonstrations, or customer training"
"Experience working with product-led growth or self-service SaaS customers"
"Experience using product telemetry or customer activation data to inform customer engagement programs"
Now "Who You'll Be Working With": description of team. Could be omitted as not required heading. Not needed.
"Where You'll Work": description of hubs, remote, travel stipend, relocation bonus.
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to avoid duplication. Let's extract substantive content sections: **About the role / Company description**: "Who We Are Our mission is to make the world programmable. Sight is one of the key ways we understand the world, and soon this will be true for the software we use, too. We’re building the tools, community, and resources needed to make the world programmable with artificial intelligence. Roboflow simplifies building and using computer vision models. Today, over 1M+ developers, including those from half the Fortune 100, use Roboflow’s machine learning open source and hosted tools. That includes counting cells to accelerate cancer research, improving construction site safety, digitizing floor plans, preserving coral reef populations, guiding drone flight, and much more. Roboflow is supported by great customers and investors, having raised over 63 million from Y Combinator, Google Ventures, Craft Ventures, Sam Altman, Lachy Groom, amongst other leading software investors. Roboflowers are passionate builders who value ownership, accountability, and a bias toward action. We're curious, hands-on with new tech, and prefer showing our work over talking about it. Many of us have a founder mindset and thrive in our high-autonomy environment." That's company overview. Could be placed under "About the role". We'll output as
. **Who You Are (desired candidate)**: "You are technically curious, customer-focused, and get satisfaction from helping people become capable and confident users of complex technology. You may come from Customer Success, technical enablement, Developer Relations, Support, Solutions Engineering, or another customer-facing technical role. You enjoy understanding why customers struggle with a product and turning those insights into better ways of teaching thousands of customers — not simply solving the same problem repeatedly. You are comfortable teaching technical concepts live, creating clear educational content, and guiding customers through unfamiliar workflows. You know when to demonstrate, when to advise, and importantly when to let the customer drive the keyboard. You look for patterns. If several customers ask the same question, your instinct is not simply to answer it again; it is to create the guide, video, workshop, workflow, or program that means the next customer can answer it themselves. Empathetic to customer needs and the importance of communicating in remote relationships, you can provide clear and prescriptive guidance while maintaining the boundaries required for a scalable self-service customer experience. Many Roboflowers have used our tools before joining. One of the best ways to stand out amongst other applicants is to write about something you have built with Roboflow or contribute to one of our open source projects." That's qualifications/requirements. We'll put under "Requirements" or "Qualifications". The instruction includes both Requirements and Qualifications headings. We need to decide which to use. Could combine? Probably better to have "Qualifications" for desired candidate traits and experience, and "Skills" for technical skills. But we also have separate "Technical Proficiency", "Individual Skills", "Bonus Skills". Those are more specific skill categories. So we can treat "Who You Are" as "Qualifications". Then "Technical Proficiency", "Individual Skills", "Bonus Skills" as "Skills". Or we could have "Requirements" for mandatory qualifications and "Skills" for desired skills. Let's map: - Qualifications: "Who You Are" (desired background, mindset). - Skills: combine Technical Proficiency, Individual Skills, Bonus Skills into a list. But we also have "Responsibilities": "What You’ll Do" and "Role And Responsibilities". We'll combine. Now "What You’ll Do": description of scalable enablement, targeted 1:1 enablement, objective, teaching customers datasets, annotations, model training/evaluation, identifying recurring friction, turning into programs/assets. Then "Role And Responsibilities": a long list of bullet-like sentences (but not formatted as list). We need to turn them into
- . The text includes many responsibilities separated by line breaks? Actually it's a paragraph with many sentences separated by spaces. We'll need to split into list items. Let's extract each responsibility sentence: "Develop, deliver, and continually improve technical enablement programs for Roboflow's self-serve customer base, covering platform onboarding, annotation strategy and quality, dataset management, model training and evaluation, workflows and deployments and workspace administration" "Host bi-weekly webinars, technical workshops, office hours, and other live educational sessions" "Develop learning journeys that guide customers towards increasingly sophisticated use of Roboflow technology" "Deliver Roboflow's structured 1:1 Targeted Enablement Option Pack for qualifying customers" "Create reusable technical enablement assets including documentation, videos, walkthroughs, recordings, and reference materials" "Identify recurring customer questions and turn them into scalable educational programs or assets" "Monitor customer activation and engagement signals to identify users and cohorts who may benefit from specific enablement programs" "Measure participation and effectiveness of enablement programs for continual improvement" "Collaborate with Product to identify and close recurring knowledge and usability gaps" "Stay current with the latest Roboflow product features, releases, workflows, and recommended best practices" That's a list. Now "Technical Proficiency": list of bullet-like sentences: "Working knowledge of computer vision and machine learning, including datasets, annotation, model training, evaluation, and inference" "Comfortable using Python and working with APIs, notebooks, and common developer tooling" "Ability to become highly proficient across the Roboflow platform and demonstrate its workflows confidently to customers" "Understanding of model evaluation concepts including precision, recall, confidence thresholds, confusion matrices, and common causes of poor model performance" "Understanding of dataset quality, annotation strategy, dataset versioning, and approaches for identifying difficult or underrepresented examples" "Ability to translate technical concepts into clear, practical guidance for users with varying levels of ML experience" Now "Individual Skills": list: "Technical Teaching: Able to explain unfamiliar technical concepts clearly and adapt the explanation to the customer's level of experience" "Pattern Recognition: Recognize recurring questions and friction across customer interactions and identify opportunities to solve them systematically" "Program Delivery: Methodical planning and delivery of structured 1:1 sessions, webinars, workshops, and other customer-facing technical programs" "Content Creation: Able to create concise, technically accurate educational material across written, recorded, and live formats" "Workload Management: Manage multiple customers progressing through structured enablement while balancing program delivery and reusable content creation" "Customer Communication: Communicate clearly and professionally before, during, and after enablement engagements, setting expectations around preparation, outcomes, and next steps" Now "Bonus Skills": list: "Experience using the Roboflow platform or contributing to the Roboflow ecosystem" "Previous experience in Customer Success, technical enablement, Developer Relations, technical education, Solutions Engineering, or technical Support" "Experience creating technical educational content such as tutorials, videos, workshops, documentation, or developer courses" "Experience delivering webinars, workshops, technical demonstrations, or customer training" "Experience working with product-led growth or self-service SaaS customers" "Experience using product telemetry or customer activation data to inform customer engagement programs" Now "Who You'll Be Working With": description of team. Could be omitted as not required heading. Not needed. "Where You'll Work": description of hubs, remote, travel stipend, relocation bonus.