FDE Data Engineer- Space (FedD141/FedD147)
Defense Unicorns
<h2><strong>EMPLOYER IS A CONTRACTOR FOR THE U.S. GOVERNMENT. THIS POSITION WILL REQUIRE U.S. CITIZENSHIP.</strong></h2> <h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="3:1-3:20;96-115">Role Description</h2> <p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="5:1-5:495;117-611">This is a forward-deployed engineering role. You'll work shoulder-to-shoulder with mission heroes: the users, operators, and program engineers who run real workloads in real DoD environments. You'll help take UDS Data Capability from "deployable" to "running in production under classification." You will deploy, integrate, and operate our data stack in the mission hero's environment alongside senior engineers, then carry what you learn back into the product so the next engagement is easier.</p> <p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="7:1-7:579;613-1191">The scope of this work varies by engagement. Some programs require standing up a governed data platform to centralize sensor or operational data from known sources, where the problem is well-defined and the priority is building and shipping. Others involve consolidating data across hundreds of interconnected government systems of record with overlapping schemas, deeply interdependent data flows, and significant architectural complexity. You should be comfortable building independently against defined problems and growing into more ambiguous, complex engagements over time.</p> <p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="9:1-9:431;1193-1623">Forward-deployed means aligned with the mission hero, not always on a plane. Most of the work is remote. You'll travel to sites when the engagement calls for it: initial standup, integration work, incident response, training and knowledge transfer. The rest of the time, you'll be on a video call or in a shared chat with that same mission hero. The role is defined by the relationship with the mission hero, not by where you sit.</p> <p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="11:1-11:209;1625-1833">You are a data engineer who can build across the breadth of a data platform (storage, ingestion, streaming, governance, and access) and deliver working solutions in constrained, mission-critical environments.</p> <h2 class="text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="13:1-13:20;1835-1854">Responsibilities</h2> <ul class="[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3" data-sourcepos="15:1-23:159;1856-3973"> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="15:1-15:326;1856-2181">Deploy and configure UDS Data Capability in the mission hero's environment. Stand up the UDS Store (Iceberg, Rook/Ceph, pgvector, Postgres), wire up UDS Transit for air-gap data movement, configure UDS Govern policies (Pepr/Lula), and integrate UDS Connect (Strimzi/Kafka) where streaming or legacy connectors are required.</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="16:1-16:352;2182-2533">Build and support integrations with existing mission systems. Connect UDS Data Capability to legacy databases, flat-file drops, SOAP/REST endpoints, message buses, existing object storage, and identity providers (Keycloak, mission-side SSO). Prior experience integrating with these types of systems is more relevant than experience building on them.</li> <li c