Inside Sales Associate II

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections where posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc as headings; fold minor metadata into short

or drop it. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Preserve all substantive info. We need to parse the job description. Key parts: - Intro about ADI: "ADI is North America’s leading wholesale distributor of security and low-voltage..." etc. This is about company, maybe "About the role"? Actually "About the role" heading is for description of role. Could use "About the role" for the paragraph describing the Inside Sales Associate role. - Then "JOB DUTIES:" list bullet points. - Then "YOU MUST HAVE:" list. - Then "WE VALUE:" list. - Then "WHAT'S IN IT FOR YOU:" list benefits etc. - Then "About Us" paragraph about company. - Then "JOB INFO" includes Job Identification, Job Category, Posting Date, Job Schedule, Locations, Incentive Eligible, Business, Hiring Salary Range, Incentive Eligible (SIP) details, Benefits, US Visa Sponsorship Eligibility. We need to include sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. - About the role: maybe the introductory paragraph describing the Inside Sales Associate role: "ADI Global Distribution is hiring an Inside Sales Associate who will increase market share, uncover new opportunities, and provide solutions to customer's needs that result in continued long-term customer partnerships." - Responsibilities: the "JOB DUTIES:" list. - Requirements: "YOU MUST HAVE:" list. - Qualifications: maybe "WE VALUE:" list? Or could be considered qualifications. But we have separate sections for Skills maybe. We have to avoid duplication. Could map: - Requirements: mandatory requirements (YOU MUST HAVE). - Qualifications: preferred qualifications (WE VALUE). - Skills: maybe combine some skill items from both? But we can also put skills under Requirements or Qualifications. However we need to include sections only if there is real specific content. We could include Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to avoid thin sections. Let's see content: - Requirements (YOU MUST HAVE): 1 year of Sales Experience; Excellent verbal and written communication skills; Computer literacy skills – Basic Knowledge to Operate Microsoft Office; Desire to be in a Sales role and be accountable for Sales Revenue. - Qualifications (WE VALUE): Prior experience in Retail / Hospitality / Customer Service Industry with ability to negotiate and understanding of marketing skills; Knowledge of Customer Relationship Management Tools; Candidates who thrive in a fast-paced result driven environment by meeting and exceeding all goals and targets; Prior distribution experience; Excellent Negotiation Skills; Ability to work as part of a team and autonomously; Highly competitive Sales Skills with a desire to contribute to a winning team/organization. - Skills: maybe we could extract specific skill items like "Excellent verbal and written communication skills", "Computer literacy", "Negotiation Skills", etc. But that overlaps with Requirements/Qualifications. Could combine them into a Skills section, but we already have Requirements and Qualifications. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one "Requirements" section? But we have separate headings allowed. However we could include only Requirements and Qualifications (both substantive) and Benefits, Pay, Schedule. That's four sections. Could also include Responsibilities (definitely). So sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's six sections, each substantive. Check each: - About the role: we have a paragraph describing the role. - Responsibilities: JOB DUTIES list. - Requirements: YOU MUST HAVE list. - Qualifications: WE VALUE list. - Benefits: WHAT'S IN IT FOR YOU list (medical, dental, vision, commuter benefit, pet insurance, 401k participation from Day 1, 2 weeks' accrued vacation time in years 1 and 2, and 3 weeks starting in year 3, 12 paid holidays each year, four weeks parental leave without using vacation time, Team Member discounts on company products and other retail/service providers, Monday to Friday working hours - no weekends, Opportunity to progress within a global business). Also note "Benefits :" in JOB INFO includes life and health insurance etc. But we already captured benefits from WHAT'S IN IT FOR YOU. We should include all benefits info. The WHAT'S IN IT FOR YOU includes many; also JOB INFO Benefits: "We provide comprehensive benefits, including life and health insurance, life assistance program, accidental death and dismemberment insurance, disability insurance, 401k Plan, vacation & holidays." That's overlapping but we can combine. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include both sets. However we must avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say we must deduplicate, but we should not lose any info. Duplication is okay if it's present in source; but we should not invent. We can include both; but we might combine to avoid redundancy but still preserve info. If we combine, we need to ensure we didn't lose any detail. If we combine, we need to include all items from both sources. That's fine. - Pay: Hiring Salary Range: "The typical hiring salary for this role, ranges from USD $15.94 to $27.14 per hour but varies by specific work location. Within a range, our company determines base pay for an individual based on various factors, including market conditions, skills, and experience." Also Incentive Eligible (SIP) details: "This position is eligible for a performance-based bonus of up to 42.86% of your annual salary, and prorated based on hire date. Attaining your sales target qualifies you for 100% of your annual sales incentive, while surpassing sales targets during the performance period enables you to earn additional incentive pay." That's pay-related. So we can include Pay section with salary range and incentive details. - Schedule: Job Schedule: Full time. Locations: 2701 Noblin Road, Raleigh, 27604, US (On-site). Also Monday to Friday working hours - no weekends (already in benefits). But schedule section should include full-time, location, maybe hours. We'll include schedule: Full-time, On-site at 2701 Noblin Road, Raleigh, NC 27604, Monday-Friday (no weekends). Also note Job Schedule: Full time. We must not include Job ID etc as headings; we can fold minor metadata into a short

or drop it. So we can include a short paragraph at top maybe with Job Category, Posting Date? But those are minor metadata; we could drop them or include in a

. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a

for things like Job Category: Inside Sales, Posting Date: 2026-09-25, Location: etc. But we already have location in Schedule section. Could include a short

for Posting Date and Job Category. However we need to preserve ALL substantive information; posting date is substantive? It's metadata but maybe considered minor. The instruction says fold minor metadata into a short

or drop it. So we can include a short

with that info. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the "About Us" paragraph? That's company description; is that substantive? It's about the company, not the role. Might be considered boilerplate? But it's substantive info about ADI. The instruction says preserve ALL substantive information; do not invent or summarize away detail. The "About Us" paragraph is substantive about the company. Should we keep it? Possibly under "About the role" or separate? But we already have About the role for the role description. The About Us could be considered company overview; maybe we can include it under About the role or as a separate section like "About the company". However allowed headings are limited to those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". So we could incorporate the About Us paragraph into About the role section (makes sense). Or we could drop it if considered boilerplate? It's not boilerplate; it's describing the company. The instruction says preserve ALL substantive information; we should keep it. So we can merge it into About the role. Thus About the role will contain: description of the role (Inside Sales Associate) plus company overview from About Us. Now we need to format lists: Use

• for any list of duties/requirements/benefits. Use

  for prose. We must output only HTML fragment, no /, no markdown. Let's craft. First, maybe a short

  for metadata: "Job Category: Inside Sales. Posted: September 25, 2026." Could be. Then

  About the role

  with

  containing role description and company overview. Then

  Responsibilities

  with
  of duties. Then

  Requirements

  with
  of must-haves. Then

  Qualifications

  with
  of valued. Then

  Benefits

  with
  of benefits. Then

  Pay

  with

  containing salary range and incentive details. Then

  Schedule

  with

  containing full-time, on-site location, Monday-Friday. We need to ensure we don't repeat headings with empty content. Now extract details precisely. From text: Role description: "ADI Global Distribution is hiring an Inside Sales Associate who will increase market share, uncover new opportunities, and provide solutions to customer's needs that result in continued long-term customer partnerships." Company overview (About Us): "ADI is a leading global distributor and solutions provider of security, AV, and smart living technologies, helping professionals deliver smarter, safer, and more connected experiences for homes and businesses around the world. Through trusted brands, exclusive solutions, and strong industry partnerships, ADI supports more than 110,000 customers across residential and commercial markets globally. From security and video surveillance to networking, audio, automation, fire, and connected technologies, ADI offers a broad portfolio of products, services, and software designed to support the evolving needs of integrators, installers, and technology professionals. With a global team spanning operations, sales, supply chain, digital, customer experience, engineering, and more, ADI combines deep industry expertise with innovation and service to help customers grow and succeed in an evolving industry. At ADI, our teams help create the technologies, partnerships, and experiences that keep people connected, protected, and supported every day. Learn more at www.adiglobal.com . You can find out more about how the talent community works here: ADI Talent Community Terms . Our recruitment privacy notice ADI - Recruitment Privacy Notice describes in more detail how we process your personal data and how you can exercise your personal data rights. If a disability prevents you from applying for a job through our website, request assistance here ." But the latter part includes legal/privacy etc which might be boilerplate? It's about recruitment privacy notice, disability assistance. Might be considered legal/EEO? The instruction says remove cookie/navigation/legal/