Why 'Prompt Engineer' Splintered Into Other Roles Rather Than Disappearing

The title 'prompt engineer' never described a single job but rather four distinct activities: discovery, craft, systematisation, and evaluation, which emerged simultaneously when working with AI models was still largely experimental. As the field matured, each activity migrated into existing roles — craft merged into application engineering, systematisation became standard software practice, and evaluation grew into its own discipline on larger teams. Discovery, the most prominent early activity, had the shortest lifespan since documented techniques quickly replaced the need for individual experimentation. A structural problem also hastened the role's fragmentation: prompt authors who did not own the surrounding system had no way to measure whether their changes worked, making the standalone role untenable. The broader pattern mirrors how every new technical skill eventually gets absorbed into the roles that control the systems it depends on.