layiq

/la·yiq/adjective

worthy; deserving; fitting; suitable.

A role, opportunity, or path that merits attention, time, and pursuit.

LAYIQ - Engineering Lead, Air Defense U.S. Air Force Portfolio at Anduril

Own the technical baseline.
Architecture, interface set, and verification approach for the delivered configurations across the portfolio. Set the baseline for each, and update it when field evidence shows the current one is incomplete or wrong. Own the certification and accreditation scope where it applies, working with the teams responsible for those functions.
Integrate systems you do not own.
Most of what these systems connect to belongs to someone else: equipment already on the base, partner command and control we integrate with rather than replace, government-furnished equipment, third-party sensors and effectors arriving through the Lattice SDK, and tactical data links into the wider air picture. Much of that scope arrives underspecified. Negotiate it directly with the partner or the program office, then give Anduril a clear account of what integrates cleanly, what needs an engineering sprint, and what is not technically ready.
Own whether it works at the site.
Define the verification and environmental qualification approach, and explain why the planned coverage is sufficient. Make the call on whether a configuration is ready to ship. When a fielded site degrades, reproduce the failure on real hardware and real data, lead the recovery under time pressure, and feed what you learn back into the product so the next site does not repeat it.
Carry the engineering position with the customer and in pursuits.
Be the engineer the portfolio brings in when the customer's engineers start asking the detailed questions. Translate operational requirements into executable technical scope, write the technical content and the basis of estimate behind a proposal, and say plainly when a commitment outruns what the engineering supports.
Solve the problems that recur across programs.
These programs share hardware, software baselines, and people, so the same failures show up at site after site, and deployment networking is the clearest example. Define the standard the next deployment builds against instead of solving it once per site.
REQUIRED QUALIFICATIONS
Engineering, science, or other technical degree, or equivalent practical experience
8+ years of systems or engineering experience on fielded systems
End-to-end accountability for whether a delivered system actually worked at the site, not only for producing its design artifacts
Has owned the architecture, interface set, and verification approach for a delivered capability or a program's technical scope
Experience integrating third-party and government-furnished hardware and software into a system you were accountable for Ability to define the verification approach for a full scope and explain why the planned coverage is sufficient
Ability to negotiate requirements, deviations, and acceptance directly with a customer's technical representatives, and to write a credible basis of estimate
Works from real hardware and real data: reproduces field failures independently before proposing a fix, and has run recovery at a fielded site under time pressure
Ability to set technical direction for a small number of engineers without managing them
Willingness to travel up to 25% of the time
Eligibility to obtain and maintain an active U.S. Secret security clearance

Engineering Lead, Air Defense U.S. Air Force Portfolio

Employer job description

ABOUT THE TEAM

ABOUT THE JOB

WHAT YOU'LL DO

PREFERRED QUALIFICATIONS

Benefits

What to Do If You Suspect Fraud:

About this listing