Signals Intelligence Analysis Technician

You are the SIGINT technical authority in the formation — the officer the S2, the battalion CDR, and the supported commander lean on when the analytic question is beyond what a senior NCO can answer. You came up through 35N; now the MOS prefix is different and the accountability goes with it.

You completed the SIGINT Warrant Basic Course (WBC) at Fort Huachuca under the U.S. Army Intelligence Center of Excellence — roughly 4-5 months of technical, doctrinal, and leadership instruction on collection management, requirements processing, source-to-product traceability, multi-INT fusion, and warrant officer duties — and arrived at your gaining unit: a Military Intelligence battalion organic to a BCT (MI BN under the BSTB), a Divisional MI battalion, an INSCOM theater intel brigade (470th at JBSA-Fort Sam Houston, 500th at Schofield Barracks, 501st in Korea, 66th in Europe, 66th MI BDE in Wiesbaden), the 706th MI Group at Fort Meade (NSA/CSS co-located), the 780th MI Brigade at Fort Eisenhower (formerly Fort Gordon, renamed 2023), or a Cyber Mission Force seat supporting ARCYBER / USCYBERCOM. Your daily work is the bridge between collection and analysis: you manage the unit's SIGINT collection requirements, advise the S2 officer on which collection assets can answer which PIRs, evaluate the technical quality of reports before they leave the element, and keep the analytic line clean to ICD 203 and ICD 206 standards. You mentor the senior 35N NCOs while also learning — fast — that warrant authority is different from senior-NCO authority, and that the O-code uniform changes the way the room hears you before you have earned the right to be heard.

• 01Manage the SIGINT collection requirements cycle — translate commander PIRs into collection strategies, deconflict requirements across assets, and brief the S2 officer on collection feasibility and gaps with a defendable assessment, not a wish list.
• 02Evaluate SIGINT product quality to ICD 203 / ICD 206 standards — confidence levels, sourcing language, alternative analysis notation, and the analytic line the next echelon will cite must be supportable by what the collection actually shows.
• 03Advise on SIGINT integration into all-source products — brief the S2 or G2 staff on what SIGINT can and cannot answer, and how to caveat single-source judgments when the multi-INT picture is ambiguous.
• 04Operate inside the collection management framework of FM 3-55 — collection planning, taskings, assessment, and the feedback loop from the supported commander back to the collector.
• 05Run TS/SCI compartmented information access discipline inside the element — badge protocol, two-person integrity, AR 380-5 and ICD 705 SCIF standards — with zero tolerance for shortcuts from soldiers who "know the SOP."
• 06Mentor 35N NCOs on technical tradecraft while being honest about the limits of your own experience. You came from the enlisted seat; the SFC with ten more years of position-time than you has knowledge you need. The warrant who fakes depth early loses the formation inside a year.

• —ADP 2-0 — Intelligence (Army intelligence doctrine at the foundational level — know it before you brief the S2).
• —ATP 2-22.3 — Human Intelligence Collector Operations (the multi-INT integration reference that frames how SIGINT and HUMINT talk to each other at the brigade and below level).
• —FM 3-55 — Information Collection (the collection management framework — requirements, collection assets, planning, assessment loop — that governs your daily work as a collection manager).
• —ICD 203 — Analytic Standards; ICD 206 — Sourcing Standards for Finished Intelligence (the Intelligence Community standards every SIGINT product you sign must meet).
• —AR 381-10 — U.S. Army Intelligence Activities; AR 380-5 — Information Security Program; AR 380-67 — Personnel Security (the legal and regulatory framework for intelligence activities and clearance management).
• —DoDM 8140 — Cyberspace Workforce Qualification; DoDM 5105.21 — SCI Administrative Security Manual (workforce qualification and SCI access framework — your soldiers need to be coded and credentialed correctly under the billet).

• —SIGINT Warrant Basic Course (WBC) complete and first unit assignment on-boarded — requirements management JQR tasks signed off within the published timeline at your gaining unit.
• —ICD 203 / ICD 206 product quality standard — every SIGINT product or analytic contribution leaving the element under your name meets the confidence, sourcing, and alternative-analysis requirements without a return from the next-echelon reviewer.
• —ACFT pass at the warrant officer standard — the technical warrant does not get a fitness exemption from the Army Human Performance standard.
• —First Officer Evaluation Report (OER) at or above center of mass for the rater's profile — warrant officer OERs in a small MI community are read by name at the next board. A below-center profile at WO1/CW2 follows the warrant for years.
• —TS/SCI polygraph current and reinvestigation on the AR 380-67 schedule — a lapsed reinvestigation removes the warrant from the position and puts the mission on the SSO's brief to the CO.

• —Confusing collection management with production. Your job is to ensure the right collection gets tasked and the product is technically defensible — not to rewrite the all-source analyst's judgment after the fact. Overstepping into production destroys the S2 staff relationship fast.
• —Letting a SIGINT product leave the element with sourcing language that overstates collection confidence. The next echelon's analyst, NSA reviewer, or supported commander cites the product — and when the target does not perform as stated, they trace the overstatement back to the originating element and the warrant who cleared it.
• —Signing a requirements package the collection asset cannot fulfill because the S2 wants an answer. Brief the feasibility gap honestly. A collection requirement that tasks against an asset's technical limitation wastes the asset and produces a negative indicator the consumer will misread.
• —Treating AR 380-5 / ICD 705 SCIF discipline as the SSO's enforcement problem. The warrant is an officer; the soldiers watch what the officer does when the SSO is not in the room.
• —Faking expertise on a target set or technical parameter you have not worked. The senior 35N on the team has been on that target for three years; the warrant who pretends to own it loses the room in the first working group.

The good junior 352N warrant is the officer the S2 can put in front of the brigade commander on a collection-feasibility brief and trust that the answer — including the "we cannot answer that from SIGINT alone" answer — will be technically sound and honestly stated. The 35N section's products survive the next echelon's read. The requirements packages it sends up are executable, and the supported commander names the element's contribution in the debrief. By the end of the CW2 time the warrant's CW3 packet is moving and the battalion CDR's OER bullet says "select to CW3 — trust with BCT-level collection management without supervision."

You are the institutional SIGINT brain trust — the technical authority the brigade CDR, the division G2, the INSCOM CG, the ARCYBER staff, and the NSA civilian senior call when the collection architecture is broken, the analytic line will not hold, or the community needs someone who actually knows the target. At CW4 and CW5 you have accumulated what cannot be taught.

At CW3 you are running the SIGINT technical function for an MI battalion, a theater intel brigade element, a CMF SIGINT support cell, or an NSA / CSS analytical line — advising O-5s and O-6s on the technical limits and strategic implications of SIGINT collection, managing the requirements architecture across an area of responsibility, and producing or overseeing the production of finished intelligence the supported command actually acts on. At CW4 you are the senior technical warrant in a brigade, a group, or a combined-action element — the officer the INSCOM commander, the ARCYBER chief of staff, or the NSA Deputy Director calls into the room when the conversation is above the S2's pay grade. At CW5 you are one of the few warrant officers in the Army with genuine institutional weight at the strategic level — the master warrant who advises on SIGINT collection architecture, workforce development, technical doctrine revision, and the long-range questions about what the cryptologic enterprise is and is not capable of. Your mentor load includes CW2s and CW3s who need you to tell them the truth about the career decisions they are weighing; your technical load includes analytic lines the GS-15 NSA civilian across the hall is watching you carry. You are also now fully inside the post-service positioning conversation — NSA SES pipelines, defense contractor SIGINT lead roles at Booz Allen, Leidos, SAIC, CACI, MITRE at Fort Meade and Fort Eisenhower, and federal civilian SES-track GS-14/15 billets are real and open to a CW5 with this record.

• 01Architect the SIGINT collection and requirements strategy for a brigade or higher command — collection planning from PIR to asset to product to assessment, deconflicted across multi-INT sources and joint collection platforms, briefable to a two-star without a translator.
• 02Advise the division G2, INSCOM staff, ARCYBER, or supported COCOM J2 on the technical and legal limits of SIGINT collection — what EO 12333, the USSID series (unclassified provisions), and the applicable FISA authorities permit, what they do not, and where the line is when the commander is asking for something that will not survive the General Counsel review.
• 03Lead or oversee production of finished SIGINT or SIGINT-integrated all-source products to ICD 203 / ICD 206 standards at the theater or strategic level — analytic lines that senior consumers act on and that survive after-action review when the collection is tested against events.
• 04Mentor junior warrants (WO1/CW2/CW3) on collection management, analytic tradecraft, officer-enlisted dynamics, and the career decisions — broadening tours, 17A conversion consideration, NSA-civilian crossover, contractor transition — that shape the next generation of SIGINT warrant officers.
• 05Lead SCIF accreditation cycles (ICD 705), DoDM 8140 workforce qualification audits, and AR 380-67 reinvestigation tracking across a multi-site MI element without a CAT-1 finding that traces to a warrant-level oversight failure.
• 06Translate SIGINT technical findings into operational and strategic decision support language — brief a four-star, testify before a congressional staff member, or write the SIGINT assessment paragraph in the commander's decision brief so the consumer knows what the intelligence says, what it does not say, and how much to trust it.

• —ADP 2-0 — Intelligence; ADP 3-0 — Operations (at the senior warrant level the doctrinal link between intelligence and operations is your translation responsibility, not the S3's).
• —ATP 2-22.3 — Human Intelligence Collector Operations; FM 3-55 — Information Collection (still your operational backbone — you are now the officer who teaches these to the staff).
• —JP 2-0 — Joint Intelligence; JP 2-01 — Joint and National Intelligence Support to Military Operations (the joint framework your SIGINT product enters when it reaches a COCOM J2 or NSA analytical line).
• —ICD 203 — Analytic Standards; ICD 206 — Sourcing Standards for Finished Intelligence; ICD 705 — SCIF Accreditation (the Intelligence Community standards you enforce as the technical senior, not the ones you study for a test).
• —EO 12333 — United States Intelligence Activities; DoDD 5240.01 — DoD Intelligence Activities (the legal architecture above every SIGINT collection and reporting decision you make or advise on).
• —DA PAM 600-3 — Officer Professional Development (Warrant Officer section); DoDM 8140 — Cyberspace Workforce Qualification; DoDM 5105.21 — SCI Administrative Security Manual (your career and your soldiers' careers live inside these — know the WO technician chapter of 600-3 before you advise anyone).

• —Intermediate Level Education (ILE) or equivalent warrant officer professional military education complete on the Army PME schedule — senior warrant officers who skip PME get passed for the billets that matter.
• —Two or more successive OER profiles at top block — in the MI / SIGINT warrant community, CW4 and CW5 promotions are competitive and the OER narrative from the CW3 billet is the primary document the board reads.
• —Production record: analytic lines, requirements architectures, or collection programs you led or shaped have demonstrable outcomes the supported command names in AARs or in writing — not self-assessed contributions.
• —SCIF / SCI program under your oversight: clean ICD 705 accreditation cycle, AR 380-67 reinvestigation schedule current, DoDM 8140 workforce-qualification current across the element — no CAT-1 findings attributable to a failure of the senior warrant's oversight.
• —CW5 competition (for those going to 5): the Army DA Centralized Warrant Officer Promotion Board reads your entire OER file plus the senior rater profile from the current billet; pull the current HRC SELCONT and the WO promotion announcement for the actual demographics — the rest is the record you built.

• —Providing a collection-feasibility assessment that tells the commander what he wants to hear instead of what the asset can produce. At the senior warrant level the downstream users — the COCOM J2 staff, the NSA analytical element, the national-level consumer — act on your assessment. A confident overstatement that turns out wrong at the strategic level ends a career and, in a contested environment, costs more than that.
• —Treating the USSID series and EO 12333 compliance conversation as the attorney's problem. The senior SIGINT warrant who advises on a collection action that skates the legal boundary and then says "the lawyers cleared it" is the warrant named in the IG referral when the collection report surfaces in the wrong congressional inbox.
• —Letting junior warrants carry the technical weight of a senior billet because "they have it." CW4 and CW5 authority exists to solve the problems CW2 and CW3 cannot. A senior warrant who stages behind the juniors loses both the technical credibility and the mentor relationship that makes the community function.
• —Stopping deckplate technical work — sitting a position, reading current collection, pulling raw — because "I am on the staff now." The SIGINT collection landscape changes continuously; the CW4 who has not driven a position in two years is a senior warrant who cannot catch a product error that a GS-12 analyst would flag.
• —Confusing community seniority with institutional authority. CW5 is the Army's most senior technical warrant designation — and the NSA GS-15 branch chief and the COCOM J2 analyst both know when the warrant's operational read is two threat-generation cycles behind current. Stay current or stop advising on current.

The good senior 352N warrant is the officer the division G2, the INSCOM CG, the ARCYBER chief of staff, and the NSA team chief call into the room when the collection architecture is not answering the requirement and they need someone to tell them why — and what to do about it. His analytic lines survive the next-echelon read. His requirements packages produce results the supported commander names in the AAR. His junior warrants carry the right analytic instincts because he told them the truth, not the comfortable version. At CW5 the MI / SIGINT community names him in the doctrine revisions, the schoolhouse curriculum, and the next warrant cohort's accession standard. Post-service the door into an NSA SES pipeline, a Booz Allen / Leidos / SAIC SIGINT lead role at Fort Meade or Fort Eisenhower, or a federal civilian GS-14/15 SIGINT chair opens the week he clears — because he never let the clearance, the analytic chops, or the collection-management instincts go cold.