Role Overview:

At Cargoo we are building the infrastructure that makes Freight reliable and scalable. Real-time logistics systems, built in.NET.

Problem space: 

Logistics operations today are still largely: 

• manual 

• reactive 

• fragmented across tools 

• incomplete / late data 

• conflicting constraints 

• real-time decision pressure 

• evolving business rules 

• legacy + new system coexistence 

We’re building a system that: 

• ingests real-time operational data 

• supports planning & execution decisions 

• adapts to constantly changing constraints 

Design principles:

• keep things simple before scalable
• prefer explicit logic over magic abstractions
• optimize for change, not perfection
• avoid “framework-driven architecture”
• accept that some parts will be ugly — temporarily 

Tech stack:

• .NET 
• Vue.JS
• service-oriented architecture
• relational + operational data storage
• cloud-based infrastructure 

What we expect from engineers:

• Ability to navigate uncertainty and work in ambiguity
• Willingness to challenge decisions
• Focus on outcomes, not just code
• Understanding of trade-offs and complex systems
• Preferring ownership over comfort 

What you wont find here: 

• over-engineering everything upfront
• unnecessary microservices
• “clean architecture” for the sake of it
• process-heavy development 

If this resonates with you – lets talk! 

Send us: 

• your LinkedIn / GitHub
• OR a short message explaining what you’ve built and why it matters