Field Service Technician II Chicago, IL (Elmhurst)

We need to output HTML fragment with sections: About the role? Actually we have "About BearCom" description at top, but we should not repeat job title. Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We have content: About BearCom (company description). Could map to "About the role"? Actually "About BearCom" is about company, not role. Could use "About the role" heading for description of role? The posting includes "Job Description: As a Field Service Technician II...". That's role description. So we can put that under

About the role

with paragraphs. Responsibilities: list of duties: "Create Mid-Level Programming Codeplugs (12+ Channels, Trunking, Multiple Zones)", "Install and Service Wireless Communications Equipment (e.g. UHF/VHF and 800/900 MHz Systems, Dispatch Consoles, BDA/DAS Systems, Microwave Systems, Wireless Broadband Devices, CCTV Equipment)", "Recommend Appropriate Equipment and Hardware That Meets Customer Requirements". Also maybe "Some Regional and/or Overnight Travel and On-Call Hours May Be Required" could be under Schedule? Actually schedule: travel and on-call hours. Could be Schedule section. Preferred Qualifications: list: "Proficient Electronics Background", "Experience in Diagnosing, Repairing, Programming, and Installing RF Equipment", "Understands Two-Way Radio Theory and RF Propagation Characteristics at Various Frequency Bands", "Competent Operating Test Equipment (Communications Service Monitors, Wattmeters, TDRs, FDRs, Multimeters)", "IP Networking Experience a Plus", "Proficient in MS Office Suite (Outlook, Word, Excel)", "Must Have a Valid Driver’s License", "Drug Screenings, Motor Vehicle Record, and Background Checks Part of the Hiring Process". Also "Benefits" section: list benefits. Qualifications: list of required qualifications: "5+ years of Service Technician experience in diagnosing, repairing, programming, and installing Motorola, Kenwood, ICOM, Vertex equipment in the 2-way radio wireless and /or communication field. (if not military experienced)", "Extensive knowledge and understanding of 2-way radio theory, RF propagation characteristics at various frequency bands and communications systems.", "Ability to interpret schematics, blueprints, and diagrams.", "Knowledge of battery backup systems, base stations, repeaters, multicouplers, and duplexers, TCP/IP principles and NIC programming.", "Proficiency in operating various test equipment including but not limited to, spectrum analyzers, system analyzers, watt meters, TDRs, FDRs, and multi-meters.", "Proficiency in designing, troubleshooting, and installing Distributed Antenna Systems (DAS) and Bidirectional Amplifier (BDA) systems. (remove if not BDA tech)", "Proficiency with MS Office Suite, such as Microsoft Word and Excel.", "CET Certification a plus.", "Journeyman level must be attained within 6 months of employment.", "Associate degree in Electronics Technology or equivalent.", "R56 Certified Installer.", "Motorola Astro 4x-7x training providing support for various system operations.", "Certification in various Astro 25 products (Quantar, GTR8000, MCC5500/7500, etc..)", "Certification in various MotoTRBO products and systems (Connect+, Capacity+, Linked Capacity+, IP Site Connect, Capacity Max etc.).", "Knowledge of audio, RF, digital, and microprocessor electronic circuits found in communications equipment at the component level.", "Security Clearance preferred. (remove unless specific to geography like Chantilly)", "Must have a valid driver’s license.", "Drug screenings and background checks are part of the hiring process which may also include a Motor Vehicle Record check." Also there is duplicate "You’ll Also Receive: Highly Competitive Compensation Medical, Dental, and Vision Insurance..." appears twice (once in Benefits section, again later). We'll include benefits once. Pay: The posting mentions "Highly Competitive Compensation" but no specific numbers. According to rule: do NOT create Pay section unless posting actually states them. It states "Highly Competitive Compensation" but that's vague. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Highly Competitive Compensation" is somewhat vague but it's a statement. Is that considered filler? It's not a specific number, but it's a statement about compensation. The rule says avoid placeholder like "commensurate with experience". "Highly Competitive Compensation" is similar to vague. I'd err on side of not creating Pay section because it's not specific. However Benefits section we have concrete list. Schedule: "Some Regional and/or Overnight Travel and On-Call Hours May Be Required" - that's schedule info. So we can create Schedule section with that sentence. Now we need to avoid boilerplate: remove EEO statements, duplicated lines, application instructions, cookie/navigation/legal etc. Also remove "KEYWORDS:" line. Also remove "BearCom is proud to be an equal-opportunity workplace..." etc. We need to preserve all substantive information. So we need to include About BearCom description? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't list About the company. But we could put About BearCom under About the role? Might be okay to include as a paragraph under About the role or maybe a separate section like "About BearCom" but not in allowed headings. The instruction says use those headings for sections; we can still include other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections; we could also use other headings if needed? Safer to stick to those. So we can incorporate BearCom description into About the role paragraph. Thus structure:

About the role

About BearCom: Largest Distributor of Wireless Voice, Data, and Video Solutions in North America... (the company description) ... If interested in BearCom, please apply. (but we should remove application instructions? The line "If interested in BearCom, please apply." is application instruction; we should remove it per rule: remove application instructions. So we drop that.) Then job description paragraph: "As a Field Service Technician II with BearCom, you will be responsible for the installation and support of wireless communications systems. Our Technicians are the heart of every service location, and we rely on their expertise in the delivery of the best service and solutions for our customers. The ideal candidate will provide exceptional customer service and possess the technical ability to create imaginative solutions that meet and exceed the most challenging customer needs." That's About the role. Then Responsibilities: list. Then Requirements? Actually we have Preferred Qualifications and Qualifications (required). Could combine into Requirements and Qualifications sections. The instruction includes Requirements and Qualifications as separate headings. We'll put required qualifications under

Qualifications

and preferred under

Requirements

or vice versa. Usually Requirements are mandatory, Qualifications are preferred. But we have both. Let's treat "Qualifications" as required (the list after "Qualifications") and "Requirements" as preferred (the list after "Preferred Qualifications"). Thus:

Qualifications

• ... each required bullet

Requirements

• ... each preferred bullet

Skills: maybe we can include technical skills like MS Office, test equipment, etc. But we already have those in qualifications/requirements. Could create Skills section for things like "Proficient in MS Office Suite", "IP Networking Experience a Plus", "Competent Operating Test Equipment". But to avoid duplication, we could keep them in qualifications/requirements. The instruction says prefer a few substantive sections over many thin ones. So maybe we skip Skills. Benefits: list. Schedule: include travel/on-call. Pay: we skip. Now ensure we don't include duplicated lines like "You’ll Also Receive:" appears twice; we include once. Also remove "KEYWORDS:" line. Remove EEO statements. Remove "BearCom is proud to be an equal-opportunity workplace..." duplicates. Remove "All employment is decided based upon qualifications, merit, and business need." duplicates. Remove "Drug screenings, Motor Vehicle Record, and Background Checks Part of the Hiring Process" appears in both Preferred Qualifications and Qualifications; we should keep only once? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. If it's duplicated, we should keep one instance? It says remove duplicated lines. So we should deduplicate. So we will include that line only once, perhaps under Qualifications (since it's part of hiring process). We'll keep it there. Now compile. Let's extract exact text. About BearCom paragraph: "About BearCom: Largest Distributor of Wireless Voice, Data, and Video Solutions in North America40+ Years Industry-Leading ExperiencePartnerships with Motorola, JVC Kenwood, Avigilon, +More75+ Branches Across North America BearCom employs a wide range of installation and technical team members and will provide extensive on-the-job training. If interested in BearCom, please apply." We need to fix missing spaces: The original had no spaces after numbers. We should preserve as is? Probably we should keep the text exactly but we can add spaces for readability? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Adding spaces could be considered altering formatting but not substantive. Safer to keep as given but it's hard to read. However we can keep as is; it's still substantive. We'll keep exactly. But we need to remove "If interested in BearCom, please apply." (application instruction). So we drop that sentence. Thus About BearCom paragraph: "About BearCom: Largest Distributor of Wireless Voice, Data, and Video Solutions in North America40+ Years Industry-Leading ExperiencePartnerships with Motorola, JVC Kenwood, Avigilon, +More75+ Branches Across North America BearCom employs a wide range of installation and technical team members and will provide extensive on-the-job training." Now job description paragraph: "As a Field Service Technician II with BearCom, you will be responsible for the installation and support of wireless communications systems. Our Technicians are the heart of every service location, and we rely on their expertise in the delivery of the best service and solutions for our customers. The ideal candidate will provide exceptional customer service and possess the technical ability to create imaginative solutions that meet and exceed the most challenging customer needs." Now Responsibilities bullets: - Create Mid-Level Programming Codeplugs (12+ Channels, Trunking, Multiple Zones) - Install and Service Wireless Communications Equipment (e.g. UHF/VHF and 800/900 MHz Systems, Dispatch Consoles, BDA/DAS Systems, Microwave Systems, Wireless Broadband Devices, CCTV Equipment) - Recommend Appropriate Equipment and Hardware That Meets Customer Requirements Now Qualifications (required) bullets: - 5+ years of Service Technician experience in diagnosing, repairing, programming, and installing Motorola, Kenwood, ICOM, Vertex equipment in the 2-way radio wireless and /or communication field. (if not military experienced) - Extensive knowledge and understanding of 2-way radio theory, RF propagation characteristics at various frequency bands and communications systems. - Ability to interpret schematics, blueprints, and diagrams. - Knowledge of battery backup systems, base