Prompt engineering should not be a job title. It is a coping mechanism wearing a LinkedIn badge.

I have watched teams turn “prompt engineer” into a role because they needed to explain why the model behaved badly. The model was undertrained, context was missing, evaluation nonexistent, or somebody wanted prompt magic to compensate for not doing the work. Hiring someone to write a clever instruction fixes none of that. It just moves the blame downstream.

The ugly truth: most prompt engineering is requirements gathering, information architecture, evaluation design, and ruthless iteration. Those are valuable skills. Calling them “prompt engineering” makes them sound like mystical prompt whisperers. I have watched “prompt engineers” land roles for reciting tricks, only to discover the real job was writing test cases and staring at dashboards.

If you cannot explain what “good” means, how you measure it, and why one output beats another, you are not engineering prompts. You are decorating a wish and asking the model to fulfill it.

Keep the title if it accurately describes your work. Otherwise, admit you are a product engineer, AI developer, or evaluator. A precise title will never embarrass you; a fashionable one eventually will.