Job search
Cyber Threat Intelligence Jobs: Check Collection, Analysis, and Who Uses the Output
Compare intelligence collection, analytical judgments and users of the finished output through two US employer descriptions and two completed fictional assets.
Compare cyber threat intelligence jobs by the questions they answer, the collection they require and the people who use the finished analysis. Finding indicators supplies one possible input to that work. To assess your fit, ask whether you can explain a judgment, its supporting evidence, its uncertainty and the decision it is meant to inform.
LandOffer publishes this guide. Use recent roles on LandOffer.ai to choose a target, then read the employer's full requirements. The complete stable employer descriptions and official publication record were checked on October 23, 2026. The employer examples are responsibility snapshots, not a continuously verified vacancy list. The worked records below are fictional; no threat actor, private community, employer system or application was accessed.

Start with the intelligence customer
An intelligence customer is the person or team that needs the analysis for a decision. A detection engineer might need context for a defensive hypothesis. A security leader might need to understand whether a reported threat changes an investment priority. The same source material can support different outputs, with different detail and timing.
NIST's Guide to Cyber Threat Information Sharing describes threat information broadly: indicators, adversary tactics and techniques, incident analysis and suggested defensive actions. Its guidance covers sharing goals, information sources, distribution rules and effective organizational use. The October 2016 publication remains useful background; it is not a current employer's job specification or permission to collect restricted material.
When a posting says “actionable intelligence,” identify the action and recipient. Does the analyst provide a written assessment, a technical handoff, a leadership briefing or an operational data product? Does the recipient feed back whether it answered the question? Those details let you compare your actual deliverables with the work the employer needs.
Two US descriptions show different demands
Anthropic's Security Engineer — Threat Intel places the function within Detection & Response. The description combines actor and campaign research with production-quality automation, collection pipelines, technical analysis and collaboration on defensive detections. The role body seeks five or more years of relevant hands-on experience and demonstrable adversary knowledge, while the application form asks whether candidates have eight-plus years. Clarify that mismatch with the employer rather than treating the lower figure as a complete screening rule. This is a technically substantial engineering role, rather than a reporting-only opening. Its remote-friendly heading also specifies travel, while the logistics section describes office attendance; check the actual arrangement before treating it as location-independent work.
ID.me's Senior Threat Intelligence Analyst emphasizes end-to-end coverage of a defined threat portfolio. Its work runs from requirements and collection strategy to finished assessments, delivery and follow-up with engineering, leadership and partners. It asks for five or more years of relevant experience, including finished intelligence, plus three or more years of specified deep- and dark-web collection experience. This role’s application form explicitly asks for five days onsite in Mountain View or McLean, including whether the candidate can commute or relocate. Neither a writing sample nor general security operations experience establishes all those requirements.
These are two senior examples with distinct organizational contexts, not evidence that every CTI job requires the same collection sources, engineering depth or years. Read the responsibilities and qualifications together. A title containing “analyst” can still require substantial technical work, independent scoping and influence over other teams.
Separate collection from analysis
Collection starts with an information need. A list of sources is incomplete unless you can explain what each source may answer, its limitations and why it is appropriate to use. More material does not necessarily reduce uncertainty: several reports can repeat the same underlying observation without providing independent corroboration.
Analysis asks what the collected material supports. Is a behavior relevant to the organization? Does the evidence identify an actor, or only a technique used by several actors? What alternative explanation remains plausible? Separate reported facts from your interpretation, and name the evidence you still lack.
An indicator of compromise, or IOC, is not a finished judgment. An address or file identifier may need context about provenance, age, relevance and handling before a recipient can use it. Copying a feed into a spreadsheet does not establish that you assessed its significance or that an organization should act on it.
For an application, describe the decision you made about the material. You might have rejected an unsupported attribution, identified a coverage gap or changed a briefing after the customer clarified the question. Those are more informative examples than saying you “used threat intelligence tools” without explaining the resulting product.
Completed asset: the same packet, two finished briefs
The following exercise uses an invented company, Northbank Software, and a completely synthetic source packet dated October 21. No real organization or campaign is described. The packet stipulates three items: an advisory reports impersonation of software-support staff; a vendor note independently describes a similar social-engineering theme; an internal training summary records two employee reports that have not been validated as malicious.
The packet contains no confirmed compromise, actor identification, technical indicators or evidence of targeting Northbank specifically. Analyst Elena must answer a narrow question: should the technical team review relevant visibility, and what should leadership understand this week? She completes separate outputs instead of sending both readers the same source dump.
Finished technical brief — recipient: detection engineering lead. Two stipulated external sources describe a similar support-impersonation theme. The fictional employee reports are unresolved and do not establish local malicious activity. Assessment: the theme warrants a scoped review of whether existing reporting and investigation processes can distinguish expected support interactions from suspicious reports. Confidence is moderate in the theme's relevance, low in any claim of local targeting. Requested decision: assign an authorized owner to assess the visibility question and return the gaps; no new block or automated account action is requested. Elena owns the assessment; the engineering lead owns any subsequent technical evaluation.
Finished business brief — recipient: security director. The supplied packet describes a support-impersonation concern, but does not demonstrate a Northbank incident or an identified adversary. The immediate decision is whether to sponsor a limited review by the existing security team, not whether to announce a breach or purchase a platform. Assessment: approve that review within existing responsibilities and revisit after the unresolved reports have been assessed. The main uncertainty is local relevance; the next update should state whether usable evidence was found, whether visibility is missing or whether the question remains unresolved. No financial loss or prevention benefit is estimated.
The briefs agree on the evidence but serve different decisions. The technical reader receives a bounded investigation question and ownership boundary. The director receives the decision, uncertainty and update condition. Neither output exaggerates the packet into a named campaign or claims that a defensive change was implemented.
This is a completed writing and reasoning exercise, not a completed security investigation. In a portfolio, Elena would retain the synthetic-source label alongside both briefs. Removing that label would make the sample appear to document access or experience she does not have.

Completed asset: requirements, sources and confidence
A second fictional candidate, Marcus, is reviewing whether his security-operations background supports a CTI application. He has prepared incident handoffs and summarized vendor advisories. He has not owned a standing collection program or conducted restricted-community collection. He completes the matrix below for an invented identity-service provider, using only stipulated materials.
| Intelligence requirement and user | Selected material in this fictional exercise | Completed judgment and uncertainty | Finished handoff |
|---|---|---|---|
| Detection lead: does a reported behavior justify a visibility review? | One synthetic vendor advisory and an invented architecture summary | Relevant system category overlaps; no local evidence. Moderate confidence in relevance, no incident conclusion | Request a scoped review by the authorized telemetry owner |
| Security director: has exposure changed enough to reprioritize work? | The same advisory plus a fictional existing-risk register entry | Insufficient evidence of changed local exposure. Low confidence in a priority change | Keep priority unchanged pending the scoped review; record the missing evidence |
| Response lead: do two reports describe one activity? | Two synthetic case summaries with incomplete timing | Relationship unresolved; similarity alone does not establish linkage | Keep separate references and request clarification through the case owners |
| Intelligence manager: where is coverage missing? | The three completed question records above | Local applicability and timing are unanswered; this is a collection gap, not negative evidence | Add those questions to the next authorized collection discussion |
Marcus records a clear stopping point: no closed forums, private accounts, live targets or employer telemetry were accessed. The proposed follow-up is a question for an authorized team, not an activity he performed. The matrix is complete as a synthetic planning and assessment artifact even though its underlying intelligence questions remain unresolved.
His application decision is also finished. He will emphasize defensible case summaries and audience-specific advisory writing, and mark standing collection ownership as a gap. He will not represent the exercise as meeting ID.me's specified collection experience or Anthropic's production-engineering requirements. A suitably scoped role may value his background, but that must be established from its own description.
Confidence should explain the evidence
Confidence describes the strength of an assessment, not a promise that an event will or will not occur. State what supports the judgment, what weakens it and which missing observation could change it. A label without that explanation gives the reader little basis for deciding how much weight to place on the product.
In Marcus's matrix, “insufficient evidence of changed exposure” is not equivalent to “no threat.” The record lacks the evidence needed to resolve the question. Similarly, two reports with similar wording may have a common origin. Do not count them as independent support without checking their provenance.
In a real work example, explain how you handled disagreement or a correction. Did a reviewer challenge an assumption? Did new information narrow an attribution? Did the customer need a different time horizon? Updating a judgment accurately can demonstrate analytical discipline; insisting that the first version was certain cannot substitute for evidence.
Match your evidence to the actual responsibility
General security operations can provide relevant investigative experience, but a case closure and an intelligence product answer different questions. A case may establish what happened within a defined event. An intelligence assessment may connect several sources to a broader requirement, identify an information gap and brief a recipient who owns the resulting decision. Some jobs combine those activities.
Prepare one example that names its requirement, sources, evaluation, judgment, recipient and feedback; state explicitly if feedback was never received. State whether you owned the work, contributed a section or only consumed someone else's report. If you built automation, explain the maintained output and review process; if you wrote the assessment, explain the reasoning rather than borrowing the engineering claim.
Keep the sample shareable. Do not take proprietary reports, customer identities, private messages or source-access details into an application. A clearly fictional reconstruction can preserve analytical structure while avoiding a false claim to confidential experience. Follow the employer's application instructions and state how the sample was produced.
Questions to settle before prioritizing a role
Ask who sets intelligence requirements, which recipients use the output and how they give feedback. Ask whether the job independently owns collection, writes assessments, builds pipelines or performs several of those tasks. Clarify expected collection environments, authorization and supervision without requesting sensitive sources or operational methods.
Before tailoring an application, check seniority, location, travel and any access conditions separately from subject-matter interest. Being interested in threat actors does not establish technical collection or finished-product experience. Conversely, strong analytical writing can be valuable when the role actually calls for it and the remaining requirements fit.
Browse recent roles on LandOffer.ai, then compare one complete employer description with an evidence chain you can explain. Apply, clarify a material requirement or choose a closer match based on the work and its users, rather than the title alone.
Sources and Further Reading
- Anthropic: Security Engineer — Threat Intel: US engineering-oriented intelligence example and opening-specific requirements.
- ID.me: Senior Threat Intelligence Analyst: requirements, collection, finished assessments and stakeholder use.
- NIST SP800-150: Guide to Cyber Threat Information Sharing: official publication record, full abstract and scope.


