Software Engineer

Valinor is a new type of defense and government tech company focused on solving the problems others don't. Our unique model of centralized go-to-market and decentralized engineering allows us to move with unparalleled efficiency to identify unmet needs, build right-sized solutions, and get products where they matter most - in the hands of users. Unlike others in the space, who focus on the flashy problems, Valinor exists to solve the quiet, unaddressed problems-the small but significant ones that lead to cracks in the country's strength, stability, and security.

Backed by General Catalyst, Founders Fund, and Friends & Family Capital, Valinor was founded in 2024 and has established strategic partnerships with Palantir, Anduril, and Helsing. We are building the dream team, and we want you on it.

 

About The Role

We're looking for a software engineer to own the architecture, data handling, and product layer of the software stack at one of Valinor’s product companies, currently in stealth. The system turns raw sensor data into a usable, trusted picture for the end user. You'll work directly with the General Manager and alongside a small team of engineers to rapidly develop a new product. You’ll also partner with product enablement at the Valinor Hub to stand up infrastructure and management.

We see this as a step-up role: someone who has already been part of building a system like this, whether embedded/edge software, sensor or data pipelines, or detection and classification work, as a strong contributor, and is ready to own that kind of architecture for the first time, with direct partnership from the GM on the highest-stakes tradeoffs.

What You'll Do

1. Overall Software Architecture

• Design the software architecture that ties the products data flow, processing, and user-facing product together end to end.

• Define clean interfaces with the sensor integration and API work, so the pieces fit into a coherent whole rather than a collection of one-offs.

• Make and document the core architecture decisions early, since the system needs to flex as we learn what the product needs to become.

2. Data Handling & Pipeline

• Architect the edge vs. cloud processing split — what runs on-system under power/compute constraints versus what gets backhauled.

• Stand up time-series and object storage systems for sensor and telemetry data, and the ingestion pipeline that gets data from the system to backend reliable.

• Design for bandwidth-constrained, compression-aware data transport, and build in the data versioning and observability needed to trust what's flowing in as sensor types multiply.