Trust
Methodology
Every number on this site is computed from data we hold, from sources we can name. Where a figure would require an estimate, we publish nothing instead. This page states exactly how each surface is built.
01 · Where the jobs come from
Roles are collected directly from employer career-site APIs and portals — the standard applicant tracking systems used across financial services, including Greenhouse, Lever, Workday, Oracle, SuccessFactors, iCIMS and others — plus two licensed aggregator feeds that extend coverage into smaller employers and agency-managed hiring.
The index refreshes daily at 06:30 ET. Every listing links to the employer's own apply page; we never place ourselves between a candidate and the employer's process. A role that has not been seen in a source for seven consecutive days is marked expired and drops out of the active index.
02 · Classification
Roles are classified title-first: the posting title is matched against rules built for this profession, not a general taxonomy. Where a title is ambiguous, a conservative description rescue looks for unambiguous signals in the body text.
Roles that cannot be confidently classified are excluded from discipline surfaces rather than guessed into one. A smaller honest index beats a larger noisy one.
03 · Compensation
Posted pay is only ever employer-disclosed: ranges parsed from the posting itself, with a currency symbol required before a figure is accepted. Nothing is inferred from title, location, or employer size.
Community submissions are a separate dataset, shown separately, and only surfaced once a cell holds at least five approved submissions. Every submission is moderated before it counts. We never estimate or model pay.
04 · Enforcement data
Remediation Watch reproduces public actions from primary federal and state sources only — the Federal Reserve, OCC, FinCEN, CFPB, NYDFS, FCA, SEC and FDIC. Each action links to the official document so you can read the source rather than our summary.
Linking an action to an employer uses conservative whole-name matching and is reviewed by hand. Where a match is uncertain, the action stays unlinked.
05 · Demand radar
The radar counts a curated vocabulary of platforms, skills and certifications using word-boundary matching over live postings, so "Actimize" is counted and incidental substrings are not.
Vendor self-postings are excluded from demand counts: a vendor hiring for its own product does not constitute market demand for that product.
06 · Fit scores and resume analysis
Fit scores are deterministic. The same resume and the same role always produce the same number, computed in your browser and your account against the live index — no model, no randomness, and every component of the score is shown to you.
Your resume text is private to your account. It is never sent to an AI model, never used to train anything, and is not visible to administrators; only the extracted signal profile is used for scoring and alerts.
07 · What we refuse to do
- We do not estimate salaries.
- We do not seed fake jobs, employers, reviews or submissions.
- We do not scrape ratings or reviews from other platforms.
- We do not count vendor self-mentions as market demand.