Skip to content

Role interview guide

Campus placement (freshers) interview questions and what to expect

Campus placement processes, especially in India, commonly run in stages: an online aptitude test, often with coding or subject questions, a technical interview on your subjects and projects, and an HR round, with a group discussion at some companies. Freshers are usually judged on fundamentals, how clearly they explain their own project, and attitude and communication rather than experience.

What candidates commonly report; it varies by employer, level and country. Last reviewed 18 October 2026.

The usual stages

  1. 1Pre-placement talk by the company (often)
  2. 2Online test: aptitude (quantitative, logical, verbal), often with coding or subject questions for technical roles
  3. 3Group discussion for some companies and roles
  4. 4Technical interview on core subjects, your final-year project and internships
  5. 5HR round on your background, motivation, relocation and willingness to learn
  6. 6Some companies combine the technical and HR rounds into one interview

What interviewers check

  • Strong basics in your main subjects, not advanced trivia
  • Owning your project: what you built, why, and what you'd change
  • Clear, structured communication
  • Willingness to learn, relocate or work on what the company needs (for many roles)
  • Honesty: 'I don't know, but here's how I'd work it out'
  • Teamwork and attitude, shown through college activities

Behavioral questions

  1. Tell me about a team project at college. What was your part, and what went wrong?

    A good answer covers

    • The project and the team in a sentence or two
    • Your own part, separated from the team's
    • One problem, how it was solved and what you learned
  2. Tell me about a time you taught yourself something difficult.

    A good answer covers

    • What you learned and why
    • How you went about it: resources, practice, asking for help
    • Something you built or achieved with it
  3. Describe a responsibility you took on outside your coursework, such as a club, a fest or an internship.

    A good answer covers

    • The role and what was expected of you
    • One challenge and how you handled it
    • The result, with a number if you have one
  4. Tell me about a failure or a poor result at college and what you did next.

    A good answer covers

    • What happened, owned honestly
    • What you think caused it
    • What you changed and how things went after

Questions about the job

  1. Walk me through your final-year project: the problem, your part and what you'd do differently.

    A good answer covers

    • The problem and why it mattered, in two sentences
    • Your own part, the tools used and one hard decision
    • The results, the limits and what you'd change with more time
  2. Pick the subject from your degree you're strongest in and explain one idea from it as if to a first-year student.

    A good answer covers

    • A clear, simple explanation without jargon
    • An everyday example
    • Where it's used in industry
  3. Tell me about an internship or training you did. What did you do there yourself?

    A good answer covers

    • Where it was and what the team did
    • Your own tasks and one thing you delivered
    • What you learned about working in a company
  4. Explain the difference between a stack and a queue, and give an everyday example of each.

    A good answer covers

    • Stack: last in, first out; queue: first in, first out
    • Examples such as a pile of plates and a ticket line
    • Where each is used in software, such as undo or task scheduling
  5. What happens, step by step, when you type a website address into a browser? Keep it simple.

    A good answer covers

    • Finding the server's address through DNS
    • Connecting, securely if it's HTTPS, and sending a request
    • The server's response and the browser showing the page
  6. What's the difference between a primary key and a foreign key? Use a college database as your example.

    A good answer covers

    • A primary key uniquely identifies each row, such as a student ID
    • A foreign key links to another table's primary key, such as a student ID in a marks table
    • Why that link keeps data consistent
  7. Which programming language are you most comfortable with, and what have you built in it?

    A good answer covers

    • One language, named honestly
    • Something you built and a problem you solved in it
    • What you're learning next
  8. Estimate how many students in your college bring a laptop to class each day. Talk me through your reasoning.

    A good answer covers

    • Starting from total students and splitting by year or branch
    • Clear, rounded assumptions said out loud
    • A quick sense-check of the final number
  9. Group discussion: 'Should coding be taught in all schools?' Give your opening point and say how you'd bring others in.

    A good answer covers

    • A clear stand with one reason and an example
    • Building on or politely countering what others say
    • Summarising the discussion if you get the chance

Motivation and fit

  1. Tell me about yourself.

    A good answer covers

    • Your education and branch in a line or two
    • One or two things you've built, led or achieved
    • Why this company and role fit what you want next
  2. Why should we hire you over other freshers?

    A good answer covers

    • Two or three strengths, each backed by an example
    • How they match what the role needs
    • Willingness to learn, said with a sign you mean it
  3. Are you willing to relocate, work in shifts or work on a different technology from the one you studied?

    A good answer covers

    • An honest answer, with any real limits stated clearly
    • Openness to learning, with an example of picking up something new
    • What you'd want to grow into over time
  4. Where do you see yourself in five years?

    A good answer covers

    • Growing skills and responsibility in this kind of role
    • A direction you're interested in, without sounding like you'll leave soon
    • What you're doing now to get there
  5. Do you have any questions for us?

    A good answer covers

    • One or two thoughtful questions, such as training, the first project or team
    • Nothing you could have found on the company's website
    • A short thank-you

Tips

  • Revise your branch's core subjects (for computer science: data structures, OOP, DBMS, operating systems and networks) and know one programming language well.
  • Know every line of your CV; interviewers commonly pick a project or skill from it and go deep.
  • Practise aptitude regularly under time limits; speed comes from practice, not tricks.
  • In a group discussion, speak early, make one clear point with an example and let others speak; talking over people rarely helps.
  • Research each company before its pre-placement talk: what it does, its main clients or products, and the role on offer.
  • If you don't know an answer, say so and explain how you'd work it out; a confident guess usually does more harm.
  • Outside India, graduate schemes often use online tests, video interviews and assessment centres instead; the same basics and stories still apply.

Practise it out loud

A mock interview asks what campus placement (freshers) interviews usually test, follows up on your answers and gives you a report. The warm-up is free, needs no account and checks five of these questions as you answer.

About this guide

Written by Orbit from what candidates and interviewers commonly describe for this kind of job. The questions are Orbit's own practice questions, not questions taken from any employer's interviews. Processes change, so check the job post and what your recruiter tells you.