Senior Communication System Designer

We need to output HTML fragment with sections: About the role? The posting includes a job summary paragraph. We need to use

for section headings like 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. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Additional Information" maybe? But we need to preserve substantive info. The posting includes: company description, job summary, responsibilities & qualifications (combined), "What We’re Looking For" (requirements/qualifications), "Why Join TYLin?" (benefits? maybe culture), "Additional Information" (benefits description), "We believe in recognizing..." etc. Also mention "TYLin offers a comprehensive total rewards package." That's benefits. Also mention "Collaboration, mission-driven focus..." maybe not needed. Also mention "TYLin is an equal opportunity employer..." that's EEO boilerplate, should be removed. Also mention "The company and its employees are required to comply..." maybe legal boilerplate, remove. We need to decide sections: About the role (job summary), Responsibilities (list of duties), Requirements/Qualifications (education, experience, skills), Skills (maybe separate but could combine), Benefits (benefits description), Pay (not specified -> do not include), Schedule (not specified -> do not include). Also maybe "Why Join TYLin?" could be considered Benefits or Culture but we can treat as Benefits? Actually they have a separate "Why Join TYLin?" describing meaningful infrastructure, technical challenge, project variety, technical leadership, collaborative culture. That's more about role/benefits but not explicit benefits. Could be considered "About the role" or separate "Why Join TYLin?" but we only allowed headings from list. Could incorporate into About the role or Benefits. Since Benefits section should only be included if posting actually states them. They do state benefits: "TYLin offers a comprehensive total rewards package. Our benefits may include extensive medical, disability and life insurance coverage, continuing education benefits, paid time off, employee assistance program and a retirement savings plan with company matching contributions." That's specific benefits. So we can create Benefits section with that list. Also "Why Join TYLin?" could be considered part of About the role or maybe we could add a section "About the role" that includes job summary and why join. But we must not invent headings not in list. So we can put that content under About the role as prose. Responsibilities: we have a big list under "Responsibilities & Qualifications" and also under "What You’ll Do". We need to extract duties as list items. We'll create

• for each duty. Requirements/Qualifications: we have "What We’re Looking For" with bullet-like sentences. We'll create list. Skills: Could be extracted from responsibilities but maybe we can combine into Requirements. However we have a separate Skills heading allowed. We could list specific skills: fiber optic communications networks, radio/wireless, CCTV, PIS, CAD/AVL, SCADA, PACS, video/audio, communications/server room infrastructure, UPS, networking protocols, network architecture, routers, switches, wireless technologies, network security, AutoCAD/MicroStation, BIM/Revit, etc. But we need to ensure we don't invent. We can pull from responsibilities and qualifications. Might be okay to have Skills section listing those specific technical skills. But we must not create thin sections; better to have few substantive sections. Perhaps combine Requirements and Skills into one "Requirements" section. But the instruction says use headings for those categories if content exists. It doesn't forbid combining, but we can decide to have Requirements and Qualifications as one section (maybe heading "Requirements"). However they list both Requirements and Qualifications as possible headings. We could use "Requirements" heading and include education, experience, skills. Or we could have two sections: Requirements and Qualifications. But they'd be thin if we split. Better to have one "Requirements" section that includes education, experience, and skills. Or we could have "Qualifications" heading and include education/experience, and "Skills" heading for technical skills. That would be two sections, each substantive. Let's see content: Under "What We’re Looking For": Bachelor’s degree, 10+ years experience, demonstrated experience designing and delivering communications systems for rail, transit, transportation, aviation, or other complex infrastructure environments. Strong understanding of communications networks, including fiber optic infrastructure, Ethernet, routers, switches, wireless communications, network architecture, and related technologies. Experience developing detailed engineering/design documentation, including contract drawings, specifications, equipment schedules, network diagrams, and system architecture documentation. Experience with AutoCAD, MicroStation, or similar design platforms; familiarity with BIM/Revit environments is an asset. Ability to interpret and apply technical standards, specifications, codes, and client design criteria. Experience coordinating multidisciplinary designs and working directly with project managers, engineers, architects, contractors, vendors, and clients. Strong understanding of the full project lifecycle, from conceptual design through construction and commissioning. Ability to independently manage technical assignments, prioritize competing deadlines, and take ownership of deliverables. Professional Engineer (PE) license preferred, or demonstrated progression toward professional registration. Strong written and verbal communication skills, with the ability to explain complex technical concepts clearly to both technical and non-technical stakeholders. Experience providing technical direction, mentoring, or quality review of junior staff is preferred. That's a mix of qualifications and skills. We could split: Requirements: education, experience, PE license, ability to manage assignments, etc. Skills: technical knowledge of networks, software, standards, etc. But it's ambiguous. Given instruction to prefer few substantive sections over many thin ones, maybe we just have one "Requirements" section that includes all that. Then we can have "Responsibilities" section, "Benefits" section, and maybe "About the role" section (job summary + why join). That's four sections. We must not include Pay or Schedule. Now we need to remove boilerplate: The initial paragraph about TYLin being globally recognized etc. That's company description; could be part of About the role? Might be considered boilerplate but it's substantive about the firm. Could include in About the role as context. However it's somewhat generic but still about the company. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not boilerplate per se; it's okay to keep. We also need to remove "Additional Information" paragraph that repeats benefits? Actually we already captured benefits. The "Additional Information" includes: "We believe in recognizing the unique value that each individual brings to our team..." and "TYLin offers a comprehensive total rewards package..." plus military stuff and EEO. We'll keep the benefits part, discard the rest (military, EEO, compliance). Also remove "TYLin is an equal opportunity employer..." etc. Now craft HTML. Structure:

  About the role

  TYLin is a globally recognized, full-service infrastructure consulting firm committed to providing innovative, cost-effective, constructible designs for the global infrastructure market. With over 3,000 employees throughout the Americas, Asia, and Europe, the firm provides support on projects of varying size and complexity. Together, we enhance conventional designs with smarter, more resilient systems. We provide people with better mobility. We steward precious resources by finding more sustainable solutions.

  Are you an experienced communications systems professional with a passion for rail and transit? TYLin is seeking a Senior Communication System Designer to join our growing Rail + Transit team in Philadelphia, PA. This is an opportunity for a technically strong professional with 10+ years of experience to play a key role in the design and delivery of complex communications and Operations Technology (OT) systems supporting major transit and rail infrastructure projects across Philadelphia, New York, and the Northeast. You will bring strong technical expertise, sound design judgment, and a collaborative approach to projects ranging from station upgrades and maintenance facilities to major rail and transit programs. The successful candidate will be comfortable taking ownership of communication systems design packages while working closely with engineers, architects, project managers, clients, and other technical disciplines.

  Why Join TYLin? Meaningful Infrastructure: Contribute to major rail and transit programs that support safe, reliable, and connected transportation systems used by millions of passengers. Technical Challenge: Work on complex communications and systems projects involving multiple disciplines, technologies, stakeholders, and operating environments. Project Variety: Support major infrastructure programs across Philadelphia, New York, and the broader Northeast, including stations, maintenance facilities, rail corridors, and transit systems. Technical Leadership: Take ownership of significant design responsibilities while working alongside experienced professionals across TYLin’s multidisciplinary organization. Collaborative Culture: Work in an environment that values technical excellence, collaboration, innovation, and a commitment to delivering exceptional project outcomes.

  Then Responsibilities:

  Responsibilities

  • Lead and perform the design and technical delivery of communications and Operations Technology (OT) systems for complex rail and transit projects.
  • Develop communications systems designs from concept through final design, procurement, construction, testing, and commissioning.
  • Prepare detailed contract drawings, specifications, calculations, equipment schedules, design narratives, and other technical documentation suitable for construction.
  • Design and coordinate a range of transit communications systems, which may include: fiber optic communications networks and infrastructure; radio and wireless communications systems; CCTV and video surveillance systems; Passenger Information Systems (PIS), including electronic signage and displays; Computer-Aided Dispatch / Automatic Vehicle Location (CAD/AVL) systems; SCADA systems, including traction power and train dispatch applications; Physical Access Control Systems (PACS); video and audio systems, including recording and storage infrastructure; communications/server room infrastructure and UPS systems.
  • Evaluate technical requirements, scopes of work, specifications, design criteria, directive drawings, and applicable standards.
  • Develop system architecture, network diagrams, equipment layouts, interconnection diagrams, and detailed design documentation.
  • Apply knowledge of networking protocols, network architecture, routers, switches, wireless technologies, and network security principles to transit communications environments.
  • Coordinate communications system designs with civil, structural, architectural, electrical, systems, signaling, track, traction power, and other project disciplines.
  • Review designs and technical work prepared by other designers and engineers for quality, completeness, constructability, and compliance with project requirements.
  • Develop and review construction cost estimates for communications systems, equipment, materials, and installation.
  • Participate in client meetings, technical workshops, design reviews, site investigations, and construction support activities.
  • Provide technical guidance to less-experienced designers and engineers and contribute to the development of team standards, processes, and design practices.
  • Support field investigations, construction administration, shop drawing reviews, RFIs, testing, commissioning, and troubleshooting as required.
  • Help identify technical risks and develop practical, cost-effective solutions that meet client, operational, and regulatory requirements.
  • Maintain a high standard of technical quality across all assigned deliverables and project phases.
  Then Requirements:

  Requirements

  • Bachelor’s degree in Electrical Engineering, Systems Engineering, Telecommunications, or a related discipline.
  • 10+ years of relevant experience in communications systems, electrical systems, rail/transit systems, telecommunications, or a closely related field.
  • Demonstrated experience designing and delivering communications systems for rail, transit, transportation, aviation, or other complex infrastructure environments.
  • Strong understanding of communications networks, including fiber optic infrastructure, Ethernet, routers, switches, wireless communications, network architecture, and related technologies.
  • Experience developing detailed engineering/design documentation, including contract drawings, specifications, equipment schedules, network diagrams, and system architecture documentation.
  • Experience with AutoCAD, MicroStation, or similar design platforms; familiarity with B