Installation/Alarm Service
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Need to extract content from description. Let's parse the job posting. Description: "Install, configure, support, monitor, test, optimize and troubleshoot products and issues pertaining to deployment, integration and implementation of new equipment and software at client locations Be a team player demonstrating continual growth, professionalism and independence when working with clients and co-workers. Assist with providing high-level assessments and proposals of client needs, costs, and benefits/risks to develop and deliver total security solutions. Deliver projects and service calls on time and within budget A Broad-based technology understanding and competence in at least two security industry related areas is required. The ability to lead teams, delegate tasks and responsibilities among team members, initiate feedback, proactively build rapport, respond immediately if possible and escalate if necessary while maintaining a professional image to the client is a must. Demonstrate the ability to creatively solve client problems. A basic understanding of business principles, the ability to accommodate different personality types and make good decisions based on a given situation. Solid project management ant time management skills with the ability to execute subtasks in the projects while acting as a coach and mentor to others. Knowledge of the following: Access Control experience S2 Avigilon Galaxy Paxton HID Keri Brivo Skills Install, Security, Cctv, Programming Top Skills Details Install,Security,Cctv,Programming Additional Skills & Qualifications candidates should possess a minimum 3+ years of installation and service-related experience within the security industry. This includes but is not limited to video surveillance, access control, intrusion and fire alarms, perimeter security and traffic control as well as door hardware and locksmithing. Strong mechanical skills as well as low voltage wiring experience and general contracting knowledge are a significant advantage. Basic computer skills are required including but not limited to Microsoft Office applications. MS Word, Excel and Outlook are required, Visio and/or CAD drawing and design are a plus. Proven work experience interacting with clients is preferred. Bachelor’s degree or equivalent field experience is required. A valid PA driver’s license is mandatory. Experience Level Intermediate Level Job Type & Location This is a Contract position based out of Pittsburgh, PA. Pay And Benefits The pay range for this position is $25.00 - $33.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: Medical, dental & vision Critical Illness, Accident, and Hospital 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available Life Insurance (Voluntary Life & AD&D for the employee and dependents) Short and long-term disability Health Spending Account (HSA) Transportation benefits Employee Assistance Program Time Off/Leave (PTO, Vacation or Sick Leave) Workplace Type This is a fully onsite position in Pittsburgh,PA. Application Deadline This position is anticipated to close on Oct 5, 2026. About TEKsystems ..." We need to remove boilerplate: About TEKsystems, equal opportunity, etc. Also remove application instructions (deadline maybe? It's metadata but we can include as short p? The instruction says: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include location, job type, maybe deadline as a short p. But we should not create sections for them unless they have real content. Probably we can include a short paragraph with "Job Type & Location: Contract position based out of Pittsburgh, PA. Application Deadline: Oct 5, 2026." That is minor metadata. Now we need sections: About the role (maybe description of role), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From description we have responsibilities: install, configure, support, monitor, test, optimize, troubleshoot products and issues pertaining to deployment, integration and implementation of new equipment and software at client locations; be a team player; assist with providing high-level assessments and proposals; deliver projects and service calls on time and within budget; lead teams, delegate tasks, etc.; demonstrate ability to creatively solve client problems; basic understanding of business principles; solid project management and time management skills; act as coach and mentor. That's responsibilities. Requirements: maybe "Broad-based technology understanding and competence in at least two security industry related areas is required." Also "minimum 3+ years of installation and service-related experience within the security industry." Also "Bachelor’s degree or equivalent field experience is required." Also "Valid PA driver’s license mandatory." Also "Strong mechanical skills as well as low voltage wiring experience and general contracting knowledge are a significant advantage." Also "Basic computer skills required including MS Word, Excel, Outlook; Visio/CAD a plus." Also "Proven work experience interacting with clients is preferred." Qualifications: maybe overlapping with requirements. Could combine. Skills: list of specific technologies: Access Control experience S2 Avigilon Galaxy Paxton HID Keri Brivo; Install, Security, Cctv, Programming; also video surveillance, access control, intrusion and fire alarms, perimeter security and traffic control, door hardware and locksmithing. Pay: given: $25.00 - $33.00/hr. Benefits: listed: Medical, dental & vision; Critical Illness, Accident, and Hospital; 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available; Life Insurance (Voluntary Life & AD&D for the employee and dependents); Short and long-term disability; Health Spending Account (HSA); Transportation benefits; Employee Assistance Program; Time Off/Leave (PTO, Vacation or Sick Leave). Schedule: Not explicitly given; maybe "Workplace Type This is a fully onsite position in Pittsburgh,PA." That's not schedule. No schedule info like full-time, part-time, shift. So we should NOT create a Schedule section because no specific content. Thus sections: About the role (maybe a brief summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to avoid repeating job title as heading. Not needed. We need to use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific tech names, etc.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove boilerplate: About TEKsystems sections, EEO, etc.
We need to output only HTML fragment.
Let's craft.
First, maybe a short paragraph for job type/location/deadline as minor metadata: could be a
before sections.
But instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short p for job type, location, deadline.
Let's do:
Job Type: Contract. Location: Pittsburgh, PA. Application Deadline: Oct 5, 2026.
But we should avoid using ? Not prohibited. Could just plain text.
Now sections.
About the role: maybe a brief summary: "Install, configure, support, monitor, test, optimize and troubleshoot products and issues pertaining to deployment, integration and implementation of new equipment and software at client locations. Be a team player demonstrating continual growth, professionalism and independence when working with clients and co-workers. Assist with providing high-level assessments and proposals of client needs, costs, and benefits/risks to develop and deliver total security solutions. Deliver projects and service calls on time and within budget."
That's basically responsibilities but could be About the role. However we also have Responsibilities section. To avoid duplication, we could treat About the role as a short overview, and Responsibilities as detailed list.
But we must not repeat same content verbatim? It's okay if overlapping but we should preserve all info. Might be okay to have About the role as a paragraph summarizing role, and Responsibilities as a list of duties.
Let's extract responsibilities list:
- Install, configure, support, monitor, test, optimize and troubleshoot products and issues pertaining to deployment, integration and implementation of new equipment and software at client locations
- Be a team player demonstrating continual growth, professionalism and independence when working with clients and co-workers
- Assist with providing high-level assessments and proposals of client needs, costs, and benefits/risks to develop and deliver total security solutions
- Deliver projects and service calls on time and within budget
- Lead teams, delegate tasks and responsibilities among team members, initiate feedback, proactively build rapport, respond immediately if possible and escalate if necessary while maintaining a professional image to the client
- Demonstrate the ability to creatively solve client problems
- A basic understanding of business principles, the ability to accommodate different personality types and make good decisions based on a given situation
- Solid project management and time management skills with the ability to execute subtasks in the projects while acting as a coach and mentor to others
Note: there is a typo "ant" but we keep as is? It says "Solid project management ant time management skills". We'll keep exactly as in source? Probably we should preserve but maybe fix? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't say we must keep typos exactly; but we should not change meaning. Changing "ant" to "and" is a minor correction but could be considered altering. Safer to keep as is? It's obviously a typo; but we could keep "ant". I'd keep as is to preserve original.
Now Requirements: list:
- Broad-based technology understanding and competence in at least two security industry related areas is required
- Minimum 3+ years of installation and service-related experience within the security industry (includes video surveillance, access control, intrusion and fire alarms, perimeter security and traffic control, door hardware and locksmithing)
- Bachelor’s degree or equivalent field experience is required
- Valid PA driver’s license is mandatory
- Strong mechanical skills as well as low voltage wiring experience and general contracting knowledge are a significant advantage
- Basic computer skills required including Microsoft Office applications (MS Word, Excel and Outlook required; Visio and/or CAD drawing and design are a plus)
- Proven work experience interacting with clients is preferred
Qualifications: maybe overlapping; but we could treat qualifications as education/experience etc. But we already have those in Requirements. To avoid duplication, maybe we combine Requirements and Qualifications into one section? But headings need to be used only if real content. We could have Requirements (includes education, experience, licensure) and Qualifications (maybe skills?). However the posting lumps them.
Better to have:
- Requirements: experience, education, licensure, etc.
- Qualifications: maybe "Broad-based technology understanding and competence in at least two security industry related areas is required." Actually that is a requirement.
But we can just have one section "Requirements" covering all mandatory items, and another "Skills" for specific tech skills.
Let's decide:
Section "Requirements": list mandatory items: 3+ years experience, Bachelor's degree or equivalent, PA driver's license, broad-based tech understanding in at least two security areas, basic computer skills (MS Office), etc. Also maybe "Strong mechanical skills ... are a significant advantage" (that's advantage not requirement). We'll keep as requirement? It says advantage, not required. Could be in Qualifications.
Qualifications: maybe "Strong mechanical skills as well as low voltage wiring experience and general contracting knowledge are a significant advantage." Also "Proven work experience interacting with clients is preferred
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific tech names, etc. We need to avoid filler like "commensurate with experience". Not present. We need to remove boilerplate: About TEKsystems sections, EEO, etc. We need to output only HTML fragment. Let's craft. First, maybe a short paragraph for job type/location/deadline as minor metadata: could be a
before sections. But instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short p for job type, location, deadline. Let's do:
Job Type: Contract. Location: Pittsburgh, PA. Application Deadline: Oct 5, 2026.
But we should avoid using ? Not prohibited. Could just plain text. Now sections. About the role: maybe a brief summary: "Install, configure, support, monitor, test, optimize and troubleshoot products and issues pertaining to deployment, integration and implementation of new equipment and software at client locations. Be a team player demonstrating continual growth, professionalism and independence when working with clients and co-workers. Assist with providing high-level assessments and proposals of client needs, costs, and benefits/risks to develop and deliver total security solutions. Deliver projects and service calls on time and within budget." That's basically responsibilities but could be About the role. However we also have Responsibilities section. To avoid duplication, we could treat About the role as a short overview, and Responsibilities as detailed list. But we must not repeat same content verbatim? It's okay if overlapping but we should preserve all info. Might be okay to have About the role as a paragraph summarizing role, and Responsibilities as a list of duties. Let's extract responsibilities list: - Install, configure, support, monitor, test, optimize and troubleshoot products and issues pertaining to deployment, integration and implementation of new equipment and software at client locations - Be a team player demonstrating continual growth, professionalism and independence when working with clients and co-workers - Assist with providing high-level assessments and proposals of client needs, costs, and benefits/risks to develop and deliver total security solutions - Deliver projects and service calls on time and within budget - Lead teams, delegate tasks and responsibilities among team members, initiate feedback, proactively build rapport, respond immediately if possible and escalate if necessary while maintaining a professional image to the client - Demonstrate the ability to creatively solve client problems - A basic understanding of business principles, the ability to accommodate different personality types and make good decisions based on a given situation - Solid project management and time management skills with the ability to execute subtasks in the projects while acting as a coach and mentor to others Note: there is a typo "ant" but we keep as is? It says "Solid project management ant time management skills". We'll keep exactly as in source? Probably we should preserve but maybe fix? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't say we must keep typos exactly; but we should not change meaning. Changing "ant" to "and" is a minor correction but could be considered altering. Safer to keep as is? It's obviously a typo; but we could keep "ant". I'd keep as is to preserve original. Now Requirements: list: - Broad-based technology understanding and competence in at least two security industry related areas is required - Minimum 3+ years of installation and service-related experience within the security industry (includes video surveillance, access control, intrusion and fire alarms, perimeter security and traffic control, door hardware and locksmithing) - Bachelor’s degree or equivalent field experience is required - Valid PA driver’s license is mandatory - Strong mechanical skills as well as low voltage wiring experience and general contracting knowledge are a significant advantage - Basic computer skills required including Microsoft Office applications (MS Word, Excel and Outlook required; Visio and/or CAD drawing and design are a plus) - Proven work experience interacting with clients is preferred Qualifications: maybe overlapping; but we could treat qualifications as education/experience etc. But we already have those in Requirements. To avoid duplication, maybe we combine Requirements and Qualifications into one section? But headings need to be used only if real content. We could have Requirements (includes education, experience, licensure) and Qualifications (maybe skills?). However the posting lumps them. Better to have: - Requirements: experience, education, licensure, etc. - Qualifications: maybe "Broad-based technology understanding and competence in at least two security industry related areas is required." Actually that is a requirement. But we can just have one section "Requirements" covering all mandatory items, and another "Skills" for specific tech skills. Let's decide: Section "Requirements": list mandatory items: 3+ years experience, Bachelor's degree or equivalent, PA driver's license, broad-based tech understanding in at least two security areas, basic computer skills (MS Office), etc. Also maybe "Strong mechanical skills ... are a significant advantage" (that's advantage not requirement). We'll keep as requirement? It says advantage, not required. Could be in Qualifications. Qualifications: maybe "Strong mechanical skills as well as low voltage wiring experience and general contracting knowledge are a significant advantage." Also "Proven work experience interacting with clients is preferred