Everything from frontend development with React, to custom Kubernetes controller logic in Go.

Software Engineer on a US-based distributed team primarily focused on platform engineering through building backend services, shared libraries, infrastructure abstractions, observability tooling, and delivery mechanisms used across our engineering teams with a keen eye towards minimizing cloud spend while maximizing availability.

Set/educated developers of best practices, technical standards, and established processes concerning infrastructure, observability, incident response, and build/release systems.

Developed a globally available, cloud native API Gateway built with Golang and custom Caddy modules, which performs intelligent routing, retries, authentication, and observability transparent to our internal services.

Lead developer for the application configuration service, a tier-1, globally available GraphQL-based Nest.js (Typescript Node.js) backend service that stores versioned multi-tenant configuration in a globally replicated MongoDB cluster, with configuration creation done via a second event-driven Nest.js microservice using AWS SQS.

Co-owner (member of an engineering-wide subteam) of shared Typescript Node.js/Nest.js libraries, primarily focusing on a standardized way to easily implement logging, tracing, resolving runtime configuration, and message queue utilization.

Helped drive design for modern, multi-region, global orchestration platform based on AWS Elastic Kubernetes Service, utilizing spot instances, Karpenter, AWS SecretsManager, AWS ALB ingress controller, AWS Global Accelerator, KEDA-based autoscaling, and OpenTelemetry with associated abstractions in terraform.

Developed solution for using GPU enabled nodes for use with ML solutions and ephemeral development environments for our data scientists.

Developed shared CircleCI tooling in the form of a CircleCI orb, used across all our build pipelines to automate actions such as git tagging and releasing, deployments, Docker image and artifact builds, etc.

This is a development-skewed role.

Site reliability engineer on a distributed team developed multi-cloud, cloud-native infrastructure to provide a managed solution for Dgraph's graph database solution

Streamlined operations work with Golang, Terraform, and Ansible to automate tasks around configuration, CICD, and resource provisioning on baremetal Rancher Kubernetes, AWS, and GCP

Co-owner of metrics, alerting, and log aggregation pipeline, using Prometheus, Promtail, Thanos, and Loki to collect metrics and logs and forward them upstream to Grafana.

Primary owner of the baremetal cluster resources. Automated system onboarding via Ansible, Terraform, and shell scripts in order to initialize system configurations, networking resources, storage solutions, Rancher Kubernetes cluster creation, and observability resources.

Worked alongside other SREs and Customer Success engineers to respond to production incidents and debug customer problems by participating in on-call rotation and authoring runbooks.

Maintained instance of our developer-facing forums (https://discuss.dgraph.io/) which received 10s of thousands of visits per month.

This was an operations-skewed role.

Junior site reliability engineer on a distributed team, developed scalable AWS cloud infrastructure on a greenfield SaaS application.

Developed automation and services around reducing toil and operations work, including

monitoring, alerting, instrumentation, and secrets management with Golang (primarily for

services) and Python (for general scripting tasks).

Authored infrastructure-as-code with Terraform in order to deploy various microservices and

infrastructure in order to ensure that the application was scalable, self-healing, and resilient using modern serverless technologies.

Developed infrastructure abstractions for use in Jenkins using a Groovy-based shared library, abstracting complex worfklows like automated releases, branching strategies, etc.

Worked to make DevOps culture a daily part of our engineering culture and introduced

policies around on-call strategies, documentation, code conventions, logging, releases, etc.

This was a development-skewed role.