TMC Operator I
for sections present: About the role? The posting includes "What You Will Do", "What You’ll Be Challenged To Do", "Education | Experience: What You Will Bring To Our Firm", "What We Prefer You Bring", "Compensation: Status:", "Featured Benefits", "Company Overview", "Location: Nashville, TN Core Business Hours: 24/7/365 operational coverage for assigned shifts. Employment Status: Full-Time". Also "Compensation: Status:" includes contingent upon contract award etc. Not actual pay or schedule details. So we should not create Pay or Schedule sections because no specific pay or schedule given. Benefits: there is "Featured Benefits" list. So we can have Benefits section.
We need to use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose appropriate headings based on content. For responsibilities: "What You Will Do" and "What You’ll Be Challenged To Do" both describe duties. Could combine into Responsibilities section.
Requirements/Education: "Education | Experience: What You Will Bring To Our Firm" and "What We Prefer You Bring" could be Qualifications or Requirements.
Skills: maybe include "Ability to work rotating shifts..." etc.
We need to preserve all substantive info, not invent. Remove boilerplate: EEO, unsolicited resumes, background check, etc. Also remove navigation, cookie, legal, duplicated lines. Also remove the video link and emojis? Probably remove the 📣 Watch Traffic Management Video! line.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content:
Job title: FULL TIME Traffic Dispatcher (Systems Operator I - Trainee) – but we do not repeat as heading.
Location: Nashville, TN (onsite regular attendance). Also mention Core Business Hours: 24/7/365 operational coverage for assigned shifts. Employment Status: Full-Time.
We can include location and maybe schedule? But schedule not specific; we have 24/7/365 coverage but not a specific schedule. Might be considered schedule info? The rule: do NOT create Pay/Schedule/Benefits sections unless posting actually states them. It states "Core Business Hours: 24/7/365 operational coverage for assigned shifts." That is schedule info. So we could create a Schedule section with that detail. However the rule says: 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. It does state schedule info, so we can include Schedule section.
But we need to decide if we want to include Schedule. The posting says "Core Business Hours: 24/7/365 operational coverage for assigned shifts." That's a schedule description. So we can include Schedule Schedule
Schedule
Core Business Hours: 24/7/365 operational coverage for assigned shifts.
Pay: there is no specific pay, only "Traffic Dispatchers are eligible for pay increases upon successful completion of each training level." That's not a specific pay amount or range. The rule says do NOT create Pay section unless posting actually states them. It does not state a specific pay, just eligibility for increases. Likely we should not create Pay section. Benefits: we have "Featured Benefits Hybrid (in-person and remote) work environment.Comprehensive benefits package including wellness programs, parental leave, and pet insurance, in addition to medical, dental, vision, disability, and life insurance.Tax-deferred 401(k) savings plan.Competitive paid-time-off (PTO) accrual.Tuition reimbursement for continued education.Commitment to professional development, access to internal and external training programs, and support of active participation in professional organizationsIncentive compensation for eligible positions." We can list as- ...
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings when appropriate. We can also use other headings if needed? The instruction says use for section headings (e.g. ...). It doesn't forbid other headings, but to be safe we stick to those.
Thus we need to map:
- About the role: could include brief description of role and company overview? The posting includes "What You Will Do" and "What You’ll Be Challenged To Do". That's responsibilities. So About the role could be a short summary: "GFT is seeking a FULL TIME Traffic Dispatcher (Systems Operator I - Trainee) for the Regional Traffic Management (TMC) Center in the Tennessee State Department of Transportation (TDOT) office located in Nashville, TN." plus maybe company overview. We'll include that.
- Responsibilities: list duties from "What You’ll Be Challenged To Do" and maybe also from "What You Will Do". We'll combine.
- Requirements: Education and Experience: "Education | Experience: What You Will Bring To Our Firm". Also maybe "What We Prefer You Bring" could be Qualifications or Skills. We'll treat Requirements as mandatory: High School Diploma or GED required; Associate degree preferred; Minimum of one (1) year experience in traffic operations, transportation management, dispatching, emergency communications, public safety, customer service, or related technical operations environment; Ability to work rotating shifts, weekends, holidays, overtime, and emergency activations; Strong written and verbal communication skills; Ability to multitask in a fast-paced operational environment; Proficiency with computer systems and Microsoft Office applications.
- Qualifications: "What We Prefer You Bring": Experience working in a TMC, TOCC, 911 Dispatch, EOC, or similar; Knowledge of ICS; National TIM training; Experience with ITS technologies; Certifications related to transportation operations, emergency management, or public safety communications; Good Customer Service.
- Skills: maybe combine some overlapping? Could include "Ability to multitask..." etc but that's already in Requirements. Could put technical skills: Proficiency with computer systems and Microsoft Office; Ability to operate ATMS; etc. But we already have those. Might not need separate Skills section if thin. But we can include Skills: "Proficiency with computer systems and Microsoft Office applications; Ability to operate Advanced Traffic Management Software (ATMS) and associated TMC systems; Strong written and verbal communication skills; Ability to multitask in fast-paced environment." However we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But they ask to use headings for those categories. We'll create Requirements (mandatory) and Qualifications (preferred). That's two sections.
- Benefits: as described.
- Schedule: "Core Business Hours: 24/7/365 operational coverage for assigned shifts."
- Pay: not included.
Now we need to remove boilerplate: EEO, unsolicited resumes, background check, etc. Also remove "Location: Nashville, TN Core Business Hours: 24/7/365 operational coverage for assigned shifts. Employment Status: Full-Time." We'll keep location maybe in About the role or separate? Not a heading. Could embed location in About the role paragraph.
We also need to remove duplicated lines. Ensure we preserve all substantive info.
Let's craft HTML:
About the role
for section headings (e.g. ...). It doesn't forbid other headings, but to be safe we stick to those.
Thus we need to map:
- About the role: could include brief description of role and company overview? The posting includes "What You Will Do" and "What You’ll Be Challenged To Do". That's responsibilities. So About the role could be a short summary: "GFT is seeking a FULL TIME Traffic Dispatcher (Systems Operator I - Trainee) for the Regional Traffic Management (TMC) Center in the Tennessee State Department of Transportation (TDOT) office located in Nashville, TN." plus maybe company overview. We'll include that.
- Responsibilities: list duties from "What You’ll Be Challenged To Do" and maybe also from "What You Will Do". We'll combine.
- Requirements: Education and Experience: "Education | Experience: What You Will Bring To Our Firm". Also maybe "What We Prefer You Bring" could be Qualifications or Skills. We'll treat Requirements as mandatory: High School Diploma or GED required; Associate degree preferred; Minimum of one (1) year experience in traffic operations, transportation management, dispatching, emergency communications, public safety, customer service, or related technical operations environment; Ability to work rotating shifts, weekends, holidays, overtime, and emergency activations; Strong written and verbal communication skills; Ability to multitask in a fast-paced operational environment; Proficiency with computer systems and Microsoft Office applications.
- Qualifications: "What We Prefer You Bring": Experience working in a TMC, TOCC, 911 Dispatch, EOC, or similar; Knowledge of ICS; National TIM training; Experience with ITS technologies; Certifications related to transportation operations, emergency management, or public safety communications; Good Customer Service.
- Skills: maybe combine some overlapping? Could include "Ability to multitask..." etc but that's already in Requirements. Could put technical skills: Proficiency with computer systems and Microsoft Office; Ability to operate ATMS; etc. But we already have those. Might not need separate Skills section if thin. But we can include Skills: "Proficiency with computer systems and Microsoft Office applications; Ability to operate Advanced Traffic Management Software (ATMS) and associated TMC systems; Strong written and verbal communication skills; Ability to multitask in fast-paced environment." However we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But they ask to use headings for those categories. We'll create Requirements (mandatory) and Qualifications (preferred). That's two sections.
- Benefits: as described.
- Schedule: "Core Business Hours: 24/7/365 operational coverage for assigned shifts."
- Pay: not included.
Now we need to remove boilerplate: EEO, unsolicited resumes, background check, etc. Also remove "Location: Nashville, TN Core Business Hours: 24/7/365 operational coverage for assigned shifts. Employment Status: Full-Time." We'll keep location maybe in About the role or separate? Not a heading. Could embed location in About the role paragraph.
We also need to remove duplicated lines. Ensure we preserve all substantive info.
Let's craft HTML:
About the role
GFT is seeking a FULL TIME Traffic Dispatcher (Systems Operator I - Trainee) for the Regional Traffic Management (TMC) Center in the Tennessee State Department of Transportation (TDOT) office located in Nashville, TN. This position requires onsite regular attendance at the Nashville, TN office. As GFT expands its transportation operations presence throughout Tennessee, it supports an anticipated statewide Traffic Management Center (TMC) Operations contract for TDOT. GFT is known for high-quality work and a culture of excellence and strong leadership that drive its reputation for delivering award-winning, community-shaping, and innovative solutions.
Responsibilities
- Monitor statewide roadway conditions using CCTV cameras, traffic sensors, and Intelligent Transportation System (ITS) devices.
- Detect, verify, and document traffic incidents, lane closures, roadway hazards, and weather-related events.
- Coordinate response activities with TDOT personnel, law enforcement, emergency services, towing and recovery operators, and maintenance crews.
- Operate Advanced Traffic Management Software (ATMS) and associated TMC systems.
- Prepare incident reports and maintain accurate event logs in accordance with established procedures.
- Disseminate traveler information through Dynamic Message Signs (DMS), 511 systems, social media platforms, and other approved communication channels.
- Monitor ITS device performance and report equipment outages or operational issues.
- Participate in emergency operations, special event traffic management, and planned roadway closure activities.
- Maintain compliance with all TDOT operating procedures, safety policies, and quality management requirements.
Requirements
- High School Diploma or GED required.
- Associate degree in transportation, public safety, information technology, communications, or related field preferred.
- Minimum of one (1) year experience in traffic operations, transportation management, dispatching, emergency communications, public safety, customer service, or related technical operations environment.
- Ability to work rotating shifts, weekends, holidays, overtime, and emergency activations.
- Strong written and verbal communication skills.
- Ability to multitask in a fast-paced operational environment.
- Proficiency with computer systems and Microsoft Office applications.
Qualifications
- Experience working in a Traffic Management Center, Transportation Operations Center, 911 Dispatch Center, Emergency Operations Center, or similar environment.
- Knowledge of the Incident Command System (ICS).
- National Traffic Incident Management (TIM) training.
- Experience with Intelligent Transportation Systems (ITS) technologies.
- Certifications related to transportation operations, emergency management, or public safety communications.
- Good customer service.
Benefits
- Hybrid (in-person and remote) work environment.
- Comprehensive benefits package including wellness programs, parental leave, and pet insurance, in addition to medical, dental, vision, disability, and life insurance.
- Tax-deferred 401(k) savings plan.
- Competitive paid-time-off (PTO) accrual.
- Tuition reimbursement for continued education.
- Commitment to professional development, access to internal and external training programs, and support of active participation in professional organizations.
- Incentive compensation for eligible positions.
Schedule
Core Business Hours: 24/7/365 operational coverage for assigned shifts.
We should also mention Employment Status: Full-Time maybe