HVAC Sales Representative

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Content: - About the company: description of FirstCall Mechanical, C2H partnership, etc. That could be "About the role"? Actually "About the role" maybe about the position. But we have "Position Overview" and "WHO IS FIRSTCALL MECHANICAL?" which is about company. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (maybe combine company overview and position overview), Responsibilities, Requirements (maybe qualifications), Qualifications (maybe separate?), Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: - Benefits Overview: list of benefits: Competitive Weekly Pay, Comprehensive Healthcare Coverage..., Financial Resources..., Time-Off & Holidays..., Career Growth & Development..., Generous Referral Bonus..., Role-Specific Perks... - Pay: "Competitive Weekly Pay" is mentioned under Benefits Overview. Also maybe pay specifics not given beyond "Competitive Weekly Pay". Since we should not create Pay section unless posting actually states them. It does state "Competitive Weekly Pay". That's a pay statement. So we can include Pay section with that detail. - Schedule: Not mentioned. No schedule info. So we should not include Schedule. - About the role: Could include "Position Overview" and "WHO IS FIRSTCALL MECHANICAL?" maybe as About the role. Provide description of company and role purpose. - Responsibilities: List under "Job Responsibilities". Many bullet-like sentences separated by semicolons. We need to convert to

• . Must preserve all substantive info. We'll split each responsibility into separate li. - Requirements: There's a "Qualifications" section with bullet list: 2-3 years experience..., Retrofit and Service sales experience..., Aptitude for technical knowledge..., Excellent presentation skills..., Experience selling service and maintenance..., Exposure to sales methodologies..., Knowledge of Building HVAC Systems. Also there is "BEHAVIORAL PROFILE" with Language Skills, Mathematical Skills, Reasoning Ability, Mental stamina..., Environmental Requirements, Physical Demands, Specific vision abilities. Those could be considered Skills or Requirements. The instruction: Use headings for Skills, Requirements, Qualifications. We need to decide mapping. We have Qualifications section already. Could treat that as Qualifications. Then Skills could be language, math, reasoning, mental stamina, etc. Requirements could be experience etc. But we have overlapping. Better: Use Qualifications for the list under "QUALIFICATIONS". Use Skills for the behavioral profile (language, math, reasoning, mental stamina). Use Requirements for the experience etc? But we already used Qualifications for experience list. Hmm. Alternatively, we could combine experience and technical qualifications into Requirements, and keep Qualifications for education/certifications (none). But there is no separate education. Given the instruction: "Prefer a few substantive sections over many thin ones." So we should not create many sections with little content. We have substantive content for About the role, Responsibilities, Qualifications (experience/skills), Benefits, Pay. Maybe we can combine Skills into Qualifications or Requirements. We could have sections: About the role, Responsibilities, Qualifications (includes experience, technical knowledge, behavioral profile), Benefits, Pay. That seems reasonable: Qualifications includes all the qualification/skill details. Thus we will output:

  About the role

  ... company description and position overview ...

  Responsibilities

  • ...
  ...

  Qualifications

  • ...
  ...
  (including experience, technical, behavioral, environmental, physical, vision)

  Benefits

  • ...
  ...

  Pay

  Competitive Weekly Pay

  We must not include Schedule. Now we need to extract substantive info. About the role: combine "WHO IS FIRSTCALL MECHANICAL?" and "Position Overview". Let's craft a paragraph summarizing: FirstCall Mechanical is a commercial and industrial HVAC services provider in the Atlanta metro area, founded 2013, partnered with C2H in 2024, now part of FirstCall Mechanical, a leading provider of commercial and industrial HVAC, building controls, electrical, and plumbing services serving distribution centers, industrial plants, universities, airports, healthcare facilities, self-storage units, etc., with ~700 employees across multiple states, committed to building durable partnerships and expanding nationwide, focusing on employee growth and development. The HVAC Sales Representative role is critical to growth and profitability of the HVAC Service business, responsible for initiating, establishing, and building profitable service relationships with new customers. We must preserve all substantive information; not invent or summarize away detail. So we need to keep specifics: founding year, partnership year, employee count, states, facility types, commitment, etc. We'll include them. Responsibilities: list each responsibility from "Job Responsibilities". The text is a long sentence with semicolons separating items. Let's split: - Follows a disciplined and professional process to identify, target and qualify prospective new customers; takes advantage of market conditions and networks effectively to uncover new leads and contacts. - Contacts prospective customers and schedules appointments - Builds a referral network to identify new customers - Conducts sales calls crafted to identify key sources of problems and/or dissatisfaction confronting Facility Directors in operating and maintaining heating/cooling, ventilation and control system equipment - Develops a sense of urgency to resolve needs and positions FirstCall Mechanical as the supplier of choice - Proposes solutions to prospective customers needs through creative and innovative application of local branch service capabilities with a focus on selling renewable maintenance agreements with an emphasis on digital service offerings, sustainability, and decarbonization - Understands the customer's business and speaks their language - Reviews and finalizes proposals with prospects and secures their commitment to the FirstCall Mechanical solution - Conducts customer kick-off meetings, resolves customer issues, creates pull-through opportunities, maintains service agreements, extends service agreements and supports the collections process - Keeps management informed of progress and account status using BuildOps tool and other means - Develops and implements territory marketing plans consistent with the FirstCall Mechanical business strategy Also there is "Accountabilities" after responsibilities: "Continual learning and development in the body of knowledge through FirstCall Academy, to ensure we set the bar for skill level in the industry; Elite level of customer service, to ensure we continue to be the FirstCall our customers make for their HVAC & Refrigeration needs". These could be considered part of responsibilities or qualifications. They are under "Accountabilities". Might be considered responsibilities as well. We'll include them as responsibilities. Also "ORGANIZATIONAL ALIGNMENT This position reports to the local Branch Leader and has a responsibility to the entire service team and all of our customers." That's also responsibility. We'll include all. Qualifications: list from "QUALIFICATIONS" and then "BEHAVIORAL PROFILE", "Environmental Requirements", "Physical Demands", "Specific vision abilities". Also note "NOTE: This job description is not intended to be all-inclusive..." we can drop as boilerplate? It's a note but maybe not boilerplate; it's a disclaimer. Might be considered boilerplate? It's not cookie/navigation/legal/EEO etc. It's a note about job description. Might keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This note is not those. It's a generic note. Might keep but it's not substantive? It's a disclaimer. Could be considered boilerplate but not listed. Safer to keep? It says "NOTE: This job description is not intended to be all-inclusive. Employee may perform other related duties as negotiated to meet the ongoing needs of the organization." That's generic; could be considered boilerplate. I'd drop it as it's not substantive detail about the job. We'll omit. Now compile qualifications list: - 2-3 years of experience in previous progressive sales roles - Retrofit and Service sales experience, preferred - Aptitude for technical knowledge with high level of attention to detail - Excellent presentation skills complete with the ability to captivate in both individual and group communications. - Experience selling service and maintenance - Exposure to sales methodologies, standards, and disciplines. - Knowledge of Building HVAC Systems Behavioral profile: Language Skills: - Ability to read and comprehend simple instructions, short correspondence, and memos. - Ability to write correspondence. - Ability to effectively present information in one-on-one and small group situations to customers, clients, and other employees of the organization. Mathematical Skills: - Ability to add, subtract, multiply, and divide in all units of measure, using whole numbers, common fractions, and decimals. - Ability to compute rate, ratio, and percent and to draw and interpret graphs. Reasoning Ability: - Ability to apply common sense understanding to carry out instructions furnished in written, oral, or diagram form. - Ability to deal with problems involving several concrete variables in standardized situations. - Mental stamina for problem solving and prioritizing multiple tasks. Environmental Requirements: - Will be required to work in a field environment, multiple customer sites on a daily basis. Physical Demands: - While performing the duties of this job, the employee is regularly required to use hands to operate computer keyboard reach with hands and arms. - The employee frequently is required to stand, walk, and sit. - The employee is continually required to climb or balance and stoop, kneel, crouch, or crawl. - The employee must regularly lift and/or move up to 25 pounds, frequently lift and/or move up to 50 pounds. Specific vision abilities required by this job include close vision, distance vision, peripheral vision, depth perception, and ability to adjust focus. We'll put all these as li under Qualifications. Benefits: list from "Benefits Overview": - Competitive Weekly Pay - Comprehensive Healthcare Coverage - Medical, Dental, Vision, Free Telehealth + More - Financial Resources - 401(k) Retirement Savings Plan with a 5% match, Life Insurance, Short & Long-Term Disability - Time-Off & Holidays - Up to 4 weeks of Paid Off, 9 Paid Holidays + Veterans Day for Veterans - Career Growth & Development- Company-sponsored education and career advancement programs like the FirstCall Academy, the Learning & Education Assistance Program (LEAP), and the FirstCall Progression Program - Generous Referral Bonus of $2,500 per referral - Role-Specific Perks - Company vehicle or allowance, mobile phone or phone allowance, uniforms, and work boot and pants allowances Pay: we already have Competitive Weekly Pay listed under Benefits; but we also need a Pay section. Could just repeat that detail. But we must not duplicate content? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicating is okay if it's already present elsewhere? Might be considered duplication but not prohibited. However we could avoid duplication by not listing Competitive Weekly Pay under Benefits and instead put it under Pay only. But the Benefits Overview explicitly lists Competitive Weekly Pay as a benefit. If we remove it from Benefits, we would be omitting that detail from Benefits section. But we could keep it in Benefits and also have Pay section repeating it. That duplicates but preserves all info. Might be okay. However the instruction says "Prefer a few substantive sections over many thin ones." Duplication may create thin Pay section. But we need Pay section only if posting actually states them. It does state Competitive Weekly Pay. So we need a Pay section. We could keep the benefit list without that line, and put the pay detail