Confirm the route before you plan.
Planned portfolio only. Avenor’s approved scope, applicable standard version, assessor capacity, fees and service dates must be confirmed before booking. The standard’s Skills England approval is not approval of Avenor.
Checked 19 October 2026: version 1.1 is approved for delivery. Version 1.0 is retired and must not be described as the current new-start standard. Assessment details remain dependent on the version registered for the apprentice.
View the official standard and assessment plan ↗What this occupation demonstrates
For apprentices contributing to software development under clear direction and supervision. This route focuses on building and testing discrete components within a wider solution. Providers should help apprentices explain the requirement they were given, how they implemented it and how they recognised when advice or escalation was needed. Preparation should build confidence without overstating responsibility. A small, clearly explained contribution can be more informative than a large project where the apprentice cannot distinguish their own work from that of the rest of the team.
Providers supporting junior developers, application support colleagues and entry-level software team members.
- Follow a defined requirement and explain the resulting component.
- Use basic testing and debugging to check expected behaviour.
- Work responsibly in a shared codebase and seek advice at appropriate points.
Prepare for a fair assessment
Use the applicable plan as your starting point. The following are preparation prompts, rather than additional gateway requirements or a substitute for the assessment specification.
- Choose examples small enough for the apprentice to explain completely. Keep the task brief, personal contribution, tests, feedback and final change linked in a clear sequence.
- Practise recognising the limits of responsibility. Ask the apprentice to explain a situation where they sought help and what they learned from the response.
- Agree a safe approach to code examples with the employer. Remove access keys, client information and other sensitive material, and avoid uploading a private repository to a public service.
Plan a useful handover.
Procure this Level 3 route around bounded contribution, supervision and dependable development habits. Share the kinds of discrete components apprentices build, the level of direction they receive and employer restrictions on repositories. Ask how the organisation distinguishes this route from Software Developer Level 4 and how it recognises appropriate help-seeking rather than rewarding overstated autonomy. The provider owns correct route selection and preparation; employer supervisors verify contribution; an evidence owner agrees safe extracts before submission.
A realistic evidence conversation
Illustrative, not a prescribed requirement: an apprentice implements a small validation component from an agreed task brief. The record contains acceptance criteria, a short design note, their code contribution or safe equivalent, tests, one defect correction, review feedback and the point at which they sought advice. A supervisor confirms boundaries and no private repository is exported. Use the scenario to ask how a prospective organisation would verify the apprentice's work, handle restricted source and judge responsible escalation without turning a modest task into an inflated ownership claim.
Handover checks
- Curriculum owner confirms Level 3 scope and avoids importing Level 4 expectations.
- Employer supervisor identifies bounded tasks and records the apprentice's own contribution and support.
- Evidence owner approves safe code extracts, test data and repository-history alternatives.
Questions to ask before buying
- How do you distinguish competent supervised contribution from Software Developer Level 4 autonomy?
- What alternatives support employers that prohibit source-code or repository export?
- How is personal contribution verified when tasks involve pairing, review and shared components?
Think it through.
Explain your decisions.
These are original learning prompts. They are not live assessment questions, an official mock paper or a prediction of your result.
1. A task description is ambiguous. What would you clarify before starting to code?
Explore a response structure
Identify the expected user behaviour, inputs, outputs and acceptance checks. Explain how you would ask a supervisor a focused question rather than guess. Record the agreed interpretation so the implementation and testing work toward the same outcome.
2. Your component works for a normal input but fails when the input is empty. How would you respond?
Explore a response structure
Describe how you would reproduce the problem, inspect the relevant code and clarify the intended behaviour. Propose a targeted fix and suitable tests. Explain when a wider design or validation question should be escalated.
3. How would you safely contribute a change to a shared codebase?
Explore a response structure
Discuss the team’s branch, review and testing process, keeping the change focused and communicating its purpose. Explain how you would respond to review feedback and avoid including unrelated files, secrets or personal data in the change.
Questions about this standard
How does this differ from Software Developer Level 4?
This standard is intended for a supportive, entry-level contribution under supervision. The appropriate choice depends on the job’s duties and expected responsibility, rather than which programming language the employer uses.
Which assessment methods apply?
Use the published assessment plan for the apprentice’s registered version and option. Methods, timings, gateway documents and grading rules can differ between versions. These original practice prompts are learning resources, not live assessment questions or a prediction of an assessment outcome.
Can we book with Avenor?
This standard is in Avenor’s planned portfolio. Ask us to confirm our approved scope, the applicable version, assessor capacity, fees and dates before making a booking. Publication of this guide does not establish Avenor approval.
Sources and review
Guide updated 20 October 2026; official source reviewed 20 October 2026. Standard titles, versions and requirements can change. Always check the linked official record for the apprentice’s start date.
Skills England: Software Development Technician ↗190 starts in 2023/24, published in the ICT-related apprenticeship data. Historic starts inform our portfolio; they do not establish today’s demand or our availability.