PD Onboarding

How we run a product designer intern’s first 180 days, day to day. This is the PD companion to PE Apprenticeship (the engineer version) and PM Onboarding; the hiring bar lives in Hiring & Internship and the ladder and attributes in Product Designer. It covers the milestones, the guardrails that make early autonomy safe, the 1:1 cadence, and the day-90 call. A per-person tracker to copy into a fresh doc is at the bottom.

A designer is accountable for whether the user gets the outcome, not whether the screen looks polished. The rhythm mirrors the engineer’s 7 / 30 / 60 / 90 shape, adapted to the design craft: the first “ship” is a small real design that reaches users, not a pixel-perfect mockup.

Two people run it. The onboarding buddy (a senior designer) owns the day to day: pairing on research and flows, reviewing every design, transferring how we design here. The manager owns growth and fit, using the Product Designer radar. The buddy is the first line for everything; the manager reads trajectory.

The milestones

What an intern can do unsupervised by each date, not a checklist to race through. The dates are targets; someone can arrive early or need longer, and that is what the day-90 call is for.

By	Milestone	What it means
Day 7	First design shipped	Has taken one small, real design change from problem to a spec engineers built: the states, the handoff, verified in the product. Small, but every step, none done for them.
Day 30	Works across the flow	Carries a small feature’s design across the whole flow: the real need, the states (empty, loading, error, edge), the visual craft, the handoff, using the design system rather than forking it.
Day 60	Owns a small flow	Takes a scoped flow to done without being walked through it: researches the need, designs the states, prototypes, and hands off cleanly, deriving the intent from the definition.
Day 90	Decision checkpoint	Enough signal for an honest call: on track for junior, extend the runway, or stop. Never a surprise.
Day 180	Clears the junior bar	Owns a small flow end to end, states, spec, and handoff, and unblocks themselves. Ready for the next half of the apprenticeship. Or a re-based plan if they need longer.

Week one: get to the first design

The first week is built backwards from day 7. Front-load context so the week ends on a real design in the product, not a moodboard.

Day 1. Accounts, the design tool and the design system, calendars. Meet the buddy, set the standing daily time, walk the guardrails below. Start Core and How Systeric Works.
Days 2 to 3. Shadow the buddy: sit in on a Discover conversation and a Define session, walk the design system and a few current flows. Pick one small, real design change worth owning.
Days 4 to 5. Design it, states and handoff included, review with the buddy, and hand it to build. Verify it in the product. First design done.

By the end of week one they have touched the flow once, from a real need to a shipped design. Weeks two to four widen it: a full feature’s design, less pairing.

The day-one welcome messages are role-agnostic; they are in PE Apprenticeship.

Guardrails

These hold for the whole apprenticeship. They are what make it safe to give someone real design influence early. Walk them on day one.

Start from the problem, not the screen. No visual polish before the real need and the flow are clear. A pretty screen that solves the wrong problem is a reject.
Design the whole flow, not the happy path. Empty, loading, error, and edge states are part of the design, not an afterthought.
Use the design system; do not fork it. Reuse components. Extend the system deliberately, and only when it is genuinely missing something.
Hand off cleanly. A design engineers can build without guessing: every state, the spec, and the why.
Escalate early. A slipping design or a doubt surfaces the same day. Silence is the failure mode.

The 1:1 cadence

Two 1:1s, two jobs. Same shape as the engineer program.

Buddy 1:1 (daily, then tapering). A senior designer, the first line. Daily for the first weeks to transfer how we frame problems and design here, then a few times a week as they find their feet. Unblocking, pairing on live work, reviewing every design before it goes out.
Manager 1:1 (weekly, then biweekly). Weekly for the first month, then biweekly. Growth and fit, run against the Product Designer radar: feed the spike, clear the one thinnest spoke holding them below junior. Delegate one rung ahead, then close the gap with review. No surprises: the day-90 call is discussed continuously, never sprung.

The 90-day checkpoint ([date])

Enough signal for an honest call. On track for junior, extend the runway, or stop. Written against the radar, with one concrete moment per attribute, never a surprise.

On track: owning small designs with guidance, the craft spokes (user insight, interaction and UX, visual craft) visibly moving.
Extend: the trajectory is right but the reps need longer; re-base the plan and say so.
Stop: a non-negotiable is failing, or the craft is not moving despite the reps. Kind, clear, early.

Per-person tracker

Copy this into a fresh doc for each intern. Keep it live; it is the spine of the manager 1:1.

[Name] · started [date] · buddy [name] · manager [name]

Milestones

Day 7: first design shipped (problem to a spec engineers built, states and handoff, verified live)
Day 30: works across the flow (need, states, visual craft, handoff, on the design system)
Day 60: owns a small flow (research to handoff, unsupervised)
Day 90: decision checkpoint
Day 180: clears the junior bar

Shape (the seven PD attributes)

Product sense · User insight · Interaction & UX · Visual craft · Prototyping & delivery · Communication · Leadership. Note the spike to feed and the one blocker to clear.

Buddy 1:1 log

[date]: [what they worked on, what to reinforce]

Manager 1:1 log

[date]: [trajectory, the spike, the blocker, the next rep]

90-day decision ([date])

[On track / extend / stop, with the concrete evidence]