Conduent / ACS CAD/AVL Administrator

Ryan Mahoney

Why this role is hard · Ryan Mahoney

The hardest part of filling this role is telling the difference between someone who actually knows the system and someone who just talks a good game. You need a person who can track down a dropped GPS packet across three network segments and clearly explain the fix to a dispatcher who suddenly lost sight of six buses. Plenty of candidates look great until you ask them how they handle a routine patch deployment under real pressure. The best admins treat every configuration change like a binding promise to the fleet, so they will openly push back on a rushed rollout before touching a live terminal. They also know how to listen for the exact moment a radio handshake fails instead of guessing at the root cause.

Core Evaluation

Critical questions for this role

The competency and attitude questions below are where the hiring decision is made. They run in the live interview rounds and are calibrated to the level selected above.

16 Competency Questions

1 of 16

  1. Discipline

    Transit CAD/AVL Systems Administration & Integration

  2. Job requirement

    Autonomous & Micromobility Data Integration

    Integrates third-party autonomous vehicle APIs, configures geofencing rules, and troubleshoots micromobility telemetry synchronization issues.

  3. Expected at Mid

    AV/micromobility is typically scoped to pilot programs; foundational proficiency ensures mid-level admins can maintain data pipelines and resolve basic sync issues.

Interview round: Hiring Manager Core Systems & Architecture

Share an instance where you configured operational boundaries or resolved telemetry sync issues for a newly integrated transit data feed.

Positive indicators

  • Defines geofences based on operational service areas
  • Tests boundary triggers under varied conditions
  • Resolves sync gaps through log analysis and coordination
  • Validates data accuracy against ground truth
  • Maintains clear integration documentation

Negative indicators

  • Sets arbitrary boundaries without operational input
  • Ignores telemetry synchronization validation
  • Fails to coordinate with third-party providers
  • Lacks testing of boundary triggers
  • No documentation of integration processes

12 Attitude Questions

1 of 12

Active Listening

The deliberate, focused practice of fully receiving, comprehending, and validating verbal and non-verbal communication from transit operators, dispatchers, vendors, and cross-functional stakeholders before formulating technical responses or system adjustments. It involves suspending judgment, accurately interpreting operational constraints and experiential insights, and translating those inputs into precise, reliable CAD/AVL configurations, troubleshooting workflows, and integration strategies.

Interview round: Recruiter Alignment & Operations Fit

Describe an instance where you had to diagnose a Tier-2 CAD incident based primarily on verbal operator complaints rather than automated logs. What steps did you take to verify the details?

Positive indicators

  • Asks targeted questions to isolate system variables
  • Maps verbal descriptions to specific database fields
  • Avoids leading questions during initial intake

Negative indicators

  • Accepts complaints at face value without technical translation
  • Forces operators to use technical jargon they don't know
  • Ignores environmental context in operator reports

Supporting Evaluation

How candidates earn the selection conversation

The goal is to reduce effort for everyone by collecting more useful signal before adding more interviews. Lightweight application prompts and structured screens help the panel focus live time on the candidates most likely to succeed.

Stage 1 · Application

Filter at the door

Runs the moment a candidate hits Submit. Disqualifying answers end the application; everything else is captured for review.

Knock-out Questions

1 of 2

Application Screen: Knock-out

Do you have at least 3 years of hands-on experience administering CAD/AVL or transit dispatch systems in a production environment?

Yes
Qualifies
No
Auto-decline

Video-Response Questions

1 of 3

Application Screen: Video Response

During a partial CAD server degradation, dispatch supervisors are requesting immediate, unvetted configuration changes to restore tracking. Describe how you would communicate the technical risks and enforcement boundaries to these stakeholders while preserving operational trust and maintaining system integrity.

Candidate experience

REC
0:42 / 2:00
1Record
2Review
3Submit

Response time

2 min

Format

Recorded video

Stage 2 · Resume Screening

Read the resume against fixed criteria

Reviewers score every application that clears the door against the same criteria. Stronger reviews advance to live interviews; weaker ones are archived without further screening.

Resume Review Criteria

8 criteria
Independent administration of route-level CAD configurations, firmware patch deployments, and change window management across assigned depots.
Proven ability to cross-check AVL positional logs against GTFS-Realtime feeds and validate middleware integrations for fare, traffic, or rider-facing systems.
Experience configuring dispatch routing logic based on battery management system (BMS) telemetry, charging APIs, and dynamic route assignment protocols.
Track record of developing training materials and conducting console walkthroughs for dispatch operators on routing adjustments, alert management, and incident response.

Does the cover letter or personal statement convey clear relevance and familiarity with the job?

Does the resume indicate required academic credentials, relevant certifications, or necessary training?

Is the resume complete, well-organized, and free from formatting, spelling, and grammar mistakes?

Does the resume show relevant prior work experience?

Stage 3 · During Interviews

Where the hire is decided

Interview rounds use the competency and attitude questions outlined above, then add tests, work simulations, and presentations that reveal deeper evidence about how the candidate thinks and works.

Presentation Prompt

Prepare a short deck and walk us through a past experience where you owned end-to-end administration for a route or depot configuration change or patch deployment. Discuss how you balanced strict change control protocols with the urgent need to maintain dispatch reliability, managed escalations, and validated integration health post-deployment.

Format

deck-and-walkthrough · 20 min · ~2 hr prep

Audience

CAD/AVL Systems Administration Team and Operations Manager

What to prepare

  • 3-5 slides outlining the context, your decision-making process, execution steps, and outcomes
  • Brief notes on how you handled trade-offs between change windows and operational urgency

Deliverables

  • A structured presentation of your past work, highlighting configuration management and incident prioritization

Ground rules

  • Use only work you are permitted to share; anonymize sensitive agency or vendor details if necessary.
  • Focus on your reasoning, stakeholder coordination, and post-deployment validation rather than proprietary system details.
  • Do not produce net-new strategic artifacts; discuss your historical approach.

Scoring anchors

Exceeds
Presents a cohesive narrative linking change management, risk mitigation, and validation, with clear evidence of cross-functional alignment and operational ownership.
Meets
Describes a standard deployment process, mentions change windows and basic validation, and shows adequate stakeholder coordination.
Below
Lacks structure, omits change control or validation steps, or cannot clearly articulate decision-making during deployment.

Response time

20 min

Positive indicators

  • Clearly maps change control steps to operational risk mitigation
  • Demonstrates structured stakeholder communication during deployment windows
  • Articulates specific validation metrics used to confirm integration health
  • Balances urgency with compliance, explaining trade-offs transparently

Negative indicators

  • Focuses solely on technical execution without addressing change control or risk
  • Fails to describe how escalations were managed or prioritized
  • Vague on post-deployment validation and success criteria
  • Ignores cross-functional coordination with dispatch or vendor teams

Work Simulation Scenario

Scenario. You are a CAD/AVL Systems Administrator. A critical CAD-to-AVL sync patch must be deployed tonight. The Network Team warns of a firewall rule conflict that could block AVL telemetry. Dispatch Operations insists on a strict 2-hour service window for route adjustments. Vendor Support says the patch expires if not applied within 4 hours. You must facilitate a decision on timing, rollback plan, and stakeholder communication.

Problem to solve. Drive a structured tradeoff discussion to align deployment timing, risk mitigation, and communication cadence across conflicting operational and technical constraints.

Format

cross-functional-decision · 40 min · ~2 hr prep

Success criteria

  • Facilitates a decision that respects all critical constraints
  • Establishes a clear rollback trigger and communication protocol
  • Aligns cross-functional teams on risk ownership and next steps

What to review beforehand

  • Standard CAD/AVL patch deployment workflow
  • Firewall rule change impact assessment templates
  • Dispatch service window scheduling guidelines

Ground rules

  • You have 30 minutes to reach a deployment decision and communication plan
  • You cannot unilaterally override network security or dispatch scheduling mandates
  • Focus on tradeoff facilitation, not unilateral technical fixes

Roles in scenario

Network Operations Lead (cross_functional_partner, played by peer)

Motivation. Prevent firewall misconfigurations from blocking AVL telemetry or creating network security vulnerabilities.

Constraints

  • Requires 45 minutes to test and validate new firewall rules
  • Cannot approve deployment until telemetry baseline is confirmed
  • Limited to a single maintenance window tonight due to upstream ISP work

Tensions to introduce

  • Insists on delaying deployment until firewall rules are fully tested
  • Questions whether the patch's telemetry dependency outweighs the sync fix
  • Requests a dedicated rollback network path before committing

In-character guidance

  • Focus on technical risk and security compliance
  • Provide honest answers about testing timelines when asked
  • Accept phased deployment if a clear telemetry validation step is included

Do not

  • Do not volunteer the exact firewall conflict details unless asked
  • Do not concede to an untested deployment timeline
  • Do not solve the scheduling conflict for the candidate

Dispatch Scheduling Manager (skeptical_stakeholder, played by cross_functional)

Motivation. Protect the evening route adjustment window to ensure buses are correctly positioned for tomorrow's morning peak.

Constraints

  • Only a 2-hour window is available tonight without disrupting driver assignments
  • Cannot tolerate more than 15 minutes of CAD console downtime
  • Requires immediate notification if routing logic is affected

Tensions to introduce

  • Pushes for immediate deployment before the network team finishes testing
  • Questions why the patch cannot be split into non-disruptive components
  • Demands a guaranteed fallback if CAD routing logic shifts unexpectedly

In-character guidance

  • Prioritize operational continuity and driver scheduling stability
  • Answer honestly about the impact of delays on morning service
  • Agree to a constrained window if a strict downtime limit and clear communication plan are set

Do not

  • Do not volunteer alternative scheduling options without being prompted
  • Do not escalate to executive leadership during the scenario
  • Do not accept a deployment plan that lacks a clear rollback trigger

Scoring anchors

Exceeds
Orchestrates a phased deployment with explicit telemetry validation gates, strict downtime limits, and a synchronized communication plan that satisfies both network and dispatch constraints.
Meets
Facilitates a compromise on timing, documents rollback triggers, and establishes a basic communication cadence, though some operational tradeoffs remain loosely defined.
Below
Fails to align stakeholders, pushes a unilateral timeline that violates constraints, or lacks clear risk mitigation and rollback planning.

Response time

40 min

Positive indicators

  • Structures the discussion by mapping constraints, identifying the critical path, and sequencing decisions
  • Proposes a phased or staggered deployment that isolates firewall testing from console downtime
  • Establishes explicit rollback triggers, success metrics, and stakeholder notification cadences
  • Translates technical risks into operational impacts and vice versa to build shared understanding

Negative indicators

  • Fails to reconcile conflicting timelines, resulting in an unworkable or ambiguous plan
  • Ignores network security or dispatch scheduling constraints in favor of vendor deadlines
  • Does not define clear rollback criteria or communication protocols for live deployment
  • Dominates the conversation without facilitating tradeoff alignment between stakeholders

Progression Framework

This table shows how competencies evolve across experience levels. Each cell shows competency at that level.

Transit CAD/AVL Systems Administration & Integration

7 competencies

CompetencyJuniorMidSeniorPrincipal
Autonomous & Micromobility Data Integration

Tracks autonomous shuttle locations in test environments, logs micromobility API connections, and verifies basic route data.

Integrates third-party autonomous vehicle APIs, configures geofencing rules, and troubleshoots micromobility telemetry synchronization issues.

Designs multi-modal integration frameworks, establishes safety protocol overlays for autonomous fleets, and scales micromobility data pipelines.

Defines strategic partnerships for emerging mobility tech, sets regulatory compliance frameworks for AV data, and pioneers unified mobility dashboards.

Core CAD/AVL Infrastructure Administration

Performs routine server health checks, applies patches, and monitors basic CAD/AVL hardware connectivity under supervision.

Independently configures system parameters, troubleshoots network bottlenecks, and manages baseline infrastructure deployments to ensure continuous CAD/AVL availability.

Architects high-availability CAD/AVL environments, leads complex infrastructure migrations, and establishes system hardening standards.

Defines enterprise-wide infrastructure strategy, evaluates emerging hardware/software platforms, and drives cross-organizational technology roadmaps.

EV Fleet Telematics & Power Management

Monitors EV charging station connectivity, tracks basic battery telemetry, and reports range anomalies to dispatch.

Integrates charger APIs into CAD/AVL systems, configures power management alerts, and optimizes charging schedule data flows to support electric fleet operations.

Architects unified EV fleet management platforms, develops predictive range modeling, and ensures grid-load balancing integration.

Directs enterprise electrification strategy, establishes cross-agency charging infrastructure standards, and drives sustainability tech roadmaps.

Real-Time Dispatch & Fleet Communication

Monitors real-time telemetry feeds, assists dispatch console users, and logs communication anomalies.

Optimizes data routing pipelines, configures dispatch rules, and resolves latency issues in vehicle-to-dispatch links to maintain real-time operational accuracy.

Designs scalable telemetry architectures, integrates multi-modal dispatch workflows, and implements advanced failover protocols.

Establishes industry-leading dispatch communication frameworks, directs vendor interoperability standards, and optimizes system-wide throughput.

Security, Compliance & Fare System Integration

Applies baseline security patches, monitors access logs, and assists with fare system API connectivity testing.

Implements role-based access controls, troubleshoots MaaS integration errors, and conducts routine compliance audits to ensure secure CAD/AVL operations.

Designs zero-trust security architectures, negotiates vendor SLA compliance, and architects secure multi-agency data exchanges.

Establishes enterprise cybersecurity policies, directs regulatory compliance strategy for transit data, and sets industry-standard MaaS integration protocols.

Transit Data Analytics & Performance Monitoring

Generates standard operational reports, monitors dashboard alerts, and cleanses historical AVL datasets.

Builds custom KPI visualizations, optimizes data warehouse queries, and implements automated anomaly detection to drive proactive transit performance monitoring.

Architects predictive analytics models, establishes enterprise data governance, and drives cross-departmental performance optimization.

Directs enterprise-wide data strategy, establishes advanced equity modeling frameworks, and influences industry analytics standards.

Transit Signal Priority & V2I Integration

Assists in GPS receiver installation, validates basic V2I data feeds, and documents signal priority configurations.

Tunes transit signal priority algorithms, troubleshoots vehicle-infrastructure handshake failures, and optimizes GPS accuracy settings for connected corridors.

Engineers complex V2I integration architectures, leads municipal connectivity deployments, and resolves cross-system protocol conflicts.

Shapes regional connected infrastructure standards, directs next-generation V2X research pilots, and aligns transit tech with smart city initiatives.