Intelligence Surveillance Reconnaissance (ISR) Systems Engineer

You are the sensor technician. The intelligence picture the MAGTF is flying off of lives or dies on whether the hardware you maintain is transmitting clean data — and right now, nobody on the gun line, the air desk, or the S-2 bench knows your name, which means your job is to keep it that way.

You check in to a Marine Unmanned Aerial Vehicle Squadron, a Radio Battalion ISR element, or a MEF Intelligence Group detachment, and the staff sergeant in charge of your section sits you down in front of a rack of sensor hardware and tells you what it does and why it matters. The first six months are operator-level work: power-up procedures, built-in-test sequences, basic software checks on the collection systems, cable management on the antenna arrays, and the maintenance log entries that track every system anomaly you find or create. Field operations are where the job shows its teeth — you occupy a sensor site, run the ground-based radar or persistent surveillance sensor through its initialization sequence, troubleshoot the integration feed into the command and control network when it drops, and sit on the radio until the data link comes back up. You also pull your share of working parties, motor-T maintenance on the vehicles that move the equipment, and the administrative overhead of an ISR section — accountability of sensitive items that require your signature on a hand receipt sub-sub-receipt, daily. The job is not glamorous at this tier; it is disciplined, exact work in a windowless SCIF and in a fighting hole at night, and the analyst section depends on it.

• 01Execute the power-up, initialization, and built-in-test sequence for the AN/TPS-80 G/ATOR ground radar system to the operator-level technical documentation standard — no shortcuts on the BIT, because a missed fault code at initialization is a failed collection window at H-hour.
• 02Perform organizational-level preventive maintenance on ground-based ISR sensor hardware — antenna assemblies, processing units, power conditioning equipment, cable connectors — and log every discrepancy in the maintenance tracking system before the section chief finds it.
• 03Troubleshoot a basic data link integration failure between the sensor collection system and the command and control network — isolate the fault to hardware, software, or connectivity, then call it accurately to the section chief rather than guessing.
• 04Handle, account for, and secure TS/SCI-associated hardware and media under the requirements of DoD 5240.1-R and the unit's information security program — no sensitive item leaves your hands without a witnessed hand-receipt transfer.
• 05Zero and qualify the M4 to the Annual Rifle Training standard — Expert is the floor, because ISR sites need ground defense and the section chief is not standing you in a gun position you cannot fill.
• 06Write a legible maintenance discrepancy report and a system status report for the watch officer that accurately describes what is broken, what you did about it, and what the operational impact is — in words the S-2 can pass to the commander.

• —NAVMC 3500.20 — Intelligence/Electronic Warfare Training and Readiness Manual (the source of every 2651 individual and collective task you are evaluated against; know your T&R events and where you stand on each).
• —MCWP 2-26 — MAGTF Intelligence Operations (the doctrinal framework your collection systems feed; operators who understand the intelligence cycle work smarter than operators who just push buttons).
• —JP 2-01 — Joint Intelligence Support to Military Operations (the joint doctrine your ISR feeds into; understanding why the JISE cares about your sensor uptime changes how you treat the maintenance window).
• —DoD 5240.1-R — Procedures Governing the Activities of DoD Intelligence Components (the legal and policy framework governing your collection activities — read it before you touch collection hardware, not after).
• —Technical documentation, AN/TPS-80 G/ATOR ground radar system, MCSC Program Manager (the operator's technical reference for the primary system; your section chief will verify you know it).
• —MCO 6100.13 — Marine Corps Physical Fitness, Body Composition, and Military Appearance (PFT/CFT standards you maintain on a watch rotation that does not care about your sleep schedule).

• —1st-Class PFT and CFT under MCO 6100.13 — ISR collection sites require Marines who can move equipment under load and occupy a fighting position; a 2nd-Class score in an ISR section draws attention.
• —Annual Rifle Qualification: Expert badge maintained — the site defense plan at a sensor position depends on every Marine in the section carrying their sector.
• —TS/SCI clearance in adjudicated status before reporting to any operational billet — a clearance issue at this rank is a career-defining problem, and financial and legal issues are the most common triggers.
• —T&R events for 2651 at the NAVMC 3500.20 individual task level completed and signed within the unit's timeline — unqualified junior operators are a liability on a collection site and the section chief's FitRep notes it.
• —Sensitive item accountability 100% at every formation and every field operation — one discrepancy triggers an investigation that starts with your name on the hand receipt.

• —Skipping the built-in-test sequence because the system "worked fine yesterday." The fault that kills a four-hour collection window during a named operation is almost always the fault the operator decided not to log during initialization.
• —Reporting a data link failure as a sensor failure — or vice versa — without isolating the fault first. The section chief who troubleshoots your mis-diagnosis loses 45 minutes the watch officer is asking about.
• —Allowing a TS/SCI media item to sit unaccounted for between shifts, even for five minutes. The information security officer does not accept "I was going to log it." The unit's security manager now knows your name.
• —Posting anything on social media that references your unit, your equipment, your location, or your mission. The S-2 runs OPSEC sweeps; ISR data and sensor capability are high-value targeting indicators, and one post ends the clearance.
• —Signing a hand receipt sub-receipt for equipment you have not physically inventoried. You are responsible for what you sign for, and the equipment that comes up missing during a field operation comes off your pay.

The good junior 2651 is the operator the section chief trusts with the sensor initialization sequence at 0300 without standing over them. By month nine the watch officer is routing system status questions directly to the LCpl who wrote the last discrepancy report correctly; by month eighteen the section chief is putting their name on the Corporals Course packet and the Cpl board recommendation at the same time.

You are the first NCO between the junior operators and the collection hardware. The section chief owns the mission; you own the systems health and the junior operators who keep them running — and the watch officer is learning your name because the data link status report lands in his inbox with your initials on it.

You run the day-to-day systems readiness picture for your ISR section — maintenance tracking, preventive maintenance scheduling, equipment accountability, operator qualification management for the junior Marines under you, and the interface between your section chief and the maintenance work orders that keep the collection systems operational. You write proficiency and conduct marks that feed your Marines' composite scores. You sit through more technical training than your junior operators, you are the first troubleshooter the section chief calls when the data feed degrades mid-collection, and you start working the software integration layer above the operator level — understanding how the ground-based radar feed and the persistent surveillance system feeds are aggregated and passed to the C2 network, not just whether the power indicator is green. You will also attend additional technical training — system-specific courses at the schoolhouse — and you start showing up in the unit's internal training planning cycle as the NCO who briefs junior operators on new equipment or updated technical procedures.

• 01Manage the section's preventive maintenance schedule across multiple ISR systems — AN/TPS-80 G/ATOR, persistent ground surveillance sensors, data link equipment — and close maintenance work orders before the section chief has to ask about them.
• 02Troubleshoot a multi-system integration failure — sensor, data link, C2 network — and correctly isolate the fault to the appropriate system layer before calling the section chief or requesting external maintenance support.
• 03Brief junior operators on a new technical procedure or a system configuration change using the technical documentation as the source, not memory — and verify comprehension before the section goes to a collection window.
• 04Write proficiency and conduct marks for junior Marines that the section chief can defend at a Cpl board — observed behavior, accurate assessment, no inflation.
• 05Execute sensitive item accountability for the section's TS/SCI-associated hardware at every formation, every field operation, and every equipment transfer — inventory confirmed before you sign, not after.
• 06Operate battery-net communications and pass a clear system status report to the watch officer that accurately characterizes collection system readiness and operational impact of any degradation.

• —NAVMC 3500.20 — Intelligence/EW T&R Manual (Cpl-level individual and collective tasks; you are building toward section-chief qualification and the T&R tasks define the path).
• —MCWP 2-26 — MAGTF Intelligence Operations (the intelligence operations framework your collection systems support; Cpls who understand the consumer end of the ISR pipeline maintain systems better than those who only know the hardware).
• —Technical documentation, AN/TPS-80 G/ATOR ground radar system, MCSC Program Manager (own the technical manual; your section chief verifies your knowledge of it before trusting you with the initialization sequence alone).
• —JP 2-01 — Joint Intelligence Support to Military Operations (joint context for the collection mission; understanding the joint picture makes you a better section NCO than one who only knows the unit's organic systems).
• —MCO 1610.7 — Performance Evaluation System (you write proficiency and conduct marks now; understand what Section A of a FitRep looks like before you are writing one).
• —MCO 1400.32 — Marine Corps Promotion Manual (composite scores, cutting scores, and the Sergeants Course eligibility you are building toward — pull the current MARADMIN for the 0270/2651 cutting score).

• —Corporals Course graduate — required and gated; the Sgt board does not move without it and the section chief is tracking the slot.
• —1st-Class PFT and CFT — junior operators do not respect a systems NCO who cannot carry his own weight on a sensor site occupation.
• —TS/SCI clearance maintained and adjudicated — any reportable incident (financial, legal, foreign contact) goes to the security manager immediately, not after you decide how bad it is.
• —Section maintenance readiness rate tracked monthly — the section chief and the watch officer see the equipment status report, and a systems NCO whose section's equipment is chronically red is not competitive for Sgt.
• —Composite score current against the TFRS / MARADMIN cutting score for 2651 to Sgt — pull the current cycle before you ask the section chief where you stand.

• —Closing a maintenance work order before the system passes the post-maintenance verification check. The collection window that fails because of an unclosed discrepancy opens a unit-level investigation that begins with the last signature on the maintenance log.
• —Letting a junior operator brief a system procedure from memory because they seem confident. The technical documentation is the standard; the procedure that diverges from it is a training failure and your name is on the section training plan.
• —Reporting sensitive item accountability as complete before physically counting. One unverified item that comes up missing in the field costs the section a day and generates a report of survey that starts with your last signed inventory.
• —Allowing a data link configuration change without documenting the change and the rationale. The configuration that gets pushed during a late-night troubleshoot and not documented is the change the next watch cannot reverse when the system behaves unexpectedly.
• —Skipping the Corporals Course packet because the slot is "probably next quarter." Slots evaporate in ISR billets because the section is always forward or on-call; the cutting score does not wait for a convenient training window.

The good 2651 Cpl is the NCO the section chief puts on the hardest integration problem — degraded data link, unfamiliar C2 software, new system configuration pushed by the program office — and trusts to either fix it or correctly characterize why it cannot be fixed without higher maintenance support. His junior operators are T&R-qualified and his maintenance logs are clean before the section chief reviews them. The watch officer knows this Cpl's name because the system status report is always on time and accurate.

The section is yours. The collection mission, the equipment, the Marines operating it, and the data link feeding the S-2 — all of it runs on your watch. The watch officer calls you first when the feed drops, and the answer you give had better be accurate, because the intelligence picture the MAGTF is working off of is only as good as the sensors your section is keeping alive.

You run an ISR systems section — typically four to eight Marines operating ground-based radar, persistent surveillance systems, and data link equipment in support of the MAGTF intelligence collection plan. You are responsible for their training, their T&R qualifications, their equipment, and their conduct. You write FitReps on your Cpls. You brief the section on the collection plan before the watch starts, you supervise the initialization sequence and the system integration checks, you troubleshoot multi-system failures that the Cpl cannot resolve at the organizational maintenance level, and you are the voice the watch officer trusts when she needs an accurate characterization of sensor capability and degradation. You start showing up in the S-2 planning cycle — the collection management officer coordinates with your section chief for collection window allocation, and as a Sgt you are the NCO who sits in those coordination meetings for your section and translates operational requirements into sensor employment. The technical depth at this tier goes up: you are managing software configurations, understanding the integration between the AN/TPS-80 G/ATOR and the C2 architecture, and in pre-deployment training you are the one briefing the battalion intelligence officer on what your section can and cannot do against the anticipated threat.

• 01Occupy a sensor site, initialize the AN/TPS-80 G/ATOR and supplementary collection systems, integrate the feeds into the unit C2 network, and pass a collection-ready report to the watch officer without coaching from the OIC.
• 02Troubleshoot a multi-layer integration failure — sensor hardware, data link, software configuration, C2 network interface — and correctly characterize the fault and the fix timeline to the watch officer with enough accuracy that she can brief the S-2.
• 03Write FitReps on your Cpls — Section A with observed behavior, action-result-impact, and attribute ratings the reporting senior can defend — because the ISR occfield is small and a weak FitRep cycle has long memory.
• 04Build and execute a section training plan that drives T&R event completion for every Marine in the section, integrates new equipment technical training as system upgrades arrive, and satisfies NAVMC 3500.20 collective task requirements.
• 05Brief the collection management officer and the battalion intelligence officer on your section's organic sensor capabilities, current system readiness, collection windows available, and the operational impacts of any degraded capability — in language the intelligence professional can translate into the collection plan.
• 06Mentor your Cpls into section-chief-candidate-qualified and Sergeants Course-ready Marines — technical fundamentals, T&R completion, FitRep awareness, and composite score management.

• —NAVMC 3500.20 — Intelligence/EW T&R Manual (Sgt-level individual and collective tasks; you build the section training plan off this and you are evaluated against it).
• —MCWP 2-26 — MAGTF Intelligence Operations (the operational framework your collection section supports; section chiefs who understand the intelligence cycle brief the S-2 better and get more useful collection requirements in return).
• —FM 3-55 — Information Collection (joint doctrinal reference for ISR operations; the USMC operates alongside this alongside MCRP 2-22, and the joint language is what you will use when working with Army or joint ISR elements).
• —JP 2-01 — Joint Intelligence Support to Military Operations (joint intelligence framework; ISR sections routinely support joint task forces and the section chief who only knows USMC doctrine gets caught flat-footed at the JTF intelligence synchronization meeting).
• —DoD 5240.1-R — Procedures Governing the Activities of DoD Intelligence Components (the legal framework governing collection; section chiefs are responsible for ensuring their section's collection activity stays within the authority granted by the collection plan and the legal review).
• —MCO 1610.7 — Performance Evaluation System (you write FitReps on your Cpls now, not just receive them; understand relative-value mechanics before you submit the first one).

• —Sergeants Course graduate — required and gated; no path to SSgt without it.
• —1st-Class PFT and CFT; the section average is watched, and a section chief who cannot carry his own load on a sensor site occupation sets the wrong standard for a physically demanding field assignment.
• —TS/SCI clearance maintained — any reportable incident goes to the security manager same day, regardless of how small it seems, because the clearance adjudicator does not distinguish between "minor" and "unreported."
• —Section T&R completion rate at or above the unit standard in NAVMC 3500.20 — the collection management officer and the battalion S-2 see the unit training report, and a section chief with chronic T&R gaps does not get the complex collection assignments.
• —Composite score current against the TFRS / MARADMIN cutting score for 2651 to SSgt — pull the current cycle and track it monthly.

• —Verbal-only corrections on system procedures. If a Cpl is running the initialization sequence wrong, the correction goes in the training record — not because you want to paper your section, but because the operator who gets injured or causes a collection failure on a procedure you corrected verbally twice leaves you with nothing to defend yourself with.
• —Accepting a "green board" on system status from a Cpl you have not personally verified during a pre-deployment readiness cycle. The degraded sensor that the Cpl marked green because he did not want to hold up the timeline is the sensor that fails at the worst possible moment in the collection window.
• —Underestimating the collection management briefing. The intelligence officer who receives a vague "we can probably do that" answer from the section chief will build a collection plan around an assumption, and the assumption will be wrong. Give accurate capability characterizations, even when the accurate answer is "no."
• —Allowing the section's TS/SCI media and hardware accountability to slip during a high-tempo collection window. A missing item discovered after a 72-hour collection rotation opens a loss investigation that traces back to your last signed accountability record.
• —Hiding a system malfunction from the watch officer to avoid breaking the collection window. The collection that runs on a degraded sensor produces data of unknown reliability; the intelligence that gets acted on based on that data is the section chief's problem.

The good 2651 Sgt is the section chief the watch officer calls when the data link goes down in the middle of a named operation, because the answer she gets will be accurate, the fix timeline will be honest, and the workaround will already be in motion. His Cpls are FitRep-ready and the section's T&R events are current before the S-2 checks. The collection management officer has started including the section chief in the planning cycle — not just the execution — because the guidance coming out of that meeting is better when the NCO who runs the sensors has a voice at the table.

You are the senior systems NCO. You own the technical standard for multiple ISR sections, you advise the intelligence officer on sensor capability in operational planning, and the SSgt-to-GySgt board is reading your FitRep profile against every other ISR NCO in the Marine Corps who wants the same billet.

You run the enlisted side of an ISR systems platoon or serve as the senior NCO for a multi-section ISR element — managing two to four section chiefs, their Marines, and the collective readiness of the collection systems across all of them. You write three to four Sgt FitReps per cycle, you build the platoon training calendar in concert with the OIC, you advise the intelligence officer on sensor employment during the operations planning process, and you start liaising with external stakeholders — the program manager office at Marine Corps Systems Command (MCSC) when system upgrades or technical bulletins come down, the intelligence community elements at NSA or DIA when collection architecture questions arise during joint operations, and the collection management section at the MEF when the battalion is plugged into a larger ISR architecture. The job at SSgt is no longer purely technical execution — it is translating technical capability into operational advice. The section chief who can only tell the S-2 what the system does technically, but cannot say what collection requirement it can satisfy and at what confidence level, is not competitive for the GySgt billets the Corps needs in ISR.

• 01Build a platoon training plan that drives NAVMC 3500.20 T&R event completion across multiple sections simultaneously — synchronized with the unit operational schedule, the system maintenance cycle, and the equipment upgrade timeline from MCSC.
• 02Advise the intelligence officer on ISR sensor employment for an operational planning cycle — articulate organic collection capabilities, coverage gaps, integration requirements with joint ISR architecture, and the realistic collection windows the ground sensor picture can deliver.
• 03Write three to four Sgt FitReps per cycle that the reporting senior can defend at the battalion FitRep board — clean Section A, defensible relative value, no inflation the SSgt-to-GySgt board will see through.
• 04Coordinate with MCSC program office representatives during a system technical bulletin or capability upgrade cycle — receive the change, assess impact to operational readiness, build the training plan for the new configuration, and brief the OIC on timeline and risk.
• 05Mentor three section chiefs into SSgt-board-ready candidates without letting your own Career Course prep fall behind.
• 06Run a system degradation debrief for the intelligence officer and the collection management section after a collection failure — accurate fault characterization, root cause, corrective action, and timeline to restored capability.

• —NAVMC 3500.20 — Intelligence/EW T&R Manual (platoon-level collective tasks you are building training against across multiple sections).
• —MCWP 2-26 — MAGTF Intelligence Operations (at SSgt you start shaping how the ISR collection plan is built, not just executing it; you need to understand the whole intelligence operations framework).
• —FM 3-55 — Information Collection (joint ISR doctrine; SSgts who own joint ISR language are the ones the MEF intelligence section calls when a joint task force integration question needs a technical answer).
• —JP 2-01 — Joint Intelligence Support to Military Operations (joint framework for the ISR architecture your sections contribute to; understanding the JISE and the DIA/NSA equities at SSgt prepares you for the senior billets).
• —MCO 1610.7 — Performance Evaluation System (FitRep mechanics you now write against and teach your section chiefs to understand).
• —MCO 1400.32 — Marine Corps Promotion Manual (SSgt-to-GySgt board mechanics, FitRep relative-value impact; pull the current MARADMIN for the board cycle and track your profile against peers).

• —Career Course (resident or distance) completed; SNCO Academy Senior Course slated before the GySgt board window opens.
• —Black Belt MCMAP minimum — at SSgt you are one of the senior instructors in the unit and the platoon is watching.
• —Platoon T&R completion rate and equipment readiness rate above the battalion standard — the MEF intelligence officer sees the collective ISR readiness report and knows which ISR element is dragging.
• —FitRep profile above battalion average — the SSgt-to-GySgt board is FitRep-driven for ISR NCOs in a small, competitive occfield, and one weak cycle moves the timeline by years.
• —TS/SCI clearance maintained with no reportable incidents — at SSgt a clearance issue that surfaces during a FitRep cycle ends the GySgt conversation before it starts.

• —Writing a FitRep as a performance summary instead of an evaluation. The GySgt board at HQMC reads hundreds of FitReps from the ISR community; the SSgt who inflated his Sgts produces a grade-inflation record that the board recognizes and discounts.
• —Accepting MCSC technical bulletin implementation on an operator's verbal confirmation that "the system works." The technical bulletin change that was not properly verified through a post-implementation functional check is the system failure the section cannot explain six months later.
• —Briefing the intelligence officer with vague capability language because you are not sure of the answer. The collection plan built on a vague answer produces a collection failure, and the intelligence officer does not distinguish between "the SSgt was not sure" and "the SSgt gave me bad information."
• —Letting one section chief's T&R currency slide because the section is operationally deployed. T&R currency is a readiness issue; a deployed section chief with lapsed qualifications is a liability and the MEF intelligence section's readiness reporting will flag it.
• —Hiding platoon-level system readiness problems from the OIC to look good going into a collection window. The OIC who finds out from the watch officer that a sensor was degraded finds out in the worst way, and the SSgt absorbs it.

The good 2651 SSgt runs ISR sections that collect clean data on the first window and have the section chief qualified and the junior Marines trained before the deployment cycle begins. His OIC trusts him to represent the section's capability honestly in the intelligence planning cycle — not optimistically. The MEF intelligence section knows this SSgt's name because the system status reports are accurate and the capability briefings produce collection plans that actually work.

You are the senior enlisted ISR systems advisor — to the intelligence officer, to the collection management section, and to the program office. You are no longer just keeping the hardware running. You are telling the commander what the hardware can and cannot do, and your assessment goes into the collection plan that shapes the operation.

You run the ISR systems enlisted structure for a battalion, regiment, or MEF-level intelligence element — managing section chiefs and platoon sergeants through your GySgt authority, building the training and readiness calendar in concert with the OIC and the MEF intelligence staff, and advising the collection management officer on ISR sensor capability, coverage architecture, integration requirements, and the gaps that cannot be filled with organic systems. You write three to five SSgt FitReps per cycle. You interface directly with MCSC program office representatives on system upgrades, fielding timelines, and capability modernization for the AN/TPS-80 G/ATOR and associated ground sensor systems — the GySgt-level ISR advisor who has been through multiple system cycles is the Marine the program manager calls first when she needs a field-perspective assessment of a proposed configuration change. You also start carrying institutional-level responsibilities: shaping the T&R manual review cycle for 2651 tasks, informing the MEPB on the MOS roadmap, and mentoring the SSgts who will be the GySgts and 1stSgts of the next decade. This is the rank where the intelligence community outside the USMC — DIA, NSA, joint ISR staffs — starts knowing your name.

• 01Build and defend a battalion or regiment ISR systems training calendar that the MEF intelligence officer can brief without corrections — T&R-aligned, equipment-upgrade-cycle-aware, joint-collection-architecture-integrated.
• 02Write three to five SSgt FitReps per cycle that the reporting senior can defend at the battalion review — clean Section A, defensible relative value, accurate career-potential characterization for a small competitive occfield.
• 03Advise the collection management officer and the MEF S-2 on ground ISR sensor employment, capability gaps, and integration architecture for a joint task force collection plan — with the technical depth to brief a DIA or NSA representative who already knows the system.
• 04Represent the field perspective in an MCSC program office discussion on AN/TPS-80 G/ATOR capability modernization, technical bulletin implementation timelines, or new system configuration — providing honest operational feedback on what works and what does not before the change goes to fleet.
• 05Mentor three or four SSgts into Career Course graduates and GySgt-board-ready candidates; identify the one or two who should be steering toward senior technical advisor versus operational section chief billets.
• 06Brief the battalion commander honestly on ISR systems readiness, collection capability, and the gap between what the intelligence plan requires and what the organic systems can deliver — with enough clarity that the commander can make an informed decision about requesting augmentation.

• —NAVMC 3500.20 — Intelligence/EW T&R Manual (you now contribute to the review cycle, not just execute against it; at GySgt you are one of the field practitioners the MEPB consults when the 2651 T&R tasks are updated).
• —MCWP 2-26 — MAGTF Intelligence Operations (you own the intelligence operations framework at this tier; the collection plan that the GySgt's section executes should be one the GySgt helped shape).
• —FM 3-55 — Information Collection (joint ISR doctrine; GySgts who brief joint ISR staffs need to own the joint language as fluently as USMC doctrine).
• —JP 2-01 — Joint Intelligence Support to Military Operations (the joint intelligence architecture your collection systems feed into at MEF and above; at GySgt you sit in the joint intelligence synchronization meeting, not just receive its outputs).
• —MCO 1610.7 — Performance Evaluation System (FitRep mechanics you teach to your SSgts and execute at the senior-NCO level).
• —MCO 1400.32 — Marine Corps Promotion Manual (GySgt-to-MSgt/1stSgt board mechanics; pull the current MARADMIN for the slate and track your FitRep profile against the ISR community).

• —SNCO Academy Advanced Course (Career Course) graduate; SNCO Academy Senior Course slated before the MSgt board approaches.
• —Black Belt Instructor MCMAP minimum — at GySgt you are the senior technical and physical standard in the ISR element.
• —1st-Class PFT and CFT; the ISR element watches the GySgt's scores and the MEF intelligence officer's health-of-the-force brief notes whose element is carrying the unit.
• —FitRep profile that the senior reporting official can defend at the MSgt/1stSgt board — relative value, attribute rationale, and career-potential language all aligned for a competitive ISR occfield.
• —TS/SCI clearance maintained with no reportable incidents — at GySgt a clearance problem ends the MSgt slate conversation and generates an Inspector General inquiry before it ends.

• —Letting one SSgt drift technically because he is reliable administratively. The collection failure that traces back to the SSgt's section — the one the GySgt trusted without verifying — is the GySgt's problem at the MEF-level AAR.
• —Accepting a program office assurance that a configuration change is transparent to operations without independently assessing the implementation risk. The change that "should not affect collection" but does is the change the GySgt approved without pushing back.
• —Confusing being technically deep with being the SME who cannot explain the gap to a non-technical commander. The GySgt who cannot translate ISR capability limitations into operational language that a maneuver commander understands is not advising — he is briefing himself.
• —Carrying a disagreement with the OIC or the collection management officer out of the planning meeting and into the SSgts' section spaces. The ISR occfield is small; the GySgt who undermines the collection plan after failing to change it in the meeting loses credibility with both the officers and the senior NCOs.
• —Going around the OIC to the MEF S-2 with a system readiness issue the OIC does not know about. You will be right on the facts and wrong on the relationship; fix the readiness issue and inform the OIC before it reaches the MEF.

The good 2651 GySgt is the senior NCO the MEF intelligence officer brings to the joint ISR synchronization meeting because the technical assessment she gets will be accurate and the capability gap characterization will be actionable. His SSgts earn their GySgt billets. His sections produce clean collection. The program manager at MCSC already knows his name from the technical feedback that prevented a bad configuration from going to fleet, and the DIA liaison officer at the JTF has started routing ground sensor integration questions through him because the answers are reliable.

You are the institutional memory of Marine Corps ISR systems. The split between 1stSgt/SgtMaj (troop leadership) and MSgt/MGySgt (occupational SME — MEF ISR staff, MCSC program liaison, NSA/DIA senior billet, or schoolhouse master systems senior) is the defining career choice of your final decade, and neither track is a consolation prize.

As 1stSgt you run the formation — personnel, discipline, family readiness, training accountability, the section chiefs and platoon sergeants, and the boundary between what the intelligence officer needs and what the ISR element can actually deliver at the human level. As MSgt you are the senior occupational advisor — MEF-level ISR systems staff senior, MCSC program office liaison, NSA or DIA senior billet, or schoolhouse senior advisor shaping the next generation of 2651 section chiefs. In the MSgt or MGySgt track you are the practitioner the program manager brings to Quantico or Dahlgren when the AN/TPS-80 G/ATOR modernization program needs a senior operator's honest assessment before the capability goes to contract. You brief two-star intelligence officers. You write the comments on the 2651 T&R manual review cycle. You are the Marine the MOS monitor calls when the billet structure for ISR systems needs an honest read against the threat the MAGTF is about to face. As SgtMaj you advise the regimental or MEF commanding general on every enlisted decision in the intelligence occfield — and the Marines in your formation know whether the ISR program is healthy or broken by watching how you stand in front of it.

• 01Run a 1stSgt's call that produces actions and accurate intelligence on the formation's human and systems readiness — accountability, training gaps, retention signals, discipline patterns — in 30 minutes flat.
• 02Brief a two-star intelligence officer or a senior collection manager on the Marine Corps ground ISR systems readiness, the gap between organic capability and the threat environment, and the recommended course of action for a systems modernization decision.
• 03Write the senior-NCO-level input to the 2651 MOS roadmap, the NAVMC 3500.20 T&R review cycle, or the MCSC program office capability assessment — grounded in operational reality, not program office optimism.
• 04Mentor four GySgts and the senior SSgts as the next 1stSgt/MSgt cohort — with honest reads on who is troop-leadership track and who is senior technical advisor track, and the career consequences of the wrong choice at this rank.
• 05Represent the Marine Corps ISR community at a joint ISR capability review, a DIA senior systems conference, or an NSA technical exchange — as a practitioner, not a spokesperson.
• 06Brief the intelligence officer and the battalion commander honestly on the gap between the ISR collection plan and the organic systems' realistic capability — in language that produces a resource decision, not a staff study.

• —MCWP 2-26 — MAGTF Intelligence Operations (you teach this to your GySgts and you brief senior officers from it).
• —FM 3-55 — Information Collection; JP 2-01 — Joint Intelligence Support to Military Operations (the joint ISR framework you operate in at the senior billet level).
• —MCO 1610.7 — Performance Evaluation System (you are the rater or reviewing officer on the FitReps that pick the next GySgt and SSgt slates).
• —MCO 1400.32 — Marine Corps Promotion Manual (1stSgt / SgtMaj / MGySgt board mechanics; pull the current MARADMIN for the slate and know the ISR community's competitive landscape).
• —MCO 1900.16 — Marine Corps Separation and Retirement Manual (you are the resource the ISR element comes to for transition questions; and your own transition plan runs 24-36 months out).
• —DoD 5240.1-R — Intelligence Activities oversight (the legal framework you enforce and the legal framework the IG audits against when a collection complaint surfaces on your watch).

• —SNCO Academy Senior Course graduate; Sergeants Major Course (Marine Corps University) before competing for a command SgtMaj slate in the intelligence occfield.
• —ISR systems readiness, T&R completion rate, and security incidents in the top tier of the MEF intelligence element — the MEF deputy CG sees the intelligence readiness brief and knows whose ISR element is the problem.
• —Personal FitRep profile that the reporting senior can defend at HQMC — the bar at this rank is whether your rated GySgts get selected for MSgt and 1stSgt.
• —Zero clearance or information security incidents at the senior enlisted level — one incident at MSgt/SgtMaj in an intelligence occfield ends the career permanently and generates a congressional inquiry.
• —Post-service transition plan running 24-36 months out — federal civilian pipeline (DIA systems engineer GS-12/13, NSA technical billet, defense contractor) identified and progressing; VA claim filed pre-EAS; no retirement walked into cold.

• —Taking a briefing position to the program manager or to the two-star that is more optimistic than the field reality supports. The senior ISR NCO who tells the program office the system is ready when it is not produces a fielding decision the Marine Corps lives with for fifteen years — and the NCO who is honest about the gap is the one who actually shapes the modernization.
• —Confusing rank with credibility in the intelligence community. The DIA senior analyst who has been working ground ISR for twenty years knows more about the technical problem than a fresh MGySgt billet; your value is the operational employment knowledge and the formation-level perspective, not the seniority.
• —Stopping personal technical depth because you are "too senior for the systems." The senior NCO who loses touch with the actual hardware and software loses the ability to give accurate capability assessments and becomes a staff officer with chevrons instead of an ISR advisor.
• —Letting a GySgt run a bad collection posture or a bad security program because he is your guy. The IG and the DCIP both audit ISR elements; the senior NCO who knew and did not act owns the finding.
• —Confusing the warm-up to retirement with the job. The junior 2651s in the formation are watching how you carry the final tour; the ones who decide whether to re-enlist are doing the math on whether the ISR career field produced the kind of senior NCO they want to become.

The good 2651 MSgt or MGySgt is the Marine the MEF intelligence officer trusts to deliver the honest assessment of ISR systems capability before a named operation — not the optimistic assessment, not the "we will figure it out" assessment, but the one that is accurate enough to build a collection plan on. He is the practitioner the MCSC program manager flew out to Quantico to hear before committing to the next AN/TPS-80 G/ATOR software increment. His GySgts get MSgt. His sections collect clean. The junior 2651 who decides to re-enlist at the six-year mark does it partly because this senior NCO made the career look worth carrying.