Software Integration Engineer - C2 Systems

Software Integration Engineer - C2 Systems About Forterra

At Forterra, we are unleashing autonomy at scale to transform the battlefield. Our mission is to build the foundational platforms that enable an intelligent ecosystem to coordinate, adapt, and execute with speed and precision even in the uncertainty and disruption of modern conflict. In an era marked by rapid technological change and evolving threats, we design for flexibility, survivability, and operational dominance.

Forterra delivers weapons, sensors, and battlefield effects through integrated autonomous networks reaching operational areas faster, safer, and without placing human lives  systems operate with distributed control, dynamic routing, and real-time responsiveness, enabling sustained advantage across complex mission environments.

Forterra is seeking a C2 Software Integration Engineer to own the command-and-control workflow that connects our autonomy stack to the operators who use it in the field. This is a full-stack integration role that spans the layers of that workflow: the autonomy stack, the middleware that moves data between systems, and the operator control unit (OCU) that operators use to command and monitor vehicles.

Your job is to make command and control work end to end — from a command defined on a vehicle, through the middleware and the network, to the action an operator takes at the OCU — and to keep it working in real-world deployments.

We are in the middle of transitioning from our legacy OCU to a next-generation replacement. You will help bring the new interface online while keeping the legacy one running for the programs that still depend on it, and help carry those workflows across as the fleet transitions.

You will not be a middleware engineer or a front-end engineer. You will be the integrator who ties those layers together: fielding, debugging, supporting, and owning the success of this full-stack C2 workflow for programs. You will directly support real-world missions across our fleet of ground vehicles operated by our national security customers around the world.

The ideal candidate picks up unfamiliar codebases quickly, is a self-starter who does not wait to be handed scope, and is eager to leave a visible impact on how our systems are commanded and controlled. You are comfortable being the person who follows a problem across multiple systems and the network between them until it is resolved.

• Own command and control end to end. Take a command from its definition on the vehicle, through the middleware and the network, to its representation at the OCU — and be accountable for the whole path working.
• Define and evolve the contracts between systems. Add and extend the message contracts that describe vehicle state, tasks, and commands, and carry them through to every system that produces or consumes them.
• Own the bridge between autonomy and middleware. Extend the integration layer that translates between the autonomy stack and the middleware — publishing what the vehicle knows (telemetry, autonomy state, Number of headcount you want to hire? 1 1 route and convoy state, zones) and turning operator commands into vehicle behavior (waypoint driving, route planning, convoy, teleop) while reporting status back.
• Frame command and control through the interface. Partner on the operator-facing interface to expose new commands and vehicle behaviors to operators in a usable way. You do not need to arrive as a frontend expert, but you must be willing to learn how command and control is framed through user interfaces and to contribute across that boundary.
• Support the outgoing interface. Keep the legacy OCU working for the programs that still rely on it, and help migrate those workflows…