Three months of guided practice—when a cohort is active.
An intended learning journey from foundations to a reviewed contribution and an honest portfolio reflection. This page does not announce an open cohort.
Structure is not availability.
The timeline below describes how a three-month cohort is intended to work. Application dates, capacity, selection, schedule, location, compensation if any, certificates, and potential future opportunities must be confirmed for each cohort. Participation does not guarantee employment, placement, or paid work.
Foundations. Contribution. Ownership.
Each month ends with visible evidence of learning rather than a vague attendance milestone.
- Month 1
Foundations and team practice
Build a shared understanding of product delivery, code quality, collaboration, and the tools used in the learning project.
- Environment setup, version control, and issue workflow
- Small exercises in the participant's selected discipline
- Reading existing requirements and asking precise questions
- Pairing, feedback, and introductory review practice
Month milestoneComplete a small reviewed feature or design task and explain the decisions, trade-offs, and follow-up work.
- Month 2
Guided product contribution
Contribute to a bounded project workflow while practicing estimation, implementation, testing, communication, and iteration.
- Break a requirement into reviewable tasks
- Implement or design a complete journey, including edge states
- Participate in critique, code review, or quality review
- Document progress, blockers, and assumptions clearly
Month milestoneDeliver a working project increment that meets agreed acceptance criteria and has been improved through feedback.
- Month 3
Ownership and portfolio reflection
Take greater ownership of a contained outcome, prepare it for handover, and turn the learning into evidence of professional practice.
- Plan and lead a small final project increment
- Address quality, accessibility, documentation, or operational gaps
- Present the outcome and respond to structured review
- Prepare a truthful portfolio narrative and personal learning plan
Month milestonePresent the completed contribution, supporting evidence, known limitations, and the next skills to develop.
Ask for confirmed terms before committing.
When an application window exists, the cohort notice should state the discipline, schedule, working arrangement, selection process, capacity, and any compensation or fee. Until those details are published or confirmed directly, this page is informational only.
- Share your current learning level honestly
- Link only to work you can explain and discuss
- Confirm the time and equipment expectations
- Ask how feedback and supervision will work
An enquiry starts a conversation. It is not an application acceptance or a reservation.
Ask what is confirmed before planning around the opportunity.
We will share current availability and terms if a cohort is planned. If nothing is open, your enquiry remains only an expression of interest.