Ujjwal Sharma

Founding SWE Intern

OCT 2026 – PRESENT
AuditBuddy

Building and fixing the core product (0 → 1) for the November launch, working hybrid from Bengaluru across the full stack and infrastructure — Python, TypeScript, HCL, Shell, Bicep, PowerShell, and Docker.

View Project / PR →

Building AuditBuddy's Core Product from 0 to 1

Company: AuditBuddy
Role: Founding Software Engineer Intern
Location: Bengaluru, Karnataka, India (Hybrid)
Tech Stack: Python, TypeScript, HCL, Shell, Bicep, PowerShell, Docker

The Role: Founding Engineer Energy, Intern Title

As a founding-stage engineering intern at AuditBuddy, I'm working directly on the core product — building and fixing it from 0 to 1 ahead of the November launch. At this stage there's no separation between "product work" and "infrastructure work": the same people writing application code are the ones provisioning the cloud resources it runs on and scripting the automation around it.

The hybrid setup in Bengaluru means being close enough to the team for the fast, in-person decisions that early products demand, while still doing deep-focus work remotely.

The Work: Full Stack, Plus the Infrastructure Under It

The stack spans both the application layer and the infrastructure layer:

  • Python & TypeScript — the core product's backend and frontend code.
  • HCL & Bicep — infrastructure as code for provisioning and managing cloud resources declaratively.
  • Shell & PowerShell — automation and operational scripting across Linux and Windows environments.
  • Docker — containerizing services so the product runs consistently from a dev machine to production.

Building toward a hard launch date means every fix and feature is weighed against what November needs. There's no room for gold-plating — the discipline is in shipping the right thing, then hardening it.

Skills

  • Python
  • TypeScript
  • HCL
  • Shell
  • Bicep
  • PowerShell
  • Docker

The Outcome & Learnings

The product is being built and stabilized for the November launch. The biggest learning so far is what "0 to 1" actually demands day to day: you own the problem end to end — code, infrastructure, deployment, and the fixes when any of them break. Working across application code and IaC in the same week has reinforced that the boundary between "software engineer" and "infrastructure engineer" is mostly artificial at a small, fast-moving team.

Start a conversation about this role? Get in touch.

Say hello

  • E-Mail
    sharmaujjwal5705@gmail.com
  • LinkedIn
    linkedin.com/in/ujjwal-sharma
  • Instagram
    instagram.com/ujjwal75
Lights on