Raytheon SDE onboarding and first 90 days tips 2026

Raytheon SDE Onboarding and First 90 Days Tips 2026

TL;DR

Raytheon’s SDE onboarding is not about coding speed—it’s about systems judgment under compliance constraints. The first 90 days test your ability to navigate classified environments, not your LeetCode score. Success means aligning technical execution with government contract timelines, not shipping features fast.

Who This Is For

This is for newly hired software engineers at Raytheon who passed the technical screen but have never worked under ITAR, NIST 800-171, or DoD 5015.2 compliance. If your last job was at a startup or FAANG, your velocity expectations are wrong. You’re here because you need to survive the cultural shift—from agile autonomy to audit-driven delivery—without being flagged in your first performance review.

What does the Raytheon SDE onboarding timeline actually look like?

Onboarding takes 22–35 days, not the 10-day estimate HR gives. The delay isn’t bureaucracy—it’s clearance syncing. In Q2 2025, six SDEs started on the same Monday. Three were cleared to code on Day 12. Three waited until Day 31 because their eQIP hadn’t synced with DCSA backend systems. No amount of lobbying your manager moves that needle.

You’ll spend Days 1–5 in mandatory training: Cyber Awareness (90 minutes), Export Control (ITAR, 120 minutes), and Records Management (DoD 5015.2, 75 minutes). These aren’t checkboxes. You’ll be tested. Fail one, and your badge access freezes until retraining. One hire in Tucson failed the export control quiz twice. He was benched for 11 days.

Days 6–14 are tool provisioning hell. You won’t get admin rights. You won’t run Docker locally. You’ll use a locked-down VM with a 12-hour timeout. Your laptop ships with a hardware key. Lose it, and you’re out of access for 72 hours while Raytheon Logistics logs a theft report.

The problem isn’t the tools—it’s the audit trail. Not all software environments are equal, but compliant ones are all slow in the same way. Not security is a barrier, but rather security is the product. You’re not building features—you’re building verifiable, traceable, defensible artifacts.

How much do Raytheon SDEs really make in 2026?

Base salary for L4 SDEs ranges from $112,000 to $128,000, depending on location and prior govcon experience. In Tucson or Arlington, expect the floor. In Colorado Springs or Huntsville, you might hit $125K if you have prior TS/SCI. RSUs are not part of comp. Bonuses average 6.2%, not the 10% some Glassdoor posts claim.

One hire in 2025 listed “$140K total comp” on LinkedIn. The number was real—but included a sign-on bonus amortized over two years and a one-time relocation stipend. Actual recurring comp was $119K + 6% target bonus.

The disconnect isn’t deception—it’s framing. Not total comp is what matters, but liquid comp. You can’t take equity from a defense contractor and sell it. Not salary is the full picture, but billable rate is. Raytheon’s internal bill rate for L4 SDEs is $185/hour. Your salary is 38% of that. The rest covers overhead, audits, and compliance tax.

This isn’t punishing. It’s structural. Not you’re underpaid, but you’re in a different economic model. You trade growth potential for job stability and low layoff risk. In 2024, Raytheon cut 1.2% of tech staff. FAANG peers averaged 7.3%.

What technical systems will I touch in the first 90 days?

You’ll spend 60% of your time in DOORS for requirements tracing. Another 20% in IBM Engineering Lifecycle Management (ELM) for change requests. Only 20% on actual code—usually Java or Ada on Red Hat Enterprise Linux. Python is tolerated but not trusted for production.

One new hire in Indianapolis was assigned to a missile guidance module rewrite. First task: link 347 code files to 121 requirements in DOORS. No coding for 18 days. He pushed back. His mentor said, “You’re not here to write code. You’re here to prove this code was written correctly.”

Not documentation follows code, but documentation precedes it. Not you implement features, but you implement audit trails. The government doesn’t pay for functionality—it pays for proof of functionality.

You’ll use Git, but not GitHub. Raytheon runs on on-prem GitLab with mandatory merge request templates. Every commit must reference a change ticket. No free-form branching. No rebasing. Your feature branch lives for 6 weeks because the change board meets biweekly.

You won’t deploy to cloud. You’ll deploy to isolated enclave networks. CI/CD pipelines exist, but each stage requires manual approval. One SRE in Boston described it as “CI without the CD.” The pipeline stops at staging. Production push requires a 72-hour change advisory board (CAB) approval.

How should I prioritize in my first 30, 60, 90 days?

First 30 days: Learn who owns what. Not understanding systems, but understanding accountability. Identify the gatekeepers—the DOORS admin, the security officer, the CAB scheduler. Map the approval chain for a single code deploy. Do not touch production systems.

One hire tried to “optimize” a CI pipeline by automating the security scan. He bypassed the manual signoff. Incident report filed. His 30-day review noted “lack of procedural judgment.” Not technical ability is in question, but risk assessment maturity.

Days 31–60: Deliver a traced change. Pick a small bug. Fix it. But spend twice as long proving it was fixed correctly. Write the test report. Link it to the requirement. Submit the deviation request if needed. The goal isn’t impact—it’s process fluency.

At Day 57, you’ll have a checkpoint with your supervisor. They won’t ask what you built. They’ll ask: Did you follow the process? Was your paperwork complete? Were your artifacts retrievable?

Days 61–90: Expand scope, not speed. Volunteer for a cross-system integration task. Not to show initiative, but to expose yourself to inter-team dependencies. In a 2025 debrief, a hiring manager said, “She didn’t deliver fast, but she knew where every dependency broke.” That became her strength.

Not velocity matters, but verifiability. Not you shipped early, but you left no audit gaps.

How do performance reviews work for new SDEs?

You get your first formal review at Day 90. It’s not a pass/fail. It’s a risk classification: Low, Medium, or Elevated. Low means you’re cleared for independent work. Medium means you need oversight. Elevated means you’re on a performance improvement plan (PIP).

In 2025, 17% of new SDEs received Elevated. Most were from non-govcon backgrounds. The top reason wasn’t technical deficiency—it was procedural deviation. One engineer from Meta automated a deployment without CAB approval. “I saved two days,” he said. The review noted: “Unacceptable risk tolerance.”

The review uses a 5-point scale across four domains: Technical Execution (30%), Process Adherence (35%), Collaboration (20%), and Security Judgment (15%). Note the weights. Not coding matters most, but process does. Not you solved the problem, but you solved it within bounds.

You’ll be compared to peers hired in the same batch. Not absolute output, but relative compliance. One manager in Dulles said, “We don’t PIP people for being slow. We PIP them for creating risk surfaces.”

Your review feeds into your security clearance standing. A single Elevated rating doesn’t revoke clearance. But two do trigger a DSS inquiry. Not performance is separate from clearance, but performance affects clearance sustainability.

Preparation Checklist

Complete all pre-onboarding eLearning modules before Day 1. Waiting kills momentum.
Bring two forms of government-issued ID for badging. One must be a passport or birth certificate.
Set up encrypted email (Raytheon uses Proofpoint). Test it before arrival.
Learn DOORS NG basics—requirement linking, traceability matrices, change requests.
Work through a structured preparation system (the PM Interview Playbook covers govcon onboarding with real debrief examples from Raytheon and Lockheed 2024 cycles)
Memorize your contract number. You’ll need it for system access requests.
Prepare for a 3-week tool provisioning delay. Have offline study materials ready.

Mistakes to Avoid

BAD: Trying to “streamline” a process on Day 10. One SDE at the Waltham site disabled a logging requirement to speed up a test. The system flagged an audit gap. His mentor had to file a corrective action. Result: delayed project signoff, formal warning.

GOOD: Asking for a dry run. Before touching systems, request a sandbox walkthrough with your mentor. Document every step. Get signoff on your approach before execution. One hire in Indianapolis did this. His first change was 10 days late—but fully compliant. Praised in review.

BAD: Using consumer cloud tools. A new SDE used Google Keep to track tasks. Screenshots leaked in a shared VM. Security incident report filed. Device wiped. Clearance review triggered.

GOOD: Writing everything in OneNote or Raytheon-approved SharePoint. Even meeting notes go in labeled, tagged notebooks. One engineer kept a daily log with timestamps. During a DSS audit, it was used as evidence of procedural discipline.

BAD: Assuming “small changes” don’t need tickets. A developer fixed a typo in a UI string without a change request. The string was tied to a certified requirement. Deviation detected in regression scan. Rollback required.

GOOD: Treating every change as auditable. Even documentation updates get a ticket. One SDE created a template for minor fixes. His manager reused it across the team. Became a best practice.

FAQ

Is Raytheon’s onboarding slower than FAANG?

Yes. FAANG onboarding averages 5 days to code. Raytheon averages 22–35. The delay isn’t inefficiency—it’s compliance syncing. Not time to first commit is the metric, but time to first auditable commit. That’s what matters.

Will I work on cutting-edge tech as a new SDE?

Rarely. First projects are maintenance, not innovation. You’ll work on certified, audited systems. Not new tech impresses leadership, but zero audit findings do. One hire expected AI/ML. Got Ada code refactoring. Stayed for stability, not novelty.

Can I transfer to a different Raytheon division later?

Yes, but not before 18 months. Transfers require clearance revalidation and manager approval. Internal mobility is real but slow. Not moving fast is possible, but moving with audit continuity is required. Plan tenure in years, not months.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.