General Dynamics SDE onboarding and first 90 days tips 2026

General Dynamics SDE Onboarding and First 90 Days Tips 2026

TL;DR

General Dynamics onboarding for SDEs is highly structured but slow-moving, averaging 22 business days from offer to badge access. The first 90 days prioritize security clearance progression, system access, and tribal knowledge absorption—not coding output. Most SDEs who fail do so not from technical deficits, but from misreading the organization’s political inertia.

Who This Is For

This is for software engineers joining General Dynamics in classified defense tech roles—particularly those transitioning from Big Tech, who expect agile workflows and rapid autonomy. It applies to SDEs at the GS-13 to GS-15 pay band equivalent (typically $110,000–$165,000 base) in divisions like Mission Systems, Aerospace, or Marine Systems.

What does the General Dynamics SDE onboarding timeline actually look like in 2026?

Onboarding takes 3 to 5 weeks post-offer, with Day 1 access limited to HR portals and mandatory cybersecurity training. The full tech stack and source repos are inaccessible until interim clearance is granted—typically on Day 18. Email and internal chat activate on Day 10, but real system access (JIRA, GitLab, CI/CD pipelines) arrives between Day 20–25.

During a Q3 2025 onboarding review, a hiring manager at General Dynamics Mission Systems halted a new SDE’s integration because their Common Access Card (CAC) hadn’t cleared Phase 2 provisioning. This isn’t a glitch—it’s the standard. The problem isn’t delays; it’s expecting agility in a culture built on audit trails.

Not every day counts. Weekends and federal holidays stall clearance workflows. The government-owned facilities mean IT provisioning follows DoD 8570.01-M compliance, not DevOps speed.

Not lack of preparation, but misaligned expectations—this isn’t onboarding. It’s controlled acculturation.

Not technical ramp-up, but compliance sequencing—your first 10 tasks will be forms, not features.

How do security clearances impact my first 90 days as an SDE?

Interim clearance grants read-only access to project documentation; full clearance (typically achieved by Day 45–60) unlocks commit rights. Until then, you’re shadowing, not shipping. In one case, a new SDE at General Dynamics Marine Systems spent 38 days in “observer mode” because their final adjudication was delayed by a credit check anomaly.

Your first code commit will likely occur in Week 6—sometimes Week 8. Pushing earlier is rare and requires sponsorship from a cleared principal engineer. Clearance level (Secret vs. Top Secret) also dictates team placement: Top Secret projects begin technical onboarding faster but demand stricter separation of duties.

The clearance process isn’t a barrier to work—it’s the work.

Not technical stagnation, but compliance velocity.

Not bureaucracy as noise, but bureaucracy as signal: your adherence to process is being evaluated more than your GitHub contributions.

What tools and systems will I use as a General Dynamics SDE?

You’ll work in locked-down environments: GitLab on-premise instances, JIRA with custom DoD workflows, and Jenkins for CI/CD—all behind two-factor CAC authentication. Local development is restricted. Docker containers require approval. VS Code is permitted; IntelliJ needs a waiver.

In a 2024 debrief, a team lead rejected a candidate’s suggestion to migrate to GitHub Enterprise because “audit lineage in on-prem GitLab is already mapped to our RMF control set.” That’s the mindset: tooling exists to serve compliance, not developer experience.

Not modern tooling, but auditable tooling.

Not integration speed, but traceability depth.

Not innovation in stack, but permanence in control frameworks.

You’ll spend hours in eMASS (Enterprise Mission Assurance Support Service) and DIACAP/RMF documentation portals. Your commit messages must reference control IDs. Your pull requests require compliance tags. This isn’t incidental—it’s core to the engineering model.

How should I navigate team dynamics and mentorship in the first 30 days?

Your assigned mentor is often overcommitted—expect 30 minutes per week, not daily standups. Peer mentorship is unofficial but critical. In a Q2 2025 post-mortem, a failed onboarding case showed the new SDE waited 27 days to ask a teammate for schema documentation, assuming “it would be pushed to me.” It wasn’t.

Initiate contact on Day 2. Ask for the “unwritten runbook”—the one not in Confluence. In one debrief, a hiring manager praised a SDE who, on Day 3, requested a walkthrough of the last three change approvals for their subsystem. That signal—proactive curiosity within bounds—was the deciding factor in their early trust calibration.

Not formal mentorship, but informal sponsorship.

Not waiting for structure, but mapping the shadow workflow.

Not visibility through output, but credibility through context absorption.

You are being assessed on your ability to operate within silent hierarchies, not your ability to disrupt them.

How is performance evaluated during the first 90 days?

Performance is not measured by tickets closed or code shipped. It’s assessed through compliance adherence, meeting attendance, and precision in reporting. Weekly status updates must follow the 5-3-1 format: 5 tasks, 3 risks, 1 escalation. Deviate, and you signal poor process alignment.

In a 2024 HR review, a high-potential SDE was flagged for “informal communication patterns” after using Slack-like shorthand in email (“FYI, patch deployed”). The feedback: “Use full sentences. Tone reflects protocol awareness.” That wasn’t nitpicking—it was a cultural litmus test.

Not velocity, but verifiability.

Not autonomy, but alignment.

Not initiative in action, but initiative in approval chains.

Your first review occurs at 60 days, not 90. It’s conducted by your manager and a functional reviewer from the security office. Coding skills are table stakes; operational discipline is the variable.

What are the hidden expectations no one tells SDEs about?

You are expected to read acquisition policy. Specifically, DFARS 252.204-7012 and NIST 800-171. Not skim—understand. In a hiring committee meeting, one candidate lost an offer after failing to explain how their CI pipeline addressed CUI (Controlled Unclassified Information) handling. “He knew Kubernetes,” the security lead said, “but not the data boundary.”

You must attend at least two program management reviews (PMRs) in your first 45 days—even if not required. Sitting silently in the back signals engagement. One SDE was fast-tracked after asking a precise question about test waiver documentation in a PDR (Preliminary Design Review). The technical content was minor. The signal—operational literacy—was major.

Not just writing code, but defending control narratives.

Not just solving bugs, but mapping them to risk registers.

Not just being smart, but being bureaucratically legible.

The fastest way to fail is to assume this is a software company. It’s a compliance-delivery vehicle that uses software.

Preparation Checklist

Complete all pre-onboarding paperwork within 48 hours of acceptance—delays cascade.
Study DFARS 252.204-7012 and NIST 800-171 basics; know where CUI resides in SDLC.
Set up CAC-compatible hardware: Windows 11 with TPM 2.0 or approved Mac with Jamf.
Map the org chart of your division; identify not just your manager, but the security POC and COR (Contracting Officer’s Representative).
Work through a structured preparation system (the PM Interview Playbook covers defense tech onboarding with real debrief examples from GD, Lockheed, and Raytheon).
Prepare a 30-60-90 plan focused on compliance milestones, not feature goals.
Schedule informal 15-minute intro calls with 3 team members before Day 1.

Mistakes to Avoid

BAD: Showing up on Day 1 asking for API keys and GitHub access. You’ll be seen as reckless. The systems aren’t designed for immediate access—your urgency reads as ignorance of protocol.

GOOD: Acknowledging access is phased and asking for the compliance checklist for your role.

BAD: Rewriting a script to “improve efficiency” without approval. One SDE automated a log upload task and triggered a SOX audit violation. They were reassigned within a week.

GOOD: Documenting the inefficiency and submitting a change request through the engineering review board.

BAD: Using informal language in written comms. “Let’s push this fix” in an email triggers red flags.

GOOD: Writing “Recommend initiating deployment of patch GD-MS-2026-087 following regression verification” — precision over brevity.

FAQ

What salary can I expect as a new SDE at General Dynamics in 2026?

Base pay ranges from $110,000 to $165,000, depending on clearance level and location. Arlington roles average 12% higher. Bonuses are rare; retention is driven by stability, not incentives. Your offer is likely non-negotiable—counteroffers are viewed as poor cultural fit signals.

How long does it take to get meaningful work as a new SDE?

Meaningful work begins around Day 45, after full clearance and system access. Until then, your role is to absorb documentation, attend reviews, and build credibility. Shipping code before Day 30 is uncommon and often discouraged. Value is demonstrated through comprehension, not output.

Is remote work possible during onboarding?

Hybrid is standard post-onboarding, but onboarding requires on-site presence for CAC issuance and facility badging. Remote start requests are denied 90% of the time. Expect to relocate or commute for the first 4 weeks—this is non-negotiable for defense contractors.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.