Jr. Technical Sales Support Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to extract content. Given posting: It includes "About This Role" paragraph. Then "Key Responsibilities And Accountabilities" bullet list (actually sentences). Then "Essential Qualifications, Experience, And Skills". Then "Travel" section. Then "Compensation: $80,000 USD". Also mention "Upon request, we will provide reasonable accommodation..." etc. Also mention "All qualified applicants..." etc. Those are boilerplate EEO etc; we need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO statements, the accommodation line? The accommodation line is about disability accommodation; might be considered EEO? It's about reasonable accommodation for disabilities; likely considered EEO/legal boilerplate, we should remove. Also the line about all applications reviewed directly etc. Also the thank you note. Those are boilerplate; remove. We need to preserve substantive info: About the role paragraph, responsibilities list, qualifications/skills list, travel info, compensation. We need to format sections: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections we have content for. We have About the role: yes. Responsibilities: yes (Key Responsibilities And Accountabilities). We'll output as

• each responsibility. Qualifications: The posting has "Essential Qualifications, Experience, And Skills". This includes qualifications, experience, skills. We could split into Qualifications and Skills sections if we have distinct content. The list includes: Bachelor’s degree in engineering. Electrical Engineering preferred. Previous experience interacting directly with customers. Technical and Creative problem-solving skills; ability to systematically diagnose problems and determine next steps or solutions. Exceptional time management and multitasking skills. Ability to pivot priorities and shift focus for Reactive or Time-sensitive asks. Excellent communication skills (written and verbal), interpersonal skills, and networking/collaboration abilities. Initiative/Attitude to seek out true solutions and improve internal processes to more effectively perform job duties. Team-oriented attitude; ability to work within small teams to support other technicians/engineers with shared problems and varied experience. 1-2 years of related technical experience. Familiarity with electrical standards and codes (e.g., NEC, UL, ANSI, IEC). Preferred previous experience using customer relationship management (CRM) software e.g. Salesforce; update and track customer requests within software. Excellent presentation skills, with previous experience building presentation materials and speaking to small and medium-sized groups. Multilingual skills (especially French or Spanish). Experience with consumer-based power tools; ability to operate them safely. We could separate Qualifications (education, experience, years, familiarity with standards, CRM experience) and Skills (problem solving, time management, communication, initiative, teamwork, presentation, multilingual, power tools). But the instruction says prefer a few substantive sections over many thin ones. Could combine Qualifications and Skills into one section? But they ask to use headings like Qualifications, Skills separately if content exists. We have content for both. Could split. Travel: we have travel info. That could go under Schedule? Actually travel is not schedule. There's no explicit Benefits section. No benefits mentioned besides maybe travel? Not benefits. So we should not create Benefits unless posting actually states them. No benefits mentioned. So omit Benefits. Pay: we have compensation: $80,000 USD. So include Pay section. Schedule: Not mentioned. No schedule info (like full-time, part-time, shift). So omit Schedule. Requirements: Could be similar to Qualifications? The posting doesn't have a separate "Requirements" heading; but we have qualifications etc. Could we treat Qualifications as Requirements? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide if we have content for Requirements. The posting includes "Essential Qualifications, Experience, And Skills". That could be considered Qualifications and Skills. Requirements might be overlapping. But we could treat the qualifications as Requirements. However we also have Skills. To avoid duplication, maybe we put all under Qualifications and omit Requirements. But we need to follow instruction: include a section ONLY when the posting has real, specific content for it. So if we don't have distinct Requirements content separate from Qualifications, we should not create a Requirements section. So we will have About the role, Responsibilities, Qualifications, Skills, Pay, Travel? Travel is not a standard heading; but we could put under Schedule? Not appropriate. Travel could be considered under Schedule? Not really. There's no heading for Travel. Could we put travel under Schedule? No. The instruction only lists those headings; but we can add other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples, not exhaustive? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings where appropriate. Travel is not listed; but we could still create a heading like Travel if needed? The instruction says use those as examples; but we should probably stick to those headings. Travel info could be placed under Schedule? Not accurate. Could be under Requirements? Not really. Could be under About the role? Could add a sentence about travel in About the role? But we should preserve all substantive info; we could include travel details in a

  under About the role or maybe under Responsibilities? Travel is not a responsibility but a condition. Could be under Requirements (like travel required). But the heading "Requirements" could contain travel requirement. However the posting also has "Drivers license required." That's a requirement. So we could put travel and driver's license under Requirements. But we also have qualifications etc. Might be better to have a Requirements section for things like degree, experience, travel, driver's license, etc. And Skills section for abilities like problem solving, communication, etc. Let's parse. The posting includes: - Bachelor’s degree in engineering. Electrical Engineering preferred. - Previous experience interacting directly with customers. - 1-2 years of related technical experience. - Familiarity with electrical standards and codes (e.g., NEC, UL, ANSI, IEC). - Preferred previous experience using CRM software e.g. Salesforce; update and track customer requests within software. - Drivers license required. - Travel: Up to 30% of yearly working hours, up to 3 trips per month (max) Majority of destinations remain within North America. Potential overseas travel to company HQ in France (for training). These could be considered Requirements (or Qualifications). Then Skills: - Technical and Creative problem-solving skills; ability to systematically diagnose problems and determine next steps or solutions. - Exceptional time management and multitasking skills. - Ability to pivot priorities and shift focus for Reactive or Time-sensitive asks. - Excellent communication skills (written and verbal), interpersonal skills, and networking/collaboration abilities. - Initiative/Attitude to seek out true solutions and improve internal processes to more effectively perform job duties. - Team-oriented attitude; ability to work within small teams to support other technicians/engineers with shared problems and varied experience. - Excellent presentation skills, with previous experience building presentation materials and speaking to small and medium-sized groups. - Multilingual skills (especially French or Spanish). - Experience with consumer-based power tools; ability to operate them safely. Thus we can split. Thus sections: About the role, Responsibilities, Requirements, Skills, Pay. We have no Benefits, Schedule. We need to output HTML fragment only. We'll wrap each section in

  heading then content. For About the role: a

  with the paragraph. For Responsibilities:

  • each responsibility sentence. We need to extract each responsibility sentence from the block: "Answer technical inquiries from both the clients and internal employees, primarily through Email-to-Case ticketing system." etc. Let's list them: 1. Answer technical inquiries from both the clients and internal employees, primarily through Email-to-Case ticketing system. 2. Become an expert in Socomec products; understand the design, primary use, benefits, and (especially) limitations of Socomec products in order to give accurate and realistic recommendations to customers and external agents. 3. Train and onboard professionals on the Socomec product portfolio and relevant applications (Sales, Service, External Representatives). 4. Investigate and troubleshoot customer issues; provide assistance by referencing technical manuals, conferring with users, and/or conducting product diagnostics. 5. Handle “Reactive” situations; ability to work under pressure or pivot priorities as more-pressing situations reveal themselves. 6. Effectively navigate Socomec’s network of experts, both in North America and Overseas, to effectively and efficiently leverage their experience. 7. Understand and Clearly Articulate the governing standards applicable to both Socomec products and the larger systems they are installed within. 8. Become a primary user for data platforms and integration/testing softwares. 9. Prepare/manage official reports for Remote Support and Customer calls. 10. Confer directly with customers to assess equipment needs and to determine system requirements. 11. Develop, present, and respond to proposals for customer requirements; work with business developers to propose industry-specific solutions. 12. Prepare and deliver technical presentations explaining Socomec products, features, connectivity, and/or services to customers and prospective customers. 13. Host trainings focused on Socomec products and targeted customer applications. 14. Conduct Site-Audits; point out potential challenges with customer’s design and recommend solutions; anticipate potential issues around installation, integration, network implementation, or limitations of specified devices. 15. Conduct demonstrations and trial installations of equipment; Manipulate demo/sample equipment and give walkthroughs of device setup and usage. 16. Confer with Product Marketing, MARCOM, Business Development, and Regional Sales Teams to support Socomec’s marketing strategies and activities; promote products and services. 17. Present seminars/webinars with Q&A sessions to clients, general sales teams and reps. 18. Participate in promotional activities like Conventions and Trade Shows. 19. Prepare situational case studies based on experiences in the field. 20. Assist in the creation and management of marketing collateral materials for product launches and upgrades/updates. 21. Update technical aspects of promotional materials, and collaborate with Marketing team to update existing marketing resources to modern offerings. 22. Support with product catalog; confer with Marketing team to ensure all corrections are implemented. That's many items. We'll keep them. For Requirements: list items: - Bachelor’s degree in engineering. Electrical Engineering preferred. - Previous experience interacting directly with customers. - 1-2 years of related technical experience. - Familiarity with electrical standards and codes (e.g., NEC, UL, ANSI, IEC). - Preferred previous experience using customer relationship management (CRM) software e.g. Salesforce; update and track customer requests within software. - Drivers license required. - Travel: Up to 30% of yearly working hours, up to 3 trips per month (max). Majority of destinations remain within North America. Potential overseas travel to company HQ in France (for training). We could split travel into separate sentences. For Skills: list items: - Technical and Creative problem-solving skills; ability to systematically diagnose problems and determine next steps or solutions. - Exceptional time management and multitasking skills. - Ability to pivot priorities and shift focus for Reactive or Time-sensitive asks. - Excellent communication skills (written and verbal), interpersonal skills, and networking/collaboration abilities. - Initiative/Attitude to seek out true solutions and improve internal processes to more effectively perform job duties. - Team-oriented attitude; ability to work within small teams to support other technicians/engineers with shared problems and varied experience. - Excellent presentation skills, with previous experience building presentation materials and speaking to small and medium