Rudrajit Choudhuri

Rudrajit Choudhuri

Auto-generated profile, based on publicly available information

Rudrajit Choudhuri

Oregon State University, Corvallis, USA

Research Focus & Metrics

Academic Career Length

5Years (2022-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
12 April 2024
Verified
Conference Paper
Open access
RCRudrajit Choudhuri
Rudrajit Choudhuri
DLDylan Liu
Dylan Liu
ISIgor Steinmacher
Igor Steinmacher
MGMarco Gerosa
Marco Gerosa
ASAnita Sarma
Anita Sarma
Conversational Generative AI (convo-genAI) is revolutionizing Software Engineering (SE) as engineers and academics embrace this technology in their work. However, there is a gap in understanding the current potential and pitfalls of this technology, specifically in supporting students in SE tasks. In this work, we evaluate through a between-subjects study (N=22) the effectiveness of ChatGPT, a convo-genAI platform, in assisting students in SE tasks. Our study did not find statistical differences in participants' productivity or self-efficacy when using ChatGPT as compared to traditional resources, but we found significantly increased frustration levels. Our study also revealed 5 distinct faults arising from violations of Human-AI interaction guidelines, which led to 7 different (negative) consequences on participants.

22 October 2022 in Neural Computing and Applications
Verified
Journal Article
Closed access
PDF file
RCRudrajit Choudhuri
Rudrajit Choudhuri
AHAmiya Halder
Amiya Halder

12 April 2026
Verified
Conference Paper
Open access
RCRudrajit Choudhuri
Rudrajit Choudhuri
CBCarmen Badea
Carmen Badea
CBChristian Bird
Christian Bird
JBJenna L. Butler
Jenna L. Butler
RDRobert DeLine
Robert DeLine
BHBrian Houck
Brian Houck
Generative AI is reshaping software work, yet we lack clear guidance on where developers most need support and how to design it responsibly. We report a large-scale, mixed-methods study of N=860 developers examining where, why, and how they seek or limit AI across SE tasks. Using cognitive appraisal theory, we provide the first empirically validated mapping of developers’ task appraisals to AI adoption patterns and Responsible AI (RAI) priorities. Appraisals predict AI openness and use, revealing distinct patterns: strong current use and demand for improvement in core work (e.g., coding, testing); high demand to reduce toil (e.g., documentation, operations); and clear limits for identity- and relationship-centric work (e.g., mentoring). RAI priorities vary by context: reliability and security for systems-facing tasks; transparency, alignment, and steerability to maintain control; and fairness and inclusiveness for human-facing work. Our results offer concrete, contextual guidance for delivering AI where it matters to developers and their work.

3 September 2025 in Empirical Software Engineering
Verified
Journal Article
Open access
PDF file
CCChimdi Chikezie
Chimdi Chikezie
PCPannapat Chanpaisaeng
Pannapat Chanpaisaeng
PAPuja Agarwal
Puja Agarwal
SASadia Afroz
Sadia Afroz
BMBhavika Madhwani
Bhavika Madhwani
MBMargaret Burnett
Margaret Burnett
Software producers are now recognizing the importance of improving their products’ suitability for diverse populations, but little attention has been given to measurements to shed light on products’ suitability to individuals below the median s ocio e conomic s tatus (SES)—who, by definition, make up half the population. To enable software practitioners to attend to both lower- and higher-SES individuals, this paper provides two new surveys that together can facilitate measuring how well a software product serves socioeconomically diverse populations. The first survey (SES-Subjective) is who-oriented: it measures who their potential or current users are in terms of their subjective SES (perceptions of their SES). The second survey (SES-Facets) is why-oriented: it collects individuals’ values for an evidence-based set of facet values (individual traits) that (1) statistically differ by SES and (2) affect how an individual works and problem-solves with software products. The surveys’ design goal is worldwide applicability, but as a first step, here we empirically validated both these surveys with deployments at University A and University B (464 and 522 responses, respectively), which showed reliability of both the surveys in a US context. Our results also statistically agree with both ground truth data on respondents’ socioeconomic statuses and with predictions from foundational literature. Finally, we explain how the pair of surveys can be uniquely actionable by software practitioners, such as in requirements gathering, debugging, quality assurance activities, maintenance activities, and fulfilling legal reporting requirements such as those being drafted by various governments for AI-powered software.

22 August 2026 in ACM Transactions on Software Engineering and Methodology
Verified
Journal Article
Open access
RCRudrajit Choudhuri
Rudrajit Choudhuri
BTBianca Trinkenreich
Bianca Trinkenreich
RPRahul Pandita
Rahul Pandita
EKEirini Kalliamvakou
Eirini Kalliamvakou
ISIgor Steinmacher
Igor Steinmacher
ASAnita Sarma
Anita Sarma
Generative AI (genAI) tools promise productivity gains, yet developers still struggle to determine when to trust and effectively integrate these tools into their everyday work. Moreover, genAI can be exclusionary, failing to adequately support developers across individual differences. One such difference is cognitive style , which can shape how developers engage with genAI (e.g., risk-averse developers may gate outputs behind tests, whereas risk-tolerant ones may prototype directly and address issues post hoc). When tools fail to accommodate these differences, they can create additional usability barriers. Thus, to design tools that developers intend to use, we must understand which factors shape developers’ trust in and adoption of genAI at work . We developed a theoretical model of developers’ trust and adoption of genAI using a large-scale survey ( N = 238) conducted at GitHub and Microsoft. Using Partial Least Squares Structural Equation Modeling (PLS-SEM), we found aspects related to genAI’s system and output quality (e.g., presentation, safety/security, and performance), functional value (e.g., educational and practical benefits), and goal maintenance (ability to sustain alignment with task goals) to be significantly associated with trust. Trust, alongside developers’ cognitive styles (i.e., risk tolerance, technophilic motivations, and computer self-efficacy), was in turn significantly associated with adoption intentions, which ultimately were associated with reported usage. An Importance-Performance Matrix Analysis (IPMA) identified high-importance factors for which existing genAI tools provided insufficient support, highlighting actionable targets for design improvements. We bolstered these findings through a qualitative analysis of developers’ reported challenges and risks of genAI use, uncovering why these gaps persisted in development contexts. Our study offers practical guidance for designing genAI tools that support trustworthy and inclusive developer–AI interactions.

12 August 2024
Verified
Conference Paper
Open access
ACAmreeta Chatterjee
Amreeta Chatterjee
RCRudrajit Choudhuri
Rudrajit Choudhuri
MSMrinmoy Sarkar
Mrinmoy Sarkar
SCSoumiki Chattopadhyay
Soumiki Chattopadhyay
DLDylan Liu
Dylan Liu
ASAnita Sarma
Anita Sarma
Online computer science (CS) courses have broadened access to CS education, yet inclusivity barriers persist for minoritized groups in these courses. One problem that recent research has shown is that often inclusivity biases (“inclusivity bugs”) lurk within the course materials themselves, disproportionately disadvantaging minoritized students. To address this issue, we investigated how a faculty member can use AID—an Automated Inclusivity Detector tool—to remove such inclusivity bugs from a large online CS1 (Intro CS) course and what is the impact of the resulting inclusivity fixes on the students’ experiences. To enable this evaluation, we first needed to (Bugs): investigate inclusivity challenges students face in 5 online CS courses; (Build): build decision rules to capture these challenges in courseware (“inclusivity bugs”) and implement them in the AID tool; (Faculty): investigate how the faculty member followed up on the inclusivity bugs that AID reported; and (Students): investigate how the faculty member’s changes impacted students’ experiences via a before-vs-after qualitative study with CS students. Our results from (Bugs) revealed 39 inclusivity challenges spanning courseware components from the syllabus to assignments. After implementing the rules in the tool (Build), our results from (Faculty) revealed how the faculty member treated AID more as a “peer” than an authority in deciding whether and how to fix the bugs. Finally, the study results with (Students) revealed that students found the after-fix courseware more approachable - feeling less overwhelmed and more in control in contrast to the before-fix version where they constantly felt overwhelmed, often seeking external assistance to understand course content.