Interview Sarthi

Home › Guides › Infosys interview questions for freshers

Infosys interview questions for freshers: practice guide

Practise your project explanation, programming fundamentals and HR answers together. Infosys has different hiring routes, so prepare from your own role and invitation instead of assuming every candidate gets the same rounds.

Updated 15 September 2026 · 8 min read · Published by Interview Sarthi

Check the official hiring process first

Infosys’s HackWithInfy page describes a coding competition with possible pre-placement interview opportunities. It is one route into Infosys; it does not establish a fixed interview format for every graduate role. Infosys HackWithInfy.

Your preparation checklist

Prepare for	What to do
Your hiring route	Read the role, test instructions and interview invitation. Campus hiring and competition-based hiring can differ.
Technical discussion	Practise explaining your project decisions, OOP, SQL and the programming skills in the job description.
HR discussion	Prepare an introduction, a specific reason for applying and honest answers about availability and location.

Role names, pay and training

Use the role and compensation in the current vacancy and your own offer. We have not verified one current salary table or a single interview duration that applies across Infosys graduate hiring.

Infosys describes its Foundation Program at the Global Education Center in Mysuru. Ask your recruiter which training arrangements apply to your offer.

Technical questions to practise

• Your project, then one level deeper. Same opening as everywhere. But A useful follow-up is “what would you change if you rebuilt it today?” Prepare a real answer; it separates candidates who built the project from those who watched it get built.
• OOP, thoroughly. The four pillars with examples from your own project, not textbook definitions. Abstraction vs encapsulation trips more freshers than any coding question.
• SQL and DBMS. Joins, normalisation up to 3NF in plain words, primary vs unique key. If your resume says a database, expect a query written live.
• A short program, watched live: palindrome, Fibonacci, count vowels, reverse a string without built-ins. They're watching your thinking-out-loud, not your syntax memory.
• Software engineering vocabulary: SDLC stages, what Agile means in one sentence, what testing you did on your project. Services interviews love process questions because delivery is process.

HR answers to practise for Infosys

• Why this role? Choose one specific responsibility from the current posting and connect it to something you have done or want to learn.
• When can you join, and can you relocate? Give your actual availability and constraints. Correct any old information in your application.
• What are the offer terms? Read the current pay, training, location and any agreement before accepting. Ask questions if anything is unclear.

Use our HR practice questions and answer examples to rehearse these conversations.

Mistakes to avoid during practice

• Textbook OOP answers with no example. The follow-up “show me that in your project” is where memorised definitions die.
• Contradicting the application form on relocation, gaps or backlogs, the classic avoidable rejection everywhere in mass hiring.
• Treating the HR minutes casually because the technical minutes went well. Prepare both technical and HR answers.
• Panic freezes. Ask for ten seconds, structure, answer. The pause habit is trainable: how to stop blanking out.

Use the language requested in your invitation. If you want to switch languages, ask the interviewer first. Our Hinglish answer examples can help you practise when that language is permitted.