Internships built around a real piece of work.
Our internships are project-based: a defined problem, senior guidance, and an output that can be reviewed and explained — not a semester of observation.
Discover
Architect
Build
Operate
Delivery standard
Clear ownership. Working software. Production evidence.
A short engagement with a clear output.
A useful internship gives the participant a real problem and the support to make progress on it. The scope is small enough to finish and substantial enough to learn from.
Interns work with the same review and documentation expectations as the rest of the team, adapted to the length of the engagement.
At a glance
- Defined project scope
- Senior engineer mentorship
- Review and feedback
- Portfolio-ready evidence
How the internship is structured.
Every internship has a scope, an owner, a review rhythm, and a final output.
Defined scope
A bounded problem with a clear output, constraints, and success criteria.
Senior mentorship
Regular working sessions with an engineer who reviews the work and explains decisions.
Engineering practice
Version control, testing, documentation, security, and review as part of the work.
AI in context
Where relevant, exposure to retrieval, evaluation, and AI application engineering.
Review and feedback
Structured feedback at agreed points, not only at the end of the engagement.
Final output
A demonstrable result, a short write-up, and a discussion of what was learned.
A structured path from intent to evidence.
Every programme starts with a clear question, produces something testable, and ends with an honest decision about what comes next.
- 01 · Frame
Define the learning or operating question
Agree the participants, problem, constraints, and what useful evidence would look like.
- 02 · Build
Make the idea tangible
Produce a working prototype, curriculum module, or product slice with senior engineering involvement.
- 03 · Validate
Test it with real users or data
Evaluate usefulness, quality, risk, and adoption in a context close to the real environment.
- 04 · Advance
Decide what to do next
Continue, incubate, publish, or stop with the evidence and ownership recorded.
A finished piece of work and a clearer direction.
The aim is meaningful practice, honest feedback, and evidence the participant can discuss.
A completed output
A scoped project that is documented, reviewed, and demonstrated at the end.
Honest feedback
Clear input on strengths, gaps, and the next capability to develop.
Portfolio evidence
A piece of work the participant can explain and reference in future applications.
What an internship can cover.
Projects are selected to match the team’s current work and the participant’s level.
Areas
- Web engineering
- APIs
- Data
- AI evaluation
- Automation
- Content systems
Format
- Defined project
- Mentoring
- Code review
- Documentation
- Demo
- Feedback
Terms
- Duration
- Location
- Stipend
- Eligibility
- Application
- Selection
Practical answers before the first call.
If your question is not here, bring it to the conversation.
How do I apply?
Are internships paid?
What should I show in an application?
What do you want to learn, test, or build?
Whether you are a team, an institution, or an early-career engineer, start with the outcome you want and we will map a sensible path.

