Senior Sales System Engineer 2-Ter
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info.
We need to parse the job posting.
Key info:
- Title: Senior Sales System Engineer 2-Ter (but we don't repeat as heading)
- Overall Purpose: Drives the design, implementation, and optimization of advanced technical sales solutions, serving as a subject matter expert to ensure successful customer integration of company products and services.
- Salary: $85,400 - $128,000 + $26,400 commissions, total target compensation $111,800 - $154,400.
- Benefits: Medical/Dental/Vision coverage, 401(k) plan, Tuition reimbursement program, Paid Time Off and Holidays (at least 23 days vacation each year and 9 company-designated holidays), Paid Parental Leave, Paid Caregiver Leave, Additional sick leave beyond state/local law may be available but unprotected, Adoption Reimbursement, Disability Benefits (short term and long term), Life and Accidental Death Insurance, Supplemental benefit programs: critical illness/accident hospital indemnity/group legal, Employee Assistance Programs (EAP), Extensive employee wellness programs, Employee discounts up to 50% off on eligible AT&T mobility plans and accessories, AT&T internet (and fiber where available) and AT&T phone.
- Weekly Hours: 40
- Time Type: Regular
- Location: Hoover, Alabama, Huntsville, Alabama
- Key Roles and Responsibilities: list of tasks (Technical Expertise and Customer Consultation, System Design, Implementation, and Continuous Improvement, Customer Integration and Support, Project Management and Collaboration, Product Demonstrations and Documentation)
- Job Contribution: description of role.
- Supervisor: No
- Education/Experience: Bachelor’s degree (BS/BA) desired. 5+ years of sales related experience. Sales Targets: Demonstrated ability to meet and/or exceed assigned sales targets. Valid Driver’s License: Must have a valid driver’s license with a satisfactory driving record, current auto insurance, and a reliable vehicle to meet the transportation needs of the market.
- Also mention: Sales employees will concentrate on acquiring new business and conducting customer visits in the field. When not in the field, they are expected to collaborate with their team from their assigned office location, if available.
We need to map to sections:
- About the role: could include overall purpose and maybe description of role (Job Contribution). Could combine.
- Responsibilities: list of tasks (Key Roles and Responsibilities). Also maybe mention field work and office collaboration.
- Requirements: Education/Experience, Valid Driver's License, Sales Targets, maybe Supervisor: No? Not needed.
- Qualifications: maybe Bachelor's degree desired, 5+ years sales experience, driver's license.
- Skills: maybe technical expertise, system design, project management, product demonstrations, etc. Could be derived from responsibilities.
- Benefits: list benefits.
- Pay: salary range + commission.
- Schedule: Weekly Hours: 40, Time Type: Regular.
We must not include sections with placeholder or vague content. All sections we include must have real specific content.
We must not repeat job title as heading. Must not include Job ID etc.
We must output only HTML fragment, no /, no markdown fences.
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.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions.
We need to avoid repeating same info multiple times.
Let's extract substantive content:
Overall Purpose paragraph: "Drives the design, implementation, and optimization of advanced technical sales solutions, serving as a subject matter expert to ensure successful customer integration of company products and services."
Job Contribution paragraph: "A mid-level sales representative with comprehensive knowledge of sales principles, practices, products, and services. Manages mid-size to large, complex sales with moderate supervision. Responsible for an average quota or territory. Utilizes advanced data analysis, creative problem-solving, and exercises judgment. Leads presentations and mentors less experienced peers. If the sales career path includes multiple positions at the I09 level, the more senior role entails higher sales targets, broader scope, and greater complexity."
Field work: "Sales employees will concentrate on acquiring new business and conducting customer visits in the field. When not in the field, they are expected to collaborate with their team from their assigned office location, if available."
Supervisor: No (maybe not needed).
Education/Experience: "Bachelor’s degree (BS/BA) desired. 5+ years of sales related experience."
Sales Targets: "Demonstrated ability to meet and/or exceed assigned sales targets."
Valid Driver’s License: "Must have a valid driver’s license with a satisfactory driving record, current auto insurance, and a reliable vehicle to meet the transportation needs of the market."
Responsibilities list (Key Roles and Responsibilities): bullet points:
- Technical Expertise and Customer Consultation: Serve as a subject matter expert, providing technical guidance and consultation to direct sales teams and customers on the design, customization, and implementation of complex technical products and services.
- System Design, Implementation, and Continuous Improvement: Lead the design, development, and implementation of advanced sales solutions, continuously identifying and implementing process enhancements in collaboration with product architects and the development community.
- Customer Integration and Support: Ensure product integration, troubleshoot and escalate issues, support sales plans, and provide training to sales teams and customers.
- Project Management and Collaboration: Manage deployment projects, align technical solutions with business goals, and lead technical discussions in client meetings.
- Product Demonstrations and Documentation: Design solutions, support sales presentations, create prototypes, maintain product knowledge, and document systems and processes.
Benefits list: many items.
Pay: "$85,400 - $128,000 + $26,400 in commissions with a total target compensation of $111,800 - $154,400." Also repeated later: "$85,400.00 - $128,000.00 + commission $26,400". We'll include once.
Schedule: "Weekly Hours: 40 Time Type: Regular". Also location maybe not needed for schedule but could be in About the role? Location is not schedule; maybe we could include location in About the role or separate? There's no specific heading for location; we could put location in About the role as prose.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state them, so include.
We must not include sections with filler like "commensurate with experience". We have actual numbers.
Now decide which sections to include:
- About the role: include overall purpose and job contribution and field work and location maybe.
- Responsibilities: the list.
- Requirements: maybe include education/experience, driver's license, sales targets.
- Qualifications: maybe overlapping with requirements; but we could combine. However we need to avoid thin sections. Could combine Requirements and Qualifications into one? But spec says use headings for those categories if we have content. We could have both if we have distinct content. Let's see: Requirements could be mandatory items: Bachelor's degree desired, 5+ years sales experience, valid driver's license, ability to meet sales targets. Qualifications could be preferred or additional: maybe supervisor? Not much. Could skip Qualifications if not distinct.
- Skills: could list technical expertise, system design, project management, product demonstrations, etc. Could be derived from responsibilities but we might avoid duplication. However we need to preserve all substantive info; if we put skills as list, we might duplicate responsibilities. Better to put skills as a short list of competencies: technical guidance, system design, process improvement, troubleshooting, project management, technical discussions, product demonstrations, documentation, data analysis, problem-solving, judgment, presentation, mentoring. That is substantive and not just repeating responsibilities verbatim but derived. However we must not invent or summarize away detail; we can list skills that are explicitly mentioned in the posting. Let's extract skill mentions: technical guidance, consultation, design, customization, implementation, process enhancements, collaboration, troubleshoot, escalate, support sales plans, provide training, manage deployment projects, align technical solutions with business goals, lead technical discussions, design solutions, support sales presentations, create prototypes, maintain product knowledge, document systems and processes, advanced data analysis, creative problem-solving, exercises judgment, leads presentations, mentors less experienced peers. That's a lot; we could list them as skills.
But we must avoid too many thin sections; maybe we can combine Skills into Responsibilities? However spec says use
- for any list of duties/requirements/benefits. So responsibilities list is already a list. Skills could be another list.
But we need to decide which sections to include to avoid too many thin ones but still capture all info. Perhaps we can include About the role (purpose + job contribution + field work + location), Responsibilities (list), Requirements (education/experience, driver's license, sales targets), Benefits (list), Pay (salary+commission), Schedule (hours/time type). That's six sections. Skills maybe omitted if we feel responsibilities cover it. However the posting also mentions "Technical Expertise and Customer Consultation" etc which are responsibilities; skills are implied. I think we can omit Skills section to avoid thinness.
Qualifications maybe also omitted.
Let's verify we haven't missed any substantive info: Supervisor: No (maybe not needed). Could be included in Requirements as "Supervisor: None". But it's minor; we could drop as it's not a requirement.
Location: Hoover, Alabama, Huntsville, Alabama. Could be in About the role.
Now we need to format.
We'll produce:
About the role
Drives the design, implementation, and optimization of advanced technical sales solutions, serving as a subject matter expert to ensure successful customer integration of company products and services. A mid-level sales representative with comprehensive knowledge of sales principles, practices, products, and services. Manages mid-size to large, complex sales with moderate supervision. Responsible for an average quota or territory. Utilizes advanced data analysis, creative problem-solving, and exercises judgment. Leads presentations and mentors less experienced peers. Sales employees will concentrate on acquiring new business and conducting customer visits in the field. When not in the field, they are expected to collaborate with their team from their assigned office location, if available. Positions are located in Hoover, Alabama and Huntsville, Alabama.
Responsibilities
- Technical Expertise and Customer Consultation: Serve as a subject matter expert, providing technical guidance and consultation to direct sales teams and customers on the design, customization, and implementation of complex technical products and services.
- System Design, Implementation, and Continuous Improvement: Lead the design, development, and implementation of advanced sales solutions, continuously identifying and implementing process enhancements in collaboration with product architects and the development community.
- Customer Integration and Support: Ensure product integration, troubleshoot and escalate issues, support sales plans, and provide training to sales teams and customers.
- Project Management and Collaboration: Manage deployment projects, align technical solutions with business goals, and lead technical discussions in client meetings.
- Product Demonstrations and Documentation: Design solutions, support sales presentations, create prototypes, maintain product knowledge, and document systems and processes.
Requirements
- Bachelor’s degree (BS/BA) desired.
- 5+ years of sales related experience.
- Demonstrated ability to meet and/or exceed assigned sales targets.
- Valid driver’s license with a satisfactory
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to avoid repeating same info multiple times. Let's extract substantive content: Overall Purpose paragraph: "Drives the design, implementation, and optimization of advanced technical sales solutions, serving as a subject matter expert to ensure successful customer integration of company products and services." Job Contribution paragraph: "A mid-level sales representative with comprehensive knowledge of sales principles, practices, products, and services. Manages mid-size to large, complex sales with moderate supervision. Responsible for an average quota or territory. Utilizes advanced data analysis, creative problem-solving, and exercises judgment. Leads presentations and mentors less experienced peers. If the sales career path includes multiple positions at the I09 level, the more senior role entails higher sales targets, broader scope, and greater complexity." Field work: "Sales employees will concentrate on acquiring new business and conducting customer visits in the field. When not in the field, they are expected to collaborate with their team from their assigned office location, if available." Supervisor: No (maybe not needed). Education/Experience: "Bachelor’s degree (BS/BA) desired. 5+ years of sales related experience." Sales Targets: "Demonstrated ability to meet and/or exceed assigned sales targets." Valid Driver’s License: "Must have a valid driver’s license with a satisfactory driving record, current auto insurance, and a reliable vehicle to meet the transportation needs of the market." Responsibilities list (Key Roles and Responsibilities): bullet points: - Technical Expertise and Customer Consultation: Serve as a subject matter expert, providing technical guidance and consultation to direct sales teams and customers on the design, customization, and implementation of complex technical products and services. - System Design, Implementation, and Continuous Improvement: Lead the design, development, and implementation of advanced sales solutions, continuously identifying and implementing process enhancements in collaboration with product architects and the development community. - Customer Integration and Support: Ensure product integration, troubleshoot and escalate issues, support sales plans, and provide training to sales teams and customers. - Project Management and Collaboration: Manage deployment projects, align technical solutions with business goals, and lead technical discussions in client meetings. - Product Demonstrations and Documentation: Design solutions, support sales presentations, create prototypes, maintain product knowledge, and document systems and processes. Benefits list: many items. Pay: "$85,400 - $128,000 + $26,400 in commissions with a total target compensation of $111,800 - $154,400." Also repeated later: "$85,400.00 - $128,000.00 + commission $26,400". We'll include once. Schedule: "Weekly Hours: 40 Time Type: Regular". Also location maybe not needed for schedule but could be in About the role? Location is not schedule; maybe we could include location in About the role or separate? There's no specific heading for location; we could put location in About the role as prose. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state them, so include. We must not include sections with filler like "commensurate with experience". We have actual numbers. Now decide which sections to include: - About the role: include overall purpose and job contribution and field work and location maybe. - Responsibilities: the list. - Requirements: maybe include education/experience, driver's license, sales targets. - Qualifications: maybe overlapping with requirements; but we could combine. However we need to avoid thin sections. Could combine Requirements and Qualifications into one? But spec says use headings for those categories if we have content. We could have both if we have distinct content. Let's see: Requirements could be mandatory items: Bachelor's degree desired, 5+ years sales experience, valid driver's license, ability to meet sales targets. Qualifications could be preferred or additional: maybe supervisor? Not much. Could skip Qualifications if not distinct. - Skills: could list technical expertise, system design, project management, product demonstrations, etc. Could be derived from responsibilities but we might avoid duplication. However we need to preserve all substantive info; if we put skills as list, we might duplicate responsibilities. Better to put skills as a short list of competencies: technical guidance, system design, process improvement, troubleshooting, project management, technical discussions, product demonstrations, documentation, data analysis, problem-solving, judgment, presentation, mentoring. That is substantive and not just repeating responsibilities verbatim but derived. However we must not invent or summarize away detail; we can list skills that are explicitly mentioned in the posting. Let's extract skill mentions: technical guidance, consultation, design, customization, implementation, process enhancements, collaboration, troubleshoot, escalate, support sales plans, provide training, manage deployment projects, align technical solutions with business goals, lead technical discussions, design solutions, support sales presentations, create prototypes, maintain product knowledge, document systems and processes, advanced data analysis, creative problem-solving, exercises judgment, leads presentations, mentors less experienced peers. That's a lot; we could list them as skills. But we must avoid too many thin sections; maybe we can combine Skills into Responsibilities? However spec says use
- for any list of duties/requirements/benefits. So responsibilities list is already a list. Skills could be another list.
But we need to decide which sections to include to avoid too many thin ones but still capture all info. Perhaps we can include About the role (purpose + job contribution + field work + location), Responsibilities (list), Requirements (education/experience, driver's license, sales targets), Benefits (list), Pay (salary+commission), Schedule (hours/time type). That's six sections. Skills maybe omitted if we feel responsibilities cover it. However the posting also mentions "Technical Expertise and Customer Consultation" etc which are responsibilities; skills are implied. I think we can omit Skills section to avoid thinness.
Qualifications maybe also omitted.
Let's verify we haven't missed any substantive info: Supervisor: No (maybe not needed). Could be included in Requirements as "Supervisor: None". But it's minor; we could drop as it's not a requirement.
Location: Hoover, Alabama, Huntsville, Alabama. Could be in About the role.
Now we need to format.
We'll produce:
About the role
Drives the design, implementation, and optimization of advanced technical sales solutions, serving as a subject matter expert to ensure successful customer integration of company products and services. A mid-level sales representative with comprehensive knowledge of sales principles, practices, products, and services. Manages mid-size to large, complex sales with moderate supervision. Responsible for an average quota or territory. Utilizes advanced data analysis, creative problem-solving, and exercises judgment. Leads presentations and mentors less experienced peers. Sales employees will concentrate on acquiring new business and conducting customer visits in the field. When not in the field, they are expected to collaborate with their team from their assigned office location, if available. Positions are located in Hoover, Alabama and Huntsville, Alabama.
Responsibilities
- Technical Expertise and Customer Consultation: Serve as a subject matter expert, providing technical guidance and consultation to direct sales teams and customers on the design, customization, and implementation of complex technical products and services.
- System Design, Implementation, and Continuous Improvement: Lead the design, development, and implementation of advanced sales solutions, continuously identifying and implementing process enhancements in collaboration with product architects and the development community.
- Customer Integration and Support: Ensure product integration, troubleshoot and escalate issues, support sales plans, and provide training to sales teams and customers.
- Project Management and Collaboration: Manage deployment projects, align technical solutions with business goals, and lead technical discussions in client meetings.
- Product Demonstrations and Documentation: Design solutions, support sales presentations, create prototypes, maintain product knowledge, and document systems and processes.
Requirements
- Bachelor’s degree (BS/BA) desired.
- 5+ years of sales related experience.
- Demonstrated ability to meet and/or exceed assigned sales targets.
- Valid driver’s license with a satisfactory
- for any list of duties/requirements/benefits. So responsibilities list is already a list. Skills could be another list.
But we need to decide which sections to include to avoid too many thin ones but still capture all info. Perhaps we can include About the role (purpose + job contribution + field work + location), Responsibilities (list), Requirements (education/experience, driver's license, sales targets), Benefits (list), Pay (salary+commission), Schedule (hours/time type). That's six sections. Skills maybe omitted if we feel responsibilities cover it. However the posting also mentions "Technical Expertise and Customer Consultation" etc which are responsibilities; skills are implied. I think we can omit Skills section to avoid thinness.
Qualifications maybe also omitted.
Let's verify we haven't missed any substantive info: Supervisor: No (maybe not needed). Could be included in Requirements as "Supervisor: None". But it's minor; we could drop as it's not a requirement.
Location: Hoover, Alabama, Huntsville, Alabama. Could be in About the role.
Now we need to format.
We'll produce: