Final assignment

After Module 5
about 2 hr

What you will be able to do

Bring the whole course together in one document: a career transition brief. It says where you are going, what you already bring, what you must learn, in which order, and how you will show it. You can give it to a mentor or a manager, and you can use it to check your progress every month.

Before you startWhat to know and to have readyAbout 120 minutes

What you need to know

You completed Modules 1 to 5. Each part below names the lessons and the notes.md sections that it uses.

What you need

Your notes.md, with the sections from the guided practices. The brief uses these most:
- ## My route, from Choose a realistic route: Guided practice: your choice.
- ## My head start, ## Domain card and ## Inventory with evidence, from Your experience is a head start, Domain knowledge in practice and Evidence over self-ratings.
- ## Course order, ## My study week and ## Eight-week plan, from Read the curriculum, Plan deliberate practice and Manage tools and costs.
- ## Project briefs, ## Walkthrough and ## Job map, from Portfolio anatomy, Explain decisions and Prepare for applications.
If a section is missing, do the guided practice of that lesson again.
Make a new file in your ai-career folder with the name career-brief.md. Write the brief there, not in notes.md.
Two to three pages is enough. Short and specific is better than long and general.

Part 1: the target role

Uses The main job families, Technical and adjacent routes, One project, many roles and Choose a realistic route.

Name your primary role and your adjacent option.
Describe the work of the primary role: its normal day, its output, how it is judged, and its coding level.
Describe how the role works with others. In a project like Larkfield’s, what does it do, decide and ask?
Give your reason for the choice. Use the four questions from Choose a realistic route.

Part 2: what you bring

Uses Skills inventory, Your experience is a head start, Domain knowledge in practice and Evidence over self-ratings.

Copy your skills inventory with evidence: five areas, a level and evidence for each.
Add your domain card. It has one use case, at least three things the AI team needs to know, and a mistake story.
Add at least three “I know …, so I can …” lines.
Write your two most important gaps as specific skills, each with the evidence that shows the gap.

If you are a fresh graduate with little work experience, use your field of study, a job or a serious interest as your domain. Say honestly how deep your knowledge is.

Part 3: the study plan

Uses Read the curriculum, Plan deliberate practice and Manage tools and costs.

List the courses for your route in a working order, with their hours. Mark any course that you will skip, with the evidence for skipping it.
Copy your eight-week starter plan: real weekly hours, a lighter week, and one small deliverable.
Show one normal study week with the five activities. Include independent work, a later review and interview practice.
Write the tools and costs: what you use, what costs money, and how you keep the cost under control.
Write the dependency check: for each course in the plan, its required courses come earlier or are demonstrated.

Part 4: two portfolio projects

Uses Problem framing, From baseline to deployment, Portfolio anatomy and Explain decisions.

Copy your two project briefs. Each one has a problem, data that you may publish, an approach, a baseline, a success measure with a number, and expected limitations.
For each project, name the skills from Part 2 that it gives evidence for, including the gaps that it closes.
Add your two-minute walkthrough outline for project 1.
Draw or write your claim-to-evidence map: each skill that you will claim for the target role, and the evidence for it, now or planned.

Part 5: one job map

Uses Prepare for applications.

Add your map of one real job advertisement for the primary role. It shows each requirement, your evidence and its strength. Then write your decision, “apply now” or “apply after …”, with the reason.

Template

You can start from this outline:

# Career transition brief

## 1. Target role
Primary role:
Adjacent option:
The work (day, output, how judged, coding level):
How it works with others (does, decides, asks):
Why this role (four questions):

## 2. What I bring
Skills inventory with evidence:
Domain card:
I know …, so I can …:
Two main gaps, with evidence:

## 3. Study plan
Course order, with hours and skips:
Eight-week starter plan:
A normal study week:
Tools and costs:
Dependency check:

## 4. Portfolio projects
Project 1 brief:
Project 2 brief:
Skills that each project gives evidence for:
Walkthrough outline for project 1:
Claim-to-evidence map:

## 5. Job map

Check your work

There is no reviewer for this course yet. Review your brief with this table, or ask a colleague or mentor to use it. Mark each item as demonstrated, partially demonstrated or not yet demonstrated, with a reason. The course is complete when every item is demonstrated. You can improve an item and review it again as often as you need.

Required evidence	Demonstrated when
Role choice supported by responsibilities	The brief describes the role’s real work, its output and how it is judged, and how it shares work with other roles. The reason for the choice uses the learner’s own evidence and real advertisements, not only interest. An adjacent option shares most of its skills.
Skills gaps tied to evidence	Every level in the inventory has a specific piece of evidence. Domain experience appears with specific examples, not general sentences. Each gap is a specific skill, and evidence shows why it is a gap.
Feasible weekly learning schedule	Weekly hours are realistic and include a lighter week. Every course comes after its required courses, or the skip has evidence. The study week includes independent work, review on a later day and interview practice. Costs and data rules are stated.
Portfolio projects with measurable outcomes	Both projects have a baseline and a success measure with a number, data that may be published, and expected limitations. Each one gives evidence for a named skill of the target role. Every claim in the claim-to-evidence map has evidence or a plan.

A brief that sounds good is not enough. A course may come before its required courses, or a project may have no measurable outcome. Then that item is not yet demonstrated, even if everything else is strong.

Common mistake

A brief that hides the domain

Symptom: a professional has ten years in health care, but the brief reads like a new graduate’s. It has courses, a generic project and a target role “at any company”. Nothing in it uses health care.

Cause: the learner still believes that experience in another field does not count in AI.

Fix: go back to Part 2. Put the domain card and the “I know …, so I can …” lines at the centre. Then check: does the target role use this knowledge? Does at least one project use it? Usually, the strongest route is AI work in the field that you already know.

Recap

In this course, you went from “I want to work in AI” to a plan that you can follow and defend:

The work: an AI product has five parts. Six job families and several adjacent routes do the work, and they divide it into who does, who decides and who is asked.
Your starting point: five areas of skill, rated by evidence, not by feeling. Domain experience is a head start: AI teams need it in every phase, and domain experts can contribute to AI work, lead it or build it.
A real project: frame the problem first, ask if AI is needed, start from a baseline, evaluate the errors that matter, integrate with a person checking, and monitor.
Your plan: a prerequisite-safe course order, practice that builds skill, and tools without surprise costs.
Your evidence: portfolio projects with baselines and limitations, honest decision stories, and a map from job requirements to evidence.

Review your brief every month. Update the evidence as your projects finish, and move items from “gap” to “strong”.