Product Digest Prompt and Context Engineering Certification
A certification for anybody building a feature on a language model. Six modules covering how a model reads a prompt, how a context window is assembled and budgeted, how to get output a program can rely on, how tools and agents are held together, and how any of it is tested. Ninety questions.
Practice questions (90)Free. Sign in to answer, so your result is kept and reported by module.
At a glance
Cost
Free There is no examination fee and no course fee.
Format
Six modules and a single assessment of 90 questions covering all of them. The reading is open to anyone. The assessment requires an account.
Pass mark
70 per cent, or 63 of 90, measured across the whole assessment rather than per module.
Prerequisites
None, and the material assumes no machine learning background. It does assume the reader has used a language model and wants to ship something built on one. Engineers, product managers, designers and analysts are all in scope, and the depth is set by the subject rather than by a job title.
Renewal
None. A result records the syllabus as it stood at the time of assessment.
Based on
The a syllabus developed by Product Digest, drawing on the published research on context and evaluation and on the patterns that have survived contact with production systems
What it covers
What it covers. Product Digest issues this certification. No external body accredits it and the assessment is not proctored. It gives a structured route through the material and a record that a candidate has completed the reading.
The title carries both terms on purpose. Prompt engineering is what most people search for and what most material still teaches. Context engineering is the name the work took once a single prompt stopped being enough, and it is where the difficulty actually sits. The course treats the first as a component of the second.
Two modules cover ground that prompting guides skip. Engineering the context takes the context window as a budget, sets out the four things a team can do with it, and names the ways a long context degrades rather than fails. Evaluating and testing treats a language model feature as something that cannot be tested like ordinary software and shows what replaces the unit test.
The material is vendor neutral. Model providers, their interfaces and their limits change faster than a syllabus can, so the pages teach the mechanism and name a vendor only where a specific behaviour is the vendor's own.
The syllabus6 domains · free
Product Digest’s own domains. Each opens its own page listing the concepts beneath it, and each concept has a page of its own.
A housing association holds 200 support policies, each running to about 1,500 words. An engineer proposes placing all of them in the window of a model that accepts 200,000 tokens, on the grounds that 300,000 words of policy is a small library and the window is large. Working from the published ratio of about four characters of English to a token, what does the arithmetic show?
AAbout 225,000 tokens, since a token is about three quarters of a word and three quarters of 300,000 words is 225,000, so the policies overflow by roughly an eighth.
BAbout 400,000 tokens, since 1,500 words is roughly 2,000 tokens and 200 policies at 2,000 tokens each is 400,000, which is twice the whole window before anything else is counted.
CAbout 300,000 tokens, since English runs to roughly one token a word once punctuation and spacing are counted in, so the policies overflow by half.
DThe policies fit, since the input and the generated answer are counted against separate limits and only the answer has to stay inside the 200,000.