Back to all careers
๐ŸŽฏ
AI ยท Entry level

AI Prompt Engineer

Design and optimize prompts for large language models. Help organizations get maximum value from AI tools like ChatGPT, Claude, and Gemini.

Salary
$95,000
$70,000 to $130,000
Demand
High
Time to entry
1 to 2 months
Difficulty
Entry
A Day in the Life

What a typical day looks like

Prompt engineering as a standalone role is a 2024 invention. Most days I'm working at the intersection of product, AI, and content. Mornings start with reviewing prompt performance from yesterday โ€” looking at outputs that users rated poorly, finding patterns, then crafting better prompts. By 10 I'm usually iterating on a specific prompt โ€” running it through dozens of variations to see which performs best across a test set. Afternoons are more collaborative: working with product to define success criteria for a new AI feature, working with engineering to wire up new prompt versions, working with subject matter experts to verify outputs are actually correct. The field changes every week. A good prompt engineer is part writer, part data analyst, part product designer.

Hour-by-hour

9:00
Coffee. Check evaluation dashboard. Yesterday's prompt change improved accuracy by 8% but increased latency by 200ms. Trade-off discussion needed.
9:30
Look at the 20 worst-scoring outputs from yesterday. Find a pattern: the model is hallucinating dates.
10:00
Iterate. Try 3 different prompt structures to fix the date hallucination. Test each on the same 50 examples.
11:30
Standup. Update the team on the date issue. Decide to add a date-validation step before showing to users.
12:00
Lunch. Read the latest Anthropic blog on chain-of-thought prompting.
13:00
Meeting with subject matter expert (a doctor) to verify the model's medical answers. They flag 3 wrong, 17 correct.
14:00
Build a new evaluation set based on what the doctor flagged. Add to the automated test suite.
15:00
Pair with the engineer who deploys our prompts. Walk through how to A/B test the new variant.
16:30
Write up findings in our 'prompt experiments' Notion doc. Track what worked, what didn't, why.
17:30
Done. Push the new prompt to staging for tomorrow's broader test.

Skills you need

Required

LLM KnowledgePrompt EngineeringCritical ThinkingCommunicationDomain Expertise

Nice to have

PythonAPI IntegrationFine-tuning ConceptsRAG Systems
Portfolio Projects

Build these to stand out

Hands-on projects beat any CV bullet point. Pick one and finish it.

Beginner 1 weekend

Prompt Engineering Cookbook

Pick a real task (e.g. summarising news, writing job descriptions, explaining code). Try 10 different prompt structures (zero-shot, few-shot, chain-of-thought, role-based, structured output). Document results with concrete examples. Publish on GitHub.

Tech: OpenAI API or Claude API, Python, Jupyter Notebook
Why it helps

Shows you understand prompting beyond 'be polite to the AI'. Standout portfolio piece.

Intermediate 2 weekends

Evaluation Harness for LLM Outputs

Build a small Python framework that takes a list of prompts, runs them against an LLM, and scores the outputs against criteria you define (accuracy, length, tone, factual correctness). Can use another LLM as judge.

Tech: Python, OpenAI or Anthropic API, JSON-based eval datasets
Why it helps

Evaluation is the unsexy but critical part of prompt engineering. Most candidates miss it.

Intermediate 2 to 3 weekends

Specialised AI Assistant

Build a small Streamlit or web app that uses an LLM to do one thing very well: e.g. a code reviewer, a meeting note summariser, a recipe generator. Polish the prompt until outputs are consistently good. Deploy publicly.

Tech: Streamlit or Next.js, OpenAI/Claude API
Why it helps

Working AI products are more impressive than theoretical prompt knowledge.

Help someone else find this

This is free, no ads. Share with anyone preparing for the test.