Oct 2022 – Jul 2024 · 1 yr 9 mos · Bengaluru, Karnataka, India

• I worked as a Technical Architect leading the RPG Studio's backend team
• My roles and responsibilities include:
• 1. Design: high level and low level architecture design of features of the Tennis Champs game .
• 2. Hands on: implement the features and ad hoc tasks
• 3. Management: responsible for the RPG studio's deliverables.
• Highlights:
• 1. Development Process Enhancement
• Brought up a few changes into the feature development life cycle such as
• involving at least one product member during technical design discussion to clarify any doubts, understand priorities and feasibility.
• break up the feature into smallest tasks and then provide ETA for each task. Figure out if there are any dependencies or roadblocks.
• present the backend design to other engineering teams especially the client team and get to a consensus about the APIs and their schemas.
• inter team code reviews.
• 2. Technical Debt Resolution
• There was a necessity to revamp the Reward system in the infra level code and negotiated with the product team about its importance and relevance. At the same time, we didn’t let the priority items stop.

Apr 2022 – Oct 2022 · 6 mos

• Vormir
• 1. Centralised service to save and return cohorts in the system.
• 2. Implemented finite state machine to handle various states of cohort.
• 3. Implemented search ranking algorithm by assigning appropriate weights to the Elasticsearch results.
• 4. A very critical service widely used across multiple different apps in the organisation. It’s one of the top products that is showcased to the clients and it features in the products section of the main website - https://nference.com/nsights (Cohort Library)
• Other highlights
• 1. Two environments (CDAP dev - CDAP prod) which are private clouds need to sync cohorts. Both the environments share the data sets of patients but the environments cannot communicate with each via ports so there are no APIs that could be called from each other. The only common bridge between the two environments was a Google Cloud Bucket. Here’s what I proposed…
• Whenever a cohort is persisted in one environment, a meta info was added to a folder in the common bucket.
• There are cron jobs running in the local env to copy the data from local bucket to the common bucket and the meta info is updated accordingly.
• There are cron jobs running in the other environment which keeps on reading the meta info and copy the actual cohort and meta from the common bucket to its local bucket.
• The sync also happens vice-versa.
• This has been seamless and was well appreciated by various teams in the company because the cohorts are used across multiple apps/services.

Apr 2020 – Mar 2022 · 1 yr 11 mos

• Cell Lines Explorer*
• This application allows a user to determine the features (literature and molecular) which are significantly enriched in a test group of input cell lines with a control group.
• Few engineering highlights:
• Achieved a 10x performance improvement of a couple of APIs.
• The project was initially built using python (leveraged libraries such as pandas to deal with large columnar data frames). Couple of APIs had very long response times (~35s and ~7s respectively). We have achieved this by
• 1. first moving to Golang
• 2. executing code in parallel wherever possible using go routines
• 3. implemented server side pagination instead of sending all of the results to client at once
• 4. use caching for pagination

Apr 2019 – Mar 2020 · 11 mos · On-site

• Responsible for building the server side components of the mobile games. Our team has developed the server code mostly in Golang for our games, common libraries (to be used across all games) and a couple of microservices.

Apr 2018 – Mar 2019 · 11 mos · On-site

• Developed a Routing Service (based on Node.js) to collect, modify and send event data from the games to Amplitude.
• Developed a simple Facebook Messaging service that sends specific messages to targeted players based on their game play behaviour.

Aug 2017 – Mar 2018 · 7 mos · On-site

• Realm Merge in TGF game
• Merged players (or multiple profiles of a user) on multiple realms into few realms. Wonderful learning experience of the technicals involved.
• Player platform migration from Wonderhill to Facebook
• Challenging task to form the linking between the two platforms. Database architecture design was made perfect to achieve this.
• One important thing learnt is that we should never be sure that third party APIs will always give us proper responses (even the likes of Facebook). We should always handle the error cases where they give unexpected results or timeouts etc.

May 2015 – Jul 2017 · 2 yrs 2 mos · On-site

• Backend Engineer for the Midcore games based on RoR (backend)
• Built the Token Store in The Godfather. Learned how to make server side APIs more robust and secure against potential exploitations. Also had a great learning experience of Object Oriented Design of the feature.
• Resolved a scalability issue by implementing async job mechanism for opening chest items in Dragons of Atlantis.
• Single Point of Contact for the engineering requirements of Business Intelligence, and Xpromo of Kiwi games
• Integrated RY Analytics into the Kiwi Games during its migration.

Jan 2012 – May 2015 · 3 yrs 4 mos

• Engineer for BI system.
• Built the Business Intelligence module for the company (team of 4). Responsible for capturing, piping, saving, retrieving game data for analytics. Worked on building tickers (google, high charts APIs) and reports (MVC framework).
• Built other in-house tools to facilitate ease of processes like event notifications to adnetworks, adding/editing/running reports for analysts.
• Adlooper Engineer (Ad mediation product)
• Built webconsole (based on Ruby on Rails) for adlooper users (team of 3).
• Full stack developer for the features involved in adlooper product.

Jun 2009 – Jan 2012 · 2 yrs 7 mos

• Backend Engineer for Party Account
• Web application Development and B2B
• Worked as a developer of web application for players’ account-related-activities after the business’ acquisition of licence for online-gaming in Denmark, France. Effectively added new functionalities like winnings limit and banned-player check involving gateway call to third party API. Provided web applications for the regulatory, other businesses and integrated some of their business into the application as part of a B2B deal.
• Accomplishments include:
• Obtained specifications from the product team and their end-to-end development was taken care of independently.
• Each functionality changed/added is very well documented.
• Messaging
• The team is concerned with all sorts of communication to the player. It includes PAM, Mailing, and Pushchat.
• Pushchat
• Pushchat is an open-source chat client used to trigger chats to the players in order to chat with them as and when certain events are captured.
• Made changes to openfire/spark-client, a third party software to meet the requirements of the company. Provided technical enhancements to the software making it easier for customer support to guide players.
• Modify Openfire source code to forward the metadata of the player when an agent transfers chat to another agent. Enabled multiple chat transfers.
• Display player information in the agent chat window in the form of a table in required order. Added mouse listener to the table cells making them clickable and launch URLs in external browsers.
• Identified defects in the software and successfully rectified them.