Lockheed Martin internships

Program finance sits close to the contract and program rather than operating like investment banking. Intern work can involve budgets, forecasts, variance analysis, cost performance, pricing, estimating or business cases. The useful output is an explanation of why cost or schedule moved and what action the program should take. Candidates should be comfortable with accounting, Excel and scenario analysis and should understand that long-duration government programs have formal cost, schedule and contract controls.

Supply-chain and procurement work can involve sourcing, supplier performance, material planning, obsolescence, affordability, production readiness and logistics. A good preparation exercise is a constrained supplier decision: compare lead time, capacity, quality, price, qualification risk and program schedule rather than minimizing purchase price alone. Supplier-quality work is related but distinct because its core output is evidence that a defect was understood, corrective action implemented and recurrence controlled.

Program management and planning are also distinct from finance. Planning focuses on schedules, dependencies and execution logic; program management integrates customer commitments, technical delivery, cost, schedule and risk; program finance focuses on financial performance. Students applying to all three should tailor examples instead of using one generic “project management” story.

Co-op/Summer Intern is also an experience classification on Lockheed Martin’s job architecture, not proof that every student role lasts one summer. The Goleta program-planning role is an example: it expects part-time work during the school year and full-time work during breaks. A semester role, traditional summer internship, high-school program, apprenticeship, international placement, returnship and post-graduate leadership program are different programs even if a search engine puts “intern” in several titles.

Lockheed Martin is not one aerospace internship. The company is organized around four large businesses — Aeronautics, Missiles and Fire Control, Rotary and Mission Systems, and Space — and those businesses put students around different products, customers, facilities and constraints. A systems intern on an aircraft program, a software intern on a space mission, a manufacturing intern in a missile plant and a program-planning intern supporting cost and schedule control can all work for Lockheed Martin while learning almost entirely different jobs. [LM3]

The 2026–27 recruiting cycle is also in transition. Lockheed Martin moved to a new Eightfold careers experience in August 2026 and said candidates who applied before August 17 could be asked to reapply. The new site says new roles are being added regularly. A useful report therefore needs durable work descriptions plus a short, dated opening snapshot rather than a supposedly complete job count. [LM8][LM15]

Lockheed Martin reported about $75.0 billion of 2025 sales. Aeronautics accounted for about $30.3 billion, Rotary and Mission Systems about $17.3 billion, Missiles and Fire Control about $14.5 billion, and Space about $13.0 billion. The scale is useful context because each business has its own product families, engineering methods, operating sites and recruiting needs. [LM3][LM16]

Aeronautics builds and sustains military aircraft including the F-35, F-22, F-16, C-130 and U-2 and includes Skunk Works. Its current business page also points to digital engineering, DevSecOps, modular open systems architectures and connected battlespace work. An intern here is likely to be closer to aircraft structures, flight sciences, avionics, mission systems, embedded or mission software, systems integration, test, manufacturing, sustainment or program execution than to generic “aerospace research.” [LM4]

Missiles and Fire Control develops and manufactures missiles, rockets, precision-engagement systems, sensors, electro-optical systems, integrated air and missile defense and hypersonic technologies. That product mix creates technical routes in guidance, navigation and control, seekers and sensors, electronics, embedded software, modeling and simulation, test, mechanical design and manufacturing. It also creates business routes in program planning, finance, contracts, procurement and supply chain because schedule and supplier execution directly affect delivery programs. [LM5]

Rotary and Mission Systems includes Sikorsky helicopters plus radar, electronic warfare, C4ISR, maritime and undersea systems, cyber, training and logistics. Lockheed Martin says computer systems, software and hardware engineering are the largest professional workforce segment in RMS. A student should therefore separate rotorcraft work from radar software, undersea systems, mission integration, training systems and cyber rather than treating “RMS” as one technical specialty. [LM6]

Space works on precise navigation, secure communications, missile warning, mission command-and-control software, spacecraft and transportation systems, strategic and missile-defense systems and classified national-security products. Space internships can consequently span spacecraft systems, payloads, ground systems, RF/electrical work, propulsion, software, mission operations, manufacturing, integration and test, quality and program functions. The customer and mission can materially change access requirements. [LM7]

Aircraft work is heavily interface-driven. A structures or mechanical intern can analyze loads, materials, thermal environments, mechanisms or durability, but the valuable output is the decision the analysis supports: a geometry change, material selection, repair disposition, test plan or manufacturing release. Electrical and avionics work can involve power, sensors, communications, controls, wiring, electronic hardware and test equipment. Systems engineering can involve requirements, architecture, interface definition, modeling, risk and verification across several disciplines at once.

Strong applicant evidence is therefore a project where requirements were explicit. A Formula SAE component, UAV, avionics board, control system or research vehicle becomes more convincing when the candidate can name the operating conditions, competing constraints, interface failures, verification method and resulting design decision. “Used MATLAB” or “built a drone” is weaker than explaining the model, test, failure and change that followed.

Aeronautics also includes digital engineering and software-heavy work. Candidates targeting mission systems or aircraft software should be ready to discuss software interfaces, hardware-in-the-loop behavior, test automation, reliability and traceable requirements rather than only consumer-app architecture. Skunk Works can involve advanced and sometimes non-public programs; students should discuss only public or authorized project information and should not try to prove interest by soliciting restricted details. [LM4]

MFC combines high-performance engineering with production. Guidance, navigation and control work can involve dynamics, estimation, trajectories, sensor fusion, control laws and simulation. Sensor or electro-optical work can involve signals, optics, electronics, calibration and test. Embedded software can sit close to real-time hardware and must be validated under mission and reliability constraints. A good technical portfolio should make the model, scenario coverage, acceptance criteria and failure analysis visible. [LM5]

A manufacturing intern’s useful output could be a process or tooling change, work-instruction improvement, capacity analysis, root-cause investigation, automation project, material-flow fix or quality intervention. The users are production supervisors, manufacturing engineers, quality, design engineering, supply chain and program operations. Strong applicants should quantify the baseline and the result: cycle time, first-pass yield, scrap, ergonomic risk, downtime, throughput or cost. CAD, statistical tools, automation, controls, manufacturing systems or Lean methods matter only when they are tied to the actual assignment.

That role shows what “business” can mean inside a defense company. A strong applicant should understand critical-path logic, dependencies, schedule risk and Excel well enough to explain how a delayed supplier, failed test or engineering dependency changes a program plan. Generic leadership examples are not enough if the work is quantitative program control.

RMS work can range from Sikorsky rotorcraft to naval systems, radar, electronic warfare, command-and-control, training and cyber. Systems and software applicants need to identify the mission layer. Radar signal processing, a helicopter avionics interface, a training simulation and enterprise IT can all be labeled “software,” but the engineering constraints differ. [LM6]

Dated role · 2026-09-05
For mission software, a credible project shows more than code volume. Explain the operating environment, interfaces, latency or reliability constraint, tests, debugging method and failure behavior. Cyber candidates should distinguish product security, embedded security, network defense, vulnerability analysis and governance. A secure mission system may also be physically and administratively constrained by the facility or program, so remote-work assumptions should come from the requisition rather than a general careers page.

Integration and test deserves its own treatment. Test engineers plan how evidence will show a system meets requirements. Outputs can include test procedures, instrumentation, automation, anomaly reports, data analysis, verification records and root-cause findings. Candidates should be able to explain an acceptance criterion, a test that failed, how they isolated the cause and what design or process decision changed afterward.

Space combines spacecraft, payloads, ground software, mission operations and strategic systems. The work can be highly technical without being purely research oriented. A spacecraft systems intern may trace requirements across power, thermal, communications and payload interfaces; a software intern may debug operational code or ground systems; an electrical intern may work on RF or avionics; a manufacturing/test intern may support hardware integration and environmental qualification. [LM7]

These fields answer different questions and should be read independently.

Facility access is another practical layer. A role can be onsite because it uses a lab, production floor, aircraft, test asset or secure facility even when its clearance field is “None.” Shift, physical, travel, badge, background and safety requirements should be kept separate from formal clearance status.

The practical pattern is team and program variance. Large defense programs can create formal processes, dependencies and periods where an intern waits for access, data, hardware or another team. Other assignments can give substantial real-project exposure. Ask about the named deliverable, what access is needed before useful work can start, who reviews the intern’s work each week, whether a clearance or account setup can delay the project, and what backup work exists if the primary task is blocked.

That question is especially important for an offer comparison. A technically impressive program with months of access delay may teach less than a less famous team where the intern owns a test, model, schedule, process change or software release from start to finish.

Prioritize Lockheed Martin if you want complex hardware/software systems, long-lived programs, rigorous testing and a close connection between engineering and program execution. Aeronautics suits students drawn to aircraft systems, flight sciences, avionics, manufacturing and sustainment. MFC is a strong fit for guidance, controls, sensors, embedded systems, manufacturing and program controls. RMS suits students interested in rotorcraft, radar, maritime, C4ISR, training, cyber and integration. Space fits spacecraft, mission systems, ground software, RF/electrical, propulsion, test and mission operations. Business students should look closely at program planning, program finance, supply chain, procurement and contracts rather than assuming Lockheed Martin is only for engineers.

Be more selective if your top priority is fully remote work, fast product cycles or the ability to discuss every technical detail publicly. Also be selective when a role’s clearance or facility process could consume a large fraction of a short internship. Those constraints can be reasonable for the mission, but they are part of the internship economics and should be compared with actual project ownership and mentorship.

Dated role · 2026-09-05
Before applying, choose the business area and the work layer. Then build one piece of evidence matched to that decision: a requirements-and-test package, controls simulation, embedded system, manufacturing process study, schedule-risk model, supplier analysis or program-finance model. Preserve the direct requisition and map every basic qualification separately. The right question is not “Can I get a Lockheed internship?” It is “Which program can use the evidence I already have, and what legal or facility access does that exact job require?”

Technical preparation should still be function-specific. Aerospace and mechanical candidates should practice explaining load cases, design trade-offs and validation. Electrical candidates should be able to walk through interfaces, failure modes and test evidence. Systems candidates should explain requirements and traceability. Software candidates should prepare coding and debugging stories matched to the role’s language, with operating systems, networking or embedded constraints where relevant. Manufacturing candidates should quantify a process change. Program-planning applicants should understand critical path, schedule risk and Excel. Finance candidates should connect variances and forecasts to program decisions.