Role and Identity Work of Software Engineering Professionals in the Generative AI Era
This paper argues that the influence of Generative AI on software engineers' identity work varies significantly across different roles, such as developers and testers, and proposes a research agenda to investigate these role-specific dynamics in order to develop better support artifacts and practical implications for the industry.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine the world of software engineering as a bustling, high-stakes kitchen. For decades, the chefs (developers) have been the stars, chopping vegetables, searing steaks, and plating the final dishes. The taste testers (quality assurance engineers) have been the unsung heroes in the corner, occasionally checking a dish before it leaves the kitchen, often feeling like they were the "second-class citizens" of the culinary world.
Now, a magical new kitchen robot has arrived: Generative AI (GenAI). This robot can chop, sear, and plate entire meals in seconds.
This paper, written by Jorge Melegati, asks a very human question: When the robot does the cooking, who are the chefs and the testers now? And how does that change how they see themselves?
Here is the breakdown of the paper using simple analogies:
1. The Problem: Everyone is Changing Their Uniform
In the past, a software developer's identity was like a chef's hat: "I am the one who creates the code." A tester's identity was like a health inspector: "I am the one who finds the mistakes."
But with the new AI robot, the workflow is shifting.
- The "Vibe Coding" Shift: Developers are starting to spend less time cooking (writing code from scratch) and more time tasting and critiquing the robot's output. They are becoming more like editors or taste-testers.
- The Identity Crisis: If a developer's whole identity was "I am a creator," but now they are mostly "I am a reviewer," they might feel lost. They might ask, "Am I still a chef, or am I just a food critic now?"
2. The Twist: Not Everyone Feels the Same Way
The author argues that we can't treat all software workers the same.
- Developers (The Chefs): They might feel threatened. If the robot does the hard work, do they lose their value? Or do they feel relieved they don't have to do the tedious chopping anymore?
- Testers (The Inspectors): They might feel a mix of emotions. On one hand, their job is becoming more important because the robot makes mistakes, and someone has to catch them. On the other hand, they've always felt like "second-class citizens." Now, if developers are just "vibe coding" and handing off the robot's messy output to testers, the testers might feel even more overwhelmed or undervalued.
The Analogy: Imagine a soccer team where a new robot starts playing the goalkeeper. The human players might panic: "Do I still need to be a striker? Or do I just kick the ball to the robot and watch?" The paper suggests that the "Striker" (Developer) and the "Defender" (Tester) will react to this robot differently, and their feelings about their own jobs will change in different ways.
3. The Proposed Plan: A Research Roadmap
The author isn't just complaining; they are proposing a plan to study this. Think of it as a five-step recipe for understanding the future:
- Step 1 & 2 (The Baseline): First, we need to ask the chefs and the inspectors, "Who do you think you are right now, before the robot fully takes over?" We need to map out their current feelings.
- Step 3 (The Trigger): Next, we watch what happens when they start using the robot. Do the chefs feel angry? Do the testers feel anxious? We want to see how they change their "uniforms" (identities) to fit the new reality.
- Step 4 (The Team Dynamic): How does the robot change the relationship between the chef and the inspector? Do they start fighting more? Do they start respecting each other more?
- Step 5 (The Solution): Finally, based on what we learn, we will design new "kitchen rules" and tools. Maybe we need to create a new job title, like "AI-Human Team Manager," or change how we train new chefs so they don't panic when the robot arrives.
4. Why Does This Matter?
If we ignore this, we might end up with a kitchen full of unhappy, confused staff who feel like their jobs don't matter anymore. This leads to burnout and bad software.
But if we understand these feelings, we can:
- Train people better: Teach students and workers how to be "AI-Chefs" rather than just "Code-Cookers."
- Fix the team: Stop the fighting between developers and testers and make them a cohesive unit.
- Keep the humans happy: Ensure that even with the robot, the humans still feel proud, useful, and essential.
The Bottom Line
Generative AI is a powerful new tool, but it's not just a technical upgrade; it's a psychological earthquake for software workers. This paper argues that to survive the earthquake, we need to understand how different roles (like developers vs. testers) are reacting, so we can build a future where humans and AI work together without anyone losing their sense of self.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.