Vasanth Ganesh

Took on the tech ownership for the entire risk solutions. Establishing inter and intra team processes . Increased direct interactions with the customers to understand and devise appropriate strategic solutions along with the product team.

Built multiple risk-related insurance products . Contributed to the product roadmap and stakeholder management. Focused efforts on making the tech platform robust and scalable. Working with the team on their career growth and path .

Set up an engineering team from scratch. Started out hands-on while also focusing on recruitment . Leveraged the serverless architecture here using AWS SAM, Step Functions and Lambdas .

Ran 2 engineering squads with a total strength of 12. Built a complex orchestration platform leading to multiple automation solutions for our users. Along with the responsibilities of a lead engineer, was involved with interfacing with external teams like Product/CS and setting the right roadmap.

Lead a squad of frontend, backend, and QA engineers. Responsible for smoothly architecting, building, and scaling of various projects that support >350 TPS at peak instances. Also mentored multiple engineers who were in/outside my team.

Built multiple complex microservices in Rails/Flask from the ground-up using various technologies like Redis, Kafka, Celery/RabbitMQ, Elasticsearch, Scrapy, Postgres , etc. Also responsible for scaling up of certain heavy-duty APIs to support 8x traffic.

Built various features in Jobspire and some auxiliary products surrounding it using Rails, Redis, Postgres, JS and Heroku . Jobspire also reached a successful acquisition in 2017.

After the internship, I worked with the payments platform and its dependent services. This involved tweaking our services and exposing new APIs to simplify the dB overhead. Also, created test frameworks to simplify the addition of new tests to the system.

I was part of the payments platform team. I worked on making the payments system durable to handle high scales of transactions( >200 TPS ). This involved working with Core Java, Spring, DynamoDB, EC2, EMR , and other auxiliary Amazon-internal tools