Request talent
Expertise
PolicyCenter DevelopersClaimCenter DevelopersBillingCenter DevelopersIntegration DevelopersGuidewire Cloud TalentNICE Actimize TalentDuck Creek TalentSAS Financial Crime TalentFinancial Crime Technology
Solutions
Solutions for InsuranceBanking & Financial Services
Staffing Models
Contract StaffingContract-to-HireDedicated Technology TeamsProject Team Staffing
Insights
BlogAbout Us
Contact Us
Request talent
SAS Financial Crime

SAS Financial Crime Talent Who Can Both Code and Defend the Model

Hire AML detection, tuning, case management, data and platform specialists across SAS financial crime estates. The scarce combination here is a genuine SAS programming background alongside financial crime domain judgement — and that is exactly what we screen for.

Share Your RequirementSee the Profile Shapes We Place

For banks, payments firms and SAS delivery partners. Contract, contract-to-hire and dedicated pods.

What a SAS Brief Usually Looks Like

Live demand
Roles
AML developer, scenario and tuning specialist, case management configurator, SAS data engineer, platform engineer
Core stack
Base SAS and macro, SQL, data integration tooling, scenario administration, case management, Viya or SAS 9 platform
Typical trigger
A tuning or optimisation cycle, a regulatory finding, a Viya migration, or thin platform administration cover
Engagement
Contract · Contract-to-hire · Dedicated team · Project pod
Working models
Onsite, hybrid, offshore, or blended with your existing squad
Send us a JD or a rough outline —start a requirement.
Coverage
  • AML detection
  • Tuning
  • Case management
  • Fraud & real-time
  • Data & SAS programming
  • Platform & Viya
Why This Role Is Hard to Fill

The Market Has SAS Programmers and Financial Crime People, Rarely Both

SAS estates reward engineers who are genuinely comfortable in code — Base SAS, macro, heavy SQL and data integration work sit under the solution layer. Financial crime hiring, meanwhile, prizes typology and tuning judgement. Candidates usually arrive strong in one and thin in the other, and briefs rarely say which one they actually need.

So we ask first and screen accordingly. If the work is scenario and tuning, we prioritise domain judgement and defensibility. If it is data, integration or platform, we prioritise engineering depth. Where you genuinely need both in one person, we say what that costs and how long it takes to find, rather than sending compromises and hoping.

All Expertise
  • SAS Analytics Background, No Financial CrimeStrong SAS programmers from reporting or risk analytics roles who have never worked a detection scenario or a tuning cycle.
  • Financial Crime Background, No SASGood domain candidates who will need months before they can work confidently in the code and data layer.
  • Platform Version MismatchSAS 9 and Viya estates differ in tooling, deployment and administration. We check which the experience came from.
  • Administration Under-ResourcedPlatform, environment and job scheduling ownership is routinely absorbed by developers who have other work to do.
  • Tuning Without DefensibilityThreshold work with no sampling method or documentation creates a finding rather than an improvement.
Roles We Staff

The SAS Financial Crime Roles Banks Ask Us For

Mix and match into a squad, or add one specialist to a team you already have.

SAS AML Developer

Most Requested

Configures and extends detection on the AML solution, comfortable in both the solution layer and the code beneath it.

  • Scenario config
  • Base SAS
  • Macro
  • SQL

Scenario & Typology Specialist

Designs and amends detection for new products, markets and typologies, then proves behaviour.

  • Typologies
  • Scenario design
  • Backtesting

Tuning & Optimisation Analyst

Above and below-the-line testing, segmentation review and the evidence pack behind each change.

  • ATL / BTL
  • Sampling
  • Evidence

Case Management Configurator

Case types, workflow, queues, forms and investigator experience on the SAS case tooling.

  • Case types
  • Workflow
  • Queues
  • Forms

SAS Data Engineer

Source feeds, mappings, reference data and the reconciliation that proves nothing was dropped.

  • Data integration
  • Base SAS
  • SQL
  • Reconciliation

Fraud & Real-Time Specialist

Real-time payment fraud detection, decisioning performance and channel coverage on SAS fraud tooling.

  • Real-time
  • Latency
  • Channels

SAS Platform & Viya Engineer

Environments, job scheduling, deployment, performance and migration between platform generations.

  • Administration
  • Viya
  • Scheduling
  • Migration

Model Validation & QA

Independent challenge of detection and tuning, regression across change, and pre-audit evidence.

  • Validation
  • Regression
  • Audit readiness
What We Screen For

The Capability Grid Behind Every Shortlist

Requirements get mapped against this grid before we send anyone, so you can see depth by area instead of reading it out of a CV.

AML DetectionThe solution layer
  • Scenario configuration
  • Scenario administration
  • Risk factors
  • Segmentation
  • Alert generation
  • Suppression logic
  • Customer due diligence
  • Watch list screening
Tuning & Model GovernanceThe part that gets reviewed
  • Above-the-line testing
  • Below-the-line testing
  • Threshold analysis
  • Sampling methodology
  • Model documentation
  • Validation support
  • Regulator and audit response
SAS Programming & DataWhere SAS estates differ from the rest
  • Base SAS
  • SAS macro
  • Advanced SQL
  • Data integration tooling
  • Feed design & mapping
  • Reference data
  • Completeness controls
  • Performance tuning
Case ManagementWhat the investigator works in
  • Case & alert types
  • Workflow states
  • Queues & routing
  • Forms & field logic
  • Roles & permissions
  • Audit trail
  • Reporting & MI
Fraud & Real-TimeA different constraint entirely
  • Real-time decisioning
  • Latency budgets
  • Payment channels
  • Rule and model deployment
  • Throughput at peak
  • Incident response
Platform, Viya & DeliveryVersion currency and administration
  • SAS 9 estates
  • Viya estates
  • Platform migration
  • Environment management
  • Job scheduling
  • Deployment & release
  • Capacity & performance

Platform-agnostic briefs are staffed from the discipline practices — see AML, transaction monitoring and fraud talent.

Engagement

Four Ways to Bring SAS People On

Compare all models

Contract Staffing

Named specialists for a defined period — a tuning cycle, a migration wave, administration cover.

A known gap with a known end dateDetails

Contract-to-Hire

Work together first, convert to permanent once the fit with your compliance team is proven.

Building permanent SAS capabilityDetails

Dedicated Technology Teams

A standing pod that owns detection change, tuning cycles and the platform underneath.

Detection change never really stopsDetails

Project Team Staffing

A scoped outcome — a Viya migration, a model overhaul, a regulator-driven remediation.

Defined scope with a delivery dateDetails
How We Get to a Shortlist

Screening, in the Order It Happens

Four steps, and you hear from us at each one.

  1. 1

    Requirement Intake

    Which solutions, SAS 9 or Viya, whether the role is domain-led or engineering-led, and who signs off model change.

  2. 2

    Specialist Screening

    A reviewer with financial crime background probes both sides: detection owned, and how comfortable the candidate really is in code.

  3. 3

    Shortlist With Notes

    Profiles arrive with SAS engineering depth and financial crime judgement rated separately, plus notice period and rate.

  4. 4

    Interview and Onboard

    We coordinate panels, handle paperwork and stay involved through the first weeks on your estate.

Profile Shapes

What a SAS Shortlist Tends to Contain

Representative profile structures for the three most common briefs.

Senior SAS AML Developer

Detection and code · multi-solution

  • Owned scenario configuration on a live AML estate
  • Fluent in Base SAS, macro and heavy SQL
  • Has taken detection change through model governance
  • Comfortable debugging in the data layer, not just the solution

Tuning & Optimisation Analyst

Model governance facing · statistical background

  • Ran above and below-the-line testing end to end
  • Segmentation review with documented rationale
  • Reduced false positives without losing coverage, and can prove it
  • Evidence packs that survived validation and audit

Platform & Migration Engineer

SAS 9 toward Viya · administration-led

  • Owns environments, scheduling and deployment
  • Has worked a platform migration between generations
  • Performance and capacity tuning on large data volumes
  • Keeps detection running while the platform moves underneath it

These are representative profile structures, not live availability. Current availability, notice periods and rates are shared against a specific requirement.

Before You Send a Brief

Questions We Get Asked

Do we need SAS programming skills or financial crime knowledge?

It depends on the role, and it is the first thing we establish. Scenario and tuning work leans on domain judgement; data, feed and platform work leans on engineering. We rate the two separately on the shortlist rather than averaging them into a single impression.

Would a SAS programmer from a risk or reporting background work?

For data and platform roles, often yes. For detection and tuning roles the domain gap is real, and we would tell you what the ramp-up looks like rather than presenting it as a straight fit.

We are migrating to Viya. Does that change the profile?

It does, particularly for platform and administration roles where tooling and deployment differ between generations. We check which estate the experience came from and flag it on the shortlist.

Can you cover other financial crime platforms too?

Yes — see NICE Actimize talent for vendor-specific briefs, or the discipline pages if you are platform-agnostic: AML, KYC, transaction monitoring and fraud.

Can you staff platform administration on its own?

Yes, and it is worth briefing separately. Administration is routinely absorbed by developers who then have less time for detection work, which slows both.

What do you need from us to start?

A JD if you have one. If not: which solutions, SAS 9 or Viya, whether the role is domain or engineering-led, seniority, engagement type and location expectations.

Request Talent

Tell Us What Your SAS Estate Needs

Send a JD or a two-line outline. We come back with the roles that fit, what the market looks like for them, and a shortlist against your requirement.

For Hiring Teams

Send the solution, the platform generation and the start date.

Request Talent

Send Your Requirement

Two minutes now, a shortlist conversation next.

No profiles shared without a right-to-represent conversation first.

Protected by reCAPTCHA. Google's Privacy Policy and Terms of Service apply.