Apr 2023 – Sep 2024 · 1 yr 5 mos · Bengaluru, Karnataka, India

Apr 2023 – Jun 2024 · 1 yr 2 mos · Bengaluru, Karnataka, India · On-site

• I am part of engagement / platform team
• I am currently developing an orchestration layer for the gateway that handles traffic routing and can also modify request and response data.
• Established a CI/CD pipeline from the ground up for the gateway service
• Additionally, constructed an A/B deployment pipeline specifically tailored for the gateway service.
• Tech: Aws, Redis, MongoDb, Cassandra, Kafka, SQS, Grafana, Kong, Scalyr, Go, Node.js, lua, Docker, Kubernates

Aug 2022 – Dec 2023 · 1 yr 4 mos · Bengaluru, Karnataka, India · Remote

Jul 2022 – Apr 2023 · 9 mos · Bengaluru, Karnataka, India · Hybrid

• Scale: 4M+ events/sec. Message Bus cluster can handle such load
• I have also led the AWS cost optimization effort, assisting the company in saving 2000$+ per day, or 5 million INR per year.
• We are creating Centralized Message Bus from the ground up. As a member of the data platform team, I have been in charge of technical decisions.
• I am also the technical lead on a separate project that is very similar to Zendesk but will be an in-house solution. This project allows users to create service tickets that will assist them. I contributed to the creation of design documents, code reviews, the establishment of coding best practises, and the resolution of technical issues for the team.
• Our team also won first place in a hackathon

Apr 2022 – Apr 2024 · 2 yrs

Aug 2021 – Present · 4 yrs 7 mos · Bengaluru, Karnataka, India

Mar 2021 – Jul 2022 · 1 yr 4 mos · Bengaluru, Karnataka, India · Hybrid

• OCI did not have CDN service as comapred to other leading cloud providers. We are building control plane for CDN in first phase and then data plane we move ahead.

Dec 2019 – Mar 2021 · 1 yr 3 mos · Bengaluru, Karnataka

• Scale: Managed 3M+ request/day.
• I worked on re-designing the risk engine (rule engine) from the ground up at Zestmoney. Change from monolithic to microservice-based architecture, which can handle 10 times the demand with the same number of instances. MaaS (model as a service) was also exposed, which can be used by several teams.
• JVM parameters have been tweaked to accommodate high throughput. Analyzed garbage collector logs and heap dumps to resolve application-level scalability concerns.
• Tech Used: Java, SpringBoot, sqs, MySQL, Redis, ElasticSearch, New Relic, Sumo logic, Sl4j, DataDog

Dec 2018 – Dec 2019 · 1 yr · Bengaluru Area, India

• Scale: 100M+ events daily.
• I was part of trust platform team.
• I have experience with data pipelines (offline jobs). We had an offline fraud detection mechanism in place that took 6 hours or more to execute, by which time we would have distributed incentives to partners. It was necessary to develop a real-time fraud detection system that could detect these scams in seconds and penalise the partner based on the severity of the fraud. We developed a system that can manage 100 million or more events while also being scalable. Developed various guidelines and solutions that helped Ola save millions of rupees each month.

Sep 2016 – Dec 2018 · 2 yrs 3 mos

• Scale: 20M+ records
• Wrote a data pipeline that included generic parsers, field auto-detection, regex pattern matching to extract meta data, nlp (pos tagger), and knowledge graph merge.

Dec 2015 – Oct 2016 · 10 mos

• I worked as a full stack developer. The old legacy tool that was used to check merging records was re-architected. Frontend to backend system designed and deployed to AWS. To speed up the data retrieval process, I created a caching layer and a caching method. The concept of bucketisation was utilised to scale data retrieval from the caching layer. Optimisations on the MySQL side, such as indexing, storage engine switching, query cache, and so on.

Mar 2014 – Nov 2015 · 1 yr 8 mos

Jun 2012 – Feb 2014 · 1 yr 8 mos

• Crawled data from accounts like dropbox , evernote , gmail , google drive for discovery . Recommendations based on users crawled data

Jan 2012 – Apr 2012 · 3 mos · bangalore

• I learned how to use a cicso router. I ran various network simulations. Set up a massive dynamic network to monitor each network failure event and filter specific packets from certain routers, among other things. I learned about several networking protocols and how to set a proxy in a network.