Software Architect, Backend Developer, Cloud Engineer - Software

A leading UAE‑based consumer technology company that builds the digital infrastructure of everyday life, focusing on AI‑powered fintech, communication, and digital services. Headquartered in Abu Dhabi.

We are at a critical juncture — building and scaling next‑generation payment systems across merchant acquiring and core payment processing, powering real‑time transaction flows at production scale. This high‑impact, cross‑platform role will own backend architecture, make authoritative technical decisions across multiple squads, and directly shape the technical direction of our payments platform.

• Platform Architecture & Ownership Architect and evolve systems spanning Merchant Management, POS, and eCommerce acceptance. Own the platform architecture across acquiring and adjacent payment services, design for high throughput, low latency, and production‑first reliability across authentication, clearing, settlement, and reconciliation flows.
• Technical Direction Across Squads Own technical architectural direction and design decisions across multiple engineering squads simultaneously. Lead and mentor a pod of engineers, owning design quality and delivery accountability while holding the full‑system perspective.
• Product & Business Alignment Work directly with Product Owners to translate product intent and regulatory requirements into technically sound, scalable, and auditable system designs, bridging the gap between what is asked and what should be built, and communicating clearly in both directions.
• Protocol, Integration & Hands‑on Engineering Define the integration architecture across card schemes, payment processors, and internal switching layers, setting technical standards for payment integration including ISO 8583 message design, inter‑service communication patterns using Dubbo or a comparable RPC framework, and how the acquiring service mesh connects and fails safely. Contribute to critical Java microservice components, lead code and architecture reviews, and resolve complex production issues.
• API & Event‑Driven Architecture Design REST/JSON APIs with strong emphasis on idempotency, fault tolerance, and exactly‑once semantics. Drive event‑driven flows using Rabbit
  
  MQ for transaction lifecycle events, downstream processing, and asynchronous workflows. Design Redis‑backed patterns for distributed caching, idempotency key management, rate limiting, and real‑time state, ensuring operability and diagnosability.
• AI‑Augmented Engineering Use Claude Code as the default AI coding assistant to support architecture reviews, code and test generation, runbook creation, log triage, and elimination of manual engineering toil. Automate aggressively: identify repetitive tasks and lead AI‑automation initiatives for the team.

• 12 to 15 years of backend or platform engineering experience, with a material portion spent building, owning, and operating production card payment systems at a licensed fintech, payment processor, acquirer, or financial institution, spanning architecture, delivery, and production ownership.
• Expert‑level Java and Spring Boot proficiency—microservices design, application framework, transactional integrity, service decomposition, and production API development. Expected to review and write code, not just approve designs, with strong testing literacy.
• Deep, production‑proven command of ISO 8583 and payment messaging with full transaction lifecycle knowledge—authorization, clearing, settlement—and sufficient protocol fluency to make authoritative architectural decisions. Prior experience with jPOS or equivalent switching framework is expected.
• Demonstrated experience integrating with payment gateways and processors
  —REST and ISO‑based integration, hosted payment pages, tokenization, EMV 3DS 2.x authentication, and back‑office reconciliation. Previous work with MPGS, Cybersource, or leading gateway integrations is a strong asset.
• Experience working with Rabbit
  
  MQ or Kafka message brokers—designing reliable transactional event flows, exchange/queue topology, dead‑letter queue strategies, and message acknowledgement patterns in a high‑volume payment environment.
• Worked with Dubbo or a comparable RPC framework (gRPC)—judgment on when RPC is appropriate over async messaging and design for service‑boundary failure isolation.
• Architect Leader
  —lead a pod of engineers by example, setting standards through solution design documents, Architecture Decision Records, and integration specifications, while presenting architecture trade‑offs to Product, Risk, and Compliance stakeholders.

• Java / Spring Boot
• ISO 8583
• jPOS
• MPGS / Cybersource / Payment gateway
• Rabbit
  
  MQ / Kafka
• Redis
• gRPC Framework
• REST APIs
• Microservices
• Git Lab / Git Hub
• MySQL / Mongo
  
  DB / Elastic Search

• Azure / AWS
• 3DS (EMV 3DS 2.x)
• EMV
• Tokenisation
• Visa / Mastercard Scheme Integration
• CI/CD
• TOGAF