Prompt evaluation harness
Deliverable: A test set of at least fifty cases with scoring criteria, comparing three prompt strategies with measured quality differences rather than impressions.
Course
A short, applied track for people who already program — prompting with evaluation attached, retrieval systems, and the guardrails that separate a demo from something you can ship.
6 modules · 3 months
Deliverable: A test set of at least fifty cases with scoring criteria, comparing three prompt strategies with measured quality differences rather than impressions.
Deliverable: A working RAG application over a private document set, with a documented chunking and retrieval strategy, a groundedness evaluation, and an honest list of queries it still answers badly.
Deliverable: A pipeline extracting structured records from unstructured documents, with schema validation, a measured accuracy figure and defined behaviour when extraction fails.
Deliverable: A set of adversarial inputs against your own application, with the failures found, the guardrails added, and evidence of what those guardrails do and do not stop.
Every student gets placement assistance — that is what 100% placement assistance means. It is support for all, not a job for all. We do not promise a specific salary, a specific number of interviews, or placement at any named company, and you should be wary of anyone who does.
Build the test set before you build the feature.
Most people iterate on prompts by feel. They change a wording, the output looks better, they declare success. Then it behaves differently on the twentieth input and nobody knows why, because there was never a baseline.
Every applied module here requires an evaluation set first. By the end you will be able to say that a change improved groundedness on a fifty-case set — which is the difference between an opinion and a result, and it is the single most employable habit in applied AI right now.
You need to program already. That is a firm prerequisite rather than a suggestion.
The reason is that the interesting work is not the model call — it is everything around it. Handling a timeout. Deciding what to do when retrieval returns nothing. Structuring the application so a prompt change does not require a rewrite. Debugging why extraction works on one document format and fails on another.
Someone without programming fundamentals can produce a working demo and cannot progress past it, which is a frustrating place to be and a crowded one.
Retrieval-augmented generation is presented almost everywhere as the answer to hallucination. It is not.
RAG grounds a model in documents you supply. It does not stop the model misreading them, combining two passages into a false claim, or answering confidently when retrieval returned nothing relevant. Those failure modes remain, and they are subtler because the output now cites a source.
Module four spends real time on diagnosing whether a bad answer came from retrieval or from generation, because the fixes are completely different and teams routinely spend weeks fixing the wrong one.
Three months makes you capable of building, evaluating and shipping LLM features, and of telling a colleague why a proposed approach will not work.
It does not make you a machine learning engineer, and it does not replace software engineering fundamentals if you want to work on production AI infrastructure. We say so on the first day.
Questions
The AI course is a six-month track that builds machine learning and deep learning foundations first, then covers generative AI on top. This is a focused three-month track that assumes you already program and goes straight to applied LLM work. Choose this if you want to build AI features soon; choose the AI course if you want the underlying foundations too.
No, but you do need to program comfortably in Python. This track treats the model as a component you build around rather than something you train, which is what most applied AI work actually involves. If you want to train and evaluate models yourself, the AI or data science course is the right choice.
No, and no three-month course honestly can — pretraining a competitive model costs millions of dollars. You will learn to build applications around existing models, retrieve against private data, and evaluate output rigorously. That is what applied roles hire for.
The narrow version — collecting clever phrases — was always thin and is fading. The durable version is building an evaluation set, measuring whether a change helped, and designing systems that degrade sensibly when the model gets something wrong. That is engineering, and this course is built around it rather than around prompt lists.
Three details is all we need. A course advisor will call you back.
Python, machine learning foundations and applied generative AI in one track — ending with a retrieval-augmented application you have built, evaluated and can explain end to end.
Python taught as a working tool rather than a syntax tour — you finish able to read unfamiliar code, automate real tasks, call APIs and write tests that catch your own mistakes.
Classical machine learning done properly — feature engineering, honest evaluation, and the discipline to notice when a good score is an artefact rather than a result.
Next step
Tell us what you want to learn and we will help you pick the right course, batch and mode.