📋 What This Article Covers
- The actual technical questions Infosys asks freshers with what each one tests
- The HR questions Infosys uses and how to answer without sounding scripted
- What Infosys interviewers are really evaluating — not just what they are asking
- The mistakes that end Infosys interviews before they should
- A 7-day preparation plan to cover both rounds
Clearing the Infosys online assessment gets you to the interview. What happens in that room is a completely different test. The technical round is not just about what you know — it is about whether you actually built what you claim and whether you can explain your thinking under pressure.
This article covers both interview rounds with the real questions, what each question is actually evaluating, and how to answer in a way that sounds like a person who genuinely understands their work — not someone who spent three nights memorizing definitions.
🔍 What Infosys Interviewers Are Actually Looking For
Infosys interviewers are not looking for perfect candidates. They are looking for candidates who understand the logic behind what they have built, can explain their thinking clearly under mild pressure, and are honest when they do not know something. A candidate who says “I am not sure of the exact answer but here is how I would think through it” consistently scores higher than one who guesses incorrectly and defends the wrong answer.
Your final year project is not a formality. Interviewers spend significant time here — often 15 to 20 minutes of a 45-minute technical round. They are checking whether you built what your resume says you built. Know every technical decision you made and why.
Technical Interview Questions — What Is Actually Asked
The technical round starts with your resume and project, then moves into core CS fundamentals. Every answer you give opens a follow-up question — interviewers follow the thread of what you say.
“Explain the latest project you have worked on.”
Answer using this structure: the problem you solved, the tech stack you chose and why, your specific contribution (not the team’s), one significant challenge you faced, and what you would improve now. Never claim team work as your own contribution — interviewers follow up with specific implementation questions that expose this immediately. If your project used a database, be ready to show the schema. If it used an API, be ready to explain how it works.
“Explain the four pillars of OOP with real-world examples.”
Encapsulation: a capsule holds medicine without exposing its contents — in code, a class wraps data and methods together and controls access through public and private modifiers. Inheritance: a savings account inherits basic account properties but adds interest-specific behaviour. Polymorphism: the same brake function works differently in a car versus a bicycle — one method, multiple implementations. Abstraction: a TV remote lets you change channels without knowing the internal circuit — in code, an interface exposes what a class does without showing how. Use your own project as an example wherever possible. That connection earns extra credit.
“What is the difference between DROP and TRUNCATE commands?”
DROP removes the entire table structure along with all its data from the database permanently — the table no longer exists after a DROP. TRUNCATE removes all the data inside the table but keeps the table structure intact for future use. TRUNCATE is faster than DELETE for clearing all rows because it does not log individual row deletions. You cannot roll back a DROP without a backup. TRUNCATE can be rolled back in some database systems depending on the transaction model.
“What is the difference between a process and a thread?”
A process is an independent program in execution with its own memory space, resources, and state. A thread is a subset of a process — it is a unit of execution within a process. Multiple threads within the same process share the same memory space, which makes communication between threads faster than between processes. Because threads share memory, they are more efficient but require careful synchronisation to avoid race conditions. Creating a new thread is faster and uses fewer resources than creating a new process.
“Explain the difference between a stack and a queue with use cases.”
A stack follows Last In First Out (LIFO) — the last element added is the first removed. Used in function call stacks, undo operations in text editors, and browser back navigation. A queue follows First In First Out (FIFO) — the first element added is the first removed. Used in print queues, CPU scheduling, and message processing systems. If you used either in your project, mention it specifically. That connection demonstrates applied understanding, not just memorisation.
“Reverse a string without using built-in functions.”
Talk through your approach before writing. Use two pointers — one starting at the beginning, one at the end, swap characters and move inward until they meet. This is O(n) time and O(1) space. Mention edge cases: empty string, single character, even versus odd length. Write it cleanly with variable names that explain the logic. If you make a mistake, correct it calmly — do not freeze or apologise excessively. Interviewers notice composure under pressure.
💡 Technical Round — Priority Preparation Order
| Topic | Priority | What to Cover |
|---|---|---|
| Final Year Project | 🔴 Critical | Architecture, your role, tech stack decisions, one challenge, what you would improve |
| OOP Concepts | 🔴 Critical | All four pillars with real examples, overloading vs overriding, abstract class vs interface |
| DBMS and SQL | 🔴 Critical | Normalization, keys, ACID, DROP vs TRUNCATE vs DELETE, second highest salary query |
| Data Structures | 🟠 High | Stack, queue, linked list, array vs linked list, binary search |
| Basic Coding | 🟠 High | String reversal, palindrome, prime check, array duplicates, second largest |
| Operating Systems | 🟡 Medium | Process vs thread, deadlock, context switching, memory management |
| Computer Networks | 🟡 Medium | OSI model basics, TCP vs UDP, HTTP vs HTTPS, what happens when you type a URL |
HR Interview Questions — What Is Actually Asked
The HR round at Infosys is not a formality. It is the final filter for cultural fit, communication clarity, and practical flexibility. Disqualifications are rare but happen when communication is genuinely poor or when policy questions — relocation, shift flexibility — are refused outright.
“Tell me about yourself.”
Use the Present, Past, Future structure. Present: your degree, your strongest skill or area. Past: one specific academic achievement or project you are proud of. Future: why Infosys and what you want to learn here. Keep it under 90 seconds. Do not recite your resume — the interviewer has it in front of them. Do not start with your hometown or family details — start with your professional identity. Practice this until it sounds natural, not memorised.
“Why do you want to join Infosys?”
Mention something specific: the structured Foundation Training Programme at Mysuru, Infosys’s focus on emerging technologies through the DSE and SP tracks, or a specific Infosys initiative you read about. Connect it to your own goal — not what Infosys can give you, but what you want to contribute and build there. A candidate who says “I want to work on cloud infrastructure and I read that Infosys has been expanding its AWS practice significantly” is more memorable than one who says “Infosys is a global leader in IT services.”
“Where do you see yourself in 5 years?”
Be honest about being at the start of your career. A strong answer: in the first two years, master the foundation training and deliver well on my first project. Within five years, develop enough technical depth to take on a module lead or senior developer role. Avoid saying you want to be a manager in two years — it signals unrealistic expectations. Avoid saying you want to start your own company in five years — it signals you see Infosys as temporary. Frame your growth within Infosys, not away from it.
“Are you willing to relocate or work in rotational shifts?”
Answer directly and positively: “Yes, I am completely comfortable with relocation and rotational shifts. I understand that working with global clients means adapting to different time zones and I see this as an opportunity to gain broader exposure.” If you have a genuine constraint, state it calmly with a specific reason and openness to discussion — do not present it as a refusal. The Mysuru training relocation specifically is a condition of joining and should be accepted without qualification.
“What is your biggest weakness?”
Choose a real weakness that is not critical to the SE role. State it honestly, then explain what you are actively doing to address it. Example: “I sometimes get absorbed in technical problems and lose track of time. I have started using time-boxing — setting a fixed time limit before asking for help or moving on — which has made my problem-solving more efficient.” The structure is: honest weakness, specific improvement action, measurable result. The weakness itself matters less than the self-awareness and the action you took.
⚠️ Mistakes That End Infosys Interviews Early
- Not knowing your own project. If you cannot explain your final year project architecture, tech decisions, and your specific role in clear terms, the technical round ends quickly. This is the most consistent rejection point across all Infosys interview accounts.
- Claiming skills you cannot demonstrate. If Java is on your resume, expect to write Java code. If SQL is listed, expect to write a JOIN query on screen. Every skill is a potential question.
- Generic answers to company-specific questions. “Why Infosys?” answered with “it is a global leader” is the most common HR mistake. Interviewers hear this hundreds of times in a single hiring drive. Specific answers win.
- Refusing relocation or shift flexibility. Both are operational requirements at Infosys. Any answer that sounds like a refusal rather than an acceptance with conditions ends the HR round.
- Memorised answers that sound rehearsed. Infosys interviewers ask follow-up questions specifically to break through prepared answers. An answer anchored in your own experience and project work holds up under follow-up. A memorised definition does not.
- Not having questions for the interviewer. “Do you have any questions for us?” is always asked at the end of both rounds. Saying no signals disinterest. Prepare two genuine questions — about the onboarding process, the type of projects freshers typically join, or how performance is evaluated in the first year.
7-Day Preparation Plan
✅ If Your Interview Is Within a Week
- Day 1 — Project preparation. Write out your project explanation covering problem, tech stack, your role, one challenge, and what you would change. Practice saying it out loud until it takes 90 seconds and sounds natural. Anticipate follow-up questions on every technical decision.
- Day 2 — OOP and DBMS. All four OOP pillars with real examples from your project. ACID properties, normalization, DROP vs TRUNCATE vs DELETE, primary vs foreign key. Write the second highest salary SQL query without looking it up.
- Day 3 — Data structures and coding. Stack, queue, linked list — definitions and when to use each. Practice: string reversal, palindrome check, prime number, array duplicates, second largest element. Talk through your approach before writing each solution.
- Day 4 — OS and computer networks. Process vs thread, deadlock, context switching. OSI model basics, TCP vs UDP, HTTP vs HTTPS, what happens when you type a URL in a browser.
- Day 5 — HR preparation. Write and practice your self-introduction using Present, Past, Future structure. Research one specific Infosys initiative or programme to mention in “Why Infosys.” Prepare your weakness answer with the honest weakness plus improvement action structure.
- Day 6 — Full mock interview. Ask a friend or classmate to interview you across both technical and HR rounds. Record it. Review your composure, the clarity of your project explanation, and whether your HR answers sound like a person or a script.
- Day 7 — Final review and logistics. Revise only weak areas identified from Day 6. Prepare your documents — resume copies, ID, mark sheets. Confirm interview location and report time. Rest well.
📊 Tracking Multiple Company Interviews Alongside Infosys?
Most freshers apply to TCS, Infosys, Wipro, and Cognizant simultaneously. Different test dates, different interview schedules, different follow-up timelines across four companies creates real cognitive load. The DecodedCareers Interview Tracker keeps every application, every stage, and every deadline in one place so nothing falls through the cracks.
Use Interview TrackerThis article was built from real interview data.
“Foundit Infosys interview guide, PrepInsta question bank, Internshala HR question breakdowns, AmbitionBox candidate accounts, and Reddit experience threads — all cross-checked before a single question was included here.”If this helped you walk into that interview room more prepared — consider supporting DecodedCareers. No subscription. No pressure. One reader choosing to back honest, useful content.
Support DecodedCareersFrequently Asked Questions
What are the most common Infosys interview questions for freshers?
The most consistently asked questions across Infosys fresher interviews are: explain your final year project, the four pillars of OOP with examples, difference between DROP and TRUNCATE, process versus thread, difference between stack and queue, write a string reversal or palindrome program, tell me about yourself, why do you want to join Infosys, where do you see yourself in 5 years, and are you willing to relocate. These appear in almost every Infosys interview regardless of track.
How many rounds are there in the Infosys interview for freshers?
Infosys fresher interviews have two rounds: a technical interview lasting 30 to 45 minutes and an HR interview lasting 15 to 20 minutes. Both can happen on the same day or on separate dates. The technical round covers OOP, DBMS, OS, data structures, coding, and your final year project. The HR round covers self-introduction, company motivation, career goals, and policy questions like relocation and shift flexibility.
Does Infosys reject after the HR round?
Yes, Infosys can reject candidates at the HR round, though it is less common than technical round rejections. HR round rejections typically happen when communication is genuinely poor, when a candidate refuses to accept relocation to Mysuru for training, when shift flexibility is refused outright, or when answers raise significant concerns about cultural fit. The HR round is not a formality — prepare it with the same seriousness as the technical round.
What OOP questions does Infosys ask freshers?
The most common OOP questions are: explain the four pillars of OOP with real-world examples, what is the difference between overloading and overriding, what is an abstract class versus an interface, can you give a real example of polymorphism, and what is the difference between compile-time and runtime polymorphism. Prepare practical examples for each concept rather than textbook definitions, and connect answers to your own project work wherever possible.
What SQL questions are asked in Infosys interviews?
Common SQL questions include: difference between DROP, TRUNCATE, and DELETE, what is normalization and why is it important, explain ACID properties, difference between primary key and foreign key, write a query to find the second highest salary, what are joins and explain INNER vs LEFT JOIN. Be ready to write SQL queries on screen or paper — Infosys technical interviewers consistently ask candidates to write live queries rather than just explain concepts.
How should I answer “Why do you want to join Infosys?”
Mention something specific rather than generic praise. Reference the structured Foundation Training Programme at Mysuru, Infosys’s growing presence in cloud and AI through the DSE track, or a specific recent Infosys initiative you researched. Connect it to your own goal — what you want to build, learn, or contribute there. A specific answer that demonstrates you researched Infosys distinctly from TCS or Wipro is far more effective than positioning Infosys as “a global leader in IT services.”
What should I say when asked about my weakness in an Infosys HR interview?
Choose a real weakness that is not directly critical to the SE role. Then explain the specific action you took to improve it and the result. A strong structure: “I sometimes get absorbed in a problem and lose track of time. I started using time-boxing — setting a 30-minute limit before asking for help or moving on — and this has made my problem-solving more efficient and my project work more timely.” The weakness itself matters less than your self-awareness and the concrete action you took.
What questions should I ask the Infosys interviewer at the end?
Always prepare two genuine questions. Strong options: “What does the typical first project assignment look like for freshers joining the SE track?” or “How is performance evaluated during the Mysuru training period?” Avoid asking about salary in the interview round — that is handled at the offer stage. Saying you have no questions signals disinterest and is one of the most common missed opportunities in the Infosys HR round.
How long does the Infosys technical interview last for freshers?
The Infosys technical interview for freshers typically lasts 30 to 45 minutes. The project viva often takes 15 to 20 minutes of this time. The remaining time covers OOP, DBMS, OS fundamentals, and one or two coding questions. The interviewer may ask you to share your screen and write code live, or write on paper depending on the interview format. Prepare equally for both written and verbal formats.
Can I crack the Infosys interview without a CS background?
Yes. Many non-CS freshers clear Infosys SE track interviews by preparing OOP fundamentals, basic SQL, data structure concepts, and a strong project. Infosys values communication ability and logical thinking alongside technical knowledge. The pseudocode section of the online assessment specifically does not require language-specific coding knowledge. Freshers from ECE, EEE, and MCA backgrounds regularly clear Infosys interviews with 3 to 4 weeks of focused preparation on the core topics.
What is the STAR method and how should I use it in Infosys HR interviews?
STAR stands for Situation, Task, Action, Result. Use it for behavioural questions in the HR round. Situation: briefly describe the context. Task: what you were responsible for. Action: the specific steps you took. Result: what happened and what you learned. For example, if asked about handling a challenge in a team project: describe the specific conflict or problem, your role in resolving it, the action you took, and the outcome. Keep the full answer under 90 seconds. STAR answers are effective because they are specific and structured — the opposite of a rehearsed generic response.
How should I prepare for the Infosys interview in 7 days?
Day 1: project preparation and explanation practice. Day 2: OOP and DBMS. Day 3: data structures and coding problems. Day 4: operating systems and computer networks. Day 5: HR preparation including self-introduction, company research, and weakness answer. Day 6: full mock interview across both rounds with recording and review. Day 7: revision of weak areas only, document preparation, and rest. Sixty to ninety minutes of focused daily practice is more effective than one long cramming session.
What documents do I need for the Infosys interview?
Bring printed copies of your updated resume (at least two copies), a recent passport-size photograph, original government-issued ID (Aadhaar or PAN), original and photocopies of Class 10, 12, and graduation mark sheets and certificates, and your Infosys interview call letter with the date and location. Some drives also require your offer or shortlist letter. Confirm the document checklist in the interview invitation email as requirements vary by drive format.
How to pass an Infosys interview as a fresher?
Know your final year project deeply — this is where most technical rounds are won or lost. Prepare OOP, DBMS, OS, and data structure fundamentals with practical examples rather than textbook definitions. Practice writing basic code without syntax errors. For the HR round, research Infosys specifically, prepare your self-introduction using the Present, Past, Future structure, and accept relocation and shift flexibility without qualification. Show composure when you do not know an answer — explain how you would approach finding the answer rather than guessing incorrectly.
Continue Learning
Now build the skills Infosys is actually looking for
You know the questions. You know the answers. The next edge is having the technical skills that make those answers credible — the SQL depth, the OOP understanding, and the coding fundamentals that Infosys probes in every technical round. The Skills menu on DecodedCareers helps you decide what to learn next.
Explore SkillsWas this article useful?
Your vote helps us understand what works.
Important Notice
DecodedCareers publishes educational content based on publicly available information and independent research. Interview questions and answer guidance are based on verified candidate experiences from Foundit, PrepInsta, AmbitionBox, Internshala, and Reddit as of June 2026. Infosys may update its interview process, question patterns, and evaluation criteria at any time. This article is for preparation guidance only and does not guarantee interview or employment outcomes.
References
- Foundit — Infosys Interview Questions 2026: foundit.in
- PrepInsta — Infosys Interview Questions: prepinsta.com
- Internshala — Top 40 Infosys HR Interview Questions: internshala.com
- AmbitionBox — Infosys Interview Questions: ambitionbox.com
- Unstop — 30 Infosys Interview Questions: unstop.com
- ACTE Technologies — Infosys Fresher Interview Q&A: acte.in
Have you appeared for an Infosys interview? Tell us which round surprised you most and what question you were least prepared for. One comment here helps hundreds of freshers preparing for the same interview. Leave a comment below. 👇