SIWES software development placement interview practice
Programming fundamentals, debugging habits, version control and readiness to learn during a SIWES software placement. Practise the 5 questions the real interviewer asks with follow-ups. Paid plans add scored feedback on every answer.
Free with an Intaviu account: 320 credits a month, at 10 credits a minute of practice. Private: interview creators never see them.
- 15 minutes
- 5 questions
- Scored feedback on paid plans
About this interview
This interview is for a student seeking a SIWES placement with a software team. The interviewer is looking for sound foundations, honest ownership of project work, careful debugging and the ability to learn under supervision.
How to prepare
- Review one or two projects until you can explain the problem, your contribution and a difficult bug.
- Practise describing how you would test a small feature and isolate an error.
- Refresh basic Git actions such as creating a branch, committing a focused change and resolving a simple conflict.
- Prepare an example of learning a new tool or concept with limited guidance.
Common mistakes
- Claiming full ownership of a group project without separating your contribution.
- Listing many languages but being unable to explain a basic decision in any of them.
- Guessing silently when a task is unclear instead of asking a focused question.
What to expect
A real mock interview
5 questions the way the real interviewer asks, with follow-ups when an answer needs more.
Spoken, like the real thing
Speak your answers in your browser or the free desktop app, with live captions. You can ask the interviewer to repeat anything.
Scored on 4 areas
The things this interview weighs most. With a paid plan, your report shows how you did on each one.
A private report
On Plus, Pro and Premium: every answer scored, your strongest lines quoted and what to say differently next time. Interview creators never see it.
More job interview practice practice
Graduate Software Developer
Programming fundamentals, problem solving, version control, teamwork and learning in a first software role.
Job interview practiceBackend developer technical screen
A technical screen on API design, data access, debugging, testing and practical backend trade-offs under realistic load.
Competitions and awardsUniversity coding hackathon final
A student team final covering the working build, code decisions, testing, debugging, individual contributions and next technical steps.