Lead Access Control Technician
Preferred Technologies, LLC · Austin, Texas Metropolitan Area · 3 wk ago
On-siteEngineeringFull-time
We need to produce HTML fragment with sections: About the role? The posting includes "Why Pref-Tech?" intro, then Position Overview, Key Responsibilities, Required Qualifications, Preferred Qualifications, Benefits, Work Hours & Travel, Physical Requirements, Core Values, Purpose statement, EEO etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should drop EEO statement, ADA accommodation, etc. Also drop duplicated lines like "Employment is contingent upon successful completion of background investigation and pre-employment drug screen." etc.
We need to use for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content.
We have content: Position Overview (could be "About the role"). Key Responsibilities (Responsibilities). Required Qualifications (Requirements/Qualifications). Preferred Qualifications (maybe Skills). Benefits (Benefits). Work Hours & Travel (Schedule). Physical Requirements (maybe could be part of Requirements? but we can make a separate section? The instruction says use headings for those specific names; we can add Physical Requirements as a heading? Not listed but we could maybe include under Requirements. Better to keep to listed headings. However we can create a section for "Physical Requirements" if we think it's substantive, but the instruction says use
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content.
We have content: Position Overview (could be "About the role"). Key Responsibilities (Responsibilities). Required Qualifications (Requirements/Qualifications). Preferred Qualifications (maybe Skills). Benefits (Benefits). Work Hours & Travel (Schedule). Physical Requirements (maybe could be part of Requirements? but we can make a separate section? The instruction says use headings for those specific names; we can add Physical Requirements as a heading? Not listed but we could maybe include under Requirements. Better to keep to listed headings. However we can create a section for "Physical Requirements" if we think it's substantive, but the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, not exclusive? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. But we could also add other headings if needed? Safer to stick to those.
We need to map content:
- About the role: Position Overview paragraph.
- Responsibilities: Key Responsibilities list.
- Requirements: Required Qualifications list.
- Qualifications: maybe Preferred Qualifications? Or Skills? Could treat Preferred Qualifications as Skills.
- Benefits: Benefits list.
- Schedule: Work Hours & Travel (includes schedule and travel). Could also include Physical Requirements? But schedule heading is for work hours & travel.
We should not include Pay section because no specific salary numbers.
We should not include Schedule if not specific? Work Hours & Travel includes schedule info: "Must be willing to work days and nights. There is no set schedule for field personnel, as work schedules vary depending on client needs. Travel is 10-20% to Pref-Tech offices, job sites, and conferences." That's specific enough.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep the details from each section.
We must not repeat job title as heading.
We must not put Job ID/requisition numbers as headings (none present).
We must remove boilerplate: EEO statement, ADA accommodation, duplicated lines, etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content:
Why Pref-Tech? Voted "Top Workplaces" by Austin American Statesman, 3 years in a row! We aim to make “family” a core reason we attract incredible people, retain them, and collectively deliver unequaled quality and service to customers. If your heart and mind are pushing you to join a team who deeply desires to be the best in the world, has a long-game approach to business, prides itself on doing exceptional work, celebrates service to others, and is willing to invest in you, you should consider Pref-Tech.
That's introductory marketing fluff; could be part of About the role? Might be considered "About the company". But we can include it in About the role section as prose.
Position Overview: A Security System Lead Technician at Pref-Tech will be responsible for leading a small team of security and/or cabling technicians to complete access control, video surveillance, intrusion detection, and related projects safely, within time constraints, at or above quality standards, and within budget. The Lead Technician's duties include, but are not limited to, assisting Project Managers with planning daily tasks, managing materials and equipment, executing installations, troubleshooting, and resolving issues, communicating with customers, reporting progress, conducting quality control inspections, and testing systems.
Key Responsibilities: list bullet points (starting with "Plan daily tasks...").
Required Qualifications: list bullet points.
Preferred Qualifications: list bullet points.
Benefits: list bullet points.
Work Hours & Travel: paragraph.
Physical Requirements: list bullet points.
Core Values: list bullet points (maybe we could include under About the role? But it's substantive; we could add a section "Core Values" but not in the list of headings. However we could incorporate into About the role as prose? But better to keep as a section maybe "Core Values". The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "e.g." So we could add Core Values as a heading if we want. However to be safe, we could incorporate Core Values into About the role or maybe as a separate section named "Core Values". Since it's not in the examples, risk of being considered unnecessary. But the instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the expected headings; we should stick to them. So we should not create a Core Values heading. Instead we could incorporate core values into About the role or maybe as a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. But we could also add other headings if needed? Safer to stick to those.
We need to map content:
- About the role: Position Overview paragraph.
- Responsibilities: Key Responsibilities list.
- Requirements: Required Qualifications list.
- Qualifications: maybe Preferred Qualifications? Or Skills? Could treat Preferred Qualifications as Skills.
- Benefits: Benefits list.
- Schedule: Work Hours & Travel (includes schedule and travel). Could also include Physical Requirements? But schedule heading is for work hours & travel.
We should not include Pay section because no specific salary numbers.
We should not include Schedule if not specific? Work Hours & Travel includes schedule info: "Must be willing to work days and nights. There is no set schedule for field personnel, as work schedules vary depending on client needs. Travel is 10-20% to Pref-Tech offices, job sites, and conferences." That's specific enough.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep the details from each section.
We must not repeat job title as heading.
We must not put Job ID/requisition numbers as headings (none present).
We must remove boilerplate: EEO statement, ADA accommodation, duplicated lines, etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content:
Why Pref-Tech? Voted "Top Workplaces" by Austin American Statesman, 3 years in a row! We aim to make “family” a core reason we attract incredible people, retain them, and collectively deliver unequaled quality and service to customers. If your heart and mind are pushing you to join a team who deeply desires to be the best in the world, has a long-game approach to business, prides itself on doing exceptional work, celebrates service to others, and is willing to invest in you, you should consider Pref-Tech.
That's introductory marketing fluff; could be part of About the role? Might be considered "About the company". But we can include it in About the role section as prose.
Position Overview: A Security System Lead Technician at Pref-Tech will be responsible for leading a small team of security and/or cabling technicians to complete access control, video surveillance, intrusion detection, and related projects safely, within time constraints, at or above quality standards, and within budget. The Lead Technician's duties include, but are not limited to, assisting Project Managers with planning daily tasks, managing materials and equipment, executing installations, troubleshooting, and resolving issues, communicating with customers, reporting progress, conducting quality control inspections, and testing systems.
Key Responsibilities: list bullet points (starting with "Plan daily tasks...").
Required Qualifications: list bullet points.
Preferred Qualifications: list bullet points.
Benefits: list bullet points.
Work Hours & Travel: paragraph.
Physical Requirements: list bullet points.
Core Values: list bullet points (maybe we could include under About the role? But it's substantive; we could add a section "Core Values" but not in the list of headings. However we could incorporate into About the role as prose? But better to keep as a section maybe "Core Values". The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "e.g." So we could add Core Values as a heading if we want. However to be safe, we could incorporate Core Values into About the role or maybe as a separate section named "Core Values". Since it's not in the examples, risk of being considered unnecessary. But the instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the expected headings; we should stick to them. So we should not create a Core Values heading. Instead we could incorporate core values into About the role or maybe as a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the expected headings; we should stick to them. So we should not create a Core Values heading. Instead we could incorporate core values into About the role or maybe as a
within About the role. Similarly Purpose statement could be included in About the role. We need to preserve all substantive information; we can embed them as paragraphs. Thus final HTML:
About the role
Why Pref-Tech? Voted "Top Workplaces" by Austin American Statesman, 3 years in a row! We aim to make “family” a core reason we attract incredible people, retain them, and collectively deliver unequaled quality and service to customers. If your heart and mind are pushing you to join a team who deeply desires to be the best in the world, has a long-game approach to business, prides itself on doing exceptional work, celebrates service to others, and is willing to invest in you, you should consider Pref-Tech. A Security System Lead Technician at Pref-Tech will be responsible for leading a small team of security and/or cabling technicians to complete access control, video surveillance, intrusion detection, and related projects safely, within time constraints, at or above quality standards, and within budget. The Lead Technician's duties include, but are not limited to, assisting Project Managers with planning daily tasks, managing materials and equipment, executing installations, troubleshooting, and resolving issues, communicating with customers, reporting progress, conducting quality control inspections, and testing systems. You must also fulfill our purpose statement with all decisions and actions: “Within a family culture, nurture and inspire our employees to creatively resolve customer pain using the highest level of craftsmanship and service.” Our core values are Professionalism, Grit, Right, Intelligent Thought, and Trusted Advisors.
Responsibilities
- Plan daily tasks with the Project Manager and/or Superintendent.
- Conduct safety meetings with team.
- Lead, coach, train, manage, and mentor technician team.
- Install cabling, mount equipment, install card readers, door contacts, mag locks, electrified strikes, and integrated systems.
- Troubleshoot cabling, card readers, door contacts, mag locks, electrified strikes, cameras, PLC's, intrusion detection equipment, and integrated systems.
- Maintain a mastery of low voltage systems, relays, principals of normally closed/normally open, series and parallel wiring.
- Maintain a general understanding of Ethernet networking.
- Master understanding of using multi-meter to test for voltage, continuity, amperage, and resistance.
- Possess mechanical and computer skills.
- Operate hand tools and equipment necessary to perform all associated tasks, to include lifts.
- Document and report progress in a timely manner to Project Managers and customers.
- Communicate effectively in written and verbal for with internal staff and customers.
- Mastery in reading and understanding drawings and equipment schematics is required.
- Proven ability to use resources available to them to troubleshoot and resolve issues encountered on projects.
Requirements
- High School Diploma or GED Equivalent.
- Must be at least 18 years of age.
- Must possess a valid TX driver’s license, successfully pass an MVR (Motor Vehicle Record) check, and maintain a clean driving record as a condition of continued use of a company vehicle.
- At least 5 years of relevant security experience.
- At least 2 years of relevant leadership experience.
- Willingness to take on new challenges and build on current skills.
- Exceptional analytical and conceptual thinking.
- Currently licensed or must have the ability to immediately obtain TXDPS Security License.
Skills
- Proficiently use MS Word, MS Excel, MS Project, MS Visio, and Adobe.
- Understand the basics of IP networking and IP-based equipment.
- Low Voltage Industry certifications from ASIS, BICSI, ESA etc.
- Access Control Manufacture certifications – see required familiarity list above.
Benefits
- Competitive Salary
- Company Vehicle
- Inclusion in Operational Incentive Program, which shares excess profits as bonuses
- 401K Safe Harbor Plan with matching dollar-for-dollar up to 4% of annual gross salary (Traditional and Roth options available)
- Health, Dental, and other elective insurances
- Travel and Night Work Incentives
- World-class training and professional development
Schedule
Must be willing to work days and nights. There is no set schedule for field personnel, as work schedules vary depending on client needs. Travel is 10-20% to Pref-Tech offices, job sites, and conferences.
We should also include Physical Requirements? Not covered. Could be omitted? But we must preserve ALL substantive information. Physical Requirements is substantive. Where to put? Could be under Requirements or maybe a separate section but not in list. Could add as aunder Requirements or maybe under About the role. Since we have Requirements heading for qualifications, we could add Physical Requirements as a sub-list within Requirements? But the instruction says use
- for any list of duties/requirements/benefits. So we could add a list under Requirements for physical requirements. However Requirements already used for qualifications; we could split into two sub-sections? Not allowed because we cannot create new headings not in list. But we could embed physical requirements as part of Requirements
- as additional items. That would mix qualifications with physical requirements but still a list of requirements. That's acceptable.
Similarly, we could embed core values and purpose statement into About the role paragraph.
Thus final HTML includes all info.
Check for duplicated lines: we removed EEO, ADA, duplicate lines about background investigation etc.
Check for any boilerplate: removed "EEO Statement", "ADA Accommodation Statement", "Employment is contingent upon successful completion of background investigation and pre-employment drug screen." etc.
Check for any mention of "Job ID" etc none.