Skip to main content
HonestMOS
●InvestigationsCongress made VA disability claims free to file. An entire industry charges veterans anyway — and nobody can stop them.→
←Back to 352N Signals Intelligence Analysis Technician — overview, pay, training, civilian translation, reviews
352NWO1-CW2

Signals Intelligence Analysis Technician

WO1 to CW2 (Junior Warrant) · Army

WO1–CW2CW3–CW5
HEADS UP

The SIGINT Warrant Basic Course at Fort Huachuca will teach you the collection management framework and the officer transition — but the first 90 days in your gaining unit will teach you whether you understand the difference between being a senior analyst and being a technical officer. Those are not the same job. The warrants who conflate them spend two years rebuilding credibility they never had to lose.

The Honest MOS Read
You came up through 35N — most likely as a well-regarded SGT or SSG with a strong JQR jacket, two or three position qualifications, solid ICD 203 product fundamentals, and a recommendation from an SFC, a CW3, or a watch chief who thought you were carrying warrant-officer thinking before you had the designation. Then you sat the WBC at the U.S. Army Intelligence Center of Excellence at Fort Huachuca, Arizona — the Army's intelligence schoolhouse, which also trains the 35N, 35P, 35S, and 35F pipelines under the same roof — and arrived at your first warrant billet carrying a new uniform and a WO1 bar that the formation is watching to see if it matches the person underneath. At Fort Huachuca the WBC runs you through collection management doctrine, requirements processing, source evaluation, legal authorities (EO 12333, the USSID series unclassified provisions), warrant officer leadership responsibilities, and the practical gap between what collection promises and what collection delivers. It is not a refresher of your 35N training — it is a reorientation of your role inside the SIGINT enterprise from 'analyst executing the mission' to 'technical officer advising the staff, managing the requirements, and accountable for the product quality out the door.' Your first unit assignment is most likely one of four places: a Military Intelligence battalion organic to a Brigade Combat Team (the BSTB-organic MI BN that provides the BCT's organic intelligence support), a Divisional MI battalion at Fort Cavazos (1st Cavalry Division), Fort Wainwright (25th ID), Fort Campbell (101st Airborne), Fort Stewart (3rd ID), Fort Bliss (1st Armored Division), or one of the OCONUS divisions in Europe or Korea; an INSCOM theater intel brigade element (the 470th at JBSA-Fort Sam Houston, the 500th at Schofield Barracks, the 501st in Korea, or the 66th MI BDE in Wiesbaden); or a 706th MI Group or 780th MI Brigade seat at Fort Eisenhower or Fort Meade — the NSA/CSS and ARCYBER-adjacent assignments that put you immediately on a joint floor with GS-13 NSA civilians who have been on the same target set since before you enlisted. The daily work is collection management and analytic quality control. You translate the S2's Priority Intelligence Requirements into collection strategies, evaluate whether the tasked assets can actually answer the question (they frequently cannot — and saying so is your job, not the S2's staff officer's job), review SIGINT products for ICD 203 and ICD 206 compliance before they leave the element, and advise the S2 on how to integrate what the SIGINT collection shows into the all-source analytic line. You are also the officer the formation watches for SCIF discipline — badge protocol, two-person integrity, AR 380-5 and ICD 705 enforcement — because the warrant is an officer, and what the officer does when the SSO is not watching sets the standard for the section. The hardest adjustment at WO1/CW2 is not technical. You walked in with strong analytic tradecraft and a working knowledge of the collection systems your unit uses. The adjustment is the officer-enlisted dynamic — specifically, that the senior NCO in the room (the SFC or SSG who has been on the target set for three years) may know things you do not, and the warrant officer who pretends otherwise loses the section's respect before he has built any. The best junior 352N warrants are honest about the gap: they carry the officer authority and the ICD/doctrine framework, they defer to the NCOs on target familiarity and position-specific tradecraft, and they close the gap aggressively through OJT, reading the traffic, and sitting a position themselves rather than supervising from the console room door. The goal of the WO1/CW2 window is to build enough of a technical and leadership record that the CW3 board reads your OER profile and selects — and the battalion CDR's OER narrative says 'trust with BCT-level collection management without supervision' rather than 'technically competent, still developing officer judgment.' Those are two different profiles. The record that builds the first one is deliberate, not incidental.
Career Arc
  • 01WO1 appointment: SIGINT Warrant Basic Course at Fort Huachuca — 4-5 months; arrive at gaining unit; begin collection management OJT and requirements JQR sign-off within the published timeline.
  • 02First 18 months: first unit assignment — SIGINT collection management, product quality review, ICD 203/206 compliance on the element's output, SCIF program discipline. First OER written at approximately 12 months in billet.
  • 03CW2 promotion window: ~24 months time-in-grade from WO1; promotion is federally controlled and relatively formula-driven at CW2 — focus is building the technical and leadership record for the competitive CW3 board, not the CW2 pin.
  • 04Broadening opportunities: NSA / CSS rotation at Fort Meade, INSCOM theater billet, CMF SIGINT support seat, or 780th MI BDE cyber-SIGINT integration assignment. The warrants who spend the WO1/CW2 window at the same unit doing the same job and the warrants who broaden are visibly different to the CW3 board.
  • 05CW3 packet: the DA Centralized Warrant Officer Promotion Board reads your OER profile and your senior rater's narrative. The CW2 who has managed collection requirements at two different echelons, held a broadening tour, and has a senior-rater bullet that uses the word 'trust' without qualification is the packet that pins.
  • 06Post-CW2 decision: CW3 in an MI battalion or INSCOM element, or begin positioning for the senior warrant track (CW4/CW5 requires selection to a centralized billet; the record that matters starts at WO1/CW2, not at CW3).
Common Screwups
  • ×OPSEC breach in or out of the SCIF — a geotag, a vague-but-identifiable social media post, a conversation on an unclassified line that describes a collection result. At this rank in this MOS, one OPSEC breach triggers an SCI access review, an AR 381-10 / AR 381-12 referral, and an OER narrative the CW3 board will read for the rest of the career.
  • ×Financial misconduct or debt crisis without a command-level counseling. TS/SCI with poly reinvestigation under AR 380-67 specifically asks about financial judgment; a warrant officer who hits a debt spiral and does not notify the security officer puts the clearance, the access, and the mission at risk simultaneously.
  • ×Fraternization or inappropriate personal relationship with an enlisted soldier in the section — the formation is watching the warrant officer's social boundaries the same way it watches the junior officer's. The UCMJ and AR 600-20 apply; the MI community is small enough that the story travels before the investigation closes.
  • ×Providing a written product or assessment that overstates collection confidence and then defending the overstatement when the next-echelon reviewer flags it. The warrant who will not take the correction loses the S2's trust permanently, and a 352N who has lost the S2's trust in an MI battalion is in a billet with no useful purpose.
  • ×Missing a polygraph reinvestigation deadline or allowing a soldier's reinvestigation to slip without a command-level disclosure. The SSO will find it; the SSO will brief the CO; the CO will ask the warrant why it was not on his desk first.

A Day in the Life

  • 0530–0630PT — unit formation or individual workout depending on the MI battalion's PT plan. The 352N warrant is an officer; the formation owns you on PT days.
  • 0700–0730Arrive at the SCIF. Badge in. Review overnight collection reports flagged by the duty officer or the section's on-call NCO. Note any product quality issues before the morning brief.
  • 0730–0830Morning intelligence update brief prep or attendance. BCT/DIV MI BN context: the S2 briefs the CDR at 0800 or 0900; the 352N warrant feeds the SIGINT paragraph, reviews the collection annex, and is present if the CDR asks a collection-feasibility question the S2 needs technical backup on.
  • 0830–1000Collection requirements management — review the outstanding PIR/CCIR slate, check collection tasking status on the current requirements, identify gaps, draft updated requirements or collection strategies for items where the current tasking is not producing results.
  • 1000–1130Product review cycle — evaluate SIGINT products awaiting clearance from the section. ICD 203 / ICD 206 compliance check on confidence language, sourcing statements, alternative analysis notation. Return for revision or clear for transmission.
  • 1130–1300Lunch, then administrative work — OER input, soldier counseling scheduling, JQR signoff documentation, DTS / MEDPROS / IPERMS items. Warrant administrative load is real and the section notices whether the officer handles it or ignores it.
  • 1300–1500Staff coordination — S2 working group, cross-functional collection coordination with the GEOINT section or the all-source analytic team, liaison with the battalion's SSO on any open security items.
  • 1500–1630NCS (National Cryptologic School) course progress, JWICS professional reading, or current collection familiarization — position on a collection system with the SFC's oversight if the JQR task calls for it. The warrant who does not keep current tradecraft currency loses technical credibility faster than any other single factor.
  • 1630–1700End-of-day product and collection summary — brief the section's lead NCO on anything pending overnight. Check the duty officer's watch schedule for anything SIGINT-relevant flagged for commander notification.
  • 1700–1900Depart. Warrant officers at the WO1/CW2 level are not expected to live in the SCIF — the formation notices whether the officer respects normal duty hours or creates an artificial intensity that burns the NCOs without tactical necessity.

Weekly Cadence

The garrison week runs on the morning intelligence brief cycle and the collection requirements review. Mondays are the S2 staff huddle — the warrant clears the collection slate for the week, flags any asset availability constraints, and identifies the PIRs where the current tasking is stale. Mid-week is production volume: products from the previous weekend's collection come due for review, the requirements package for the next window is drafted, and any cross-functional coordination with GEOINT or all-source is done before Thursday's update brief. Thursday and Friday are documentation and administrative completion — OER input is due, JQR signoffs are tracked, soldier counselings are written. When there is a field problem or CTC rotation, the pace inverts. Collection management happens in compressed cycles against a moving operational picture; product review happens faster, with less ability to return-and-revise; the warrant is in the SIGINT element forward or in the analytical cell running real-time requirements against collection windows that will not recur. The competencies that look theoretical in garrison — feasibility assessment, real-time product review, collection-to-staff communication — are tested for real in the field, and the S2 learns during a CTC rotation whether the 352N warrant was actually doing collection management in garrison or just processing administrative paperwork. When there is a SCIF reinspection (ICD 705 accreditation cycle or a command-directed security inspection), the warrant is involved in the pre-inspection walkthrough, the corrective action tracking, and the debrief of any findings. The 352N warrant does not own the SCIF accreditation process — that is the SSO's domain — but the warrant is the officer the CO asks about the section's security posture, and the warrant who cannot answer that question specifically has not been paying attention.

Key Skills — How to Drill Each

  1. 01
    Manage the SIGINT collection requirements cycle — translate commander PIRs into collection strategies and brief collection feasibility with a defensible assessment.
    Study the unit's current collection architecture before you brief the first feasibility question — which assets are tasked, which are tiered, which have bandwidth constraints that the S2 staff does not know about yet. FM 3-55 lays the requirements cycle; your value is applying it to the unit's actual collection posture, not the doctrinal ideal. When the requirement cannot be filled, say so in writing with the gap analysis attached, not in the hallway after the brief.
  2. 02
    Evaluate SIGINT product quality to ICD 203 / ICD 206 standards — confidence language, sourcing, alternative analysis.
    Pull the last ten products the element sent up and mark every sourcing statement against ICD 206. If you find 'reporting indicates' without a sourcing call, 'intelligence suggests' without a confidence level, or a time-sensitive collection report missing the standard caveats — those are your remediation targets. The review discipline is not punitive; it is what separates a 35N section that builds credibility with the next echelon from one that erodes it product by product.
  3. 03
    Advise on SIGINT integration into all-source products — brief what SIGINT can and cannot answer.
    Build a one-page SIGINT capability matrix for the S2 staff that shows, in plain language, which collection assets answer which target-behavior question and at what fidelity. The all-source analyst writing the estimate does not always know what a SIGINT report's sourcing caveat actually means; your job is to make the integration honest, not to make the SIGINT look more capable than it is.
  4. 04
    Run TS/SCI compartmented information access discipline — ICD 705, AR 380-5, two-person integrity.
    Conduct a physical SCIF security walkthrough within the first two weeks in billet — every container, every badge reader, every classified destruction log, every escort log. The warrant officer who inherits a section with lax badge discipline and does not correct it inside 30 days now owns the finding. Document your walkthrough in writing; give a copy to the SSO; have a standard.
  5. 05
    Mentor 35N NCOs on technical tradecraft without pretending to outrun their position experience.
    Set a deliberate one-on-one cadence with the section's SFC and SSG in the first month — not a counseling session, a technical conversation. Ask what collection problems they are not seeing answered and what analytic gaps the S2 ignores. The junior 352N warrant who treats these conversations as management outreach misses the actual function: the senior NCOs will tell you what the section needs from a technical officer that it has not been getting.

Manuals & References — What Chapters Matter

  • ADP 2-0 — Intelligence
    The Army's capstone intelligence doctrine — the framework the S2 officer, the G2 staff, and the CDR use to describe what intelligence is supposed to do. Read it before you brief the staff on anything SIGINT-specific; the terminology your audience uses comes from here and the warrant who does not share the vocabulary loses the room.
  • FM 3-55 — Information Collection
    The collection management doctrine. The requirements-tasking-collection-assessment loop in FM 3-55 is the cycle your daily work operates inside. The gap between what the doctrine describes and what actually works at a BCT MI BN is where your experience as a 35N pays off — read the doctrine, then overlay the actual asset limitations your unit carries.
  • ATP 2-22.3 — Human Intelligence Collector Operations
    The multi-INT integration reference, specifically for understanding how SIGINT and HUMINT collection interact when both are answering the same collection requirement. The S2 staff integrates all-source products; the 352N warrant who understands the seams between SIGINT and HUMINT at the collection level advises more accurately on what gap cannot be closed by a single INT.
  • ICD 203 — Analytic Standards; ICD 206 — Sourcing Standards for Finished Intelligence
    The Intelligence Community product quality standards that govern every SIGINT report and finished product the element produces. Print both and keep them next to the review checklist. A product that leaves the element with a sourcing violation under ICD 206 is a product the next-echelon reviewer sends back — and the sending back is tracked.
  • AR 380-5 — Information Security Program; ICD 705 — SCIF Accreditation
    The legal and physical security framework for the element's classified operations. The WO1/CW2 may not own the SCIF accreditation cycle (that typically sits with the SSO or the unit's senior security officer), but the warrant is the officer the CO looks at when a physical security finding appears. Know what ICD 705 requires; know what AR 380-5 requires for classified destruction, storage, and handling.

Standards — How to Hit Each

  • SIGINT Warrant Basic Course complete and gaining unit JQR requirements on track within the published timeline.
    Do not treat the JQR as a box-checking exercise. Each task in the collection management JQR represents a competency the mission depends on. If a task is being signed off without the underlying proficiency, you will surface the gap at the worst moment — in the S2 brief during a CTC rotation or a contingency event, not in garrison.
  • ICD 203 / ICD 206 product quality standard — every SIGINT product or contribution leaving the element under your name meets IC standards without a next-echelon return.
    Review every product before it sends. If the volume is too high for individual review, build a section quality-control step with the SFC or SSG and spot-review a sample every week. The goal is zero returns — and zero is achievable if the section understands the standard and applies it daily, not on the day the product is due.
  • First OER at or above center of mass for the rater's profile.
    The OER narrative is built by what you do, not what you report. Measurable outcomes — collection requirements managed, products that survived next-echelon review, soldiers who closed JQR tasks on schedule, a SCIF finding that went corrected rather than deferred — are what the rater can defend. Track those outcomes from day one; do not reconstruct them in March when the OER is due in April.

Technical Mistakes — Concrete Consequences

  • Providing a collection-feasibility assessment that tells the S2 what the commander wants rather than what the asset can produce.
    The collection gets tasked, the asset reports negative or is degraded, the S2 briefs the CDR on a gap the CDR thought was covered, and the CDR asks who assessed the collection as feasible. The answer is the warrant. One confident overstatement that produces an operational blind spot is the OER narrative that follows the WO1/CW2 into the CW3 board.
  • Letting a SIGINT product leave the element with sourcing language that overstates what the collection actually shows.
    The supported commander or the NSA analytical line acts on a confidence level the evidence does not support. When the event does not match the assessment, the review traces the product to the originating element and the warrant who cleared it. The next product from the element enters the consumer's inbox with a credibility debt the warrant has to pay off over months.
  • Signing a requirements package for a collection asset against a technical limitation you know exists but did not disclose.
    The asset reports as tasked, the negative indicator is misread as a collection failure rather than an asset-limitation artifact, and the S2 writes a gap in the intelligence picture that the all-source analyst will fill with assumption. You knew the limitation; you did not say so. The warrant's job is to disclose, not to paper over the capability gap to avoid an uncomfortable feasibility conversation.
  • Treating AR 380-5 / ICD 705 SCIF discipline as someone else's enforcement problem.
    The SSO finds the violation — a container left unlocked, a classified document without a cover sheet, an unescorted visitor in the secure space — and the first question is 'where was the warrant?' The officer is accountable for the section's security posture. The soldier who shrugs at SCIF discipline watched the officer shrug first.

Career Decisions at This Rank

  • Broaden tour now (NSA / CSS rotation, CMF seat, INSCOM element) vs. stay in the first assignment through CW2 promotion.
    The CW3 board reads two things: OER profile and career diversity. A WO1/CW2 who spends two years at the same BCT MI BN doing the same collection management job and a WO1/CW2 who does one year at the BCT and one year on a joint floor at Fort Meade with NSA civilians have produced different packets. The broadening is worth the turbulence if the billet produces a genuine technical challenge — not if it is just a different zip code for the same garrison routine. Ask the gaining unit's CW3 or CW4 what the actual work is before you request the assignment.
  • Pursue 17A Cyber Operations Officer conversion vs. remain on the 352N warrant track.
    The 17A branch is growing and the ARCYBER / USCYBERCOM demand signal for SIGINT-trained officers is real. The 17A path is a branch transfer, not a warrant designation change — it means leaving the warrant officer corps, commissioning as a 17A, and entering the Cyber branch officer career path with all the commissioning source requirements and officer schooling that implies. The warrants best positioned to make this move are those whose career arc has been building toward Cyber Mission Force or USCYBERCOM work, not those converting because the 352N board looked competitive. Talk to a serving 17A who came from 35N / 352N before deciding.
  • Apply for the CW3 board on the standard timeline vs. request an additional year of OJT in a broadening assignment to strengthen the packet.
    The standard WO promotion timeline is federally controlled; you cannot delay CW2 promotion. But the CW3 board is a DA Centralized board, and the packet you present is shaped by the billet history and OER profile you accumulate through CW2. The question is not 'should I delay the board' — it is 'is my current billet producing the OER narrative and the technical record the board reads as CW3-ready?' If the honest answer is 'not yet,' the request for a broadening billet or a more demanding assignment before the board window is the right move. Do not wait for someone to offer it.
  • NSA civilian crossover vs. contractor route vs. staying Army through CW4.
    This conversation happens earlier than most junior warrants expect — NSA civilian hiring at the GS-9 to GS-12 entry level is actively recruiting 35N and 352N personnel with current clearances and position qualifications. The trade is: Army housing allowance, retirement clock, and rank structure vs. civilian pay scale, geographic stability at Fort Meade or Fort Eisenhower, and a different kind of career ceiling. The contractor route (Booz Allen, Leidos, SAIC, CACI at Fort Meade) pays more upfront but the clearance is your leverage and deprecates if you leave the work. The honest answer is that all three paths are viable; the choice depends on family geography, financial situation, and how much the Army structure itself — the PT formation, the deployment cycle, the permanent-change-of-station turbulence — is sustainable past CW2.

How the Seat Varies by Unit Type

  • BCT-organic MI Battalion (BSTB or BEB)
    The tactical SIGINT environment — collection management against a near-peer or asymmetric threat, direct support to the BCT CDR, compressed product cycles, field operations during CTC rotations. The 352N warrant here is the BCT's organic SIGINT technical authority; the S2 is a captain or major; the warrant advises that officer directly. High tempo, tight command relationship, visible impact. The limitation is that BCT SIGINT assets are relatively limited compared to the INSCOM or NSA/CSS environments.
  • INSCOM Theater Intel Brigade (470th / 500th / 501st / 66th)
    Regional SIGINT support to a Geographic Combatant Command — CENTCOM, INDOPACOM, EUCOM, SOUTHCOM. More analytic depth, longer-term target development, direct interface with COCOM J2 SIGINT staff. The collection management requirements are more complex and the product quality bar is higher because the consumer is a COCOM staff, not a BCT CDR. The 352N warrant here builds strategic-level collection management experience faster than at the BCT level but at the cost of tactical immediacy.
  • 706th MI Group / NSA/CSS Fort Meade co-located seat
    You are working on a joint floor with NSA civilians, contractors, and joint-force elements. The mission is NSA-tasked; the product standards are IC-level; the daily interface is with GS-13 analysts and NSA senior civilian leadership. The Army rank structure matters for your administrative and career management functions; the technical floor does not care about rank. The 352N warrant on this floor either produces at the IC quality standard or is visible to NSA leadership as an Army warrant who did not make the transition from tactical to strategic SIGINT.
  • 780th MI Brigade / Cyber Mission Force SIGINT support seat
    The 780th MI Brigade at Fort Eisenhower is ARCYBER's organic MI formation — cyber-SIGINT integration, CMF support, the ARCYBER operational element. The 352N warrant in this environment works at the intersection of signals intelligence and cyberspace operations. The work is technically demanding, the clearance and access requirements are among the most stringent in the Army intelligence enterprise, and the billet produces the cross-domain SIGINT / cyber experience the most competitive CW3/CW4 packets show.

What Good Looks Like at This Rank

The good WO1/CW2 352N is the officer the S2 staff treats as a technical resource, not a management layer — which means the S2 brings the hard collection questions to the warrant before the staff meeting rather than after the brief goes sideways. The collection requirements the warrant manages get answered at a higher rate than the ones sent blind from the staff. The products leaving the element survive the next-echelon read. The senior NCOs in the section respect the warrant's ICD / doctrinal framework because the warrant also respects what twelve years of position time produces in a SFC who has been on the target. By the time the CW2 is positioning for the CW3 packet, the record shows two things: an analytic and collection management track that the OER narrative names in measurable terms, and a leadership track that shows the warrant learned how to carry an officer's accountability inside an enlisted-heavy technical workforce without either over-managing the NCOs or hiding behind them. The CDR's OER bullet uses the word 'trust.' That is the credential. The junior 352N warrant who builds that record at WO1/CW2 does not get there by being the smartest person in the SCIF. He gets there by being the most honest person in the collection-feasibility brief — including on the days when the honest answer means the CDR does not get the intelligence he asked for.

Preview — The Next Rank

At CW3 the role changes from executing collection management under an S2 officer's direction to advising the brigade or division G2 staff independently — which means the warrant is now the officer the two-star or one-star staff brings into the room when the SIGINT question is above the staff officer's technical range. That is a different accountability than supporting a battalion S2 captain. The product quality bar rises because the consumer is a COCOM J2 or NSA analytical element rather than a BCT CDR, and the collection architecture you manage covers more assets across a wider area of operations. The leadership load also shifts. At WO1/CW2 you mentored 35N NCOs from an adjacent-but-superior position. At CW3 you are mentoring WO1/CW2 warrants who are making the same transition you made — and you are the officer they call when they do not know if they have enough to brief the S2 or not. That mentorship is where the SIGINT warrant community's institutional knowledge actually lives. The thing CW2s are routinely surprised by at CW3 is the staff work volume — the briefings, the requirements documents, the formal assessments, the written advisories to O-5 and O-6 officers — that goes up the chain rather than staying inside the section. The CW3 is a staff officer as much as a technical expert, and the transition to thinking in staff-document terms (clarity, defensibility, decision-support framing) rather than section-product terms is the work of the first year at the new rank.
FAQ

352N WO1-CW2 — Frequently Asked Questions

Q01What does a WO1-CW2 352N (Signals Intelligence Analysis Technician) actually do?
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 (470t…
Q02What's the most important thing to know as a WO1-CW2 352N?
The SIGINT Warrant Basic Course at Fort Huachuca will teach you the collection management framework and the officer transition — but the first 90 days in your gaining unit will teach you whether you understand the difference between being a senior analyst and being a technical officer.
Q03What does a typical day look like for a WO1-CW2 352N?
Time-blocked day at the WO1-CW2 352N rank tier: 0530–0630 PT — unit formation or individual workout depending on the MI battalion's PT plan. The 352N warrant is an officer; the formation owns you on PT days, 0700–0730 Arrive at the SCIF. Badge in. Review overnight collection reports flagged by the duty officer or the section's on-call NCO. Note any product quality issues before the morning brief, 0730–0830 Morning intelligence update brief prep or attendance. BCT/DIV MI BN context: the S2 briefs the CDR at 0800 or 0900; the 352N warrant feeds the SIGINT paragraph,…
Q04What mistakes get WO1-CW2 352N soldiers fired or relieved?
OPSEC breach in or out of the SCIF — a geotag, a vague-but-identifiable social media post, a conversation on an unclassified line that describes a collection result. At this rank in this MOS, one OPSEC breach triggers an SCI access review, an AR 381-10 / AR 381-12 referral, and an OER narrative the CW3 board will read for the rest of the career; Financial misconduct or debt crisis without a command-level counseling.…
Q05What career decisions matter most at the WO1-CW2 352N rank tier?
Broaden tour now (NSA / CSS rotation, CMF seat, INSCOM element) vs. stay in the first assignment through CW2 promotion — The CW3 board reads two things: OER profile and career diversity. A WO1/CW2 who spends two years at the same BCT MI BN doing the same collection management job and a WO1/CW2 who does one year at the BCT and one year on a joint floor at Fort Meade with NSA civilians have produced different packets. The broadening is worth the turbulence if the billet produces a genuine technical challenge — not if it is just a different zip code for the same garrison routine.…
Q06What's next after WO1-CW2 for a 352N (Signals Intelligence Analysis Technician) in the Army?
At CW3 the role changes from executing collection management under an S2 officer's direction to advising the brigade or division G2 staff independently — which means the warrant is now the officer the two-star or one-star staff brings into the room when the SIGINT question is above the staff officer's technical range.
Q07What manuals and regulations does a WO1-CW2 352N need to know cold?
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).

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