Working as a Navy Cryptologic Technician: What Nell Jones Actually Did and How It Works
NCIS: Los Angeles put Nell Jones front and center as the team's cryptologic tech, and for the most part the show got the day-to-day reality closer than most people give it credit for. She sat in front of screens, pulled signals, decoded traffic, and handed translations or decrypted products to the ops team. It was less "magic hacker" and more disciplined signal intelligence work with a lot of paperwork attached to it. I've spent time in and around this world, so let me break down what that role actually involves and how someone moves from raw intercept to something actionable. Nell's character was built around the Naval Cryptologic Technician (Communications) or CT(C) rating, and that's not made up. It's a real Navy community. These folks collect signals intelligence, translate foreign communications, crack encrypted traffic, and feed the results into operational workflows. On the West Coast, the nexus points are San Diego, where the Third Fleet operates out of, and the surrounding collection infrastructure that ties into broader US Navy intelligence channels. Nell would've been embedded with NCIS field elements, which is plausible because NCIS has its own intelligence staff and routinely pulls on CT products for investigations. The core workflow starts with collection, not decryption. That's the thing beginners and most TV shows skip. You have to know what you're looking for before you can find it. Nell's side of the table would involve monitoring communications bands, pulling out relevant traffic, and then either decrypting it if it was secured with a Navy system or translating it if it was plaintext foreign language traffic. The product then goes through validation — confirming source credibility, checking for consistency with other reporting, and making sure nothing got garbled in processing.
Real CT work uses specific platforms and systems. If you're talking about the Navy's real-world equivalents, things like the Joint Worldwide Intelligence Communications System (JWICS) handle classified material routing. Colleague systems and SIGINT tools run in the background doing frequency analysis and pattern matching. Nell's show-time keyboard smashing was mostly dramatic fiction. What actually happens is methodical comparison of known ciphertext against known cleartext, running traffic through decryption keys that are distributed on need-to-know basis, and cross-referencing everything against existing databases. The decryption part isn't brute force in most operational cases — it's using established cryptographic key management processes where the keys are rotated and issued through proper channels. Here's where it gets practical. Say you've intercepted a message that's encrypted under a Navy link encryption system. You don't crack it on your end. You submit a request through the proper intelligence chain to whoever holds the appropriate key material, and if your mission authorization covers it, the decrypted product comes back. That's the normal path. The alternative is working with foreign language communications that just need human translation, which is where Nell's linguistics background would come in handy. She'd be pulling meaning from actual spoken or written language, not from some fictional code machine. One edge case I ran into a few years back that the show never really addresses: time zone and shift mismatches between collection nodes. A CT in San Diego might pull traffic at 0300 that originated from a source in a completely different region, and by the time the translated or decrypted product makes it back up the chain to an operations center on the East Coast or overseas, the operational window could've already closed. The workaround I used was building a personal tracking sheet — not fancy, just a running log of intercept timestamps, source locations, and estimated delivery times through each processing step. It let me spot which routes were consistently slow and adjust my prioritization accordingly. Instead of waiting for all products to clear the queue at once, I'd flag time-sensitive material and route it through the fastest available channel, even if it meant skipping the usual verification loop for urgent items. That shortcut carries risk, but in a live investigation it's sometimes the only option.
There are a few counter-intuitive things about this work that nobody from the outside tends to understand. First, the most valuable intelligence often comes from the least sophisticated communications. A hand-written note scanned and transmitted over a commercial network can be more useful than a heavily encrypted military transmission, because the encrypted one might sit in a queue for days while the plaintext one arrives instantly and doesn't require any key material to read. Second, pattern recognition in traffic analysis is often more powerful than actual content decryption. Just knowing who's talking to whom, how often, and at what times can give investigators enough to go on without ever reading the actual message content. Nell's character did some of both, but in reality the traffic analysis side gets way more mileage than the decryption side. Another thing the show glosses over is how much red tape sits between you and the data you want. A CT can spend hours trying to access a piece of intercepted communications, only to discover that the classification level, the collector's rules of engagement, or a missing certification blocks the request. I've watched experienced technicians lose an entire morning chasing a product that ultimately couldn't be released because of a provenance issue. The workaround is building relationships with the collection assets and the release authorities early on. When you know who signs off on what and what their typical response times look like, you can plan around bottlene instead of hitting them unexpectedly during an active case. If you're interested in the actual systems and tools rather than the TV version, the closest legal entry point is studying the public-facing descriptions of the CT rating through Navy recruiting materials and the Defense Intelligence Agency's published job descriptions for signals intelligence roles. The Navy's own CT school at Great Lakes gives a publicly available overview of the curriculum. For the technical skills, cryptography courses at the college level, foreign language study at the advanced level, and familiarity with Linux command-line tools will cover maybe twenty percent of what a working CT does, but it's the foundation. The rest is institutional knowledge that can't be learned outside the community.
Get the Full Details
The downsides to this career path are worth stating plainly. The workload is mentally exhausting in a way that isn't obvious from the outside. You're constantly processing foreign language content, dealing with ambiguous or incomplete data, and operating under classification restrictions that mean you can't discuss your work with most of the people in your life. Turnover in the CT community is higher than most people realize, and the specialized nature of the skill set means transitioning out can be tougher than expected. The pay is reasonable for the education required but doesn't reflect the market value of these skills in the civilian sector the way you might expect. And the operational tempo during deployments means long stretches away from home with limited communication, which strains personal relationships whether you're on TV or not. For anyone serious about this work, the most practical starting point is contacting a Navy recruiter and asking specifically about the CT(C) and CT(I) ratings. From there, getting cleared is the next major hurdle, and that process alone can take months depending on your background. Language training through the Defense Language Institute is where most CTs spend significant time early in their careers, and picking the right language matters a lot. Some languages have far more demand and better career trajectory than others within the intelligence community. The NCIS LA portrayal of Nell was entertainment first and accuracy second, but the underlying profession it represents is real and it matters more than the show lets on. Naval cryptologic technicians on the West Coast are handling actual signals, actual translations, and actual decrypted products that feed into real investigations and operational decisions. It's dry, methodical, frustratingly bureaucratic work that occasionally produces moments of genuine importance. That's closer to the truth than any TV drama will show you.
