Available for new opportunities

Kundan
Bandaru.

Kundan Bandaru
>

I build software that solves real-world problems — from healthcare platforms and enterprise automation to scalable data processing systems.

Download ResumeExplore My JourneyContact Me
ReactPythonETLREST APIsDockerMongoDBEnterprise
~/kundan — zsh
$ whoami
kundan_bandaru
$ cat stack.json
{
"frontend": ["React", "Tailwind"],
"backend": ["Flask", "FastAPI", "ASP.NET"],
"data": ["MongoDB", "Oracle", "ETL"],
"infra": ["Docker", "Linux"]
}
$ status --now
→ building Market Access for US pharma
$
Scroll
About

The story so far — from curious to shipping.

My Computer Science degree introduced me to software fundamentals, but my real engineering journey began when I joined the industry and started solving problems for real users.

I started with HTML, CSS, and JavaScript, then progressed into React, where I learned component-based development, state management, and how to build interfaces that feel reliable in enterprise environments.

From there, I moved into backend engineering with Python and Flask. I worked on enterprise healthcare systems, built infrastructure automation software, developed ETL pipelines, and integrated multiple third-party APIs across different products.

My biggest strength is learning new technologies quickly and applying them to real business problems. AI-assisted development has also become an important part of my workflow, helping me prototype, debug, and deliver solutions more efficiently while I continue growing as a Software Engineer.

  1. Foundation
    Computer Science fundamentals
    My degree introduced me to core software concepts, but industry work is where those ideas became practical engineering habits.
  2. Frontend
    From HTML to React
    I started with HTML, CSS, and JavaScript, then progressed into React and learned to build reusable, responsive interfaces.
  3. Backend
    Python, Flask, and APIs
    I learned backend engineering by building REST APIs, connecting services, and integrating multiple third-party systems.
  4. Enterprise
    Healthcare and automation
    Early in my career, I worked on enterprise healthcare systems, infrastructure automation software, and ETL pipelines.
  5. Growth
    Learning as a strength
    My strongest skill is picking up new technologies quickly and applying them to real business problems with care.
What I do

Full-stack, end-to-end, shipping-first.

I don't identify with one layer of the stack. I identify with the outcome — reliable software that people actually use.

Frontend Engineering

React apps with real state discipline — reusable components, accessible flows, and interfaces that stay fast under real data.

Backend Development

Flask, FastAPI and ASP.NET services. Auth, validation, structured logging — the unglamorous work that makes products trustworthy.

API Integrations

MMIT, insurance data providers, internal enterprise APIs. Reading docs, negotiating contracts, taming inconsistent responses.

Enterprise Applications

Dashboards for internal operators — RBAC, audit trails, bulk actions. Software that people rely on 9 to 5.

Healthcare Systems

Hospital workflows, patient records, clinical UX. Built inside ERPNext and extended with custom modules.

Infrastructure Automation

Cisco IMC automation — inventory, power, firmware, config. Turning tickets into scripts and scripts into platforms.

Data Engineering

ETL pipelines that ingest, transform and land data in MongoDB. Idempotent jobs, observability, replayability.

DevOps Exposure

Docker, Linux, Git-based workflows. Comfortable owning a service from commit to container to production.

Roadmap

My engineering journey.

A milestone-based path of fast learning, real projects, and steady growth into larger engineering challenges.

Milestone 01
The Beginning
My professional software engineering journey started with learning HTML, CSS, and JavaScript from scratch. This phase built the foundation that shaped everything that followed.
Milestone 02
Modern Frontend Development
Expanded into React development, learning component-based architecture, state management, reusable UI design, and building responsive enterprise interfaces.
Milestone 03
Backend Engineering
Moved beyond the frontend by building REST APIs, integrating backend services with Flask, and understanding how distributed systems communicate.
Milestone 04
Enterprise Healthcare
Contributed to the development of a custom Hospital Management System integrated with ERPNext Healthcare, working across frontend, backend, and enterprise API integrations.
Milestone 05
Infrastructure Automation
Built enterprise software for Cisco Integrated Management Controller automation, implementing server monitoring, inventory management, RBAC, audit logs, power management, and bulk provisioning workflows.
Milestone 06
Healthcare Data Engineering
Designed ETL pipelines that extract, transform, and load healthcare market data from MMIT APIs, enabling pharmaceutical companies to make data-driven market access decisions.
Milestone 07
Today
Currently expanding into ASP.NET backend development while continuing to build enterprise software and seeking opportunities to solve larger engineering challenges.
Selected work

Three products, one thesis.

Different domains, same instinct: build something reliable, ship it, then make it faster and safer with every iteration.

01Healthcare · Enterprise

E-HMS

Electronic Hospital Management System

A hospital-grade management platform built on top of ERPNext Healthcare. Clinicians, front-desk staff and administrators all live in the same system — with workflows tailored to each.

12+
Modules shipped
6
External APIs
8
User roles
ReactFlaskERPNextMariaDBREST APIs
The challenge

ERPNext's healthcare module gives you the skeleton. Real hospitals need muscle: custom workflows, printable artifacts, integrations with lab and billing, and UX that respects a nurse's time.

Engineering decisions

Kept core records inside ERPNext for auditability. Extended the frontend in React for anything patient-facing, with a Flask layer bridging custom endpoints and third-party healthcare APIs.

My contribution

Owned the React frontend and Flask integration layer. Designed the appointment, IPD and outpatient flows. Wrote the API adapters between ERPNext and external providers.

Key features
  • Custom appointment & OPD flows
  • IPD admissions with bed management
  • Role-based clinician dashboards
  • Printable prescriptions & discharge summaries
  • Third-party healthcare API integration
Lessons learned

Healthcare software isn't a design exercise — it's a reliability exercise. If a nurse can't find a button in three seconds, the design failed, no matter how it looks.

02Enterprise · Automation

Cisco IMC Automation

Enterprise Server Fleet Management

A control plane for Cisco Integrated Management Controllers — monitoring, inventory, power, firmware and configuration across a fleet of enterprise servers.

500+
Servers managed
70%
Manual ops removed
6
RBAC roles
ReactPythonREST APIsDockerLinux
The challenge

Operators were doing repetitive per-server work through vendor UIs. Errors were expensive, audit trails were thin, and there was no single source of truth for the fleet.

Engineering decisions

Built a unified dashboard backed by API integrations with the IMC. Introduced RBAC, structured audit logs, and bulk operations so a single operator could safely act on hundreds of servers.

My contribution

Built the dashboard, wrote the automation flows for bulk configuration, and designed the RBAC + audit model. Turned one-off scripts into an actual product.

Key features
  • Fleet inventory & health monitoring
  • Remote power management
  • Role-based access control
  • Immutable audit logs
  • Bulk server configuration
  • Automated firmware workflows
Lessons learned

Enterprise automation is 20% scripting and 80% guardrails. The interesting engineering is in making destructive actions safe.

03Healthcare · Data · US Pharma

Market Access

Pharmaceutical Market Access Platform · Current

A platform that helps US pharmaceutical teams understand insurance coverage, plan drug launches, and answer 'which patients can actually get this drug?' with data instead of guesswork.

Multiple
Data sources
ETL
Pipelines
Shipping
Status
PythonMongoDBETLMMIT APIsASP.NET
The challenge

Payer data is huge, messy and constantly changing. Business users need clean, comparable views across insurance plans, formularies and geographies — fast.

Engineering decisions

Chose MongoDB for the flexible payer/plan schema, built ETL pipelines to ingest and normalize MMIT feeds, and structured the data layer so an incoming ASP.NET backend can consume it cleanly.

My contribution

Working on the data platform — MMIT integrations, ETL pipelines, transformation logic — and preparing to contribute on the ASP.NET backend as it comes online.

Key features
  • MMIT API integration
  • Insurance plan & formulary ingestion
  • ETL pipelines with replay
  • Drug launch strategy datasets
  • MongoDB data model for payers
  • ASP.NET backend (upcoming)
Lessons learned

In data-heavy products, your ETL is the product. If ingestion is fragile, every dashboard downstream inherits that fragility.

Toolbox

Skills, sharpened in production.

I don't list technologies I've read about. I list the ones I've shipped with.

Category · 01

Programming

PythonJavaScriptTypeScriptC#R
ReactPythonFlaskFastAPIASP.NETDockerGitLinuxMongoDBOraclePostmanMaterial UITailwindCursorChatGPTClaudeReactPythonFlaskFastAPIASP.NETDockerGitLinuxMongoDBOraclePostmanMaterial UITailwindCursorChatGPTClaude
Why work with me

Why I'm excited about building software.

These aren't buzzwords. They're the operating principles that show up in every commit.

01

Curiosity

I don't wait to be told what to learn. New tech shows up, I try it, break it, use it.

02

Ownership

I don't hand off. If it broke on my watch, it's mine to fix — and my job to make sure it doesn't happen twice.

03

Full-stack instinct

I move across frontend, backend and data without ceremony. The problem picks the layer, not my comfort zone.

04

Enterprise mindset

I've built for operators, clinicians and analysts. I know that boring reliability beats flashy features.

05

Automation reflex

If I do it twice, I script it. If we do it as a team, I turn it into a tool.

06

AI-native workflow

AI is a teammate in my loop — for prototyping, refactoring, learning new stacks faster than I could alone.

07

Continuous improvement

Every review is a chance to be less wrong tomorrow. I chase that on purpose.

08

Building products

I care about users, not just tickets. I want to see the thing I built help someone do their job better.

— Contact

Let's build something great together.

I'm open to roles where I can go deep on a real product, work with a team that cares about craft, and keep learning at the pace I'm used to. If that sounds like your team — say hi.

Start a conversationDownload resume
LinkedIn
/in/kundan-bandaru-a0b3bb230
GitHub
@KundanBandaru
Email
kundanbandaru@gmail.com