Skip to main content
HonestMOS
●InvestigationsHow EUCOM shelved a tax break for 9,000 troops in Poland — for five years.→
←Back to CTI Cryptologic Technician (Interpretive) — overview, pay, training, civilian translation, reviews
CTIE6

Cryptologic Technician (Interpretive)

E-6 (Staff Sergeant) · Navy

E1–E3E-4E-5E-6E-7E8–E9
HEADS UP

CTI1 (E-6) is the last rank where your record gets built before the Chief board reads it. The CTIC selection rate is real and the community is small — there is no anonymous middle of the pack. Your DLPT score, your eEVAL trait average, your division's production quality, and your IC community accession output are all visible to the senior CTIs who sit on the board. The CTI1 who treats this tour as a management job rather than a high-performance LPO run is the one the Chief board reads as a 'not this cycle.' Fix that narrative before it gets written.

The Honest MOS Read
Petty Officer First Class CTI (CTI1, E-6) is the last rank before the anchors, and in the CTI community that means the last chance to build the record that the CTIC board will read. You are the Lead Petty Officer of a language section or a CTI division — running eight to twenty CTIs at a Naval Security Group Activity (NAVSECGRU), a joint IC site, an NSA-affiliated command, or a deployed SIGINT element depending on where the orders dropped. You own four to six eEVALs per cycle that will determine who makes the next NWAE advancement slate and, eventually, who sits in front of the Chief board alongside you. The practical weight of the seat falls into three buckets that consume every working hour. First, language proficiency. Every CTI in your division has a DLPT cycle, and you own the sustainment program — the study schedule, the remediation triggers, the reporting to the department head when someone is trending the wrong direction. Your own DLPT score is still a personnel record entry and the Chief board reads it. The CTI1 LPO whose personal scores have drifted while the division's scores are propped up by the CTI3 who has been at DLI for nine months is not hiding anything — the community sees the delta. Second, production quality. You are the senior linguist in the section, which means the hard collection, the time-sensitive reporting, and the IC community liaison relationship are your calls. The CTI2s are handling the production shift; you are handling the calls that come in when the shift changes and the collection doesn't. You write the finished intelligence products and the ICD 203-compliant translation summaries that the department head signs off on without picking up a red pen. When an IC community customer calls the command to ask a question about a product, the call comes to you. Third, the Chief packet. The CTIC board reads your record front to back, and your LCPO is editing it now — every eEVAL trait, every collateral duty, every award write-up, every production metric cited by name. The CTI1 who builds this record in the background — warfare device current, IC community accession output running, section language scores on trend — is the one the board can defend without making a speech. The CTI1 who calls the LCPO three months before the board asking what needs to be cleaned up has already lost the cycle. The IC community liaison relationship is the most undervalued part of the LPO seat. The NSA or DIA representatives who deal with your command are watching how the CTI1 handles IC product quality, handles correction requests, handles the community inspection prep. The senior CTI retirees and GS-level civilians in the IC contractor world are a network that crosses every command the CTI community touches. The CTI1 who builds that relationship professionally — not just when he needs a reference, but as a running professional habit — is the one who gets the GS-13 call when the uniform comes off.
Career Arc
  • 01CTI1 pin-on via NWAE advancement selection; LCPO designation at a Naval Security Group Activity, joint IC site, or NSA-affiliated command.
  • 02First full DLPT sustainment cycle as section LPO — establish proficiency baselines for every CTI, every language; initiate remediation for anyone below the command floor.
  • 03First round of CTI2 and CTI3 eEVALs as primary rater — measurable production metrics, language scores, named IC products; the trait average drives the next NWAE slate.
  • 04IC community accession — Warrant application, LDO package, NSA civil-service nomination, commissioning program, or all-source/collection-management conversion for at least one Sailor per tour.
  • 05Chief board packet under LCPO editorial control — warfare device pinned and current, eEVAL profile defensible, production and proficiency brief with no caveats, collateral duty portfolio complete.
  • 06CTIC selection board result — if the record is there, this is the tour where it reads. If it is not, the LCPO delivers an honest accounting of the gap before the next cycle.
Common Screwups
  • ×DUI, NJP, or fraternization as an LPO — this ends the career in a small community where the record travels nationally. There is no 'back to the lower-visibility billet' in the CTI world.
  • ×eEVAL fraud — inflating production metrics or language scores in a rated Sailor's record to avoid a difficult counseling. When the discrepancy surfaces at the next command, the writer's name is on the bullet and the Chief board knows the LPO who could not write an honest evaluation.
  • ×OPSEC breach — posting, stating, or implying classified collection details, specific billet context, or compartment designations in any personal communication, social media, or networking forum. The community is small and the polygraph will find the inconsistency.
  • ×Clearance hygiene failure — unreported foreign contact, undisclosed financial distress, unacknowledged foreign travel. The CTI community is access-dependent from the SR to the CTICM; one adjudication hold removes you from the mission and the hole does not stay unfilled.
  • ×Going around the LCPO to the IC community liaison, department head, or CO to advance a personal career agenda. The CTI community is not large enough for this to stay private.

A Day in the Life

  • 0500-0545Wake. Check secure messaging for overnight section issues — DLPT cycle notification, clearance-related action from the security office, IC community tasking message. PT gear on.
  • 0545-0700PT with the division. Wednesday command PT run, Thursday independent. Note who is showing up, who is not, who looks like they need a counseling about something that is not fitness.
  • 0700-0730Shower and change. Review the day's production schedule, DLPT cycle calendar, and any IC community tasking that dropped overnight.
  • 0730-0800Morning quarters. Read the command plan for the day. Pass any IC community priority shifts to the CTI2 shift leads. Follow up on any counseling actions from the prior day.
  • 0800-0900DLPT sustainment check-in — review the week's study log submissions, flag anyone behind on the schedule. If a score is trending below the command floor, the remediation conversation happens this morning, not next week.
  • 0900-1130Senior linguist production work — hard-collection shift, IC product QA review of CTI2 drafts, or IC community liaison call depending on the day's tasking. If it is a QA day, read every draft against ICD 203 before signature.
  • 1130-1200Lunch. Eat with the section occasionally — not every day, but enough to know what the temperature is before the department head asks.
  • 1200-1330Administrative window — eEVAL drafting, career counseling schedule, DLPT sustainment log update, Chief packet documentation.
  • 1330-1500Department-head prep or IC community sync depending on the week's battle rhythm. Brief your own numbers — do not send a CTI2 to brief the DH on section production data.
  • 1500-1600Career counseling appointments with CTI2s and CTI3s — NEC path, Warrant packet timeline, NWAE BIB review, re-up vs ETS conversation. One real conversation per day beats six surface-level check-ins per week.
  • 1600-1700End-of-day section check — watch turnover supervised, any overnight IC tasking read, DLPT remediation update.
  • 1700-2000Off base. Target-language media — news in the primary language, structured review against current DLPT vocabulary domains, or DLI-structured sustainment materials. The LPO whose personal language does not degrade is the one doing this three to four nights a week.
  • 2000-2200eEVAL drafting or Chief packet documentation if the admin calendar is behind. The CTI1 who does this on the ship's time and never takes it home has probably not been doing it.

Weekly Cadence

Monday is planning and accountability. Pull the DLPT sustainment log, review the IC community tasking matrix for the week, check the production schedule for conflicts with DLPT cycle dates, and confirm the eEVAL draft timeline with your CTI2s. The week starts with the LPO knowing the section's proficiency and production posture cold — not learning it when the DH asks. Midweek is the production and QA peak. Wednesday and Thursday carry the bulk of the IC product review load, the IC community liaison calls, and the career counseling appointments. The senior linguist production work — the hard collection, the time-sensitive reporting — happens here too. The LPO who clears his schedule to brief the DH but has not reviewed the CTI2's product before it goes to the department head has mixed up his priorities. Friday is debrief and prep. Read the week's production output against the IC community tasking matrix, document what was completed and what rolled forward, update the DLPT sustainment log, and brief the LCPO on section status before the weekend. The CTI1 whose LCPO gets a Friday status report with no caveats is the one whose packet is being built the right way.

Key Skills — How to Drill Each

  1. 01
    Run a division-level DLPT sustainment and proficiency program — every CTI, every language, every cycle, with scores tracked and remediation initiated before the lapse becomes a production gap.
    Build the sustainment log in a spreadsheet with DLPT cycle dates, current scores, next-due dates, and a remediation flag that triggers at a defined threshold below the command floor. Brief the department head monthly — not when a score drops, but on schedule. The LPO who surprises the DH with a proficiency lapse is the one who was not tracking; the LPO who briefs the lapse with a remediation timeline and a return-to-standard date is the one the DH trusts.
  2. 02
    Defend the division's production output, language proficiency posture, and IC community reporting quality at department-head sync — own the gap, present the closure plan, name the milestone.
    Prepare the brief yourself, not a CTI2's slide deck. Know the production numbers cold — reports completed, QA failure rate, IC community return rate, reportable collection periods. Own every gap with a two-line closure plan before the DH asks. The LPO who does not know his own numbers in a meeting with the DH has sent a message about how the section is being run.
  3. 03
    Write eEVALs on CTI2s and CTI3s that the senior rater can defend at a wardroom-level board — measurable production outcomes, language scores, analytic contribution, named IC products.
    The eEVAL bullet is specific: 'Produced 47 finished SIGINT reports in the reporting period; zero IC community return requests; DLPT scores maintained at 2+/2+ across the rating period; identified collection gaps that the command's reporting plan incorporated for the next reporting cycle.' That is a defensible EP bullet. 'Performed duties in a superior manner' is not. Write the bullet you would want in your own record and test it against whether the senior rater can defend it at the wardroom board without adding adjectives.
  4. 04
    Operate as the senior CTI on a real collection or reporting requirement — the call to the front office at 0200 when the intelligence is time-sensitive is your call, not the CTI2's.
    Walk the escalation decision tree with your CTI2s before it matters: what rises to the LPO, what rises to the department head, what rises to the command duty officer. Drill it in daily watch briefs. When the 0200 call comes, the response is clean because the decision criteria were established in the planning phase, not improvised in the moment.
  5. 05
    Mentor a CTI2's NEC, Warrant, commissioning, or community-accession packet from idea to selection — and counsel honestly when the path is wrong for the Sailor.
    Know the current CTI NEC codes in NAVPERS 18068 and the current source-rating NAVADMIN before the conversation. Know the Warrant Officer accession timeline for the cryptologic designator, the LDO application cycle, the NSA civil-service hiring season, and the commissioning program windows. The CTI1 who can quote those timelines from memory is the one the CTI2 brings his career questions to; the LPO who says 'check MyNavyHR' loses that Sailor to a senior chief at the next command.
  6. 06
    Translate IC community priorities and SIGINT collection guidance into section-level tasking the CTI2s can execute without the wardroom having to re-explain the mission.
    At each production cycle, brief the CTI2s on the IC community priority tasking and how it maps to the collection your command is servicing. Not the classified specifics — the mission framing that lets the CTI2 make a correct triage call when two collection opportunities compete for the same analyst hour. The CTI1 whose CTI2s always need the DH to explain the mission has not been doing that framing work.

Manuals & References — What Chapters Matter

  • ICD 203 — Analytic Standards (ODNI); ICD 206 — Sourcing Requirements for Disseminated Analytic Products; ICD 208 — Write for Maximum Utility.
    These are the production standards your section's IC products live or die on. As LPO you are the last QA check before the product goes up the chain. ICD 203 governs analytic tradecraft — what constitutes proper sourcing, confidence language, and alternative analysis. ICD 206 governs how source attribution works. ICD 208 governs format and readability for IC customers. The CTI1 who can cite the specific tradecraft failure — 'that is an ICD 203 section 4.3 violation, the confidence statement is not supported by the sourcing' — is the one the IC community takes seriously.
  • NAVPERS 18068 Vol II — Manual of Navy Enlisted Manpower and Personnel Classifications (NEC catalog; CTI-series NEC entries and current source-rating NAVADMIN).
    The NEC structure is the career-path map for every CTI in your division. The language-specific NEC tied to each Sailor's DLPT history is what the detailer uses to build the community assignment pipeline. Pull the current edition before every career counseling conversation — the NEC codes change and the Sailor who gets counseled off an outdated version of the path makes the wrong decision.
  • OPNAVINST 1306.2 series — Navy Detailing / Assignment Policy.
    The CTI community is small and the assignment market is visible to anyone paying attention. Know what the detailer's current fill priorities are before your Sailors ask about orders. The CTI1 who can tell a CTI2 honestly — 'the community needs Arabic-capable CTIs at NAVSECGRU Pearl right now, here is the window and here is the billet type' — saves that Sailor from a lateral assignment that misses the promotion window.
  • DLIFLC sustainment framework and current DLPT proficiency requirements for your language community (verify via CIVT / DLI website before quoting).
    The DLI graduation standard and the operational proficiency floor are different numbers. Your sustainment program is built around the operational floor — the minimum DLPT score the command requires for production assignment — not the graduation score the Sailor arrived with. Brief the gap to every new accession at check-in so the remediation schedule is established before the first DLPT cycle.
  • MILPERSMAN — Manual of the Judge Advocate General; sections governing enlisted advancement, NJP, separation, and retention.
    You are the LPO in the room when the command acts on any of these against a CTI under your authority. Know the MILPERSMAN articles for NJP procedures, enlisted separation categories, and the advancement process before you need them — not the night before the Captain's Mast.
  • SECNAVINST 5239 series — Information Security; command-level TS/SCI and compartmented access management policies.
    The security officer briefs you before they brief anyone else in the section because you own the access posture of the entire CTI division. Know which CTI is in adjudication, which accesses are pending, and which compartments are relevant to the current mission — and report changes to the security officer proactively, not reactively.

Standards — How to Hit Each

  • Chief board packet under construction with the LCPO's eye on every line; eEVAL trait average defensible at wardroom level; warfare device pinned and current.
    Schedule a quarterly sit-down with your LCPO specifically on the Chief packet — not the daily battle rhythm, the strategic record read. Walk through every trait in your last three eEVALs, the collateral duty portfolio, the award write-up timeline, and the IC community accession count. The CTI1 who waits for the LCPO to initiate that conversation is the one who gets to the board cycle with a record that could have been better.
  • Division-level DLPT scores at or above command average for every language, every cycle — no caveat accepted at department-head brief.
    The no-caveat standard means every lapse is remediated before the brief, not disclosed at the brief. When a score drops, you have a remediation plan running before the next cycle date — DLI-structured review materials, a study partner assigned from within the section, a check-in schedule. The department head does not want to hear about the problem; they want to hear about the solution that is already running.
  • Production and reporting quality defensible at department head and CO level — zero IC-reportable errors in finished product that trace back to your section's QA.
    The QA gate is not a post-production review — it is built into every step of the production process. Every CTI2 drafts, you review against ICD 203 and ICD 208 before signature, and the product leaves the section with your name attached. If the IC community calls back with a correction, the post-mortem lives in your training log and the CTI2 who wrote the error is counseled with a specific tradecraft note — not a generic 'do better.'
  • Pipeline output — at least one NEC, Warrant, LDO, commissioning, or IC community accession selectee per year from your division.
    One selectee per year is not a quota — it is the evidence that you are actually running the career counseling conversations that the spec requires. If you finish a calendar year with no accessions from a division of eight to twenty CTIs, you either have a pipeline problem or a counseling problem. Both are attributable.
  • NWAE for Chief selection replaced by Chief board packet submission; packet built across the year, not the week before submission.
    The week-before submission panic is a signal the packet was not built across the year. The documentation for each collateral duty, award write-up, production metric, and IC community accession should already be in your working folder before the submission window opens. If something is missing at that point, it probably cannot be retroactively created credibly.

Technical Mistakes — Concrete Consequences

  • Briefing DLPT scores or production numbers you have not personally validated.
    The department head catches the discrepancy in the next readiness brief — IC community return rate higher than your section number, or a DLPT score the community database shows as six months past due. The CTI1 who owns unvalidated numbers at a department-head sync has told the wardroom something about how the section is being run, and the Chief board eventually hears the same story.
  • Letting a CTI2 carry the IC community liaison relationship because 'he is your LPO's pick' or 'he knows the customer better than I do.'
    When the CTI2 transfers, the relationship gap is visible inside the first IC community sync, and the senior CTI network's memory of how the gap happened is longer than the tour. The relationship belongs at the LPO level and the CTI2 may assist — not the reverse.
  • Confusing seniority with current language depth and letting personal DLPT preparation slip while managing the section.
    The junior CTI on a hard-collection shift will out-perform the LPO on current-language tasks, and the front office will notice before the next DLPT cycle confirms it. In a community where personal proficiency is the core technical credential, an LPO whose language has atrophied has undermined his own authority as the section's senior technical voice.
  • Going around the LCPO to the NSA or IC liaison, the department head, or the CO on a production, career, or personal grievance.
    The CTI and CT community is small enough that the LCPO hears about it the same day it happens, and the senior CTIs across the community hear about it within the week. The Chief board reads a record; the senior CTI network shares a reputation. Both are real.
  • Treating the IC community accession mentoring conversations as a checkbox that gets run once near transfer.
    The CTI who needed an honest accession conversation in year one of the tour gets the one in year three — which is too late for a Warrant packet that requires 18 months of application prep. The LPO's name is on the missed window.

Career Decisions at This Rank

  • Chief board timing — go hard on the current cycle or wait for a stronger record?
    The CTI community is small enough that the senior CTIs know every CTI1 who is competitive before the board convenes. If your LCPO is building your packet with confidence — language scores on trend, eEVAL profile strong, production metrics named, IC community accession output running — go hard on the current cycle. If the packet has gaps that are fixable in six months, an honest conversation with the LCPO about whether this cycle is the right cycle is worth more than a weak first look. A 'not this cycle' is recoverable in a small community where everyone knows why; a weak first look with gaps that were avoidable is a different story.
  • IC community tour — NSA billet, DIA assignment, joint IC site — vs staying in the fleet CTI track?
    The IC community tour at CTI1 is the most consequential assignment decision in the rate short of Making Chief. An NSA or DIA billet at this rank puts your name in front of the IC senior staff, builds the clearance and access profile that opens senior billets, and creates the post-Navy contractor and civil-service network that pays for itself inside three years of retirement. The fleet track is also valid — a NAVSECGRU tour in a operationally active region is a legitimate production-and-leadership record. The question is which billet the community needs at the moment of your orders, and which one your LCPO and the detailer think supports your record best.
  • Warrant Officer accession (CWO — cryptologic community designator) vs staying the enlisted CTI path to Master Chief?
    The Warrant path in the cryptologic community is a real option and the CTI1 window is the right window to apply. The Warrant trades the Chief board runway for a technical officer commission — smaller community, narrower promotion track, but direct access to senior IC staff and the ability to stay in a technical production role rather than moving into the full-time management role that the senior enlisted track requires after CTIC. The CTI1 who is a world-class linguist and analyst but dislikes the administrative weight of the LPO seat should seriously weigh this. The CTI1 who is drawn to the climate-and-retention side of leadership should stay the enlisted path. Verify the current cryptologic Warrant designator via MILPERSMAN before filing the application — the program details change and the window is tight.
  • Career-broadening tour — recruiter, Navy Career Counselor, CPO Academy cadre, DLI instructor — vs staying in the production community?
    A career-broadening tour at CTI1 is a calculated bet. It generates a different kind of eEVAL bullet — one that demonstrates leadership breadth and mentoring output rather than IC production metrics. The LCPO who reviews it can make it work for the Chief packet if the production record from the prior tour is strong. The risk is that two years out of the IC production community means two years of language sustainment without the daily operational context that keeps the language operational rather than just test-current. The CTI1 who goes to a career-broadening tour must have a disciplined personal language-sustainment plan that survives the tour.
  • Re-enlistment extension vs HYT (High Year Tenure) planning for the E-7 promotion window?
    HYT for E-7 is a real planning constraint in a small community with a long promotion timeline. Know your HYT date, know the CTI community's historical CTIC selection rate (pull from BUPERS/NETC NWAE data rather than relying on rumor), and have an honest conversation with your LCPO about whether your record is Chief-board-competitive before the extension decision. The CTI1 who extends without an honest assessment and then does not select leaves the service with a truncated transition window.

How the Seat Varies by Unit Type

  • Naval Security Group Activity (NAVSECGRU) / Navy Information Operations Command (NIOC)
    The core CTI billet. Production-focused, language-intensive, direct SIGINT collection and reporting environment. The DLPT currency pressure is immediate and visible — the senior CTIs around you are all language-operational. The IC community relationships are built here. The LPO seat at a NAVSECGRU is the one the Chief board expects to see in a competitive CTI1 record.
  • NSA / DIRNSA-affiliated command or joint IC site
    A different tempo. Less of the daily watch-floor production cadence, more of the IC analytic and collection-management environment. The GS-civilian and contractor workforce around you is large and the professional network is valuable post-Navy. Language stays relevant — CTIs at NSA-affiliated sites are expected to maintain DLPT currency — but the product type and the customer chain are different from the NAVSECGRU floor. The LPO at an NSA site is building a civilian-network record that pays off in the transition.
  • Deployed SIGINT element (fleet / expeditionary)
    Highest operational tempo, most concentrated collection environment. Language under real-world conditions is different from the sustainment program — the CTI1 who has done a deployed SIGINT tour knows what the DLPT cannot measure. The eEVAL bullets from a deployment carry weight, the production metrics are real, and the wardroom trust built on a deployment is the kind that travels to the next command in a fitness report addendum.
  • Joint intelligence support element (JISE) or combatant command J2 billet
    Joint-duty credit is a real career asset at this tier. The CTI1 at a JISE works alongside Army and Air Force SIGINT and intelligence professionals, which builds a professional vocabulary and a cross-service network that the community values. Language operations may be narrower than at a fleet NAVSECGRU — the JISE may not use your primary language operationally — which means the personal sustainment plan has to run without the daily operational context.
  • DLI follow-on cadre / language instructor or CIVT instructor billet
    A legitimate career-broadening option that carries real production risk. The CTI1 who goes to DLI or CIVT as an instructor is building a mentoring and language-teaching credential that the community values. The risk is exactly what it looks like — two to three years without operational collection context weakens the link between the DLPT score and the actual operational language performance. The instructor tour has to be paired with a disciplined personal collection-context sustainment plan.

What Good Looks Like at This Rank

The good CTI1 runs a section the department head cites at the CO's weekly battle rhythm update without modifying the slide. Every DLPT score in the division is current and on trend. The production brief runs without caveats. The eEVALs produce CTI2s who are visibly closer to Chief-board-competitive than they were when they checked in — and the ward room can name the specific metrics that support the comparison. On paper, the good CTI1's eEVAL trait average is at the top of the division's ranking, the collateral duty portfolio is running, the warfare device is current, and the Chief board packet is being built quarterly across the tour — not assembled in the week before submission. The IC community accession output is real: at least one Warrant, LDO, NSA civil-service, or commissioning selectee per year, and the CTI1 who developed that packet can speak to every decision point in the process from application to selection. Off paper, the good CTI1 is the petty officer the CTI2 comes to at 0200 when the hard collection is time-sensitive — not because the watch schedule says so, but because the CTI2 knows the LPO's answer will be technically sound, the escalation criteria will be applied correctly, and the product that goes up the chain will not come back for a rewrite. That is the reputation that travels to the Chief board before the record does.

Preview — The Next Rank

Making Chief — CTIC (E-7) — is the most structurally consequential promotion in the CTI rate. The job description does not change incrementally from CTI1 to CTIC; it changes substantially. You stop being the senior petty officer who manages the section and start being the Chief who owns the section's culture, the climate of the language community, and the standard that every CTI in the command reads off your conduct every day. The immediate difference is the goat locker. CPO 365 and the CPO Initiation cycle are real — you earn entry into the Chiefs Mess, not just the rank. The senior enlisted network of every Chief in the Navy is now your professional community, and the CTI Chiefs Mess specifically is small enough that every CTIC in the fleet is a colleague in the practical sense. The wardroom relationship changes too — the department head does not manage a Chief the way they manage a First Class; the relationship is more parallel, and the Chief is expected to walk into the department head's office with problems half-solved, not fully surfaced. The IC community liaison relationship is yours to own at CTIC — not the CTI1 LPO's, not the department head's. The NSA or DIA representative's primary point of contact for the enlisted CTI section is the CTIC. The professional standard the IC community holds the CTIC to is the one the senior IC civilians who hired the last three retiring CTI Master Chiefs carry in their professional memory.
FAQ

CTI E6 — Frequently Asked Questions

Q01What does a E6 CTI (Cryptologic Technician (Interpretive)) actually do?
You are LPO of a CTI division or senior linguist in a language section — running 8-20 CTIs at a Naval Security Group Activity, a joint IC site, an NSA-affiliated command, or a deployed SIGINT element.
Q02What's the most important thing to know as a E6 CTI?
CTI1 (E-6) is the last rank where your record gets built before the Chief board reads it.
Q03What does a typical day look like for a E6 CTI?
Time-blocked day at the E6 CTI rank tier: 0500-0545 Wake. Check secure messaging for overnight section issues — DLPT cycle notification, clearance-related action from the security office, IC community tasking message. PT gear on, 0545-0700 PT with the division. Wednesday command PT run, Thursday independent. Note who is showing up, who is not, who looks like they need a counseling about something that is not fitness, 0700-0730 Shower and change. Review the day's production schedule, DLPT cycle calendar, and any IC community tasking that dropped overnight, 0730-0800 Morning quarters.…
Q04What mistakes get E6 CTI soldiers fired or relieved?
DUI, NJP, or fraternization as an LPO — this ends the career in a small community where the record travels nationally. There is no 'back to the lower-visibility billet' in the CTI world; eEVAL fraud — inflating production metrics or language scores in a rated Sailor's record to avoid a difficult counseling. When the discrepancy surfaces at the next command, the writer's name is on the bullet and the Chief board knows the LPO who could not write an honest evaluation; OPSEC breach — posting,…
Q05What career decisions matter most at the E6 CTI rank tier?
Chief board timing — go hard on the current cycle or wait for a stronger record? — The CTI community is small enough that the senior CTIs know every CTI1 who is competitive before the board convenes. If your LCPO is building your packet with confidence — language scores on trend, eEVAL profile strong, production metrics named, IC community accession output running — go hard on the current cycle. If the packet has gaps that are fixable in six months, an honest conversation with the LCPO about whether this cycle is the right cycle is worth more than a weak first look.…
Q06What's next after E6 for a CTI (Cryptologic Technician (Interpretive)) in the Navy?
Making Chief — CTIC (E-7) — is the most structurally consequential promotion in the CTI rate.
Q07What manuals and regulations does a E6 CTI need to know cold?
ICD 203, 206, 208 — you are the division's senior voice on IC analytic and reporting standards and you enforce them on every product going up the chain.; NAVPERS 18068 Vol II + the current CTI NEC source-rating NAVADMIN — you build the pipeline off the current cycle.; OPNAVINST 1306.2 series — Detailing / assignment policy; the CTI community is small and you advise your sailors on the assignment market honestly.

Based on 14 tips from 0 contributors

Published by the Honest MOS Editorial DeskVerified against DoD/.gov sourcesUpdated May 2026Editorial standards