Engineer, Communications

We need to output HTML fragment with sections: About the role? Actually the posting includes description paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real specific content for it. We must not repeat job title as heading. We must not put Job ID etc. Remove boilerplate. We need to parse the posting: It starts with intro about Lochner and Egis merging, then description, then "Job Description We are looking for a Engineer, Communications in our Sacramento, CA office." Then responsibilities under "The Impact You’ll Make (Job Responsibilities)" bullet list. Then "Qualifications The Expertise You’ll Bring (Qualifications)" bullet list. Then "Additional Information Why You'll Thrive at Egis" etc. Then "What Sets Egis Apart" bullet list. Then "Total Rewards That Support You" bullet list. Then "Compensation & Pay Transparency" with salary range. Then EEO etc (remove). Also "Equal Employer" etc (remove). Also background check etc (remove). So we need to extract sections. We need sections: About the role (maybe intro paragraph about role?), Responsibilities (list), Requirements (maybe qualifications?), Qualifications (maybe education/experience?), Skills (maybe technical skills?), Benefits (Total Rewards), Pay (salary range), Schedule (maybe not present). The posting does not mention schedule explicitly, so we should not create Schedule section. We need to decide which sections to include based on content. We have: - About the role: Could be the introductory paragraph describing the role: "We are looking for a Engineer, Communications in our Sacramento, CA office. This role will be responsible for developing technical solutions, coordinating system interfaces, supporting compliance activities, and ensuring communications systems are successfully delivered into operation. The ideal candidate will have experience working with complex transportation infrastructure projects and collaborating with multidisciplinary engineering teams, operators, suppliers, and stakeholders throughout the project lifecycle." That seems like About the role. - Responsibilities: The bullet list under "The Impact You’ll Make (Job Responsibilities)". We'll list each as

. - Requirements: Could be the qualifications/experience needed? The posting has "Qualifications The Expertise You’ll Bring (Qualifications)" which includes degree, PE license, 10+ years experience, etc. That could be Requirements or Qualifications. We need both Requirements and Qualifications sections if content distinct. But we might combine? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if there is distinct content. The posting lumps degree, license, experience, proven experience, experience with technologies, strong understanding, demonstrated ability. That seems like qualifications. Could treat as Qualifications. Requirements could be maybe the "Additional Information Why You'll Thrive at Egis" etc? Not exactly. Might be better to treat the bullet list under Qualifications as Requirements (since they are requirements). Then we could have Qualifications for maybe skills? But we also have a separate "Skills" heading; we could extract technical skills from qualifications: fiber optic networks, IP/MPLS networking, radio systems, operational telecommunications, LTE, FRMCS, etc. Also systems integration, operational communications, cybersecurity interfaces, transportation infrastructure applications. Those could be Skills. Thus we can have: - Requirements: Bachelor's degree, PE license, 10+ years experience, proven experience delivering communications systems, etc. - Skills: Experience with fiber optic networks, IP/MPLS networking, radio systems, operational telecommunications, LTE, FRMCS, mission-critical communications technologies; strong understanding of systems integration, operational communications, cybersecurity interfaces, transportation infrastructure applications; demonstrated ability to develop technical deliverables, support compliance and operational approvals, coordinate multidisciplinary teams, suppliers, contractors. But we need to ensure we don't duplicate content. We'll split logically. - Benefits: Total Rewards That Support You bullet list. - Pay: Anticipated Base Salary Range: $160,000 – $240,000 annually. - Schedule: Not present, so omit. We also might include a section "About the role" as described. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all points from the posting, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details, but we can rephrase? Probably we should keep the exact wording or close. However we need to format into HTML with

and

. We can keep the sentences as they are. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the EEO paragraph, background check, etc. Also remove duplicated lines: There may be duplicated sentences like "At Egis, we believe transparency helps candidates make informed career decisions." etc. We'll keep only one. We need to output only HTML fragment, no /, no markdown. Let's craft. First, About the role: combine the two sentences: "We are looking for a Engineer, Communications in our Sacramento, CA office. This role will be responsible for developing technical solutions, coordinating system interfaces, supporting compliance activities, and ensuring communications systems are successfully delivered into operation. The ideal candidate will have experience working with complex transportation infrastructure projects and collaborating with multidisciplinary engineering teams, operators, suppliers, and stakeholders throughout the project lifecycle." We'll put that in

. Responsibilities: list each bullet from "The Impact You’ll Make (Job Responsibilities)". Let's extract: - Develop, review, and approve communications engineering deliverables throughout design, construction, testing, and commissioning phases. - Support requirements management, system architecture development, and interface coordination across multiple engineering disciplines. - Review supplier and contractor designs to ensure compliance with project requirements, operational needs, and applicable standards. - Provide technical oversight for communications systems, including fiber networks, radio systems, telecommunications infrastructure, operational communications, and control center technologies. - Support regulatory, operational, and compliance activities, including preparation and review of technical documentation and approval packages. - Develop and support testing, commissioning, system integration, defect resolution, and final acceptance activities. - Coordinate with project stakeholders, operators, consultants, service providers, and technical teams to ensure successful project delivery and operational readiness. We'll put each as

inside

. Requirements: from Qualifications bullet list but we need to decide which items go to Requirements vs Skills. Qualifications bullet list: - Bachelor's degree in Electrical Engineering, Telecommunications Engineering, Systems Engineering, or a related technical discipline. - Professional Engineer (PE) license, or ability to obtain licensure. - 10+ years of experience in railway communications, operational telecommunications, or transportation systems engineering. - Proven experience delivering communications systems through design, integration, testing, commissioning, and operational acceptance. - Experience with fiber optic networks, IP/MPLS networking, radio systems, operational telecommunications, LTE, FRMCS, or other mission-critical communications technologies. - Strong understanding of systems integration, operational communications, cybersecurity interfaces, and transportation infrastructure applications. - Demonstrated ability to develop technical deliverables, support compliance and operational approvals, and coordinate multidisciplinary teams, suppliers, and contractors on complex infrastructure projects. We could assign first four bullets to Requirements (degree, license, experience, proven experience). Then the last three bullets to Skills (experience with technologies, strong understanding, demonstrated ability). That seems reasonable. Thus Requirements section:
with those four items. Skills section:
with the three items. Benefits: from Total Rewards That Support You bullet list. Let's extract: - Competitive medical, dental, and vision coverage - 401(k) retirement plan with company match - Paid time off and flexible holiday program - Flexible work arrangements, including hybrid and remote opportunities where business needs allow - Life insurance and disability coverage, including maternity leave - Health Savings Account (HSA) with employer contributions - Flexible Spending Accounts (FSA) for healthcare and dependent care expenses - Paid family leave - Wellness programs supporting physical and mental well-being - Education assistance, professional development, and continuing learning opportunities - Employee Assistance Program (EAP) - Employee discount programs We'll put each as
• . Pay: from Compensation & Pay Transparency: "Anticipated Base Salary Range: $160,000 – $240,000 annually." Also mention incentive compensation etc. We should include that as well: "In addition to base salary, this position may be eligible for incentive compensation, where applicable, and a comprehensive Total Rewards package that includes health benefits, retirement savings, paid time off, professional development opportunities, and other employee programs." That's substantive. We'll include that in Pay section maybe as a

  . We must not repeat Benefits content; but we can mention that total rewards package includes those benefits, but we already have Benefits section. It's okay to mention but not duplicate list. We'll keep the sentence. Schedule: none. Now we need to ensure we didn't include any boilerplate: The EEO paragraph, background check, etc removed. Also we need to remove duplicated lines: The text about "At Egis, we believe transparency helps candidates make informed career decisions." appears maybe twice? We'll include only once. Now construct HTML. We'll start with

  About the role

  then

  ...

  Then

  Responsibilities

  • ...
  ...
  Then

  Requirements

  ...
  Then

  Skills

  ...
  Then

  Benefits

  ...
  Then

  Pay

  ...

  Make sure no extra whitespace? It's fine. Let's write. Check for any missing substantive info: The intro also includes "Lochner and Egis are entering an exciting new chapter as one organization..." That's about company background, not role-specific. Should we include that? It's substantive but not about role. The instruction: "Preserve ALL substantive information". Does that include company overview? Possibly yes, but we have to fit into sections. Could add another section like "About Egis" but not in allowed headings. Allowed headings are limited to those list. We could put company overview in About the role? But that would be mixing. However the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not strict list? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we shouldn't invent other headings. So we should fit company overview into About the role maybe? But About the role should be about the role, not company. However we could include a brief sentence about Egis as part of About the role? Might be okay. But we must preserve all substantive information; we cannot omit company overview. However we could incorporate it into About the role paragraph as a preceding sentence: "Lochner and Egis are entering an exciting new chapter as one organization. We have combined decades of trusted U.S. engineering expertise with the global reach, technical excellence, and career opportunities of a leading international engineering, consulting, and infrastructure firm. While our name has changed, our commitment to our people, clients, and communities is stronger than ever. At Egis, every project is an opportunity to create lasting impact. We collaborate with public and private clients to design and deliver innovative transportation, aviation, rail, transit, water, structural, environmental, and infrastructure solutions that connect communities and improve everyday life. Join a team where innovation is encouraged, collaboration is valued, and your work helps build a more sustainable future." Then follow