Staff Software Engineer (Payments) - MLabs - Application

Autofill application

Save time by importing your resume in one of the following formats: .pdf, .doc, .docx, .odt, or .rtf.

* Required fields

Personal information

Clear

*****First name

*****Last name

*****Email

Photo (Optional)

Choose file or drag and drop here

*****Resume

Choose file or drag and drop here

Cover letter (Optional)

*****Deep AWS Expertise: Extensive production experience across core compute, networking, storage, and security services.

YES

NO

*****Strong Backend / Systems Engineering: Proven track record of building high-performance, critical infrastructure. Deep experience in Rust is highly advantageous, but strong engineers from other systems backgrounds (such as Go, C++, or Java/Scala) who can rapidly adapt to Rust will be fully considered.

YES

NO

*****Distributed Systems Expertise: Thorough understanding of consistency models, idempotency, fault tolerance, and sagas, with experience designing systems that remain correct under partial failure conditions.

YES

NO

*****Financial or Transactional Rigor: Prior experience in payments, fintech, high-throughput transaction processing, or another domain where system correctness is vital and "mostly works" is unacceptable.

YES

NO

*****Advanced Database Fundamentals: Deep knowledge of transactions, indexing, query/caching strategies, event streaming, and a strong respect for auditability and reconciliation.

YES

NO

*****Security-First Instinct: Natural adherence to secure engineering practices, including secrets hygiene, least-privilege access, and maintaining clean audit trails.

YES

NO

*****Autonomy & Leadership: Ability to make high-impact technical decisions independently, navigate ambiguity comfortably, and execute both high-level design and necessary reliability work.

YES

NO

*****Deep Rust experience, open-source contributions, or performance optimization skills (profiling, reducing allocations, lock-free structures).

YES

NO

*****Domain depth in payment rails (card networks, bank rails, chargebacks, open banking) or accounting fundamentals (double-entry ledgers, regulatory reporting).

YES

NO

*****Experience building risk, fraud, or compliance infrastructure (rule engines, device fingerprinting, sanctions screening, KYC/AML workflows).

YES

NO

*****Familiarity with crypto, Web3, or on-chain infrastructure (wallet infrastructure, stablecoin flows).

YES

NO

*****A background in platform engineering, cloud infrastructure, or observability.

YES

NO

*****Financial Services Background: Proven track record at a neobank (e.g., Monzo, Revolut), PSP (e.g., Stripe, Adyen, Checkout.com), or a major bank’s infrastructure division.

YES

NO

*****IaC & Containers: Mastery of Terraform at scale and strong experience with Kubernetes (EKS) or ECS operations.

YES

NO

*****Database & Messaging: Experience running RDS/Aurora PostgreSQL for transactional workloads and operating Kafka (MSK) or Kinesis for financial event pipelines.

YES

NO

*****Compliance Literacy: Familiarity with the infrastructure obligations of PCI DSS, SOC 2, or FCA/PRA regulated environments.

YES

NO

*****Operational Maturity: Experience in 24/7 on-call rotations for financial systems with a focus on incident response and post-mortems.

YES

NO

*****Preferred Qualifications: Experience with Solana or EVM blockchain infrastructure, policy-as-code (OPA), or FinOps certifications. Proficiency in Rust, Python, or Go for tooling is a significant plus.

YES

NO

*****1) LinkedIn URL 2) Current Location 3) Expected salary in USD per year 4) Preference for remote/hybrid/on-site/no preference 5) Please confirm your work authorisation 6) Please confirm when you are available to start a new position (e.g 1 month notice)