Senior Traffic Operations Engineer
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc as headings. Remove boilerplate. Include sections only when posting has real specific content. Must preserve all substantive info.
We need to parse the posting.
Company description: "Work with Us. Change the World. At AECOM, we're delivering a better world..." That's company description. Should we include as a section? Possibly "About the role"? Actually "About the role" is generic heading for role description. The company description could be placed under a heading like "About AECOM" but not in allowed headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only use those headings if content exists. The posting includes a "Job Description" paragraph describing role, reporting, etc. That could go under "About the role". Then "Job Responsibilities" list -> Responsibilities. Then "Qualifications" with Minimum and Preferred -> Qualifications (maybe also Requirements?). The posting also mentions "Additional Information" about visa sponsorship, onboarding, compensation range. That includes Pay info: "Offered rate of compensation will be based on individual education, qualifications, experience, and work location. The range for this position is $114000 to $140000." Also later "Compensation: USD 114000 - USD 140000 - yearly". So we have Pay section.
Schedule: The posting says "Hours are expected to cover approximately 10"30am - 630pm, Monday through Friday; however, depending on need, these hours may be adjusted." Also "Ability to work all shifts including: nights, major holidays, weekends, and planned/unplanned events" under Preferred Qualifications. So schedule info exists. We'll include Schedule section.
Benefits: The posting includes "About AECOM" paragraph about benefits: "AECOM is proud to offer comprehensive benefits...". That's benefits. So we include Benefits section.
Skills: Could be derived from Preferred Qualifications list (like strong background, experience, etc). Could also be under Qualifications. But we have Qualifications heading already; maybe we separate Skills? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to put skill-specific content under Skills. However we must not invent sections if no specific content. The posting includes many skill-like items in Preferred Qualifications: ability to work all shifts, 8+ years experience, strong background in TSMO, direct experience supporting agencies, experience with emerging traffic technology, managing teams, communication skills, familiarity with public transportation agency funding, familiarity with ITS communications. Those could be considered Skills. But also Minimum Qualifications include BA/BS + 6 years, PE license, driver's license, ability to operate computer, ability to view CCTV. Those are more qualifications.
We could treat Minimum Qualifications as Qualifications, Preferred Qualifications as Skills. Or we could combine all under Qualifications. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Qualifications and Skills into one Qualifications section. But we have both headings allowed; we need to decide.
We have Responsibilities, About the role, Qualifications, Benefits, Pay, Schedule. That's six sections. That's fine.
We must not include headings with filler text. Ensure each heading has substantive content.
Now we need to strip boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "ReqID: J10160964 Business Line: Transportation Business Group: DCS Strategic Business Unit: West Career Area: Engineering Work Location Model: On-Site Compensation: USD 114000 - USD 140000 - yearly". That's metadata; we can incorporate compensation into Pay section, but not as heading. The work location model maybe not needed.
We need to preserve all substantive information: company description, job description paragraph, responsibilities list, qualifications (min and pref), benefits description, pay range, schedule/hours.
Let's extract content.
Company Description paragraph:
"Work with Us. Change the World. At AECOM, we're delivering a better world. Whether improving your commute, keeping the lights on, providing access to clean water, or transforming skylines, our work helps people and communities thrive. We are the world's trusted infrastructure consulting firm, partnering with clients to solve the world’s most complex challenges and build legacies for future generations. There has never been a better time to be at AECOM. With accelerating infrastructure investment worldwide, our services are in great demand. We invite you to bring your bold ideas and big dreams and become part of a global team of over 50,000 planners, designers, engineers, scientists, digital innovators, program and construction managers and other professionals delivering projects that create a positive and tangible impact around the world. We're one global team driven by our common purpose to deliver a better world. Join us."
We can keep that as prose under About the role? Actually About the role should describe the role, not company. But we could put company description under About the role? Might be odd. However the instruction says use headings for sections like About the role, Responsibilities, etc. It doesn't forbid putting company description there. But maybe better to put company description under About the role as a brief intro. The role description paragraph after "Job Description" also describes role. We could combine both.
Let's parse:
After company description, there is "Job Description AECOM is actively seeking a creative, self-driven Senior Traffic Operations Engineer for employment at a client facility located in Detroit, MI. The position will report daily to on-site management and contribute to a team of traffic operations engineers, ITS technicians, and traffic signal system operators. The applicant will need to be professional, self-motivated, resourceful, and able to prioritize multiple client requests. Communication skills are paramount in this position as the qualified candidate will be expected to work with a team on complex traffic signal systems and adapt to changing conditions in a real-time environment. This position will be assigned to a PM Traffic Operations Engineer shift. Hours are expected to cover approximately 10"30am - 630pm, Monday through Friday; however, depending on need, these hours may be adjusted. Some field work, including visiting signalized intersections and troubleshooting traffic signal equipment on-site, will be included and is expected to be part of this position’s duties. The qualified candidate will be expected to be able to complete tasks independently and unsupervised at times. This position is expected to begin work immediately."
That's role details.
Then "Job Responsibilities" bullet list.
Then "Qualifications" with Minimum Qualifications and Preferred Qualifications.
Then "Additional Information" includes visa sponsorship not available, onboarding requirement, compensation range.
Then "About AECOM" paragraph about benefits and company.
Then "What makes AECOM a great place to work" paragraph about culture.
Then EEO etc.
We need to remove boilerplate: EEO, scam warning, etc. Also remove "What makes AECOM a great place to work" maybe considered boilerplate? It's promotional but still substantive about culture; could be kept under Benefits? Not exactly benefits. Could be omitted as it's fluff. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "What makes AECOM a great place to work" is not exactly boilerplate but could be considered marketing fluff. However it's substantive about work environment; but we have Benefits section for benefits; we could incorporate culture under Benefits? Not ideal. Safer to omit it as it's not strictly required and could be considered filler. The instruction says prefer a few substantive sections over many thin ones. So we could omit that paragraph.
Also remove "About AECOM" paragraph that repeats company description? Actually there is an "About AECOM" after Additional Information that talks about benefits and company. That's substantive about benefits. We'll keep that.
Now compile sections.
About the role: combine company description and job description paragraph? Might be too long but okay. Could split: About the role: job description paragraph. Company description could be omitted? But it's substantive about AECOM; maybe we could include under About the role as context. However the heading "About the role" suggests role specifics; but we can include both.
Alternatively we could not have About the role section and instead start with Responsibilities. But we need to include some intro. The instruction says use headings for sections like About the role, Responsibilities, etc. It doesn't require About the role to be present; we can omit if no real specific content. But we have role description content, so we can put that under About the role.
Thus About the role: include the Job Description paragraph (the one starting "AECOM is actively seeking...").
We might also include a brief sentence about company? But maybe not needed.
Responsibilities: list from Job Responsibilities.
Qualifications: combine Minimum and Preferred Qualifications.
Benefits: from About AECOM paragraph about benefits.
Pay: compensation range.
Schedule: hours and shift flexibility.
Now we need to format.
Use
for each heading.
Use - for any list.
Use
for prose.
We must not repeat job title as heading.
We must not include Job ID etc as headings.
We must preserve all substantive information.
Let's extract exact text.
Company description paragraph: We'll keep as is but maybe trim trailing spaces.
Job Description paragraph: "AECOM is actively seeking a creative, self-driven Senior Traffic Operations Engineer for employment at a client facility located in Detroit, MI. The position will report daily to on-site management and contribute to a team of traffic operations engineers, ITS technicians, and traffic signal system operators. The applicant will need to be professional, self-motivated, resourceful, and able to prioritize multiple client requests. Communication skills are paramount in this position as the qualified candidate will be expected to work with a team on complex traffic signal systems and adapt to changing conditions in a real-time environment. This position will be assigned to a PM Traffic Operations Engineer shift. Hours are expected to cover approximately 10"30am - 630pm, Monday through Friday; however, depending on need, these hours may be adjusted. Some field work, including visiting signalized intersections and troubleshooting traffic signal equipment on-site, will be included and is expected to be part of this position’s duties. The qualified candidate will be expected to be able to complete tasks independently and unsupervised at times. This position is expected to begin work immediately."
Note there is a weird quote: 10"30am - 630pm (should be 10:30am - 6:30pm). We'll keep as given.
Responsibilities list:
- Lead and support a team of on-site Traffic Operations Engineers to deliver real-time traffic operations services for the client
- Coordinate and support the On-site Operations Manager and Project Management teams to complete assigned tasks
- Review and/or support development of actuated/coordinated traffic signal timing plans, develop timing databases, and coordinate with agency staff to determine implementation needs/desires
- Lead before-after traffic engineering studies to evaluate and analyze in-field traffic conditions, including using technical data sources and traffic management system software
- Use traffic signal equipment, technology, and software systems to manage the traffic signal network from the operations center
- Review and evaluate planned and unplanned events to assess changing traffic conditions and altering traffic patterns and evaluate, in real time, potential changes to traffic signal timing as appropriate
- Lead preparation and development of various written reports, memos, and verbal presentations
- Support AECOM QA/QC best practices
Qualifications:
Minimum Qualifications:
- BA/BS + 6 Years of experience or
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc as headings. Remove boilerplate. Include sections only when posting has real specific content. Must preserve all substantive info. We need to parse the posting. Company description: "Work with Us. Change the World. At AECOM, we're delivering a better world..." That's company description. Should we include as a section? Possibly "About the role"? Actually "About the role" is generic heading for role description. The company description could be placed under a heading like "About AECOM" but not in allowed headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only use those headings if content exists. The posting includes a "Job Description" paragraph describing role, reporting, etc. That could go under "About the role". Then "Job Responsibilities" list -> Responsibilities. Then "Qualifications" with Minimum and Preferred -> Qualifications (maybe also Requirements?). The posting also mentions "Additional Information" about visa sponsorship, onboarding, compensation range. That includes Pay info: "Offered rate of compensation will be based on individual education, qualifications, experience, and work location. The range for this position is $114000 to $140000." Also later "Compensation: USD 114000 - USD 140000 - yearly". So we have Pay section. Schedule: The posting says "Hours are expected to cover approximately 10"30am - 630pm, Monday through Friday; however, depending on need, these hours may be adjusted." Also "Ability to work all shifts including: nights, major holidays, weekends, and planned/unplanned events" under Preferred Qualifications. So schedule info exists. We'll include Schedule section. Benefits: The posting includes "About AECOM" paragraph about benefits: "AECOM is proud to offer comprehensive benefits...". That's benefits. So we include Benefits section. Skills: Could be derived from Preferred Qualifications list (like strong background, experience, etc). Could also be under Qualifications. But we have Qualifications heading already; maybe we separate Skills? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to put skill-specific content under Skills. However we must not invent sections if no specific content. The posting includes many skill-like items in Preferred Qualifications: ability to work all shifts, 8+ years experience, strong background in TSMO, direct experience supporting agencies, experience with emerging traffic technology, managing teams, communication skills, familiarity with public transportation agency funding, familiarity with ITS communications. Those could be considered Skills. But also Minimum Qualifications include BA/BS + 6 years, PE license, driver's license, ability to operate computer, ability to view CCTV. Those are more qualifications. We could treat Minimum Qualifications as Qualifications, Preferred Qualifications as Skills. Or we could combine all under Qualifications. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Qualifications and Skills into one Qualifications section. But we have both headings allowed; we need to decide. We have Responsibilities, About the role, Qualifications, Benefits, Pay, Schedule. That's six sections. That's fine. We must not include headings with filler text. Ensure each heading has substantive content. Now we need to strip boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "ReqID: J10160964 Business Line: Transportation Business Group: DCS Strategic Business Unit: West Career Area: Engineering Work Location Model: On-Site Compensation: USD 114000 - USD 140000 - yearly". That's metadata; we can incorporate compensation into Pay section, but not as heading. The work location model maybe not needed. We need to preserve all substantive information: company description, job description paragraph, responsibilities list, qualifications (min and pref), benefits description, pay range, schedule/hours. Let's extract content. Company Description paragraph: "Work with Us. Change the World. At AECOM, we're delivering a better world. Whether improving your commute, keeping the lights on, providing access to clean water, or transforming skylines, our work helps people and communities thrive. We are the world's trusted infrastructure consulting firm, partnering with clients to solve the world’s most complex challenges and build legacies for future generations. There has never been a better time to be at AECOM. With accelerating infrastructure investment worldwide, our services are in great demand. We invite you to bring your bold ideas and big dreams and become part of a global team of over 50,000 planners, designers, engineers, scientists, digital innovators, program and construction managers and other professionals delivering projects that create a positive and tangible impact around the world. We're one global team driven by our common purpose to deliver a better world. Join us." We can keep that as prose under About the role? Actually About the role should describe the role, not company. But we could put company description under About the role? Might be odd. However the instruction says use headings for sections like About the role, Responsibilities, etc. It doesn't forbid putting company description there. But maybe better to put company description under About the role as a brief intro. The role description paragraph after "Job Description" also describes role. We could combine both. Let's parse: After company description, there is "Job Description AECOM is actively seeking a creative, self-driven Senior Traffic Operations Engineer for employment at a client facility located in Detroit, MI. The position will report daily to on-site management and contribute to a team of traffic operations engineers, ITS technicians, and traffic signal system operators. The applicant will need to be professional, self-motivated, resourceful, and able to prioritize multiple client requests. Communication skills are paramount in this position as the qualified candidate will be expected to work with a team on complex traffic signal systems and adapt to changing conditions in a real-time environment. This position will be assigned to a PM Traffic Operations Engineer shift. Hours are expected to cover approximately 10"30am - 630pm, Monday through Friday; however, depending on need, these hours may be adjusted. Some field work, including visiting signalized intersections and troubleshooting traffic signal equipment on-site, will be included and is expected to be part of this position’s duties. The qualified candidate will be expected to be able to complete tasks independently and unsupervised at times. This position is expected to begin work immediately." That's role details. Then "Job Responsibilities" bullet list. Then "Qualifications" with Minimum Qualifications and Preferred Qualifications. Then "Additional Information" includes visa sponsorship not available, onboarding requirement, compensation range. Then "About AECOM" paragraph about benefits and company. Then "What makes AECOM a great place to work" paragraph about culture. Then EEO etc. We need to remove boilerplate: EEO, scam warning, etc. Also remove "What makes AECOM a great place to work" maybe considered boilerplate? It's promotional but still substantive about culture; could be kept under Benefits? Not exactly benefits. Could be omitted as it's fluff. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "What makes AECOM a great place to work" is not exactly boilerplate but could be considered marketing fluff. However it's substantive about work environment; but we have Benefits section for benefits; we could incorporate culture under Benefits? Not ideal. Safer to omit it as it's not strictly required and could be considered filler. The instruction says prefer a few substantive sections over many thin ones. So we could omit that paragraph. Also remove "About AECOM" paragraph that repeats company description? Actually there is an "About AECOM" after Additional Information that talks about benefits and company. That's substantive about benefits. We'll keep that. Now compile sections. About the role: combine company description and job description paragraph? Might be too long but okay. Could split: About the role: job description paragraph. Company description could be omitted? But it's substantive about AECOM; maybe we could include under About the role as context. However the heading "About the role" suggests role specifics; but we can include both. Alternatively we could not have About the role section and instead start with Responsibilities. But we need to include some intro. The instruction says use headings for sections like About the role, Responsibilities, etc. It doesn't require About the role to be present; we can omit if no real specific content. But we have role description content, so we can put that under About the role. Thus About the role: include the Job Description paragraph (the one starting "AECOM is actively seeking..."). We might also include a brief sentence about company? But maybe not needed. Responsibilities: list from Job Responsibilities. Qualifications: combine Minimum and Preferred Qualifications. Benefits: from About AECOM paragraph about benefits. Pay: compensation range. Schedule: hours and shift flexibility. Now we need to format. Use
for each heading.
Use - for any list.
Use
for prose.
We must not repeat job title as heading.
We must not include Job ID etc as headings.
We must preserve all substantive information.
Let's extract exact text.
Company description paragraph: We'll keep as is but maybe trim trailing spaces.
Job Description paragraph: "AECOM is actively seeking a creative, self-driven Senior Traffic Operations Engineer for employment at a client facility located in Detroit, MI. The position will report daily to on-site management and contribute to a team of traffic operations engineers, ITS technicians, and traffic signal system operators. The applicant will need to be professional, self-motivated, resourceful, and able to prioritize multiple client requests. Communication skills are paramount in this position as the qualified candidate will be expected to work with a team on complex traffic signal systems and adapt to changing conditions in a real-time environment. This position will be assigned to a PM Traffic Operations Engineer shift. Hours are expected to cover approximately 10"30am - 630pm, Monday through Friday; however, depending on need, these hours may be adjusted. Some field work, including visiting signalized intersections and troubleshooting traffic signal equipment on-site, will be included and is expected to be part of this position’s duties. The qualified candidate will be expected to be able to complete tasks independently and unsupervised at times. This position is expected to begin work immediately."
Note there is a weird quote: 10"30am - 630pm (should be 10:30am - 6:30pm). We'll keep as given.
Responsibilities list:
- Lead and support a team of on-site Traffic Operations Engineers to deliver real-time traffic operations services for the client
- Coordinate and support the On-site Operations Manager and Project Management teams to complete assigned tasks
- Review and/or support development of actuated/coordinated traffic signal timing plans, develop timing databases, and coordinate with agency staff to determine implementation needs/desires
- Lead before-after traffic engineering studies to evaluate and analyze in-field traffic conditions, including using technical data sources and traffic management system software
- Use traffic signal equipment, technology, and software systems to manage the traffic signal network from the operations center
- Review and evaluate planned and unplanned events to assess changing traffic conditions and altering traffic patterns and evaluate, in real time, potential changes to traffic signal timing as appropriate
- Lead preparation and development of various written reports, memos, and verbal presentations
- Support AECOM QA/QC best practices
Qualifications:
Minimum Qualifications:
- BA/BS + 6 Years of experience or
for prose. We must not repeat job title as heading. We must not include Job ID etc as headings. We must preserve all substantive information. Let's extract exact text. Company description paragraph: We'll keep as is but maybe trim trailing spaces. Job Description paragraph: "AECOM is actively seeking a creative, self-driven Senior Traffic Operations Engineer for employment at a client facility located in Detroit, MI. The position will report daily to on-site management and contribute to a team of traffic operations engineers, ITS technicians, and traffic signal system operators. The applicant will need to be professional, self-motivated, resourceful, and able to prioritize multiple client requests. Communication skills are paramount in this position as the qualified candidate will be expected to work with a team on complex traffic signal systems and adapt to changing conditions in a real-time environment. This position will be assigned to a PM Traffic Operations Engineer shift. Hours are expected to cover approximately 10"30am - 630pm, Monday through Friday; however, depending on need, these hours may be adjusted. Some field work, including visiting signalized intersections and troubleshooting traffic signal equipment on-site, will be included and is expected to be part of this position’s duties. The qualified candidate will be expected to be able to complete tasks independently and unsupervised at times. This position is expected to begin work immediately." Note there is a weird quote: 10"30am - 630pm (should be 10:30am - 6:30pm). We'll keep as given. Responsibilities list: - Lead and support a team of on-site Traffic Operations Engineers to deliver real-time traffic operations services for the client - Coordinate and support the On-site Operations Manager and Project Management teams to complete assigned tasks - Review and/or support development of actuated/coordinated traffic signal timing plans, develop timing databases, and coordinate with agency staff to determine implementation needs/desires - Lead before-after traffic engineering studies to evaluate and analyze in-field traffic conditions, including using technical data sources and traffic management system software - Use traffic signal equipment, technology, and software systems to manage the traffic signal network from the operations center - Review and evaluate planned and unplanned events to assess changing traffic conditions and altering traffic patterns and evaluate, in real time, potential changes to traffic signal timing as appropriate - Lead preparation and development of various written reports, memos, and verbal presentations - Support AECOM QA/QC best practices Qualifications: Minimum Qualifications: - BA/BS + 6 Years of experience or