←Back to 18F Special Forces Intelligence Sergeant — overview, pay, training, civilian translation, reviews
18FE6
Special Forces Intelligence Sergeant
E-6 (Staff Sergeant) · Army
HEADS UP
At SSG you are either the senior intelligence seat on a high-OPTEMPO ODA or the company S2 managing intelligence for multiple teams. Either way, the solo-practitioner model of the SGT seat is over — you are now accountable for the quality of intelligence that other people produce, not just your own. The most important thing you can do wrong at this rank is confuse those two responsibilities.
The Honest MOS Read
Staff Sergeant is the rank where the 18F career field diverges into two serious tracks: the senior ODA intelligence sergeant seat — the more experienced, often higher-OPTEMPO team, the CT-tasked ODA, the DA-focused team that needs the most analytically seasoned intelligence NCO — and the company-level intelligence sergeant, the S2 NCO managing intelligence for six or more ODAs at the company headquarters. Both tracks are legitimate and both produce MSG-ready senior NCOs; the path you walk depends on the group's billet structure, your Team Sergeant's read of your strengths, and which track the group's intelligence chief has open.
On the ODA at SSG, you are the de facto intelligence chief. There is no senior 18F to defer to on the team — the 18Z (Team Sergeant) is the senior enlisted voice, and the 18A (Team Commander) leads, but on intelligence matters your analysis and your collection products are the authoritative team input. The targeting packages you produce go up the chain clean; the area assessment you maintain is the one the company quotes when briefing the battalion; the collection plan you manage produces the PIR answers the team commander needs before going into isolation. The junior 18F billet does not exist on the ODA — you are the only one — so there is no one to mentor at the team level. The mentoring function shifts upward: you are advising the 18A and the 18Z on intelligence integration into the planning process, and you are becoming the template the company S2 points to when he wants to show the other team 18Fs what the product standard looks like.
At the company S2 level, the day-to-day changes significantly. You are no longer running a single team's intelligence production; you are coordinating the intelligence production of multiple teams, deconflicting collection requirements across the company's concurrent operations, managing the relationship with the group G2 on behalf of the company, and building the company-level intelligence products that the company commander briefs at the battalion BUB. The mentoring function is central at this level: the team-level 18F NCOs are your subordinate intelligence NCOs in function if not in formal organizational chain, and the quality of their products reflects directly on the quality of your leadership.
The promotion clock at SSG runs through the ALC requirement (required for E-7 board eligibility) and the NCOER profile. The SF senior rater at the group level reads 18F NCOERs with specific attention to operational intelligence production, collection management quality, language performance, and the mentoring or leadership of the team's intelligence function. The 18F who writes his own promotion bullets in his NCOER counseling sessions — who tells his rater specifically what he produced, for whom, with what operational outcome — is the one whose NCOER competes at board.
Career Arc
- 01ALC (Advanced Leader Course) complete — the hard prerequisite for E-7 board eligibility; schedule it before the SSG promotion pin-on if possible.
- 02Senior ODA intelligence sergeant billet or company S2 assignment — which track depends on the group's billet structure and the company's operational needs.
- 03Advanced school completion: CDQC, MFF, Mountain Warfare, or Sniper / SOTIC — at least one team-mission-relevant advanced school in the ERB beyond the pipeline qualifications.
- 04Language DLPT sustainment at or above 2/2 — the group senior rater reads the language score on the ERB; the company S2 who cannot communicate in the target language is a liability in partner-nation intelligence coordination.
- 05SLC (Senior Leader Course) packet building — required for E-8 board competitiveness; the SLC slot competition inside the SF community is real.
- 06NCOER cycle: first fully ratable NCOER with the company commander or battalion S2 (officer) as senior rater — the bullets that pick the E-7 date live in this block.
- 07Company-level intelligence program ownership or ODA targeting package quality — the measurable output the group senior rater quotes in the promotion board narrative.
Common Screwups
- ×Confusing the company S2 role with the team 18F role. The company S2 who micro-manages individual team 18F products while neglecting the company-level intelligence coordination function is doing the wrong job at the wrong echelon.
- ×Letting the TS/SCI periodic reinvestigation run past the window because of operational tempo. A clearance suspension at E-6 in an SF group is a career-critical event; the intelligence billet cannot be filled by a sergeant without a current clearance.
- ×Producing NCOERs for junior 18F NCOs that do not accurately reflect their intelligence production quality. The NCOER that is generically positive does not help the junior 18F compete at the SSG board; the NCOER that specifically describes his targeting package quality, his collection management discipline, and the operational outcome of his intelligence work is the one that moves the dial.
- ×Treating the partner-nation intelligence relationship as a reporting exchange rather than a relationship investment. The partner-intelligence-service liaison that exists because the SSG 18F maintained it through three rotation cycles is the most valuable collection asset the company has; the one that was transactional during the last rotation is gone when the next team arrives.
- ×Going to the group G2 or the JSOTF J2 with a collection requirement without first routing it through the company commander and the company S2 chain. The intelligence request that appears at the group level without the company's awareness creates the same friction as any bypass of the chain.
A Day in the Life
- 0500Wake. Kit check on anything that shipped home from the previous deployment — the senior 18F who has let the kit drift since redeployment is the one who cannot respond to the recall notification.
- 0530PT formation. Company S2 billets may be at the company headquarters rather than on the ODA — PT formation at company level under the company first sergeant or operations sergeant.
- 0700-0900Hygiene, change, breakfast. Intelligence traffic read — incoming products from the group G2, theater intel centers, and national feeds. Flag anything that changes the company running estimate. Update the PIR tracking board.
- 0900Company formation or staff meeting. Company S2: brief the company commander on overnight intelligence traffic and any changes to the PIR status. ODA senior 18F: team formation with the Team Sergeant; intelligence update to the team warrant.
- 0915-1200Morning work: company S2 — collection coordination with team 18Fs, group G2 liaison, company CONOP intelligence annex review. Senior ODA 18F — targeting package development, area assessment update, team-level intelligence training for the upcoming deployment cycle.
- 1200-1300Chow. Language study — 20 minutes of target-language media during the lunch break maintains the DLPT standard without requiring a separate study session.
- 1300-1600Afternoon work: NCOER input collection from the team-level 18F NCOs, partner-nation intelligence liaison preparation, SLC packet administrative work, or advanced school preparation if a CDQC or MFF slot is upcoming.
- 1600Final formation. Intelligence running estimate update. PIR tracking log end-of-day status. Sensitive item accountability.
- 1700-2000Personal time or family. The SSG 18F who goes home at 1700 and returns at 0700 without a check on overnight intelligence traffic is the one who walks into the 0900 brief unprepared. A 10-minute evening check on the incoming queue is the difference.
- Pre-deployment isolationThe schedule compresses to an isolation rhythm: intelligence annex production, targeting package finalization, collection plan briefed to the team commander and team sergeant, partner-nation intelligence read-in. The company S2 manages the intelligence flow for multiple teams simultaneously during this period — each team's isolation timeline is running in parallel.
Weekly Cadence
The company S2's week is shaped by the company training schedule, the group's intelligence production cycle, and the battalion BUB schedule. Monday is the intelligence update cycle — company running estimate reviewed, team PIR status boards checked, group G2 products distributed to teams. Tuesday is intelligence coordination — collection deconfliction between teams, partner-nation liaison calls, group G2 relationship maintenance. Wednesday and Thursday are production days — CONOP intelligence annexes in review, targeting packages receiving feedback, the company's contribution to the group's monthly area assessment update. Friday is administrative — NCOER input collected, school packets updated, DLPT sustainment confirmed across the company 18F community.
The week changes dramatically during the train-up cycle. The intelligence production tempo increases as the deployment window approaches — more area assessment updates, more targeting package development, more collection deconfliction. The company S2 who starts the train-up cycle with the company running estimate current and the team-level PIR boards updated is the one whose train-up is productive; the one who starts with outdated products is spending train-up time on baseline production that should have happened in the steady-state garrison window.
The language sustainment window — 20 minutes daily, or a weekly conversation session — must survive the schedule compression of the train-up cycle. The DLPT retest for an SSG 18F who is in a train-up cycle when the retest window opens is negotiable with the group language officer; the retest for the SSG 18F who let the language lapse during a garrison window is not.
Key Skills — How to Drill Each
- 01Build and maintain a targeting package — target development, pattern-of-life, key leadership engagement matrix, collection gaps — to SF targeting standards.A targeting package at the ODA level is the product the team commander briefs to the company to justify a DA or SR operation. The format includes: target description (biographic or organizational), pattern-of-life (daily schedule, routine, associates, locations), collection gaps (what we do not know and why), engagement criteria (what conditions trigger the operation), and the ISR support request for closing the gaps. The targeting package that gets approved is the one that is honest about what is confirmed, what is inferred, and what is still a gap — not the one that fills every column with something.
- 02Manage collection at the company level across multiple concurrent ODA operations.The company S2's collection management function requires maintaining visibility on every team's open PIRs, every collection asset tasked at the company level, and the deconfliction between teams that are operating in overlapping geographical areas or against related targets. Build a PIR tracking board that the company commander can read in 90 seconds: open PIRs by team, assigned collection asset, expected answer window, and date since last update. The PIR that has been open for 30 days without an update is the intelligence gap that will embarrass the company at the battalion BUB.
- 03Mentor team-level 18F NCOs in intelligence product quality and collection management discipline.The most effective mentoring method is product review with specific feedback. When a team 18F submits a CONOP intelligence annex, review it against the IPB standard: Is the BLUF present and specific? Is the threat COA development accurate and sourced? Are the collection gaps identified? Give the feedback in writing, in the margin of the product, and follow up at the next one-on-one to confirm the adjustment was made. The junior 18F who receives consistent, specific, written feedback on his products improves measurably over a six-month cycle.
- 04Translate intelligence risk into language the company commander and battalion S3 will brief without rewording.The company commander is not an intelligence officer. He reads the intelligence product you give him and uses it to make decisions. The intelligence product that arrives in intelligence-community language — structured with intelligence cycle jargon, heavy on collection methodology, light on operational implications — is the product he will ask you to translate before the BUB. The product that arrives with the operational implication in the first paragraph — 'we assess [threat element] will conduct [action] in [window] based on [indicators]' — is the product he briefs directly.
- 05Run the intelligence annex for a company-level deliberate operation.The company-level operation intelligence annex covers: situation (current threat assessment), enemy (specific threat to this operation), terrain and weather (operational environment), troops and support available (friendly intelligence assets), civilian considerations (relevant population dynamics), commander's PIR (what the commander needs answered before COA approval), collection plan (how PIRs get answered), and the production schedule (when key products are due). The annex that is integrated into the OPORD from the beginning — not appended as an afterthought — is the one that makes the operation work.
- 06Sustain TS/SCI accesses and the counterintelligence awareness standard across the company.The pre-deployment CI brief is not a checkbox. Build it around three categories: what the threat knows about the unit (publicly available information, previous reporting), how the threat attempts collection (human approaches, cyber, signals), and what each soldier can do to complicate that collection (social media hygiene, foreign contact reporting, travel awareness). The brief that uses specific, recent examples from the company's operational environment is the one that changes behavior; the generic brief that could have been given to any unit does not.
Manuals & References — What Chapters Matter
- ADP 2-0 — Intelligence.The intelligence warfighting function framework is what the company commander is thinking in when he asks for the intelligence picture. The SSG 18F who speaks that framework fluently — collection management, production, dissemination, analysis methodology — is the one the commander brings into planning conversations at the COA development stage.
- ATP 2-01.3 — Intelligence Preparation of the Battlefield.The company-level IPB product is the aggregated picture of all the team-level IPBs the 18F NCOs under your coordination have built. The company S2 who can identify where the individual team IPBs are inconsistent with each other — where team A's threat assessment contradicts team B's — and resolve the discrepancy before the battalion brief is the one the battalion S2 trusts.
- FM 2-22.3 — Human Intelligence Collector Operations.At the company S2 level, the HUMINT coordination function includes deconflicting the collection activities of multiple team 18Fs and any attached HUMINT collectors. FM 2-22.3 Chapter 4 (source operations) is the standard both for assessing whether the team 18Fs are running their collection activities within their authority and for identifying when a source development activity has escalated to a level that requires higher coordination.
- Joint Publication 2-0 — Joint Intelligence.The company S2 connects the team-level collection requests to the JSOTF J2 or the supporting theater intelligence architecture. JP 2-0 describes how the joint intelligence community structures its collection management and production functions — understanding that architecture is what makes the company S2's collection requests responsive rather than lost in the joint collection manager's queue.
- FM 3-18 — Special Forces Operations.The mission-set framework that determines what intelligence the company's teams need at the task level. The company S2 who understands how the intelligence requirements for a FID mission differ from a UW mission differ from a CT mission produces a collection plan that serves the actual mission, not a generic intelligence requirement.
- AR 600-8-19 — Enlisted Promotions; AR 623-3 — Evaluation Reporting System.The NCOER the SSG 18F writes for the junior NCOs under his functional supervision is the most consequential product he produces at this rank. AR 623-3 describes the NCOER format, the rated NCO's rights, and the rater's responsibilities. The 18F who writes NCOERs that specifically describe operational intelligence outcomes — not generic leadership qualities — is the one whose rated NCOs compete at board.
Standards — How to Hit Each
- ALC complete; SLC packet built.ALC is the prerequisite for the E-7 board; SLC is the prerequisite for the E-8 board. Schedule ALC through the company operations sergeant or the group's school-slot management process before the SSG pin-on date if possible. Build the SLC packet — application, endorsements, senior-rater input — before the group's annual SLC slot allocation window. The SF community's SLC allocation is competitive; late packets do not get slots.
- Zero TS/SCI handling incidents during tenure.The TS/SCI handling standard is binary: no incidents or a career-critical event. Build team and company-level handling discipline by example — brief the handling procedures at every pre-deployment CI session, audit the intelligence handling practices of the team 18Fs you mentor, and report any observed handling discrepancy immediately to the security manager. The SSG who lets a handling discrepancy go unreported to protect a junior soldier is compounding the original incident with a second one.
- Language DLPT at the team or company required standard — at or above 2/2.The 2/2 DLPT rating means you can read and understand native-speaker media and conduct substantive conversation on professional topics. Build a daily language maintenance routine: 20 minutes of target-language reading (news, professional materials) and a weekly native-speaker conversation session. The DLPT retest cycle at most groups runs annually; do not let the language degrade between cycles.
- Intelligence products rated as the company standard by the group G2.The group G2 sees the products from every company in the group; the ones he pulls to use as the format template for other companies are the ones that will be attributed to the SSG 18F who produced them. Build that reputation by submitting products early, not at the last minute — the product that arrives before the deadline gives the group G2 time to read it carefully, and the product that arrives at the deadline gets a fast read.
Technical Mistakes — Concrete Consequences
- Micro-managing team-level 18F products from the company S2 position.The company S2 who reviews and rewrites every team 18F's intelligence product before it goes to the company commander creates two problems: the team 18Fs stop developing because their products are always overwritten, and the company commander stops trusting the quality of the team-level products because he can see the rewriting happening. Give specific feedback; let the team 18F revise; hold the standard without doing the work for them.
- Treating the partner-nation intelligence service as an information sink rather than an information source.The partner intelligence service that is always asked to share and never offered anything in return will stop sharing. The collection relationship that produced 40% of the team's reporting during the last rotation disappears when the next team arrives. The SSG 18F who brings something to the exchange — analysis products, training, collection support — is the one whose partner-service relationship survives the rotation change.
- Building a collection plan that serves the group S2's reporting requirement but not the team's operational need.A collection plan that is optimized for producing reports for the higher intelligence architecture rather than answering the team commander's PIR generates reporting volume without intelligence value. The team commander who cannot use the intelligence picture to make a planning decision because the collection plan answered the wrong questions loses confidence in the intelligence function — and eventually stops including the 18F in the planning process at the stage where the intelligence would actually make a difference.
- Allowing OPSEC discipline to relax post-deployment because 'the threat is not here.'Intelligence collection against SF units is not geographically limited to the operational theater. Social media, personal communication, and public financial records are accessible from anywhere. The SSG 18F who allows team members' social media posts about deployment locations, operational activities, or partner-force relationships during the garrison period is contributing to a counterintelligence picture that feeds into the next deployment environment.
Career Decisions at This Rank
- Company S2 vs. senior ODA billet — which track to pursue.Both tracks produce competitive MSG candidates, but through different institutional experiences. The company S2 builds management, coordination, and leadership skills that the ODA senior billet does not directly develop — managing multiple teams' intelligence programs, coordinating with higher echelons, writing NCOERs, representing the company at the battalion intelligence staff level. The senior ODA billet deepens the operational intelligence production skills — targeting, collection management, partner-force engagement — that the company S2 role sometimes abstracts away from. The honest assessment: the 18F who wants to be a group-level intelligence chief at MSG/SGM needs both experiences in sequence; the company S2 billet is the bridge from the ODA practitioner to the institutional intelligence leader.
- Advanced school investment — which school to prioritize at SSG.At SSG, the school-slot competition is more transparent than at SGT because the Team Sergeant or company operations sergeant has a clearer read of the operational need. CDQC and MFF are the most commonly discussed because they are the most competitively allocated. For the 18F specifically, the question is which school adds intelligence collection capability — CDQC enables maritime collection platforms; MFF enables clandestine infiltration that supports SR missions; Mountain Warfare enables alpine-environment operations. The school that aligns with the team's next deployment profile is the correct choice, not the school that looks best on the ERB in isolation.
- IC agency employment (active investigation) vs. remaining to senior NCO.The SSG 18F with an active TS/SCI, an SF tab, operational experience, and a working target-language DLPT score is in the most competitive position in the defense intelligence employment market. The decision point is whether the remaining Army career value — MSG billet, language and regional expertise deepening, USASOC intelligence senior NCO track — exceeds the compensation and lifestyle value of the IC or defense contractor transition. The honest military case: the MSG 18F who has a group-level intelligence chief billet and a relationship with allied intelligence services has operational access and authority that the contractor role does not replicate. The honest civilian case: the compensation gap between E-6 base pay and a cleared GS-13 or contractor equivalent is real and compounds over time.
- SLC packet timing — when to compete.SLC (Senior Leader Course) is required for the E-8 board. The SF community's SLC slot allocation is competitive — there are more SSG 18Fs who need SLC than there are slots in any given allocation window. The 18F who competes for SLC early, with the company commander's full endorsement and a current NCOER that documents operational intelligence production quality, is the one who gets the early slot. The 18F who builds the SLC packet in the year before the E-7 board rather than the year after the E-7 promotion is playing the promotion game correctly.
How the Seat Varies by Unit Type
- Company S2 at active-component SF groupThe company S2 at an active SF group manages a company of six ODAs through continuous rotation cycles — deploy, reset, train-up, deploy. The intelligence coordination volume is high; the JSOTF intelligence architecture is deep; the partner-nation relationships are well-established. The most demanding aspect of the company S2 role in the active component is the concurrent operations pace — multiple teams in various stages of their deployment cycle simultaneously, each with its own open PIR list and collection plan.
- Senior ODA 18F at a DA-focused teamThe DA-focused ODA in the current environment operates in a high-tempo targeting cycle. The 18F's production demands are the highest in the SF community at this billet — targeting packages on shorter timelines, more frequent isolation periods, direct integration with joint ISR assets and the JSOTF targeting cell. The analytical discipline required is the same; the timeline compression is what distinguishes this environment from the FID-focused or UW-focused ODA.
- SF group G2 section (battalion or group staff)The SSG 18F assigned to the group G2 section is operating at the institutional level, not the team level. The production work is different — strategic and operational intelligence products, not team-level tactical products — and the collection management responsibility is broader. This billet is less common for E-6 18Fs and is more typically an E-7 or MSG position, but it exists as a developmental assignment for high-performing SSG 18Fs who the group G2 wants to develop for the eventual E-7 group-level intelligence chief role.
What Good Looks Like at This Rank
The good senior 18F is the intelligence NCO the company commander names when the group G2 asks which company's intelligence products should be the format template for the group. His targeting packages arrive at the company level before the isolation window and require no revision before going to the battalion; his collection plans produce PIR answers with enough lead time to actually change the mission planning; his NCOER bullets for the team-level 18F NCOs he mentors are specific enough that the SF senior rater can quote them in the promotion board narrative.
The team-level 18F NCOs in his company produce better intelligence products after 90 days of his feedback than they did before. That is the metric. Not the quality of his own products — his products were already strong enough to get him to SSG — but the quality of the products that come out of a company that has been operating under his intelligence leadership for a full deployment cycle.
The group G2 is already talking to the company commander about his SLC timeline, and the company commander has already told the battalion that this 18F's intelligence program is the one the battalion wants for the next high-priority mission. The SFC conversation is happening before the E-7 board window officially opens.
Preview — The Next Rank
The SFC window is the company-level intelligence chief role or the battalion assistant S2 — the point where the 18F intelligence NCO transitions from managing a company's intelligence program to advising the battalion or company commander on operational-level intelligence. The scale expands: instead of managing six ODA intelligence programs, you are managing the intelligence picture for a battalion of multiple companies, coordinating with a theater intelligence architecture that connects to the national intelligence community, and writing NCOERs that determine the career trajectories of the company S2 NCOs below you.
The most significant transition is the shift from intelligence producer to intelligence advisor. At SSG, you still produce — targeting packages, area assessments, collection plans — and you manage others who produce. At SFC, you are increasingly in the advisor role, translating the intelligence picture into operational implications for commanders who need to make decisions, not for analysts who want to understand the collection. That translation skill — taking a complex, uncertainty-laden intelligence picture and expressing it in the language the commander uses to brief his boss — is what makes the SFC 18F the person the battalion commander calls when he needs to understand what the intelligence picture means for the mission.
The language and regional expertise that have been building since Phase 6 are the foundation of the SFC 18F's authority in the room. The battalion commander who knows that his intelligence SFC can walk into a partner-nation intelligence briefing, follow the conversation, and report back accurately has a different relationship with his intelligence NCO than the one who is working through an interpreter.
FAQ
18F E6 — Frequently Asked Questions
Q01What does a E6 18F (Special Forces Intelligence Sergeant) actually do?
At SSG the 18F either stays on a senior ODA billet — the higher-OPTEMPO teams, the direct-action-focused ODAs, the CT-tasked teams — or moves into the company-level S2 role managing intelligence for a company of six or more ODAs.
Q02What's the most important thing to know as a E6 18F?
At SSG you are either the senior intelligence seat on a high-OPTEMPO ODA or the company S2 managing intelligence for multiple teams.
Q03What does a typical day look like for a E6 18F?
Time-blocked day at the E6 18F rank tier: 0500 Wake. Kit check on anything that shipped home from the previous deployment — the senior 18F who has let the kit drift since redeployment is the one who cannot respond to the recall notification, 0530 PT formation. Company S2 billets may be at the company headquarters rather than on the ODA — PT formation at company level under the company first sergeant or operations sergeant, 0700-0900 Hygiene, change, breakfast. Intelligence traffic read — incoming products from the group G2, theater intel centers, and national feeds.…
Q04What mistakes get E6 18F soldiers fired or relieved?
Confusing the company S2 role with the team 18F role. The company S2 who micro-manages individual team 18F products while neglecting the company-level intelligence coordination function is doing the wrong job at the wrong echelon; Letting the TS/SCI periodic reinvestigation run past the window because of operational tempo. A clearance suspension at E-6 in an SF group is a career-critical event; the intelligence billet cannot be filled by a sergeant without a current clearance;…
Q05What career decisions matter most at the E6 18F rank tier?
Company S2 vs. senior ODA billet — which track to pursue — Both tracks produce competitive MSG candidates, but through different institutional experiences. The company S2 builds management, coordination, and leadership skills that the ODA senior billet does not directly develop — managing multiple teams' intelligence programs, coordinating with higher echelons, writing NCOERs, representing the company at the battalion intelligence staff level. The senior ODA billet deepens the operational intelligence production skills — targeting, collection management,…
Q06What's next after E6 for a 18F (Special Forces Intelligence Sergeant) in the Army?
The SFC window is the company-level intelligence chief role or the battalion assistant S2 — the point where the 18F intelligence NCO transitions from managing a company's intelligence program to advising the battalion or company commander on operational-level intelligence.
Q07What manuals and regulations does a E6 18F need to know cold?
ADP 2-0 — Intelligence.; ATP 2-01.3 — Intelligence Preparation of the Battlefield.; FM 2-22.3 — Human Intelligence Collector Operations.
This playbook has no tips yet. Be the first to share what you know.
Published by the Honest MOS Editorial DeskVerified against DoD/.gov sourcesUpdated May 2026Editorial standards