Top 10 Infosys Online Assessment Interview Questions and Answers 2026: Clear the Gate and Win the Interview

Let’s clear up the biggest myth first. Infosys doesn’t screen freshers with a one-way video interview, and there’s no HireVue waiting to record you in a dark room. People search for an Infosys HireVue that simply doesn’t exist in any candidate report.

What you actually face is a proctored, multi-section online assessment branded as InfyTQ or delivered through the NQT (National Qualifier Test). It covers reasoning, math, verbal, pseudocode, and either puzzles or live coding depending on your track. Only after you clear it, with sectional cutoffs, do you talk to a human.

That’s the part this guide gets you ready for. First we break down the assessment itself so nothing surprises you. Then we walk through the 10 questions Infosys interviewers ask most once you’re through the gate, with full sample answers you can adapt.

Treat this like advice from someone who’s seen both sides of the table. Calm, specific, and built so you walk in knowing exactly what each question is really testing.

Understanding Infosys’s Online Assessment Process

Here’s the shape of it. You apply or register for a drive, then the very first screening is a proctored online assessment. No recruiter talks to you before this. Clear it and you move forward, miss a sectional cutoff and you’re out, even with a strong overall score.

For the System Engineer track, you get 54 questions in roughly 100 minutes: 15 reasoning, 10 math, 20 verbal, 5 pseudocode, and 4 puzzles. The Specialist Programmer and Power Programmer tracks swap the puzzles for 2 to 3 live coding problems and stretch the whole thing to around 180 minutes. According to Unstop’s Infosys recruitment breakdown, there’s no negative marking, but the sectional cutoffs are real and they’re where most people fall.

Each section has its own fixed time block, and you can’t revisit a section once it’s done. Reasoning gets about 25 minutes, math or technical about 35, verbal 20, pseudocode 10, and puzzles 10. The coding block on the SP track runs 60 to 120 minutes for the whole set.

Scoring is automated for the MCQ and pseudocode sections, and coding answers are checked against test cases. The pass rate is brutal in places. One on-campus report cited on GeeksforGeeks had 103 of 780 students clearing the assessment, roughly 13 percent, with another drive reported near 5 percent.

After the assessment, you get live technical and HR interviews, often the same day or the next day on campus, or over Microsoft Teams for off-campus hires. This isn’t a phone screen, but the clarity it demands rhymes with one, and our rundown of common phone interview questions is a useful warmup for talking about yourself under pressure.

• Format: Proctored in-house online assessment (InfyTQ / NQT), not a video interview
• Questions: 54 total for SE (15 Reasoning + 10 Math + 20 Verbal + 5 Pseudocode + 4 Puzzles); SP/PP swap puzzles for 2-3 coding problems
• Duration: ~100 minutes for SE; ~180 minutes for SP/PP coding-heavy track
• Section time limits: Reasoning 25 min, Math/Technical 35 min, Verbal 20 min, Pseudocode 10 min, Puzzles 10 min
• Scoring: Automated for MCQ and pseudocode; coding checked against test cases; sectional cutoffs apply
• Negative marking: None for the SE track
• Retakes: No retakes; can’t reapply to Infosys within 6 months
• What follows: Live technical + HR interviews, same/next day on campus or via MS Teams off-campus

Top 10 Infosys HireVue Questions With Sample Answers

1. Tell me about yourself.

What they’re really testing: This is the opening filter for communication clarity and structured self-presentation. Infosys is a client-facing IT services company, so HR is gauging verbal fluency and confidence from your very first sentence.

Interview Guys Tip: Situation: I’m a final-year [DEGREE] student at [COLLEGE] who got hooked on building things after my first [LANGUAGE] project. Obstacle: Early on, I could write code but struggled to explain my decisions clearly, which hurt me in team settings. Action: I started leading the demo walkthroughs for my project team, built [PROJECT] end to end, and earned my [CERTIFICATION, e.g. InfyTQ or a cloud badge] to sharpen my fundamentals. I also practiced structuring every explanation around the problem, my approach, and the result. Result: I shipped [PROJECT] that [SPECIFIC OUTCOME, e.g. cut manual effort by X], and my communication is now a strength rather than a gap. That mix of hands-on coding and clear articulation is exactly what I want to bring to Infosys.

Avoid this: Reciting your resume top to bottom. Keep it to a tight arc that lands on why you fit, and lean on our guide to answering tell me about yourself if you tend to ramble.

2. Why do you want to join Infosys?

What they’re really testing: This tests genuine company knowledge versus a generic answer. Interviewers expect specific references to things like the Mysore training campus, InfyTQ, Infosys Springboard, or a particular business unit.

Interview Guys Tip: Situation: When I was deciding where to start my career, I looked closely at how companies train and grow freshers. Obstacle: A lot of firms throw you into delivery with little structure, which I wanted to avoid for my first role. Action: I researched Infosys and found the Mysore induction program, the InfyTQ learning ecosystem, and investments like Infosys Cobalt and Topaz in cloud and AI. I completed [SPECIFIC INFYTQ COURSE OR SPRINGBOARD MODULE] to understand how you work. Result: That told me Infosys builds engineers deliberately and keeps investing in new technology, so I’d grow fast while delivering real client value. That’s the environment I want to start in, and I’m ready to be flexible on the technology and location that need me.

Avoid this: Saying it’s a good company or the salary is nice. That’s an instant red flag. Name something specific you actually read about Infosys.

3. Tell me about your project: what problem did it solve, what tech stack did you use, and what was the outcome?

What they’re really testing: This is the core filter for SE and SP roles. They want concise articulation, an ownership mindset, and proof your hands-on experience is real, not just a resume line.

Interview Guys Tip: Situation: My team tackled [PROBLEM, e.g. students missing deadlines because reminders were scattered]. Obstacle: We had [CONSTRAINT, e.g. no budget for paid tools and only four weeks]. Action: I owned the [SPECIFIC PART, e.g. backend and database], built it with [TECH STACK, e.g. Python, Flask, and MySQL], designed the schema myself, and handled the [FEATURE, e.g. notification logic]. When [SPECIFIC BLOCKER] came up, I [HOW YOU SOLVED IT]. Result: We delivered [OUTCOME, e.g. a working app used by X people] that [MEASURABLE IMPACT, e.g. reduced missed deadlines by Y percent]. I can walk through any decision in the code, because I made most of them. That ownership is what I’d bring to an Infosys delivery team.

Avoid this: Listing a project you can’t defend under follow-up questions. Interviewers probe fast, and a resume line you can’t explain is the quickest way to get caught out.

4. Are you willing to work in any technology stack, and are you open to relocation anywhere in India?

What they’re really testing: Infosys assigns freshers to projects based on business need, not preference. A flat ‘no’ here is commonly cited as a disqualifier for SE roles, so adaptability is the whole point.

Interview Guys Tip: Situation: I know Infosys allocates freshers to projects based on client and business needs. Obstacle: Some candidates limit themselves to one stack or one city, which clashes with how delivery actually works. Action: Through [COURSE OR PROJECT], I’ve deliberately learned to pick up new tools quickly, moving from [TECH A] to [TECH B] in [TIMEFRAME] when a project needed it. I’ve kept my fundamentals strong so the specific language matters less. Result: I’m genuinely open to any stack you assign and to relocating anywhere in India, including the Mysore training phase. I see learning a new technology as a growth opportunity, not a hurdle, and I’d rather be useful where I’m needed than hold out for a preference.

Avoid this: Hedging with ‘I’d prefer only Python’ or ‘I can’t relocate.’ That’s one of the most reported HR-stage rejections. If you have a real constraint, raise it honestly, but know the expectation.

5. What are your strengths and weaknesses?

What they’re really testing: A standard self-awareness check that rewards honesty and evidence. Interviewers watch for clichés like ‘I work too hard’ and prefer a real weakness with a real plan around it.

Interview Guys Tip: Situation: In my project work and coursework, I’ve learned where I’m strong and where I had to improve. Obstacle: My honest weakness was [SPECIFIC WEAKNESS, e.g. I’d over-optimize code before the feature even worked]. Action: For strengths, I’m persistent at debugging and I explain technical ideas clearly, which I proved by [EXAMPLE]. For the weakness, I started writing a working version first and refactoring only after, and I asked [MENTOR OR TEAMMATE] to flag when I was polishing too early. Result: I shipped [PROJECT] on time instead of running over, and over-optimizing stopped costing me deadlines. I’d rather name a genuine gap and show I’m fixing it than give you a fake weakness that’s really a brag.

Avoid this: The disguised humblebrag. Integrity and transparency are Infosys values, and interviewers can smell a rehearsed non-weakness from across the room.

6. Explain the OOP concepts: inheritance, polymorphism, abstraction, and encapsulation, with a real-world example.

What they’re really testing: This is a fundamental CS knowledge gate for SE roles, expected of every CS or IT fresher regardless of favorite language. They want you to show understanding, not recite definitions.

Interview Guys Tip: Situation: In my [PROJECT], I used all four OOP pillars, so I’ll explain them through that. Obstacle: The tricky part is showing I understand why each exists, not just the textbook line. Action: Encapsulation is bundling data and methods and hiding internals: my [CLASS, e.g. Account] kept the balance private and exposed only deposit and withdraw. Abstraction hides complexity behind a simple interface, like calling a payment method without knowing the gateway logic. Inheritance let [CHILD CLASS] reuse [PARENT CLASS] behavior, so [EXAMPLE]. Polymorphism let the same method behave differently, like a [SHAPE] base with an area() that each shape overrides. Result: Using these kept my code modular and easy to extend, and when I added [NEW FEATURE] later, I only touched one class instead of rewriting everything.

Avoid this: Rattling off definitions with no example. Tie each concept to code you actually wrote, because the follow-up question is always ‘can you give an example?’

7. What is normalization? Explain 1NF, 2NF, and 3NF with examples.

What they’re really testing: Database fundamentals are core to most Infosys project types. Interviewers want candidates who understand why normalization exists, not just the forms by name.

Interview Guys Tip: Situation: In [PROJECT], I designed the database schema myself, so normalization wasn’t theory for me. Obstacle: My first draft had repeated data that would’ve caused update anomalies. Action: Normalization is organizing tables to reduce redundancy and keep data consistent. I applied 1NF by making every column atomic, so one cell held one value, no comma-separated lists. I applied 2NF by removing partial dependencies, splitting out [EXAMPLE, e.g. product details into their own table keyed properly]. I applied 3NF by removing transitive dependencies, so [EXAMPLE, e.g. a city depending on a pincode moved to its own table]. Result: The schema stopped duplicating data, updates touched one place instead of many, and the app stayed consistent as it grew. Understanding why each form matters helped me catch design flaws before they became bugs.

Avoid this: Defining the forms without concrete examples. The brief is explicit: they test whether you understand the why, so lead with the anomaly each form prevents.

8. Where do you see yourself in five years?

What they’re really testing: This assesses long-term commitment and career clarity. Infosys wants to avoid churn from freshers who plan to jump to a product company the moment they’re trained.

Interview Guys Tip: Situation: I’m starting my career and I want a place where I can grow deep, not just collect a brand name. Obstacle: A lot of freshers treat their first job as a six-month stepping stone, and that short-term thinking shows. Action: Over five years, I want to master delivery fundamentals, grow from a strong individual contributor into someone who mentors juniors and owns a module, and keep upskilling in [AREA, e.g. cloud or AI] through Infosys Springboard. I’d take on whatever stack the business needs along the way. Result: My goal is to be a reliable technical lead inside Infosys who delivers measurable client value and brings newer engineers up with me. I’m looking to build here, not pass through, and I think the training structure gives me room to do that.

Avoid this: Hinting you’ll leave for a product company or going so vague it reads as ‘I haven’t thought about it.’ Show commitment plus a concrete growth path.

9. If your thoughts conflict with a co-worker’s approach on a project, how would you handle the situation?

What they’re really testing: This checks collaboration and conflict-resolution maturity, which matters in Infosys’s team-based delivery environment. Fairness and respectful disagreement are core values here.

Interview Guys Tip: Situation: On [PROJECT], a teammate and I disagreed on [DECISION, e.g. whether to use one database approach or another]. Obstacle: We were both confident, the deadline was close, and digging in would’ve stalled the whole team. Action: Instead of pushing my view louder, I asked him to walk me through his reasoning first, then I laid out mine with the tradeoffs. We agreed on a quick way to test both, timing a small prototype against our actual data. When the numbers favored his approach on [METRIC], I backed it fully. Result: We shipped on time, the decision was based on evidence instead of ego, and the trust from handling it calmly made the rest of the project smoother. I care more about the right outcome than being right.

Avoid this: Framing it as you winning the argument. They’re watching for collaboration, not conquest, and the same calm pattern shows up in leadership questions answered with SOAR.

10. Do you have any questions for us?

What they’re really testing: Candidates who ask nothing read as disengaged. Smart questions about training, project allocation, or the Mysore induction signal genuine enthusiasm and research.

Interview Guys Tip: Situation: I’ve done my homework on Infosys, so I’ve got real questions rather than filler. Obstacle: I know generic questions about perks make a weak impression. Action: I’d ask things like: How does project allocation work after the Mysore training phase, and how early can a fresher start contributing to live client work? How does Infosys support upskilling once I’m on a project, through Springboard or internal certifications? What does success look like in the first six months for someone in [ROLE]? Result: Those answers help me show up ready to add value fast, and they tell me how to grow here deliberately. Asking them also signals I’m thinking about delivering for clients from day one, not just getting through onboarding.

Avoid this: Asking only about salary, leaves, or ‘when do I hear back.’ Lead with questions about training, allocation, and contribution. Save logistics for after an offer.

5 Insider Tips for Acing It

Don’t chase the HireVue that isn’t there

Plenty of candidates burn prep time looking for an Infosys video interview platform. It doesn’t exist in any credible report. Spend that energy on the actual assessment: reasoning, math, verbal, pseudocode, and coding.

Protect every sectional cutoff

A high overall score won’t save you if you bomb verbal or math. Budget your time so every section clears its minimum, and never leave an entire section blank because you ran out of time elsewhere. With no negative marking on the SE track, a reasoned guess always beats a blank.

Move on, don’t marathon one question

Sections are time-boxed and you can’t revisit them. If a puzzle or pseudocode trace is eating your clock, mark your best guess and keep moving. One stubborn question has sunk more candidates than any hard topic.

Make your project interview-proof

List nothing on your resume you can’t defend for five minutes. Rehearse the problem, your specific contribution, the stack, and the outcome until it’s second nature. The AI and cloud awareness they like also shows up in our AI interview questions guide, worth a skim if you mention Topaz or Cobalt.

Communication is scored, so slow down

Infosys weights verbal clarity heavily because the work is client-facing. Cut filler words, speak in structured answers, and finish your sentences. Mumbling or one-word replies drag your HR score down even when your technical answers are right.

Your Technical Setup Checklist

• Use a wired or stable connection for the proctored assessment, since a drop mid-section can cost you time you don’t get back.
• Sit in a quiet, well-lit room with a clear desk, because proctoring software flags movement, extra people, and background noise.
• Close every other tab and app before you start, as tab-switching can be flagged or auto-submit the test on strict drives.
• Keep your webcam and mic on and working if the drive requires live proctoring, and test them a day early, not five minutes before.
• Have your ID ready and your full name matching your registration, since campus and HirePro or Naukri Campus shells verify this at login.
• For the later live technical and HR rounds over Microsoft Teams, check your camera, lighting, and audio in advance and have a neutral background.

What Happens After You Submit

Once you submit, the MCQ and pseudocode sections are scored automatically, and coding answers run against test cases. If you clear the sectional cutoffs, you’re invited to live technical and HR interviews, often the same day or the next day on campus, or over Microsoft Teams for off-campus hires.

Timelines vary. Glassdoor data puts the overall Infosys process around 17 days in India and about 7 days specifically for Systems Engineer hires, drawn from over a thousand submissions on Glassdoor’s Systems Engineer page. Campus drives move faster than off-campus windows, so don’t panic if yours runs long.

If you clear the assessment but don’t hear back after the interview, a short, polite follow-up to your campus coordinator or recruiter is fair. Keep it brief and professional. And remember there are no retakes, and you can’t reapply for six months, so whatever the result, treat the attempt as real practice for the next one.

Frequently Asked Questions

Does Infosys use HireVue or any one-way video interview?

No. An exhaustive search across Reddit, Glassdoor, GeeksforGeeks, Naukri, and prep sites found zero credible reports of Infosys using HireVue, Spark Hire, or any asynchronous video platform. The first screen is a proctored written and coded online assessment, and the later interviews are live with real humans, on campus or over Microsoft Teams.

How many questions are on the Infosys online assessment, and how long is it?

The standard System Engineer track has 54 questions in about 100 minutes: 15 reasoning, 10 math, 20 verbal, 5 pseudocode, and 4 puzzles. The Specialist Programmer and Power Programmer tracks replace the puzzles with 2 to 3 live coding problems and run closer to 180 minutes. There’s no negative marking on the SE track, but sectional cutoffs apply.

Can I retake the Infosys assessment if I fail?

No. There are no retakes, and you can’t reapply to Infosys within six months of a previous application. That’s why time management across sections matters so much: you want to clear every cutoff on the one attempt you get.

Can I skip the online assessment entirely?

Sometimes. InfyTQ certification holders and HackWithInfy finalists may bypass the OA, and experienced lateral hires with roughly two or more years of experience usually go straight to technical L1 and L2 interviews instead of the mass assessment. Most freshers, though, take the full assessment first.

What’s the most common reason strong candidates still get rejected?

Two things. Missing a single sectional cutoff despite a high overall score, and failing the human rounds on soft factors: refusing relocation or a new tech stack, giving a generic ‘why Infosys’ answer, or being unable to explain their own project. Weak verbal communication also drags HR scores down, since the roles are client-facing. If you want more reps on structured answers, our panel interview guide helps you stay composed under follow-up questions.

The Infosys gate isn’t a mysterious video robot, it’s a timed assessment you can prepare for and a set of live questions that reward clarity, honesty, and flexibility. Clear every sectional cutoff, keep moving when a question stalls you, and make sure you can defend your own project cold.

Then in the interview, be specific about why Infosys, say yes to any stack and any city, and communicate like someone a client would trust. Do that and you’re not hoping to pass, you’re expecting to. If the opener still rattles you, run through why tell me about yourself trips people up one more time before you walk in.

Sources and Further Reading

• Infosys Careers Official Page
• InfyTQ Platform (Infosys Training & Qualification)
• Glassdoor Infosys Interview Reviews (India)
• Glassdoor Infosys Interview Reviews (US)
• TechPrep Infosys Interview Process 2026 (detailed breakdown)
• ClearRound Infosys Interview Process 2026 (InfyTQ + All Rounds)
• Unstop Infosys Recruitment Process 2026
• GeeksforGeeks Infosys Interview Experience 2025 (System Engineer)
• Naukri Campus Infosys Systems Engineer Interview Experience