Interviews for computing/IT jobs including a mock interview.


picture of computer

Try a mock interview for computing jobs, answering typical questions and also getting tips on how you should answer. There are also other questions students have been asked at computing interviews.


SYSTEMS ANALYSTS must be able to communicate with the user of their system, and be able to listen to them to find out their requirements. They must be able to investigate and solve problems. They need to be able to present their solutions to their clients and persuade them that their solution is the best one. They usually work in a team, so they need to be able to cooperate with programmers and other team members. Employers will be looking to see how you can talk about and demonstrate these skills at your interview. The sort of evidence you could offer includes:

Mock Computing Interview

Before you arrive ...

This interview will concentrate mainly on the IT specific interview questions you may be asked so it is similar to a technical interview. Computer aptitude tests are used by most large companies, so make sure you gain familiarity with these. First interviews for computing jobs may be with a personnel manager who may not know much about IT, and second interviews may be technical e.g. 'write an SQL query'. This is why is may be sensible to send your CV to the IT dept. as well as to Personnel. Also see our Computing Careers Page and Interview Reports

There follow some of the questions that might be specifically asked of students at interviews for computing jobs. General interview questions are not asked here, so you might also like to try the general and multiple choice interviews as well for standard interview questions that can be thrown at any candidate. Click on "First Question" to begin. Think carefully about how you would answer, then click on "Show Answer Tips" to get an idea of how you should be answering.


Applications for IT Jobs

See our applications and interviews section at
and the example computing CVs at



Very often you are hired as much for your problem solving skill as for your knowledge of a particular language. You can sometimes get by these questions by emphasising your ability to learn: once you know one or two programming languages you can be confident that, given a decent manual, access to a compiler, and a little time, you can learn a new language in a few weeks. e.g.


If you have been to an interview or assessment centre recently please fill in our interview report form to help other students.

Questions on course projects

Competency questions. See our page on How to Answer Competency-based Questions

Commercial Awareness Questions. See our page on How to answer Commercial Awareness Questions

Hypothetical questions. See our section on this

Technical questions

Make sure you know everything you have been taught - they try and predict what you have learned from module descriptions and quiz you on them.  For the HR interview just know your CV inside out.  The technical interviewers will keep asking you harder and harder questions so be prepared to say "I don't know" (they are trying to find the limits of your knowledge!) and don't be put off by their stares or comments to each other if it takes a while to answer a question.
(Morgan Stanley Interview)

Do research into software methodologies and software testing. Research Agile methodology in particular and mention it.
(Accenture Technology Solutions)

Questions you can ask at IT interviews.

Consultancies and software houses

IT Equipment manufacturer


Tests given to candidates. See our practice aptitude tests

Group exercises. See our page on assessment centre exercises

Presentations, See our page on these



FDM - IT Graduate Training Scheme

Good news ... I was offered a position so thanks for all of your support and guidance: it's really made the difference. There were 5 of us, on the first day we had a team exercise which was to debate cybernetics and robotics: for and against arguments, we then had our individual presentations.

On the second day there were no interviews and it was just coding for 7 hours. For 2 hours I had no code written and my lack of experience in Unix really showed. After the lunch break I really started to focus and just thought this is more of a quantity not quality situation, I felt if I show my effort it may help my cause. At the end of the day I had an interview with a manager, she was basically just asking why did I apply for the job, are your flexible, are your commited for 2 years.

The first final interview was a technical interview: I had to explain my code and what I was trying to do. I also showed how I planned the night before and also how I would have approached the task if I was more experienced. Then it was another slightly mor eintense interview with another HR manager, but I've always felt honesty is the best policy, so when I was asked what I know about the role I gave my answer but also said 'to be honest at this moment I have only a rough idea'. I felt that the interview went very well and I also feel I sold myself on the final day. When they told me I had the job they also said that they would be lining me up for an interview with Lloyds bank. (FDM)



Back to the mock interviews menu or Answers to 150 common interview questions