Traffic Analyst Interview Questions
For technicians who study road traffic under a traffic engineer. Interviews focus on analyzing traffic data, drafting signal layouts, and responding to public concerns.
30 questions, ranked by what the job needs most
Also for Traffic Analyst: Shipping, Receiving, and Traffic Clerks · compare them →
Print the top 10:Scoring sheetPractice sheet
Question 1: Describe a time you checked whether drivers could see signs or lane markings after dark.
Interviewer tipListen for a firsthand observation from the driver's approach and a specific finding the candidate recorded. A daylight check alone can't establish whether a sign or marking is visible after dark.
Candidate tipPick one field check and describe the lighting, the sign or marking you checked, and where you observed it from. Explain what you recorded about its visibility to approaching drivers.
Question 2: Walk me through a drawing you prepared for a proposed traffic signal installation.
Interviewer tipListen for what they drew themselves and how they checked that the proposed poles were in the right place on the plan. Flag an answer that treats a rough sketch as a finished drawing.
Candidate tipA drawing from a drafting course or internship works, too. Say which part of the signal layout you drew, which measurements or notes you used, and what you checked before handing it over.
Question 3: How do you handle a resident who calls to complain about a traffic signal, speeding on their street or a new parking rule?
Example answerThe interviewer wants to see that you can stay patient with upset residents, explain traffic rules and studies in plain words, and follow through. Describe the steps you take, then give a short example. Listen first and let the caller finish. Ask where and when the problem happens. Check what the agency already knows, such as past counts or studies. Explain what the policy allows, what happens next and who decides. Sample answer: "A resident called, angry about cars speeding past a school on their street, and asked for speed bumps. I let them explain, then asked which times of day were worst. We had no recent speed data there, so I told them I would set out a counter for a week and explained that our policy uses that data to decide on traffic calming. I called them back with the results and the engineer's decision, even though it wasn't the answer they hoped for." Pitfalls: promising a sign or signal you can't approve, hiding behind policy without explaining it, and never calling back.
Interviewer tipListen for how they explain the agency's rules and studies in plain terms and follow up; arguing, or promising changes they can't approve, is a red flag.
Candidate tipDescribe your steps: listen, check the facts such as counts or past studies, explain what the policy allows, and say how you follow up or pass it to the engineer.
Question 4: What's the hardest part of planning a signal upgrade for an intersection that's expected to get busier?
Interviewer tipA strong answer shows how changes for one movement through the intersection affect other drivers or people crossing. Dismissing pedestrian crossing time to move more cars is a red flag.
Candidate tipName one design trade-off, such as giving more green time to a busy turn while leaving enough time for people to cross. Explain what makes it hard to meet both needs as traffic grows.
Question 5: What do you look for in traffic data before recommending a way to ease a recurring backup at an intersection?
Interviewer tipListen for a link between where and when vehicles back up, the turning counts, and the proposed fix. Relying on the daily traffic total alone can hide the busiest hour.
Candidate tipExplain which turning counts and lengths of waiting traffic you'd compare by time of day. Show how the pattern you find would guide your recommendation.
Question 6: Share an example of a time you kept an accurate traffic count when several vehicle or pedestrian movements happened at once.
Interviewer tipListen for their own use of the counter and movement categories, plus the result and a lesson from the count. Claiming to count movements they could not observe is a red flag.
Candidate tipChoose one busy count. Describe the movements you had to record, how you used the counter to keep them separate, and how the count turned out. Mention a lesson you took into your next count.
Question 7: Tell me about a time you caught an error in a signal timing sheet, count summary or drawing before it reached the engineer or the field.
Example answerThe interviewer wants to learn whether you check your work before it can cause problems in the field. Use Situation, Task, Action, Result. Describe the error, how you found it, what could have gone wrong, and what you did to prevent a repeat. Sample answer: "I was preparing a timing sheet for a signal after an intersection was restriped. Before sending it to the engineer, I compared the sheet with the new striping drawing, as I always do. The pedestrian clearance time was still based on the old crosswalk, which was now longer. If it had gone to the field, people crossing would have had too little time. I recalculated the clearance for the new distance and noted the change for the engineer. Afterward I added a step to my checklist to confirm crossing distances against the latest drawing." Pitfalls: failing to verify or correct the error, blaming a coworker for the mistake, and leaving out what you changed in your own process.
Interviewer tipListen for how they verified and corrected the timing sheet, count summary or drawing, plus steps to prevent a repeat. Passing along an unverified error is a red flag.
Candidate tipSay what the error was, how you noticed it, what could have happened if it got through, and what you changed in your own checking afterwards.
Question 8: What would you do if you were asked to write a work order for a damaged traffic sign but the report did not clearly identify its location?
Interviewer tipA sound answer confirms the sign and location before sending a crew and alerts the supervisor if the damage may put road users at risk. Guessing the location on the work order is a red flag.
Candidate tipStart with how you would confirm which sign needs repair. Explain how you would flag any immediate safety concern and give the crew a work order with a clear location and repair request.
Question 9: Share an example of how you managed a large volume of traffic count or speed data for an engineering report.
Example answerThe interviewer wants to know how you keep a large traffic dataset organized and usable for an engineering report.
Use Situation, Task, Action, Result. Describe the data's scope, your responsibility, the system you used to organize and process it, and the effect on the final report. Include checks without making error detection the whole answer.
Sample answer: "I received traffic counts from several intersections for the same study period. I kept the raw files unchanged and organized working copies by site, direction and collection date. A tracking sheet showed which files had been imported, checked and summarized. While reviewing the hourly totals, I found a period with almost no traffic in one direction and confirmed a tube had come loose. I marked those hours as unusable and arranged a recount. The tracking sheet kept that site from being included as complete while I finished the other summaries for the engineer."
Avoid losing the link to the source files, filling gaps by guessing or leaving out how your approach affected the report. Use your own example and actual responsibilities.
Interviewer tipA strong example shows how they kept a large traffic dataset organized, checked and traceable through reporting. Losing track of sites or silently omitting records is a red flag.
Candidate tipDescribe the size and scope of the data, how you organized files by site and time, and how you tracked processing and checks. End with the effect on the report's accuracy or delivery.
Question 10: Tell me about a time traffic counts, speed data or crash records helped you recommend a fix for a problem location.
Example answerThe interviewer wants to learn how you connect traffic evidence to a practical recommendation for an engineer's review.
Use Situation, Task, Action, Result. Describe the location, your role and the data you gathered. Explain how each option addressed the observed problem, what the engineer decided and how you followed up.
Sample answer: "Drivers reported backups at a left turn into a shopping area. I collected peak-period turning counts and queue observations and reviewed crash records. The turn queue extended beyond the storage bay, and rear-end crashes were reported near the queue. I compared extending the bay with a timing review. More storage could keep waiting vehicles out of the through lane, while timing changes needed review for effects on other movements. I recommended that the engineer evaluate a longer bay. I did not recommend a protected phase based on rear-end records alone. After the engineer approved a storage change, I collected follow-up queue observations for their review."
Avoid choosing a treatment before reviewing the evidence. Don't assume one crash pattern supports every signal change. Don't omit the engineer's decision or follow-up.
Interviewer tipLook for an answer that ties the data to the choice, such as counts showing a turn lane was needed, and weighs other options; a fix picked before looking at data is a red flag.
Candidate tipName the location and problem, the data you pulled, the options you compared, and why you recommended the one you did. Say what the engineer decided and how it worked out.
Question 11: Walk me through a time you combined traffic counts from sources that used different vehicle categories into one computer file.
Interviewer tipA strong example shows how they matched source categories to the file's codes and handled categories that did not match. Combining unlike categories without noting the difference is a red flag; ask what they learned.
Candidate tipName the count sources and the category mismatch. Focus on how you matched the codes, kept track of any limits, and produced the file. End with the result and anything you would change next time.
Question 12: Describe a time you turned traffic study results into a chart or diagram that helped an engineer see a pattern.
Interviewer tipListen for a real pattern, their choice of chart or diagram, and how the engineer used it. Missing units or labels that change the meaning are red flags. Ask what they would improve.
Candidate tipBriefly explain the traffic study and the pattern you needed to show. Describe your chart or diagram, including its labels and scale, then say how the engineer used it and what you learned.
Question 13: Describe an experience when you measured and recorded the speed of vehicular traffic, using electrical timing devices or radar equipment.
Question 14: What have you found to be the best way to study traffic delays by noting times of delays, the numbers of vehicles affected, and vehicle speed through the delay area?
Question 15: How often do you visit development or work sites to determine projects' effect on traffic and the adequacy of traffic control and safety plans or to suggest traffic control measures?
Question 16: Share an effective approach to review traffic control or barricade plans to issue permits for parades or other special events or for construction work that affects rights of way, providing assistance with plan preparation or revision, as necessary.
Question 17: Name a time when you monitored street or utility projects for compliance to traffic control permit conditions.
Question 18: Walk me through how yo would compute time settings for traffic signals or speed restrictions, using standard formulas.
Question 19: What is the most challenging part of establishing procedures for street closures or for repair or construction projects?
Question 20: Name a time when you maintained or made minor adjustments or field repairs to equipment used in surveys, including the replacement of parts on traffic data gathering devices.
Question 21: Describe a time a contractor or permit holder pushed back when you told them their work zone traffic control didn't meet the permit.
Example answerThe interviewer wants to see that you can enforce permit conditions calmly and firmly when a contractor disagrees. Use Situation, Task, Action, Result. Say what was wrong with the work zone, how the contractor reacted, how you kept the talk on safety and the permit, and how it ended. Sample answer: "On a utility job, the crew had closed a lane, but the advance warning signs were missing and the taper was too short. When I pointed it out, the foreman said they would only be there an hour and didn't need signs. I stayed calm, showed the permit conditions and the approved traffic control plan, and explained that drivers were coming around a curve with little warning. I immediately notified my supervisor of the active hazard and asked the foreman to pause the work while the crew restored protection under the approved traffic control plan. I kept the discussion on driver safety rather than arguing about how long the job would take. The crew installed the signs and corrected the taper before work resumed. I noted the visit in the permit file." Pitfalls: arguing or getting personal, backing down on a real safety problem, and not documenting what happened.
Interviewer tipListen for whether they stayed calm, pointed to the permit conditions and public safety, and knew when to bring in a supervisor; backing down on a safety issue is a red flag.
Candidate tipExplain what was wrong at the site, what the contractor said, how you kept the talk on the permit and public safety, and how it was resolved.
Question 22: How do you plan your week when you have traffic counts to set out, work orders to write and permit plans waiting for review?
Interviewer tipA strong answer puts safety items and permit deadlines first and plans around counting windows and weather; working strictly in the order things arrive is a red flag.
Candidate tipWalk through how you rank the work: safety issues and permit deadlines, count windows that can't move, then the rest. Mention how you track it all.
Question 23: Share an experience in which your diligence of inspecting equipment, structures, or materials helped you identify a problem or the cause of a problem.
Example answerThe interviewer wants evidence that you inspect carefully and that your checks catch problems before they grow.
Use Situation, Task, Action, Result. Say what you were inspecting and why, what you noticed, how you traced the cause, and what happened after you reported or fixed it.
Sample answer: "During a routine walk-through, I noticed a small puddle of fluid under one of our machines. It wasn't on the checklist, but I wiped it up and checked again an hour later, and it was back. I followed the line and found a fitting that had worked loose. I tagged the machine, reported it to my supervisor, and maintenance replaced the fitting before the end of the shift. If it had failed during a full run, we would likely have lost most of a day."
Pitfalls: Don't claim you never miss anything. Avoid stories where you found a problem but didn't report it. Don't skip how you confirmed the cause.
Question 24: Describe an experience when you provided technical supervision regarding traffic control devices to other traffic technicians or laborers.
Question 25: Provide a time when you were able to identify a complex problem, evaluate the options, and implement a solution. How did the solution benefit your employer?
Example answerThe interviewer wants to see how you handle problems with many parts: how you break them down, choose a path, and follow through.
Use Situation, Task, Action, Result. Explain why the problem was complex, such as several causes or many people affected. Walk through how you found the root cause, the options you weighed, and how you put the solution in place. End with the benefit to your employer.
Sample answer: "Our monthly billing kept going out late. The cause wasn't one thing: data arrived late from two departments, and the billing software needed manual fixes. I mapped each step, timed them, and found the manual fixes took the most time. I compared hiring temporary help with automating the fixes, and we chose automation with help from our technology team. Billing went out on time for the next three months, and customers paid faster."
Pitfalls: Don't pick a simple problem and call it complex. Avoid skipping the options you considered. Don't take credit for others' work; name who helped.
Question 26: Tell me about a time when your ability to analyze needs and product requirements helped you create an effective design or make an informed decision to benefit your company.
Example answerThe interviewer wants to see how you find out what is really needed before you design something or make a decision.
Use Situation, Task, Action, Result. Explain how you gathered the needs or requirements, how you weighed them, the design or decision you reached, and how it helped the company.
Sample answer: "Our team was asked to choose a new tool for tracking customer requests. Instead of starting with product demos, I talked to the people who would use it every day and listed what they needed most: quick search, simple tags, and reports for managers. I scored three options against that list and shared the results. We chose the one that fit the daily work best, even though it had fewer extra features. People were using it within a week, and we didn't need a second round of training."
Pitfalls: Don't jump to the solution without showing how you learned the needs. Avoid a decision made only on cost or personal preference. Don't skip the benefit to the company.
Question 27: Provide an example of a time when you were able to demonstrate excellent listening skills. What was the situation and outcome?
Example answerThe interviewer wants evidence that you listen to understand, not just to reply, and that it makes a difference to your work.
Use Situation, Task, Action, Result. Show what careful listening looked like: letting the person finish, asking follow-up questions, and repeating back what you heard. The outcome should show that listening caught something you would otherwise have missed.
Sample answer: "A manager from another department asked for a monthly report and said they wanted it faster. Instead of starting right away, I asked what they used the report for. They mentioned twice that they only looked at two of the columns. I confirmed that with them, built a one-page summary of just those figures, and it took a third of the time to produce. They used the summary format from then on."
Pitfalls: Don't just describe yourself as a good listener without an example. Avoid an answer where you talk mostly about what you said. Don't leave out the outcome the question asks for.
Question 28: Provide a time when you dealt calmly and effectively with a high-stress situation.
Example answerThe interviewer wants to see how you think and act under pressure, and whether you stay effective when things go wrong.
Use Situation, Task, Action, Result. Set the scene quickly: what made it stressful and what was at stake. Spend most of your answer on what you did: how you steadied yourself, what you dealt with first, and who you told. Close with the outcome and what you would repeat.
Sample answer: "An hour before a client presentation, the file with our final numbers was corrupted. I told the team we had a problem and a plan, split the work so two of us rebuilt the charts from the source data while another person checked them, and let the client know we might start a few minutes late. We started on time, and afterward we set up automatic backups for shared files."
Pitfalls: Don't say you never feel stress. Avoid stories where the stress came from your own avoidable mistake unless you explain what you changed. Don't skip the result.
Question 29: Provide an experience that demonstrates your ability to manage time effectively. What were the challenges and results?
Example answerThe interviewer wants to know how you plan your time and handle competing demands, and whether you meet deadlines.
Use Situation, Task, Action, Result. Name the specific challenges, such as overlapping deadlines or interruptions. Describe the steps you took to plan and protect your time, and what you did when something came up. End with the results the question asks for.
Sample answer: "During one busy week, I had a report due Thursday, two new team members to train, and my usual daily tasks. I mapped out the week on Monday, scheduled training for the mornings when things were quieter, and blocked two afternoons for the report. When an urgent request came in Wednesday, I asked a colleague to cover one training session. The report went in a day early, and both new team members finished their training on schedule."
Pitfalls: Don't just list time-management tools. Avoid a story where you met the deadline only by working through the night. Don't skip the challenges.
Question 30: Share an experience in which your understanding of a current or upcoming problem helped your company to respond to the problem.
Example answerThe interviewer wants to see that you keep up with what is happening around your work and use that knowledge to help the organization prepare.
Use Situation, Task, Action, Result. Explain what the problem was, how you came to understand it early (reading, training, talking with others), what you recommended, and how the organization responded.
Sample answer: "I read in an industry newsletter that a key supplier planned to stop making a part we used in several products. I checked with our purchasing team, confirmed the news, and researched two replacement parts. I shared a short summary with my manager, and we ordered extra stock of the old part while we tested a replacement. When the supplier stopped production months later, we switched over without any delays to customers."
Pitfalls: Don't take credit for spotting something everyone already knew. Avoid a story where you noticed the problem but did nothing. Don't leave out how you learned about it.