Titles carry status, signal expertise, and encode values—they are shorthand for understanding another person, and research suggests they shape how work feels. With AI now handling more specialized tasks and the boundaries between design, engineering, and product management eroding, the question of what those titles mean has become harder to answer. Figma's research found that 64% of product builders now identify with two or more roles.
Why job titles still matter
Studies indicate that titles can affect satisfaction at work. One study authored by Adam Grant found that letting employees choose their own title improved psychological safety and reduced emotional exhaustion by up to 10% over five weeks. "Because job titles usually carry deep social and cultural meaning, the opportunity to create one's own job title may serve as a powerful starting point for job crafting and identity work," the report states.
Professional bodies have long formalized titles, among them RIBA, IMechE, IEEE, and the AMA. But the meaning of a title drifts with the era. A "designer" in 1950 worked on objects and printed visuals; few would have imagined a design profession centered on software. "Software engineer" first appeared in a 1966 letter from the Association for Computing Machinery president, and by 1968 a NATO-sponsored conference had convened professionals around what came to be called the "software crisis"—the difficulty of writing code for ever more powerful computers.
The last two decades of digital product work have moved quickly enough that titles feel more fluid than ever. Design leader Kim Lenox recalled calling herself an "international product manager, program manager, developer, and artist" during the original dot com boom; for the first ten years of her career, "HR didn't know what title—and job family—to give [her]." More recently the "prompt engineer" role rose fast and then cooled, and the question of what comes next remains open. Wharton professor Ethan Mollick, author of "Co-Intelligence," describes jobs as bundles of tasks whose weight and difficulty shift with technology.
Practitioners on labels
Nikolas Klein, a designer turned product manager at Figma, introduces himself as "a product designer in a PM trenchcoat." Titles give him career ladders and set expectations with new colleagues; his shift to product management changed how people read him before they had worked with him, letting his expertise in strategy, service design, and connecting dots lead while he spent less time on visual design.
Jake Albaugh, Developer Advocate at Figma, calls roles "always … a limitation," knowing definitions change as expertise grows. Still, he says, "Confidently labeling my role as 'software engineer' after some time as a web designer felt very empowering"—partly because roles track what the industry values: "People want to make sure they are being labeled in whatever way aligns to the value they offer to the industry."
Emmet Connolly, Intercom's senior vice president of design, is skeptical of relabeling: "Roles are clearly shifting, so I understand why people look for new labels to give things. But we have no idea what these roles are changing into, so picking a new name doesn't seem like an urgent priority to me. Let's figure out the bigger question of what the new role is."
On Lenny's Podcast, Julie Zhuo and Lenny Rachitsky each said they no longer identify as "designer" or "PM" but simply as "builders." Not everyone accepts the broader term. Interbrand Chief Creative Officer Fura Johannesdottir calls "builder" an executional role with no meaning: "Design is a way of seeing the world. It's not just a job; it's kind of a lifestyle. I always introduce myself as a designer, it has meaning for me." Ben Lehnert, design leader and Princeton design and entrepreneurship fellow, agrees: "I still very much identify as a designer because I think I've not found any better way to describe what I do."
Trade-offs of naming
No label is objectively better. "Designer" can convey gravitas or creativity; "engineer" can imply technical acuity or systems thinking. But roles can also be reductive—"Naming a thing can be both useful and limiting," Connolly says. Figma Advocate Kaitie Chambers warns against taking expansion too far: "My biggest concern is when people think we can replace these roles wholesale. I think that undermines the value of collective creativity and collaboration that empowers teams to do much more than any one person can alone."
New AI-enhanced workflows remain largely undecided. "Just as teams today are made up of people who are variously creative, technical, or analytical, so will AI-powered teams in the future," Connolly says. Albaugh's advice: "Let the work explain itself, not the role. Figure out what types of abstractions and explorations across all of product design and development are most interesting to you. Pursue the work, the labels will come later." The labels, after all, keep changing.



