Open to senior full-stack roles & select contract work

Freight moves whether or not your software is ready.

I'm a full stack engineer on an enterprise TMS — dispatch, tracking, and brokerage for a national trucking operation. Four years of Angular front ends over a .NET Core platform, wired together with SignalR, RabbitMQ, and Redis, running multi-tenant for every brokerage on it.

4 yrsshipping production software
TMSdispatch · tracking · brokerage
Multi-tenantone platform, many brokerages
RealtimeSignalR · RabbitMQ · Redis
Multi-tenant · one deploy, many brokerages
Tier 01Front end
Angular on current standards — standalone components, signals, typed forms. Material for the shell, Kendo for the grids and charts operations people actually work in.
Angular 22Angular MaterialKendo UI GridKendo ChartsTypeScriptRxJS + signals
Tier 02API & data
A .NET Core API over SQL Server, with Redis for cache and as the SignalR backplane. Every query is tenant-scoped before it leaves the repository.
.NET CoreC#SQL ServerEntity FrameworkRedisSignalR
Tier 03Async platform
A RabbitMQ message engine for anything that must not block a dispatcher's save, and a Coravel scheduling service for recurring sweeps and reconciliation.
RabbitMQCoravelIdempotent consumersDead-letter replayDistributed locks
Tier 04Delivery & integrations
Azure DevOps YAML pipelines from build to a single shared environment where every tenant lives, plus the growing set of partner integrations the platform depends on.
Azure DevOpsYAML pipelinesSQL migrationsPartner adapters
Integrations shippedGPS & ELD tracking providers·Fraud & carrier vetting·Load boards·EDI partners·Document capture·Rating & rate refresh
All work →

Logistics is my domain, but the shape of the work travels: grid-heavy operational UIs, realtime state, and integrations with partners who each define "shipment" differently.

Grid-heavy operational UIs that stay fast at real data volumes
Realtime features: SignalR, backplanes, reconnect semantics
Message-driven integrations with unreliable third parties
Angular upgrades and Material/Kendo consolidation
Multi-tenant architecture and tenant-safe data access
Start a conversation→