New Roles · Engineering AI Builders
Prompt Engineer. The role, the market signal, and how to build it in your org.
Designs, tests, and maintains prompt suites and evals. Often paired with agent-prompt and red-team teams at model labs.
13 postings · 10 distinct titles · from 260,470 real job postings · see the live data →
What the market calls it
Prompt EngineerPrompt Engineer, EvalsLLM Specialist
Hiring this role in our corpus right now
Accenture 3Gevernova 2Cognizant 1Adobe 1Anthropic 1
What the postings ask this role to do
221 tasks extracted from real Prompt Engineer job descriptions, classified Automate / Augment / Human-only. Only 3.6% can be fully automated: companies are hiring this role for the judgment, not the keystrokes.
Automate
- Conduct unit tests on developed code.
- Document prompt engineering processes.
- Document prompt engineering best practices.
- Execute source code for software applications.
- Maintain reusable prompt libraries and version control.
Augment
- Employ techniques to guide and enhance model responses
- Collaborate with domain experts to understand business needs and translate them into clear and effective llm prompts.
Human-only
- Make team decisions
How we build it in your org
From the market's version of this role to your version of it
1. Audit the work
Start Your Audit maps the tasks this role would own in your operation and classifies each one: what AI runs, what your people run with AI, what stays human.2. Define your version
Your team composes the job description for your org's variant of the role, grounded in the audited tasks rather than a copied template.3. Make people ready
A learning plan built from that job description, delivered in GenAI Sandboxes with Simulations and Competency Assessments. Readiness is demonstrated, not assumed.Build your own
Compose your org's Prompt Engineer job description
Start from the tasks real postings ask for, keep the ones that match your operation, add what is specific to you. The tasks carry their AI classification, so the JD you take away already says what AI runs and what stays with people.
Start with the work, not the org chart.
Run the audit on one operation and see what this role would own first.