Software Engineer, Vehicle Controls

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 building the next generation of the control system that plans trips for our vehicles, keeps them safe, and drives them. We're hiring a Full-Stack Software Engineer on the Controls team to own that system across its full depth, from the server-side modules that plan and administer a trip to the onboard components that carry it out on the vehicle.

You'll work at the core of how our vehicles move: taking a requested trip, turning it into a safe plan, dispatching it, and making sure it executes correctly in the real world. You'll partner closely with the Perception team to bring autonomous capabilities into the system, and with the Embedded and Applications teams whose work sits alongside your own. "Full-stack" here means the full depth of the control stack, from the ground to the vehicle.

This is a full-time, 100% in-office role based in St. Louis, MO. You'll work with in a team of 3–10 engineers and engage in occasional domestic travel for testing, integration, demonstrations, and customer interactions. This is hands-on, safety-critical work. When the system says stop, several tons of moving railcar need to stop. If that's the kind of problem that gets you out of bed, keep reading.

• Approximately 2 years of professional software engineering experience building and shipping production software.

• Strong problem-solving ability. You can take an ambiguous, under specified problem, break it down, reason about trade-offs, and drive it to a working solution.

• Solid understanding of data structures, algorithms, and how to design maintainable systems: fundamentals that carry across languages.

• Comfort in one or more of the languages we build in (Python, C, C++, Rust, Go, MATLAB/Simulink), or the demonstrated ability to ramp into a new systems language quickly.

• Comfort reasoning about a system where multiple components talk to each other over a network, both on the ground and on the vehicle.

• Discipline about testing before production. You write unit and integration tests, verify behavior before it ships, and when you fix a bug you reproduce it and lock it down with a regression test.

• Proficiency with Git in a collaborative workflow: branching, merging, pull requests, code review.

• Comfort working in a Linux command-line environment.

• Fluent, demonstrated use of AI-assisted development tools (Claude, Cursor, Copilot, etc.) on real work, and a thoughtful point of view on when they help and when they get in the way.

• Willingness to expand into technical areas beyond your area of expertise; ability to develop innovative and novel approaches.

• Open-minded and comfortable working in a teaming environment as an individual contributor.

• Fluent in both written and verbal English.

• U.S. Person (immigration or work visa sponsorship will not be provided).

• Experience with real-time, embedded, or onboard software, and the constraints that come with running on a vehicle rather than a server.

• Experience with message-driven or distributed systems and the delivery-guarantee trade-offs involved (pub/sub, queues, streams, and handling late, dropped, or out-of-order messages). Familiarity with Redis or ZeroMQ is a plus.

• Experience with a database as a source of truth, and a feel for data integrity in a distributed setting (versioning, checksums, content hashing).

• Coursework or project experience in robotics, controls, autonomy, or real-time systems.

• Experience with rail, electric vehicles, or unmanned/autonomous systems.

• Exposure to perception, sensor fusion, localization, or GNSS/INS data, enough to build good software around it.

• Working knowledge of Docker and containerized development workflows.

• Experience with CI/CD pipelines.

• Experience reading and extending an existing codebase, not only building from scratch. Most professional engineering is understanding systems that already exist.

• Comfort working across disciplines. Collaborating with hardware, electrical, or mechanical engineers translates directly here.

Your code runs on real machines. The software you write controls and informs physical vehicles carrying real freight on real rail lines. The feedback loop between your code and the physical world is short, visible, and unforgiving in the best way.

Small team, real…