Payabli · miami, FLremote

Salary
Posted
Jul 13, 2026
Location
miami, FL
Last confirmed open
Jul 21, 2026

What this job asks for AI summary

A backend engineering role focused on building and maintaining the services that sit between complex financial infrastructure and end users — covering payment routing, connector management, token intelligence, and platform configuration. The work involves designing secure, high-volume APIs and distributed systems using C# and .NET, with additional responsibilities around mentoring engineers and contributing to architectural decisions. Best suited to engineers with a background in payments or fintech.

Senior level · 5+ years · Remote · Full-time

Must have (8)
C#.NETRESTevent-driven architecturerelational databasesdistributed systemscloud platforms, AWS, Azure or GCPpayments / fintech

“or” means any one of them counts — you don't need all of them.

Posted 2 times — it's one opening, so apply once.

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

Roughly 28,500 people nationally plausibly meet what this posting asks for (software developers). range 12,000–42,700

Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.

What gives you an edge
event-driven architecture12%

Rare in this occupation — lead with these, and say what you built with them.

What won't set you apart
relational databases51%cloud platforms50%

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

What the occupation pays Median $138,970 (middle half $107,524–$175,762).

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 (6)

No specific cloud platform is named in the JD — the requirement is stated generically as 'cloud-based applications'; AWS, Azure, and GCP are listed as the well-known interchangeable alternatives.

The JD does not name a specific relational database product (e.g. PostgreSQL, SQL Server); the requirement is captured at the category level as stated.

Payments/FinTech domain experience is explicitly called out as a hard requirement ('Strong experience in Payments, FinTech, or other high-volume transaction processing environments') but names no specific tool or platform, so it is captured as a domain skill rather than a named technology.

No compensation figures are disclosed; salary is described only as 'competitive'.

The posting explicitly states 'Principals only — no external agency submissions.'

Caller marked this a fully-remote role — scored against the national candidate pool.

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 ↗