Miami, FL

Salary
Posted
Jul 14, 2026
Location
Miami, FL
Last confirmed open
Jul 21, 2026

What this job asks for AI summary

This role focuses on payments industry domain expertise, covering card products, transaction lifecycles, retail and aviation card programs, and regulatory compliance. Day-to-day work involves translating business requirements into functional specifications, identifying gaps between current and target-state product features, and supporting system migration planning on Azure-hosted, API-driven platforms. It suits an experienced professional comfortable bridging business and technical stakeholders in enterprise-scale payment environments.

Senior level · 8+ years · National

Must have (7)
payment systemsAzureSQLRESTcard productsmerchant onboardingregulatory compliance

We read this from the posting text with AI. Skim the description below before ruling yourself out.

How this req sits in the market our data

What won't set you apart
SQL60%

Most people in this occupation already list these. Still required — just not what gets you shortlisted.

What the occupation pays Median $108,178 (middle half $84,682–$137,059).

Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.

Why we read it this way (5)

Location is not specified anywhere in the posting — CBSA and state are left blank. The role references 'workshop sessions' participation, suggesting some on-site or hybrid presence, so remote=false is a reasonable default but the posting is genuinely ambiguous.

The role blends business analysis (translating requirements, gap analysis, stakeholder communication) with deep payments domain knowledge. It sits most naturally at 15-1211 Computer Systems Analysts; 15-1299 is noted as a runner-up given the strong domain/consulting flavor.

Azure, SQL, and API-driven platforms are listed as systems the candidate must understand ('function of systems similar to those in the architecture'), not necessarily build — they are framed as required domain context within the job description body, which reads as a requirements block.

No compensation, employment type, or degree requirement is stated in the posting.

'Regulatory compliance' and 'merchant onboarding' are domain knowledge areas explicitly called out in the requirements body; they are retained as named domain skills rather than generic concepts because the posting specifically gates on payments regulatory and POS/settlement process knowledge.

Read the full posting

The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.

Apply

Apply on employer site ↗