Datta VellalGet in touch

Engineering
others can
build on.

I’m Datta, Software Competency Lead at Philips North America. I help teams build quality into regulated software, and make the next team more capable than the last.

Start with the problem

What do you need to move forward?

Philips · 2022 · Program

Make quality visible and actionable

What I owned
I was accountable for the software craftsmanship assessment program: setting common measures, reviewing team goals and overseeing rollout.
What others did
Global teams set policies, reported KPIs and worked on the gaps the assessment surfaced.
What changed
The program’s average assessment score rose from 67 to 78.

A change in responsibility

From one product to a program.

Two different measures, shown within their own cases.

Philips India · 2019

One identity management product

Unit-test coverage

Before63%After86%

Led the work. On an identity management product, recorded in my 2019 review.

Definition and attribution

unit-test coverage in six months, with no extra people. On an identity management product, recorded in my 2019 review. The record documents the role as led.

Read the case
Philips North America · by 2022

Craftsmanship assessment program

Average assessment score

Before67 / 100After78 / 100

Accountable for the program. Across the assessment program I was accountable for.

Definition and attribution

average craftsmanship assessment score. Across the assessment program I was accountable for. The record documents the role as accountable.

Read the case
Open the full comparison

How the work travels

Follow the work after the handoff.

These are recurring approaches across different employers, not steps in one continuous program.

Make engineering self-service

A recurring approach: make the safe path something another team can run and maintain.

  1. Amazon · 2016

    Letting support own a catalog migration

    What I owned
    Built the XML parser and the migration procedure.
    What others did
    Support used the procedure with feed providers.
    What changed
    29 providers migrated without a developer running each one.
  2. Amazon · 2017

    One risk contract for six teams

    What I owned
    Designed the common risk request format.
    What others did
    Six client teams adopted the interface in their own services.
    What changed
    The teams could request risk evaluations through one contract.
  3. Philips North America · 2022

    Making a required security check self-service

    What I owned
    Helped the platform team shape reusable security workflows.
    What others did
    Product teams installed and maintained the scanner checks.
    What changed
    Setup moved from months to minutes.

Help colleagues teach the next team

A recurring approach: build local knowledge and give the next organizers room to carry it forward.

  1. IBM · 2010

    Giving engineers a place to try an idea

    What I owned
    Coordinated IBM India’s eighth Hackday.
    What others did
    An engineer on my team implemented the selected project in Pune.
    What changed
    The implementation received first place; the award belonged to the team.
  2. Exeter · 2014

    A Thursday for engineers across projects

    What I owned
    Started TExeter Thursday with a small volunteer group.
    What others did
    Engineers contributed talks and later organizers continued the series.
    What changed
    A cross-project technical exchange took hold at Exeter.
  3. Philips North America · 2025

    Teaching people who could teach the next team

    What I owned
    Ran a train-the-trainer class with Philips University.
    What others did
    A Bangalore team member became a local champion and led the team’s AI work.
    What changed
    The team built an end-to-end use case from knowledge transfer to test cases.

A career in five chapters

Choose a workplace to see a decision I made and what followed.

All stories

From the evidence archive

Browse evidence

Outside work

I organize book and school uniform drives, tell stories, and teach yoga and pranayama. I also explore AI with elementary school kids. One of our games is spotting the mistakes in an illustrated story.

Datta hands notebooks to children seated on mats in a village classroom.
Handing out notebooks on a school visit.
Datta hands school supplies to a student outside, beside the distribution vehicle.
Distributing supplies on a school visit.
Children sit in a circle on the floor for a yoga lesson.
Teaching yoga to children in a community classroom.
Students sit in a school courtyard facing Datta by the blackboard.
An open-air lesson at Gandinagar government high school.

Before the school year begins

In 2026, friends and colleagues made 22 contributions for rural schoolbooks. In our first recorded drive in 2015, nine contributions raised ₹37,500. The nine drive records show what we raised and who helped get the books to schools.

Follow the book drives

When the lemons became potatoes

I wrote a story about kids running a lemonade stand for my visit as a mystery reader. In one illustration, the AI turned a bag of lemons into potatoes. I left the mistake in. After each part of the story, the children had a minute to spot what had changed in the picture.

Read my classroom story