Senior Full Stack Systems Engineer — Burnsed Brain

Burnsed Trucking | Operational Intelligence Platform

Burnsed Trucking is building Burnsed Brain — a proprietary operational intelligence and financial decision platform for refrigerated consolidation logistics.

This is not a marketing website project or a simple dashboard build.

We are building a real operational system used daily to manage:

* truck tours,
* dispatch workflows,
* contribution margin,
* reload strategy,
* operational efficiency,
* and monthly operating ratio (OR).

The system combines:

* logistics operations,
* financial modeling,
* dispatch execution,
* operational reporting,
* permissions architecture,
* and operational intelligence into one centralized platform.

We already have:

* a partially working Claude-generated codebase,
* UI/UX mockups,
* operational logic documentation,
* financial frameworks,
* dispatch workflows,
.

We are looking for a senior full stack systems engineer who can help us:

*build the architecture
* stabilize and improve the existing codebase,
* architect the system properly,
* productionize the platform,
* and help build Burnsed Brain into a long-term operational system used by dispatch, finance, leadership, and eventually drivers and customers.

?

This Is NOT a Typical Full Stack Role

We are NOT looking for:

* a junior developer,
* a no-code builder,
* a landing-page designer,
* or someone focused primarily on visual polish.

We are looking for someone who thinks in:

* systems,
* workflows,
* operational logic,
* financial accuracy,
* permissions,
* reliability,
* and maintainability.

The ideal candidate understands that operational software is fundamentally about:

trust, consistency, and decision-making.

?

Core Business Logic

The core operational unit inside Burnsed Brain is the:

Tour

A “tour” represents one truck’s full operational cycle from dispatch to return, including:

* outbound deliveries,
* reloads,
* backhauls,
* middle-mile pickups,
* fuel,
* labor,
* tolls,
* unloads,
* and all associated operational costs.

The syste ---------- asures:

* Daily Contribution Margin
* Weekly Operational Contribution Margin
* Monthly Operating Ratio (OR)

The goal is to improve:

* operational efficiency,
* consolidation quality,
* reload success,
* route profitability,
* and overall OR performance.
* incentivize performance by performance index
?

What You’ll Be Building

Core Operational Systems

* Tour Entry & Tour Management
* Daily CM Dashboard
* Weekly CM Analysis
* Monthly OR Tracking
* Performance Index System
* Dispatch Dashboard
* Alerts & Exceptions
* Rules-Based Operational Recommendations
* Driver Scorecards
* Customer Profitability Views
* Data Input & Reconciliation Workflows
* Monthly Close Workflow
* Role-Based Permissions
* Admin Controls

?

The Type of Engineer We Want

The right engineer for this role:

* asks operational questions,
* thinks about edge cases,
* thinks about auditability,
* thinks about data integrity,
* thinks about permissions,
* thinks about month-end close,
* thinks about workflow reliability,
* and understands how real operational teams behave under pressure.

We care more about:

1. Reliability
2. Maintainability
3. Permissions integrity
4. Operational usability
5. Auditability
6. Financial accuracy
7. Long-term architecture

than flashy UI work.

?

Required Skills

Must Have

* Senior full stack engineering experience
* Excellent English communication
* Experience with Claude Code / AI-assisted development workflows
* Strong backend architecture experience
* Strong database design experience
* API integration experience
* Authentication & permissions systems
* GitHub workflow discipline
* Ability to independently architect systems
* Strong debugging and production troubleshooting ability

?

Strongly Preferred

* Logistics / trucking / dispatch system experience
* TMS or fleet management experience
* Operational dashboard experience
* Financial systems understanding
* Contribution margin / operational finance understanding
* Experience building internal operational software
* Experience integrating GPS/ELD/fuel/accounting APIs

?

Important Technical Expectations

This is not intended to become:

* AI hype software,
* “agent”-driven automation,
* or overengineered enterprise bloat.

The initial recommendation engine is primarily:

rules-based operational intelligence.

Future phases may later include:

* predictive modeling,
* advanced AI recommendations,
* customer portals,
* driver mobile applications,
* and external integrations.

But Phase 1 is focused on:

building a reliable operational core.

?

Current Operational Roles

The system currently supports:

* Chad — Operations oversight
* Marco & Nicole — Dispatch execution
* Donna — Finance & reconciliation
* Leadership — Executive visibility

The platform includes:

* operational-safe views,
* dispatch views,
* finance-restricted views,
* executive financial dashboards,
* and future driver-facing mobile views.

Permissions architecture matters heavily.

?

Current Project Status

This is not a greenfield project.

We already have:

* operational workflows,
* financial logic,
* UI concepts,
* and partially working AI-assisted code.

The first responsibility is:

* code review,
* architecture cleanup,
* stabilization,
* and productionization.

Not rebuilding everything from scratch.

?

Ownership & Continuity

All:

* repositories,
* infrastructure,
* credentials,
* APIs,
* deployments,
* and hosting

must be company-owned and documented.

No single point of failure.

Documentation and maintainability are mandatory.

?

What Success Looks Like

Success means:

* dispatch uses the system daily,
* CM reporting becomes operationally trusted,
* OR tracking becomes reliable,
* month-end close works correctly,
* and Burnsed Brain becomes part of the company’s operational rhythm.

?

To Apply

Please send:

* resume / LinkedIn,
* GitHub or portfolio,
* examples of operational systems you’ve built,
* logistics/TMS/finance experience (if applicable),
* preferred stack,
* availability,
* compensation expectations,
* and a short explanation of how you would approach stabilizing and productionizing an AI-generated operational platform.