Learn the work behind Data, AI & Forward Deployed Engineering
Practical explanations, career decisions and reproducible workflows. Read the reasoning, inspect the evidence and follow the next skill into a real programme.
Write a model adaptation experiment report
An experiment report should let a reviewer understand the decision and a practitioner reproduce the run. A list of hyperparameters without data, environment, adverse results and acceptance criteria is incomplete.
Write a model card for a portfolio project
A model card helps a reader understand what a model was built to do, how it was evaluated and where its evidence ends. It should summarize an actual experiment, with links to supporting artifacts, rather than read like a
Write a model selection decision record
A leaderboard or one demo cannot explain why a model fits an application. A decision record ties selection to the exact task set, constraints, configuration and evidence available at a date.
Write a one-page scope with explicit exclusions
Scope protects the client and delivery team by making the promised boundary visible. Exclusions are especially important for a portfolio simulation.
Write a project README that an interviewer can verify
A useful project README lets a reader understand the question, run the work and compare the output with a stated expectation. It should also explain what you contributed, what the data represents and which conclusions th
Write a Python function with a clear input contract
A useful function contract states what inputs mean, which values are valid, what the function returns and how invalid input fails. Type hints help communicate that contract, but Python does not automatically enforce ever
Write a reusable Python module from a notebook
Extract the stable calculation into functions with explicit inputs and outputs, then let the notebook call those functions. Keep exploratory charts and narrative in the notebook while moving repeatable parsing, validatio
Write a structured-output contract for an LLM task
“Return JSON” specifies a serialization format, not the business contract. A useful output definition states required fields, allowed values, bounds, evidence relationships and what to emit when the task cannot be suppor
Write an agent runbook for partial completion
Multi-step work rarely fits “success” or “failed.” A run may validate, retrieve and draft successfully before ticket creation fails. Operators need exact side effects and a safe resume path.
Write an AI assurance report with reproducible evidence
An assurance report should let an independent reviewer understand what the system does, what was tested, what failed and which conclusions are still conditional. It is an evidence index, not a confidence statement.
Write an AI incident postmortem from trace evidence
An AI incident review should reconstruct what the system did and why its controls failed. A transcript alone rarely shows retrieval, versions, tool decisions, validators or missing alerts.
Write an AI statement of work with measurable acceptance
An AI statement of work should make disagreement cheap. A sponsor, engineer and reviewer must be able to tell what will be delivered, what evidence accepts it and which dependencies can stop the schedule.
Not sure which programme fits?
Tell us your background and we will map it to the right entry point — including saying so when a cheaper programme is the better fit. A counsellor replies within one working day.