Communication Systems Technician I
Mobile Communications America · Charlotte, NC · 4 wk ago
Information TechnologyFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. No metadata like Job ID. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- Intro: "MCA, your trusted advisor for wireless communications, data, and security, is seeking an experienced Communication Systems Technician in the Charlotte, NC area to support our fast-growing MSS division. MCA seeks team members who share our values: service, growth, teamwork, and safety. As a Military Friendly Employer, we welcome veterans, with over 250 already on board. Join us and become part of the MCA family, where we prioritize both work and enjoyment. We offer competitive compensation and benefits such as Medical, Dental, Vision, 401K, PTO, Holiday Pay, Education Incentives, and more."
That's about the role and benefits.
- "WHAT YOU WILL BE DOING:" list of duties.
- "WHAT YOU WILL BRI NG TO THE TEAM:" (typo) list of requirements/qualifications.
- "YOUR ENVIRONMENT AND PHYSICAL REQUIREMENTS:" physical demands.
- "TRAVEL REQUIREMENTS:" travel.
- "DIRECT REPORTS: No direct reports"
- "Who We Are" description of company.
- "What We Believe" values.
- Note about accommodation etc (boilerplate) should be removed.
We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections to include.
We have substantive content for:
- About the role: could include intro description of role, company, values, etc.
- Responsibilities: the "WHAT YOU WILL BE DOING:" list.
- Requirements: maybe the "WHAT YOU WILL BRING TO THE TEAM:" includes experience, skills, education, certifications, etc.
- Qualifications: maybe overlapping with requirements; but we could separate: Requirements (experience, education) and Skills (technical skills). However we need to avoid thin sections. Could combine.
- Benefits: we have benefits list.
- Pay: not specified (only "competitive compensation") but that's vague; we should not create Pay section unless posting actually states them. It says "competitive compensation and benefits". That's not specific numbers. According to rule: 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. Benefits we have specific list, so we can include Benefits. Pay: only "competitive compensation" which is vague; better not to create Pay section.
- Schedule: we have "First shift hours Monday–Friday, with occasional 2nd or 3rd shift and weekends depending on project schedules." Also on-call rotation. That's specific enough to create Schedule section.
Thus sections: About the role, Responsibilities, Requirements (maybe combine experience/education), Skills (technical skills), Benefits, Schedule.
We need to avoid duplication. Let's extract content.
About the role: Could combine intro paragraph plus "Who We Are" and "What We Believe". But we must not repeat job title. Provide description of company, values, military friendly, etc.
Responsibilities: list from "WHAT YOU WILL BE DOING:" bullet points.
Requirements: maybe "At least two (2) years of experience in diagnosing, repairing, programming, and installing mobile communications equipment. Team-focused with a passion to meet customer needs. Strong communications skills for end users and third parties. Resourceful technicians sometimes need assistance/guidance from others. Understanding of / willingness to learn two-way radio theory. Experience operating testing equipment like spectrum analyzers, system analyzers, watt meters, TDRs, FDRs, and multi-meters. Proficiency with Microsoft Office. A valid driver’s license. Ability to pass a 7-year background check, motor vehicle check, and drug screen. A two-year degree in Electronics, IT, or an applicable subject, preferred. P25 and/or MotoTRBO experience, preferred. CET certification, preferred."
Skills: maybe we could separate technical skills vs soft skills. But we could put all under Requirements. However we need to avoid thin sections. Could have Requirements (experience, education, certifications) and Skills (technical skills like equipment, software). But we have overlapping.
Better: Use Requirements for experience, education, background check, driver's license. Use Skills for technical skills: two-way radio theory, testing equipment, Microsoft Office, P25/MotoTRBO, CET certification. Also soft skills like team-focused, communication skills could be under Requirements or Skills. Let's decide.
We'll create:
- About the role: intro + company description + values.
- Responsibilities: duties list.
- Requirements: experience (2+ years), team-focused, passion, strong communication skills, resourceful, willingness to learn two-way radio theory, valid driver's license, ability to pass background checks, two-year degree preferred.
- Skills: experience operating testing equipment (spectrum analyzers, etc.), proficiency with Microsoft Office, P25 and/or MotoTRBO experience preferred, CET certification preferred.
- Benefits: Medical, Dental, Vision, 401K, PTO, Holiday Pay, Education Incentives, and more.
- Schedule: First shift hours Monday–Friday, occasional 2nd or 3rd shift and weekends depending on project schedules; on-call rotation for critical systems maintenance; travel as necessary.
We also have physical requirements and travel requirements. Travel could be part of Schedule or separate. But we have Travel section not in allowed headings; we could fold travel into Schedule or maybe into Requirements? The instruction: only use those headings. So we must incorporate travel info into one of those sections. Probably Schedule (since travel relates to schedule). Or we could add to About the role? Better to add to Schedule: "Travel as necessary to support company and customer needs."
Physical requirements: we could incorporate into About the role or maybe into Requirements? But physical demands are not explicitly listed in allowed headings. Could fold into About the role as part of role description. However we should preserve all substantive info. We can include physical requirements in a
under About the role or maybe under Responsibilities? Probably better to add a short paragraph under About the role describing work environment. But we must not create a section for physical requirements unless we have a heading; we can't. So we need to embed it somewhere. Let's embed physical requirements in About the role after company description. Now craft HTML. Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Schedule
- ... ...