Senior Traffic / Intelligent Transportation Systems (ITS) Engineer
AECOM · Detroit, MI · 3 wk ago
Hybrid$135k–$165k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- Company Description (but we might not need a heading for that? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include "About the role" maybe for job description. "Company Description" could be part of "About the role" or maybe we can include a short paragraph about AECOM. But we need to preserve substantive info. The company description is substantive. Could be placed under an About the role? Or maybe we can have a heading "About AECOM"? Not in list but we can still use for any section heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples, but we should use those headings where appropriate. Probably we should include sections: About the role (or About AECOM?), Responsibilities, Qualifications (maybe split into Minimum Requirements and Preferred Qualifications), Skills (maybe not separate), Benefits, Pay.
We have 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 info.
Benefits: "AECOM is proud to offer comprehensive benefits..." includes list of benefits. So we need Benefits section.
Schedule: Not mentioned explicitly. There's "Work Location Model: Hybrid". That's schedule? Not exactly schedule (like full-time/part-time). Could be considered schedule? The instruction says never create Schedule section unless posting actually states them. It does not state schedule like hours, shift, etc. So we should not create Schedule section.
We should not include "About AECOM" as separate heading unless we map to "About the role". Could combine company description and job description under About the role.
Responsibilities: The "Key Responsibilities" bullet list.
Qualifications: Minimum Requirements and Preferred Qualifications.
Skills: Could be derived from qualifications but maybe we can include a Skills section summarizing technical skills? But we should not create thin sections. Better to keep Qualifications as one section with subpoints.
We need to preserve all substantive info. So we need to include details like: work with MDOT, etc. Also mention "Candidates may be asked to provide a representative writing sample as part of the recruitment process." That's part of qualifications? Could be under Qualifications.
Also "Additional Information" includes: no visa support, day 1 onboarding, compensation based on individual..., etc. Also "At AECOM, we are committed to maintaining a secure and trustworthy recruitment process..." That's boilerplate? It's about recruitment process, maybe we can drop as it's not substantive? It's about fraudulent hiring activity, maybe considered boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is about fraudulent hiring activity, maybe considered legal boilerplate; we can drop.
Also "Offered rate of compensation will be based on individual education, qualifications, experience, and work location." That's substantive for Pay.
Also "About AECOM" paragraph after benefits? Actually after benefits there is "About AECOM AECOM is proud to offer comprehensive benefits..." Wait that seems duplicated. Actually the text: "About AECOM 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. AECOM is the global infrastructure leader, committed to delivering a better world. As a trusted professional services firm powered by deep technical abilities, we solve our clients’ complex challenges in water, environment, energy, transportation and buildings. Our teams partner with public- and private-sector clients to create innovative, sustainable and resilient solutions throughout the project lifecycle – from advisory, planning, design and engineering to program and construction management. AECOM is a Fortune 500 firm that had revenue of $16.1 billion in fiscal year 2025. Learn more at aecom.com."
Then "What makes AECOM a great place to work ..." That's also boilerplate marketing; maybe we can drop as it's not specific to role? It's generic. The instruction says remove boilerplate. So we can drop that.
Also "ReqID: J10160674 Business Line: Transportation Business Group: DCS Strategic Business Unit: West Career Area: Engineering Work Location Model: Hybrid Compensation: USD 135000 - USD 165000 - yearly". This includes metadata; we can fold minor metadata into short
or drop it. We already have Pay section; we can include Work Location Model: Hybrid maybe as a short note under About the role or separate? Could be considered schedule? Not exactly. Might be included as a short paragraph.
We need to preserve ALL substantive information. So we need to keep Work Location Model: Hybrid. That's substantive. Could be placed under a short
after the heading maybe.
We also need to keep "Hybrid" work model.
We need to keep "Compensation: USD 135000 - USD 165000 - yearly". Already covered.
We need to keep "ReqID: J10160674" etc? That's minor metadata; we can drop or fold into short
. Probably drop as not essential.
Now produce HTML.
Structure:
About the role
Company description: AECOM ... (the paragraph). Then job description summary: AECOM is seeking a Senior Traffic / ITS Engineer ... etc. Could combine.
But we need to preserve all substantive info from job description: location Detroit, Michigan; opportunity to work with MDOT etc. So include that.
We'll write a paragraph summarizing.
Then
Responsibilities
with each responsibility as - . Need to capture all bullet points from "Key Responsibilities". Let's list them:
- 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 many items; we need to keep all.
Then
Qualifications
We can split into Minimum Requirements and Preferred Qualifications maybe as subheadings? But instruction says use for section headings; we could use Minimum Requirements and Preferred Qualifications. That's okay.
Minimum Requirements:
- Bachelor’s degree in Civil Engineering from an ABET accredited university, Transportation Engineering, or related discipline
- 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:
- 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.
We could also include "Experience preparing technical proposals..." etc.
Now Benefits section:
Benefits
list of benefits: 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, employee stock purchase plan.
We could also mention "Depending on your
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key sections: - Company Description (but we might not need a heading for that? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include "About the role" maybe for job description. "Company Description" could be part of "About the role" or maybe we can include a short paragraph about AECOM. But we need to preserve substantive info. The company description is substantive. Could be placed under an About the role? Or maybe we can have a heading "About AECOM"? Not in list but we can still use for any section heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples, but we should use those headings where appropriate. Probably we should include sections: About the role (or About AECOM?), Responsibilities, Qualifications (maybe split into Minimum Requirements and Preferred Qualifications), Skills (maybe not separate), Benefits, Pay.
We have 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 info.
Benefits: "AECOM is proud to offer comprehensive benefits..." includes list of benefits. So we need Benefits section.
Schedule: Not mentioned explicitly. There's "Work Location Model: Hybrid". That's schedule? Not exactly schedule (like full-time/part-time). Could be considered schedule? The instruction says never create Schedule section unless posting actually states them. It does not state schedule like hours, shift, etc. So we should not create Schedule section.
We should not include "About AECOM" as separate heading unless we map to "About the role". Could combine company description and job description under About the role.
Responsibilities: The "Key Responsibilities" bullet list.
Qualifications: Minimum Requirements and Preferred Qualifications.
Skills: Could be derived from qualifications but maybe we can include a Skills section summarizing technical skills? But we should not create thin sections. Better to keep Qualifications as one section with subpoints.
We need to preserve all substantive info. So we need to include details like: work with MDOT, etc. Also mention "Candidates may be asked to provide a representative writing sample as part of the recruitment process." That's part of qualifications? Could be under Qualifications.
Also "Additional Information" includes: no visa support, day 1 onboarding, compensation based on individual..., etc. Also "At AECOM, we are committed to maintaining a secure and trustworthy recruitment process..." That's boilerplate? It's about recruitment process, maybe we can drop as it's not substantive? It's about fraudulent hiring activity, maybe considered boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is about fraudulent hiring activity, maybe considered legal boilerplate; we can drop.
Also "Offered rate of compensation will be based on individual education, qualifications, experience, and work location." That's substantive for Pay.
Also "About AECOM" paragraph after benefits? Actually after benefits there is "About AECOM AECOM is proud to offer comprehensive benefits..." Wait that seems duplicated. Actually the text: "About AECOM 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. AECOM is the global infrastructure leader, committed to delivering a better world. As a trusted professional services firm powered by deep technical abilities, we solve our clients’ complex challenges in water, environment, energy, transportation and buildings. Our teams partner with public- and private-sector clients to create innovative, sustainable and resilient solutions throughout the project lifecycle – from advisory, planning, design and engineering to program and construction management. AECOM is a Fortune 500 firm that had revenue of $16.1 billion in fiscal year 2025. Learn more at aecom.com."
Then "What makes AECOM a great place to work ..." That's also boilerplate marketing; maybe we can drop as it's not specific to role? It's generic. The instruction says remove boilerplate. So we can drop that.
Also "ReqID: J10160674 Business Line: Transportation Business Group: DCS Strategic Business Unit: West Career Area: Engineering Work Location Model: Hybrid Compensation: USD 135000 - USD 165000 - yearly". This includes metadata; we can fold minor metadata into short
for any section heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples, but we should use those headings where appropriate. Probably we should include sections: About the role (or About AECOM?), Responsibilities, Qualifications (maybe split into Minimum Requirements and Preferred Qualifications), Skills (maybe not separate), Benefits, Pay.
We have 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 info.
Benefits: "AECOM is proud to offer comprehensive benefits..." includes list of benefits. So we need Benefits section.
Schedule: Not mentioned explicitly. There's "Work Location Model: Hybrid". That's schedule? Not exactly schedule (like full-time/part-time). Could be considered schedule? The instruction says never create Schedule section unless posting actually states them. It does not state schedule like hours, shift, etc. So we should not create Schedule section.
We should not include "About AECOM" as separate heading unless we map to "About the role". Could combine company description and job description under About the role.
Responsibilities: The "Key Responsibilities" bullet list.
Qualifications: Minimum Requirements and Preferred Qualifications.
Skills: Could be derived from qualifications but maybe we can include a Skills section summarizing technical skills? But we should not create thin sections. Better to keep Qualifications as one section with subpoints.
We need to preserve all substantive info. So we need to include details like: work with MDOT, etc. Also mention "Candidates may be asked to provide a representative writing sample as part of the recruitment process." That's part of qualifications? Could be under Qualifications.
Also "Additional Information" includes: no visa support, day 1 onboarding, compensation based on individual..., etc. Also "At AECOM, we are committed to maintaining a secure and trustworthy recruitment process..." That's boilerplate? It's about recruitment process, maybe we can drop as it's not substantive? It's about fraudulent hiring activity, maybe considered boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is about fraudulent hiring activity, maybe considered legal boilerplate; we can drop.
Also "Offered rate of compensation will be based on individual education, qualifications, experience, and work location." That's substantive for Pay.
Also "About AECOM" paragraph after benefits? Actually after benefits there is "About AECOM AECOM is proud to offer comprehensive benefits..." Wait that seems duplicated. Actually the text: "About AECOM 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. AECOM is the global infrastructure leader, committed to delivering a better world. As a trusted professional services firm powered by deep technical abilities, we solve our clients’ complex challenges in water, environment, energy, transportation and buildings. Our teams partner with public- and private-sector clients to create innovative, sustainable and resilient solutions throughout the project lifecycle – from advisory, planning, design and engineering to program and construction management. AECOM is a Fortune 500 firm that had revenue of $16.1 billion in fiscal year 2025. Learn more at aecom.com."
Then "What makes AECOM a great place to work ..." That's also boilerplate marketing; maybe we can drop as it's not specific to role? It's generic. The instruction says remove boilerplate. So we can drop that.
Also "ReqID: J10160674 Business Line: Transportation Business Group: DCS Strategic Business Unit: West Career Area: Engineering Work Location Model: Hybrid Compensation: USD 135000 - USD 165000 - yearly". This includes metadata; we can fold minor metadata into short
or drop it. We already have Pay section; we can include Work Location Model: Hybrid maybe as a short note under About the role or separate? Could be considered schedule? Not exactly. Might be included as a short paragraph. We need to preserve ALL substantive information. So we need to keep Work Location Model: Hybrid. That's substantive. Could be placed under a short
after the heading maybe. We also need to keep "Hybrid" work model. We need to keep "Compensation: USD 135000 - USD 165000 - yearly". Already covered. We need to keep "ReqID: J10160674" etc? That's minor metadata; we can drop or fold into short
. Probably drop as not essential. Now produce HTML. Structure:
About the role
Company description: AECOM ... (the paragraph). Then job description summary: AECOM is seeking a Senior Traffic / ITS Engineer ... etc. Could combine. But we need to preserve all substantive info from job description: location Detroit, Michigan; opportunity to work with MDOT etc. So include that. We'll write a paragraph summarizing. Then
Responsibilities
- with each responsibility as
- . Need to capture all bullet points from "Key Responsibilities". Let's list them:
- 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 many items; we need to keep all.
Then
Qualifications
We can split into Minimum Requirements and Preferred Qualifications maybe as subheadings? But instruction says usefor section headings; we could use
Minimum Requirements and
Preferred Qualifications. That's okay. Minimum Requirements: - Bachelor’s degree in Civil Engineering from an ABET accredited university, Transportation Engineering, or related discipline - 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: - 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. We could also include "Experience preparing technical proposals..." etc. Now Benefits section:
Benefits
- list of benefits: 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, employee stock purchase plan.
We could also mention "Depending on your