Published 1st August 2025

Can you tell me what your role is?

I’m a research software engineer at the University of Bristol and I’m working on the project called OpenGHG, which is working hand in hand with the Met Office as well as different universities.

How did you become an RSE?

Before becoming a research software engineer, I was in industry for around three years in total. There, I was working within the aerospace domain, and prior to that, I did a master’s at the University of Bristol. While doing my master’s, I was doing part-time work for the university to teach software to undergraduates and students preparing to take A-levels. So that is where I was doing my research regarding software and various ways to deliver an impactful coding experience.

At the time of the interview I’ve been an RSE at Bristol for around three months [at time of publishing this was a bit over two years!]

What is your favourite thing about your work and being an RSE?

My favourite thing about being in RSE is that whatever research I do, be it on the softwareside or technical aspects of the project’s actual research stuff, it is getting valued, both of them. There is also a lot of flexibility in the working space, motivation for different ideas, support and motivation to implement those ideas and increase the productivity, we can say, or increase the efficiency of the project and the team itself. These kinds of things are really making me happy in the role of RSE.

What have you found surprising about your work?

To answer that question, I would refer to my master’s journey. Prior to doing my master’s, I was a software development engineer at Infosys India, where I felt like I was doing a lot of practical stuff, production stuff, and I needed to get connected with the academics. That’s when I decided to do my master’s. While doing my master’s, I found out that I can teach software as well as do research and things somehow started coming together for me. That is how these things started for me to get into the RSE field.

As a new RSE, how have you or what interactions did you have with the community and the society before becoming an RSE? And how do you feel now?

That’s actually a very good question. That’s the main motivator for me because when I was in the industry, I was feeling like I was somehow disconnected from the community. I was a software engineer, but I used to still feel like I was disconnected from the community. That meant for me to get in touch with the community of the software industry or what we call the social community, I had to always get out of my way, do some extra work and then get connected with the community. However, with being an RSE, it’s completely different. I can openly discuss the technical difficulties that I am facing within the RSE community or within the research community. I don’t have to now go out of my way to get in touch with the people who are just software engineers or who are working in social aspects, because RSEs, I feel somehow they are blend of both, which touch base upon the social aspects, like we discussed about democratizing the software in yesterday’s keynote. Which basically meant to make software and its benefits accessible to a wider community, apart from traditional IT.  So these kinds of things are happening in the RSE, which I did not get in the industry, which I felt is a very good thing for me that I am doing what I love from the technical aspects, social aspects, both on the team.

Can you talk a little bit more about that? You mentioned democratization, is there any other kind of principle that you feel you’ve seen embodied in the community?

Yes, definitely. I can try to elaborate on what I said earlier.

First of all, as an RSE, I truly feel like a part of the scientific community. In the broader industry, there’s often this perception that software developers are a different breed altogether—but in the RSE community, it doesn’t feel that way. While discrimination can exist in some places, in my experience, whether it’s in my current role or in interactions with RSE leaders, I haven’t encountered that divide. You’re valued for what you contribute—your work, your ideas, and the tools and solutions you bring to the table.

Regarding democratization, I believe that as members of the scientific community, it’s our responsibility to ensure our work has real-world impact. Every new idea should go through a process—thorough research, understanding its potential implications, and then implementation—to ensure it benefits society. These values are something I’ve consistently seen reflected in the RSE community.

Take data sensitivity, for example. We discussed the idea of Trusted Research Environments (TREs), which are often managed by RSEs. These environments make sensitive data more accessible to researchers while maintaining governance and privacy. As a result, researchers can generate meaningful outcomes—positive or negative—more easily and responsibly. This, to me, is a clear example of how we can make data more available while still respecting governance frameworks. It’s a crucial balance, and one that highlights the importance of our role.

Another aspect that stands out is the flexibility and openness around software adoption. From my personal experience in the industry, adopting a better software tool often required building a strong business case, navigating bureaucracy, and waiting a long time for approval—just to move from a legacy tool to something more efficient. In contrast, as an RSE, while we still need to justify our choices, the focus is on demonstrating utility, impact, and productivity. The decision-making is collaborative and happens quickly, which means we can stay at the forefront of both scientific and technological advancements.

So ultimately, what I was trying to express earlier is this: if a new idea or tool can bring about meaningful change and benefit the broader community, there’s a strong willingness to embrace it. That mindset—that drive to create impact—is what makes being an RSE so rewarding for me.

As a relatively new research software engineer that’s moved from industry, maybe if you want to talk about coming from another country as well, what advice would you give to someone in your situation a few years ago who wants to get into research software engineering?

First of all, I’d say that for me, teaching has always been a passion. Back in India, when I was doing my bachelor’s in mechanical engineering, I used to tutor students part-time in subjects related to the mechanical field. But as I started learning more about software and how it’s transforming the mechanical industry, I became really interested in that space and eventually transitioned into it. I wanted to leverage the best of what technology had to offer.

To anyone who’s in a similar position to where I was a few years ago—maybe you’ve come to the UK to study, or you’re working but feeling uncertain or unfulfilled—my advice would be: stay open to technology. Be curious, be research-minded, and don’t limit yourself to just one path. For example, if you’re pursuing a master’s in robotics, don’t focus only on robotics. That field is a blend of electronics, mechanical systems, software, and machine learning. Try to explore each of those areas a bit. You never know which one might spark your interest or open new opportunities.

Once you start understanding the software and automation side of things, I genuinely believe you’ll naturally feel drawn to fields like Research Software Engineering. It won’t require any external motivation—your own curiosity and passion will guide you there.

So, in short: be open, be adaptable, and explore beyond the boundaries of your degree. That’s what helped me, and that’s what I would encourage others to do as well.