Infosys Interview Questions & Answers for Freshers (2026)

You cleared the InfyTQ test. The mail came. There's a date, a time slot, and a link and now you're sitting there at 1 a.m. scrolling through random question lists, wondering which of these will actually show up.

Here's the thing most prep lists won't tell you: Infosys interviewers are rarely trying to catch you out. For fresher roles, they're checking three things do you understand the basics you claim to know, can you explain your own project without hiding behind buzzwords, and will you actually stick around after the Mysuru training.

That's it. Almost every question below is a different way of asking one of those three things.

This guide covers 35+ Infosys interview questions and answers technical, HR, and the awkward ones people fumble. Each one tells you what the interviewer is really checking, followed by an effective answer you can adapt in your own words. Don't memorise them word for word. Interviewers can hear a memorised answer from a mile away.

Preparing for IT service roles? Our free Basics of Web Development crash course and SQL Mastery crash course cover the exact fundamentals these interviews test.

Infosys Interview Process 2026: What You're Walking Into

Infosys doesn't run one single hiring funnel like some of its peers. There are multiple entry points, and which one you came through changes how hard your technical round will be.

Packages shift by cycle and location always confirm the number in your own offer letter, not from a blog.

The rounds themselves are fairly consistent:

1. Online assessment quantitative aptitude, logical reasoning, verbal ability, and pseudocode. SP and DSE candidates also get coding questions, usually in Java or Python.
2. Technical interview OOP, DBMS, data structures, and a deep dig into whatever is written on your resume.
3. HR interview situational questions, relocation, long-term plans, and the classic "why us."

Two Infosys-specific things worth knowing. InfyTQ is a free learning and certification platform that doubles as a hiring pipeline clearing the certification improves your shortlisting odds, especially for off-campus applicants. HackWithInfy is the coding contest that feeds the higher-paying tracks. If you're still in your pre-final year, both are worth doing early.

For eligibility, most drives look for 60%+ (or 6.5 CGPA) across Class X, XII and graduation, no active backlogs at the time of the drive, and an education gap within two years. Specific drives vary, so read the actual notification.

Infosys HR Interview Questions & Answers

1. Tell Me About Yourself

This is the opener in almost every Infosys interview, and most candidates waste it by reciting their resume line by line. The interviewer is checking whether you can structure a thought and stop talking on time. Give a 60–90 second arc: your academic background, what got you interested in the field, one thing you built, and why you're sitting in this chair.

Effective Answer: "I'm a final-year Computer Science student at [college]. I got properly interested in backend work in my fifth semester when I built a college event registration system it was the first time I had to think about what happens when 200 people hit submit at once, not just whether the code ran. Since then I've focused on Java and SQL, and I completed my InfyTQ certification in Java last November. I'm looking to start my career somewhere I'll get structured training and exposure to real client projects, which is what drew me to Infosys."

2. Why Do You Want to Join Infosys?

This question checks one thing: did you apply to Infosys, or did you apply to 40 companies and Infosys replied first? The failure mode is generic praise "Infosys is a reputed company with a good work culture." Every candidate says that. Name two specific things instead: a programme, a location, a domain, or something a senior actually told you.

Effective Answer: "Two specific reasons. First, the training at the Mysuru Global Education Center I've spoken to two seniors who went through it, and both said the first six months taught them more than their final year did. As someone starting out, that structured foundation matters more to me right now than a slightly higher package elsewhere. Second, Infosys works across a lot of domains banking, retail, healthcare and I'd rather start somewhere I can find out what I'm actually good at before specialising."

3. What Are Your Strengths and Weaknesses?

This tests self-awareness, and the weakness half is where people lose marks. Avoid the humblebrag "I work too hard" reads as evasive because interviewers have heard it a thousand times. Name a real, fixable, non-fatal weakness and show the correction already in progress.

Effective Answer (Strength): "I'm good at breaking a problem into pieces before I start. In my final-year project, our team was stuck for a week on a feature until I mapped out what was actually failing versus what we assumed was failing turned out the bug was in one function, not the architecture."

Effective Answer (Weakness): "I've been weak at asking for help early. I'd spend six hours on something a teammate could have unblocked in ten minutes. During my internship my mentor gave me a rule if I'm stuck past 45 minutes, I ask. It felt uncomfortable at first but my output improved a lot."

4. Where Do You See Yourself in Five Years?

This question is screening for attrition risk. Infosys invests heavily in fresher training, so a candidate who says "I want to do my MBA in two years" is an expensive hire. Show a growth path that stays inside one organisation.

Effective Answer: "In five years I'd like to be someone the team hands the tricky module to. Realistically that means two to three years of getting genuinely solid at development, then growing into module ownership and eventually mentoring the freshers who join after me. I'd like that growth to happen inside one organisation rather than by hopping you don't get depth by starting over every 18 months."

5. Are You Comfortable Relocating?

This is a filter question, not a conversation. Infosys has campuses in Mysuru, Bengaluru, Pune, Hyderabad, Chennai, Bhubaneswar and Chandigarh, and training happens at Mysuru regardless of where you're finally allocated. Saying no here can genuinely end the process but if you have a real constraint, say it honestly and briefly rather than lying and creating a problem at joining.

Effective Answer: "Yes, I'm open to any location. I know training happens at Mysuru and I'm looking forward to that. I've lived away from home during college, so relocating isn't new to me."

6. Are You Willing to Work in Shifts?

Another filter question. Client projects in IT services run on global timelines, so the interviewer wants confirmation that you understand what you're signing up for and won't raise it as a problem later.

Effective Answer: "Yes. I understand client projects run on global timelines and shift work comes with the territory in IT services. I'd manage my routine around it."

7. How Do You Handle Pressure and Tight Deadlines?

Interviewers are listening for evidence, not adjectives. "I stay calm and organised" tells them nothing. Answer with a specific incident and end with what you took away from it.

Effective Answer: "Our final-year review got moved up by ten days and we had two modules unfinished. I listed everything left, split it into what the reviewers would definitely check versus what was nice-to-have, and we cut two features nobody had asked for. We presented a smaller but working system instead of a broken ambitious one. What I took from it: under pressure, the first job is deciding what not to do."

8. Tell Me About a Time You Worked With Someone Who Wasn't Contributing

This is a teamwork and maturity check. The wrong answer is one where you escalate immediately or badmouth the teammate. They want to see whether you'll try to solve a people problem before making it someone else's problem.

Effective Answer: "One teammate went quiet for two weeks during our project. Instead of going to our guide immediately, I asked him directly what was going on he was struggling with the framework and embarrassed to say so. We paired for two sessions and he handled the entire frontend after that. I learned that non-contribution usually looks like laziness from outside and feels like being stuck from inside."

9. Why Should We Hire You?

This tests whether you can make a case for yourself without either bragging or apologising. For a fresher role, don't claim experience you don't have argue for trainability, which is what they're actually buying.

Effective Answer: "I won't claim I'm the most experienced person you'll interview today. But I've built things end to end, I pick up new stacks quickly I learned React in three weeks for my project and I'm genuinely willing to be corrected. For a fresher role, I think trainability matters more than what I already know, and that's where I'd rate myself highly."

10. Do You Have Any Questions for Us?

This looks like a closing formality but it's still being scored. Saying "no, everything is clear" reads as disinterest. Ask something that shows you're thinking about the job, not the offer letter avoid salary, appraisal and leave policy at this stage.

Effective Answer: "Yes, two things. What does a typical first year look like after the Mysuru training how soon do freshers get onto live client work? And in your experience, what separates the freshers who do really well here from the ones who struggle?"

Infosys Technical Interview Questions & Answers

For System Engineer roles, expect fundamentals explained clearly rather than hard algorithmic puzzles. For SP and DSE tracks, expect real data structures and problem solving.

11. What is Object-Oriented Programming?

This is the standard opening technical question for anyone who lists Java, C++ or Python. The interviewer is checking whether you understand the why behind OOP or have only memorised the four pillars as a list.

Effective Answer: "OOP is a way of structuring code around objects bundles of data and the methods that act on that data rather than around procedures. Its four pillars are encapsulation, inheritance, polymorphism and abstraction. The practical benefit is that code becomes reusable and easier to change without breaking unrelated parts."

12. Explain the Four Pillars of OOP With Examples

This is the follow-up to the previous question, and it separates the candidates who memorised definitions from the ones who've actually written classes. Always attach a concrete example to each pillar.

Effective Answer: "Encapsulation is keeping data private and exposing it only through methods like a bank account class where balance can't be modified directly. Inheritance lets a class reuse another's properties, so a SavingsAccount extends Account. Polymorphism lets the same method behave differently depending on the object a calculateInterest() call resolving differently for savings versus a fixed deposit. Abstraction hides implementation and exposes only what's necessary you call withdraw() without knowing how the ledger updates."

13. What is the Difference Between an Abstract Class and an Interface?

A very common Infosys technical question because it has a clean right answer and a natural follow-up ("when would you use which?"). Answer the difference, then give the rule of thumb that second part is what most candidates skip.

Effective Answer: "An abstract class can have both implemented and unimplemented methods and can hold state through instance variables, and a class can extend only one. An interface declares behaviour a class must implement, and a class can implement several. My rule of thumb is: abstract class for an 'is-a' relationship where there's shared code, interface for a capability you want across unrelated classes."

14. What is the Difference Between Method Overloading and Overriding?

This checks whether you understand compile-time versus runtime behaviour, not just the surface definition. Mention the polymorphism type it signals depth in one extra sentence.

Effective Answer: "Overloading is the same method name with a different parameter list, resolved at compile time, and it happens within the same class. Overriding is a subclass replacing a parent's method with the same signature, resolved at runtime. So overloading is compile-time polymorphism and overriding is runtime polymorphism."

15. What is a Data Structure? Which Ones Have You Used?

The second half of this question matters more than the first. The interviewer wants to know whether you've actually used data structures in code or only read about them, so name where you used each one.

Effective Answer: "A data structure is a way of organising data so that specific operations become efficient. I've used arrays for indexed access, linked lists in a playlist implementation, stacks for expression evaluation, and hash maps most often for anything that needs near-constant-time lookup by key."

16. What is the Difference Between an Array and a Linked List?

This is a classic trade-off question. Don't just list differences finish by saying when you'd choose each, because that's what the interviewer is actually testing.

Effective Answer: "Arrays store elements in contiguous memory, so access by index is O(1), but insertion and deletion in the middle cost O(n) because elements have to shift. Linked lists store nodes with pointers, so insertion and deletion are O(1) if you already have the node reference, but access is O(n) since you traverse from the head. So arrays for read-heavy work, linked lists for insert-heavy work."

17. What is a Stack and Where is it Used?

This checks whether you can connect a concept to real applications. Anyone can say "LIFO" the marks are in the examples.

Effective Answer: "A stack is a LIFO structure last in, first out with push and pop happening at the same end. It's used for function call management, undo operations, browser back navigation, and for checking balanced parentheses in expression parsing."

18. What is Time Complexity? Explain Big-O Notation

This question tests whether you think about efficiency at all, which matters because Infosys works on systems handling large data volumes. Give the common complexity classes with an example of each, then say why it matters practically.

Effective Answer: "Time complexity describes how an algorithm's running time grows as the input size grows, and Big-O notation captures the worst case. O(1) is constant time, O(log n) is binary search, O(n) is a single loop, O(n log n) is efficient sorting like merge sort, and O(n²) is nested loops. It matters because an algorithm that's fine on 100 records can be completely unusable on 10 million."

19. What is Recursion? What is a Base Case?

A favourite because it has a built-in follow-up trap if you don't mention the base case, they'll ask what happens without one. Mention it yourself and name the consequence.

Effective Answer: "Recursion is a function calling itself on a smaller version of the same problem until it reaches a base case, which is the condition that stops the recursion. Without a base case you get infinite recursion and a stack overflow. I've used recursion for factorial, Fibonacci and tree traversals."

20. What is a DBMS? What is an RDBMS?

This opens the database section of almost every Infosys technical round. Draw the distinction clearly and name real products it shows you've worked with one rather than just studied the theory.

Effective Answer: "A DBMS is software that stores, retrieves and manages data. An RDBMS stores that data in tables of rows and columns and supports relationships between tables through keys, along with ACID properties for transaction reliability. MySQL, Oracle and PostgreSQL are RDBMS examples."

21. What is Normalisation and Why Do We Do It?

This tests whether you understand database design or only query writing. Explain the normal forms briefly, but the real marks are in stating the benefit and the trade-off.

Effective Answer: "Normalisation organises data to reduce redundancy and avoid update anomalies. 1NF requires atomic values, 2NF removes partial dependency on a composite key, and 3NF removes transitive dependency. The benefit is data integrity you update a customer's address in one place instead of forty. The trade-off is more joins, which is why reporting databases are sometimes deliberately denormalised."

22. What is a Primary Key Versus a Foreign Key?

A fundamentals check that comes up in nearly every round. Keep it short and add the constraint each one enforces.

Effective Answer: "A primary key uniquely identifies each row in a table and can't be null or duplicated. A foreign key is a column that references another table's primary key, and it enforces referential integrity so you can't insert an order for a customer who doesn't exist."

23. What is a SQL JOIN? Explain the Types

SQL is tested heavily at Infosys across almost every role, and JOINs are the most likely single question. List the types, then say which ones you actually use that last line makes the answer sound practical rather than recited.

Effective Answer: "A JOIN combines rows from two or more tables using a related column. INNER JOIN returns only matching rows. LEFT JOIN returns all rows from the left table plus matches from the right, with nulls where there's no match. RIGHT JOIN is the mirror of that, and FULL OUTER JOIN returns everything from both sides. In practice I use INNER and LEFT the most."

24. What is the Difference Between DELETE, TRUNCATE and DROP?

A high-frequency question because the three are easy to confuse under pressure. The key differentiators the interviewer wants are rollback behaviour and whether the structure survives.

Effective Answer: "DELETE removes rows based on a condition, logs each row, and can be rolled back. TRUNCATE removes all rows quickly, resets the identity, and is much harder to roll back. DROP removes the entire table structure along with the data."

25. What is an Index in a Database?

This checks whether you think about performance. The analogy is fine, but you must mention the cost candidates who say indexes are purely good get a follow-up they don't expect.

Effective Answer: "An index is a structure that speeds up lookups on a column, much like the index at the back of a book. It makes reads faster but writes slightly slower, because the index has to update too. So you add them to columns you filter and join on frequently, not to every column."

26. What is the Difference Between WHERE and HAVING?

A precise question with a precise answer, often used to test whether you understand the order of execution in a SQL query. Give an example the difference is much clearer with one.

Effective Answer: "WHERE filters individual rows before grouping happens. HAVING filters groups after GROUP BY has been applied. So I'd use WHERE to exclude cancelled orders, and HAVING to show only customers whose total order value crosses a threshold."

27. What is an Operating System? What Does it Do?

A core computer science fundamental that Infosys asks across all engineering streams, not just CS. Define it, then list its main responsibilities the list is what they're waiting for.

Effective Answer: "An operating system is system software that manages the hardware and software resources of a computer and acts as the interface between the user and the machine. Its core jobs are process management, memory management, file system handling, device management and security."

28. What is the Difference Between a Process and a Thread?

This tests depth in OS concepts. Mention shared memory and its consequence synchronisation because that's the natural follow-up and it's better if you get there first.

Effective Answer: "A process is an independent program in execution with its own memory space. A thread is a unit of execution inside a process and shares that process's memory. Threads are lighter to create and switch between, but because memory is shared you have to handle synchronisation carefully."

29. What is Deadlock?

Frequently asked as a follow-up to the process and thread question. Define it, then list the four necessary conditions naming them is what distinguishes a strong answer here.

Effective Answer: "Deadlock is when two or more processes each hold a resource the other needs, so none of them can proceed. It requires four conditions at the same time mutual exclusion, hold and wait, no preemption, and circular wait. If you break any one of those, you prevent it."

30. What is the Difference Between HTTP and HTTPS?

This tests web fundamentals and basic security awareness. Don't stop at "HTTPS is secure" say what actually provides the security.

Effective Answer: "HTTP transfers data in plain text. HTTPS layers SSL/TLS encryption on top, so data in transit is encrypted and the server's identity is verified through a certificate. Anything handling logins or payments should be on HTTPS."

31. What is an API?

Almost guaranteed if your resume mentions web development. The strongest answers include one API you personally consumed, because it proves you've used one rather than defined one.

Effective Answer: "An API is a defined contract that lets two pieces of software talk to each other without knowing each other's internals. A REST API exposes endpoints over HTTP that return data, usually as JSON. In my project I consumed a weather API I sent a city name and got structured data back without knowing anything about how their system worked."

32. What is Cloud Computing?

This checks your awareness of modern technologies used across the industry. Define it, name the service models, and name real providers Infosys runs large cloud practices, so this often leads into a follow-up about which one you've touched.

Effective Answer: "Cloud computing is the delivery of computing resources like storage, servers, databases and networking over the internet on a pay-as-you-use basis, instead of owning physical hardware. The main service models are IaaS, PaaS and SaaS, and the major providers are AWS, Microsoft Azure and Google Cloud."

33. Explain Your Final Year Project

This is the most important technical question in the entire interview, and the one candidates prepare least. Interviewers follow your answer wherever it leads, so mention only what you can defend. Structure it as: problem, what you built, your specific contribution, the hardest part, and what you'd change now.

Effective Answer: "We built a hostel complaint management system because complaints were being tracked on paper and getting lost. It was a Java backend with a MySQL database and a basic web frontend. I owned the backend and the database schema design, the complaint routing logic, and the status API. The hardest part was the escalation rule: if a complaint isn't actioned within 48 hours it moves up to the warden. Getting that reliable without a scheduler was messy, and honestly, if I rebuilt it today I'd use a proper scheduled job instead of the workaround we used."

That last line volunteering a flaw is one of the strongest things a fresher can do in a technical round. It signals that you actually built the thing.

34. Which Programming Language Are You Most Comfortable With, and Why?

This question exists to decide where the rest of the interview goes. Whatever you name, the next ten minutes will be in that language so answer honestly, and never name a language you listed on your resume but haven't touched since second year.

Effective Answer: "Java, mainly because it's what I've built the most in my final-year project backend and most of my InfyTQ practice were in Java. I'm comfortable with OOP concepts, collections and exception handling in it. I can also write Python for scripting and data work, but Java is where I'd be most confident in a code review."

35. Write a Program to Reverse a String / Check a Palindrome / Find the Second Largest Element

Expect one or two basic coding problems on paper or in a shared editor for SE roles. The mistake is starting to write immediately talk through your approach first, then code, then state the time complexity without being asked. That last habit makes you look noticeably more prepared than the average candidate.

Effective Answer (approach, spoken before coding): "For the second largest element, I'd avoid sorting since that's O(n log n) for something I can do in one pass. I'll track two variables largest and second largest and update them as I traverse once. I'll need to handle the edge case where all elements are equal, and where the array has fewer than two elements. That gives me O(n) time and O(1) extra space. Shall I write it out?"

For SP and DSE candidates, this section gets significantly harder arrays, strings, hashing, trees and dynamic programming basics.

5 Mistakes That Get Freshers Rejected at Infosys

• Resume padding. Listing a skill you can't discuss for two minutes is the fastest way to lose the room. Interviewers pick the least likely item on your resume and ask about it.
• Treating the HR round as a formality. Infosys HR interviewers ask detailed scenario questions. Candidates who nail the technical round and wing HR do get rejected.
• Saying no to relocation or shifts without thinking through whether you actually mean it.
• Going silent when stuck. If you don't know something, say "I'm not sure, but here's how I'd approach finding out." A blank stare scores lower than an honest attempt.
• Zero company research. Not knowing what Infosys does, roughly how large it is, or who leads it comes across badly in a round explicitly designed to test interest.

How to Prepare for the Infosys Interview: A 4-Week Plan

Week 1-- Aptitude. Quantitative (percentages, time and work, probability), logical reasoning (series, blood relations, syllogisms) and verbal ability. Sectional timing is strict, so practise against a clock, not just for accuracy.

Week 2--Pseudocode and core CS. Pseudocode trips up more candidates than actual coding does. Then OOP, DBMS and OS fundamentals the questions above cover most of what gets asked.

Week 3-- Coding and SQL. Arrays, strings and basic DSA. Write out joins, GROUP BY and subqueries by hand. Our free SQL Mastery crash course covers the query patterns that show up repeatedly.

Week 4-- Your resume and mock rounds. Prepare a two-minute and a five-minute version of your project. Do at least three mock interviews out loud with a friend. Reading answers silently creates false confidence the gap only shows up when you have to speak.

What should I wear to an Infosys interview? Formals even for virtual rounds.

Final Thoughts

Most people who fail an Infosys interview don't fail on knowledge. They fail because they memorised twenty answers and got asked the twenty-first, or because they wrote something on a resume they couldn't defend.

Take the questions above and rewrite every effective answer in your own words, with your own project, your own college, your own examples. Then say them out loud. If a sentence feels strange in your mouth, it'll sound strange to the interviewer too.

You've already cleared the part that filters out most applicants. Go get it.