01Who

Hey, I'm TJ

I'm a senior software developer at Oracle Health. Over the past seven years I've worked across frontend, backend, developer tooling, and distributed services — first at VMware, now on healthcare software at Oracle.

I like the part of engineering where complicated systems have to become understandable: turning messy workflows into software people can depend on, improving the tools around a product, and making the next change a little safer than the last one.

View my workDownload résumé
Portrait of Tanuj Chakraborty

  • 7+ years

    Building production software

  • VMware → Oracle Health

    Infrastructure, product, then healthcare

  • 15 students

    Mentored through Vritti Academy

02Evidence

Selected impact

A few pieces of work that show different sides of the job — product outcomes, services, engineering quality, and interfaces people have to live with.

  1. 01

    Healthcare workflow

    Pharmacy refill, with less waiting

    Outpatient pharmacy and refill flows are the kind of work where a few extra steps show up as real time for patients and clinicians. I worked on those workflows at Oracle Health. One of the improvements contributed to about a 30% reduction in time-to-dispense.

  2. 02

    Backend services

    A unit-conversion service for inpatient care

    Inpatient workflows need medication units converted reliably, not as a one-off spreadsheet of special cases. I worked on a new microservice for that — Java 21 and Micronaut 4, with YAML-based configuration, mapping, and a test suite around the behavior that actually matters. It runs on OCI/Kubernetes. The interesting part was less the stack than getting a small, well-defined service into production without making it fragile.

  3. 03

    Engineering quality

    Quality gates around the pharmacy UI

    Shipping features is only half of the job. Around the pharmacy UI I introduced and tightened linting and CI/CD quality gates, including ESLint, so issues show up before they become someone else’s surprise. I care about the environment a product is built in, not only the screens that ship.

  4. 04

    Product & full-stack

    A diagnostics UI people could actually use

    At VMware I revamped the interface for the Skyline Health Diagnostics tool in Clarity Angular. The problem was a product that did useful work behind a UI that made that work harder to reach. The rewrite was about making the tool understandable — the same instinct I still bring to product surfaces now.

03Path

Career journey

The through-line is not a single layer of the stack. It is a gradual move toward owning broader problems: from testing and automation into frontend, backend, full-stack product work, and the services that sit underneath healthcare workflows.

2019–2024

VMware

Member of Technical Staff

Five years of growing the surface area of what I owned: testing and automation, then frontend, backend, and the developer tooling around pipelines and shared platforms.

  • Consolidated fragmented build and execution data into a metrics dashboard, so pipeline failures and performance regressions were easier to investigate.
  • Worked on migrating pipelines onto Netflix Conductor, making execution more consistent across teams.
  • Built a shared library to integrate existing pipelines, cutting duplicate work and the maintenance that came with it.

2024–Present

Oracle Health

Senior Software Developer

Healthcare software around medication workflows and the clinical services that support them — pharmacy, medication administration, medication products, and related task flows.

  • Worked on outpatient pharmacy and refill workflows, including a change that contributed to about a 30% reduction in time-to-dispense.
  • Helped build a unit-conversion microservice for inpatient workflows, with an emphasis on configuration, testing, and a service that other systems can actually rely on.
  • Improved engineering quality around the pharmacy UI with linting and CI/CD gates, so the product is easier to change safely.

VIT University, Vellore · B.Tech in Information Technology · 2019

04Craft

What I work on

The names are supporting evidence. The useful part is what they have been used for.

  1. 01

    Backend & services

    Java · Micronaut · Spring · APIs · Service-oriented systems

    These have been the backbone of production services, including healthcare workflows where the details have to be right.

  2. 02

    Product engineering

    React · Next.js · TypeScript · Angular

    I move between the systems underneath and the interfaces people actually use — React and Next.js now, Angular when the product called for it.

  3. 03

    Developer experience & delivery

    Docker · Kubernetes · Jenkins · CI/CD · Testing

    A lot of the work I care about is making the next change safer: shared libraries, clearer pipelines, tests, and quality gates.

  4. 04

    Data & integration

    MySQL · PostgreSQL · MongoDB · YAML · JSON

    The unglamorous glue: configuration, data shapes, and the integrations that keep services talking to each other.

05Elsewhere

Beyond my day job

Engineering is not only the work that shows up on a timesheet. Some of the most useful hours have been spent teaching, or building something because I wanted it to exist.

15

students mentored

Vritti Academy

I co-founded Vritti Academy and spent about a year and a half teaching and mentoring around 15 students. We worked through data structures and algorithms, DBMS, operating systems, computer networks, and the kind of project work that makes those topics feel real. It was a small effort, not an institution — and I liked it because teaching forces you to understand a thing well enough to hand it to someone else.

DSA · Databases · OS · Networks · Projects

Building for myself

I don't only write software when it is assigned to me. When I bump into a problem I want solved, I often just build the tool. traingrid is a current example: a personal planner for running and strength sessions. It is not a product pitch. It is a reminder that I still like making software when nobody asked.

More on the projects page

When I'm not building software

  • Cricket
  • Badminton
  • Running
  • Building side projects

Away from the screen, you'll usually find me playing cricket or badminton, or out for a run. And yes, sometimes building something I probably could have managed perfectly well without building.

Want to talk?

If you have an interesting problem, a product that needs to get clearer, or just want to compare notes, I am easy to reach.

Get in touchDownload résumé