The engineer who audited his own health the way he audits a service

What eight years at a desk in Hinjawadi actually does

The working day of a software engineer in an Indian technology park is not badly paid and it is not physically hard, which is exactly why it goes unexamined for a decade. Rohan Kulkarni's began with a cab from Baner at 8.40 a.m. and a coffee he counted as breakfast. Stand-up at ten. A block of deep work broken by the second and third coffees. Lunch in the cafeteria queue at 1.15, usually the rice counter because the queue for it moved fastest, eaten in eighteen minutes with a laptop open. Then the long flat afternoon, a 4 p.m. biscuit from the pantry, and a client call at 8.30 p.m. because the client was in Chicago.

Dinner was ordered at 9.50 p.m. from whichever app had a coupon, arrived at 10.35, and was eaten in front of a screen. On release weeks it was eaten at the desk. He walked, by his phone's own count, under three thousand steps on a normal weekday. He was thirty-two, his weight had moved by fourteen kilograms across eight years in a direction nobody notices year to year, and the company health check had started returning numbers in bold.

Nothing about that is a Pune story specifically. Swap Hinjawadi for Whitefield, Gachibowli, Magarpatta or Sector 62 and the shape holds: long sitting, a cafeteria optimised for throughput rather than for the person eating, a snack culture that runs on sugar because sugar is what the pantry stocks, and an evening that starts when the other hemisphere wakes up. The IT corridor has produced a very particular kind of health problem, and it is not an accident of individual willpower.

There is a second layer that rarely gets named. Engineering work is cognitively expensive and the body treats a hard debugging session much as it treats any other stress, which is why the pantry run at four o'clock is not really about hunger. A team under a delivery deadline eats worse than the same team in a quiet month, and the difference is not that anyone forgot how to eat. Add the sleep debt of a 2 a.m. deployment window, and appetite regulation itself starts working against the person, which is the part that no amount of resolve fixes.

Why an engineer's usual approach fails here

Engineers do not lack information. Rohan had read more about macronutrients than most people ever will, in the form of fitness subreddits, a nutrition app's blog, three YouTube channels and a colleague's confident opinions. That is precisely the problem. What he had was a large unstructured corpus with no way to rank its sources, no sense of which claims were established and which were somebody's supplement affiliate link, and no framework for Indian food at Indian portion sizes. Every plan he found assumed oats, chicken breast and a kitchen scale, and none of them assumed a mother-in-law's poha or a cafeteria with three counters.

The second failure is the one engineers make everywhere: he treated it as a problem to be solved once, in a burst, rather than a system to be maintained. He did four disciplined weeks in January, twice. Both times the first production incident of February ended it. A system that only survives when nothing goes wrong is not a system, and he knew that professionally long before he applied it to his own eating.

What a nutrition qualification changes for a working software engineer

Three concrete changes, none of which involved leaving the job.

1. It replaces a pile of opinions with one referenced framework

The single largest difference was having a hierarchy of evidence. A structured programme built on the ICMR-NIN Dietary Guidelines for Indians gives you a national reference for requirements, portions and food groups as they actually apply to a person eating Indian food. When a teammate forwards a claim about intermittent fasting or a seed oil, an engineer who has studied the subject can now say which part of it is established, which part is plausible and unproven, and which part is marketing. That is a small thing socially and a large thing internally.

2. It makes the constraints of the job designable

Once the framework was there, Rohan stopped trying to escape his schedule and started designing around it. The cafeteria rice counter stayed, but the plate composition changed. The 4 p.m. pantry biscuit became roasted chana kept in a desk drawer, which is not a heroic intervention but is one that survives a bad sprint. The 10.35 p.m. delivery order became a standing weeknight rule with two named exceptions, because a rule with declared exceptions holds and an absolute rule does not. He built a walking slot into the 30 minutes between the last stand-up and the client call, which was the only half-hour in the day nobody else wanted.

3. It opens a second line of work that is genuinely adjacent

This is the part most engineers are quietly asking about. A large number of people in Indian technology already run something on the side, and wellness coaching is unusual in that an engineer's existing skills transfer: structuring information, building a repeatable process, and being comfortable with a spreadsheet and a video call. Rohan took weekend consultations for desk-bound professionals, which is the client group he understands better than almost anyone, and it stayed a side practice rather than a career change. Some engineers go further and move into health technology product work, where actually understanding nutrition science is worth more than a course certificate on its own suggests.

The unexpected one was inside the team. Once a colleague knows you have studied the subject formally, you become the person the group brings its questions to: the teammate whose father has just been diagnosed with type 2 diabetes and who wants to know whether rice has to go; the woman on the platform team asking what to eat through a night shift; the manager who wants the offsite catering to be something other than a fried buffet. None of that is billable and none of it is a job title. It is, in Rohan's description, the part that made the six months feel worth the money before any client ever paid him.

Studying it around sprints, releases and an on-call rota

The honest constraint for an engineer is not the hours in a week. It is that the hours are not predictable. A fortnight can be flat and the next one can be a production incident that eats four evenings. Any commitment that requires attendance at a fixed weekly slot will break in month two, and blaming the learner for that is a design failure.

NNWA runs live classes in English and Hindi, records every session, and gives lifetime access to the recordings, with mentors reachable asynchronously. In practice that means an engineer studies the way an engineer already works: catch the live class when the sprint allows, watch the recording at 1.5x on a Sunday morning when it does not, and post questions to the mentor thread rather than waiting for a live slot. The Diploma runs six months, and the realistic weekly load is a few hours.

• Recordings mean an on-call week costs you the live session, not the module.
• Bilingual delivery matters more in engineering teams than people expect, because the language of the home kitchen is usually not the language of the codebase.
• Fully online with no campus and no commute, which for anyone already spending ninety minutes a day in a cab is not a small consideration.

Which NNWA programme fits a software engineer

For most engineers the flagship Diploma in Nutrition, Dietetics & Public Health is the right starting point: six months, ₹29,999, a 600-hour NCrF/NSQF Level 4 qualification, and the programme that carries the Medhavi Skills University Certificate for Skill Competency alongside NNWA's own certificate. MSU is recognised under section 2(f) of the UGC Act 1956 and is an NCVET-approved Awarding Body, and the partnership can be checked directly on the university's partner directory rather than taken on trust.

Engineers who want a narrower first step often take the Corporate Wellness Programme Management short course, because it maps onto the environment they already sit in, or Weight Management if the motivation is personal before it is professional. NNWA runs 72 courses across nutrition, dietetics, clinical care, fitness, yoga and wellness, which is one of the widest online catalogues in India, and the practical risk is choosing too many rather than too few. MSU certification applies to the flagship programmes, not to every short course, and it is worth being clear about that before enrolling.

One practical warning about the study itself, from a profession that is prone to it: engineers tend to over-optimise the learning and under-do the practice. The temptation is to treat the syllabus as documentation to be read at speed and the assessments as the deliverable. The part that actually changes anything is the applied work — building plans for real people with real kitchens, real budgets and real refusals. An engineer who skips that finishes with a certificate and a good recall of the theory, which is not the same as being able to sit across from a nervous forty-five-year-old and be useful.

Knowing which questions to refer, and to whom

The most useful thing a newly qualified engineer learns is where their own competence stops. A teammate on metformin asking whether he can stop taking it is a question for his doctor. A client with chronic kidney disease, a diagnosed eating disorder, a pregnancy with complications, or a child failing to gain weight all belong with a clinician or a registered dietitian, and the correct response is to say so in the first five minutes rather than the fiftieth. Non-clinical wellness and lifestyle work is a wide and genuinely useful field, and it has an edge.

Engineers tend to find this framing easy, because it is the same instinct as knowing when to escalate an incident rather than improvise a fix at 3 a.m. What surprises most of them is that referring makes them more trusted rather than less. A coach who hands a case on is visibly not the kind who has an answer for everything, and in a market full of confident people selling certainty about metabolism, being the one who says this is beyond me is a competitive position rather than an admission.

It is also worth knowing the shape of the wider field before you start. An NNWA certificate is a skill-enhancement qualification rather than a UGC degree, and the clinical route — hospital dietetics, therapeutic diets, Registered Dietitian status through Indian Dietetic Association registration — runs through a BSc or MSc in the subject. An engineer weighing a genuine career change should know both roads exist and pick deliberately. NNWA publishes its fees, syllabus and the scope of its certificates up front precisely so that choice can be made with the facts in hand.

Is it worth it for a software engineer?

It is worth it if you are already the person in the team who reads about this, if you want to build a weekend coaching practice on a client group you genuinely understand, or if you are moving towards health technology, corporate wellness or a product role where the domain is nutrition. It is also worth it, honestly, if the only goal is to stop running the same failed four-week experiment every January and to understand the subject well enough to build something that survives a release week.

It is not worth it if you want to become a clinical dietitian in a hospital — that is a degree route and no online certificate substitutes for it. It is not worth it if you expect a certificate to change your salary at your current employer, because it will not. And it is not worth it if you are looking for a diet plan; a diet plan costs a fraction of this and takes an afternoon. The programme is for the person who wants to understand the subject, not the person who wants an answer.