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
CTIE5

Cryptologic Technician (Interpretive)

E-5 (Sergeant) · Navy

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

The DLPT is no longer just a personal proficiency standard — it is the section's proficiency standard, and you are responsible for both. A CTI2 whose own language is drifting while managing the section has made a visible mistake that the senior CTI and the LCPO will read correctly. Maintain your language. Run the section's sustainment program. Those are not two tasks — they are the same task with different scope.

The Honest MOS Read
Cryptologic Technician Interpretive Second Class (CTI2, E-5) is the rating's working senior linguist tier and, in operational practice, the de facto LPO of a language section whether the billet title says so or not. You run a watch section, a language cell, or a production team at a Naval Security Group Activity, a joint IC site, an NSA-affiliated command, or — if the community sent you — a deployed SIGINT element. The CTI3s under you are watching how you handle hard collection, how you carry the section's proficiency standard, and how you deal with the chief. What you model is what they learn. The production responsibility has expanded from individual contributor to section output. You are not just submitting your own translations and analytic products — you are QA-reviewing CTI3 products before they go up the chain, escalating significant intelligence to the senior CTI and the reporting chain at the right moment rather than the expedient one, and doing the shift handoff clean enough that the incoming watch section does not spend the first hour of their shift reconstructing what you left behind. The senior CTI used to sign off on your products; now you are the QA layer for the CTI3 products, and the senior CTI is the QA layer for yours. The DLPT is the career's persistent constraint named honestly. At CTI2, it is no longer just about your own proficiency — the section's DLPT sustainment is your operational responsibility. You track the CTI3 scores, you schedule the cycles, and you identify who is trending down early enough for remediation before the lapse becomes a production gap. A CTI2 who lets a CTI3's DLPT drift because addressing it meant writing a remediation counseling is the same CTI2 who is explaining the production gap to the senior CTI the following quarter. The DLPT conversation is not optional; it is the job. The NEC structure is real at this tier. Your language-specific NEC, any follow-on specialization NECs the community has assigned, and the assignment track the detailer and community manager are building for your record — these are the career infrastructure conversations that belong at CTI2. The path to an IC community accession — NSA civil service pipeline, joint IC analyst program, all-source conversion — is visible from CTI2, and the record built at this tier is the one those programs evaluate. Talk to the LCPO about what the community senior staff has seen select from commands like yours. The NWAE for CTI1 advancement is on the study schedule from day one at the CTI2 tier. Pull the BIB from MyNavyHR/NETC and own it. The CTI community is small enough that the advancement rate is influenced by manning math in ways that a large rating is not; a cycle where the community is short of CTI1s can produce favorable selection rates, and the CTI2 who is already prepared takes advantage of it. Do not wait for the cycle announcement. The eEVAL inputs for CTI3s are new work at this tier — writing observable, defensible, production-metric-backed evaluation inputs for junior Sailors is a skill that does not come automatically from being a good linguist, and the CTI2 who treats the eEVAL input as a chore produces generalities that the senior rater cannot use. Observable behavior, language scores, production metrics, specific analytic contributions — the LCPO who is writing the CTI3's eval needs specifics, and it is the CTI2 LPO-in-fact who provides them. The Chief conversation belongs at CTI2. The community is small, the CTIC slate is known, and the LCPO and senior CTI community staff are already evaluating which CTI2s are building Chief-competitive records. The record built at this tier — DLPT currency, section production quality, junior Sailor development, eEVAL quality, IC community product — is what the Chief board reads. Start building it now.
Career Arc
  • 01Check in to second or third billet as CTI2 — Naval Security Group Activity, joint IC site, NSA-affiliated command, or deployed SIGINT element; often a more specialized assignment than the first billet based on language NEC and community priority.
  • 02De-facto section LPO role — production QA for CTI3 outputs, DLPT sustainment tracking for the section, shift-handoff ownership, escalation of time-sensitive intelligence to the reporting chain.
  • 03CTI3 eEVAL inputs — first experience writing evaluation documentation for junior Sailors; observable behavior, production metrics, language scores, analytic contribution.
  • 04NWAE for CTI1 advancement — BIB study from the first week at the CTI2 tier; take the exam in the first eligible cycle.
  • 05IC community accession conversation — NSA civil-service pipeline, joint IC analyst program, all-source conversion track; the LCPO and community senior staff know which pathways are selecting from your command profile.
  • 06Chief packet conversation begins — LCPO evaluating the eEVAL profile, DLPT currency, section output, and IC community contribution for CTIC board competitiveness.
  • 07Orders to next billet with community and career considerations — detailer, community manager, and the LCPO all have a view on the assignment that builds the strongest CTIC-competitive record.
Common Screwups
  • ×Letting a CTI3's DLPT lapse pass unremarked in the shift handoff because writing the remediation counseling felt like overhead. The next production review surfaces the shortfall, the senior CTI notes the gap, and the CTI2 who knew and said nothing is explaining it. The DLPT is your section's currency — track it, flag it early, and write the counseling.
  • ×Signing off on a translation product with a significant ambiguity papered over to hit the production quota. At CTI2, your QA signature is on the product. When the IC community customer finds the gap — and they find it — the name traced back in the reporting chain is the CTI2 who approved it. ICD 203 analyst notes exist for exactly this situation: flag the ambiguity, call for additional collection, and let the customer decide how to use an honestly uncertain product.
  • ×Treating the NWAE for CTI1 as a back-burner project because 'the community is small and I will probably make it anyway.' Community size cuts both ways — there are fewer slate spots as well as fewer competitors, and the senior enlisted community knows exactly which CTI2 is coasting versus which one is prepared. The prepared one advances first.
  • ×Going around the LCPO to the front office, the NSA liaison, or the IC community senior staff about a production or career issue. The CTI community is small and the goat locker is smaller; the LCPO hears about the end-run the same day, and the relationship damage affects the eEVAL profile in the current cycle.
  • ×Allowing classified-material handling to become routine to the point of sloppy — informal discussions in common areas, printed product left on the workspace between shifts, end-of-shift security cleanup treated as optional. The security office runs sweeps. A finding at CTI2 level names the senior person in the space, and the CTI2 is now that senior person.

A Day in the Life

  • 0530-0600Wake up. If at a shore-based NSGA or joint IC command with a day-work schedule, gear up and head to chow or start the commute. If on a rotating shift schedule, adjust the start of the day accordingly — what follows is a day-shift/garrison pattern.
  • 0600-0700Command PT or self-PT. The CTI2 who leads PT rather than showing up is the one setting the section's standard. Shore IC billets have voluntary and mandatory PT windows; make both matter. The CTI3s watch the senior section member's PT commitment as closely as they watch the production standard.
  • 0730-0800Morning quarters / accountability. You run the accountability report for the section, not just your own check-in. Any outstanding administrative items — security-office paperwork, eval input deadlines, DLPT cycle scheduling — surface here in the weekly section admin check.
  • 0800-0900Shift onload — review overnight production, receive senior CTI tasking, check DLPT sustainment status for the section (any upcoming cycles, any scores that came back from the last test needing a conversation), confirm open administrative actions. One brief pass through the section's tracking sheet.
  • 0900-1130Production block one — primary collection and QA work. The CTI2's production is parallel to QA review of CTI3 products. Draft your own products; review CTI3 drafts before they go up the chain. The correction cycle happens at this tier, not at the senior CTI tier — products that leave your section should not need a rewrite from the senior CTI.
  • 1130-1200Mid-morning section check — production pace against quota, any CTI3 who is struggling with a collection requirement or a translation ambiguity gets direct guidance at this point rather than at end of shift. Significant intelligence escalated to the senior CTI on the timeline the reporting requirement demands, not the expedient one.
  • 1200-1300Lunch. Use it. The afternoon production block is better after a genuine break. If there are administrative actions with afternoon deadlines — eval inputs, career-counselor appointments, security-office items — block the time now or immediately after lunch.
  • 1300-1600Production block two — continued collection, translation, analysis. The afternoon block often carries the harder collection items from the daily tasking. CTI3 QA continues; any products flagged for analyst notes or additional-collection calls go to the senior CTI with the CTI2's recommendation, not just a question.
  • 1600-1700Shift close-out — all products submitted and documented, classified materials secured (every shift, every item), DLPT tracking sheet updated if any new test results or cycle scheduling actions happened today. Shift handoff package prepared: open products with status, outstanding tasking with notes, any personnel actions pending. The handoff is done before the incoming watch section arrives, not while they are waiting.
  • 1700-1800Administrative block — BIB study for CTI1 NWAE, eEVAL input drafting for CTI3s (running document updated with today's production metrics and observations), career-counselor prep if there is a pending conversation. The CTI2 who builds administrative tasks into the end of the duty day does not spend evenings catching up.
  • 1800-2000Personal time and target-language sustainment. Structured reading in the target language — news domain, technical domain relevant to the collection work, official text — not passive background media. If secondary language is assigned, rotation between the two languages in the sustainment routine.
  • 2000-2200BIB study for CTI1 NWAE or deep target-language practice — timed listening drills, reading comprehension self-testing, vocabulary in the specific technical register the production floor uses. Not every night, but the nights it is scheduled, it happens.

Weekly Cadence

Monday through Friday at a shore-based CTI billet runs on the production floor rhythm with administrative tasks layered on top. Monday is the week's onload — review the weekend production, receive the week's tasking priorities from the senior CTI, confirm the DLPT cycle schedule and any upcoming section admin actions. The section check on Monday morning is the one where the CTI2 is setting the week's tone: what the production standard looks like, who has an outstanding action item that needs to close this week, whether any CTI3's language trend needs attention before the next test cycle. Tuesday and Wednesday carry the heaviest production weight in a standard garrison week. The collection requirements are being worked, the QA cycle is active, and the section's output is being compared to the weekly quota. Wednesday is also the midweek check on DLPT sustainment — any CTI3 who is behind on the sustainment routine gets a direct conversation on Wednesday, not Friday. Catching drift early in the week is a management habit; catching it at Friday close-out is reactive. Thursday is the advance-preparation day for the following week's administrative actions and the day the harder collection items typically land on the tasking list. Friday close-out is documentation-and-handoff focused: all products completed and submitted, classified materials secured, section tracking updated, outstanding actions with clear status, nothing in ambiguous state going into the weekend. The NWAE study rhythm belongs in the weekly schedule, not in a separate project. The CTI2 who is running the BIB continuously — 30-45 minutes of structured study on the days when it fits, not waiting until the cycle announcement generates urgency — is the one who takes the exam prepared rather than cramming. Build it into three weekday evenings consistently rather than a weekend marathon that competes with everything else. Security-office rhythm at CTI2 is the section's rhythm, not just the individual petty officer's. The weekly check — did anything happen this week in the section that needs a security-office report? Foreign contacts, financial events, uncertain situations — runs at the Monday section check and the Friday close-out. The section that develops the habit of surfacing security-office questions to the CTI2 before deciding independently produces a cleaner continuous-evaluation record than the one that relies on individuals to self-report without prompting.

Key Skills — How to Drill Each

  1. 01
    Lead a language section shift — production quota, QA review of CTI3 product, escalation of significant intelligence, clean handoff at turnover.
    The section shift standard is the one you enforce, not the one you inherited. Set the QA bar explicitly with the CTI3s on your section: this is what a product that goes up the chain looks like, this is what an analyst note for a genuinely ambiguous section looks like, this is what a sourcing citation looks like under ICD 206. The CTI3s will calibrate to whatever standard the CTI2 enforces; if you accept lazy sourcing or smoothed-over ambiguity because it hits the quota faster, that is the standard you are setting. Make the corrections explicitly — show the redline, explain the standard, and track whether the same error recurs.
  2. 02
    Write finished intelligence reports, translation summaries, and analytic notes to ICD 203/206/208 standards at a quality level the senior CTI signs without revision.
    The bar is 'the customer at the other end of the reporting chain uses this without calling back for a rewrite.' Track your own correction rate from the senior CTI. If products are coming back for revisions consistently in a particular category — sourcing citation format, analyst note construction, translation accuracy in a specific vocabulary domain — that is a skill gap to address directly, not to work around by asking for less feedback. The CTI2 who produces clean product is the one the senior CTI puts on the hard collection, which is where the next CTIC-competitive eEVAL bullet is built.
  3. 03
    Maintain DLPT proficiency at or above the operational standard for your primary language — and for a secondary language or dialect if your command has assigned one.
    Active language maintenance is the only thing that prevents decay. The specific regimen depends on the language — Category IV languages (Arabic, Mandarin, Korean, Japanese) decay faster without active use than Category I/II languages — but the structure is the same: scheduled reading in technical and news-domain material in the target language, timed listening practice in the specific collection domain relevant to your production work, and periodic self-testing against the DLPT format before the actual cycle. The CTI2 who treats language maintenance as reactive — study when the test is coming — arrives at the test having spent the previous six months letting the language decay.
  4. 04
    Run the section's DLPT sustainment plan — schedule the cycles, track the scores, identify who is trending down early enough for remediation before the lapse becomes a production gap.
    Build a tracking sheet for every CTI on your section: current DLPT score, test date, next cycle date, trend direction. Review it at least monthly. The CTI3 whose score has dropped since the last test is having a conversation with you before the next cycle, not after the next cycle confirms the trend. Early remediation — DLIFLC online resources, language-lab access, additional reading assignment in the target domain — is recoverable. A CTI3 who has missed two cycles and needs TDY remediation at Monterey is a production gap and an LPO failure, not just a junior Sailor's problem.
  5. 05
    Write CTI3 eEVAL inputs — observable behavior, production metrics, language scores, analytic contribution — to a standard the senior rater can defend.
    The three words that make an eEVAL defensible: specific, observable, measurable. 'CTI3 Lastname translated X products per shift averaging ILR [score] DLPT proficiency with zero senior-CTI rewrites in the current evaluation period' is defensible. 'Demonstrated excellent linguistic proficiency and consistently contributed to the section's mission' is not. Pull the production metrics — how many products, what error rate, DLPT score trend — and build the eval bullet from numbers the senior rater can stand behind at a wardroom board. The LCPO who gets a well-supported eEVAL input from the CTI2 in-fact LPO writes a stronger eval; the LCPO who gets generalities does not.
  6. 06
    Counsel a CTI3 honestly on career-path choices: community assignment track, NEC pathway, the re-up versus ETS conversation, the IC community accession options.
    Honest counseling at CTI3 means telling the junior Sailor what the record actually says, not what they want to hear. A CTI3 with a declining DLPT trend and a marginal production record needs to hear that the IC community accession pathway the LCPO mentioned in passing requires a significantly stronger record than what they are building. The CTI3 who is producing clean product and maintaining language currency needs to hear about the specific pathways the community is selecting from right now, not the generic 'NSA has opportunities' conversation. Your LCPO and the community career counselor are the resources; use them before you counsel, not instead of counseling.

Manuals & References — What Chapters Matter

  • ICD 203 — Analytic Standards; ICD 206 — Sourcing Requirements; ICD 208 — Intelligence Community Reporting (dni.gov / IC Directives library)
    You are writing finished product to these standards and QA-reviewing CTI3 product against them. The CTI2 who can explain to a CTI3 specifically which section of ICD 203 an analytic note convention comes from — rather than just saying 'that's not how we do it' — is building the junior Sailor's standard, not just enforcing a rule. Know these documents at the section-level operational depth.
  • NAVPERS 18068 Vol II + the current CTI NEC source-rating NAVADMIN — both available through MyNavyHR
    You are building career counseling conversations for CTI3s off the current edition. The NEC structure, the current community accession pathways, and the assignment-demand picture for your language — these come from the current NAVADMIN cycle and the NEC catalog. Do not counsel a CTI3 on career-path options using information that was accurate two years ago.
  • OPNAVINST 1306.2 series — Navy Detailing and Assignment Policy
    The CTI community is small and the detailer's assignment priorities are visible in the NAVADMIN cycles. The CTI2 who understands the assignment market — which billets are hard to fill, which language profiles the community manager is prioritizing, what the second-billet career-development track looks like for CTIC-competitive records — is the one who counsels CTI3s accurately about where the orders are likely to go and why.
  • NWAE Bibliography for Advancement (BIB) for CTI1 — NETC, available on MyNavyHR
    Pull it the week you pin CTI2. The CTI1 advancement exam tests the BIB; the CTI2 who is running the BIB continuously does not need to cram. The BIB covers rate-specific technical material, Navy-wide leadership content at the first-class petty officer tier, and the professional military knowledge subjects the NWAE draws from. Own it.
  • SECNAVINST 5239 series — DON Cybersecurity / IA Program; your command's SCI access and compartment management policies
    At CTI2, you are responsible for the section's access posture, not just your own. The security officer calls you when a CTI3 on your section has a foreign-contact issue, a financial-disclosure lapse, or a classified-handling incident. Know what the program requires and enforce it at the section level before the security office has to.
  • DLIFLC sustainment resources and the current IC community DLPT proficiency requirements — verify against the current applicable NAVADMIN and with the LPO / LCPO
    The graduation standard from DLI and the operational floor for your community are not always the same number. The proficiency requirement for your specific language and community assignment comes from the current NAVADMIN and the command SOP. Know the number for every language in your section — not just your own — and manage toward it.

Standards — How to Hit Each

  • DLPT scores at or above the operational standard every cycle, primary language without exception.
    Build the sustainment routine into the weekly schedule rather than running it reactively before the test cycle. Structured reading in the target language in the technical and news domains relevant to your collection work, timed listening practice, and periodic self-testing against the DLPT format — not passive consumption, active production. The CTI2 whose language is visibly declining while they are managing the section has made a leadership mistake; the section reads it. Maintain the language as actively as you run the section.
  • Section production quota met at or above command average without the senior CTI reworking your shift handoff.
    The handoff is the clearest signal of how the shift was run. A handoff that the incoming watch section can execute without clarification from the outgoing CTI2 is a handoff done right — open products documented with status, classified materials secured, outstanding tasking with clear notes, nothing in ambiguous state. Develop a handoff template for the section: the same structure every time, the same information every time, so the shift transition is a 10-minute event rather than a 30-minute reconstruction.
  • NWAE for CTI1 prep on the LCPO's timeline; eEVAL trait average and ranking that supports an EP or MP recommendation.
    The eEVAL profile is built across the evaluation period, not assembled from notes the week before the report due date. Track your production metrics, DLPT scores, section development contributions, and any IC community product or accession-program contribution in a running document throughout the year. When the eval period closes, the specifics are already in the record — not reconstructed from memory. The LCPO who receives a well-documented performance input from a CTI2 writes a stronger narrative eval.
  • PRT Good High or better; BCA in standard; warfare device current where the billet and platform allow.
    Shore IC billets are sedentary — the mission does not demand physical fitness in the way an FMF or shipboard billet does. The CTI2 who maintains PT independently, who shows up to the command PRT having trained for it rather than scrambling the week before, sets a different standard for the CTI3s in the section than the one who is visibly unprepared. The warfare device — information warfare, if the billet qualifies — should be current. If it is pending, have the timeline for completion in the conversation with the LCPO.
  • Clearance and continuous-evaluation status clean for the section — nobody on your watch parked off their seat for a foreign-contact or financial-disclosure lapse you could have caught.
    The section LPO-in-fact is the first person the LCPO calls when a CTI3 has a security incident. Build the habit of asking the section regularly — informally, at the section level — if anyone has had foreign contact, a financial event, or a situation they are not sure about reporting. The CTI3 who comes to the CTI2 with a foreign-contact situation rather than trying to decide independently is the one who gets a clean report instead of a late disclosure finding.

Technical Mistakes — Concrete Consequences

  • Letting a CTI3's DLPT lapse pass unremarked in the shift handoff because writing the remediation counseling felt like overhead.
    The production gap the following quarter has the CTI2's name on it. The senior CTI and LCPO trace the lapse back to when it became visible and compare that date to when the remediation counseling was initiated. A CTI2 who identified the decline and acted early has a documented management response; a CTI2 who let it ride has a management failure. The counseling conversation is not punitive — it is the job.
  • Signing off on a translation product that has a significant ambiguity papered over to hit the production quota.
    At CTI2, the QA signature is yours. When the IC community customer identifies the gap — and in a reporting chain built on finished intelligence products, gaps in source material are found — the product is traced back through the reporting chain to the CTI2 who approved it. An honest analyst note that flags the ambiguity and calls for additional collection is what ICD 203 requires and what the customer needs. A product that looks complete but is not is worse than an honestly incomplete one.
  • Treating the NWAE for CTI1 as a back-burner project because the community is small.
    Community size cuts both ways — there are fewer slate spots as well as fewer competitors, and the senior enlisted network knows which CTI2s are prepared and which ones are not. A favorable manning cycle can produce CTI2 advancement before the unprepared CTI2 realizes it, and then the competition shifts to the next cycle with a year's less time in rate relative to peers who started earlier. The BIB is the test and the test is the BIB; the CTI2 who owns it continuously does not gamble on the cycle math.
  • Going around the LCPO to the front office, the NSA liaison, or the senior IC community staff about a production or career issue.
    The CTI community is small and the goat locker is smaller. The LCPO hears about the end-run from the front office, the liaison, or the senior staff the same day. The relationship damage is immediate and the eEVAL profile reflects it — not through a negative bullet, but through the absence of the narrative support that the LCPO's trust produces in a positive one. Issues go through the chain. Disagreements are resolved in the office.
  • Allowing classified-material handling to become routine to the point of sloppy — end-of-shift cleanup treated as optional, printed products left on workstations, informal SCIF discussions about classified material.
    The security office runs sweeps at IC commands. A finding in the section names the senior person in the space; at CTI2, that is you. A classified-material finding at the LPO-in-fact level goes into the security record, the LCPO hears about it before the end of the duty day, and the eEVAL cycle that follows has a shadow on it. The habit of treating end-of-shift security cleanup as mandatory — every time, every shift — is what prevents this.

Career Decisions at This Rank

  • Second re-enlistment — commit to the Chief path, take the SRB and stay, or start planning the civilian IC transition?
    The honest framing is this: if you are currently tracking toward a Chief-competitive record — DLPT currency strong, section production clean, CTI3s advancing, eEVAL profile at EP or high MP — the community is investing in you and the SRB (Selective Re-enlistment Bonus, pull the current message from MyNavyHR before any financial decision) reflects that. The IC community credential at CTI2 level — TS/SCI with CI poly, operational-level language proficiency, IC reporting experience — has real civilian value, but the CTI2 who ETS mid-career with a mid-tier record looks different to a federal civilian hiring manager than the CTI1 or CTIC who retired with a full career of IC production and section leadership. The CTI2 who is genuinely burning out on the production floor and has declining DLPT scores needs to have the conversation with the LCPO now, not at the ETS window, so the community can make an honest assessment of whether remediation or transition is the right answer.
  • IC community accession — NSA civil-service pipeline, joint IC analyst program, all-source conversion. Is this the right time?
    The timing depends on the record. The IC community accession programs that select from active-duty CTI billets typically require a strong DLPT profile, operational-level IC production experience, a clean clearance record, and the support of the command and the community senior staff. At CTI2, the question to ask the LCPO honestly is: 'Based on what you have seen select from commands like this one, is my current record competitive, and if not, what does it need to be?' The LCPO and the community manager have a realistic view of what the programs are selecting for in the current cycle. An IC community accession from CTI2 with a strong record is a career accelerant; applying for a program you are not ready for and not selecting is a time cost with no return. Get the honest assessment before submitting the packet.
  • Warrant Officer or Limited Duty Officer pathway — is this something to pursue from CTI2?
    The Warrant Officer and LDO pathways for CTI community Sailors are specific and the current eligibility requirements, time-in-service gates, and community quotas come from the applicable NAVADMIN each cycle — verify before quoting anything. The general guidance: the CTI2 with a CTIC-competitive record who does not want the Chief path and has the educational and professional profile the program requires should have the LDO/Warrant conversation with the LCPO. These programs are competitive; the application requires command support and a well-built package. Start building the package with the LCPO's input, not independently. The CTI2 who pursues a Warrant or LDO packet with strong LCPO and commanding-officer support has a fundamentally different application than the one who puts in the paperwork without the chain's investment.
  • Building the Chief packet — what does a CTIC-competitive record look like from CTI2, and what does this tier need to produce?
    In the CTI community, the CTIC board knows everyone on the slate before the results publish — the community is that small. The record the board evaluates is the eEVAL profile across the career, the DLPT currency, the section output during the CTI2 and CTI1 tours, the pipeline produced (Warrant, LDO, commissioning, NSA civil-service accessions), and the IC community's senior staff's direct knowledge of the record. The CTI2 who builds a Chief-competitive record starts by doing the CTI2 job well: clean production, current DLPT, advancing CTI3s, defensible eEVAL inputs. The LCPO will tell you what the board's current bar looks like; ask directly and build toward the specific standard, not a generic 'be good at your job' aspiration.
  • Second-language or dialect expansion — how aggressively to pursue it at CTI2?
    The CTI2 who has primary-language DLPT scores at the operational standard and capacity for a secondary language or dialect assignment should accept it. The community invests in linguists with multi-language profiles; the assignment options are broader, the IC community accession pathways consider it positively, and the operational utility is real. The honest constraint is the sustainability check: maintaining two languages at operational proficiency simultaneously requires more active sustainment time than maintaining one. The CTI2 who accepts a secondary assignment and then lets either language drift has done more damage than staying single-language would have. If the primary language is not solidly above the operational floor, build that before adding a secondary.

How the Seat Varies by Unit Type

  • Naval Security Group Activity (NSGA) — shore-based production billet
    The most common CTI2 billet environment. Shift or day-work structure, clear section hierarchy, DLPT sustainment program managed at the command level, production metrics visible at department-head review. The NSGA CTI2 has the clearest organizational context for section leadership — the LPO role is defined, the LCPO and CTIC are close, and the senior CTI's feedback cycle is immediate. The operational pace is set by the collection requirements, which can run high-tempo or relatively steady depending on the global situation and the command's specific mission.
  • Joint IC or NSA-affiliated command
    Broader IC community context than a single-service NSGA — other-service linguists, civilian IC analysts, and a mission that may include collection and reporting work beyond the Navy's organic SIGINT mission. The CTI2 at a joint command is likely working alongside DIA, NSA civilian, Army or Air Force SIGINT, and contractor personnel. The professional exposure is valuable for IC community accession preparation. The command culture and the section structure may differ from a Navy-only environment; the QA standards and IC reporting requirements are the same regardless of the organizational wrapper.
  • Deployed SIGINT element or expeditionary assignment
    The operational tempo and the resource environment are different from shore-billet production work. The DLPT sustainment infrastructure — DLIFLC online resources, command language lab, scheduled cycles — may not be available in the same form. The CTI2 on a deployed element who is responsible for a section's DLPT currency in a resource-constrained environment needs to build a field sustainment plan before deployment, not improvise one after arrival. The production standard does not relax in the field; the QA and reporting requirements travel with the section.
  • NSA-affiliated billet or direct IC community assignment
    The highest-visibility CTI2 billet type from a community-accession perspective. NSA-affiliated assignments expose the CTI2 to the civilian IC hiring pipeline, the community senior staff's direct assessment of the record, and the production standards that NSA civil-service positions look for. The CTI2 at an NSA billet who performs well is being evaluated for the next step by people who have the authority to make it happen. The pressure is also higher — the senior CTI and the IC community liaison have a clearer view of the individual's production quality than at a service-only command.
  • Small command or isolated IC billet
    Some CTI2s serve at small commands — isolated technical installations, small joint elements, or billets with limited organic CTI community support. The leadership load at a small command can be higher than at an NSGA — fewer CTIs means each one carries more section responsibility — and the LCPO and CTIC may be remote or limited. The CTI2 at a small command who is self-directed, maintains the DLPT and production standard independently, and manages the section's security posture without daily guidance from an LCPO is the one who builds the strongest independent-operator reputation in the community.

What Good Looks Like at This Rank

The good CTI2 is the petty officer the LCPO slots on the hard collection shift without checking in from leave. Not because the CTI2 is available, but because the production will be clean, the CTI3s will be supervised, the DLPT scores in the section will not move in the wrong direction on their watch, and the handoff to the incoming section will take ten minutes instead of thirty. The production standard the good CTI2 enforces is visible in the section's correction rate. The senior CTI's revision notes on products from this section are declining in frequency because the CTI2 caught the corrections before submission. The CTI3s are learning to flag ambiguity rather than smooth it over because the CTI2 showed them what an honest analyst note looks like and why it matters more than a clean-looking product that misleads the customer. The eEVAL inputs this CTI2 produces have specific production metrics, specific language scores, and a clear trend narrative that the LCPO can defend at the wardroom-level board without hedging. The Chief conversation is already alive. The LCPO is tracking the eEVAL profile across the year, the community senior staff knows the section's output by name, and the IC community accession pathway — whether NSA civil service, joint IC program, or the all-source conversion track — is a real conversation with a real timeline, not a recruiter's pitch. The CTI2 who is building a Chief-competitive record at this tier is the one whose language scores are current, whose section is producing clean product, whose CTI3s are advancing, and whose clearance record reads clean because the hygiene was built in, not maintained by luck.

Preview — The Next Rank

The CTI1 (E-6) tier is the LPO. Not the de-facto LPO in practice — the titled LPO of record, responsible for a division of 8-20 CTIs at a Naval Security Group Activity or joint IC command, writing four to six eEVALs per cycle, building the DLPT sustainment plan for every language in the division, and defending the section's production output and proficiency posture at department-head sync. The workload that the CTI2 managed at the section level is now the division level, and the accountability moves up with it. The Chief board packet is no longer an abstract future conversation at CTI1 — the LCPO is editing the record actively, the eEVAL profile is being built for board competitiveness across the CTI1 tour, and the IC community's senior enlisted know which CTI1s are on the CTIC track before the board convenes. The community is small enough that this is literal: the senior CTIs and CTICs at the community-management level know the CTI1s by name and by record. The CTI2 who builds the right record in this tier is the one who shows up at CTI1 with momentum the LCPO does not have to create from scratch. The mentoring responsibility expands at CTI1. The expectation is not just that the CTI1 is developing their direct CTI2s for CTI1 advancement — it is that the division is producing IC community accessions: Warrant, LDO, NSA civil service, commissioning programs, all-source conversion. The CTI community senior staff knows which LPOs are building pipelines and which ones are managing headcount. In a small rating, the difference between the two is visible and permanent.
FAQ

CTI E5 — Frequently Asked Questions

Q01What does a E5 CTI (Cryptologic Technician (Interpretive)) actually do?
You run a section — a language cell, a production team, a watch section at a Naval Security Group Activity or joint IC billet, or a deployed SIGINT element depending on where your community sent you.
Q02What's the most important thing to know as a E5 CTI?
The DLPT is no longer just a personal proficiency standard — it is the section's proficiency standard, and you are responsible for both.
Q03What does a typical day look like for a E5 CTI?
Time-blocked day at the E5 CTI rank tier: 0530-0600 Wake up. If at a shore-based NSGA or joint IC command with a day-work schedule, gear up and head to chow or start the commute. If on a rotating shift schedule, adjust the start of the day accordingly — what follows is a day-shift/garrison pattern, 0600-0700 Command PT or self-PT. The CTI2 who leads PT rather than showing up is the one setting the section's standard. Shore IC billets have voluntary and mandatory PT windows; make both matter.…
Q04What mistakes get E5 CTI soldiers fired or relieved?
Letting a CTI3's DLPT lapse pass unremarked in the shift handoff because writing the remediation counseling felt like overhead. The next production review surfaces the shortfall, the senior CTI notes the gap, and the CTI2 who knew and said nothing is explaining it. The DLPT is your section's currency — track it, flag it early, and write the counseling; Signing off on a translation product with a significant ambiguity papered over to hit the production quota. At CTI2,…
Q05What career decisions matter most at the E5 CTI rank tier?
Second re-enlistment — commit to the Chief path, take the SRB and stay, or start planning the civilian IC transition? — The honest framing is this: if you are currently tracking toward a Chief-competitive record — DLPT currency strong, section production clean, CTI3s advancing, eEVAL profile at EP or high MP — the community is investing in you and the SRB (Selective Re-enlistment Bonus, pull the current message from MyNavyHR before any financial decision) reflects that. The IC community credential at CTI2 level — TS/SCI with CI poly, operational-level language proficiency,…
Q06What's next after E5 for a CTI (Cryptologic Technician (Interpretive)) in the Navy?
The CTI1 (E-6) tier is the LPO.
Q07What manuals and regulations does a E5 CTI need to know cold?
ICD 203, 206, 208 — you are writing finished product to these standards and you are QA-reviewing CTI3 product against them.; NAVPERS 18068 Vol II + the current CTI NEC source-rating NAVADMIN — you build career counseling conversations off the current edition, not the stale folder.; OPNAVINST 1306.2 series — Detailing / assignment policy; the CTI community is small and the detailer's priorities are visible to anyone who reads the current NAVADMIN cycles.

Based on 14 tips from 0 contributors

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