Behind the Clinical Trial Data: A Programmer’s Career from Bangalore to Cambridge

Jennifer Clodia D’s experience in India and the UK offers a perspective on the technical work that helps clinical research teams turn study data into usable evidence.

Clinical research is often discussed through its most visible milestones: a study begins, results are announced, or a treatment moves towards regulatory review. Less visible is the work between those milestones, when information collected during a trial must be organised, checked and prepared for analysis.

Clinical programmers work within this process. Their responsibilities bring together software, statistics and an understanding of how clinical studies operate. A dataset must be structured consistently. Programming outputs must be checked against specifications. Questions about the data need to be resolved with the people responsible for collecting, managing and analysing it.

International standards developed by the Clinical Data Interchange Standards Consortium, or CDISC, provide common structures for organising and exchanging clinical research data. Applying those standards requires technical judgement as well as familiarity with the study itself.

For Jennifer Clodia D, a clinical SAS programmer based in Cambridge, this work has been the foundation of a career spanning more than a decade, beginning in Bangalore and continuing in the United Kingdom.

Building experience in Bangalore

Jennifer’s route into clinical programming began with an academic grounding in mathematics, statistics and computer science, followed by a master’s degree in statistics from Bangalore University. She joined PPD in 2015 and progressed through associate, programmer and senior programmer roles.

Her early responsibilities included preparing listings and analysis databases, working to programming specifications and supporting the checks needed to produce dependable study outputs. As her experience developed, she took on more complex data-transfer validation and worked with clinical data management and biostatistics teams to address study requirements.

That progression brought responsibilities beyond writing individual programs. Her work expanded to include project coordination, oversight of programming outputs and support for colleagues developing their own technical skills.

The distinction matters in clinical research. A program may run successfully while still producing results that require further investigation. Understanding the source data, checking assumptions and recognising when to involve another specialist are part of the job.

Jennifer’s experience in Bangalore gave her exposure to these interconnected responsibilities. Alongside SAS programming, she developed experience in validation, study delivery and communication across functions.

Continuing the work in the UK

Now working in the UK as a Senior Programmer Analyst at PPD, part of Thermo Fisher Scientific, Jennifer’s responsibilities include programming support and leadership across Phase II–IV studies.

Her career record includes work on interim analyses, preparations for data monitoring committee reviews and coordination with global study teams. These activities involve deadlines that must be managed alongside the need for careful checking and clear documentation.

Her current director has also highlighted Jennifer’s willingness to support difficult deliverables and step in when teams face crucial timelines. Such contributions are less visible outside a study team than a published research result, but they form part of the practical work required to keep a study moving.

Her move from India to the UK provides a useful perspective on the continuity of clinical programming across locations. The professional setting changes, while the work continues to depend on shared standards, reliable handovers and collaboration between specialists.

Rather than treating the two countries as separate career chapters, Jennifer’s experience illustrates how skills developed in one location can carry into an international research environment.

Improving the way teams work

A further part of Jennifer’s work concerns the processes surrounding individual studies. Her experience includes SDTM mapping, which organises study data into a standard structure, and the use of Pinnacle 21 tools to identify potential data-standard conformance issues.

She has also contributed to departmental working-practice documentation covering SDTM, interim analyses and automated validation. This kind of documentation helps teams explain how work should be performed and checked, making knowledge easier to share across projects.

Mentoring is another recurring responsibility. Jennifer has supported colleagues in SAS, CDISC standards and validation tools, linking technical instruction with the practical demands of study delivery.

These activities show how an experienced programmer’s contribution can extend beyond completing an assigned output. It can also involve helping colleagues understand a problem, documenting a repeatable approach and making the next piece of work easier to review.

Looking ahead

The direction emerging from Jennifer’s work is a practical one: more consistent programming workflows, reusable approaches where appropriate, and continued development of technical skills within study teams.

Her proposed focus in the UK builds on that experience, combining senior clinical programming responsibilities with mentoring and improvements to validation practices. The underlying ambition is to help teams manage demanding research work with greater consistency and clarity.

For an industry whose conclusions depend on the quality of its evidence, that is a consequential area of work. Jennifer’s career offers a view of the professionals behind the datasets, and of the technical judgement and collaboration required long before a clinical result reaches the public.

LinkedIn: https://www.linkedin.com/in/jennifer-clodia-aaa613142/