Kunai · Houston, TX

Salary
Posted
Jul 19, 2026
Location
Houston, TX
Last confirmed open
Jul 21, 2026

What this job asks for AI summary

This role sits on a team breaking apart legacy monolithic infrastructure — covering areas like money transfer, fraud detection, and settlement — into cloud-native services on AWS. Day-to-day work involves designing domain-driven microservices, building Kafka-based event pipelines, and handling data flows through S3, queuing, and Redis-based caching, primarily in Python. It suits engineers with hands-on experience at high transaction volumes who want to build new systems rather than maintain existing ones.

Senior level · National

Must have (4)
PythonKafka, AWS Lambda, Rabbitmq or PulsarRedis, Memcached or Hazelcastevent-driven architecture
Nice to have (1)
Claude

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

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 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
Python51%

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

Location is not stated anywhere in the posting — CBSA and state are left blank. Remote eligibility is also unstated; remote=false is a conservative default.

No overall years-of-experience figure is given; seniority is inferred from the scope: greenfield re-architecture of high-transaction-volume, mission-critical financial systems clearly targets a Senior engineer.

Kafka is listed with the qualifier 'or equivalent streaming/messaging platforms' — common substitutes are captured in alternatives; the streaming-pipeline capability itself is a hard gate.

Redis is listed with 'e.g.' framing, indicating it is the exemplar of an in-memory caching/matching requirement rather than the only acceptable tool — alternatives reflect that.

AI-assisted development (Claude) is framed as an openness/interest rather than a hard gate ('interest in and openness to'), so it is marked preferred.

Financial services / payments domain experience is explicitly called 'a plus' under the Why This Role section — preferred accordingly.

No compensation range is disclosed in the posting.

Ignored 2 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): microservices / domain-driven decomposition, financial services / payments domain.

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 ↗