←Back to CTT Cryptologic Technician (Technical) — overview, pay, training, civilian translation, reviews
CTTE6
Cryptologic Technician (Technical)
E-6 (Staff Sergeant) · Navy
HEADS UP
CTT1 (E-6) is the LPO seat — you write the eEVALs that pick the next NWAE slate, you own the division's analytic production and clearance posture, and the Chief board packet conversation is not abstract anymore. Making Chief in the CTT community is THE career milestone, and everything you do as CTT1 is building — or burning — that record. Get ahead of it on day one of the tour.
The Honest MOS Read
Cryptologic Technician Technical First Class Petty Officer (CTT1, E-6) is the senior petty officer and Leading Petty Officer entry tier in the rating — the first rank where the SIGINT technical community holds you accountable as a leader, not just an analyst. The CTT1 LPO seat at a NAVSECGRU command, a Fleet Cyber Command / NAVIFOR element, an NSA-affiliated site, or a deployed SIGINT support element is the anchor point the division uses to measure every junior petty officer. Your eEVALs pick the next NWAE slate. Your training plan decides whether the CTT2s and CTT3s behind you can run positions without your signature on every product. Your clearance management decides whether the division loses an analyst to a preventable investigation flag that no one followed up on.
The analytic work at CTT1 deepens in a specific way: you are no longer primarily a technical analyst who also supervises. You are the division's senior technical voice with an analytic production accountability that runs all the way to the command intelligence officer's brief. You produce finished ELINT and SIGINT technical reporting to ICD 203, ICD 206, and ICD 208 standards. You QA your CTT2s' products for analytic completeness before they route up. You own the section's quality posture the IC customer chain briefs from, and you carry the gap when the assessor identifies a pattern your section was generating.
The ICD 203 and ICD 206 standards are the production floor — analytic tradecraft, sourcing, characterization of uncertainty, and dissemination controls are not options you apply when convenient. They are the line the IC customer chain holds you to at every assessment. The CTT1 who produces above that line is the one whose eEVAL the LCPO doesn't rewrite. The one who treats them as compliance paperwork is the one the senior NSA technical liaison mentions in the assessment finding.
DoD 8140 / DoDM 8140.03 compliance is now yours to run at the division level. You audit the CTT2s' and CTT3s' work-role certifications, ensure the role mappings for your command's billets are current, and know the answer before the command's IAM asks the question. The CTT community's billets are evolving toward more formal 8140 alignment; the LPO who treats this as a checkbox is going to get caught short at an external assessment.
Making Chief is the organizing framework of the CTT1 career. The LCPO is watching your record from day one of the tour: eEVAL profile, production discipline, pipeline output — Warrant packets, LDO applications, senior-NEC assignments — and the one thing the goat locker notices before the eEVAL cycle opens, which is how you stand on the watch floor when you think no one senior is looking. The CTT community is small and the goat locker is smaller. The Chief board sees the full picture.
The Chief board conversation is not something you begin six months before the eEVAL close-out. Your LCPO should be reviewing your eEVAL profile, your awards record, your education trajectory (CCAF if not complete, college transcripts), your community involvement, and your pipeline contribution before the annual counseling cycle ends. The CTT1 who waits for the LCPO to start this conversation is the CTT1 who arrives at the board with a record that needed one more tour of deliberate preparation.
Career Arc
- 01Check in as CTT1 LPO: take ownership of the division's production output, training plan, DoD 8140 compliance posture, and clearance health — establish the standard within the first 60 days of the tour so the LCPO can predict your division's readiness before asking.
- 02First EVAL cycle: produce CTT2 and CTT3 eEVALs that name observable analytic behavior, production metrics, and NEC/certification status — specific and defensible so the LCPO can block-rank without revising every bullet.
- 03Year one: produce at least one NWAE-competitive output (CTT2 with a study plan on track, CTT3 with a CTT2 NWAE prep record that the LCPO knows about) and one career-development action (Warrant letter of endorsement, LDO app draft, senior-NEC application package, or NSA technical-staff referral).
- 04Mid-tour: audit DoD 8140 work-role compliance for the division; close gaps before the external assessment cycle opens; brief the status to the command's IAM without being asked.
- 05Year two / Chief board window: LCPO finalizing your eEVAL profile, awards record, community-involvement documentation, and education trajectory — the record should read clearly enough that the LCPO's senior rater can defend it in a selection board without the LCPO in the room.
- 06Senior-tour planning: LDO, Warrant, CMC-track, or senior-NEC assignment path chosen and first steps taken — the CTT1 who arrives at E-7 without a career path is the new Chief who arrives at the goat locker without a plan.
Common Screwups
- ×Briefing production or readiness numbers the LCPO catches as un-validated. One incident in the eEVAL cycle colors the entire Chief board record — and in the CTT community, the command intelligence officer hears about it in the same sync.
- ×A clearance or continuous-evaluation event — unreported foreign contact, financial trouble, relationship change — left to develop instead of being reported to the security officer on the timeline the policy requires. At CTT1 the investigation that started as an oversight becomes a suitability concern.
- ×OPSEC discipline gap in the CTT1's own conduct: personal device use near the SCIF entry point, social-media reference to work locations or assignment patterns, a liberty conversation that carries more operational awareness than it should. In a TS/SCI community the CTT1 who is the OPSEC problem is the worst possible version of that problem.
- ×Going around the LCPO to the command intelligence officer, the front office, or an NSA technical liaison to resolve a production or personnel dispute. The goat locker hears about it the same day. The Chief board sees the pattern.
- ×Waiting for the LCPO to initiate every Chief board preparation step. The CTT1 who walks into the first pre-board counseling without a draft of the board biography, an education transcript update, and a list of pipeline actions is the CTT1 whose LCPO has to do the work the petty officer was supposed to own.
A Day in the Life
- 0500-0600PT. In garrison the section runs together on Monday, Wednesday, and Friday; individual programs on Tuesday and Thursday. The CTT1 LPO who does not PT visible to the section is the LPO the section stops taking seriously for physical standards counselings. PT is also where you get the informal read on the junior petty officers — who looks off, who has something going on at home, who is in a financial hole.
- 0600-0730Hygiene, breakfast, change into working uniform. Check section email and the command watch log before walking into the section space. The overnight watch should have left a brief for the on-coming section LPO; if it is missing, that is the first counseling of the day.
- 0730-0800Section muster and accountability. Pass daily work priorities, remind the section of any upcoming milestones (NWAE window, certification renewals, training events), collect any personnel or readiness issues the CTT2s are surfacing. Brief the LCPO at the daily sync immediately after.
- 0800-1000Production review. QA the previous shift's or day's finished analytic products before they route up: ICD 203/206 compliance check, uncertainty characterization, sourcing adequacy, dissemination controls. Flag returns to the CTT2 who produced them with specific correction guidance, not red pen. The LPO who returns products without explanation trains junior petty officers who do not know what they did wrong.
- 1000-1130Training block or technical study. Three days a week the section holds an internal training period: collection and analytic technique review, new ICD or NAVADMIN read-through, DoD 8140 work-role certification prep, or NWAE study accountability for the CTT3 on the next advancement cycle. The LPO facilitates, does not lecture — the section is technical and will disengage from a one-way brief.
- 1130-1300Chow. Eat with the section when the operational tempo allows — the LPO who disappears to the chow hall alone is the LPO who learns about morale problems from the LCPO instead of from the section. The informal lunch conversation surfaces more readiness risk than any sensing session.
- 1300-1500eEVAL drafting or career-counseling appointments. The highest-leverage LPO work of the week happens here: eEVAL bullets drafted off the running observation log, career counseling for the CTT2 weighing re-up vs ETS, the NWAE study plan review with the CTT3, the Warrant or LDO packet discussion with the petty officer who has not yet decided to pursue it.
- 1500-1600LCPO sync. Report division production, readiness, personnel, and certification status. Surface any issues before the LCPO hears about them from the command intelligence officer. The LPO who surfaces the problem is the one the LCPO defends; the one who hides it is the one the LCPO cannot protect.
- 1600-1700Section closeout: end-of-day accountability, sensitive-access and SCIF security procedures confirmed complete, watch turnover brief reviewed before signing off. The CTT1 who leaves without confirming the watch turnover is the LPO whose name is on the security discrepancy the overnight watch discovers.
- After hoursChief board preparation. CCAF coursework if not complete, college courses if the education trajectory is part of the board strategy, community-involvement documentation, award write-up drafts for the section's recent contributions. The CTT1 who defers this to 'the next tour' is the one who arrives at the Chief board with a thin record.
Weekly Cadence
Monday through Wednesday the weight of the week falls on production QA and training execution — the section is on a collection or analytic production schedule that runs regardless of the day of the week, and the LPO's primary function from 0800 to 1100 is making sure the products going up are defensible. The training block on Tuesday or Wednesday is the deliberate counterweight: technical depth and analytic-standards reinforcement outside the pressure of the production quota.
Thursday is for personnel work: eEVAL drafting, career counseling appointments, DoD 8140 certification review, NWAE study accountability check-ins. The LCPO's weekly sync usually falls on Thursday afternoon; the LPO who arrives to that sync with a prepared status brief is the LPO the LCPO stops probing. The one who arrives with vague updates is the one who gets the additional oversight.
Friday closes the week on the readiness picture: clearance-posture review if there are any open items, certification status swept, end-of-week section formation, and any administrative closes the section carried from earlier in the week. Deployment cycle or field exercise weeks shift the entire rhythm — production intensifies, training compresses, and the LPO's job becomes prioritization under pressure rather than execution against a steady-state plan. The LPO who only functions under a garrison routine is not ready for the deployment cycle.
Key Skills — How to Drill Each
- 01Lead the division's analytic production: production quota ownership, QA review of CTT2 products, escalation of significant intelligence to the senior CTT and the reporting chain, and a clean shift handoff the duty officer does not rewrite.Build a section-level production checklist before your first shift as LPO — what goes up, who signs off, what threshold triggers an escalation, how the handoff is formatted. The CTT1 who improvises the QA standard produces inconsistent output; the one who standardizes it runs a predictable section the command intelligence officer can brief from without calling you first.
- 02Produce finished ELINT and SIGINT technical reports to ICD 203, ICD 206, and ICD 208 standards — source-cited, uncertainty characterized, dissemination controls applied, and analytically honest when the picture is incomplete.Read ICD 203 and ICD 206 cover to cover before your first LPO production review — not the summary, the full documents. The quality-of-information standards in ICD 203 and the analytic standards in ICD 206 are what the IC customer chain holds the report to; the CTT1 who has internalized them writes reports the senior NSA technical staff pass without redlines. The one who produces by feel produces products the assessor flags in the quarterly review.
- 03QA CTT2 and CTT3 analytic products for completeness, format, sourcing, and tradecraft discipline — identifying the gap constructively and in a way the junior petty officer can act on.Develop a three-point QA standard you use consistently: Is the analytic conclusion supported by the characterization? Are the uncertainty and the confidence level explicit? Are the sourcing and dissemination controls correct? Apply it before every product routes up. A CTT1 who reviews 'does it look right' is not running QA — the CTT2 who produced it was already doing that.
- 04Build and run a division training and certification plan: qualification timelines, NWAE study accountability for CTT3s, DoD 8140 work-role certification tracking, and clearance and continuous-evaluation posture for all three-to-six personnel in the section.Build the training plan in the first two weeks of the tour, present it to the LCPO for review, and then run against it. The plan should have named milestones — CTT3 qualified on position X by date Y, CTT2 BIB study log validated by the NWAE window, DoD 8140 certification renewed by the next external assessment cycle. A plan that exists only in conversation is not a plan the LCPO can defend when the assessor asks.
- 05Write CTT2 and CTT3 eEVALs that name observable analytic behavior, production metrics, and development actions — specific enough that the senior rater can block-rank without generalizing every bullet.Keep a running observation log from day one of the eval period — not 'CTT2 Jones performed well on watch' but 'CTT2 Jones produced 14 of 14 shift-reportable products at IC-standard quality across the evaluation period, including three products that resulted in new emitter characterization entries in the command database.' The eEVAL writes itself from the log; it does not write itself from memory in the last week of the period.
- 06Counsel a CTT2 or CTT3 honestly on career-path choices: NEC specialization, re-up vs ETS, joint-duty options, the technical expert track vs the leadership track, Warrant or LDO consideration, and the honest truth about what the CTT community's senior-billet landscape looks like.Know the current NAVADMIN for the CTT rating's NEC source-rating assignments, the current Warrant accession message for the CT community (verify against MyNavyHR before the counseling), and the current MILPERSMAN articles governing LDO/CWO eligibility. Counsel off the live cycle. The CTT1 who counsels off memory from what his chief told him four years ago is the one whose CTT2 misses a window.
Manuals & References — What Chapters Matter
- ICD 203 — Analytical StandardsThe production floor for every finished ELINT and SIGINT technical report your section generates. The QA standard for CTT2 products you review. Know the sourcing, uncertainty characterization, and confidence-level requirements in Chapter 4 before you brief the section's production posture to the command intelligence officer.
- ICD 206 — Sourcing Standards and Tradecraft Standards for Finished IntelligenceThe document the IC customer chain holds your reporting to at the technical-product level. The assessor's checklist at the quarterly IC assessment starts here. Your CTT2 QA standard should be ICD 206-calibrated, not LCPO-calibrated.
- ICD 208 — Specific Collection Program StandardsCollection-side standards that govern how the technical characterization is built and reported. The ICD 208 framework is what separates a defensible ELINT report from one the NSA technical reviewer returns for rework. Read the applicable annexes for the collection types your section works.
- OPNAVINST 2201.3 — Cryptologic and Signals Intelligence ActivitiesThe Navy SIGINT coordination instruction your command operates under. The CTT1 who can cite OPNAVINST 2201.3 in the command intelligence officer's brief is the LPO the command intelligence officer trusts. The one who has not read it is the LPO who gets caught unprepared when a coordination question surfaces.
- DoDM 8140.03 — Cyberspace Workforce Qualification and Management ProgramThe work-role framework your section's billets are mapped to. Your division-level DoD 8140 compliance audit starts with this document. Verify the current work-role mappings for CTT billets with your command's IAM — the mappings are evolving and the version your predecessor briefed may be out of date.
- NAVPERS 18068 Vol II — Manual of Navy Enlisted Manpower and Personnel Classifications and Occupational StandardsThe NEC catalog for the CTT rating and the source-rating occupational standards your NWAE is built on. Pull the current CTT-series NEC entries and the current source-rating NAVADMIN before any career counseling or NEC-assignment conversation. The catalog updates; the version in your predecessor's binder may not reflect the current assignment paths.
- MILPERSMAN — Articles governing advancement, eEVAL, retention, NJP, and separationFluency in the relevant MILPERSMAN articles separates the LPO from the senior petty officer. You are writing eEVALs, initiating counselings, and managing retention actions. The CTT1 who reads MILPERSMAN only when something goes wrong is the LPO who makes procedural errors under pressure.
Standards — How to Hit Each
- Chief board packet tracking: eEVAL profile, awards record, education trajectory, community involvement, and pipeline contribution — LCPO reviewing the record against board standards before the annual counseling cycle closes.Request a pre-board record review with the LCPO at the six-month and twelve-month marks of the tour — bring your own assessment before the LCPO gives his. The CTT1 who arrives with a self-assessment is the CTT1 whose LCPO spends the session on refinement instead of diagnosis.
- Division production output at or above the command's section average — production quota met, QA findings minimal, IC customer-chain returns infrequent.Track the section's production metrics against the command's baseline from the first week of the tour. If you do not know the command's production benchmark, ask the LCPO in the first week's counseling. The LPO who cannot characterize the section's production posture is the LPO the command intelligence officer cannot brief from.
- DoD 8140 work-role compliance clean across the division — no position uncovered because a certification lapsed during the tour.Build the certification renewal calendar into the training plan from day one. Set a 60-day lead-time flag for every expiring certification. A lapsed certification discovered at the external assessment is a LPO-level finding, not a CTT2-level finding.
- Pipeline output: at least one Warrant, LDO/CWO, senior-NEC, or NWAE-advance action per year from the section — LCPO can name the Sailor and the status.Identify the pipeline candidates in the first 30 days of the tour. One CTT2 on the NWAE study plan with logged progress. One CTT3 with a re-enlistment counseling on record that names the NEC path. One LDO or Warrant conversation had in writing. The pipeline does not maintain itself.
- Clearance and continuous-evaluation posture clean across the division — no position lost to a preventable investigation flag, no junior parked off a seat during the tour because a foreign contact or financial change was not reported.Run a clearance-posture review with the section at the start of the tour and at the six-month mark — not a lecture, a conversation. Ask the questions the security officer will ask. The CTT1 who surfaces the issue in the conversation is the LPO who prevented the investigation. The one who avoids the conversation finds out at the worst moment.
Technical Mistakes — Concrete Consequences
- Briefing production or readiness numbers that the command intelligence officer catches as unvalidated or padded.One incident of an unsupported brief is a trust deficit with the command intelligence officer that takes a full tour to rebuild — and in the CTT community, the command intelligence officer's read on the LPO travels to the eEVAL chain before the next cycle closes.
- Submitting a CTT2 analytic product with a traceable gap that you passed through QA without catching.When the NSA technical reviewer or the IC customer chain returns the product for rework, the LPO's QA signature is on the routing. The LCPO asks one question: did you actually review it? The answer is already visible in the product.
- Letting the CTT3's NWAE study plan exist only in a verbal conversation with no record.When the NWAE results come back and the CTT3 did not advance, the LPO is the one without documentation that the counseling happened, the study plan was created, and the Sailor was given the tools. The LCPO cannot defend you at the retention counseling if there is no paper trail.
- Bypassing the LCPO to take a production concern or a personnel issue directly to the command intelligence officer or the front office.The goat locker hears about it that day. The command intelligence officer's respect for the LCPO drops by association. The LPO who went around the chain is the one the Chief board reads as not ready for the mess.
- Letting a DoD 8140 work-role certification lapse in the division because the CTT2 'was going to renew it next month.'The external assessment cycle finds an uncertified position. The finding is attributed to the LPO. The CTT2 gets counseled; the LPO gets the billet-readiness finding. In the CTT community a compliance gap at the LPO level reads as a leadership gap, not an administrative oversight.
Career Decisions at This Rank
- Chief board pursuit: invest fully in the current tour's record vs take a lateral-transfer or geographic preference request that is good for life but hurts the board profile.The Chief board for CTT rates on the totality of the service record — eEVAL profile, production output (even at one command), education, community involvement, and the senior-rater write-up that either defends the record or damns it with faint praise. A billet change that takes you to a command where the LCPO is less invested in building the record, or where the production posture is weaker, costs more than the geographic convenience gains. If the current tour is in the board window, stay put and build the record. The board does not reward comfortable choices.
- LDO / CWO (CW2 / LDO O-1) application: pursue a commission or continue as a senior technical enlisted.The LDO / CWO path from CTT1 is viable and the IC community values the warrant officer and limited duty officer tier in technical SIGINT billets. The honest calculus: LDO and CWO routes each have their own annual board, eligibility windows, and community needs. Verify the current accession message against MyNavyHR before making the decision — community needs drive selection rates more than individual records in some years. If the record is strong and the timing is right, it is worth the packet. If the Chief board is the higher-probability path in the current cycle, that is also an honest answer.
- Senior-NEC specialization: pursue a specific CTT NEC that deepens technical specialization vs remain broadly qualified and compete for a wider range of billets.The CTT NEC structure within the community creates lanes — deeper technical specialization opens senior-analyst and senior-technical-expert billets at NSA-affiliated commands and in joint IC assignments that are not accessible without the NEC. The tradeoff is billet flexibility: a highly specialized NEC produces a narrower assignment footprint. The right answer depends on whether the career goal is the Chief board with broad-base appeal or a senior technical expert track with a defined IC role. Discuss with the LCPO and the detailer at the next sea-duty planning cycle.
- Re-enlistment or extension: plan the SRB window, sea-shore rotation timing, and next billet type for the post-CTT1 tour.At CTT1 the selective reenlistment bonus (SRB) conversation is governed by the current NAVADMIN for the CTT rating — pull it from MyNavyHR and verify the current zones and multipliers before signing anything. The billet sequencing question is separate: the next tour after CTT1 should be one that either broadens the record (joint duty, NSA staff, a technical exchange billet) or cements the Chief board record with a second strong LCPO eEVAL profile. The detailer operates on community needs, but the CTT1 who arrives at the conversation with a prepared argument for a specific billet type gets better outcomes than the one who accepts whatever is open.
- Post-service planning: begin the cleared contractor or federal civilian market conversation before the 20-year mark is visible on the horizon.A CTT1 with an active TS/SCI with CI polygraph, a career of SIGINT technical production at an NSA-affiliated command, and a clean security record is in the top tier of the cleared contractor and federal civilian hire market — NSA civilian career service, DIA, DISA, and the major IC integrators (Booz Allen Hamilton, SAIC, Leidos, CACI, Peraton, ManTech, Northrop Grumman Mission Systems) all have specific CTT-lineage roles that pay well above the E-6 pay table from day one. Begin building the network — LinkedIn with appropriate security hygiene, informational conversations with separated CTT community members, JVSG counselor contact — at least three to five years before the anticipated transition date.
How the Seat Varies by Unit Type
- NAVSECGRU command or Navy cryptologic unit (NCU) afloat or ashoreThe classic CTT1 LPO billet — SIGINT technical division at a dedicated cryptologic command. Production quotas, IC assessment cycles, and NSA liaison relationships are the weekly rhythm. The section is technically specialized and the pace is analytic, not operational in the surface-warfare sense. The downside: a narrow peer group and limited visibility into the broader Navy culture, which can make the goat locker transition to the Chief's mess feel culturally abrupt if the CTT1 has never served outside the cryptologic community.
- Fleet Cyber Command / NAVIFOR element or joint IC command (Fort Meade area, NSA Hawaii, NSA Georgia)The joint IC environment at Fort Meade or one of the regional cryptologic centers is a different operational texture — larger command, more NSA-adjacent work, more joint-duty visibility, and a higher density of senior IC professionals in the workspace. The CTT1 LPO here is more likely to be working directly alongside GS-13 and GS-14 NSA civilians and joint personnel from the Army and Air Force cryptologic communities. The post-Navy market connections built in this environment are qualitatively better than those built at a smaller afloat unit.
- Deployed SIGINT support element (joint task force, combatant command, forward-deployed support)Deployment as a SIGINT technical section LPO is an accelerated record-builder — the eEVAL environment is more consequential, the production is real-world, and the Chief board record from a deployment cycle is typically stronger than the equivalent garrison eEVAL profile. The operational tempo is demanding and the section support infrastructure is leaner. The LPO who performs well in a deployed environment is the LPO whose Chief board record the LCPO defends without prompting.
- NSA-affiliated senior technical staff or technical exchange billetThe NSA technical staff billet as a CTT1 is relatively rare but exists for senior technical analysts with specific NEC qualifications and a record that supports selection. The work is analytic and advisory rather than watch-floor production — you are contributing to production standards, assessment methodology, or technical-collection design at the community level. The post-service NSA civil service path is a direct line from this billet type; the command intelligence officer relationship is replaced by a GS-14 or GS-15 branch chief relationship that can translate directly to a post-Navy offer.
What Good Looks Like at This Rank
The good CTT1 LPO runs a section the LCPO checks in on once a week — not because it needs supervision, but because the goat locker wants to know what the section is doing so they can credit it in the right forum. The production numbers are above the command average. The CTT3s are advancing on schedule. The clearance posture is clean. The DoD 8140 work-role certifications are current. And the LCPO already knows the answer to every question the command intelligence officer is going to ask in the next sync.
What separates the CTT1 at the top of the slate from the one in the middle is specificity: specific eEVAL bullets, specific production metrics, specific pipeline actions, specific dates on which specific counselings happened. The eEVAL profile reads as a record assembled by someone who was paying attention every day, not someone who reconstructed the year from memory in the last week of the period.
The Chief board record for the top CTT1 candidate reads like a section leader who produced operational output, built the next generation of operators, held the line on security and OPSEC discipline, and mentored at least one Sailor into a better outcome than that Sailor would have found on their own. The goat locker does not debate that record. They defend it.
Preview — The Next Rank
Making Chief changes more about the job than any other promotion in the rating. At CTT1 you are the LPO — the senior petty officer the LCPO tasks, the production voice the command intelligence officer verifies, and the career developer whose pipeline output is measured in NWAE slots and warrant packets. At CTTC you are a Chief — which means the goat locker is your peer institution, the command intelligence officer asks you by name, and the entire division reads the analytic standard off how you stand on the watch floor.
The Chief's mess is not a social club. It is a working leadership platform with its own accountability structure — CPO 365 guidance, the CPO Initiation process, and the culture of the goat locker that enforces the enlisted standard before the wardroom has to. The new Chief who treats the mess as a perk misses the entire point of what Making Chief means in the Navy's culture. The CTT community's chiefs sit at the command intelligence sync as the senior enlisted SIGINT technical voice; the anchor means the wardroom credits your judgment before you have briefed the result.
The technical standard does not go away. The Chief who made his anchor by producing analytically honest work and then stops studying is the Chief whose division falls behind the IC standard inside the first assessment cycle. The CTT community's senior enlisted are the technical backbone of the Navy's SIGINT production posture — the Chief is where that backbone either holds or bends.
FAQ
CTT E6 — Frequently Asked Questions
Q01What does a E6 CTT (Cryptologic Technician (Technical)) actually do?
You are LPO of a SIGINT technical division or a senior analytic cell at a NAVSECGRU command, a Fleet Cyber Command / NAVIFOR element, an NSA-affiliated site, or a deployed SIGINT support element.
Q02What's the most important thing to know as a E6 CTT?
CTT1 (E-6) is the LPO seat — you write the eEVALs that pick the next NWAE slate, you own the division's analytic production and clearance posture, and the Chief board packet conversation is not abstract anymore.
Q03What does a typical day look like for a E6 CTT?
Time-blocked day at the E6 CTT rank tier: 0500-0600 PT. In garrison the section runs together on Monday, Wednesday, and Friday; individual programs on Tuesday and Thursday. The CTT1 LPO who does not PT visible to the section is the LPO the section stops taking seriously for physical standards counselings. PT is also where you get the informal read on the junior petty officers — who looks off, who has something going on at home, who is in a financial hole, 0600-0730 Hygiene, breakfast, change into working uniform.…
Q04What mistakes get E6 CTT soldiers fired or relieved?
Briefing production or readiness numbers the LCPO catches as un-validated. One incident in the eEVAL cycle colors the entire Chief board record — and in the CTT community, the command intelligence officer hears about it in the same sync; A clearance or continuous-evaluation event — unreported foreign contact, financial trouble, relationship change — left to develop instead of being reported to the security officer on the timeline the policy requires.…
Q05What career decisions matter most at the E6 CTT rank tier?
Chief board pursuit: invest fully in the current tour's record vs take a lateral-transfer or geographic preference request that is good for life but hurts the board profile — The Chief board for CTT rates on the totality of the service record — eEVAL profile, production output (even at one command), education, community involvement, and the senior-rater write-up that either defends the record or damns it with faint praise. A billet change that takes you to a command where the LCPO is less invested in building the record, or where the production posture is weaker,…
Q06What's next after E6 for a CTT (Cryptologic Technician (Technical)) in the Navy?
Making Chief changes more about the job than any other promotion in the rating.
Q07What manuals and regulations does a E6 CTT need to know cold?
ICD 203, 206, 208 — you defend the division's production against these standards at every IC customer review.; OPNAVINST 2201.3 — Navy SIGINT / EW coordination instruction; you are the technical voice the command intelligence officer cites.; DoDI 8500.01 — Cybersecurity; DoDM 8140.03 — Cyberspace Workforce Qualification (you audit the division's compliance against the current work-role mapping).
Based on 14 tips from 0 contributors
Published by the Honest MOS Editorial DeskVerified against DoD/.gov sourcesUpdated May 2026Editorial standards