Director, Software Engineering Smart Mobility
Listed on 2026-07-08
-
Software Development
Software Project Mgr/ Lead, Software Architect
Trans Core (TRN), a subsidiary of ST Engineering, is seeking a hands‑on Director of Software Engineering to lead our Smart Mobility engineering team in Atlanta, Georgia;
Nashville, Tennessee; or Harrisburg, Pennsylvania.
Trans Core is building Smart Mobility, a cloud‑native mobility platform that lets people move through tolling and transit from their phone connecting the agencies, partners, and consumer apps behind it.
This position will own Smart Mobility delivery end to end, bringing the mobile, backend, integration, and account‑management work together into one product that ships reliably, securely, and on a predictable cadence, and that scales as we grow.
The Director of Software Engineering will set how the group builds: clear delivery practices, strong quality and security standards, and create a team structure that grows with the product. This role will partner with the Smart Mobility Architecture function, which owns technical direction, and turn that direction into working software.
Reporting & Organizational ContextThe Director of Software Engineering will own Smart Mobility engineering delivery end to end. To start, while the team is small and growing, this role reports to the VP, Smart Mobility Architecture. As engineering scales, it is expected to stand up as its own pillar with dedicated leadership. The VP, Smart Mobility Architecture represents this work at the leadership table alongside the Chief Architect, Head of Platform Engineering.
The Director of Software Engineering runs the Smart Mobility product.
The Director leads the Smart Mobility engineering teams directly and owns the relationships with every team that contributes to the product: beacon and phone integration, backend and integration, account management, and UX. Several of these are shared resources today. It will drive the shift to a full‑allocation model and, for anyone not directly under supervision, establish and own clear working agreements that define commitments, allocations, and escalation paths.
WhatSuccess Looks Like (First Year)
Illustrative targets, to be refined with the VP, Smart Mobility Architecture:
- First ~3 months: A single, unified Smart Mobility delivery plan and a predictable release cadence across all work streams.
- By ~6 months: Consistent releases with defined quality gates; QA / Test Automation and Dev Ops functions stood up; and a stable team structure with named engineering leads.
- Working agreements: Clear, owned working agreements are in place with every partner and shared team, with a defined path toward full allocation.
- Reliability: Production reliability operating to defined SLOs against the availability target.
- Engineering Delivery Ownership
- End-to-end delivery: Own delivery from staffing and sprint execution through release, accountable for shipping the complete product.
- Unify the build: Bring the mobile, backend, integration, and account‑management work under one coherent delivery plan.
- Predictable execution: Own release cadence, quality gates, and delivery commitments; surface and resolve risks early.
- Reliability and security: Own the engineering team that handles Tier 3 execution and support for Smart Mobility, and back the Tier 1/2 support managed by the separate 24x7 operations team. Drive the SLOs behind the availability target, along with security and PCI‑DSS controls, partnering with Dev Ops on CI/CD.
- People Leadership & Organization Building
- Enable and empower the teams: Create the conditions for engineering teams to design and build with autonomy, clear goals, and the support to deliver.
- Build and grow the team: Own hiring for Smart Mobility engineering, including the headcount plan and engineering budget, and develop engineers and leads through coaching, mentoring, and performance management.
- Operating structure: Set the team structure and engineering leads, and coordinate with partner organizations to stand up shared functions such as QA / Test Automation and Dev Ops (establishing them, not owning them). Keep Scrum facilitation separate from the engineers building the product.
- Culture: Set a high engineering bar and create an environment where strong…
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).