Senior Traffic / Intelligent Transportation Systems (ITS) Engineer

We need to output HTML fragment with sections: About the role? Actually we need headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real specific content. We must not repeat job title as heading. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Must not include sections with filler like "commensurate with experience". Pay and Schedule only if posting actually states them. The posting includes compensation range: $135,000 to $165,000. Also mentions "Work Location Model: Hybrid". That's schedule? Not exactly schedule but maybe schedule not given. No explicit schedule like full-time, part-time. So we should not create Schedule section unless present. Benefits: posting mentions AECOM offers comprehensive benefits, lists many. So we can include Benefits section with that list. Qualifications: includes Minimum Requirements and Preferred Qualifications. Could combine into Qualifications section. Responsibilities: Key Responsibilities list. About the role: maybe from Job Description paragraph before responsibilities. Could use About the role heading for that descriptive paragraph. Skills: maybe not explicit separate; but we could include Skills if there is content like "Strong written, verbal, organizational, and client communication skills." That's under Qualifications. Might be better to keep Qualifications only. The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Skills? But we can embed skills in Qualifications. Let's extract content. Company Description: first paragraph about AECOM. That's generic but could be part of About the role? Actually "Company Description Work with Us. Change the World." That's boilerplate but maybe we keep as About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description might be considered boilerplate? It's generic but maybe relevant to role. However we need to preserve ALL substantive information; company description is substantive about AECOM. It's not boilerplate like EEO. So we can include it in About the role or maybe a separate section? There's no heading for company description; we could put it under About the role. Job Description paragraph: "AECOM is seeking a Senior Traffic / Intelligent Transportation Systems (ITS) Engineer to join our growing Transportation team in Grand Rapids, Michigan . This is an opportunity for a versatile traffic engineering professional who can move comfortably between traffic safety and operations, ITS planning and design, signal systems, client management, and business development. You will work with MDOT, Michigan counties, cities, townships, and other public-sector clients to develop practical transportation solutions while helping expand AECOM’s presence throughout Southeast Michigan. The ideal candidate is a true traffic engineering generalist with strong technical depth in ITS and traffic signal systems, combined with the communication and client-facing skills needed to pursue and deliver work. You will have the opportunity to lead technical assignments, contribute to proposals and pursuits, mentor other engineers, and build relationships with transportation agencies across Michigan. Experience working with MDOT and local agencies in Southeast Michigan is highly valued." That's substantive; could be About the role. Key Responsibilities: list bullet points. Qualifications: Minimum Requirements and Preferred Qualifications. Benefits: paragraph about AECOM benefits. Pay: "Offered rate of compensation will be based on individual education, qualifications, experience, and work location. The range for this position is $135000 to $165000." Also later "Compensation: USD 135000 - USD 165000 - yearly". So we have pay. Schedule: Not given. Work Location Model: Hybrid is location model, not schedule. So we skip Schedule. Skills: Not separate. Thus output HTML with sections: About the role (

About the role

), Responsibilities (

Responsibilities

), Qualifications (

Qualifications

), Benefits (

Benefits

), Pay (

Pay

). We need to use

• for any list of duties/requirements/benefits. For prose use

  . For qualifications we have both minimum and preferred; could be a list? Might be better to keep as prose with subheadings? But we cannot add extra headings besides the allowed ones? The instruction only says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings inside? Probably we should stick to those headings only. Inside Qualifications we can have paragraphs and lists. We need to preserve all substantive info; we must not invent or summarize away detail. So we need to include all bullet points from responsibilities, qualifications, benefits. Let's extract responsibilities list: - Lead and perform traffic engineering, traffic operations, and ITS assignments for MDOT, counties, municipalities, and other public-sector clients. - Lead and support project management activities including scope and fee development, staffing, scheduling, budgeting, risk management, quality control, and client communication. - Develop and manage ITS planning and design efforts, including intelligent transportation systems architecture, communications, device deployment, systems integration, and operational strategies. - Provide construction-phase and implementation support, including field coordination, shop drawing reviews, RFIs, system integration, testing, commissioning, and acceptance of traffic signal and ITS systems. - Lead traffic signal design, signal timing, operations, optimization, and modernization projects. - Perform traffic operations analyses and develop recommendations related to intersections, corridors, signal systems, congestion, safety, and multimodal transportation. - Prepare plans, specifications, technical reports, traffic studies, design documentation, cost estimates, and other engineering deliverables. - Lead plan production and technical quality control, including design reviews, quantity development, specifications, cost estimates, constructability reviews, and resolution of agency review comments. - Serve as a technical lead and client-facing project representative on transportation projects throughout Michigan and the broader Midwest. - Develop innovative and practical solutions that integrate traffic engineering, ITS, signal systems, and transportation technology. - Support business development activities, including identifying opportunities, developing client relationships, participating in interviews, and preparing winning proposals. - Prepare and contribute to technical approaches, scopes of work, project descriptions, staff qualifications, and other proposal materials. - Candidates may be asked to provide a representative writing sample as part of the recruitment process. - Develop and maintain strong working relationships with MDOT, county road agencies, municipalities, regional transportation organizations, and other transportation stakeholders. - Coordinate with multidisciplinary teams including roadway, transportation planning, civil, electrical, technology, and construction professionals. - Mentor and provide technical guidance to junior and mid-level traffic and ITS engineers. - Support project managers with scope development, scheduling, budgeting, quality control, and client communication. - Contribute to the growth of AECOM's traffic and ITS practice in Michigan by combining technical expertise with strong client service and business development capabilities. That's a long list; we need to keep all. Qualifications: Minimum Requirements: - Bachelor’s degree in Civil Engineering from an ABET accredited university, Transportation Engineering, or related discipline and 8+ years of relevant traffic/ITS engineering experience or demonstrated equivalency of experience and/or education (working knowledge of traffic engineering design software and CAD platforms commonly used for transportation projects, such as MicroStation/OpenRoads, Synchro, and related analysis/design tools) Preferred Qualifications (list): - Significant experience in ITS planning, design, systems engineering, and implementation. - Significant experience with traffic signal design, signal operations, timing, optimization, and related systems. - Professional Engineer (PE) license and Professional Traffic Operations Engineer (PTOE) certification and / or ability to obtain a Michigan Professional Engineer (PE) license within 3 months of hire. - Demonstrated experience providing traffic engineering services for MDOT, county road agencies, municipalities, or other public-sector transportation clients. - Experience developing and maintaining relationships with transportation agencies and local governments throughout Southeast Michigan. - Experience preparing technical proposals, scopes of work, and written technical approaches for transportation pursuits; ability to provide a representative writing sample preferred. - Experience managing multiple concurrent projects and directing technical staff, including workload planning, delegation, QA/QC, and staff development. - Experience with GIS software and Building Information Modeling (BIM) tools and workflows is a plus. - Knowledge of connected and automated vehicle (CAV) technologies, vehicle-to-infrastructure (V2I) communications, and emerging transportation technology applications is a plus. - Broad traffic engineering experience across multiple areas, including traffic operations, signal systems, ITS, transportation planning, safety, and traffic analysis. - Experience with Michigan traffic engineering standards, guidelines, and agency practices. - Experience leading or mentoring technical staff; demonstrated interest in people management and team development is a plus. - Strong written, verbal, organizational, and client communication skills. Benefits: paragraph: "AECOM is proud to offer comprehensive benefits to meet the diverse needs of our employees. Depending on your employment status, AECOM benefits may include medical, dental, vision, life, AD&D, disability benefits, paid time off, leaves of absences, voluntary benefits, perks, flexible work options, well-being resources, employee assistance program, business travel insurance, service recognition awards, retirement savings plan, and employee stock purchase plan." Also earlier: "AECOM is proud to offer comprehensive benefits..." That's it. Pay: "Offered rate of compensation will be based on individual education, qualifications, experience, and work location. The range for this position is $135000 to $165000." Also later "Compensation: USD 135000 - USD 165000 - yearly". We'll include both? Might be duplicate; we should preserve all substantive info but avoid duplicated lines. The two statements are similar; we can combine into one sentence: "Offered rate of compensation will be based on individual education, qualifications, experience, and work location. The range for this position is $135,000 to $165,000 per year." We'll keep that. Also note "Work Location Model: Hybrid". That's not schedule but maybe we could include under About the role? It's location info. Could be included in About the role paragraph. We'll add a sentence: "This is a hybrid position based in Grand Rapids, Michigan." Now we need to strip boilerplate: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement, ReqID, Business Line etc. Those are metadata; we should drop them. Also "Additional Information This role does not provide Work Visa/Permit Support." That's maybe relevant? It's substantive about visa support. Should we keep? It's not boilerplate; it's a condition. Might be considered substantive. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Additional Information This role does not provide Work Visa/Permit Support." is not EEO; it's about visa support. Might be kept. Also "At AECOM, we are committed to maintaining a secure and trustworthy recruitment process and take any fraudulent hiring activity seriously. To support this commitment, all newly hired employees are required to attend an in-person Day 1 onboarding at an AECOM office location as a condition of employment." That's also substantive about onboarding requirement. Could be included maybe under About the role or a separate section? There's no heading for that; we could incorporate into About the role as a note. But we must not create sections with filler. We could add a paragraph under About the role covering these points. Let's craft About the role paragraph combining: - AECOM seeking Senior Traffic/ITS Engineer in Grand Rapids, MI. - Opportunity for versatile traffic engineering professional. - Work with MDOT, Michigan counties, cities, townships, other public-sector clients. - Ideal candidate: traffic engineering generalist with strong technical depth in ITS and traffic signal systems, plus