About the role
Practise connecting a user action to application behaviour in a development environment. You might add a simple form, inspect the request it sends and see how validation changes the response, with each step reviewed.
What you will practise
- Trace a small feature from its screen through the server handler to the data it reads or writes.
- Keep setup instructions and questions alongside your draft so a reviewer can run the same example.
What you will learn
- Learn how a requirement becomes an interface, an API change, a test, and a reviewable piece of work.
- Document your work, respond to feedback, and explain what is ready for review and what still needs help.
What you should bring
- Basic programming, HTML and CSS, and familiarity with at least one small application or school project.
- Willingness to ask questions, keep clear notes, and revise work after feedback. Professional experience is not required.
Examples of work in this role
- A runnable practice feature with a short explanation of its input, output and validation.
- Notes showing a bug you reproduced and the changes made after review.
Working arrangements
- Keep progress, questions, and blockers visible through the agreed communication channels.
- Availability, working hours, equipment needs, and any location eligibility requirements will be discussed during recruitment.
- Training tasks require review. Supervision, school requirements, training hours, start date, and any allowance must be agreed before the placement begins.
- Live systems, publishing, and client commitments require authorisation. Begin with practice environments or reviewed drafts appropriate to the task.
What to include in your application
- Use the application form and include your CV, availability, and a short explanation of why this work interests you.
- Include a school or personal project where possible. If this is a school OJT placement, state your course, required hours, intended dates, and any school documentation requirements.
- Include a school or personal application and identify one screen or function you built. A small unfinished example is useful if you explain what works and where you need guidance.
- Share only work you have permission to disclose. A redacted sample or a clear explanation is fine when client work is confidential.