Working at Rune Technologies: Culture, Pace and Who Thrives

How Work Gets Done

Rune Technologies, a defense-tech startup founded July 4, 2024, operates with a ~27-person team split between Rosslyn, Virginia and Honolulu. The company's job board lists seven open roles across both locations: Head of Mission Success, Forward Deployed Engineer, and backend specialists in GenAI, simulations, and maps & routing, all in Rosslyn except the Forward Deployed Engineer in Honolulu. No product management roles appear in current postings.

Zero G Talent's board data shows salary bands for senior individual contributors range from $180,000 to $240,000, with a $210,000 median across 13 salaried roles. Zero G Talent's board data shows the board's overall band runs $92,000–$227,000.

See the full compensation breakdown.

Two-thirds of the team are veterans, per co-founder David Tuttle. Forward deployed engineers work directly with military units: the 4th Infantry Division in Colorado Springs and the 25th Infantry Division in Hawaii have used TyrOS in pilot programs. Backend engineers in Rosslyn build the simulations and routing engines. The GenAI role supports LLM integration for course-of-action generation. The Head of Mission Success connects technical delivery to program outcomes.

The two-hub structure reflects operational needs: Honolulu places engineers near Pacific customers; Rosslyn concentrates modeling and infrastructure. Written communication carries weight across the distance.

Pace is set by defense customers. Pilot deployments under the U.S. Army and U.S. Marine Corps have driven development. TyrOS runs on disconnected laptops at the tactical edge: "cloud-capable, but not cloud-required," per Tuttle.

Autonomy is bounded by the mission. The compensation reflects a bar for engineers who can operate with minimal scaffolding.

What the Roles Reveal

Rune organizes around mission-critical technical domains. The role titles (the same Head of Mission Success and Forward Deployed Engineer in Honolulu, plus the backend specializations already mentioned) signal a focus on deployment readiness and domain depth.

No published values document, culture deck, or operating principles page exists. The company's self-presentation lives in its role descriptions.

The two-location structure requires written communication discipline and trust that remote counterparts execute without oversight. Seven active salaried postings as of the latest ingest suggest a growth phase where each hire shifts team composition.

Technical specializations point to a stack built for real-world autonomy and decision support. Simulation fidelity and routing correctness are paramount in environments where failure costs missions.

Absent a published values statement, the operating principles are legible in the constraints the company has chosen: small team, high technical scope, defense-adjacent domains, distributed locations, high compensation. Candidates should read those signals as the company's actual operating principles.

The available research includes no employee-authored values artifacts, internal wikis, or leadership talks. What exists is structural evidence: the roles, the locations, the compensation, the domain.

The Hiring Bar

The hiring bar at Rune Technologies extends Peter Goldsborough's own trajectory: self-taught builders who chose shipping over credentialing, then proved they could operate inside the messiest constraints the U.S. military can throw at them. Goldsborough dropped out of the Technical University of Munich at 19 because he "could already build a lot of things on my own," joined Facebook's AI research team, and later became a chief engineer at Anduril deploying ML infrastructure alongside warfighters in the field.

The current team of roughly 27 carries outsized scope across TyrOS, a logistics platform fusing deep-learning demand forecasting (time-series models across hundreds of variables), traditional optimization for aircraft load planning, and an edge-first architecture that operates on such laptops at the tactical level. The job board reflects that breadth across seven specializations.

Technical depth is necessary but insufficient. Goldsborough spent months doing dozens of customer interviews a day with Army logisticians before writing significant code. Forward Deployed Engineers embed with units: the 4th Infantry Division, 25th Infantry Division in Hawaii.

Mission alignment is tested explicitly. Goldsborough frames the work as a "moral imperative" and "duty to use my skills to build technology to support America." The company's human-centered stance — "humans on the loop" rather than replaced by automation — means the system must amplify expert judgment, not supersede it. That philosophy shows up in TyrOS's design: predictive intelligence that surfaces the fastest resupply route for a hilltop unit low on ammunition, then gets out of the logistician's way.

Autonomy is the final filter. With ~27 people covering ML research, optimization, edge runtime, frontend, mapping, simulation, and forward deployment, there is no room for specialists who need a platform team to unblock them. Goldsborough's advice to founders applies to his own hiring: don't "live in Narnia" about human behavior, run "really difficult" real-world experiments early, and get "real" with customers before the code hardens.

Where Are the Reviews?

The company's founding date (2024) and its small headcount (~27 people across Rosslyn and Honolulu) mean the sample size for any aggregated sentiment is effectively zero.

What exists instead are signals embedded in the roles and compensation bands. The Zero G Talent board lists seven open positions across the specializations detailed in the table below. The overall salary band runs the same range, with the same median across 13 salaried roles, well above market for early-stage defense-adjacent startups.

The role titles themselves carry implicit testimony. "Forward Deployed Engineer" signals that engineers ship to customer environments, work directly with operators, and own outcomes past the commit. "Head of Mission Success" suggests a customer-facing ownership layer. The GenAI backend role indicates active LLM integration work.

Candidates should read these as descriptors of daily scope: you will touch hardware-adjacent stacks, travel to operational units, and debug in environments where "reproduce locally" is often impossible.

The company has not published a handbook, a values deck, or a public engineering blog. Two-sided feedback requires sources. The only attributable sources currently available are the job postings and the compensation data they carry. Everything else — culture, management style, work-life integration, technical debt, leadership accessibility — lives in conversations candidates must initiate.

Who Thrives, Who Burns Out

The ~27-person team operates across Rosslyn and Honolulu: two time zones, two very different operational contexts, one shared mandate to deliver defense-adjacent frontier tech at a pace that belies the headcount. The roles signal a company that ships code to environments where latency, reliability, and clearance-adjacent constraints are daily realities. The compensation reflects market rates for cleared or clearable talent who can operate without hand-holding.

People who thrive here share three traits. First, they treat "forward deployed" as a feature, not a bug. The Honolulu posting puts engineers on-site with customers where requirements shift in real time. Second, they handle multi-location coordination without waiting for a process to be handed to them. With the team split across the DC orbit and the Pacific, synchronous overlap is narrow. Engineers who default to writing things down, recording decisions, and designing APIs that survive async review survive. Third, they tolerate the particular ambiguity of defense-adjacent work: classification boundaries, export-control gates, customer stakeholders who cannot articulate the full threat model but expect the system to handle it anyway.

The burnout profile is the inverse. Engineers who joined expecting a typical startup experience find instead a team carrying the technical scope of an organization several times its size. The GenAI, Simulations, and Maps & Routing backends are production systems with defense-relevant uptime requirements. The Head of Mission Success role exists because the gap between "model works in notebook" and "operator trusts it in theater" is where most projects die; Rune has decided that gap is an engineering problem. That decision pushes operational burden onto the engineering team.

Autonomy at Rune is not the "pick your project" variety. It is the "the customer needs this capability by Friday and nobody else is going to build it" variety. The board shows no junior roles; every posting assumes the candidate can own a subsystem end-to-end.

The two-location reality amplifies both poles. For the right person, Honolulu is a force multiplier: proximity to Pacific customers, shorter feedback loops. For the wrong person, it is isolation: six hours behind the Rosslyn core, expensive travel, a time zone that makes late-afternoon syncs a 7 a.m. start. The Forward Deployed Engineer posting leads with location.

No public Glassdoor corpus exists; the company is too new, too small, too clearance-adjacent for aggregate review sites to be meaningful. The signal lives in the hiring pattern: the absence of junior or support roles suggests the bar has not moved. The salary bands are competitive for the clearance tier.

Compensation at a Glance

Overall band across 13 salaried roles: $92k–$227k. Median: $210k. Source: Zero G Talent board, latest ingest.

Forty-eight hundred miles of ocean and two time zones separate the Rosslyn modeling stack from the Honolulu forward line. The only thing that closes the gap is the judgment of the engineers who show up — same as day one.

Working in frontier tech? Zero G Talent tracks the openings: see every open Rune Technologies role, browse frontier tech jobs, the companies hiring, and the people building the field.