New Wave Devs

We're hiring a Senior Software Engineer to join us for a long-term engagement with a fast-growing UK travel tech client. The role focuses on owning and evolving their production document AI pipeline (OCR plus ML inference on passport and ID documents, CPU only deployment, no GPU).

This is hands-on production engineering, not research. You'll be improving OCR accuracy, optimizing CPU inference (INT8 quantization, ONNX Runtime, batching), refactoring pipeline complexity, and improving observability of a system serving enterprise clients at scale.

What you'll do:

• Take ownership of the existing OCR and document understanding pipeline in Python
• Optimize ML inference for CPU production (ONNX Runtime, quantization, batching, kernel tuning)
• Improve OCR accuracy, latency, throughput, and memory efficiency
• Refactor architectural complexity and reduce technical debt
• Work across ML systems, backend services, APIs, and data pipelines
• Help shape architectural decisions as the platform scales

Required:

• 5 plus years of professional Python software engineering
• Strong experience with OCR and document processing pipelines
• Familiarity with LayoutLMv3, Doctr, PaddleOCR, EasyOCR, Donut, or DocFormer
• Production ML systems experience (not just notebook experimentation)
• ONNX Runtime, quantization, TorchScript, or related CPU inference optimization
• Strong understanding of PDFs, image preprocessing, bounding boxes, and page segmentation
• Experience with systems serving external customers at scale

Nice to have:

• HuggingFace Transformers production experience
• Enterprise SaaS or aviation/travel tech background
• MLflow, Vertex AI, or similar ML operations tooling
• Distributed systems and backend API design experience

Engagement:

• Fully remote
• Long-term (6 plus months) with potential to expand engineering ownership over time
• Part-time (25-30 hrs/week) or full-time (35-40 hrs/week), depending on candidate availability
• Flexible timezone (engagement requires some overlap with UK working hours)

How to apply:
Send a short note covering relevant OCR / document AI work, production ML systems you've shipped, CPU inference optimization experience, GitHub or LinkedIn, current availability, and timezone.

We are a US-registered outstaffing partner. We embed senior engineers into product teams across fintech and payments. Sourcing now for a near-term client engagement in the cross-border crypto-fiat space.

This role is engineering-hands-on. You will own the KYC/KYB onboarding flow architecture for high-AOV merchants in a production environment. Not project management, not consulting.

Required (must have shipped in production):
- KYC or KYB onboarding flows in fintech, payments, or crypto
- At least 2 verification provider integrations from: Onfido, Sumsub, Persona, Alloy, Middesk, Veriff, Jumio
- Backend in Node.js (NestJS, Express) or Python (FastAPI, Django)
- Manual review queues or automated decisioning logic
- Scale context (transactions per day, merchants onboarded, time-to-activate metrics)

Nice to have:
- Cross-border payments or crypto-fiat (TransFi, BitPay, CoinsPaid, OpenPayd, Reap landscape)
- AML / transaction monitoring
- Multi-jurisdictional compliance (GCC, LATAM, SEA, EU)
- VARA, CBUAE, FATF Travel Rule familiarity

Terms:
- Remote, EU or Eastern Europe timezone (must overlap UAE/GCC business hours)
- Start: as soon as we mutually confirm fit
- Embedded model: you work alongside the client's team with full ownership of your scope

To apply, reply with these specifics (generic CVs will not move forward):
1. CV
2. One concrete KYC or KYB onboarding flow you personally coded — architecture, providers integrated, scale, your role in it
3. Programming languages and frameworks you use day-to-day
4. Current availability (hours per week) and earliest start date
5. GitHub or public portfolio if available

Looking for engineering depth, not implementation oversight.

About the role

We are sourcing a senior payments engineer for a US fintech client running a number of card tokenization deployments. The work centers on Mastercard Digital Enablement Service (MDES) and Visa Token Service (VTS) integrations — payment credential tokenization, lifecycle management, network certification, and supporting infrastructure for fintech rollouts.

This is not a generic "fintech experience" role. We are specifically looking for engineers who have shipped MDES or VTS in production, ideally at a card issuer, processor, or BaaS platform.

What you will work on

Card network tokenization flows (MDES and/or VTS) Token provisioning, lifecycle, and de-tokenization Network certification and compliance work Integration with card management systems, HSMs, and issuer/processor APIs Cross-functional work with payments product, risk, and infrastructure teams

Required

5+ years in payments engineering Production experience with MDES or VTS (not adjacent, not "exposure" — actual ship-to-prod work) Strong backend engineering (Java, Go, Python, or Node.js depending on stack) Familiarity with PCI DSS scope, HSM integration patterns, tokenization standards Comfortable working directly with a US-based product team in their working hours (some overlap required)

Nice to have

Background at Mastercard, Visa, Marqeta, Galileo, Stripe Issuing, Adyen, Thredd, GPS, Worldpay, Fiserv, or a similar issuer/processor/BaaS EMV / 3DS / ISO 8583 working knowledge Experience with Apple Pay / Google Pay / Samsung Pay provisioning flows Card issuing background (BIN sponsorship, KYC integrations, dispute flows)

Engagement details

Start: ASAP (within 2-3 weeks of selection) Duration: Multi-deployment scope, initial commitment 3-6 months with strong likelihood of extension Mode: Embedded full-time (40h/week) or senior project consulting (20-30h/week) depending on your availability Working hours: Some overlap with US Eastern timezone required (at least 3-4 hours)

How to apply

Reply with your CV and a short note covering:

1. The specific MDES or VTS production work you have shipped (network, issuer, processor, what role you played)
2. Your current availability and earliest possible start date

Thank you.