BEST Technical Sales Trainee - Security - Charlotte, NC
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate. Need to preserve all substantive info. Let's parse the posting. Content: - Intro paragraph about Johnson Controls (global leader...). That's about the company. Could be "About the role"? Actually "About the role" maybe includes description of role and company. We'll put that in a
under an
About the role
. - "Launch Your Career in Technical Sales Our Building Early Career Sales Training (BEST) Program is a 6-month development program designed for recent graduates looking to launch a career in technical sales. From day one, you'll be paired with a dedicated mentor and supported by a nationwide network of sales professionals. Through classroom training, hands-on experience, and customer interactions, you'll develop the technical expertise, business acumen, and relationship-building skills needed to succeed in a high-growth sales career." This is description of program. Could be part of About the role. - "What You Will Do" list: bullet points. - "What We Offer" list: bullet points. - "Required" heading then "What We Look For": bullet points. - "Preferred" bullet points. - "Check us out: A Day in the Life at Johnson Controls | Sales Roles https://www.youtube.com/watch?v=rS3_3zSHb4Q" This is a link; maybe we keep as awith link? It's not boilerplate; it's a resource. We'll keep. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have: - About the role: company intro + program description. - Responsibilities: "What You Will Do" list. - Requirements: "What We Look For" under Required. - Qualifications: maybe same as Requirements? Could combine? But we need separate sections only if content. We have "Preferred" which could be Qualifications or Skills. Let's map: Qualifications: Bachelor's degree in Business, Communications, Engineering or related field with anticipated graduation date Dec 2026 or May/June 2027. Also U.S. Citizenship or Permanent Residency. Skills: Strong analytical, problem-solving, communication skills; ability to manage multiple priorities and work collaboratively. Preferred: Internship, co-op, engineering, sales, or customer-facing experience; Interest in technical sales and customer relationship management. Benefits: Medical, dental, vision, 401(k) benefits starting Day 1; Paid vacation, sick time, floating holidays; Company vehicle; Dedicated mentorship and professional development; Clear career growth opportunities upon program completion; Collaborative and supportive team environment. Pay: Competitive Compensation package starting at $89,800, which includes base salary and bonus. Schedule: Not mentioned. So we should NOT include Schedule section. We must not include sections with filler like "commensurate with experience". We have actual pay. We need to output only HTML fragment, no /. Use
for each section heading, then content:
for prose,
- for lists.
We must not repeat job title as heading. Not include Job ID.
We need to preserve all substantive info: ensure we don't lose any bullet points.
Let's list bullet points:
What You Will Do:
- Participate in a structured 6-month sales development program
- Learn Johnson Controls' Security equipment, services, and building solutions
- Support sales activities, proposals, and project opportunities
- Build relationships with contractors, architects, engineers, and building owners
- Present technical solutions that help customers improve building performance and sustainability
- Partner with local sales and operations teams to deliver successful customer outcomes
What We Offer:
- Competitive Compensation package starting at $89,800, which includes base salary and bonus.
- Medical, dental, vision, and 401(k) benefits starting on Day 1
- Paid vacation, sick time, and floating holidays
- Company vehicle
- Dedicated mentorship and professional development
- Clear career growth opportunities upon program completion
- Collaborative and supportive team environment
Required What We Look For:
- Bachelor's degree in Business, Communications, Engineering or a related field with an anticipated graduation date of December 2026 or May/June 2027
- Strong analytical, problem-solving, and communication skills
- Ability to manage multiple priorities and work collaboratively
- U.S. Citizenship or Permanent Residency
Preferred:
- Internship, co-op, engineering, sales, or customer-facing experience
- Interest in technical sales and customer relationship management
Link: Check us out: A Day in the Life at Johnson Controls | Sales Roles https://www.youtube.com/watch?v=rS3_3zSHb4Q
We could put that as a
with an tag. Now decide sections: - About the role: includes intro paragraph about Johnson Controls and program description. Let's combine first two paragraphs: "Johnson Controls, a global leader... helps customers..." and "Launch Your Career in Technical Sales Our Building Early Career Sales Training (BEST) Program is a 6-month development program..." That's substantive. We could split: About the role (company overview) and maybe a separate section for Program Overview? But we only have allowed headings. We'll put all in About the role. - Responsibilities: list of What You Will Do. - Requirements: maybe combine Required and Preferred? But we have separate headings: Requirements and Qualifications and Skills. We need to decide mapping. We have Required (education, skills, citizenship). We have Preferred (experience, interest). We have Skills (analytical, problem-solving, communication, managing priorities). Actually those are in Required as well. Let's parse: Required bullet list includes: - Bachelor's degree... - Strong analytical, problem-solving, and communication skills - Ability to manage multiple priorities and work collaboratively - U.S. Citizenship or Permanent Residency Preferred bullet list includes: - Internship, co-op, engineering, sales, or customer-facing experience - Interest in technical sales and customer relationship management Thus we can map: Requirements: education and citizenship? Actually education is a qualification. Skills: analytical, problem-solving, communication, managing priorities. Qualifications: maybe education + citizenship? But we have separate headings for Qualifications and Skills. Let's assign: - Qualifications: Bachelor's degree in Business, Communications, Engineering or related field with anticipated graduation date Dec 2026 or May/June 2027; U.S. Citizenship or Permanent Residency. - Skills: Strong analytical, problem-solving, and communication skills; Ability to manage multiple priorities and work collaboratively. - Preferred (maybe we could put under Skills? But we have no heading for Preferred. Could put under Qualifications as "Preferred qualifications"? But we have no heading for Preferred. We could include Preferred under Qualifications as a list but label? The instruction: Use headings only from list. So we cannot create a heading for Preferred. We could embed Preferred content under Qualifications or Skills as additional bullet points. But we must not lose info. We could add them under Qualifications as extra bullet points, but they'd be mixed with required qualifications. That's okay as long as we preserve info. However we should not misrepresent them as required. But the instruction is to preserve ALL substantive information; not to mislabel. We could add a note? But we cannot add extra headings. Perhaps we can put Preferred under Skills as "Preferred skills/experience". But that might be inaccurate. Alternative: We could create a section "Qualifications" for education and citizenship, and a section "Skills" for analytical etc., and then put Preferred content under "Skills" as additional bullet points but maybe label them as "Preferred". However we cannot add extra text outside of
or
- . We could add a
before the list saying "Preferred:" but that's extra prose not a heading. That's allowed. The instruction: Use
for prose. So we can include a
Preferred:
then a- . That's okay.
Thus we can have:
- Internship, co-op, engineering, sales, or customer-facing experience
- Interest in technical sales and customer relationship management
Qualifications
Bachelor's degree in Business, Communications, Engineering or a related field with an anticipated graduation date of December 2026 or May/June 2027; U.S. Citizenship or Permanent Residency.
Skills
Strong analytical, problem-solving, and communication skills; Ability to manage multiple priorities and work collaboratively.
Preferred:
paragraphs. Now Responsibilities: list. Now Requirements: maybe we should keep a section "Requirements" for the required items (education, citizenship). But we already used Qualifications and Skills. The instruction says use headings for those categories if content exists. It didn't say we must use all; we can choose which to include. We have content for Qualifications, Skills, Benefits, Pay, Responsibilities, About the role. We could also include Requirements if we want, but we might duplicate. Better to follow the headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We have content for About the role, Responsibilities, Benefits, Pay. For Requirements we could put the required items (education, citizenship). For Qualifications we could put the degree? But that overlaps. Actually we could map: - Requirements: education and citizenship (maybe also "U.S. Citizenship or Permanent Residency"). - Qualifications: Bachelor's degree in Business, Communications, Engineering or related field with anticipated graduation date Dec 2026 or May/June 2027. - Skills: Strong analytical, problem-solving, and communication skills; Ability to manage multiple priorities and work collaboratively. - Preferred: we could put under Skills as a
Preferred:
then list. But we have duplication of degree. Let's think: The Required list includes degree, skills, citizenship. So we could put all required items under Requirements. Then we could have Qualifications for preferred? But Qualifications usually refers to qualifications like degree, certifications. Preferred could be extra qualifications. However we have no heading for Preferred. We could put preferred under Qualifications as extra bullet points with a note. But we must not invent sections with filler. If we put Qualifications heading, we need to have substantive content. We could put the