Job Summary

Our client, a leader in mobile payment systems, is looking to bring on a Senior Python Engineer that will be part of a team responsible for solving some of the complex backend problems related to the world of connected payments. Be a technical stalwart and take responsibility for one of the biggest payments platforms that caters to 27.4 million monthly active users and estimated to have a transaction volume of 100 billion dollars in 2020.

The ideal candidate will be a backend developer with strong experience writing Python services on Kubernetes, using MySQL and other NoSQL databases. As a PaaS Engineer, you will be responsible for making engineering design decisions and developing features pertaining to the services that are the backbone of our client. You will be expected to be a role model on coding standards, frameworks, platforms and other best practices for the rest of our client’s engineering team.

Job Responsibilities

  • Design and implement new services using cutting edge technologies to support Our Client in achieving its business goals.
  • Collaborate with the architecture team to develop robust, portable, and interoperable solutions to the difficult problems faced by a growing organization.
  • Collaborate with the Information Security team to keep Our Client, and its customers, safe from emerging security threats.
  • Take an active role in reducing the technical debt in our various codebases.
  • Triage, debug, and assure the timely resolution of software defects.

Qualifications

  • Expert in Python, with knowledge of Django web framework
  • Experience with Apache Kafka or Confluent Kafka in high volume environments
  • Experience in development projects using Java/J2EE technologies
  • Working experience on Cassandra and caching solutions (e.g. Redis, ElastiCache).
  • Expertise in architecting and developing scalable software solutions with gRPC based microservices.
  • Strong understanding of algorithms and data structures.
  • Strong understanding of design patterns including why and where a pattern should be used
  • Understanding of accessibility and security compliance

What will really get our attention

  • Experience in payments processing or payments domain
  • Experience in risk or compliance domains
  • Experience integrating disparate systems together