Senior Hybrid Network Engineer
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to extract relevant content.
Let's parse the posting.
First paragraph: description of Anduril, mission, Lattice OS, etc. That's about the company, maybe "About the role"? Actually "About The Team" and "About The Job". The "About The Team" is about AIS. "About The Job" describes responsibilities. So we can have sections: About the role (maybe summarizing the job description). Responsibilities (list of duties). Requirements (required qualifications). Qualifications (maybe preferred qualifications). Skills (maybe software background etc). Benefits (benefits description). Pay (salary range). Schedule (maybe not present). We need to include only sections with real content.
Check if schedule is mentioned: No mention of schedule (e.g., full-time, remote, etc). So we should not include Schedule heading.
Pay: There's US Salary Range $191,000—$253,000 USD. Also note "The salary range for this role is an estimate based on a wide range of compensation factors, inclusive of base salary only. Actual salary offer may vary ...". That's content. So we can include Pay section with that info.
Benefits: There's a Benefits paragraph: "Highly competitive equity grants are included in the majority of full time offers; and are considered part of Anduril's total compensation package. Additionally, Anduril offers top-tier benefits for full-time employees, including: At Anduril, we invest in our people. Our comprehensive, competitive benefits package (available at little to no cost to employees) ensures you’re supported in health, recovery, and whatever comes next. For more information, Explore Our Benefits." That's vague but still some content. We can include Benefits section with that paragraph.
Now we need to extract responsibilities list: Under "What You’ll Do" there are bullet-like sentences separated by periods? Actually they are sentences with hyphens? Let's see:
"What You’ll Do Identity federation & degraded auth - extend centralized Keycloak/LDAP identity to disconnected edge; cached-credential authentication when the hub is unreachable; propagate RBAC-by-operation/group to spokes.Data reconciliation & state consistency - own the cloud↔edge data-refresh contract: DSB migration, entity-persist service, CoTv2 bilateral consistency, un-egress republishing cache.Config / architecture drift - automate propagation of cloud-architecture changes (DSB, NCC hub-spoke, DNS) to every edge NixOS closure so spokes never silently fall out of parity.DDIL reliability mandate - define and test failover/reconnect behavior against the High-Availability / DDIL ConOpsSet the technical direction for the sub-team; mentor and receive the support IC."
It seems missing punctuation; but we can treat each hyphen-separated item as a bullet. So we can create a
with - for each:
- Identity federation & degraded auth: extend centralized Keycloak/LDAP identity to disconnected edge; cached-credential authentication when the hub is unreachable; propagate RBAC-by-operation/group to spokes.
- Data reconciliation & state consistency: own the cloud↔edge data-refresh contract: DSB migration, entity-persist service, CoTv2 bilateral consistency, un-egress republishing cache.
- Config / architecture drift: automate propagation of cloud-architecture changes (DSB, NCC hub-spoke, DNS) to every edge NixOS closure so spokes never silently fall out of parity.
- DDIL reliability mandate: define and test failover/reconnect behavior against the High-Availability / DDIL ConOps.
- Set the technical direction for the sub-team; mentor and receive the support IC.
Now responsibilities could be that list.
Now "About The Team" and "About The Job" maybe we can combine into About the role section: a paragraph summarizing the role: As Senior Hybrid Network Engineer, you'll own a net-new, architecturally critical function: the hub-and-spoke contract between the cloud and our on-prem failover edge nodes. You'll ensure on-prem nodes mirror cloud architecture at small scale, keep operating through Degraded, Disconnected, Intermittent, and Limited (DDIL) conditions, and reconcile cleanly with the hub on reconnect - owning everything from identity federation and degraded auth to data reconciliation, config-drift automation, and DDIL reliability testing. You'll also anchor the sub-team, setting technical direction and mentoring ICs. This role requires a strong software background (Go/Rust/Python), distributed-systems fundamentals, cloud architecture depth (GCP preferred), comfort at the edge, and demonstrated ownership of a reliability/SRE or platform-engineering charter.
That's a good prose for About the role.
Now Required Qualifications: list bullet points:
- Currently possesses and is able to maintain an active U.S. Top Secret / SCI Clearance
- Software background is mandatory
- Strong in a systems language (Go/Rust/Python), distributed-systems fundamentals (consensus, conflict resolution, eventual consistency).
- Cloud architecture depth (GCP preferred - VPC, IdP, networking) and comfort at the edge (on-prem, bare-metal deployments).
- Willing to travel as needed
Preferred Qualifications:
- Demonstrated ownership of a reliability/SRE or platform-engineering charter.
We could put Required Qualifications under Requirements section, and Preferred Qualifications under Qualifications section (or Skills). The instruction: Use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map.
We have:
- About the role: prose summary.
- Responsibilities: list of duties.
- Requirements: required qualifications.
- Qualifications: maybe preferred qualifications? Or could be "Qualifications" for both required and preferred? But we have separate headings. We'll put Required Qualifications under Requirements, and Preferred Qualifications under Qualifications (or Skills). Skills could be technical skills like Go/Rust/Python, distributed systems, cloud architecture, etc. But we already have those in requirements. Might be redundant. Better to follow instruction: Use sections only when posting has real, specific content. We have content for Requirements (required qualifications). We have content for Qualifications (preferred qualifications). We have content for Skills? Could list specific technical skills: Go/Rust/Python, distributed systems fundamentals, cloud architecture (GCP), edge/comfort, identity federation, data reconciliation, config drift, DDIL reliability, mentoring. But that overlaps. Perhaps we can put Skills as a list of technical skills extracted from responsibilities and qualifications. But we must not invent or summarize away detail; we must preserve ALL substantive information. If we create a Skills section, we need to ensure we are not omitting any info that belongs elsewhere. It's okay to have overlapping content as long as we preserve all info somewhere. But we should avoid duplication? Not prohibited. However, we should prefer few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But headings are prescribed; we can still include both if they have content. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating many sections with little content. We have decent content for Requirements and Qualifications; each is a list. That's okay.
Skills: Could we derive from the posting? The posting mentions "Strong in a systems language (Go/Rust/Python)", "distributed-systems fundamentals", "cloud architecture depth (GCP preferred - VPC, IdP, networking)", "comfort at the edge (on-prem, bare-metal deployments)", "identity federation & degraded auth", "data reconciliation & state consistency", "config / architecture drift", "DDIL reliability mandate", "mentor". Those are more like responsibilities/qualifications. If we create a Skills section, we would be repeating. Better to omit Skills if not distinct content. The instruction: "include a section ONLY when the posting has real, specific content for it". If we don't have distinct skills beyond what's already covered, we could omit Skills. However, we might still include Skills as a list of specific technical skills: Go/Rust/Python, distributed systems, cloud architecture (GCP), edge, identity federation, data reconciliation, config drift, DDIL reliability. But that is essentially repeating. Might be considered thin. I'd lean to omit Skills.
Benefits: we have content.
Pay: we have content.
Schedule: none, omit.
Now we need to output only HTML fragment, no /, no markdown fences.
Thus output something like:
About the role
As Senior Hybrid Network Engineer, you'll own a net-new, architecturally critical function: the hub-and-spoke contract between the cloud and our on-prem failover edge nodes. You'll ensure on-prem nodes mirror cloud architecture at small scale, keep operating through Degraded, Disconnected, Intermittent, and Limited (DDIL) conditions, and reconcile cleanly with the hub on reconnect - owning everything from identity federation and degraded auth to data reconciliation, config-drift automation, and DDIL reliability testing. You'll also anchor the sub-team, setting technical direction and mentoring ICs. This role requires a strong software background (Go/Rust/Python), distributed-systems fundamentals, cloud architecture depth (GCP preferred), comfort at the edge, and demonstrated ownership of a reliability/SRE or platform-engineering charter.
Responsibilities
- Identity federation & degraded auth: extend centralized Keycloak/LDAP identity to disconnected edge; cached-credential authentication when the hub is unreachable; propagate RBAC-by-operation/group to spokes.
- Data reconciliation & state consistency: own the cloud↔edge data-refresh contract: DSB migration, entity-persist service, CoTv2 bilateral consistency, un-egress republishing cache.
- Config / architecture drift: automate propagation of cloud-architecture changes (DSB, NCC hub-spoke, DNS) to every edge NixOS closure so spokes never silently fall out of parity.
- DDIL reliability mandate: define and test failover/reconnect behavior against the High-Availability / DDIL ConOps.
- Set the technical direction for the sub-team; mentor and receive the support IC.
Requirements
- Currently possesses and is able to maintain an active U.S. Top Secret / SCI Clearance
- Software background is mandatory
- Strong in a systems language (Go/Rust/Python), distributed-systems fundamentals (consensus, conflict resolution, eventual consistency)
- Cloud architecture depth (GCP preferred - VPC, IdP, networking) and comfort at the edge (on-prem, bare-metal deployments)
- Willing to travel as needed
Qualifications
- Demonstrated ownership of a reliability/SRE or platform-engineering charter
Benefits
Highly competitive equity grants are included in the majority of full‑time offers and are considered part of Anduril's total compensation package. Additionally, Anduril offers top‑tier benefits for full‑time employees, including a comprehensive, competitive benefits package (available at little to no cost to employees) that supports health, recovery, and future needs. For more information, see Explore Our Benefits.
Pay
The US salary range for this role is $191,000—$253,000 USD (
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to extract relevant content. Let's parse the posting. First paragraph: description of Anduril, mission, Lattice OS, etc. That's about the company, maybe "About the role"? Actually "About The Team" and "About The Job". The "About The Team" is about AIS. "About The Job" describes responsibilities. So we can have sections: About the role (maybe summarizing the job description). Responsibilities (list of duties). Requirements (required qualifications). Qualifications (maybe preferred qualifications). Skills (maybe software background etc). Benefits (benefits description). Pay (salary range). Schedule (maybe not present). We need to include only sections with real content. Check if schedule is mentioned: No mention of schedule (e.g., full-time, remote, etc). So we should not include Schedule heading. Pay: There's US Salary Range $191,000—$253,000 USD. Also note "The salary range for this role is an estimate based on a wide range of compensation factors, inclusive of base salary only. Actual salary offer may vary ...". That's content. So we can include Pay section with that info. Benefits: There's a Benefits paragraph: "Highly competitive equity grants are included in the majority of full time offers; and are considered part of Anduril's total compensation package. Additionally, Anduril offers top-tier benefits for full-time employees, including: At Anduril, we invest in our people. Our comprehensive, competitive benefits package (available at little to no cost to employees) ensures you’re supported in health, recovery, and whatever comes next. For more information, Explore Our Benefits." That's vague but still some content. We can include Benefits section with that paragraph. Now we need to extract responsibilities list: Under "What You’ll Do" there are bullet-like sentences separated by periods? Actually they are sentences with hyphens? Let's see: "What You’ll Do Identity federation & degraded auth - extend centralized Keycloak/LDAP identity to disconnected edge; cached-credential authentication when the hub is unreachable; propagate RBAC-by-operation/group to spokes.Data reconciliation & state consistency - own the cloud↔edge data-refresh contract: DSB migration, entity-persist service, CoTv2 bilateral consistency, un-egress republishing cache.Config / architecture drift - automate propagation of cloud-architecture changes (DSB, NCC hub-spoke, DNS) to every edge NixOS closure so spokes never silently fall out of parity.DDIL reliability mandate - define and test failover/reconnect behavior against the High-Availability / DDIL ConOpsSet the technical direction for the sub-team; mentor and receive the support IC." It seems missing punctuation; but we can treat each hyphen-separated item as a bullet. So we can create a
- with
- for each:
- Identity federation & degraded auth: extend centralized Keycloak/LDAP identity to disconnected edge; cached-credential authentication when the hub is unreachable; propagate RBAC-by-operation/group to spokes.
- Data reconciliation & state consistency: own the cloud↔edge data-refresh contract: DSB migration, entity-persist service, CoTv2 bilateral consistency, un-egress republishing cache.
- Config / architecture drift: automate propagation of cloud-architecture changes (DSB, NCC hub-spoke, DNS) to every edge NixOS closure so spokes never silently fall out of parity.
- DDIL reliability mandate: define and test failover/reconnect behavior against the High-Availability / DDIL ConOps.
- Set the technical direction for the sub-team; mentor and receive the support IC.
Now responsibilities could be that list.
Now "About The Team" and "About The Job" maybe we can combine into About the role section: a paragraph summarizing the role: As Senior Hybrid Network Engineer, you'll own a net-new, architecturally critical function: the hub-and-spoke contract between the cloud and our on-prem failover edge nodes. You'll ensure on-prem nodes mirror cloud architecture at small scale, keep operating through Degraded, Disconnected, Intermittent, and Limited (DDIL) conditions, and reconcile cleanly with the hub on reconnect - owning everything from identity federation and degraded auth to data reconciliation, config-drift automation, and DDIL reliability testing. You'll also anchor the sub-team, setting technical direction and mentoring ICs. This role requires a strong software background (Go/Rust/Python), distributed-systems fundamentals, cloud architecture depth (GCP preferred), comfort at the edge, and demonstrated ownership of a reliability/SRE or platform-engineering charter.
That's a good prose for About the role.
Now Required Qualifications: list bullet points:
- Currently possesses and is able to maintain an active U.S. Top Secret / SCI Clearance
- Software background is mandatory
- Strong in a systems language (Go/Rust/Python), distributed-systems fundamentals (consensus, conflict resolution, eventual consistency).
- Cloud architecture depth (GCP preferred - VPC, IdP, networking) and comfort at the edge (on-prem, bare-metal deployments).
- Willing to travel as needed
Preferred Qualifications:
- Demonstrated ownership of a reliability/SRE or platform-engineering charter.
We could put Required Qualifications under Requirements section, and Preferred Qualifications under Qualifications section (or Skills). The instruction: Use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map.
We have:
- About the role: prose summary.
- Responsibilities: list of duties.
- Requirements: required qualifications.
- Qualifications: maybe preferred qualifications? Or could be "Qualifications" for both required and preferred? But we have separate headings. We'll put Required Qualifications under Requirements, and Preferred Qualifications under Qualifications (or Skills). Skills could be technical skills like Go/Rust/Python, distributed systems, cloud architecture, etc. But we already have those in requirements. Might be redundant. Better to follow instruction: Use sections only when posting has real, specific content. We have content for Requirements (required qualifications). We have content for Qualifications (preferred qualifications). We have content for Skills? Could list specific technical skills: Go/Rust/Python, distributed systems fundamentals, cloud architecture (GCP), edge/comfort, identity federation, data reconciliation, config drift, DDIL reliability, mentoring. But that overlaps. Perhaps we can put Skills as a list of technical skills extracted from responsibilities and qualifications. But we must not invent or summarize away detail; we must preserve ALL substantive information. If we create a Skills section, we need to ensure we are not omitting any info that belongs elsewhere. It's okay to have overlapping content as long as we preserve all info somewhere. But we should avoid duplication? Not prohibited. However, we should prefer few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But headings are prescribed; we can still include both if they have content. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating many sections with little content. We have decent content for Requirements and Qualifications; each is a list. That's okay.
Skills: Could we derive from the posting? The posting mentions "Strong in a systems language (Go/Rust/Python)", "distributed-systems fundamentals", "cloud architecture depth (GCP preferred - VPC, IdP, networking)", "comfort at the edge (on-prem, bare-metal deployments)", "identity federation & degraded auth", "data reconciliation & state consistency", "config / architecture drift", "DDIL reliability mandate", "mentor". Those are more like responsibilities/qualifications. If we create a Skills section, we would be repeating. Better to omit Skills if not distinct content. The instruction: "include a section ONLY when the posting has real, specific content for it". If we don't have distinct skills beyond what's already covered, we could omit Skills. However, we might still include Skills as a list of specific technical skills: Go/Rust/Python, distributed systems, cloud architecture (GCP), edge, identity federation, data reconciliation, config drift, DDIL reliability. But that is essentially repeating. Might be considered thin. I'd lean to omit Skills.
Benefits: we have content.
Pay: we have content.
Schedule: none, omit.
Now we need to output only HTML fragment, no /, no markdown fences.
Thus output something like:
About the role
As Senior Hybrid Network Engineer, you'll own a net-new, architecturally critical function: the hub-and-spoke contract between the cloud and our on-prem failover edge nodes. You'll ensure on-prem nodes mirror cloud architecture at small scale, keep operating through Degraded, Disconnected, Intermittent, and Limited (DDIL) conditions, and reconcile cleanly with the hub on reconnect - owning everything from identity federation and degraded auth to data reconciliation, config-drift automation, and DDIL reliability testing. You'll also anchor the sub-team, setting technical direction and mentoring ICs. This role requires a strong software background (Go/Rust/Python), distributed-systems fundamentals, cloud architecture depth (GCP preferred), comfort at the edge, and demonstrated ownership of a reliability/SRE or platform-engineering charter.
Responsibilities
- Identity federation & degraded auth: extend centralized Keycloak/LDAP identity to disconnected edge; cached-credential authentication when the hub is unreachable; propagate RBAC-by-operation/group to spokes.
- Data reconciliation & state consistency: own the cloud↔edge data-refresh contract: DSB migration, entity-persist service, CoTv2 bilateral consistency, un-egress republishing cache.
- Config / architecture drift: automate propagation of cloud-architecture changes (DSB, NCC hub-spoke, DNS) to every edge NixOS closure so spokes never silently fall out of parity.
- DDIL reliability mandate: define and test failover/reconnect behavior against the High-Availability / DDIL ConOps.
- Set the technical direction for the sub-team; mentor and receive the support IC.
Requirements
- Currently possesses and is able to maintain an active U.S. Top Secret / SCI Clearance
- Software background is mandatory
- Strong in a systems language (Go/Rust/Python), distributed-systems fundamentals (consensus, conflict resolution, eventual consistency)
- Cloud architecture depth (GCP preferred - VPC, IdP, networking) and comfort at the edge (on-prem, bare-metal deployments)
- Willing to travel as needed
Qualifications
- Demonstrated ownership of a reliability/SRE or platform-engineering charter
Benefits
Highly competitive equity grants are included in the majority of full‑time offers and are considered part of Anduril's total compensation package. Additionally, Anduril offers top‑tier benefits for full‑time employees, including a comprehensive, competitive benefits package (available at little to no cost to employees) that supports health, recovery, and future needs. For more information, see Explore Our Benefits.
Pay
The US salary range for this role is $191,000—$253,000 USD (