Engineers who build payment systems that hold up under audit.

The Role

Remote contract role helping build NXOPAY's next-generation payment platform.

You'll own core payment processing pipelines, voucher network logic, ledger consistency under concurrency, and PSP integration layers. Day-to-day you'll design distributed state machines, debug race conditions, write idempotent APIs, and operate services end-to-end — from schema to Kafka consumer to Prometheus alert. You'll work against a precise technical spec with a small, highly technical team, and you'll be expected to push back when the spec is wrong.

Engagement

• Contract-based, full-time hours (40 hours/week)
• Initial contract: 3 months, with strong likelihood of extension based on performance and roadmap
• Remote; open to candidates based in Pakistan, India, Thailand, or Eastern Europe
• Working hours must overlap 14:00–18:00 GMT+4 daily (minimum 4 hours)

What We're Looking For

• 6+ years of production Java (Java 21, Spring Boot 3.x, Hibernate / JPA)
• Hands-on production experience with PostgreSQL 15+, Redis 7+, and Apache Kafka — not side-project exposure
• Proven experience building or debugging financial systems, or comparable high-stakes domains (trading, clearing/settlement, core banking, exchanges, high-throughput transactional systems)
• Strong grasp of idempotency, transaction isolation, outbox pattern with Kafka relay, and graceful failure modes in distributed systems
• Production experience with the Spring Boot stack used at NXOPAY: spring-boot-starter-kafka, spring-boot-starter-data-jpa with auditing, spring-retry, micrometer-registry-prometheus, Flyway for schema migrations
• Docker and Kubernetes in AWS production environments (Kustomize or Helm for environment overlays a plus)
• Comfortable working against a detailed technical spec and verifying that implementations — your own or otherwise — hold up under scrutiny
• Able to discuss real architectural trade-offs (Spring vs. Quarkus, sync vs. async ledger writes, at-least-once vs. effectively-once delivery) without dogma
• Payments domain experience strongly preferred, especially direct acquirer or gateway integrations (MPGS, Adyen Platform, Checkout.com, or similar). Comparable complexity in other domains is acceptable.
• Excellent written English — most collaboration is async

How to Apply

Tell us about the most complex distributed system you've personally built or debugged — what failed, what you changed, what you'd do differently now.

The Role

Remote contract role owning NXOPAY's platform and infrastructure layer on AWS (me-south-1).

You'll set up, automate, and operate everything that isn't application code: cloud infrastructure, Kubernetes clusters with Kustomize overlays across dev / staging / production, RDS PostgreSQL, Kafka, Redis, NGINX ingress, External Secrets Operator integration with AWS Secrets Manager, GitLab CI pipelines, observability (Prometheus + Grafana + structured logs), and developer tooling. You'll work closely with a small, highly technical engineering team building ten Spring Boot microservices that must hold up under regulatory audit.

Day-to-day you'll write Terraform, debug Kubernetes issues at the cluster level, keep Kafka healthy (consumer lag, DLQ monitoring, partition sizing), optimize CI/CD pipelines, build internal tooling that saves the team hours, and keep the platform within cost, compliance, and performance boundaries. You'll be responsive to the engineering team during working hours and expected to make architectural trade-offs deliberately and document them.

Engagement

• Contract-based, full-time hours (40 hours/week)
• Initial contract: 3 months, with strong likelihood of extension based on performance and roadmap
• Remote; open to candidates based in India or Eastern Europe
• Working hours must overlap 14:00–18:00 GMT+4 daily (minimum 4 hours)

What We're Looking For

• 6+ years of production DevOps, SRE, or platform engineering experience
• Deep production experience with AWS — EC2, VPC networking, RDS PostgreSQL, Secrets Manager, IAM, CloudWatch
• Deep Kubernetes experience in production, including Kustomize or Helm overlays for environment separation
• Terraform at scale: modules, remote state, drift detection, CI-integrated workflows
• Hands-on operation of Apache Kafka in production — consumer lag, partition strategy, DLQ handling, upgrade paths
• Observability stack: Prometheus, Grafana, structured logs. Experience defining meaningful SLOs/SLIs, not just dashboards.
• CI/CD with GitLab CI — including pipeline design, caching, matrix builds, environment gates with approval flows, secure secret handling via OIDC federation to AWS, and audit-trail-friendly deployment controls. GitLab Security Dashboard, OWASP Dependency Check, or Snyk integration a plus.
• External Secrets Operator (or equivalent patterns for injecting cloud-managed secrets into Kubernetes workloads) in production
• Solid Linux systems, networking (VPCs, peering, private service access), and low-level debugging when needed
• Experience in regulated environments (payments, banking, fintech, healthcare) strongly preferred — you understand that compliance is cultural, not checkbox
• Ability to discuss real architectural trade-offs (self-hosted vs. managed, GitOps vs. push deploys, Kustomize vs. Helm) without dogma
• Excellent written English — most collaboration is async

How to Apply

Tell us about the most challenging infrastructure migration or production incident you've personally led — what broke, what you changed, what you'd do differently now.

The Role

Remote contract role owning test engineering for NXOPAY's payment platform — a stack of ten Spring Boot microservices handling payments, vouchers, ledger consistency, reconciliation, and PSP integration under regulatory audit.

You will design and build the full test pyramid: unit, integration, contract, and end-to-end tests. You own the Sprint gate evidence — no sprint proceeds to the next without your test suite passing against documented acceptance criteria. You will work from a detailed technical specification alongside a small, highly technical team and will be expected to push back early when a service's testability is weak.

Day-to-day you will write integration tests using Spring Boot Test + Testcontainers (real PostgreSQL, Kafka, and Redis — no mocks for infrastructure), build E2E harnesses for complete payment and voucher flows against the EazyPay sandbox, implement contract tests for Kafka event schemas, run security scans, and produce clear, audit-ready evidence artefacts.

This role starts at Sprint 2 and runs through Sprint 4 go-live. Performance and load testing are out of scope for this engagement.

Engagement

• Contract-based, full-time hours (40 hours/week)
• Initial contract: 3 months, starting at Sprint 2, with strong likelihood of extension based on performance and roadmap
• Remote; open to candidates based in Pakistan, India, Thailand, or Eastern Europe
• Working hours must overlap 14:00–18:00 GMT+4 daily (minimum 4 hours)

What We're Looking For

• 6+ years of production test engineering experience on Java backends (not manual QA with light automation)
• Payments domain experience required — you have personally tested end-to-end payment flows, ledgers, or PSP integrations in production. Comparable experience in core banking, clearing/settlement, or exchanges is acceptable.
• Strong JUnit 5 + Mockito for unit testing
• Production experience with Spring Boot Test + Testcontainers using real PostgreSQL, Kafka, and Redis
• Spring Cloud Contract or equivalent for consumer-driven contract testing of Kafka event schemas
• Solid understanding of testing distributed systems: idempotency, outbox pattern, retry logic, race conditions, and event ordering
• Experience building E2E test harnesses for regulated financial flows (success, decline, failure, and exception paths) tied to acceptance criteria
• OWASP ZAP or equivalent security scanning (auth bypass, injection, IDOR) against APIs
• Ability to produce audit-ready evidence: test reports, coverage metrics, and traceability matrices
• Git + GitLab CI for integrated test workflows and flaky test management
• Ability to discuss real testing trade-offs (integration vs. E2E coverage, contract tests vs. shared fixtures, when to use Testcontainers vs. mocks) without dogma
• Excellent written English — test reports and evidence are the primary collaboration medium

How to Apply

Tell us about the most complex financial or transactional flow you've personally tested end-to-end — what you covered, what you caught before production, and what slipped through (and how you closed the gap).