You will design and execute a zero-downtime migration for a fare collection system’s core tables while meeting strict external audit requirements and keeping query latency down during morning and evening peak hours. This is not a theoretical exercise; the data you protect flows directly into scheduling engines, payment processors, and fleet maintenance logs that hundreds of transit workers depend on every shift. When you tune an index or coordinate a vendor schema update, you are preventing missed buses, stalled turnstiles, and delayed payroll reports. Your work sits at the exact intersection of technical precision and public service reliability.
At this stage, your focus shifts from reacting to alerts to engineering predictable performance across mixed environments. You will take ownership of cross-vendor schema harmonization between SQL Server, Oracle, and PostgreSQL, turning fragmented inherited structures into coherent, query-friendly architectures. You will also build self-service automation pipelines that handle routine patching, backup verification, and DR drills, giving development teams faster access to stable data without waiting on ticket queues. This is where you stop firefighting and start designing systems that scale with agency growth.
The team operates on a simple rule: you are trusted to own your environment and speak directly to developers, vendors, and operations leads without bureaucratic handoffs. We prioritize collaboration over heroics, which means you will get candid execution reviews, shared runbooks after incidents, and dedicated time to study vendor documentation alongside seasoned engineers. If you prefer a workplace where curiosity is expected, mistakes are treated as calibration points, and the work quietly keeps a city running, you will find your rhythm here quickly.
