Security Project Specialist 1 (Data Centers) - San Antonio, TX

We need to output HTML fragment with sections only when there is real specific content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real content. Let's parse the posting. - Title: Security Project Technician (but we do not repeat as heading). - About the role: The first paragraph: "Convergint is looking for a full-time, enthusiastic, results driven and forward-thinking Security Project Technician to join our amazing culture. In this role, you will install, program, system start-up/check-out, certify, and customer train on assigned projects including small to large projects that vary in complexity. As a Security Project Technician, you are a part of a dynamic team that allows you to grow as Convergint grows." Also later there is "For information about how we use your personal information, please see our Colleague & Applicant Privacy Notice, available on convergint.com/careers." That's boilerplate, remove. - Who You Are: That's more about personal attributes; could be part of Requirements or Qualifications? Might be "Who You Are" but we only have allowed headings; we could map to "Requirements" or "Qualifications". The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide which sections to include based on content. We have content about responsibilities: many bullet-like sentences describing duties. We'll put those under

Responsibilities

with

• . We have content about what you need: skills, qualifications, experience, etc. That could go under Requirements and Qualifications and Skills. We need to decide best mapping. We have "Company Benefits" section with list of benefits. So Benefits heading. We have Pay? Not mentioned explicitly. No salary info. So we should NOT include Pay section. Schedule? Not mentioned explicitly (full-time). Could infer but not explicit; we should not include Schedule unless stated. The posting says "full-time". That's a schedule detail. It says "full-time". That is schedule info. Should we include Schedule? The rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. "full-time" is specific content about schedule. So we could include Schedule section with that detail. However they said "Prefer a few substantive sections over many thin ones." Might be okay to include Schedule with just that line. But we could also fold schedule into About the role or Responsibilities? Probably better to have Schedule section with "Full-time position." But we need to check if they consider that as schedule content. The posting says "Convergint is looking for a full-time, enthusiastic...". That's schedule. So we can include Schedule. Pay: Not mentioned, so omit. Now we need to decide on sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. Possibly also "Qualifications" vs "Requirements". The posting includes "What You’ll Need" which is requirements. Also "Education: High School/GED or equivalent experience Minimum Experience: 3-5 years relevant Preferred Experience: (but not required): Relevant field service Certifications: Product-specific certifications, Industry-specific certifications and/or licenses, DMP, PACOM, Hanwha, March Networks, Verint, or AMAG." That's qualifications/requirements. Also "Who You Are" includes personal attributes (integrity, commitment, etc.) which could be under Skills or Qualifications. We could combine. We need to avoid duplication. Let's extract substantive content. First, About the role: we have description of role and team. Second, Responsibilities: list of duties from "Installs, programs, test, repairs, and services a variety of non-routine systems..." etc. Many sentences. We'll extract each distinct duty as list items. Third, Requirements/Qualifications/Skills: We have "What You’ll Need" list: Exceptional customer focus and ability to work under pressure; ability to maintain awareness of and seek to meet the needs and wants of the customer without being prompted. Solid technical skills and experience fire alarm systems, and/or electronic security systems. Solid programming skills and proven ability to troubleshoot problems and look for solutions. To be a self-starter and work well with minimal supervision. Solid mechanical and electrical aptitude (e.g. works with a variety of hand and power tools such as drill, screwdriver, wire stripper, hacksaw, crimper) and ability to read blueprints and drawings; solid math skills (for some positions, this may include calculating area, velocity, resistance, voltage, etc.). Strong verbal, written and interpersonal communication skills. Solid organizational skills and the ability to handle multiple projects simultaneously. Advanced computer skills including familiarity with MS Office applications (Outlook, Word, Excel) and proficient in other relevant applications. A valid driver’s license with a clean driving record. Ability to travel locally to jobsites on a regular basis. Minimal overnight travel may be required. Also Education: High School/GED or equivalent experience. Minimum Experience: 3-5 years relevant. Preferred Experience: (but not required): Relevant field service. Certifications: Product-specific certifications, Industry-specific certifications and/or licenses, DMP, PACOM, Hanwha, March Networks, Verint, or AMAG. Also "Who You Are": passion for providing world-class service, person of integrity with commitment to growth, accountability and delivering results, want to join organization with positive culture that embraces equal opportunity, wants to grow with us and deliver results as an exceptional Security Technician. We could treat "Who You Are" as part of Skills or Qualifications (soft skills). We'll include under Skills maybe. We need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. But we might have overlapping content. To avoid too many sections, we could combine Requirements and Qualifications into one section (maybe Requirements). But the instruction gave examples; we can choose which to include. It says "Prefer a few substantive sections over many thin ones." So we should aim for maybe 4-5 sections. Potential sections: - About the role (intro) - Responsibilities (duties) - Requirements & Qualifications (combined) - Skills (maybe separate? but could be part of Requirements) - Benefits - Schedule But we need to avoid duplication. Let's think: Requirements & Qualifications can include education, experience, certifications, driver's license, travel. Skills can include technical skills, programming, mechanical aptitude, communication, organizational, computer skills, customer focus, etc. "Who You Are" could be under Skills as personal attributes. Thus we could have: - About the role - Responsibilities - Skills - Requirements (education, experience, certifications, license, travel) - Benefits - Schedule That's 6 sections. Check if any section would be empty: All have content. Now we need to format. We must not include boilerplate like privacy notice, equal opportunity statement, etc. Also remove duplicated lines. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all specifics: e.g., list of specific tools (drill, screwdriver, wire stripper, hacksaw, crimper), list of certifications (DMP, PACOM, Hanwha, March Networks, Verint, or AMAG). Also list of benefits: 10 Company Holidays and Paid Time Off starting at 13 days annually, Fun & Laughter Day Off, Medical, Dental & Vision Plan, Life insurance & Disability Plan, Wellness Program, 401K Matching Plan, Colleague Assistance Program, Tuition reimbursement, Competitive salary and compensation plan, Vehicle reimbursement plan or company vehicle, Corporate Social Responsibility Day, Cell phone reimbursement (if applicable), Paid parental leave. We need to keep those exactly as written? We should preserve substance but can format as list items. Now produce HTML. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Skills

  • ...
  ...

  Requirements

  • ...
  ...

  Benefits

  • ...
  ...

  Schedule

  Full-time position.

  Check if we need to include "full-time, enthusiastic, results driven and forward-thinking" in About the role? Already we have description. Could include that as part of About the role. Now let's extract About the role text: "Convergint is looking for a full-time, enthusiastic, results driven and forward-thinking Security Project Technician to join our amazing culture. In this role, you will install, program, system start-up/check-out, certify, and customer train on assigned projects including small to large projects that vary in complexity. As a Security Project Technician, you are a part of a dynamic team that allows you to grow as Convergint grows." We should not repeat the job title as heading, but we can mention it in paragraph. That's fine. Now Responsibilities: We need to pull all duty sentences from the block after "What you’ll do with “Our Training and Your Experience”". Actually there is a weird phrase: "What you’ll do with “Our Training and Your Experience” Convergint's greatest strength is our people! Every colleague is encouraged to participate in our Recruit Awesome People program, helping us grow Convergint by promoting our colleague-first culture and referring top talent to the Talent Acquisition Team and hiring managers.Installs, programs, test, repairs, and services a variety of non-routine systems and equipment which may include security, pneumatic systems, and/or building automation. Colleague is key interface for the provision of technical support and training for the customer and as such is accountable for maximizing customer satisfaction. Refers only the most complex issues to higher levels.Reads basic blueprints, schematics, manuals, and other specifications to determine installation procedures; Interprets manuals, schematics, and wiring diagrams, and repairs equipment, utilizing knowledge of electronics and using standard test instruments and hand tools.Operates systems to demonstrate equipment, commission new systems, analyze performance and identify malfunctions. Writes a variety of non-routine programs for systems.Acts as “our customer’s best service provider” at all times thereby ensuring Convergint Technologies is the customer’s first choice for service.Consults with engineering personnel to resolve unusual problems in system operation, maintenance, and warranty work.May advise management regarding customer satisfaction, product performance, installation techniques and standards as well as suggestions for product improvements.Executes most of the technical aspects of multiple projects with varying timelines and budgets including programming, graphics development, start-up, certification testing, customer training, close-out documentation, and on-going technical support etc..Identifies potential project risks, communicates to appropriate parties and assist in the development and implementation of strategies to minimize impact and to control deviations from estimated costs and project deadlines.Works closely with the Project Manager and/or Operations Manager and assists in the overall coordination of specific projects; makes recommendations regarding quality of work and potential changes in scope, and identifies ways to continuously improve customer satisfaction.Using technical knowledge, skills and experience, acts as a mentor to less experienced staff. May supervise workers in testing, tuning, and adjusting equipment to obtain optimum operating performance.Performs other duties and responsibilities as requested or required." We need to split into sensible list items. Let's break by sentences (though some are run-on). We'll create list items for each distinct duty. Potential list items: - Installs, programs, tests, repairs, and services a variety of non-routine systems and equipment which may include security, pneumatic systems, and/or building automation. - Serves as key interface for provision of technical support and training for the customer, accountable for maximizing customer satisfaction. - Refers only the most complex issues to higher levels. - Re