Job Description: Apprentice Developer

An apprentice developer writes, tests, and maintains code under the guidance of senior staff, usually in languages like HTML, CSS, JavaScript, NodeJS, and C# (.net core). They focus on building foundational skills, fixing bugs, and collaborating on web or software applications within an Agile environment.

Key Responsibilities:

• Coding & Development: Assisting in coding, testing, and debugging applications, often focusing on UI components or back-end features.
• Maintenance & Support: Maintaining existing codebases and resolving minor bug fixes.
• Learning & Collaboration: Working alongside senior developers, attending team meetings, and participating in code reviews to learn best practices.
• Documentation: Documenting technical tasks and creating reports for senior team members.
• Troubleshooting: Analysing errors and supporting software performance improvements.

Typical Daily Tasks:

• Writing new code for small features.
• Fixing bugs reported by users or testers.
• Reviewing existing documentation.
• Pair programming or attending stand-up meetings.

Training

Apprenticeships include time away from working for specialist training. You’ll study to gain professional knowledge and skills.

Training Provider

WEST NOTTINGHAMSHIRE COLLEGE

Training Course

Software development technician (level 3)

Understanding apprenticeship levels (opens in new tab)

What You'll Learn

Course Contents

• Write simple code for discrete software components following an appropriate logical approach to agreed standards (whether web, mobile or desktop applications) under supervision.
• Apply appropriate secure development principles to specific software components at all stages of development.
• Support development of effective user interfaces.
• Make simple connections between code and defined data sources as specified.
• Test simple code and analyse results to correct errors found using unit testing under supervision.
• Conduct a range of test types under supervision, such as Functional and Non-Functional.
• Apply structured techniques to problem solving, including carry out simple debug of code.
• Follows organisational and industry good coding practices (including for naming, commenting etc.).
• Solve logical problems, seeking assistance when required (including appropriate mathematical application).
• Support the creation of simple software documentation and visuals to effectively communicate understanding of the program.
• Define functional and non-functional requirements such as use cases, storyboards, user stories, performance, and accessibility.
• Work within operational requirements such as health and safety, budgets, brands, and normal business protocols.
• Develop user interfaces as appropriate to the organisations development standards and the type of software development being developed.
• Build scripts in line with work instructions for deployment into the relevant environment.
• Follow simple software designs and functional/technical specifications in line with work.
• Follow simple testing frameworks and methodologies in line with work instructions.
• Follow company, team, or client approaches to continuous integration, version, and source control as instructed.
• Support the communication of software solutions and ideas to technical and non-technical stakeholders.
• Apply algorithms, logic, and data structures in a supported context in line with work instructions.
• Follow work instructions to contribute to building a given design whilst remaining compliant with security and maintainability requirements.
• Apply techniques to break down complex problems.
• Demonstrate how Key Performance Indicators (KPIs) can be used to frame and measure desired outcomes.
• Implement secure code in appropriate languages of different types which is maintainable, readable, functional.
• Design simple software solutions to meet a requirement using tools and techniques, such as waterfall and agile.
• Work in a shared code base with appropriate etiquette and tools, such as modularity and data definition.
• Use simple debugging techniques, such as interactive debugging, print debugging, remote debugging.
• Implement test plans under supervision to show that a test plan is implementable in practice and implementation conforms to the plan.
• Develop and use simple acceptance criteria.
• Apply and maintain procedures and security controls to ensure confidentiality, integrity, and availability.
• Use collaboration tools and technologies for source and version control to enable working together on common projects, regardless of physical location.
• Follow instructions to ensure client data is held securely under supervision e.g., not using personally identifiable information in test systems, making sure personal actions comply with ICO regulations.
• Use collaboration tools and technologies for writing technical documentation for, and adapting to, specific audience(s). e.g., technical, non-technical, internal, external.