Work Experience Open for hire

These are the professional engagements that I've pursued full-time.

4+ years of professional experience. Been coding since I was 14. What got me into this world was a fascination with Borland C++ blue coloured screen.

Argonaut.dev

  • Core backend team member.
  • Features I built:
    • Added support for multiple AWS integrations in Argonaut's stack.
    • Built a debugging/operations job procedure to allow users to troubleshoot/manage their K8 clusters.
    • Added support for Keda based auto-scaling to in users' K8 clusters.
  • Fixed bugs in existing features.
  • Migrated some legacy services in the API.
  • Collaborated and coordinated with the front-end team for UI changes for the features I built.

Culture

  • Permanently remote team. India-wide distributed.
  • Small team of 10 people. Including design and marketing. Rest engineers.
  • Directly reporting to the CEO i.e. Surya.
  • ~ 2 week sprints.
  • Daily standup calls.
  • Townhalls every Tuesday.
  • Hangout session every Friday.
  • Tickets on GitHub Issues and Linear.
  • Communication and coordination over Slack.

Stack

REST APIs in Golang
React for front-end
Kubernetes for orchestration
GitHub Actions for CI/CD
AWS, GCP and Azure for infrastructure

Locale.ai, Bangalore

  • Core backend team member.
  • Designed the architecture for Locale v2 which is an alerts engine that runs queries on top of your conventional databases.
  • Contributed to Locale v1 as well. But we decided to close it's support shortly after I joined.
  • Handled design, development, testing, documentation and deployment of the CLI.

I quit Locale due disagreements with the founders about the product and their wisdom to pivot to version 2.

Culture

  • Hybrid attendance. Had to physically visit office at least 2 days/week.
  • Small product team of 10 people. Including designers. Rest were engineers.
  • Reported to an Engineering Manager, who in turn reported to the CTO.
  • 2 week sprints.
  • Daily standup calls.
  • Tickets on GitHub Issues and Linear.
  • Communication and coordination over Slack.
  • Product demonstrations on Friday.

Stack

API written in Java (Quarkus)
Hasura as the core GraphQL engine
Kubernetes for orchestration
GitHub Actions for CI/CD
GCP for infrastructure

Learnings

  1. Be careful in startups where founders panic due to rejections and low sales and decide to make a bad pivot.
  2. When you sense your company is running out of funds and a new round doesn't seem to be going through anytime soon - it's better to leave and move on to your next project, instead of waiting.

Nhost.io, Stockholm

  • Second core team member.
  • Designed and maintained the Nhost CLI from scratch. The source code is open-source and available here. This repository can be used to judge my Golang skills.
  • Contributed to all of Nhost stack, in the early stages, including front-end SDKs, authentication and storage.
  • Wrote an experimental Golang library for exposing local environment using HTTP tunnels to the public internet to increase testing time, and serve as an alternative to preview environments.
  • Handled design, development, testing, documentation and deployment of the CLI.

From May 2021 to February 2022, I worked with Nhost, as a backend engineer. Was one of the core team members after Nhost raised $3 Million from the founders of GitHub and Vercel.

Culture

  • Permanently remote team. Globally distributed.
  • Small team of 10 people. Including design and marketing. Rest engineers.
  • Directly reporting to CEO and CTO.
  • 2 week sprints.
  • Weekly standup calls every Monday.
  • Tickets on GitHub Issues and JIRA.
  • Communication and coordination over Discord.
  • Directly solving users' issues over Discord channels.

Stack

CLI written in Golang using Cobra
Hasura as the core GraphQL engine
Docker for orchestrating Nhost's auth, storage and DB services
GitHub Actions for CI/CD
AWS for infrastructure

Learnings

I learned a great deal from Johan and Nuno about how to set up an early-stage engineering team. Everything from carefully handpicking engineers, to prioritizing which features make sense to be rolled out next, to finding workarounds from troubling yet insignificant engineering problems, and finally building a great product, whilst placing a lot of focus on user feedback. Apart from how much I loved writing code and solving engineering problems, I have a special respect for both of them.

Oversight, Founder & CEO

You can read my entire story of Oversight's inception and death over here.

  • CMS for research collaboration to allow scientists, faculties and students to collaborate on each other's research through mentorship, internships or professional collaboration.
  • Crowdfund on your research or generate monthly income from your followers.
  • The primary platform is available at research.oversight.in.

We ran Oversight for 1.5 years (until Q1 of 2021). Until we fell short on distribution and sales and decided to quit. We shut down Oversight in March 2021.

Culture

  • Permanently remote team. Nationally distributed in India.
  • Small team of 10 people. Including engineering and sales.
  • Directly coordinating with each other.
  • 2 week sprints.
  • Weekly standup calls every Monday.
  • Tickets on GitHub Issues.
  • Communication and coordination over Discord.
  • Directly solving users' issues over Discord channels.

Stack

NuxtJS for front-end
Golang for API, using Echo framework
Hasura for GraphQL
AWS (Hasura on EC2, RDS, ELB)
Razorpay for Payments

Learnings

You can read my entire journey of Oversight, and the learnings I got from it, in detail over here.

InstantPost, Bangalore

  • Automated remote servers across India for a production-ready edge-computing environment.
  • Handling load balancing, health monitoring, fault tolerance, auto-scaling of services and secure server-to-server connections.
  • Technical writer for all the innovations and developments within the company.

Stack

Python
Headless Servers
Docker
LXC
Ubuntu
RHEL
OpenSSH
Discuss on Twitter Updated at Sun, Mar 17, 2024