Feb 2018 – May 2019 · 1 yr 3 mos · Gurgaon, Haryana, India

• Lead developer in the finance domain
• The entire domain had to be created from scratch so we decided to use the Microservices pattern to represent our Bounded context. The entire domain worked asynchronously around a generic Decisioning subdomain which managed the workflow of the various types of Loans for Borrowers. The focus was to give a decision on Loan Approval or Denial on the basis of customer data and history and give it as quickly as possible, within 10 min for small loans.
• Decisioning
• A generic subdomain working as an orchestrator for other microservices as well as workflow manager for various loan types. A decision domain event was the output on the basis of the final sub-flow stage of a particular loan workflow.
• We tried to make it as generic as possible and 100% code change independent while integrating new rules with a new set of data and new workflows and sub-flows. The workflows required configuration through Couchbase Document-based NoSQL DB.
• This resulting architecture was 100% release with an expected increase in complexity.
• Authentication
• In house authentications system using OAuth and JWT.
• Documents
• Document Managing and storage using AWS S3, SFTP, other third-party solutions.
• AES-based encryption was used to encrypt the document data before storing it to tackle any security leaks.
• Bank Statement Analysis
• System to read a customer’s bank statements and break them into meaningful data to help decide the loan disbursement process.
• Third-party APIs were used to group data in a basic JSON structure which was converted into required data groups.
• All the parts from request handling, retry to reporting, and call-back was automated with weekly reports on the data processing efficiency being mailed.

Jan 2017 – Feb 2018 · 1 yr 1 mo · Noida Area, India

• Senior developer in the mobile wallet and mobile banking domain.
• CTA (Call to Action)
• Middleware for communication between frontend (App and web) and backend systems. Implemented a Rule Engine and Actor model-based architecture for an optimal design that was less release intensive, able to scale, and lightweight. The system was designed to handle almost 300 TPS in the first phase of release.
• The scale was a major focus of this system which we delivered by using circuit breaking (using Hystrix), caching (using Aerospike), and Async processing.
• CKYC (Central Know Your Customer)
• Target was to act as a communicator between Central Gov. systems and in-house KYC system to get the CKYC Id of Paytm KYCed customers for their Payments Bank account.
• This resulted in the creation of a messaging-based ACL domain which kept the rest of the domain free from legacy Gov. system concerns.
• Kafka Queue based design to collect KYC User Ids which were needed to collect user Metadata and verification document from various backend systems, required by gov. CKYC.
• AWS S3 buckets were used to store user Data files in folders created on an hourly basis.
• Quartz scheduling was used for various Java tasks like pulling data from the S3 bucket to be shared on CKYC SFTP location, etc.
• A proper retry mechanism was also a major concern due to a lot of interactions.
• DMS (Document Management System)
• System to save and serve the User documents and related data in AWS S3 storage.
• Kafka Queue based integration with other services.

Sep 2016 – Jan 2017 · 4 mos

• Senior developer in the Legal Contracts management domain.
• Design and development of bulk-update functionality to update multiple contracts.

May 2015 – Sep 2016 · 1 yr 4 mos

• Senior Developer in Shipping/Fulfillment Domain
• In-house Courier
• Courier for the delivery of a packaged order from seller/warehouse location to customer location. Target was to handle a scale of around 500K orders a day maintaining the complete order flow history and tracking details.
• Needed to integrate with almost all third-party couriers for seamless courier allocation and tracking which required clear defined domains to be developed.
• Workflow manager based domain design for ease of defining new workflows and transition management.
• Validation and Processor layers with plug and play functionality to quickly add validations and processors, resulting in a timely testing and production release cycle.
• Complete tracking of the package from a source location to destination location to provide more visibility thereby decreasing package loss and increase customer immersion.

Mar 2014 – May 2015 · 1 yr 2 mos

• Software Developer in Shipping/Fulfillment Domain
• Various warehouse management models developed.
• Model for fast shipping which enabled the implementation of same day, next day delivery features.
• Model to increase countrywide reachability for sellers, thereby increasing registered sellers and catalog and inventory size. We were the first to cover even remote areas very optimally.
• Model to enable Quality check and packaging at our end to reduce seller overheads in packaging an order, improving package shipping times.
• O2O (Offline to Online) Model to allow offline sellers/retailers to register their products on Snapdeal with a focus to increase inventory size and sellers count.
• Lane Priority
• A module that allowed the creation of supply lanes on the basis of various criteria like source city/state, destination city/state, etc. to define the ranking of order fulfillment and delivery.
• The module intelligently calculated the ranking in which each order and cart item needed to be processed to enhance customer experience through better delivery.

Jul 2012 – Mar 2014 · 1 yr 8 mos

• Software Developer in Shipping/Fulfillment Systems
• Worked on a complete architectural overhaul of the existing supply-chain and logistic domain by using Microservices Architecture where the existing domain was broken into Shipping, Tracking, and Serviceability Subdomains for independent development and in-depth focus.
• Worked on system scalability to support around 500K orders a day and around 10X load on festival sales period.
• Worked on domain-specific patterns to optimize costs by incorporating capability for optimal delivery routes and optimal packaging.
• Developed state machine subdomain to make core domain more modular and less release intensive.