Responsibilities

Own the portfolio operating system
Own the MDI status dashboard and risk register: a live blocker-level register spanning COMSEC and encryption, policy and authorization, technical infrastructure, customer and stakeholder commitments, and program execution. Each entry carries why it matters, what unblocks it, who holds it, and what closes it. Keeping this current and honest is a core deliverable, not an administrative chore
Enforce status hygiene across the portfolio. An initiative open past its baseline end date does not get reported green. You will be the person who makes that call and defends it
Run the operating cadence: core team stand-ups, the weekly cross-functional sync, and program reviews. Note that MDI weeklies deliberately alternate between Australia-friendly and UK-friendly time zones so no region is permanently disadvantaged, which means the cadence itself needs active management
Produce weekly and monthly reporting that leadership can act on, in the established format: Slack-native updates with named owners and explicit red, yellow, green calls
Own the program management toolkit and planning artifacts
Own MDI's work breakdown structure, which is machine-generated from Jira rather than hand-maintained, structured Objective to Initiative to Epic to Task, and currently carries a seven-figure budget rollup. Keep the Jira hygiene good enough that the generated WBS is trustworthy
Own MDI's submissions into the division program manager toolkit: repository entries, point-of-contact tracking, and submission deadlines set by Division Operations. These have slipped before; this role exists in part so they stop slipping
Drive charge code and financial hygiene with Finance. Most MDI initiatives currently run on modeled cost estimates rather than Finance-confirmed codes. Closing that gap is concrete, high-leverage work
Support annual planning and internal research funding submissions: basis-of-estimate workbooks, per-pillar one-pagers, and the small set of hard, checkable statements that define what must be true for each pillar to succeed in the coming year
Track cloud and infrastructure spend against budget. Infrastructure budgets here can be set by default formulas if nobody supplies a real number, so the person watching deadlines materially affects what MDI gets funded
Build cross-program technical fluency

Qualification

Track record owning scheduleStrong written communicationExperience with sovereignWorking knowledge of at least two ofFamiliarity with AUKUSExperience supporting maritimePrior military

Required

6+ years in technical program management, systems engineering, engineering operations, or a comparable role in defense, national security, or another highly regulated technical environment
Demonstrated ability to hold broad technical context across multiple domains simultaneously, networking, cloud infrastructure, and systems integration, without being the deepest expert in any one of them
Track record owning schedule, risk, and dependency management for complex programs with external dependencies you do not control
Experience managing execution across distributed teams in multiple countries or time zones
Strong written communication, specifically the ability to turn messy program reality into a clear, honest status that an executive can act on
Direct experience coordinating with government, military, or regulatory stakeholders
Comfort operating in classified environments. Active US clearance required, TS/SCI preferred
Self-starter who builds structure where none exists. There is no inherited playbook for most of this portfolio
Willingness to travel roughly 20% for program milestones, exercises, customer engagements, and periodic time with the UK and Australia teams
Eligible to obtain and maintain an active U.S. Secret security clearance

Preferred

Experience with classified network infrastructure, including COMSEC handling, Type 1 encryption, or cross-domain solutions
Experience with sovereign, air-gapped, or multinational cloud environments
Working knowledge of at least two of: US NIST 800-53 and risk management framework, Australian ISM and IRAP, UK cyber security model and JSP 440
Familiarity with AUKUS, Five Eyes, or comparable coalition program structures, including export control and foreign national access considerations
Experience supporting maritime, undersea, expeditionary, or autonomous systems programs
Experience with Jira-driven work breakdown structures, earned value or budget rollups, and charge code administration
Background in an organization scaling fast enough that process had to be invented rather than inherited
Prior military, defense civilian, or defense industry experience

Information Security Analyst at Anduril Industries · LumiJobs

Information Security Analyst

Responsibilities

Qualification

Required

Preferred

Benefits

Company

Anduril Industries

More roles at Anduril Industries