Senior Software Engineer (Platform Modernization - PHP/Laravel * C#/.NET)

Transport Solutions of America is an innovative company that focuses on solving our customers biggest problems in the transportation industry. We are recognized as a premier driveaway transport vendor in the US and Canada., The current system is a Laravel 11 API exposing a GraphQL-only interface over MySQL 8, with three separate client apps talking to it - a staff application and a customer portal (both Nuxt/Vue) and a driver mobile app (Flutter). Our direction is to modernize it toward enterprise-grade C# / .NET, incrementally rather than in one rewrite.

To be plain about the skills mix: we are not looking for a PHP specialist. We need someone who can read and reason about an existing Laravel and GraphQL codebase confidently, and who is strong enough in C#/.NET to build the replacement properly. If you have spent your career in one language and have no appetite for the other, this is not the seat. If you enjoy understanding a system well enough to move it somewhere better, it is.

There is no product-manager layer between you and the people who use this system. You will sit closely with all internal departments and see your work change how the business runs inside the same quarter. The target architecture is genuinely open - the person in this seat helps decide it.

Work arrangement: In-person for the first 90 days, then negotiable on transitioning to a hybrid schedule if desired.

What you’ll own

Understanding what exists

• Reading the current platform well enough to make credible calls about what to replace, what to wrap, and what to leave alone. That includes the GraphQL schema, which is where most of the behaviour actually lives - of roughly 350 operations, only about 46 have hand-written resolvers. For the rest, the schema definition is the implementation.
• Capturing what currently exists only in the departing vendor’s heads, before it stops being available.
• The MySQL data model - roughly a hundred tables carrying live operational data.

Modernization and delivery

• An incremental path from the current stack to C#/.NET - strangler-fig style, with the business running throughout. We are not interested in a two-year rewrite that lands all at once.
• Reversible database migrations with a written apply plan another engineer could execute: preconditions, verification steps, and the conditions that would abort the change.
• Release and deployment discipline - building out the deployment pipeline is part of the job, not something you inherit finished.

Engineering discipline

• Test design - you decide what the tests are and what constitutes a passing bar, including demonstrating that a control refuses when it should, not only that it permits.
• Architecture decision records for significant technical choices, written so a non-technical reader can follow the tradeoff.
• Code review and technical mentoring for less experienced engineers as the team grows.

• Five or more years shipping production software end to end as an individual contributor - eight or more preferred, particularly if some of it was as the senior-most engineer in a small function.
• Strong C# / .NET - this is where we are going, and you will be building it.
• The ability to work productively in PHP / Laravel, at the level of reading an unfamiliar codebase, tracing behaviour, and changing it safely. Deep PHP expertise is genuinely not required; unwillingness to touch it is disqualifying.
• GraphQL - practical experience with schema design and with APIs where the schema carries real behaviour, not just as a query language you have used from the front end.
• Strong SQL and relational schema work, including reversible migrations and rollback planning. The data model is the hard part of this job.
• Demonstrated experience modernizing or migrating a legacy system that had to keep running - a strangler-fig or incremental-extraction approach rather than a big-bang rewrite.
• Comfort inheriting a codebase you did not write, in a language that may not be your first choice, and forming a credible view of it quickly.
• Version control fluency, and the habit of attaching evidence to a change rather than asserting it worked.
• The ability to explain a technical tradeoff to a non-technical colleague in language they can act on.
• Comfort with ambiguity and limited direction - this is a small function and nobody will be assigning you tasks daily.

A bachelor’s degree in computer science, information systems or a related field is useful, and equivalent practical experience is equally acceptable. We care about what you have shipped and what you decided, not where you studied.

Nice to have

• Logistics, transportation, distribution or B2B services industry experience.
• Direct experience of a vendor-to-in-house transition - taking an application over from a third party.
• Multi-tenant application experience.
• Vue / Nuxt, or Flutter - the client apps are in both, and someone comfortable across the whole surface is a bonus rather than a requirement.
• Redis-backed queues and background job processing.
• Cloud infrastructure - Azure or AWS.
• Comfort using AI-assisted development tools as part of a normal workflow. We use them here and we are not precious about it.

Pulled from the full job description

• 401(k)
• Health insurance
• Retirement plan
• Vision insurance
• Dental insurance
• Life insurance, * 401(k)
• Dental insurance
• Health insurance
• Life insurance
• Retirement plan
• Vision insurance