A note from the team on where we're going and why Texas makes sense
We didn't pick Austin because it's having a moment. We picked it because the force we build for is already there.
Fort Hood. Joint Base San Antonio. Fort Bliss. Transformation and Training Command (T2COM), headquartered in Austin itself. Texas has more military installations than any other state, and the Austin area sits at the geographic and institutional center of a lot of the Army's modernization energy right now. When your software is built specifically for military logisticians, being physically proximate to where they work isn't a nice-to-have. It's how you stay disciplined about what you're actually building.
A strong engineering talent pool helps us build. Proximity to the Army helps us build the right thing. Austin gives us both.
This isn't a new philosophy for us. Our DC presence keeps us connected to the policy, sustainment, and acquisition communities shaping how the DoW buys and fields logistics technology. El Segundo puts us alongside the Air Force and Space Force installations and the defense technology corridor that surrounds them. Austin extends that same logic to where the Army's modernization energy is concentrated. Every office is a decision about who we need to work side-by-side with, not just where we want to be.
Defense logistics is a domain problem, not just a software problem. Navigator delivers predictive decision support across echelons, from tactical distribution planning to theater-wide sustainment visibility. The goal is the same at every level: shift logistics from reactive to proactive. That work requires staying in contact with the operators, planners, and commands working these problems every day. That's what our offices are for.
If you're an engineer who wants to build software that military logisticians will actually use, we're hiring in Austin.
