← Back to Insights
January 20, 2026 · 6 min read
What belongs in a Praktikumsbericht from a software studio
A practical outline we give interns so the report is evidence, not a diary of standups.
German internships usually end with a report. We do not write it for the student. We do make sure the work produces artefacts that belong in one.
A useful report for an engineering internship is not a list of tickets. It is:
- Context & Motivation: Why this problem existed in the production system.
- Prior State: What invariants and architecture were already true in the codebase.
- Design & Implementation: What you changed, what you refused to change, and why.
- Verification & Evaluation: How you proved it worked (automated tests, error analysis, benchmarking, operator demo).
- Future Outlook: What you would prioritize in the subsequent engineering iteration.
We maintain pull requests, living architecture decision records (ADRs), and recorded demos. The formal Praktikumsbescheinigung we issue details project scope, duration, verified hours, and mentor evaluation.