Graditute
Learning Experience

A steady weekly rhythm, reviewed by people who do the work.

Whichever partner company you intern with, the pattern is the same: a milestone opens, you build, you submit, your company mentor reviews. Repeat until the project is complete.

A typical weekMonTueWedThuFriSatSunMilestoneOpensBuild at your own pace · 8–10 hrsSubmitBufferSupportLast week's review returnedOffice hoursQ&A thread open all week
The student journey

What happens, and when.

Four phases, the same for every programme. Durations vary by track.

  1. Before you start

    Apply, get matched, prepare

    Your application is reviewed for intent and readiness, and you're matched with a partner company. You then confirm your seat and receive the brief, rubric, calendar and setup guide.

  2. Week 1

    Orientation

    Meet your mentor and cohort, walk through the brief together, and agree how you will work.

  3. Weeks 2 to final

    Milestones and reviews

    One milestone a week (or fortnight, on longer tracks). Each submission gets rubric scores and written feedback before the next one is due.

  4. At completion

    Final review and certificate

    Your complete project is reviewed against the completion criteria. If they are met, your certificate is issued and becomes publicly verifiable.

Guidance

Who helps you — and how.

M

Your mentor

A practitioner from the partner company. Reviews every milestone, runs office hours and answers questions in the thread.

Does: question, guide, score fairlyDoesn't: write your code or your report
C

Programme coordinator

From our team. Handles your match, schedules, extensions, payments and anything that isn't about the work itself.

Does: keep the programme runningReach: [coordinator email]
P

Your cohort

Students on the same track. Discuss approaches, share resources, and give each other feedback.

Rule: discuss ideas, never share solutions
1Milestone 3 of 5Due Sun, 11:59 pm2

Dashboard view

3
SubmitA deployed preview link and a pull request with a short write-up.
4
Scored on
Functionality · 30Code · 25UX · 25Docs · 20
5
Feedback windowReview returned by Tuesday. Resubmit once if the minimum score isn't met.
Anatomy of a milestone

Every milestone answers five questions.

  1. 1Where am I in the project?
  2. 2When is it due?
  3. 3What exactly do I submit?
  4. 4How will it be judged?
  5. 5When do I hear back?
Evaluation

You see the rubric before you write a line.

EXAMPLE RUBRIC EXCERPT
Developing1–4Proficient5–7Strong8–10
Functionality30%Core screens incomplete or break with real data.All required screens work with the mock API.Handles empty, loading and error cases gracefully.
Code quality25%Logic duplicated; hard to follow.Reusable components with clear names.Well-structured, documented and easy to extend.
UX & accessibility25%Layout breaks on mobile; low contrast.Responsive; keyboard reachable.Consistent, accessible, considerate of real users.
Certificate criteria

A certificate means the work was done — and reviewed.

We do not issue certificates for attendance or payment alone. That is what makes them worth verifying.

How verification works →
RequiredEvery milestone submittedNo gaps. Late is acceptable within the programme window.
RequiredMinimum score on eachSet per programme and published with the rubric.
RequiredFinal review passedThe complete project meets the brief as a whole.
RequiredOriginal workIn line with the academic integrity policy.

See it applied to a real programme.

Apply for internshipBrowse sample briefs