Prompt Engineer
Prompt Engineers design, test, and optimise the instructions that guide large language model behaviour. Their daily English covers writing and documenting prompt templates, explaining chain-of-thought reasoning to stakeholders, communicating output quality trade-offs to product teams, and writing evaluation criteria for prompt changes. This path builds the vocabulary for discussing prompt design patterns, output quality, and the language of LLM-powered system design.
Topics covered
- Prompt design patterns
- Chain-of-thought reasoning
- Few-shot learning
- System prompt architecture
- Prompt versioning
- Output quality evaluation
Vocabulary spotlight
4 terms every Prompt Engineer should know in English:
A prompting technique that instructs the model to reason step-by-step before giving a final answer — improving accuracy on complex reasoning tasks
"Adding 'think step by step' to the prompt improved the model's accuracy on multi-step maths problems from 43% to 78%."
Providing a small number of input-output examples in the prompt to demonstrate the desired response format or behaviour without fine-tuning
"Three few-shot examples were enough to get the model to consistently output structured JSON in our required format."
The initial instructions provided to an LLM before a user conversation begins — defining the model's persona, constraints, output format, and task scope
"The system prompt specifies that the assistant should never discuss competitor products and always respond in the user's language."
A parameter controlling the randomness of LLM outputs — lower values produce more deterministic responses, higher values increase creativity and variation
"We set temperature to 0.1 for the classification task where consistency matters and 0.8 for the creative writing feature."
📚 Vocabulary Reference
Key terms organised by category for Prompt Engineers:
Prompting Techniques
Prompt Components
Parameters
Quality & Versioning
Recommended exercises
Real-world scenarios you'll practise
- Writing a system prompt specification document: explaining persona, constraints, output format requirements, and the rationale for each design decision
- Presenting prompt A/B test results to a product team: explaining what changed, why the metrics improved, and what edge cases remain
- Explaining chain-of-thought prompting to a stakeholder who wants faster, cheaper LLM calls and is pushing back on the longer reasoning steps
- Writing a prompt versioning changelog: documenting what changed between prompt versions and the evaluation results that justified each change
Recommended reading
Frequently Asked Questions
What English skills do Prompt Engineers most need to improve?+
Prompt Engineers most commonly need to improve: technical vocabulary (the correct English terms for domain concepts), collocation accuracy (using the right verb for each action), written communication (bug reports, PR descriptions, technical docs), and spoken communication for standups, code reviews, and stakeholder meetings.
How long does the Prompt Engineer learning path take?+
The Prompt Engineer learning path contains 20–40 hours of material studied comprehensively. Most learners focus on the highest-priority modules first and return to the rest over time. Spending 30 minutes per day for 4–6 weeks produces noticeable improvement in workplace English.
What vocabulary should a Prompt Engineer prioritise first?+
Start with the vocabulary that appears most in your daily work — terms you read in documentation, use in commit messages, and hear in meetings. The Prompt Engineer path begins with the most frequent vocabulary clusters before moving to advanced communication patterns.
Are there interview exercises for Prompt Engineer roles?+
Yes. The Prompt Engineer path includes role-specific interview question modules with model answers and key phrases — the actual questions interviewers ask and the vocabulary needed to answer them fluently. There is also a dedicated Interview Practice hub for general interview skills.
Does this path include pronunciation help?+
Yes. The path links to pronunciation exercises for the technical terms most commonly mispronounced in this domain. The Pronunciation hub includes drills for acronyms, silent letters, word stress, and minimal pairs — all in IT context.
What are the most common English mistakes Prompt Engineers make?+
The most common mistakes: incorrect collocations (using the wrong verb with a technical noun), false friends from L1, tense errors when narrating past incidents or walkthroughs, and using overly formal or overly casual register in written communication.
How do I improve my English for code reviews?+
Learn the standard code review collocations: approve a PR, request changes, leave a nit, address feedback, block a merge, resolve a conversation. Use hedging language for suggestions: "This might be cleaner as…", "Have you considered…?". The Collocations section includes a dedicated Code Review set.
Can I use this path alongside my daily work?+
Yes — the path is designed for working professionals. Each exercise set takes 10–15 minutes. The most effective approach is to study a vocabulary module before a meeting or task where you'll use that vocabulary, then practise immediately after. Context-linked practice produces much faster retention.
Is the content free?+
Yes, completely free. No registration required, no payment, no time limit. All vocabulary modules, exercises, glossary entries, and learning path guides are open access.
How do I track my progress through this path?+
Progress is tracked in your browser's local storage — completed exercise sets are marked with a checkmark when you return. No account is needed. You can bookmark specific modules and use the exercises overview to see which sets you've completed.