Mobile Developer

The Role

We are looking for a Mobile Developer who will take full, end-to-end ownership of the BusPlanner mobile application portfolio. This is not a role where someone else builds the platform and you apply a UI on top of it. You will write the mobile code, build the C# APIs that support it, work directly with the ruggedized tablets and peripherals our customers use in the field, and own getting releases into the Apple App Store and Google Play.

Our mobile products include a driver and attendant application used on in-vehicle tablets and a parent-facing application used on both iOS and Android consumer devices, along with ridership and scanning capability that integrates with physical hardware. All of it is built on .NET MAUI in C#.

The work is varied: some weeks are focused feature and integration work on the mobile apps, others are spent in the supporting APIs, on hardware and peripheral behaviour, or in adjacent parts of the platform such as BusPlanner Web, GPS tracking, live viewer and dispatch. We are looking for someone who is happy moving across that surface rather than staying in a single lane.

What You Will Own

• Mobile development in .NET MAUI — building, maintaining and improving our driver, attendant and parent applications for both Android and iOS.
• End-to-end release ownership — producing builds, managing signing and provisioning, publishing to the Apple App Store and Google Play, and shepherding releases through review and rollout.
• Backend API development in C# — designing and building the APIs your mobile work depends on, so mobile delivery is never blocked waiting on another team.
• Device and peripheral integration — working on ruggedized Android tablets (currently the Samsung Galaxy Tab Active 5) and the peripherals attached to them, including RFID readers, QR and barcode scanners, USB devices, and mounting and power considerations.
• Push notifications and messaging — owning the notification pipeline that reaches drivers, attendants and parents.
• Production support — investigating and resolving issues reported from the field across the mobile portfolio and its supporting services.
• Cross-product contribution — pitching in on ridership and scanning features, GPS and live tracking, dispatch and other products in our student transportation ecosystem.

What Success Looks Like

• First 30 days - Environment set up, able to build and run all mobile applications locally, first bug fixes shipped, familiar with the release process.