DDC/BAS Controls Technician I - New Construction

We need to output HTML fragment with sections: h3 headings for sections present with real content. Must not repeat job title. Must not include Job ID etc. Must include Pay and Benefits if present. Must include Responsibilities (Essential Duties and Responsibilities). Must include Qualifications (maybe combine Qualifications and Preferred Qualifications). Must include maybe Physical Requirements? Not required heading list but we can include if content present. The instruction: Use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Only include sections when posting has real specific content. So we need to decide which sections to include. From posting: - Pay Range: "$33.00 - $40.18 per hour, plus potential profit share." So we can have

Pay

with that info in

. - Benefits: list of benefits. So

Benefits

with

• each. - Essential Duties and Responsibilities: list of duties. So

  Responsibilities

  with
  . - Qualifications: list of qualifications (required). Also Preferred Qualifications. Could combine into one

  Qualifications

  with both required and preferred maybe separate
  or separate headings? The instruction says use h3 for section headings; we could have Qualifications and maybe Preferred Qualifications as subheadings? But they said only use h3 for section headings; we could still have multiple h3 sections: Qualifications and Preferred Qualifications. However they said prefer a few substantive sections over many thin ones. Might combine required and preferred into one Qualifications section with two lists: Required Qualifications and Preferred Qualifications as headings inside? But we cannot use other headings besides h3? Not prohibited but better to keep simple: one Qualifications section with both required and preferred as separate
  maybe with a note. - Physical Requirements, Environment, Hazards, Competencies: Could be included as sections? The instruction list didn't include those as examples but we could still include if content present. However they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are typical but not exclusive; we could still add others if needed. However they also said "Prefer a few substantive sections over many thin ones." So maybe we should include only the main ones: Responsibilities, Qualifications, Benefits, Pay. Possibly also "About the role" from Position Purpose? There's a Position Purpose paragraph: "As a LONG Controls Technician, you will support customers..." That could be considered About the role. So we could include an

  About the role

  with that paragraph. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive information. Must not invent or summarize away detail. Must remove boilerplate: EEO, legal, etc. Must remove duplicated lines, navigation, cookie, etc. Must remove application instructions (none). Must remove "Key Word Search" etc. Must remove "Physical Requirements", "Environment", "Hazards", "Competencies" maybe? But they are substantive; however we might omit to keep few sections. But we must preserve ALL substantive information; we cannot drop info. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot drop Physical Requirements etc. So we need to include them somehow. However we can combine them into a section like "Working Conditions" or similar. But the instruction only gave examples; we can still create other h3 headings if needed. It didn't forbid other headings. So we should include all substantive info: Position Purpose, Essential Duties and Responsibilities, Qualifications (required and preferred), Preferred Qualifications maybe separate, Physical Requirements, Environment, Hazards, Competencies, Benefits, Pay. Also maybe "About the company" description at start? The first lines: "LONG Building Technologies LONG Building Technologies, Inc. is an Equal Opportunity Employer." That's boilerplate EEO; we should remove. The description after that includes job title and location etc. Location we might include as metadata? They said do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. Location is minor metadata; we could include in a short

  maybe under About the role? Or we could drop it? They said fold minor metadata into a short

  or drop it. So we could include location in a

  maybe after About the role. But we must preserve all substantive information; location is substantive? It's location of job; maybe considered metadata but still substantive. We'll include it in a short

  . We also need to include Category? "Category Technician - Building Automation". That's also metadata; could be included similarly. We must not repeat job title as heading. The job title appears: "DDC/BAS Controls Technician I - New Construction". We should not use that as heading. We'll not. Now produce HTML fragment. Structure:

  Location: Littleton, CO, United States

  Category: Technician - Building Automation

  Then

  About the role

  with the Position Purpose paragraph. Then

  Responsibilities

  with
  list of duties. Then

  Qualifications

  maybe with two subsections: Required Qualifications and Preferred Qualifications. Could use

  but not allowed? Only h3 for section headings; but we could still use inside. Safer to use

  Qualifications

  and then within have

  Required:

  ... then

  Preferred:

  ... Then

  Physical Requirements

  with
  maybe. Then

  Work Environment

  with
  for Environment and Hazards? Could combine. Then

  Competencies

  with
  . Then

  Benefits

  with
  . Then

  Pay

  with

  . We must not include boilerplate like EEO, equal opportunity, etc. Also remove "Key Word Search" etc. Now extract details. From posting: **Position Purpose** paragraph: "As a LONG Controls Technician, you will support customers by troubleshooting and programming temperature control systems based on project specifications. Using your expertise in the commercial HVAC industry, you will perform installation, warranty, and emergency procedures." That's the only prose under Position Purpose. **Essential Duties and Responsibilities** list: - Program databases for all supported systems to meet specified sequences of operation and equipment manufacturers recommendations, in accordance with LONG standards and contract documents. - Perform calibration and check-out of control systems and ensure that specified sequence of operations and commissioning obligations are met. - Create control graphics for projects and provide the labor and expertise for the delivery of graphical user interfaces in accordance with LONG standards and contract documents. - Instruct customer's personnel on operation and maintenance of temperature control systems and energy conversation routines. - Provide information to update drawings and keep records of equipment for as-built documentation (submit all redlined drafting to application engineers) - Advises service sales manager of additional sales potential and solicits service contracts while performing start-up, commissioning, and owner training tasks. - Other duties assigned. Also earlier: "Required To perform this job successfully, you must be able to perform each essential duty satisfactorily. Other duties or tasks assigned as required. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." That's boilerplate; we can include maybe as part of responsibilities? It's generic; but we should preserve substantive info; it's not really a duty. Might drop as boilerplate? It's not a duty but it's about essential functions. Might be considered boilerplate; but it's not EEO. It's about essential functions. Might keep as a p? However it's generic; but we can include as a short p before the list. **Qualifications** (required): - 1 year temperature control system start-up, checkout, and service experience - Ability to legally drive a company vehicle. - High aptitude for computer systems or mechanical systems - Knowledge of HVAC, control systems, building automation, electrical systems, energy management, engineering, installation, and construction procedures - Programming and troubleshooting skills with KMC, Distech, Tridium/Honeywell, and other equivalent systems. - Strong analytical skills in solving software and integration challenges. - Ability to interpret mechanical plans and specifications. - Ability to handle multiple tasks simultaneously and willingness to accept responsibility and accountability. - Strong customer service and analytical skills. **Preferred Qualifications**: - Completion up to level 1 of the ASP Program - Certifications in KMC, Distech, Tridium/Honeywell, and other equivalent systems - Computer programming or electronic technical degree - No candidate will meet every single desired qualification. If your experience looks a little different from what we have identified and you think you can bring value to the role, we would love to learn more about you! That last sentence is encouragement; we can keep as a p. **Physical Requirements**: - This work may involve standing for extended periods, climbing ladders or scaffolds, and working in tight spaces. - This position may require lifting to 50 lbs. from floor to countertop and countertop to floor. - Thi position requires climbing ladders and the ability to function at heights. (typo: "Thi"). **Environment**: - Inside and outside work environments - Consistent in state travel to jobsites **Hazards**: - High precarious places - General construction worksite hazards **Competencies**: - To perform this position successfully, an individual must display the following leadership qualities and/or be able to work within the following supervisory relationships. - LONG expects its employees to understand and meet customer needs, collaborate effectively with colleagues, manage potential hazards and risks, and engage with and contribute to the community. - These values are part of our core values used as performance metrics and are integral to company culture. - LONG Building Technologies, Inc. is a leading provider of HVAC equipment and contracting services, serving commercial clients. With a strong commitment to quality and customer satisfaction, we pride ourselves on delivering innovative solutions and exceptional service. Our company operates in an environment where unions play a significant role, ensuring fair labor practices and adherence to industry standards. At LONG Building Technologies, we don't just accept difference - we celebrate it, and we thrive on it for the benefit of our co-workers, our customers, and our company. We are proud to be an equal opportunity employer. We are committed to equal employment opportunity regardless of race, color, ancestry, religion, sex, national origin, sexual orientation, age, citizenship, marital status, disability, or Veteran status. That last part is EEO boilerplate; we should remove it. So we need to strip EEO statements from Competencies section. The Competencies paragraph includes EEO at the end; we should remove that. Keep the rest: understanding customer needs, collaborate, manage hazards, engage community, core values, leading provider, commitment to quality, innovative solutions, exceptional service, union environment, celebrate difference. We'll keep those. **Benefits** list: - Medical, Dental and Vision Insurance - Voluntary Life Insurance - Voluntary Accident and Critical Care Insurance - Basic Life - Short-Term and Long-Term Disability - Employee Assistance Program (EAP) - 401(k) with Employer Matching contributions - Profit Sharing/Bonus/ Commission Program as applicable - Paid Time Off - Paid Community Service Day - 8 Paid holidays - Tuition Reimbursement - Pet Insurance - Legal and IDShield **Pay Range**: "$33.00 - $40