Experienced Full-Stack Software Engineer

About Us

At Intramotev, we are dedicated to revolutionizing the freight industry by liberating tons of freight from congested highways, reducing carbon emissions, and enhancing transportation efficiency. We are deploying self-propelled battery-electric railcars and vehicles to transform freight logistics and bring innovation to our rail network. Based in St. Louis, MO, we are committed to promoting industrial revitalization, saving lives, and minimizing the environmental impact of trucking.

We actively foster a work environment for every teammate that's welcoming, respectful and inclusive, with great opportunities for professional growth. Find your future with us.

We're hiring a Full-Stack Software Engineer to own the software our operators actually touch — the C# services behind our fleet and the Flutter applications running on the ruggedized Android tablets mounted in and around our railcars. You'll build the operator-facing interfaces that turn vehicle telemetry and fleet state into something a human can act on in the field, and the backend services that feed them.

This is hands‑on, end‑to‑end work: you'll be designing the tablet UX, wiring it to the backend, and seeing it run on hardware in a rail yard. We care more about how you solve problems than about which languages you've used — if you're a strong engineer who can ramp into our stack, we want to talk.

This is a full‑time, in‑office position, based in St. Louis, MO.

You're past the "what is a pull request" stage, so we'll get you productive quickly. In your first month you'll get the codebase running locally, ship a real fix or improvement through code review, and pair with the team to understand our vehicle architecture and how the tablet apps talk to the backend. By month two you'll own a well‑defined feature end‑to‑end — design, implementation, tests, review — including UI that ships to the Android tablets.

By month three you'll be taking on moderately complex work with little guidance, contributing to design discussions, and starting to shape how we build the operator‑facing layer rather than just executing tickets.

• Build and maintain operator‑facing Flutter applications targeting ruggedized Android tablets — designing for field use: glare, gloves, intermittent connectivity, and people who are not software engineers.
• Write, test, and maintain the C# backend services and internal tools those interfaces depend on — telemetry ingestion, fleet operations, real‑time visibility.
• Write unit and integration tests for your code and verify behavior before it ships to production — our software runs on vehicles in the field, so catching problems before they reach hardware is part of the job, not an afterthought.
• Investigate and fix bugs in production systems — reproduce, diagnose root cause, write the regression test.
• Participate in code reviews, both giving and receiving feedback.
• Work with experienced engineers to break product requirements into concrete implementation tasks.
• Contribute to documentation and internal technical knowledge bases.
• Support field testing and integration on physical rail vehicles when needed — including getting tablets and software working in the yard.

• The engineering team is small — you'll typically work in groups of two to four on focused projects, with a broader team of around ten collaborating across efforts. At this size there's no hiding behind process or hierarchy. You'll be in the room for design discussions, and your questions get answered by the people who built the system.
• We do daily standups, asynchronous communication in Discord, and design reviews for anything nontrivial. Code review is mandatory — not as a gate, but as a practice the whole team treats as a teaching and learning tool.
• We expect you to use AI tools well. Our engineers use LLM‑based development tools daily, and we want someone who has real judgment about where they accelerate the work and where they quietly create problems. Strong, fluent use of these tools is part of how this team ships.
• We test before we ship. Because our code ends up on vehicles carrying real freight,…