Title: Raytheon PM Onboarding First 90 Days: What to Expect in 2026

TL;DR

The first 90 days as a program manager at Raytheon are not about proving competence — they’re about proving alignment. You will not be measured on deliverables but on integration: how quickly you map stakeholders, absorb program risk posture, and speak the language of compliance. Most new hires fail not from poor execution, but from misjudging the cultural hierarchy — where finance and contracts hold more power than engineering.

Who This Is For

This is for candidates who have passed the final panel and received an offer for a program manager role at Raytheon in 2026, particularly in defense, aerospace, or government-contracted programs. It’s not for generalists or commercial tech PMs expecting agile autonomy. If your background is in fast-paced startups or consumer tech, you are operating with a handicap — this environment rewards precision, documentation, and deference to process over speed.

What does the first week of onboarding look like for a PM at Raytheon?

The first week is administrative saturation, not technical immersion. You will spend 70% of your time in compliance modules, security briefings, and contract data rights training — not meeting your team or reviewing program dashboards.

In Q1 2025, a new PM assigned to a hypersonics program arrived eager to review schedule variances — only to be redirected by HR to complete two overdue ethics certifications before accessing any project files. That delay cost them three days of shadowing the outgoing PM, which later showed up in their 30-day review as “insufficient transition absorption.”

Not agility, but audit readiness is the priority. Not ownership, but accountability trail creation is expected. Your first artifact isn’t a project plan — it’s a signed data access log.

You will attend a mandatory “Program Governance 101” session run by the Contracts Governance Office, not your hiring manager. That’s by design: Raytheon treats program managers as risk nodes, not leaders. Until you pass the ITAR awareness test, you cannot open a single program folder on the secure server.

How are program managers evaluated in the first 90 days?

Performance in the first 90 days is evaluated through risk containment, not delivery velocity. Your manager isn’t tracking sprint completions — they’re tracking how many unapproved changes you initiated (zero should be the answer).

During a Q4 2025 hiring committee debrief, a senior director rejected a positive 90-day review because the PM had “proactively” streamlined a reporting template — without legal’s sign-off. The rationale: “Initiative without approval is noncompliance.” That PM was placed on a PIP despite on-time delivery.

Not innovation, but fidelity to process is rewarded. Not autonomy, but adherence is measured. Not problem-solving speed, but traceability is audited.

You will have two formal check-ins: one at 30 days with your direct manager, and one at 60 days with the Integrated Product Team (IPT) lead. The 90-day review is not a conversation — it’s a package submission: a completed Risk Register Traceability Matrix, a Stakeholder Engagement Log, and a Change Control Waiver History (even if empty).

Bonuses are not tied to scope or schedule — they’re tied to clean audit outcomes. One missed signature on a Configuration Item Approval Form can void your eligibility.

What systems and tools will I need to master immediately?

You must achieve basic proficiency in SAP ERP, DOORS, and the Raytheon Technical Data Management System (RTDMS) within 14 days. Waiting until week three to request access is a red flag.

In February 2025, a PM from a tech startup background assumed Jira would be the primary tool — it wasn’t even provisioned for their program. Their first status report, built in Notion, was rejected because it lacked the mandatory RTF-47B header used in all customer submissions.

Not collaboration tools, but compliance systems are core. Not visibility, but version control is sacred. Not real-time updates, but audit trails are mandatory.

SAP is used for cost accrual tracking; DOORS for requirements traceability; RTDMS for document configuration. If you can’t pull a change history for a single requirement in DOORS by day 10, you’re behind.

Your laptop will have nine mandatory bookmarks pinned — none of them are Slack or Teams. One is the Export Compliance Portal. Another is the Program Confidence Assessment Dashboard, updated weekly by finance.

What cultural norms trip up new program managers?

The biggest cultural shock is the inversion of decision authority: the Contracts Administrator has veto power over the Engineering Lead, and the Program Control Analyst can block a schedule update from the PM.

A 2024 post-mortem review of a failed satellite comms program found that the PM had overridden a finance hold on a subcontractor payment — based on “schedule urgency.” The decision triggered a DCAA audit. The PM was reassigned within 10 days.

Not urgency, but compliance is the default. Not escalation, but pre-approval is required. Not technical merit, but contractual alignment is the filter.

In meetings, deferring to Legal or Contracts isn’t seen as weakness — it’s proof of discipline. Saying “I’ll check with Contracts” is the safest, most respected response to any scope or timeline question.

One unwritten rule: never email a customer without the Communications Office pre-approving the subject line. In 2025, a PM sent a status update with “Urgent: Schedule Risk Identified” in the subject — it was deemed a disclosure event. The customer filed a formal complaint.

Preparation Checklist

  • Complete all ITAR and EAR training modules before Day 1 — access will be blocked until certification.
  • Map the IPT structure and identify the non-negotiable stakeholders: Contracts, Finance, Security, and Export Control.
  • Request SAP, DOORS, and RTDMS access on your first morning — provisioning takes 3–5 days.
  • Draft a 30-day listening plan, not an action plan — your goal is observation, not optimization.
  • Work through a structured preparation system (the PM Interview Playbook covers Raytheon’s governance models with real debrief examples from 2024–2025 panels).
  • Schedule informal coffees with the Contracts Lead and Program Control Manager — not just your direct team.
  • Print and annotate the current Program Management Plan (PMP) — digital markup alone is not considered diligence.

Mistakes to Avoid

BAD: Sending a revised schedule to engineering without finance co-signature.

In 2023, a new PM adjusted task durations to reflect a supplier delay — but failed to update the EVM baseline in SAP. The variance triggered a Level 3 audit. The PM was removed from customer-facing duties.

GOOD: Flagging the delay, documenting the impact, and submitting a formal change request through the Configuration Control Board (CCB) process — even if it takes five days to approve.

BAD: Using agile terms like “sprint” or “backlog” in customer meetings.

One PM referred to “our backlog prioritization” during a DoD review. The customer interpreted it as uncommitted work — a breach of FAR 15.4. The term was banned from all future briefings.

GOOD: Using approved terminology: “unfunded task inventory” or “phase-deferred requirements.” Language is contractual, not descriptive.

BAD: Trying to “streamline” a reporting process in your first 60 days.

A PM from a tech firm replaced a 12-field Excel tracker with a Power BI dashboard. It was immediately disabled — the old file had 17 required audit fields, three of which were hidden.

GOOD: Replicating the existing process exactly for 90 days, then proposing changes through the Process Improvement Request (PIR) system with a compliance impact assessment.

FAQ

What should I focus on in the first 30 days as a Raytheon PM?

Your only job in the first 30 days is stakeholder mapping and process replication. You are not expected to fix anything. The risk of unauthorized changes outweighs any efficiency gain. One misstep in documentation can delay your full integration by months. Do not optimize — observe, document, and repeat.

Is there a formal training program for new program managers?

Yes, but it’s not technical — it’s compliance-focused. You’ll attend the Raytheon Program Governance Bootcamp, a 4-day session covering contract types (FAR vs. DFARS), data rights, and EVM reporting thresholds. Technical training on tools like DOORS is self-paced and unmonitored — failing to complete it is not excused.

How much input do PMs really have on program decisions?

Less than you think. Final decisions on scope, schedule, and spend require consensus from Contracts, Finance, and the Government Customer Rep. The PM synthesizes inputs but rarely decides unilaterally. Your role is orchestration within constraints — not leadership in the startup sense. Influence is earned through precision, not charisma.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.