Associate Full-Stack Software Engineer
Listed on 2026-07-16
-
Software Development
Software Engineer, Full Stack Developer
Associate Full-Stack Software Engineer
Job type:
Full Time
· Department:
Software
· Work type:
On‑Site
· USD 70,000‑90,000 / year
St. Louis, Missouri, United States
About UsAt 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 and transportation.
We are a small team, which means the work you do here ships to real hardware and you see its effect fast. 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.
Role OverviewWe're hiring an Associate Full‑Stack Software Engineer to help build the operator‑facing layer of our autonomous railcar fleet — the Flutter applications that run on the ruggedized Android tablets our operators use in the field, and the C# services behind them. You'll work in C# and Flutter against a real product surface: the human‑machine interface (HMI) that lets operators see and control what our self‑propelled rail vehicles are doing, and the backend that feeds it.
You'll start by reading and extending systems that already exist, with mentorship and code review from senior engineers as you ramp.
This is a full‑time, 100% in‑office role based in St. Louis, MO. You'll work with in a small group of two to four engineers inside a broader team of around ten, with occasional domestic travel for field testing, vehicle integration, and customer demonstrations — the kind of travel where you see your software running on actual hardware.
What Your First 6 Months Look LikeMonths 1–2
Get hands‑on with the codebase — start by reading, running, and debugging existing modules rather than writing new code from scratch. Pair with a mentor to understand our operator‑interface architecture and development workflow. Set up your local environment, get comfortable with our CI pipeline and testing practices, and ship your first small fix or improvement through code review by the end of your second month.
Months 3–4Own well‑defined features or modules end‑to‑end — from understanding the requirement, through implementation, testing, and code review. You'll be writing Flutter and C# that runs on tablets in the field, so you'll start developing an instinct for how software quality translates to physical system behavior. Expect to work across two or three focused areas rather than one, and to be asking fewer questions about "how does this work" and more about "should we do it this way or that way."
Months 5–6Take on moderately complex tasks with decreasing guidance. Start contributing to technical design discussions — not leading them yet, but asking the questions that shape them. You might propose a small improvement to a tool, a testing pattern, or a piece of infrastructure that makes the team's work better. By this point you'll have enough context to move through the operator‑interface stack on your own.
What You'll Do Day to DayOperator Interfaces: Build and improve Flutter applications that run on our ruggedized Android tablets — the operator‑facing HMI for our rail vehicles.
Backend Services: Write, test, and maintain the C# services behind those interfaces — the systems that move data between the vehicles and the people operating them.
Testing & Quality: Write unit and integration tests for your code, and help reproduce, diagnose, and fix bugs to root cause before they reach production.
Collaboration & Code Review: Participate in code review — giving and receiving feedback — and work with experienced engineers to break product requirements into concrete implementation tasks.
Field Support: Support field testing and integration of software on physical rail vehicles when needed.
The engineering team is small — you'll typically work in groups of two to…
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).