Technical Enablement Engineer

We need to output HTML fragment with sections only if real content. Remove boilerplate: application window line, Meet the Team, Your Impact, Minimum Qualifications, Preferred Qualifications, Why Cisco?, Message to applicants... We need to keep substantive info: team description, impact description, minimum qualifications list, preferred qualifications list, why Cisco description, salary range and benefits info, schedule? There's mention of paid holidays etc. That's benefits and schedule info. We should create sections: About the role? Actually we have "Meet the Team" and "Your Impact". Could combine into About the role? But we must use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. We have no explicit responsibilities list; we have impact description which could be responsibilities. Could put under Responsibilities. Minimum Qualifications list -> Requirements or Qualifications. Use Requirements for minimum qualifications. Preferred Qualifications -> Skills or Qualifications? Could use Skills. Why Cisco? could be About the role or maybe a separate section like About Cisco? Not in list. Could omit or put under About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. We can include About the role (team description + impact + why Cisco?). Responsibilities maybe from impact. Requirements from minimum qualifications. Qualifications maybe from preferred? But we already have Requirements and Qualifications separate. Could treat Requirements as minimum qualifications, Qualifications as preferred qualifications. Skills maybe from preferred? But we have limited headings. We need to avoid empty sections. So we need to decide which sections have content. We have: - About the role: could include "Meet the Team" and "Your Impact" and "Why Cisco?" maybe combined. - Responsibilities: maybe the impact description (advancing skills, delivering training). Could be responsibilities. - Requirements: minimum qualifications list. - Qualifications: preferred qualifications list. - Skills: maybe we could extract from preferred qualifications like ability to explain complex technical concepts, presentation skills, etc. But we already have Qualifications for preferred; maybe Skills for specific abilities. - Benefits: benefits description (medical, dental, vision, 401k, parental leave, disability, life insurance, RSU, paid time off details, volunteer days, bonuses). Also mention of paid holidays etc. - Pay: salary range info (starting salary range $98,600-$125,000, plus location-specific ranges, plus incentive details). Also mention of incentive compensation. - Schedule: maybe mention of vacation accrual etc? That's more benefits. Could treat schedule as work schedule? Not given. Could omit Schedule if no specific schedule content. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay and Benefits content. Schedule not explicitly given; we have vacation accrual details but that's more benefits. Could still put under Benefits. So we omit Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to ensure we don't repeat job title heading. Now extract content. About the role: combine Meet the Team paragraph, Your Impact paragraph, Why Cisco? paragraph. Keep all substantive info. Responsibilities: maybe from Your Impact: "At Cisco, we are dedicated to advancing the skills of our technical sales professionals through impactful training programs. Our global Learning & Development team focuses on delivering comprehensive training across our networking, data center infrastructure, collaboration, security, and observability products. By combining technical expertise with strong facilitation skills, we create engaging learning experiences that accelerate professional development and drive success in technical sales." That's responsibilities. Requirements: Minimum Qualifications list (bullet points). Need to preserve each line. List: - 5+ years of experience in technical sales or sales engineering roles. - Minimum 2 years of experience in technical training or facilitation. - 3+ years of experience with enterprise technology solutions across multiple domains, including automation and DevOps. - Current technical certifications in relevant technology areas - 3+ years hands-on experience with implementation and troubleshooting. - 3+ years of experience in one or more areas such as networking infrastructure and SDN, data center technologies and cloud infrastructure, security solutions and zero trust architectures, collaboration platforms and solutions, observability/monitoring tools, and application development/DevOps skills and practices. - 3+ years working in SE role and / or trained SEs. Ideally experienced in Cisco or competitor Data Center technologies. We should keep as

• . Qualifications: Preferred Qualifications list. List: - Ability to explain complex technical concepts clearly. - Experience with virtual training platforms and tools. - Strong presentation and public speaking skills. - Ability to lead group dynamics and encourage participation. - Experience with adult learning principles and techniques. - Bachelor’s or Master's degree in a technical field or education. - Training certifications (e.g., CTT+, CST, etc.). - Experience with learning management systems. - Background in solution architecture or technical consulting. - Experience with agile and DevOps methodologies. - Knowledge of multiple regional markets within assigned geography. Skills: maybe we can extract specific skills from preferred: ability to explain complex technical concepts, presentation/public speaking, leading group dynamics, adult learning principles, etc. But we already have Qualifications. Could treat Skills as those abilities. But to avoid duplication, maybe we put Skills as subset: ability to explain complex technical concepts clearly, strong presentation and public speaking skills, ability to lead group dynamics and encourage participation, experience with adult learning principles and techniques. However that duplicates. Could instead not have Skills section if content overlaps. But we need to decide. The instruction: prefer a few substantive sections over many thin ones. So maybe we combine Qualifications and Skills into one? But we need headings only if real content. Could have Qualifications (preferred) and not Skills. Or have Skills and not Qualifications. Which is more appropriate? The headings list includes both Qualifications and Skills. We could put minimum qualifications under Requirements, preferred under Qualifications, and maybe specific abilities under Skills. But that splits preferred list. Might be okay. Let's assign: - Requirements: minimum qualifications. - Qualifications: preferred qualifications that are credentials/education/certifications: Bachelor’s/Master's degree, Training certifications, Experience with LMS, Background in solution architecture, Experience with agile/DevOps, Knowledge of multiple regional markets. - Skills: abilities: explain complex technical concepts, experience with virtual training platforms, strong presentation/public speaking, lead group dynamics, adult learning principles. That seems reasonable. Now Benefits: extract benefits paragraph. From "Message to applicants...": benefits include medical, dental and vision insurance, a 401(k) plan with a Cisco matching contribution, paid parental leave, short and long-term disability coverage, basic life insurance. Also RSU grants. Paid time away: 10 paid holidays per full calendar year, plus 1 floating holiday for non-exempt employees, 1 paid day off for employee’s birthday, paid year-end holiday shutdown, and 4 paid days off for personal wellness determined by Cisco. Non-exempt employees receive 16 days of paid vacation time per full calendar year, accrued at rate of 4.92 hours per pay period for full-time employees. Exempt employees participate in Cisco’s flexible vacation time off program, which has no defined limit on how much vacation time eligible employees may use (subject to availability and some business limitations). 80 hours of sick time off provided on hire date and each January 1st thereafter, and up to 80 hours of unused sick time carried forward from one calendar year to the next. Additional paid time away may be requested to deal with critical or emergency issues for family members. Optional 10 paid days per full calendar year to volunteer. For non-sales roles, employees are also eligible to earn annual bonuses subject to Cisco’s policies. Employees On Sales Plans Earn Performance-based Incentive Pay On Top Of Their Base Salary... That's more about pay/incentive; but we can keep bonus mention under Benefits? Actually annual bonuses for non-sales roles; but for sales plans it's incentive pay. We'll keep benefits as described, maybe mention annual bonuses for non-sales roles. Pay: salary range info: starting salary range $98,600-$125,000, location-specific ranges: New York City Metro Area $106,700-$155,700; Non-Metro New York State & Washington State $101,700-$148,100. Also note that for quota-based sales roles, ranges include base pay and sales target incentive compensation combined. Also details of incentive calculation: .75% etc. Also mention that employees on sales plans earn performance-based incentive pay on top of base salary, split between quota and non-quota components, etc. Also note that Cisco sales plans do not have a minimum threshold. We need to preserve all substantive info; not invent. Now produce HTML. Structure:

  About the role

  ... combined paragraphs ...

  Responsibilities

  ... impact paragraph ...

  Requirements

  • ... each ...

  Qualifications

  • ... preferred qualifications that are credentials ...

  Skills

  • ... abilities ...

  Benefits

  ... benefits paragraph ...

  Pay

  ... salary and incentive details ...

  Make sure not to include any boilerplate like "Message to applicants applying to work in the U.S. and/or Canada:" we can keep the content after that but remove the intro sentence? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Message to applicants applying to work in the U.S. and/or Canada:" is like a heading; we can drop that heading but keep the content after. So we just include the benefits and pay paragraphs without that heading. Also remove "The application window is expected to close on: 10/02/2026" - drop. Now craft the paragraphs. About the role: combine: "Our team is made up of passionate professionals who are committed to driving the success of Cisco's technical sales force. We thrive on collaboration, innovation, and delivering exceptional learning experiences to our global workforce. Together, we combine technical expertise, real-world experience, and a dedication to professional development to support Cisco's mission of shaping the future of technology." "At Cisco, we are dedicated to advancing the skills of our technical sales professionals through impactful training programs. Our global Learning & Development team focuses on delivering comprehensive training across our networking, data center infrastructure, collaboration, security, and observability products. By combining technical expertise with strong facilitation skills, we create engaging learning experiences that accelerate professional development and drive success in technical sales." "At Cisco, we’re revolutionizing how data and infrastructure connect and protect organizations in the AI era – and beyond. We’ve been innovating fearlessly for 40 years to create solutions that power how humans and technology work together across the physical and digital worlds. These solutions provide customers with unparalleled security, visibility, and insights across the entire digital footprint. Fueled by the depth and breadth of our technology, we experiment and create meaningful solutions. Add to that our worldwide network of doers and experts, and you’ll see that the opportunities to grow and build are limitless. We work as a team, collaborating with empathy to make really big things happen on a global scale. Because our solutions are everywhere, our impact is everywhere. We are Cisco, and our power starts with you." We can combine into one or multiple

  . Probably multiple

  under same heading is okay. Responsibilities: use the impact paragraph (the second one). Could be same as above but we already used it in About the role; maybe we should not duplicate. Better: About the role includes team description and why Cisco; Responsibilities includes the impact/training description. Let's split: About the role: team description