Senior Python Engineer (Fintech / Payments / Digital Platforms / ERP / Fashion / Assessment Platform) – Remote

February 12, 2026
500,000 - 600,000 / month
Application ends: March 2, 2026
Apply Now

Job Description

KloudOpp Limited is seeking a highly experienced Senior Python Engineer with 10+ years of hands-on backend engineering experience to design, build, and scale mission-critical platforms across fintech, payments, digital banking, Web3, lending, ERP, commerce, and digital platforms. This role is deeply hands-on and delivery-driven, with ownership of production systems and responsibility for building secure, high-scale, cloud-native, event-driven architectures used in real financial workflows.

Key Responsibilities

  • Architect and build scalable, secure backend systems for fintech-grade workloads
  • Design and implement event-driven and serverless architectures across AWS and Azure
  • Build and maintain high-performance APIs using FastAPI or Django
  • Own database design, performance tuning, data integrity, and migrations across PostgreSQL and MongoDB
  • Implement message-driven systems using RabbitMQ and background workers
  • Write clean, testable, production-grade Python code aligned with Clean Architecture principles
  • Enforce engineering best practices including code reviews, CI/CD discipline, and architecture standards
  • Take ownership of system reliability, scalability, performance, and security in production
  • Mentor other engineers and raise overall engineering standards
  • Collaborate in an Agile delivery environment with clearly defined monthly milestones tied to business outcomes

Technology Stack

  • Backend: Python (3.10+), FastAPI, Django, async workers (Celery, RQ, or equivalent)
  • Databases: PostgreSQL (primary), MongoDB (unstructured or event data)
  • Cloud: AWS (EC2, S3, RDS, Lambda), Azure (App Services, Functions, Event Grid, Service Bus)
  • Caching: Redis
  • Messaging / Events: RabbitMQ (or Kafka, Azure Service Bus, or equivalent)
  • Architecture: Serverless, event-driven systems, microservices, Clean Architecture, API-first design

Requirements

  • Minimum of 10 years professional backend engineering experience
  • Deep mastery of Python in production environments
  • Strong experience building fintech, payments, banking, lending, or other high-scale platforms
  • Proven hands-on experience with PostgreSQL including schema design, transactions, performance tuning, and migrations
  • Practical experience with MongoDB for unstructured or event-driven data
  • Experience using Redis for caching and performance optimization
  • Experience implementing message-driven systems with RabbitMQ or similar brokers
  • Strong hands-on experience with AWS services including EC2, S3, RDS, and Lambda
  • Solid understanding of Azure serverless and event-driven services such as Functions, Event Grid, and Service Bus
  • Strong grasp of distributed systems, event-driven design, microservices, and Clean Architecture
  • Strong understanding of security, performance, and reliability engineering
  • Ability to write clean, maintainable, testable, production-grade Python code
  • Comfortable owning production systems and being accountable for delivery outcomes
  • Highly result-oriented with the ability to meet clearly defined monthly milestones

Performance and Work Culture

  • Delivery-driven role with monthly milestones tied to real product outcomes
  • Strong focus on shipping, improving system quality, reducing technical risk, and increasing platform reliability and performance
  • Agile, execution-focused environment with high autonomy, high responsibility, and high impact

How to Apply
Interested and qualified candidates should send a CV, cover letter (addressing the mandatory question below), and a GitHub link or equivalent portfolio of real production work using “Senior Python Engineer” as the subject of the email.

Mandatory Cover Letter Question

  • Design a high-volume fintech payments platform using Python that supports:

  • Real-time transactions
  • Event-driven processing
  • PostgreSQL as the source of truth
  • Redis for caching
  • RabbitMQ for asynchronous workflows
  • A mix of AWS (Lambda, RDS, S3) and Azure (Functions, Event Grid / Service Bus)
  • Explain in detail:

  • The architecture to be designed
  • How services communicate (synchronous vs asynchronous)
  • How reliability, idempotency, and data consistency are ensured
  • How the Python codebase is structured (modules, layers, boundaries)
  • How scaling, failures, and observability are handled
  • Key trade-offs and the reasoning behind them