Academic requirements
Marks: 6.0 / 60% floor across 10th, 12th, graduation
Degree: B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT/Maths/Stats/Physics)
Year: Final year + recent grads within ~2 years
Backlogs: None active at final selection
Infosys is a global leader in consulting, technology, and next-generation digital services. Founded in 1981 and headquartered in Bengaluru, Infosys is one of the top recruiters of engineering graduates in India, with offices across 40+ Indian cities and a large global delivery footprint.
Explore: Online Assessment · SE / DSE / SP · Coding Questions · Interview Experience · Preparation Guide · Certifications & Career · Download PDF
Academic requirements
Marks: 6.0 / 60% floor across 10th, 12th, graduation
Degree: B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT/Maths/Stats/Physics)
Year: Final year + recent grads within ~2 years
Backlogs: None active at final selection
Branch & programming
Branches: All eng + science streams on many SE drives
Coding languages: C, C++, Java, Python
Experience: Freshers and up to ~2 years for some entry posts
Minimum CGPA required (candidate-reported): 60% or 6.0 CGPA across 10th, 12th, and graduation. That is the usual Systems Engineer / IRT floor - not a promise that 6.0 alone gets you shortlisted when your campus prints a tighter list. Always verify the drive notice.
Infosys does not publish one universal India cutoff for every IRT, campus, HackWithInfy, and InfyTQ window. Numbers below synthesize campus notices, Careers-portal chatter, and interview write-ups as of August 2026. Your placement email / HackWithInfy FAQ wins.
What that means day to day: a 7.8 CGPA who clears four aptitude sections and leaves coding at zero still fails IRT. A 6.4 who banks one full coding AC and stays above sectional cutoffs moves on. Infosys’s volume-hiring story matches how drives feel - sectional discipline first, then interview fundamentals.
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 6.0 CGPA / 60% at 10th, 12th, and graduation | Average selected often clusters 7.0-7.9; 8.0+ helps premium / HackWithInfy chatter |
| Degree | B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT/Maths/Stats/Physics) | Full-time only |
| Branch | All eng + science streams appear | CS/IT dominate premium tracks; others clear SE when coding holds |
| Year | Final year + recent grads (~2 years) | Entry posts also take up to ~2 years experience in some paths |
| Backlogs | No active at final selection | Some students sit IRT with backlogs but must clear before joining |
| Gaps | Max ~2 years education gap | Have a clean story |
| HackWithInfy | Final-year B.E./B.Tech; all branches; often no hard CGPA floor | Academics still help soft shortlists |
| InfyTQ | Often ~60% 10/12/grad; no backlogs at joining | Batch-year rules change - verify |
| CGPA range | Rough chances | Reality check |
|---|---|---|
| 6.0-6.9 | Eligible for many SE drives | You need sectional + ≥1 coding |
| 7.0-7.9 | Average selected cluster | Matches many SE stories |
| 8.0+ | Stronger premium / SP chatter | Still loses if coding is zero |
Good fit: You can sit a three-hour sectional test without melting, you treat coding as mandatory not optional, and you are open to relocating across Infosys’s 40+ Indian cities. Mysore-training lore still shows up in HR talk - be ready for foundation-program questions.
Harder path: You only grind verbal RC and skip coding; you chase Power Programmer CTC without contest practice; you freeze on “Why Infosys?” after a perfect IRT score. Infosys’s late-stage drops are often relocation, training commitment, or a shaky project story - not a surprise system-design hard problem for SE.
Branch myth: Non-CS students are not “extra lucky” at Infosys - they simply are not auto-rejected on many SE drives. You still need the same sectional + coding bar. Use the open-branch policy as permission to attempt, not as a free pass past Pseudo and Coding.
IRT with backlogs: some students report being allowed to attempt IRT while a backlog is active, but final selection still expects clearance before joining. Read your notice twice before assuming leniency.
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch IRT window, PPT, college CGPA list | Sectional + coding bar |
| Careers portal (IRT) | Open windows; score often valid 1 year | Same IRT shape |
| HackWithInfy | Contest rounds before interviews | Medium-hard DSA; SP/DSE outcomes |
| InfyTQ | Cert exam sections; priority interviews | Still expect coding + SQL depth |
Campus path (typical): placement cell → PPT → IRT on campus or online → tech + HR → offer. Season-aligned.
Off-campus path (typical): Careers portal registration → IRT → interviews when shortlisted. Retakes may exist with a waiting period - check the portal, do not assume unlimited retries.
Off-campus does not mean easier coding. It often means more applicants fighting the same 180-minute filter. If your CGPA sits near 6.0, spend energy on timed IRT mocks - not on hunting a mythical lower cutoff blog post.
Yes for eligibility on many SE drives. No as a substitute for IRT. Infosys’s quiet filter is sectional cutoffs + ≥1 coding solve before anyone cares about your CGPA story. Put one honest project on the resume and be ready to explain it in 30-45 minutes.
Gap years and backlogs: a gap over about two years is the usual hard stop students report. Active backlogs at final selection are a common reject; some notices let you attempt IRT first - still plan to clear before joining. Full-time degrees only.
Infosys Certifications / Springboard: Lex and Springboard help after joining more than they replace IRT prep. Optional reading: certifications and InfyTQ notes there.
Download 2026 Infosys placement papers
2026 pattern in detail
2025 placement papers
2024 placement papers
Previous year question papers
Infosys papers are simulators for IRT stamina, not leaked live exams. Themes repeat more than exact clones. If you can finish a 2024 IRT pack under 180 minutes with every sectional above cutoff, a 2026 test still feels familiar even when the RC topic is new.
| Round (typical) | What to practice |
|---|---|
| Reasoning / Quant / Verbal | Series, DI, P&L, RC, grammar - the 70/100 aptitude block |
| Pseudo Code | Output tracing in C/C++/Java/Python style |
| Coding | 2 problems; clear ≥1 |
| Interviews | OOPs, SQL, OS, projects, Why Infosys |
How to use a paper: run the full 180 minutes; mark every sectional score; rewrite any coding answer that fails edge cases; log whether you failed on speed vs concept. Three reviewed IRTs beat ten skimmed PDFs. When essay-style verbal appears in a pack, write one timed paragraph - reading someone else’s essay does not build the muscle.
| Theme that shows up | What to drill next |
|---|---|
| Arrays / strings | Reverse, palindrome, frequency maps, two pointers |
| Sorting / searching | Binary search templates; complexity talk for interviews |
| Basic DS | Stack/queue via arrays; simple linked-list reverse |
| Pseudo output | Nested loops, short-circuit conditionals, off-by-one |
Verbal RC note: passages of roughly 300-500 words with 2-3 passages and 4-6 questions each show up in pattern guides. Skim for main idea first; do not reread the whole passage for every question.
Cutoff trend colour (student tables): overall ~60-65% across recent years with coding ≥1 problem as the constant; 2021/2023 rows sometimes sit a notch lower on sectionals. Use the trend as a mock target, not as Infosys HR policy.
If you “finish aptitude perfectly” and open coding with 25 minutes left, you are practicing the fail mode Infosys rewards least.
Infosys runs campus drives, Careers-portal IRT, HackWithInfy, and InfyTQ pathways. The technical idea is the same: clear a timed filter, then defend fundamentals in interviews. Premium CTC usually needs contest- or cert-track depth.
Campus recruitment
Placement cell lists → PPT → batch IRT → tech + HR. Season-aligned with college calendars. Same sectional bar as off-campus.
Careers portal / IRT
Register on Infosys Careers. IRT scores are often cited as valid for 1 year and usable for Infosys + some partner hiring. Retake rules vary - check the portal.
HackWithInfy / InfyTQ
Contest or certification path into DSE/SP interviews. See HackWithInfy and certifications.
Infosys Recruitment Test (IRT) - ~180 minutes
Platform: Infosys proprietary / online proctored; English. No negative marking in most reports - attempt everything, but do not burn coding time.
| Section | Questions | Marks | Time (approx.) | Difficulty | Approx cutoff |
|---|---|---|---|---|---|
| Reasoning Ability | 15-18 | 25 | 25-30 min | Medium | ~60% |
| Quantitative Ability | 15-18 | 25 | 30-35 min | Medium-Hard | ~60% |
| Verbal Ability | 15-18 | 20 | 20-25 min | Easy-Medium | ~50% |
| Pseudo Code | 5-7 | 10 | 15-20 min | Medium | ~50% |
| Coding | 2 | 20 | 60-70 min | Medium-Hard | ≥1 problem |
Total: ~65-70 questions, 100 marks, 180 minutes. Aptitude block (R+Q+V) is 70/100. Coding often 10 marks per problem.
Candidate-reported clear rate for IRT sits around ~20%. You must clear sectional and overall (~60-65% overall; safe mock target 65-70%).
Example fail mode students hate: R 16/25, Q 15/25, V 11/20, Pseudo 6/10, Coding 1 solve → 48/100 - sectionals may look “okay” while overall still fails. Do not celebrate one strong section.
Time boxing: protect coding. If quant is eating the clock, skip after 90-120 seconds. Section switching is often allowed; buffer ~10 minutes for review if your mock data supports it.
Technical Interview - 30-45 minutes (virtual or onsite)
Programming, DBMS/SQL, OS, OOPs, networking, live coding (reverse linked list, palindrome, factorial), and project deep-dive. Roughly ~70% of IRT qualifiers clear tech in student-reported funnels.
Expect “pointers vs references?”, “normalization?”, “overloading vs overriding?”, and “explain your project end to end.” If you cannot explain your own resume bullet, that is a red flag.
HR Interview - 20-30 minutes
Why Infosys?, relocation across cities, strengths/weaknesses, 5-year plan, training/foundation questions. Around ~90% of tech-clear candidates get offers when location and commitment answers are clean. Overall selection from applicants often lands around ~12-15% in student stats pages.
| Round | Duration | Problems | Selection notes |
|---|---|---|---|
| Prelims | ~3h | 3 (Easy/Med/Hard) | Top → Semis; C/C++/Java/Python; HackerEarth/Infosys |
| Semifinals | 3-4h | 4-5 Med-Hard | Top ~100-200 often cited |
| Finals | 4-5h | 5-6 Hard-VH | Top ~50-100; onsite/virtual |
| Interviews | Varies | Live coding + CS | SP/PP or DSE outcomes |
Typical calendar students report: Reg Mar-Apr → Prelims May-Jun → Semis Jun-Jul → Finals Jul-Aug → Interviews Aug-Sep. Some certifications pages describe a simpler 3-round contest shape - trust the year’s official HackWithInfy brief.
2025 SP colour: 3-hour / 3-question coding on 12 July 2025; interview mail 12 September asking for a 2-slide PPT (self + career aspirations); live 40-min coding opener then DSA/SQL/OOPs/OS/DBMS/projects; SP selection via TPO 25 September 2025 (GeeksforGeeks write-up).
DSE lag: one Medium write-up described an onsite coding interview 6 January 2026 (~6 months after the July 2025 qualifier) with 1 of 2 DSA in 45 min. SP interviews often happen months earlier than DSE - budget emotional patience.
| Section | Q | Duration |
|---|---|---|
| Programming MCQs | 10 | 25 min |
| Programming Hands-on | 2 | 60 min |
| Advanced Programming (SP/PP track) | 2 | 90 min |
| SQL | 5 | 15 min |
Strong InfyTQ performance is commonly tied to priority interviews and higher bands versus a plain SE clear - verify current-year rules.
| Phase | Duration | What happens |
|---|---|---|
| IRT | 1 day | Aptitude + pseudo + coding |
| IRT results | Within ~1 week (often) | Shortlist mail |
| Technical | 1-2 weeks | Fundamentals + coding |
| HR | 2-3 days | Fit / location / joining |
| Offer | ~1 week after final selection | Letter + background checks |
Total: usually 2-4 weeks once IRT is done. HackWithInfy can stretch months from Prelims to interview.
Fold this into your practice plan - it used to live as hollow FAQ dumps and belongs here instead:
If you only remember three numbers: 180 minutes, clear every sectional plus overall ~60-65%, and finish ≥1 coding problem.
| Track | How you usually enter | What interviews feel like |
|---|---|---|
| SE | IRT clear (≥1 coding) | Fundamentals + basic coding |
| DSE | Stronger coding / InfyTQ / HackWithInfy DSE | Medium DSA + deeper CS |
| SP / Power Programmer | HackWithInfy finals / top coding | Medium-hard DSA + contest stamina |
Deep dives: SE · DSE · SP · comparison.
Campus vs contest planning tip: if your placement season is crowded, sit IRT early so a 1-year score validity (when applicable) covers later interview windows - and run HackWithInfy in parallel only if you can protect contest practice hours. Trying both without a calendar usually means mediocre IRT sectionals and a weak Prelims day.
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
If a Infosys invite is 3-8 weeks out, treat this hub as the map and the nested pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Infosys sits around ₹3.6 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Infosys eligibility for freshers 2026 is candidate-reported: typically 60% or 6.0+ CGPA across 10th, 12th, and graduation; B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT/Maths/Stats/Physics and related); final-year students and recent graduates within about 2 years; no active backlogs at final selection; max ~2 years education gap; full-time degrees; Indian citizens for India roles. HackWithInfy often has no hard CGPA floor.
What you are training for: Standard Systems Engineer path: Infosys Recruitment Test (IRT, ~180 min aptitude + pseudo + coding) → Technical Interview (30-45 min) → HR (20-30 min). Premium paths use HackWithInfy or InfyTQ with deeper coding. Campus and Careers-portal timelines usually land in about 2-4 weeks from IRT to offer; HackWithInfy interview lag can be longer.
Short version of the prep split: For IRT: split roughly 40% aptitude (reasoning/quant/verbal), 30% coding (clear ≥1 of 2), 20% pseudo + CS fundamentals, 10% tech/HR. Practice 10-15 timed IRT papers (20-25 if you want buffer). For SP/DSE, add contest stamina via HackWithInfy-style sets.
Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the Infosys previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Infosys drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Infosys usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Infosys?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Infosys-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the Infosys story (eligibility, rounds, salary). Use those pages for reps. If a card 404s on your campus mirror, the explore links at the top of this page are the same destinations.
If you do one thing after reading this: schedule three timed Infosys papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Infosys papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Infosys-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed Infosys paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Infosys. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Infosys, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Infosys mistakes, you are collecting content, not preparing.
Sit one more mixed Infosys set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Figures below are candidate-reported as of August 2026. Role labels and bands conflict across pages - offer letters win.
| Role | Band (candidate-reported) | Notes |
|---|---|---|
| Systems Engineer | ₹3.6 LPA hub table; many year/HR notes ₹4-4.5 LPA; Rohan offer ₹4.2 LPA | Volume SE path via IRT |
| DSE | ₹6.5-9.5 LPA | Hub range; InfyTQ “Digital Specialist” sometimes cited ~₹5 LPA |
| Specialist Programmer (SP) | ₹9-12 LPA | Often ≈ Power Programmer in conversation |
| Power Programmer (FAQ) | ₹10-12 LPA | Priya / Ankit stories ₹10 LPA |
| Senior Systems Engineer | ~₹6-7 LPA (1-2 yrs / off-campus) | Arjun ₹6 LPA |
| QA / Test | ~₹3-4.5 LPA | Separate track |
| Business Analyst | ~₹5-8 LPA | |
| IT Analyst | ~₹6-10 LPA |
InfyTQ / certifications pages also quote Digital Specialist ~₹5 LPA, Power Programmer ~₹6.5 LPA, Specialist Programmer ~₹9.5 LPA, and HackWithInfy Grand Finalist ~₹9.5 LPA + ₹1 Lakh prize - preserve those as alternate mappings, not “corrections” of the hub table.
Foundation / Mysore-style training narratives, Infosys Lex (1000+ internal courses), Springboard, roughly 8-12% annual increment chatter, and promotions every ~2-3 years in comparison notes. Relocation across many Indian cities is expected - HR will ask.
How to read the SE band: ₹3.6 LPA appears on hub/certification tables; ₹4-4.5 LPA appears on year pages, comparison tables, and HR sample answers; candidate Rohan reported ₹4.2 LPA. Treat that spread as candidate-reported range, not a contradiction you must “pick.” Exact splits vary by year and letter.
How to read SP/PP: hub FAQ ~₹10-12 LPA; SP card ~₹9-12 LPA; InfyTQ SP ~₹9.5 LPA; some InfyTQ PP rows ~₹6.5 LPA for “top performers.” Trust the offer letter role name. SP ≈ Power Programmer in conversation - HR may use either label.
Peer context: TCS NQT fresher bands often cited near ₹3.5-4 LPA; Wipro volume bands often lower/flat depending on year; Infosys’s differentiator for ambitious students is the HackWithInfy / InfyTQ ladder, not a dramatically higher SE floor.
Know SE vs DSE vs SP bands, ask fixed vs variable, and clarify joining vs finals. One calm clarifying question beats aggressive negotiation with no market anchor. Do not negotiate SP numbers on an SE offer letter.
Net for 2026 prep: do not wait for a rumor that coding is optional or that sectionals are gone. Double down on timed 180-minute mocks, one reliable coding AC, and a clean Why Infosys / relocation answer. Process length and contest calendars matter for planning your semester; they do not replace fundamentals.
Also expect more practical wording in coding prompts and more cloud/AI vocabulary in interviews than older seniors remember. The IRT bar does not drop because the wording modernizes - only the surface topics do. If your college finally gets a campus Infosys drive after a quiet year, treat it as a real shot: reserved seats help, the sectional math does not soften.
Year-page hiring-volume chatter (15,000 campus revival vs 55,000+ expected hires on the same 2025 page) is context for “Infosys is hiring,” not a personal probability. Your job is still 180 minutes, five sections, and ≥1 coding solve.
Standard SE path: IRT (~180 min) → Technical (30-45 min) → HR (20-30 min). Premium paths use HackWithInfy or InfyTQ before deeper interviews. Campus/Careers timelines often land in 2-4 weeks after IRT; HackWithInfy can stretch longer.
Most SE loops report three stages after application (IRT + tech + HR). HackWithInfy adds Prelims/Semis/Finals before interviews. Count the mailer.
Yes. Free Infosys placement papers PDF and 2024-2026 IRT-style practice are on placementpapers.app - trainers with solutions, not leaked live papers. Start with the 2026 PDF or the archive.
Commonly ~180 minutes, ~65-70 questions, 100 marks: Reasoning, Quant, Verbal, Pseudo Code, and 2 coding problems. No negative marking. Sectional cutoffs plus overall ~60-65%. Languages: C, C++, Java, Python. Details: IRT exam pattern.
Candidate-reported: 60% / 6.0 CGPA across 10th, 12th, graduation; listed degrees/branches; final year or recent grads within ~2 years; no active backlogs at final selection; max ~2 years gap; full-time; Indian citizens for India roles. HackWithInfy often has no hard CGPA floor. Verify your notice.
SE often cited ~₹3.6 LPA on hub tables and ₹4-4.5 LPA in many year/HR notes (candidate offer example ₹4.2 LPA). DSE ~₹6.5-9.5 LPA. SP/PP often ₹9-12 LPA (stories at ₹10 LPA). Offer letter wins.
SE = volume IRT path. DSE = stronger coding / InfyTQ-HackWithInfy digital track. SP (Specialist Programmer, often called Power Programmer) = selective top coding track. See SE, DSE, SP.
Split ~40% aptitude, 30% coding (≥1 AC), 20% pseudo+CS, 10% interview. Practice 10-15 timed IRTs (20-25 for buffer). Details: preparation guide.
C, C++, Java, Python for IRT and HackWithInfy. Pick one early. Do not switch the week of the test.
Infosys’s student coding competition path: Prelims → Semis → Finals → interviews for SP/PP-style roles. Final-year B.E./B.Tech, all branches; often no hard CGPA requirement. Guide: HackWithInfy.
Certification / hiring pathway with programming MCQs, hands-on coding, optional advanced programming, and SQL. Strong performance can mean priority interviews and higher bands. See certifications.
Many student reports say IRT scores remain valid for about 1 year and can support Infosys + some partner hiring. Confirm on the Careers portal for your attempt - policies can change.
All three are large services paths. Infosys leans IRT sectionals + coding. TCS is NQT (often cited with longer score validity). Wipro Elite/NLTH-style tests are shorter in some comparisons (~120 min). Shared aptitude helps; specialize mocks per company. Deep dive: comparison and TCS vs Infosys vs Wipro.
Prefer zero active backlogs at final selection. Some students sit IRT with backlogs if the notice allows, but you must clear them before joining. Do not treat backlog leniency as a free pass past coding.
Bank ≥1 full coding solve and watch every sectional cutoff. Infosys rejects “aptitude hero, coding zero” every year. If you want SP/DSE money, treat HackWithInfy like a real contest season.
Start with Infosys interview experience on placementpapers.app, then cross-check recent community write-ups. Patterns shift by year - use them as maps, not scripts.
Usually yes - Infosys has offices in 40+ Indian cities and HR commonly checks relocation willingness and foundation-training logistics. Be honest early.
It meets the commonly reported minimum for many SE drives. Average selected candidates often cluster higher (7.0-7.9). At 6.0 you need especially clean sectionals and a reliable coding AC - CGPA alone never clears IRT.
Minimum 10-15 timed full IRTs; 20-25 if you want buffer. Quality beats volume - review every miss. Simulate the real 180-minute block, not 40-minute aptitude-only snippets.
Roughly 50-60% on sectionals depending on the section, 60-65% overall, and ≥1 coding solve. Safe mock target ~65-70% overall. Not official Infosys numbers - use them as practice goals.
Profile: B.Tech CSE, Tier-2, CGPA 7.5. IRT 68%, 1 coding solve, call in ~1 week. Tech 45 min: pointers, reverse linked list, stack/queue, normalization, SQL 2nd highest + joins, inheritance, overloading vs overriding, project, palindrome in C. HR 25 min: Why Infosys, relocate, strengths, 5 years, training questions. Selected SE ₹4.2 LPA.
Profile: B.Tech IT, Tier-1, CGPA 8.2, HackWithInfy finalist. IRT 72%, both coding solves. Tech 50 min: JVM, ArrayList vs LinkedList, collections, stack via arrays, sorting complexities, binary search, hash vs tree, e-commerce schema, indexing, complex SQL, URL shortener, load balancing. Selected PP ₹10 LPA.
Profile: B.Tech ECE 2023, 1 year exp, CGPA 7.8. IRT 65%, 1 coding. Tech 40 min: OOPs, factorial recursive/iterative, process vs thread, TCP/IP, ACID, prior work, prime + optimize. Selected Senior SE ₹6 LPA.
What hurt other candidates: opening coding too late; missing one sectional by a few marks; treating HR as a formality; claiming SP prep while only solving easy arrays; freezing on “explain your project without buzzwords.”
Common question families candidates keep listing:
What to steal: protect the coding window; log sectional scores; rehearse relocation; if you chase SP, train contest stamina months ahead. Do not treat one Medium/GfG post as a fixed paper template - use it as a vibe check, then return to timed mocks on placementpapers.app. More narratives: interview experience.
Emotional budget: IRT week is a three-hour focus problem; HackWithInfy season is a multi-month stamina problem. Do not confuse them. If you only have four weeks, clear SE via IRT first, then decide whether SP prep is realistic for the next cycle.