Cyber Threat Intelligence Analyst, Scams (DC, MD, VA only)
TRM Labs · Washington, DC · 1 mo ago
RemoteRemoteInformation Technology$115k–$160k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities?, Requirements?, Qualifications?, Skills?, Benefits?, Pay?, Schedule? Only include sections that have real specific content.
We need to parse the job posting.
First, remove boilerplate: cookie/navigation/legal/EEO etc. Also remove application instructions, interview process, life at TRM, AI fluency, leadership principles, join our mission repeated, privacy policy, etc.
We need to keep substantive info: About The Role (description), The Impact You Will Have (list of bullet-like sentences), What We're Looking For (requirements), About The Team (team description), Team Operating Rhythms (maybe schedule? but it's about rhythms, not schedule), Join Our Mission (maybe mission statement but could be considered fluff). Also mention location requirement: Must be located in Washington, D.C./MD/VA area.
We need to decide sections: About the role (use
About the role
) containing prose from "About The Role" paragraph. Responsibilities: Could be derived from "The Impact You Will Have" bullet points (they are responsibilities). So we can make a- list.
Requirements: "What We're Looking For" list.
Qualifications: maybe same as requirements? Could combine but we need separate sections only if distinct content. The posting doesn't have separate qualifications beyond requirements. Could skip Qualifications.
Skills: maybe list of specific skills from requirements: infrastructure attribution, CTI tooling, detection logic, attribution tradecraft, etc. Could be part of Requirements.
Benefits: Not mentioned explicitly. No benefits described. So skip Benefits.
Pay: Not mentioned. Skip.
Schedule: Not mentioned explicitly; Team Operating Rhythms mentions weekly syncs, daily async standups, primary time zone overlap US Eastern/Central, surge availability expected during time-sensitive disruption windows. That could be considered schedule info. Could create a Schedule section with those details.
But we must not create sections with filler like "not specified". The schedule info is specific: weekly team syncs, daily async standups via Slack, primary time zone overlap US Eastern/Central, surge availability expected during time-sensitive disruption windows. So we can include Schedule.
Also About The Team could be a section: maybe "About the team". But we have only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use
for section headings (e.g. ...). Likely they expect only those headings. But we could also include About the team as a heading? Not in list. Safer to stick to allowed headings. However we have team info that is substantive; maybe we can fold into About the role or Responsibilities? Could incorporate into About the role paragraph? Might be okay to add a separate section like "About the team" but not in the list; risk of being considered not following instruction. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create any heading as long as it's meaningful. However they gave examples; we can use those. Safer to use those headings only. Thus we need to map content to those headings. We have About the role: we can put the paragraph about the Scam Disruption team and role description. Responsibilities: the impact bullet points. Requirements: the "What We're Looking For" bullet list. Skills: maybe extract specific skills from requirements: infrastructure attribution, CTI tooling, detection logic, attribution tradecraft, producing actionable intelligence, etc. Could list them. Schedule: from Team Operating Rhythms. We should not repeat job title as heading. We must not include Job ID/requisition numbers. We must preserve all substantive information; do not invent or summarize away detail. We need to ensure we don't lose any substantive info: Let's extract all substantive content. Original text (relevant parts): - "Build a Safer World. TRM Labs provides AI-powered intelligence solutions that help public and private sector agencies investigate and disrupt crime. TRM's platforms enable investigators to trace illicit activity, build cases, and construct operating pictures of threat networks. Leading agencies and businesses worldwide rely on TRM to make the world safer and more secure." This is introductory fluff but still substantive about company. Could be included in About the role? Might be considered boilerplate? It's not about the role but about company. Might be okay to keep in About the role section as context. However instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This intro is not boilerplate; it's company description. Could keep. - "About The Role The Scam Disruption team is TRM's tip of the spear against pig butchering syndicates, romance fraud networks, and investment scam operations that steal billions from victims each year. As a Cyber Threat Intelligence Analyst, you'll lead infrastructure-driven investigative work: pivoting from a single domain, IP, or certificate to the network behind it, following it to the money, and delivering actionable intelligence to law enforcement and government partners. You'll track scam infrastructure as it evolves, fusing technical, open-source, and on-chain data to build the operational pictures that help dismantle scam operations." That's role description. - "The Impact You Will Have Start from one indicator — a scam domain, IP, or certificate — and pivot across shared certificates, registrars, nameservers, hosting, and ASNs to map the wider infrastructure behind Southeast Asia scam operations, clustering one-off indicators into campaigns.Track campaigns as they evolve — new domains, hosting and registrar changes, certificate reuse — and stay on actors as they rebuild and re-register after takedowns and seizures, anticipating their next infrastructure.Drive attribution of threat actors by leveraging open-source and commercially available data.Fuse technical infrastructure with the on-chain picture — carrying an investigation from infrastructure through to the wallet, the laundering path, and the cash-out.Build clustering logic, detection rules, and automation or tooling to surface malicious infrastructure proactively, rather than waiting on off-the-shelf feeds.Produce defensible, calibrated assessments — assigning confidence, weighing evidence across sources, and standing behind a malicious-versus-benign call.Synthesize on-chain and off-chain intelligence (OSINT, technical, and financial) into targeting packages that a government or law-enforcement consumer can act on.Own the intelligence cycle end to end with minimal supervision, partnering with the Scams SME team and with data, engineering, and product to sharpen TRM's collection capabilities." These are responsibilities. - "What We're Looking For 5+ years of proven experience in cyber threat intelligence or threat infrastructure analysis roles (this is not an entry-level position).Hands-on infrastructure attribution: infrastructure pivoting and campaign tracking across shared certificates, registrars, nameservers, hosting, and ASNs — and a habit of thinking in campaigns, not isolated indicators.A track record of staying on an actor or campaign over time, including through takedowns and re-registration.Hands-on fluency with CTI tooling — passive DNS, WHOIS, certificate or Shodan-style fingerprinting, and phishing monitoring.Experience building detection and clustering logic, rules, or automation yourself — not just configuring vendor tooling.Attribution tradecraft: using open-source and commercially available data to drive attribution of threat actors.Demonstrated ability to produce actionable intelligence or targeting packages for a government, law-enforcement, or equivalent consumer who acted on them, and calibrated, defensible analytic judgment.Must be located in the Washington, D.C./MD/VA area (periodic in-person collaboration and travel may be required)" These are requirements. - "About The Team The Scam Disruption team operates within TRM’s Blockchain Intelligence organization, alongside threat intelligence analysts, on-chain investigators, and federal partnersAll-Source Investigators and Cyber Threat Intelligence Analysts are the operational core, converting strategy and tooling into prosecutable, actionable intelligenceDistributed team with an async-first approach via Slack and Notion, plus structured syncs for alignmentHigh autonomy, high standards, low bureaucracy — work directly with analysts, engineers, and customers who depend on your output" Team description. - "Team Operating Rhythms Weekly team syncs to align targeting priorities and review disruption opportunitiesDaily async standups via Slack on active work, returns, and target packages in flightPrimary time zone overlap: US Eastern / CentralAll output documented in Notion and TRM’s investigative toolsSurge availability expected during time-sensitive disruption windows" Schedule info. - "Join Our Mission We seek people whose work matters, who build with speed and rigor, and who take pride in protecting others through their craft. If you’re excited by TRM’s mission but don’t check every box, apply anyway. Build to protect civilization. Let’s do it together." Mission statement; could be considered fluff but maybe keep as part of About the role? Might be considered boilerplate? It's motivational. Might be okay to include in About the role? But we already have About the role content; we could add after. But we must not repeat job title as heading. We need to output only HTML fragment. Let's structure:
About the role
... (company intro + role description)
Responsibilities
- ... each bullet from Impact You Will Have
Requirements
- ... each bullet from What We're Looking For
Skills
- ... maybe list specific skills: infrastructure attribution, CTI tooling (passive DNS, WHOIS, certificate/Shodan fingerprinting, phishing monitoring), detection and clustering logic/rules/automation building, attribution tradecraft using OSINT/commercial data, producing actionable intelligence/targeting packages, calibrated analytic judgment, etc.
Schedule
- Weekly team syncs to align targeting priorities and review disruption opportunities
- Daily async standups via Slack on active work, returns, and target packages in flight
- Primary time zone overlap: US Eastern / Central
- All output documented in Notion and TRM’s investigative tools
- Surge availability expected during time-sensitive disruption windows