Mar 2023 – Jan 2025 · 1 yr 10 mos · Vancouver, British Columbia, Canada · Remote

• Implementing, and debugging issues in Jane app
• Upgrading Jane app to Rails 6.1
• Implementing Datadog on new platforms for metric evaluation and alerts
• Blocking SQL injection attacks and improving Data input validations

Jun 2020 – Aug 2022 · 2 yrs 2 mos · Pune, Maharashtra, India · Remote

• Development and Maintenance of Onit's Apptitude Platfrom.
• Packaging tool to export and import corporations's metadata across different
• environments.
• Data Anonymization tool to secure user’s confidential data across different
• environments. Allow customization for users to decide what data should be whitelisted.
• Debugging and providing support for production bugs and issues

Jul 2018 – Jun 2020 · 1 yr 11 mos · Gurgaon, India

• Developed B​abatrucks.com​ from scratch using spree.
• Revamped Polygons UX and improve site response. Created a major feature called customized polygons using google Places and Drawing Apis.
• Implemented Reverse Geocoder using Map My India
• Created all Apis and Admin backend for Lookup/Installer app using Grape and Active Admin
• Created many customized user reports using GraphQL and Javascript. Later migrated all the reports to class based reports due to maintenance issues

Jun 2017 – Jun 2018 · 1 yr · Noida Area, India

• Responsibilities: ​Development of Livvel platform
• Challenges:
• Centralised Authentication Service
• Devise is used for authentication. Devise expects views and models should be in the same Rails application. Thus, devise had to be extended to accommodate SOA while maintaining system integrity and security.
• Overriding Rails View - Model Dependency
• Form builder api used in rails views, expects a model object to be present in local database. View service was only meant for creating html views. It was getting data from other services rather than local database. As a solution, a tableless model extension was created that allowed us to utilize power of rails form builder and nested attributes features effectively.
• Designing User Data Services
• The main challenge was to create different data services keeping in the mind their deployment topology in future. Basic principle was, relevant data should be together and separated from generic data and should have possibility of geography based distributed deployment.
• Optimisation of Views with Ajax
• To improve site response, ajax was used not only to get relevant data but also relevant views instead of full page request. Jquery was used extensively. Benefits of this approach were security and compatibility.
• Learnings:
• Importance of a good Architecture
• Because of a flexible architecture, today there are so many deployment and optimization possibilities in the current system.
• Power of SOA
• SOA allows an architecture to remain fully flexible even for a complex application . It allows easy identification and treatment of bottlenecks. It allows different base technologies to communicate easily so one can leverage their benefits wherever required.
• Power of Pair Programming and Agile
• Incremental building of application using agile and pair programming allowed us fast paced and quality development while satisfying business objectives alongside.

Oct 2016 – Jun 2017 · 8 mos

• Responsibilities:
• To develop json based web service aggregator APIs. They are developed in Python-Django with Django rest framework. I mainly worked on Deal and Feed Modules.
• 'Deal' can be inferred as a reward to the customer at a merchant. ‘Feed’ is the social networking part which is essentially a stream of posts and widgets created by the selfies of the customers. Both the modules are essentially the collection of aggregator APIs. Deal has 18 and Feed has 11 APIs.
• Point contact for Aggregator Hops. Standardisation of client data
• Challenges:
• There were some big challenges such as Django doesn't have REST built-in and requires other third party APIs for the purpose. Similarly, to serialize an object, a model is required even if model objects are not being used.
• Technical experience:
• The APIs that I developed at MagicPin, followed standard design of service handler/controller and service operations/action that are responsible to create and manipulate relevant business data and aggregate them in ready to client business objects. Client of APIs are mostly android, ios and web apps.
• All operations/actions followed stateless design. These APIs are also called Hops. It is not related with the Hop servers(javascript based client/server platform)
• There were many benefits of intermediary hop systems such as speedy server to server communication, and less processing time on client side. Update of data preparation is centralised and doesn’t result in client upgrade. Only essential information flows overs the network resulting in requirement of low bandwidth.