Director of Engineering

Role Overview

Director of Engineering (TransitOS Solution/Enterprise Architecture) — Remote (U.S.)

This is a hands-on architecture leadership role that defines the future of TransitOS by unifying six mature SaaS platforms into one enterprise platform powering multiple mobility modes.

Responsibilities

• Enterprise Solution Architecture
  • Define and evolve the TransitOS canonical data model
  • Design scalable solutions for strategic initiatives
  • Establish architecture standards, API conventions, and integration patterns
  • Govern architectural consistency across six SaaS platforms
  • Lead build-vs-buy and platform reuse decisions
• Platform Convergence
  • Architect the technical convergence of:
    • Fixed Route
    • Paratransit
    • On-Demand Transit
    • Non-Emergency Medical Transportation (NEMT)
• Architecture Governance
  • Review and approve integration designs, data models, API standards, and non-functional requirements (e.g., scalability)
  • Assess security architecture and performance considerations before development begins
• Product & Engineering Partnership
  • Translate architecture into epics, user stories, acceptance criteria, and technical requirements
  • Reduce rework by ensuring engineering teams can execute with confidence
• Delivery Leadership (through SDLC)
  • Participate in backlog grooming, PI Planning, sprint outcomes, and UAT
  • Clarify architectural intent and remove technical ambiguity
  • Prevent integration failures before release
• Executive & Client Engagement
  • Represent Transit Technologies as the architectural expert in executive reviews, customer meetings, technical presentations, RFP support, and solution demonstrations

Success Criteria

• First 90 days: Learn multiple platforms; publish first TransitOS canonical data model; deliver architecture for strategic initiatives; build relationships across Product and Engineering.
• Within 6 months: Establish architecture governance across product teams; improve backlog quality and requirements maturity; reduce mid-sprint clarification requests; lead customer architecture presentations.
• Within 1 year: Become trusted architectural authority; reduce architectural rework/integration defects; improve delivery predictability; further shape the roadmap (truncated in posting).