←Back to 35M Human Intelligence Collector — overview, pay, training, civilian translation, reviews
35ME5
Human Intelligence Collector
E-5 (Sergeant) · Army
HEADS UP
You are an NCO now and the quality-control gate on everything your team reports. The IIRs that leave carry your name as much as the collector's, and so does the legal line — you signed for the team, so a compliance failure under you is yours to answer for, in writing, possibly under investigation. Counsel in writing, QC every report, and never approve an approach you have not personally walked against ATP 2-22.3. The day you stop collecting yourself is the day you stop being able to coach it.
The Honest MOS Read
You pinned SGT and now you lead a HUMINT collection team — a few collectors and their interpreters running screenings, debriefs, and source contacts. The job changed shape the moment the stripe went on. At E-4 the question was 'is my report clean and is my session inside the lines.' At E-5 the question is 'is my team's report clean and is every session my collectors run inside the lines' — and the answer is your signature, your NCOER, and, if it goes wrong, your investigation. You are the quality-control gate. The reporting that leaves your team carries your name as much as the collector's, and the oversight discipline of the team is something you enforce in writing, not in hallway conversation.
The craft you still own personally — and you must, because the day you stop running sessions is the day you stop being able to coach them. You quality-control every IIR before it leaves the team: BLUF earns its space, source evaluation graded honestly, no spillage of method, written to ICD 203 / 206. You triage the team's requirements against placement and access and decide where the team's limited collection time goes. You sit between your collectors and the operational management element and you are the senior collector on the team when the section NCOIC is gone. But the higher-leverage work now is the work on people: you counsel your soldiers on the 14th and after every reporting cycle, and you write the DA 4856 that captures both a technical slip and a development plan — Plan of Action specific and measurable, never 'collector will improve reporting,' because a vague counseling protects nobody and develops no one.
The legal line is now something you enforce on other people, and that is harder than holding it for yourself. When a junior collector brings you a session plan, you walk it against ATP 2-22.3 before you approve it — and sometimes you have the 'I am not approving this approach' conversation, and you mean it, even when the collector is talented and the requirement is hot. ATP 2-22.3 is the only approved standard, the law of war and the Geneva Conventions are the hard ceiling, and you are the gate that does not let operational pressure move either one. The collectors learn the standard by watching you enforce it consistently — if you let a talented collector cut a corner once because the source was valuable, you have taught the whole team that the line is negotiable, and in this MOS a negotiable line is how a coercion allegation, a burned source, or a CI compromise gets born. You signed for the team. A compliance failure under you is yours to answer for, in writing, possibly under a 15-6.
The NCO-business load is real. ALC is the next professional-development gate — you should have the slot built and ready when the schedule drops. Your team's reporting quality is measurable and you should be tracking it: IIR rework rate, source-evaluation accuracy, and the cleanest metric of all, zero oversight or legal-compliance findings during your tenure. You manage the team's language readiness — a team that loses its DLPT capability loses its mission, and that loss lands on you. You keep the source-administrative and intelligence-oversight files audit-clean, because the S2X, CI, and the IG all inspect them, and in HUMINT a file gap is not an admin ding, it is a finding that can become a security incident. And you coordinate with the supporting CI element on the hard boundary between HUMINT collection and CI investigation — step a collector into a CI investigation and you have compromised both.
The career conversation that defines this rank is the 351M HUMINT Collection Technician path. If the warrant has had you on the short list since E-4, the packet conversation is real now. The SGT whose team's IIRs get cited up the chain, whose collectors pass their reviews the first time, and whose oversight files survive any audit without a comment is the SGT the warrant pushes for technician school. You also start building the next NCOs — your collectors should be on the SGT-board slate when their time comes, raised by you to write their own reporting clean and to hold their own line. The choice between the technician track (deep collection expertise, the 351M warrant) and the NCO track (broaden into SSG section NCOIC, then SFC senior HUMINT NCO) is the strategic decision in front of you. Both are real careers; the warrant will tell you honestly which one your strengths fit, and so will the senior NCO who runs the section.
Career Arc
- 01E-5 pin-on; take the collection team — a few collectors and their interpreters.
- 02Become the QC gate — every IIR runs through you to ICD 203 / 206 and ATP 2-22.3 compliance before it leaves the team.
- 03Counseling rhythm established — monthly on the 14th and after every reporting cycle, documented on the DA 4856.
- 04ALC slot built and ready when the schedule drops — the next professional-development gate.
- 05Team reporting quality tracked — rework rate down, source-evaluation accuracy up, zero oversight findings in your tenure.
- 06351M technician packet conversation gets serious for the SGT the warrant has on the short list.
- 07Your collectors hit the SGT-board slate; the section NCOIC starts reading you for the SSG-track or the technician-track fork.
Common Screwups
- ×Approving an approach or a session plan you have not personally walked against ATP 2-22.3. You signed for the team — a compliance failure under you is your signature to answer for, in writing, possibly under a 15-6, and the IG and CI find it before you do.
- ×Counseling verbally. If a collector's sourcing or oversight slip is not on a DA 4856, the senior rater cannot defend you and the section NCOIC cannot help you. Document the slip and the development plan or it did not happen.
- ×Letting source-administrative paperwork drift because operations are busy. The audit does not care how busy you were — a file gap is a finding, and in HUMINT a finding can be a security incident with your name as the team NCO on it.
- ×DUI / Article 15 / integrity hit as an NCO with a TS/SCI — the clearance suspension runs in parallel with the UCMJ action, and as an NCO the failure also reads on every collector you were supposed to be setting the standard for.
- ×Treating the CI deconfliction line as a formality. Step a collector into a CI investigation and you have compromised both the collection and the investigation — know the boundary cold and keep your team on your side of it.
A Day in the Life
- 0500Wake. Coffee, no phone in the SCIF. PT uniform on. Run the team's day in your head — which collector runs which source, which session plans you have to walk, which IIRs from yesterday still need to clear the gate.
- 0530-0700Lead team PT from the front. Your ACFT is a leadership statement at this rank, so you set the pace. Then hygiene, OCPs, breakfast — and a quick read of any overnight item that touches the team's sources.
- 0700-0730In-process the SCIF, SF 702 past the team's containers, systems up. Pull the requirements picture and triage the day's collection against placement and access — where does the team's limited time go today, and against which requirement.
- 0730-0900Team huddle and session-plan review. Each collector briefs his plan; you walk it against ATP 2-22.3 before you approve it. The 'I am not approving this' conversation happens here when it has to — with the doctrine explained, not just the verdict. You confirm the cherry's first-independent-session plan in detail.
- 0900-1130Run your own session or supervise the team's. You still collect — a source of your own, or sitting in on a collector's session to coach the read and the interpreter control. The day you stop running sessions is the day your redline loses credibility.
- 1130-1300Chow with the team. Conversation is the team's business — the ALC schedule, a collector's board prep, the source picture, the 351M packet the warrant mentioned. You listen for the friction that does not show up in the reporting.
- 1300-1500Reporting QC gate. Every team IIR runs through you — analytic pass against ICD 203 / 206, legal-compliance pass against ATP 2-22.3 with the in-bounds documentation checked. Redline to teach. Source-administrative file spot-check across the team; two-person integrity verified.
- 1500-1600Counseling and development. DA 4856 on the 14th and after the reporting cycle — measurable Plan of Action, not filler. Walk a collector's NCOER input, coordinate a deconfliction with the supporting CI element, or build your own ALC packet.
- 1600-1700Final huddle. You brief the team's reporting picture to the section NCOIC or the S2X; you set the next day's collection priorities for the team. SF 702 walk-around and SF 701 closeout; every container, source file, and classified item accounted for before the team leaves.
- 1700Released — most garrison days. You may stay to clear a hot report through the gate, finish a counseling, or close an oversight file. The team NCO leaves last on the days that matter. Watch shifts and field cycles rewrite this hour entirely.
- 1700-2000Personal time and NCO business. Gym, family, study (DLC, ALC prep, DLPT sustainment). The 351M packet reading if the warrant has you building it. Married SGTs are home; the team's problems travel with you either way.
- 2000-2200NCOER and packet work, or sleep. The reporting-cycle counselings, the board prep for a collector hitting his window, the technician-packet milestones. Tomorrow starts at 0500 and the team's clean record is yours to keep clean another day.
- CTC rotation (NTC, JRTC, JMRC) / real-world contingencyYour team runs a 24/7 watch in the field SCIF / S2X cell. The OC/T or the theater consumer grades every product that leaves your gate; the legal and oversight discipline gets harder to hold when everyone is tired and the requirement is hot — which is exactly when the team NCO earns the trust. A 14-day rotation is the test of whether the battle rhythm you built runs without you in the room every minute.
Weekly Cadence
The Mon-Fri rhythm at SGT level is the team's rhythm, and you own building it. Monday is the heaviest planning day — you triage the week's requirements against the sources the team can reach, set each collector's session priorities, and clear the weekend reporting that piled up. You read the brigade's collection priorities and decide where the team's limited time goes, because placement and access — not curiosity, not the loudest requirement — drive the plan. The discipline you are modeling is the one you want your collectors to internalize: the team chases the sources who can actually answer the requirement.
Tuesday and Wednesday are the heavy collection days, and your job is the gate. You walk each session plan against ATP 2-22.3 before approval, you observe the sessions you can, and you run the reporting QC gate every product clears — analytic pass and legal-compliance pass. This is also the counseling and mentorship block: the DA 4856s on the 14th and after the cycle, the 'walk me through your plan' conversation with the cherry, the redline that teaches a collector why the source evaluation was off rather than just that it was. The SGT whose Tuesday-Wednesday is a real gate is the SGT whose team's reporting gets cited up; the one who waves products through to keep up with volume is the one explaining a finding to the IG later. Thursday is the staff-process and compliance day — you brief the team's picture to the S2X, run the self-audit on the oversight files, coordinate deconfliction with CI, and prep for whatever inspection is on the horizon. Friday is the company-level event day and release.
The week's second rhythm is NCO business and the security-and-compliance machinery, and neither stops. Your collectors' promotion-point worksheets, NCOER inputs, board prep, and school slots are a standing load; your own ALC packet and DLC progression sit alongside them. The compliance machinery runs continuously: TARP / SAEDA, OPSEC, and intelligence-oversight trainings on the brigade's schedule that you enforce on the team, Continuous Vetting in the background, and self-reporting under AR 381-12 / SEAD 3 that you make a team norm rather than an annual scramble. The S2X audits, the source-file self-audits, and the SCIF-compliance prep are events you pull the team together for. Field rotations collapse the whole rhythm into a 24/7 watch where the gate gets harder to hold — and where the team NCO who built a battle rhythm that runs without him in the room every minute is the one who comes out the other side with the reporting, the soldiers, and the legal line all intact.
Key Skills — How to Drill Each
- 01Run a collection team's daily cycle — requirements triage, session planning, reporting quality control, oversight documentation — without a single IIR going out of bounds.Build a battle rhythm the team can run without you in the room: a morning requirements triage against placement and access, a session-plan review where you walk each plan against ATP 2-22.3 before approval, a reporting QC gate every product clears, and an end-of-day oversight-documentation closeout. Inspect what you expect — spot-check files, sit in on sessions, read every IIR before it leaves. The team NCO who builds the rhythm is the one whose team runs clean on the day he is at ALC or in the field somewhere else.
- 02Quality-control reporting to ICD 203 / 206 standards and to ATP 2-22.3 legal compliance before it leaves the team — you are the last gate.QC has two passes and you owe the team both. The analytic pass: BLUF earns its space, source evaluation graded honestly per ICD 206, uncertainty expressed per ICD 203, no method spillage. The legal-compliance pass: the session that produced this report maps to an approved ATP 2-22.3 approach and the in-bounds documentation exists. A report that fails either pass does not leave the team. The collector learns the standard from your redline; the consumer learns to trust your team from the product that clears the gate.
- 03Write the DA 4856 that documents both a technical slip and a development plan — Plan of Action specific and measurable, not 'collector will improve reporting.'Name the slip concretely (the source evaluation overstated reliability on the 12th; the tear-line exposed method) and write a Plan of Action with a measurable target and a date (rework rate below X by next cycle; re-write the last three IIRs against ICD 206 by Friday). Counsel monthly on the 14th and after every reporting cycle. The documented counseling protects the soldier, protects you, and gives the senior rater the record to defend the NCOER. The vague counseling protects nobody and is the one the IG reads as 'the NCO knew and did nothing.'
- 04Mentor a junior collector through their first independent source contact — including the 'I am not approving this approach' conversation, and meaning it.Walk the cherry's session plan with him before you sign it: objective, approved approach, sourcing plan, termination criteria. When the plan flirts with the line, say no and explain the doctrine, not just the verdict — the collector who understands WHY the approach is out of bounds is the one who will not bring it back. Observe the first independent session if you can. The hard part of this rank is holding the line for someone else's session under their pressure to perform; the SGT who can do it consistently is the one the warrant trusts with a team.
- 05Manage source-administrative files and intelligence-oversight documentation so they survive an S2X, CI, or IG audit cold.Own the team's file health as a tracked metric, not an afterthought. Schedule a self-audit before the inspectors do — every source file contemporaneous, two-person integrity where required, no floating pages, no backfilled lines, the SF 700/701/702/153 discipline clean. AR 380-5 and AR 381-10 are what they grade against. The team NCO who self-audits monthly never has a finding; the one who treats the file as paperwork is the one explaining a gap to a CI inspector while a collector's career hangs on the answer.
- 06Coordinate with the supporting CI element and the S2X on indicators, deconfliction, and the line between HUMINT collection and CI investigation.Know the boundary cold (AR 381-20): collection identifies and reports indicators; investigation belongs to CI. When a collector surfaces a CI indicator — a source feeding the team, an elicitation attempt — you hand it to the supporting CI element through the right channel and you do not let your team work it as collection. Deconflict source access with CI and the S2X before it becomes a collision. The SGT who treats the boundary as a formality is the one who compromises both efforts; the one who treats it as the protective line it is keeps his sources and his collectors safe.
Manuals & References — What Chapters Matter
- ATP 2-22.3 — Human Intelligence Collector Operations.You teach it now, not just consume it. Your collectors learn the approved approaches and the prohibitions from how you QC their session plans and their reporting. Know it well enough to explain WHY an approach is out of bounds, not just that it is — the collector who understands the doctrine holds the line on his own. This is the regulation your signature stands on every time you approve a session.
- AR 381-10 — U.S. Army Intelligence Activities; AR 381-20 — Counterintelligence; AR 381-100 — the Army intelligence-activities procedural framework.381-10 governs what the team can collect and under what authority; 381-20 governs the CI boundary you enforce; 381-100 is the procedural framework you operate the team under. At E-5 you are accountable for the team's compliance with all three, which means you self-audit against them and you catch the drift before the IG does.
- ICD 203 — Analytic Standards; ICD 206 — Sourcing Requirements for Disseminated Analytic Products.The IC-wide rubrics you QC every team product against. ICD 203 for objectivity, sourcing, and expressing uncertainty; ICD 206 for how a disseminated product is sourced. Your collectors should be writing to these because you hold the gate at this standard — the report that meets them is the report that gets cited at theater instead of returned.
- DoDD 3115.09 — DoD Intelligence Interrogations, Detainee Debriefings, and Tactical Questioning.The DoD policy that bridges the law of war and ATP 2-22.3 and that your unit SOP flows from. You enforce the standard it sets across the team, and you are the NCO who catches a 'how we do it here' proposal that does not match what DoD actually authorizes — because at this rank, you are the one who knows the difference.
- AR 380-5 — Information Security; AR 381-12 — TARP.AR 380-5 is the classified-handling discipline your team's files are audited against; AR 381-12 (TARP) is what you and your collectors report, when, and to whom. You enforce both on the team — you make sure the files are clean for the audit and you make sure your collectors self-report inside the windows before Continuous Vetting finds it for them.
- FM 2-0 — Intelligence; the law of war and the Geneva Conventions as the hard legal ceiling you enforce on the team.FM 2-0 keeps your team's HUMINT product fitted into the all-source picture the S2X briefs. The law of war and the Geneva Conventions are the ceiling above ATP 2-22.3 that you are now accountable for enforcing — not reciting, enforcing — for every session every collector on your team runs. That accountability is the spine of the NCO job in this MOS.
Standards — How to Hit Each
- BLC graduate; ALC slot built and ready when the schedule drops.ALC is the next professional-development gate and the slot pipeline runs through your section NCOIC and the brigade S3 schedule. Have the packet ready — ATRRS, prerequisites, DLC complete — so when the slot drops you take it instead of deferring it. The SGT who defers ALC because the team is busy is the SGT whose SSG timeline slips; the one who has the slot built and goes when it comes is the one the section reads as ready to broaden.
- Team reporting quality measurable — IIR rework rate, source-evaluation accuracy, zero oversight or legal-compliance findings during your tenure.Track the team's rework rate the way you tracked your own at E-4, but now across every collector. Spot-check source evaluations against the reporting that came back from theater. Self-audit the oversight files monthly. 'Zero findings during my tenure' is the metric the S2X and the senior rater read, and it is the one entirely inside your control — it depends on the gate you hold and the files you keep, not on the sources the team happens to draw.
- ACFT 560+ as a floor — your collectors do not respect an NCO who skates the test they are graded on.560 is a leader's score, not a passing score, and at this rank your number is a leadership statement. Build it the way you taught your SPCs to — deadlift and push-up volume, interval running, grip and core — and lead the team's PT plan from the front. The collectors who watch their team NCO out-score them are the collectors who do not call the HUMINT shop soft and do not cut corners on the standard you set, because you obviously do not cut corners on yours.
- DLPT maintained and the team's language readiness tracked — a team that loses its language capability loses its mission.If you hold a language, keep your own DLPT current and visible. Track every collector's language readiness as a team metric and schedule sustainment into the battle rhythm — a team's language capability decays quietly until a requirement surfaces it. Re-test collectors before scores lapse. The team NCO who lets the team's language readiness drift is the one explaining to the S2X why the team can no longer cover a requirement the brigade is counting on.
- Promotion points stacked: schools, language pay, credentials, college, correspondence (DLC), and a security file with zero friction.Your own board competitiveness still matters — keep the point stack current and the DLC progressing. But at this rank the security file is the differentiator that points cannot capture: an NCO with zero security friction is the one the warrant trusts and the chain promotes without a second conversation. Self-report under TARP / SEAD 3 inside every window, keep the finances stable, and never carry an unreported anything into a reinvestigation. Clean AND competent is the combination that pins SSG and opens the technician door.
Technical Mistakes — Concrete Consequences
- Approving an approach or session plan you have not personally walked against ATP 2-22.3.You signed for the team — a compliance failure under you is yours to answer for, in writing, possibly under a 15-6. The collector ran the approach you approved; the allegation lands on the approval. The IG and CI find an un-walked plan before you do, and the senior rater remembers the SGT who rubber-stamped a session that crossed the line. Walk every plan, or do not sign it.
- Pushing a source's reliability up because the requirement is hot.You QC'd it; if the reporting is wrong, the commander's bad decision traces back to your gate. Source evaluation is the discipline you enforce on the team, and the moment you inflate it under pressure you have taught the team that the gate moves when the requirement is urgent. The burn-notice on a fabricator graded reliable has your name on it as the NCO who let it through.
- Counseling verbally instead of on a DA 4856.If a collector's sourcing or oversight slip is not in writing, the senior rater cannot defend you, the section NCOIC cannot help you, and the IG reads the gap as 'the NCO knew and did nothing.' The undocumented counseling protects no one and develops no one. When the same slip surfaces again — and it will, because you never gave the collector a measurable plan — you have no record that you addressed it the first time.
- Letting source-administrative paperwork drift because operations are busy.The audit does not care how busy you were. A file gap is a finding, and in HUMINT a finding can be a security incident that triggers a CI review. The team NCO who treats the file as paperwork is the one explaining a missing line to an inspector while a collector's clearance and a source's safety hang on the answer. Self-audit monthly; the inspection should find nothing you did not already fix.
- Treating the CI deconfliction line as a formality.Step a collector into a CI investigation as a collection effort and you have compromised both — the investigation loses its integrity and the source loses protection. AR 381-20 draws the boundary to keep sources and soldiers safe; going around it is how both get burned. The SGT who lets his team work an indicator as collection instead of handing it to CI is the SGT who learns the boundary the hard way, after the compromise.
Career Decisions at This Rank
- 351M (HUMINT Collection Technician) packet versus the NCO track to SSG.This is the strategic fork of the rank. The 351M warrant is the deep-collection-expertise path — you stay close to the craft, mentor collection, and become the technical authority the formation leans on. The NCO track broadens you into SSG section NCOIC, then SFC senior HUMINT NCO, running the workforce and the readiness picture. Both are real, respected careers. The honest test the warrant and the section NCOIC will help you run: do your strengths point at being the best collector and collection-mentor in the room (technician), or at building and leading the broader formation (NCO)? Build the packet if the craft is the thing you love and your reporting and files are the proof. You can take the NCO track if you decide the leadership load is where you do your best work.
- ALC timing against the team's operational calendar.ALC is the next professional-development gate, but it pulls you out of the team for the course. The decision is whether to take the earliest slot — keeps your SSG timeline on track — or wait for a window that does not strip the team of its NCO during a CTC rotation or a real-world mission. Have the packet built and ready either way; the trap is deferring so long that the slot becomes a problem at the next board. Talk to the section NCOIC about the unit's calendar and your collectors' readiness to run without you before you lock the slot.
- Re-enlistment / SRB as a SGT with a clear path.Your re-enlistment math at SGT is different from the SPC window — you are now a trained, board-selected NCO in a hard-to-fill MOS. Pull the current HRC SRB MILPER for 35M before assuming a bonus; 35M is often on the schedule and the zone math at SGT can be favorable. The honest factor is direction: a SGT with a 351M conversation in motion or a clear NCO-track path forward, a friction-free clearance, and a team he is good at running has a strong re-up case; a SGT burning out on the SCIF or chafing at the NCO load should weigh the transition honestly. Cleared HUMINT NCOs have real civilian options, but the in-service path is also strong — decide on direction, not just the bonus.
- Developing your collectors for the SGT board versus protecting them from hard reps.Your collectors' board competitiveness is partly your responsibility now, and the way you build it is by giving them hard reps — the difficult source, the first independent session, the reporting that has to clear a real gate — and counseling them through the misses. The temptation is to keep the hard work for yourself to protect the team's metrics; the cost is collectors who never develop and never hit the slate. The SGT whose collectors make the SGT board is the SGT the chain reads as a developer of people, which is exactly what the SSG board and the technician sponsor both want to see. Develop them on purpose, document it, and let them earn the reps.
- Holding the line for someone else under pressure.This is not a paperwork decision; it is the decision that defines the rank. At E-4 you held the legal line for your own sessions. At E-5 you hold it for collectors who want to perform, against requirements that are hot, with a section NCOIC who wants results. The analysis is simple and the execution is hard: ATP 2-22.3 and the law of war do not move, you signed for the team, and a compliance failure under you is yours to answer for. The SGT who decides in advance that he will say no when he has to — and who builds the documentation habit that lets him prove the team stayed in bounds — is the SGT whose career survives the contested day. The one who decides he will 'use judgment' under pressure is the one who eventually crosses the line for a talented collector and a valuable source, and there is no coming back from that in this MOS.
How the Seat Varies by Unit Type
- BCT / division MI company HUMINT team NCOThe team NCO in a tactical element runs collectors against brigade or division requirements and lives by the CTC cycle. The team is small and the feedback is fast, which means your gate and your battle rhythm get tested constantly and your reputation forms quickly with the section NCOIC and the warrant. The SGT who builds a rhythm the team can run during a rotation — clean reporting, clean files, line held — is the one the S2X names when the brigade slide says 'HUMINT is solid.' The trade-off is the tactical analytic problem; the strategic-HUMINT exposure comes at the next assignment.
- Brigade / division S2X team NCO / OMT-adjacentCloser to the S2X and the operational management element, the team NCO does more requirements-management and deconfliction and gets an earlier education in the OMT skills that define the SSG section-NCOIC job. More staff visibility, more coordination with CI, and a faster path into the management side of the discipline. The SGT here is being read earlier for the SSG track because the section sees how he handles the requirements and deconfliction picture, not just the collection.
- Theater / MI battalion HUMINT team NCOLeading a team that works theater-level problems means the reporting standards (ICD 203 / 206) bite harder because the product moves toward the national IC, and your QC gate is graded by a more demanding consumer. The OPTEMPO is more deliberate, the analytic rigor is higher, and the credibility a team NCO builds here travels well into the technician track and the cleared-civilian world. The trade-off is fewer raw tactical reps and a sometimes-slower pinning rhythm than a BCT seat.
- INSCOM unit / closed-access HUMINT formation team NCOThe team NCO in an INSCOM or closed-access formation runs collectors in a more compartmented environment with tighter access controls and a more sensitive source picture. The craft and the legal discipline are identical; the difference is the closed-access culture and the higher sensitivity of the deconfliction picture. Seats are often by name-request, so the SGT who lands one already has a reputation worth requesting — clean gate, clean files, line held without exception.
- Joint / supported-staff HUMINT team NCO (JTF, task-organized element)On a joint or task-organized staff, the team NCO has to brief and report in the supported staff's language and coordinate deconfliction across a crowded picture of elements that may not be Army. The authorities and OPSEC discipline get more scrutiny because more eyes are on the team. It is a stretch seat that builds the cross-organizational fluency the SSG section-NCOIC job and the SFC senior-HUMINT-NCO job both demand — usually given to the SGT whose gate and files are already trusted at home.
What Good Looks Like at This Rank
The good SGT 35M is the team NCO the S2X trusts with the reporting picture on a contested day. His team's IIRs get cited up the chain because every product cleared a real QC gate — analytic pass and legal-compliance pass — before it left the team. His collectors pass their reviews the first time, because he counsels them in writing, redlines their reporting to teach not just to correct, and walks every session plan against ATP 2-22.3 before he signs it. He says 'I am not approving this approach' when he has to, and he explains the doctrine when he does, so his collectors learn the line as understanding rather than as a rule they resent. The standard propagates through his team without a class, because they watch him hold it consistently — including the time the source was valuable and the requirement was hot and he held it anyway.
His oversight files survive any audit without a comment, because he self-audits monthly and fixes the drift before the inspector arrives. His team's language readiness holds, so the brigade never loses a requirement on his account. His ACFT is a leader's score, so nobody calls the HUMINT shop soft. His own security file has zero friction, and so do his collectors' — he made self-reporting under TARP / SEAD 3 a team norm, not a once-a-year scramble. He keeps collecting himself, running sessions alongside his team, because he knows the day he stops is the day his coaching goes stale and his redline loses its credibility.
The SGT being read for the next level looks different from the SGT who is comfortable owning a team. He has ALC built and ready, his collectors are on the SGT-board slate because he raised them to write clean and hold their own line, and the warrant has the 351M technician conversation on the table because his team's product and files are the proof of his craft. He is honest with himself about the fork in front of him — technician deep-expertise versus the NCO track to SSG section NCOIC — and he is building the case for whichever one his strengths actually fit, not the one that sounds more impressive. The comfortable SGT runs a clean team and stops there; the next-level SGT runs a clean team AND builds the NCOs and the packet that decide the next decade of his career.
Preview — The Next Rank
E-6 Staff Sergeant is the next rank, and it moves you from owning a team to owning a section — multiple collection teams, or an operational management team (OMT), on a MI company, a brigade S2X, or a theater HUMINT element. The captain runs the staff; you run the collectors, the reporting standard, and the legal discipline across more than one team. The question scales again: at E-5 you owned your team's reporting and line; at E-6 you set and enforce the reporting and oversight standard that every team in your section runs by, and you sign for the collection effort the S2X briefs to the brigade commander.
The new load at SSG is management at scale and senior-NCO judgment. You manage requirements against placement and access across multiple teams. You build two SGTs into ALC-graduate, SLC-ready team NCOs, which means you are now developing the developers. You sit in the S2X huddle and coordinate with CI, the ISR enterprise, and theater HUMINT elements. And you become the senior enlisted voice on whether a source is worth the risk — and the one who tells a colonel 'we cannot collect that under our authorities' when the room wants a different answer, and backs it with the regulation. That conversation is the SSG version of the 'I am not approving this approach' conversation you have with a cherry now, except the audience is a field-grade officer and the stakes are the section's authority to operate.
The differentiator at SSG and toward SFC is whether you can run a section's reporting and legal discipline through a CTC rotation and a real-world mission without a finding, build NCOs the next board selects, and defend the section's authorities line to a commander. ALC graduate, SLC packet built, a language credential or instructor-level reporting qualification as the edge, and an NCOER profile written on the official achievement list — action-result-impact, measurable, no filler. The 351M technician path either becomes the packet you complete or the door you consciously close in favor of the senior-NCO track to SFC senior HUMINT NCO and beyond. Run a clean team now, build the SGTs under you, decide the fork honestly, and the section that 'HUMINT is solid' gets said about is the one you will be running next.
FAQ
35M E5 — Frequently Asked Questions
Q01What does a E5 35M (Human Intelligence Collector) actually do?
You lead a small HUMINT collection team — a few collectors and their interpreters running screenings, debriefs, and source contacts.
Q02What's the most important thing to know as a E5 35M?
You are an NCO now and the quality-control gate on everything your team reports.
Q03What does a typical day look like for a E5 35M?
Time-blocked day at the E5 35M rank tier: 0500 Wake. Coffee, no phone in the SCIF. PT uniform on. Run the team's day in your head — which collector runs which source, which session plans you have to walk, which IIRs from yesterday still need to clear the gate, 0530-0700 Lead team PT from the front. Your ACFT is a leadership statement at this rank, so you set the pace. Then hygiene, OCPs, breakfast — and a quick read of any overnight item that touches the team's sources, 0700-0730 In-process the SCIF, SF 702 past the team's containers, systems up.…
Q04What mistakes get E5 35M soldiers fired or relieved?
Approving an approach or a session plan you have not personally walked against ATP 2-22.3. You signed for the team — a compliance failure under you is your signature to answer for, in writing, possibly under a 15-6, and the IG and CI find it before you do; Counseling verbally. If a collector's sourcing or oversight slip is not on a DA 4856, the senior rater cannot defend you and the section NCOIC cannot help you. Document the slip and the development plan or it did not happen;…
Q05What career decisions matter most at the E5 35M rank tier?
351M (HUMINT Collection Technician) packet versus the NCO track to SSG — This is the strategic fork of the rank. The 351M warrant is the deep-collection-expertise path — you stay close to the craft, mentor collection, and become the technical authority the formation leans on. The NCO track broadens you into SSG section NCOIC, then SFC senior HUMINT NCO, running the workforce and the readiness picture. Both are real, respected careers.…
Q06What's next after E5 for a 35M (Human Intelligence Collector) in the Army?
E-6 Staff Sergeant is the next rank, and it moves you from owning a team to owning a section — multiple collection teams, or an operational management team (OMT), on a MI company, a brigade S2X, or a theater HUMINT element.
Q07What manuals and regulations does a E5 35M need to know cold?
ATP 2-22.3 — Human Intelligence Collector Operations (you teach it now, not just consume it).; AR 381-10 — U.S. Army Intelligence Activities; AR 381-20 — Counterintelligence; AR 381-100 — the Army intelligence-activities procedural framework you operate under.; ICD 203 — Analytic Standards; ICD 206 — Sourcing Requirements.
Based on 17 tips from 0 contributors
Published by the Honest MOS Editorial DeskVerified against DoD/.gov sourcesUpdated May 2026Editorial standards