COMMUNICATIONS ELECTRICIAN O 3686 (REVISED 01-23-26)
City of Los Angeles · Los Angeles Metropolitan Area · 1 mo ago
Management$121k–$128k/yrFull-time
We need to produce HTML fragment with sections: About the role? Responsibilities? Requirements? Qualifications? Skills? Benefits? Pay? Schedule.
We must include only sections with real specific content. The posting includes duties description, salary info, shift differential, maybe benefits? Not explicit benefits. Pay: we have salary numbers. Schedule: shift differential indicates night work, maybe schedule info? Not explicit schedule. We can include Pay section with salary details. Benefits: none explicit, so omit. Schedule: maybe mention shift differential and possible permanent assignment outside area; but not schedule specifics. Could include Schedule if we have info: shift differential for night work, some positions may require permanent assignment outside Southern California area. That's more about location than schedule. Probably not enough for Schedule section. We'll include Pay.
We need About the role? Could be a brief paragraph summarizing role. Use duties as Responsibilities? The posting includes "DUTIES" then description of work. So we can put Responsibilities section with that description.
Requirements: list of requirements/minimum qualifications. Use
- .
Qualifications maybe same as requirements? Could combine. But we can have Requirements section and Qualifications maybe duplicate; better to have one Requirements section.
Skills: maybe list of skills from duties? Could extract but not explicit list. Might skip.
We need to preserve all substantive info: salary numbers, shift differential, possible assignment outside area, reciprocity link, notes about salary start, etc. Also process notes: driver license requirement, disqualification criteria, internal use notes, selective certification details, application deadline, selection process details (multiple-choice test, interview, competencies, etc). We must include all that.
We need to avoid boilerplate: cookie/navigation/legal/EEO etc. The posting includes many notes; we need to keep substantive info but remove duplicated lines and application instructions? The instruction says remove application instructions. However we need to keep info about where to apply & application deadline? That's application instructions. The instruction says remove application instructions. So we should drop WHERE TO APPLY & APPLICATION DEADLINE section. Also remove links to application process? Probably yes. But we need to keep substantive info like salary, duties, requirements, process notes (selection process). The selection process details are part of examination; that's not application instructions per se, but it's about how exam is administered. Might keep.
We need to be careful not to include instructions on how to apply, where to apply, deadlines. So we will omit that section.
We also need to remove duplicated lines.
We need to output only HTML fragment.
Let's structure:
About the role
maybe a short paragraph summarizing role: Communications Electrician does skilled direct hands-on work in maintenance, repair, installation, configuration and programming of communications systems and equipment such as ... (list). That's from duties.Responsibilities
maybe same as duties? Could combine. But we need to avoid duplication. Perhaps About the role is brief summary, Responsibilities is detailed list of duties. We'll include both. Responsibilities: list of duties: maintenance, repair, installation, configuration and programming of communications systems and equipment such as microwave radio, conventional and trunking two-way radio, VoIP telephony, SONET, SCADA, data networks, radio communications transmitters/receivers and systems, multiplexing, audio and video, IP security cameras, badge access control systems, CCTV, and CAD. We can put as- each item.
Requirements
list of minimum qualifications: four years experience... or two years plus etc. We'll list as bullet points.Qualifications
maybe not needed if same as requirements. Could skip.Skills
maybe list of skills from duties: troubleshooting, installation, etc. Could extract but not explicit. Might skip.Pay
paragraph with salary info: Annual salary $116,760 (flat-rated) for the role? Also salary range in Department of Water and Power $121,479 to $128,244 and $135,907 (flat-rated). Shift differential for night work. Annual salary is at start of pay range. Current salary range subject to change. Confirm starting salary with hiring department. Also note about candidates appointed to lower pay grade positions. We'll include that.Selection Process
maybe as section? Could be under Requirements? But we have info about examination weights, multiple-choice test, interview, competencies, etc. That's substantive. We'll include a section maybe titled "Selection Process". Not in the prescribed headings list but we can use headings only from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Selection Process not allowed. So we need to fit that info into existing headings. Could put under Requirements? Or maybe under About the role? Better to put under Requirements as additional info? But the instruction: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. It didn't say we cannot use other headings, but likely they expect only those. Safer to stick to those. We can incorporate selection process details into Requirements or maybe under About the role? But that would be mixing. We could create a "Requirements" section that includes both minimum qualifications and selection process details (since they are part of the process). But selection process is not a requirement. However we could add a "Qualifications" section for selection process? Not ideal. Alternatively, we could create a "Pay" section and put selection process elsewhere? Not allowed. Maybe we can treat selection process as part of "Responsibilities"? No. Given the instruction, we should only use those headings. So we need to fit all info into those categories. Let's map: - About the role: brief description of role. - Responsibilities: duties list. - Requirements: minimum qualifications. - Qualifications: maybe additional qualifications like driver license, selective certification, etc. - Skills: maybe specific skills like radio, fiber-optics, microwave, certifications, etc. - Benefits: none. - Pay: salary info. - Schedule: shift differential and possible assignment outside area? Could treat shift differential as schedule info (night work). Also mention some positions may require permanent assignment outside Southern California area (location). Not schedule but maybe we can put under Schedule: shift differential for night work; some positions may require permanent assignment outside Southern California area (though that's location). We'll include shift differential. Thus we can allocate: About the role: short paragraph summarizing role. Responsibilities: bullet list of duties. Requirements: bullet list of minimum qualification options. Qualifications: bullet list of additional qualifications: valid Class C driver’s license, DMV record criteria, etc. Also maybe internal use notes about licensing verification. Skills: bullet list of selective certification skills/training options: radio, fiber-optics, microwave; certifications from Motorola, Harris, Nokia, Aviat; CompTIA Network+; ETA-I FOT; FCC General Radio Telephone Operator license. Pay: paragraph with salary details. Schedule: paragraph about shift differential for night work, and note about possible permanent assignment outside Southern California area (maybe location but we can put here). We must ensure we don't include boilerplate like links to reciprocity, accredited institutions, etc. Those are notes but substantive? They provide info about reciprocity and accreditation. Should we keep? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep those notes as they are substantive. Where to put them? Reciprocity link could go under Qualifications or About the role? It's about reciprocity between City departments and LADWP. Could be under Qualifications? Not exactly. Maybe under About the role as a note. Accredited institutions list also note about qualifying education. Could be under Qualifications. We need to keep the links? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The reciprocity link is not boilerplate; it's a reference. So we should keep it. Similarly the accredited institutions link. We need to embed them as tags? The output is HTML fragment; we can include link. That's fine. We must not include markdown fences. Now craft HTML. Let's draft:
About the role
The Communications Electrician performs skilled direct hands‑on work in the maintenance, repair, installation, configuration and programming of communications systems and equipment, including microwave radio, conventional and trunking two‑way radio, VoIP telephony, SONET, SCADA, data networks, radio communications transmitters/receivers and systems, multiplexing, audio and video, IP security cameras, badge access control systems, CCTV, and CAD.
Responsibilities
- Maintenance of communications systems and equipment.
- Repair of communications systems and equipment.
- Installation of communications systems and equipment.
- Configuration of communications systems and equipment.
- Programming of communications systems and equipment.
- Work with microwave radio, conventional and trunking two‑way radio, VoIP telephony, SONET, SCADA, data networks.
- Work with radio communications transmitters/receivers and systems, multiplexing, audio and video.
- Work with IP security cameras, badge access control systems, CCTV, and CAD.
Requirements
- Four years of full‑time paid experience in maintenance, repair, and installation of any of a wide variety of electronics and communications systems including video, conventional and trunking two‑way radio, microwave radio, telephone systems, monitoring systems, public address, data networks, IP security camera systems, badge access control systems, video and access systems including programming, configuration or troubleshooting of communications systems; OR
- Two years of full‑time paid experience of the type specified above, plus one of the following:
- Completion of a certificate program or associate degree program in electronics technology, telecommunications, or computer science at an accredited college or trade school; OR
- Successful completion of a U.S. military electronics technical course of 24 weeks or longer within the last 10 years; OR
- A certification in Cisco or HP Networking (CCNA, CCDA, CCDE, CCDP, CCNP, CCIE, HP AIS, HP ASE, HP Master ASE) and two years of experience in the installation and configuration of data network switches, routers and addressable nodes.
Qualifications
- Valid Class C driver’s license issued by the California DMV.
- DMV record within the last 36 months must not reflect three or more moving violations and/or at‑fault accidents, or a conviction of a major moving violation such as DUI or DWI in any state or jurisdiction.
- Licensing verification for Class C licenses will occur at the time of appointment.
- Qualifying education must be from a college, university, or trade school accredited by a City of Los Angeles recognized agency; a list of approved accrediting agencies can be found here.
- Candidates completing the examination process will be contacted by the Personnel Department to provide required proof of qualifying certificate program, associate degree, or coursework; applicants may attach a copy to their on‑line application to expedite the process.
- For information regarding reciprocity between City of Los Angeles departments and LADWP, see this document.
- each item.