Coding questions
How to Prepare for Infosys
Infosys IRT is a long aptitude-heavy paper with pseudo-code and 2 coding problems. Clear sections first. HackWithInfy is a separate harder coding track for Power Programmer-style roles.
What Infosys actually tests
First round: Infosys IRT (+ HackWithInfy for premium tracks)
Time split that matches how candidates report outcomes (not a marketing pie chart):
- Aptitude 40%
- Coding basics 30%
- Core CS 20%
- HR 10%
Patterns are from student reports and vary by role and drive. Trust your college placement email over blog folklore.
Hiring flow you should prep for
| Stage | Time | What they check |
|---|---|---|
| IRT | ~180 min | Reasoning, quant, verbal, pseudo-code, coding |
| Technical interview | 30-45 min | CS fundamentals + projects |
| HR | 20-30 min | Communication and fit |
Time allocation
- Practice Infosys IRT previous year papers with solutions
- Focus on aptitude sections (Reasoning, Quantitative, Verbal) which carry 70 marks
- Master coding basics - solve at least 1 coding problem correctly
- Practice pseudo code questions in C/C++/Java/Python
- Review core computer science subjects (DBMS, OS, OOPs, Networking)
- Practice mock IRT tests to improve time management
Daily loop (90-120 minutes)
- One timed block that matches Infosys’s first round (aptitude + coding OA)
- Log misses: topic + why you failed (speed, concept, carelessness)
- Re-solve yesterday’s misses cold
- Twice a week: 10 minutes of resume/project narration out loud
6-8 week service-company plan
| Week | Focus | Exit criteria |
|---|---|---|
| 1-2 | Quant + reasoning speed | 2 full aptitude mocks, >70% accuracy |
| 3-4 | Verbal + programming logic / pseudo-code | Comfortable under sectional timers |
| 5-6 | Coding basics + CS fundamentals | 1-2 coding problems solvable cleanly |
| 7-8 | Full mocks + interview answers | Sectional cutoffs cleared in mocks |
Round-by-round strategy
Online Assessment
- Sectional cutoffs matter more than a hero score in one section
- Quant/reasoning: skip time sinks after 90-120 seconds
- Verbal: accuracy over vocabulary flex
- Coding/pseudo: get one clean full solve before polishing a second
Technical interview
- OOPs, DBMS, OS, Networks - definitions plus one example each
- Be ready to write a simple program on paper/editor
- Project explanation: problem → your work → result (numbers if any)
HR
- Why Infosys, gap years, location preference, bond/notice if asked
- Speak clearly; service HR rounds fail quiet candidates more than imperfect ones
Infosys-specific drills
- Sectional timed aptitude (aim 70%+ safe)
- Pseudo-code tracing daily
- At least one full coding solve under IRT constraints
- If targeting HackWithInfy: contest-style DSA separately
Topic checklist
- Aptitude speed with sectional accuracy
- One coding language for basic problems
- OOPs, DBMS, OS one-liners you can expand
- HR answers: why company, relocation, gaps
- Pseudo-code / output prediction
- Essay or communication modules when present
- Full-length mock every other day
- Light revision only - no new rabbit holes
- Sleep, ID proofs, machine/network checklist for test day
Final stretch
30 days out: 3+ full Infosys-pattern mocks per week; build an error log by section.
7 days out: one mock every other day; revise only error-log topics; rehearse HR answers aloud.
Day before: light revision, no all-nighters - sectional exams punish fatigue.
Common mistakes for Infosys aspirants
- Missing sectional cutoffs or zero coding solves on IRT - fix this first
- Preparing only interviews while failing Infosys’s first round
- Collecting notes without timed mocks
- Listing five frameworks on the resume and defending none
- Changing language/stack one week before the drive
- Grinding LeetCode hard while failing aptitude cutoffs
Practice on this site
- Infosys aptitude / mock quiz
- Infosys coding questions
- Infosys interview experience
- Infosys previous year papers
- Infosys 2026 guide
- Infosys hub
- PDF: Infosys Placement Papers PDF (2026)

