The Infosys hiring process is one of the most structured and well-documented recruitment pipelines in the Indian IT industry. Whether you are a final-year engineering student waiting for campus placements, a fresh graduate searching for off-campus opportunities, or an experienced professional considering a lateral move, understanding how Infosys evaluates and selects candidates is the single most important step you can take before entering the process.

Infosys Hiring Process Guide

Infosys hires at scale. The company consistently ranks among the top employers for engineering graduates in India and recruits tens of thousands of candidates every cycle across multiple hiring tracks. That scale means the process is rigorous, and it also means that being well-prepared gives you a measurable advantage over the majority of applicants who walk in without a clear strategy.

This guide covers everything you need to know, from eligibility criteria and registration to the online assessment, technical interviews, HR rounds, offer letter timelines, and the onboarding experience. It also covers the full range of hiring scenarios, including campus placements, off-campus drives, lateral hiring for experienced professionals, and referral-based hiring. Every section goes beyond surface-level summaries to give you the depth, specificity, and strategic insight you need to navigate each stage with confidence.

Table of Contents

  1. Understanding the Infosys Hiring Ecosystem
  2. Eligibility Criteria
  3. The Four Major Hiring Tracks
  4. Registration and Application Process
  5. The Infosys Online Assessment: Complete Breakdown
  6. Technical Interview Rounds
  7. The HR Interview Round
  8. Offer Letter Timeline and What to Expect
  9. Infosys Onboarding Process
  10. Common Mistakes Candidates Make at Every Stage
  11. Stage-by-Stage Preparation Strategy
  12. Frequently Asked Questions

Understanding the Infosys Hiring Ecosystem

Before getting into the mechanics of each stage, it helps to understand the broader context in which Infosys hiring operates. Infosys is not a single-track recruiter. The company uses multiple parallel pipelines to bring talent in, and the experience of a fresher going through campus placement is structurally quite different from the experience of a lateral hire with five years of experience at another IT services firm.

Infosys primarily recruits for the Systems Engineer (SE) role at the entry level. This is the standard designation for freshers, and it represents the largest volume of hiring that the company does. Above this, there are premium tracks such as the Digital Specialist Engineer (DSE) and the Power Programmer (PP) designation, which are typically accessed through competitive routes like HackWithInfy or InfyTQ performance.

The hiring process for the SE role, which is what most candidates go through, follows a consistent structure regardless of the specific entry point. There is an online assessment, followed by one or more interview rounds, followed by an HR discussion. The specifics of what is tested in each stage, how the evaluation is weighted, and what the interviewers are looking for vary depending on whether the candidate is a fresher, a lateral hire, or someone who has come in through a special hiring program.

Understanding this ecosystem matters because it changes how you should prepare. A fresher preparing for campus placement needs to focus almost entirely on the online assessment and on building a strong foundation in the fundamentals of their chosen technology stack. An experienced candidate going through lateral hiring needs to be ready for deeper conversations about past project work, domain expertise, and behavioral competencies. This guide addresses both, with clear signposting wherever the advice diverges based on hiring track.

Eligibility Criteria

Infosys has specific eligibility criteria that candidates must meet before they can participate in any hiring drive. These criteria apply across all tracks, though the specifics differ slightly between fresher and experienced hiring.

For Freshers (Systems Engineer and equivalent roles):

The core academic eligibility requirement is a minimum of 60 percent aggregate marks or an equivalent CGPA across the 10th standard, 12th standard (or equivalent diploma), and the undergraduate degree. Some drives specify this as 6.0 CGPA on a 10-point scale. The rule is consistent: there is no rounding. A 59.9 percent aggregate does not qualify as 60 percent under Infosys norms, and this is applied strictly.

The eligible educational backgrounds include B.E., B.Tech, M.E., M.Tech, MCA (from a 3-year bachelor’s program), and M.Sc. (Computer Science or IT streams). Some drives also accept BCA candidates for specific roles. Infosys does not have a branch restriction as a hard rule, meaning students from non-CS streams like Mechanical, Civil, or Electrical Engineering are eligible as long as they meet the aggregate cutoff. In practice, however, the online assessment and technical interview do evaluate fundamental CS and programming knowledge, so non-CS students need to invest more in preparation.

Infosys also imposes an education gap restriction. Candidates must have no more than one year of gap in their academic history. This means a gap year between 12th and undergraduate, or between undergraduate and the date of application, should not exceed 12 months. Gaps due to health reasons or other documented circumstances are sometimes considered on a case-by-case basis, but candidates should be prepared to explain any gap clearly during the HR round.

The age requirement for fresher roles is typically up to 28 years at the time of application, though this varies by drive and may extend up to 30 in some cases.

For Lateral Hires (Experienced Professionals):

For lateral hiring, the academic eligibility broadly mirrors the fresher criteria, though the primary focus shifts to professional experience and skill alignment. Candidates with 2 to 12 years of relevant experience are typically the target for most lateral openings. Specific roles may require domain expertise in areas like Oracle, SAP, Java, .NET, cloud platforms, data engineering, testing, or project management.

Infosys does hire candidates who do not have traditional academic backgrounds if their professional experience and skill set are compelling enough, but this tends to apply to niche technical roles rather than general lateral openings.

Backlogs:

Active backlogs (ongoing failures in academic subjects) generally disqualify a candidate from fresher drives. Candidates with cleared backlogs (all subjects eventually passed but not in the first attempt) may be eligible depending on the specific drive, but must disclose this accurately during registration. Providing false information about backlogs is treated as serious academic dishonesty and can result in permanent disqualification if discovered.

The Four Major Hiring Tracks

Infosys recruits through four primary pathways. Each has its own mechanics, timeline, and candidate experience.

Campus Placement

Campus placement is the dominant mode of fresher hiring at Infosys. The company conducts campus drives at engineering colleges across India, and the volume of hiring through this channel is substantial. Campus placements at Infosys follow a clear and predictable structure, which makes them one of the more navigable placement processes for students who are well-prepared.

The college receives a Pre-Placement Talk (PPT) before the actual drive. This is a formal presentation by Infosys representatives who walk students through the company, the role, the compensation package, and the process. The PPT is not just a formality. It is an opportunity to understand what Infosys is communicating as its value proposition to new hires, and attentive candidates sometimes pick up signals about what the interviewers will emphasize.

After the PPT, the online assessment is conducted, usually on the same day or within a day or two. Shortlisted candidates then move to the interview rounds, which may be conducted on campus or at a designated assessment center depending on the college’s arrangement with Infosys. The typical campus placement process at Infosys concludes within one to three days.

One important dynamic in campus hiring is the role of the college’s relationship with Infosys. Tier-1 institutions often have more favorable arrangements, including guaranteed interview slots for all eligible students and sometimes a higher number of offers relative to total students placed. For students at Tier-2 or Tier-3 colleges, the competition at the assessment stage is proportionally higher, but the interview process, once you get there, is identical.

Making the Most of the Pre-Placement Talk:

Candidates who attend the Pre-Placement Talk and pay close attention often pick up useful signals. The Infosys representative presenting the PPT will typically discuss the company’s focus areas for hiring, the kinds of projects freshers get assigned to, the training program structure, and any specific skills or qualities they are emphasizing for that cycle. This information directly informs how you should position yourself in the interview round.

Take notes during the PPT. After the session, look up anything mentioned that you were not already familiar with. If the PPT mentions a specific technology practice, service line, or recent business direction, knowing about it before the interview gives you material for compelling answers to questions like “why do you want to join Infosys?” or “what aspects of Infosys’s work interest you?”

Timing and Batch Dynamics in Campus Drives:

Campus drives at top-tier institutions typically happen earlier in the academic calendar than drives at Tier-2 or Tier-3 colleges. This means that students at Tier-1 colleges who receive Infosys offers early in their final year can potentially use the secured offer as a psychological baseline while continuing to pursue other opportunities. Students at institutions where drives happen later in the year may face more time pressure.

The batch dynamics of a campus drive also matter. In any given batch of students sitting for the assessment, the curve of preparation varies enormously. Well-prepared students in an average batch tend to stand out more noticeably than they would in a highly competitive batch. The practical implication is that the absolute standard of your preparation matters less than whether you are among the best-prepared in your specific batch, though maintaining high absolute standards is always the safest approach.

Off-Campus Hiring

Off-campus hiring at Infosys operates primarily through two channels: the Infosys careers portal (infosys.com/careers) and the InfyTQ platform. Freshers who were not placed through campus drives, or who graduated some time ago and are looking for opportunities, typically apply through these routes.

The off-campus process broadly mirrors the campus process in terms of its stages. There is an online application, an online assessment (often taken remotely through a proctored platform), and then interview rounds. The key difference in off-campus hiring is that the filtering is more aggressive at the assessment stage because the pool of applicants is far larger and less pre-screened than a campus batch.

For off-campus freshers, the InfyTQ platform has become a particularly relevant entry point. InfyTQ allows candidates to take Infosys-aligned certification courses in Python, Data Structures, and DBMS, and then appear for an assessment. Strong performance on InfyTQ can lead to a direct interview call from Infosys, bypassing the standard online assessment stage.

The Infosys off-campus hiring cycle is not as predictable as campus placements in terms of timing. Application windows open and close based on the company’s hiring needs, and it is common for the process to take longer, sometimes several months from application to offer letter.

Lateral Hiring for Experienced Professionals

Lateral hiring at Infosys typically targets professionals with two or more years of experience who bring a specific technical skill set or domain knowledge. The positions filled through lateral hiring range from mid-level individual contributor roles to team lead and project management positions.

The lateral hiring process starts with either a direct application on the Infosys careers portal or through a recruiter. Unlike fresher hiring, lateral candidates are not required to go through the standard online aptitude test. Instead, the evaluation focuses on technical interviews that are aligned with the specific role and skill stack the candidate brings.

A lateral hire at Infosys can expect one to three rounds of technical interviews followed by an HR round. In technical rounds, the conversation will revolve around the candidate’s prior project experience, the technologies used, design decisions made, and how problems were solved. Interviewers for lateral roles are typically senior technical staff who can evaluate depth of knowledge rather than just familiarity with concepts.

The HR round for lateral hires covers salary negotiation, notice period and joining timeline, and cultural fit. Salary negotiation in lateral hiring at Infosys works differently from the fixed-package structure of fresher hiring. There is more room for discussion, particularly for candidates with niche skills or leadership experience, though Infosys has a reputation for being conservative in its lateral package increments.

Background verification is a critical component of lateral hiring. Infosys conducts thorough background checks including verification of employment history, educational qualifications, and in some cases, criminal background checks. Discrepancies in documents or experience claims are taken seriously and can result in offer withdrawal even after the process is complete.

Referral-Based Hiring

Employee referrals are a meaningful hiring channel at Infosys, particularly for experienced roles. Infosys employees can refer candidates through an internal referral portal, and referred candidates generally receive expedited processing, meaning their application is reviewed more quickly than a cold application.

However, it is important to understand what a referral does and does not do. A referral at Infosys does not guarantee an interview, and it certainly does not guarantee an offer. What it does is ensure that the application receives attention from a recruiter rather than potentially sitting in a queue. The candidate still needs to clear the same assessment and interview stages as any other applicant.

The person making the referral at Infosys typically receives a referral bonus if the referred candidate is hired and completes a defined period of service. This creates an incentive for employees to refer strong candidates, but candidates should not assume that the referring employee has significant influence over the hiring decision itself.

How to Find and Use a Referral Effectively:

The most effective approach to finding a referral is through your professional network: LinkedIn connections who currently work at Infosys, college seniors who joined the company, or professional acquaintances from previous internships or industry events. When reaching out to someone for a referral, be specific and professional. Share your resume, mention the specific role you are targeting, and explain why you believe you are a good fit. An employee who submits a referral is putting their professional reputation behind you to some degree, so make it easy for them to feel confident about the referral by presenting yourself well from the first interaction.

A referral is most valuable as an entry accelerator rather than as a substantive advantage in the evaluation itself. Use the potentially faster processing time that a referral provides to ensure you are maximally prepared for the assessment and interviews. The worst outcome is a quick assessment invitation that you are not ready for because you expected the referral to carry you through.

When Referrals Do Not Lead to Interviews:

Sometimes, even with a referral submitted, the application does not progress. This can happen if the role has already been filled, if the volume of applications was very high and the initial screening filtered out your profile for a technical eligibility reason, or if there is a hiring freeze in effect for that particular business unit. In these cases, the employee who referred you may not have visibility into exactly why the application did not advance. Follow up professionally with the referrer to ask if they received any feedback, and also track your application status on the careers portal directly.

Registration and Application Process

For Campus Placement:

The registration process for campus placements is managed through the college’s placement cell. Students typically register on the college portal or through a form shared by the placement team, and the placement cell forwards the registered list to Infosys. Students should ensure that all academic details submitted at this stage are accurate, including CGPA, backlog status, and personal information, because this data feeds into the eligibility verification that happens before the offer letter is issued.

For Off-Campus via Infosys Careers Portal:

Candidates should create an account on the Infosys careers portal and complete their profile in full before applying to any open positions. An incomplete profile reduces the chances of clearing the initial screening. The profile should include accurate academic details, work experience (if any), technical skills, and correct contact information.

After submitting the application, there is typically a screening phase where the submitted information is reviewed for basic eligibility. Candidates who pass this screening receive an email with a link to the online assessment. The turnaround between application and assessment call can range from a few days to several weeks depending on the volume of applicants and Infosys’s current hiring pace.

For InfyTQ:

Registration on InfyTQ (infytq.infosys.com) requires a college email ID or a verified personal email. After registration, candidates access the learning modules and certifications. The assessment that qualifies candidates for an Infosys interview call is separate from the certification and must be specifically attempted after completing the relevant courses.

For Lateral Hiring:

Lateral candidates apply through the Infosys careers portal, searching for roles that match their skill profile. After applying, the application is reviewed by a recruiter. The recruiter may reach out directly for an initial screening call before scheduling technical interviews. Candidates should ensure their resume is well-structured and clearly highlights relevant experience, technology stacks, and project outcomes.

The Infosys Online Assessment: Complete Breakdown

The online assessment is the first major filter in the Infosys hiring process for freshers. It is conducted through a proctored online platform and consists of multiple sections evaluated independently. Understanding the structure, the time constraints, and the specific skills tested in each section is essential for performing well.

The current standard assessment format used by Infosys consists of the following sections:

  • Quantitative Aptitude
  • Logical Reasoning
  • Verbal Ability
  • Pseudocode and Programming

There is sectional time-limiting in many versions of this assessment, meaning candidates cannot spend extra time on one section by saving time from another. Managing time within each section is as important as knowing the material.

Importantly, the assessment uses a scoring mechanism that includes both accuracy and sometimes negative marking. Candidates should read the instructions at the start of each section carefully before beginning.

Quantitative Aptitude

The Quantitative Aptitude section tests numerical reasoning and mathematical problem-solving. The questions at this section are generally of moderate difficulty, but the time constraint makes them challenging. Topics that consistently appear include:

Number Systems and Number Theory: Questions on divisibility, factors, HCF and LCM, remainders, and properties of integers. These are foundational and appear in almost every drive.

Percentage and Ratio: Calculation of percentages, percentage change, ratio and proportion, mixture and alligation. These topics are practical and relatively straightforward but require accuracy under time pressure.

Profit, Loss, and Discount: Basic profit-loss calculations, successive discounts, and cost price-selling price relationships.

Time, Speed, and Distance: Relative speed problems, boat and stream questions, train problems. These are reliable appearance topics.

Time and Work: Problems involving shared work, pipes and cisterns, and efficiency calculations.

Simple and Compound Interest: Interest calculations over single and multiple periods.

Data Interpretation: Bar charts, pie charts, line graphs, or tables followed by 3-5 questions requiring calculation. This sub-topic can be time-consuming, and candidates who do not pace themselves carefully risk running out of time.

Probability and Permutation-Combination: Basic probability questions and counting problems. These appear with moderate frequency.

The recommended approach for this section is to start with the topics you are most confident in, mark difficult problems for review, and avoid spending more than 90 seconds on any single question in the first pass. Data interpretation questions should be attempted strategically: read all the questions first before reading the data to know exactly what information you need to extract.

Logical Reasoning

The Logical Reasoning section tests analytical thinking and the ability to identify patterns, draw inferences, and evaluate arguments. Infosys places significant weight on this section. The topics include:

Series Completion (Number and Letter Series): Identifying the rule governing a sequence and determining the next element. Practice with both simple arithmetic progressions and more complex nested patterns.

Blood Relations: Multi-step family relationship problems. Drawing a family tree diagram is usually the most reliable approach.

Seating Arrangement: Linear and circular arrangement puzzles. These are common in Infosys assessments and can take time if not approached systematically.

Coding-Decoding: Problems where a rule is applied to transform one set of symbols into another and you must identify or apply that rule.

Syllogisms: Problems with given statements and conclusions where you must determine which conclusions logically follow. A clean approach to inclusion-exclusion or Venn diagram thinking is useful.

Direction-based Problems: Tracing movement through compass directions and calculating final positions or distances.

Data Sufficiency: Given a problem and two statements, determine whether the information in the statements is sufficient to answer the problem.

Puzzles: Complex multi-constraint logic puzzles that require careful tracking of information across several variables.

Logical reasoning questions at Infosys tend to be more application-heavy than purely mechanical. The candidate needs to actually think through the problem rather than apply a memorized formula. Time management is critical here because puzzles can consume disproportionate amounts of time if you get stuck on them.

Verbal Ability

The Verbal Ability section tests English language proficiency, including reading comprehension, grammar, vocabulary, and written communication. For many engineering students, this is the section they are least prepared for, which makes it a significant differentiator.

Topics in this section include:

Reading Comprehension: One or more passages followed by questions that test inference, detail recall, tone identification, and logical conclusions drawn from the passage. The passages in Infosys assessments are typically of medium complexity and are drawn from topics like business, technology, science, or social issues.

Fill in the Blanks: Single or double blank sentences where the appropriate word or phrase must be selected. This tests vocabulary and contextual understanding.

Error Identification: Sentences with underlined portions where the candidate must identify grammatical or usage errors.

Sentence Correction: Selecting the most grammatically correct or effectively worded version of a sentence.

Para-jumbles: Scrambled sentences that must be rearranged into a coherent paragraph. This tests understanding of logical flow and discourse structure.

Vocabulary (Synonyms and Antonyms): Less common in recent versions but still appears in some formats.

For reading comprehension, the most effective strategy is to read the questions before reading the passage, then scan the passage for relevant information. Do not try to memorize the passage; identify where the information you need is located, then answer.

Candidates who want to improve quickly on the verbal section should read quality English writing for at least 30 minutes a day in the weeks leading up to the assessment. Business publications, science magazines, and well-written opinion pieces are all useful. The goal is to build a feeling for clear, correct English rather than to memorize rules.

Pseudocode and Programming Section

This section has become a standard part of the Infosys assessment for freshers, reflecting the company’s increasing emphasis on technical capability at the point of hiring. It typically includes two sub-types of questions: pseudocode interpretation and actual coding tasks.

Pseudocode Interpretation:

In this type of question, a block of pseudocode is presented along with a specific input, and the candidate is asked to trace through the code and determine the output. No actual programming knowledge is required in the traditional sense; the test is whether you can read, parse, and follow algorithmic logic. Topics covered include:

  • Loops (for, while, nested)
  • Conditional statements (if-else chains)
  • Simple recursive logic
  • String operations (concatenation, substring)
  • Array traversal and manipulation
  • Basic mathematical operations within code

The key to performing well on pseudocode questions is to work through them step by step, tracking variable values on paper as you go. Candidates who try to do this mentally often make errors in nested loops or complex conditionals.

Coding Questions:

The actual coding section requires candidates to write working code to solve a problem. The platform typically supports multiple languages including C, C++, Java, and Python. Problems range from easy to medium difficulty on a competitive programming scale.

Common problem types include:

  • String manipulation (reversals, palindrome checks, anagram detection, character frequency)
  • Array operations (sorting, searching, finding duplicates, subarray sums)
  • Basic mathematical problems (prime checking, factorial, Fibonacci, GCD computation)
  • Pattern printing
  • Basic greedy or mathematical logic problems

For most SE-track candidates, solving the coding question correctly and efficiently is sufficient. The evaluation criteria include correctness (does the code produce the right output), code quality (is it readable and sensibly structured), and sometimes efficiency (though highly optimal solutions are not required for standard SE roles).

Candidates should practice writing complete, compilable code from scratch rather than relying on partial solutions. A common mistake is submitting code that would work in theory but has syntax errors or off-by-one bugs that cause it to fail on test cases. Time spent on clean, working code is more valuable than time spent on clever but broken optimizations.

The Assessment Environment:

The Infosys online assessment is delivered through a remote proctored platform. For off-campus candidates, this means the test is taken on your own computer with webcam and microphone monitoring active throughout. For campus candidates, the assessment is typically conducted in a college computer lab with both system-based proctoring and human invigilators.

Common technical issues that disrupt the assessment include unstable internet connections, webcam detection failures, and browser compatibility problems. Infosys specifies the recommended browser and system requirements in the pre-assessment instructions. Test these requirements the day before the assessment using a system check link provided in the assessment invitation email.

If you face a technical disruption during the assessment, such as a disconnect or a webcam failure, do not panic. Note the time, take a screenshot if possible, and immediately contact the support number or email provided in the assessment email. Most proctoring platforms have a dedicated support line for exactly this scenario. Claiming a technical issue after the assessment without contemporaneous documentation is far less likely to result in a reattempt.

Score Reporting:

Infosys does not communicate individual section scores or the cutoff criteria to candidates. The result is communicated as a pass or fail, with shortlisted candidates receiving an email to schedule or prepare for the interview round. Because the scoring criteria are not transparent, candidates should not try to guess their performance from the number of questions they answered correctly. The better approach is to prepare thoroughly, perform consistently across all sections, and wait for the official communication.

Sectional Cutoffs:

While Infosys does not officially publish sectional cutoffs, the assessment is widely understood to apply minimum performance thresholds for each section in addition to an overall score threshold. This means that even if your total score is high, performing very poorly in one section can result in disqualification. Candidates should not plan to maximize performance in their strongest sections to compensate for weak ones. The goal should be acceptable-to-strong performance across all sections simultaneously.

Practice Resources:

The most effective preparation resources for the Infosys online assessment are previous drive question compilations available on placement preparation platforms, timed mock assessments that mirror the actual format, and books specifically designed for placement aptitude preparation. Topic-specific practice should precede full-length mock tests rather than replacing them. The transition from comfortable topic practice to timed full-section mocks is where most candidates discover their actual weak points.

Technical Interview Rounds

Clearing the online assessment takes you to the interview stages. For fresher candidates going through standard SE hiring, there is typically one technical interview round, though some drives include two. For lateral hires, the number of technical rounds depends on the seniority of the role and the complexity of the technology stack involved.

What Interviewers Actually Evaluate

Understanding what the interviewer is looking for changes how you present yourself. Infosys technical interviewers for fresher roles are primarily evaluating three things:

Conceptual Clarity: Do you actually understand the fundamentals, or did you just memorize answers? The interviewer will often ask you to explain a concept and then ask a follow-up that tests whether you understood it or just recited it. For example, if you say you know object-oriented programming, the follow-up might not be “what is polymorphism?” but rather “can you give me an example from your project where you applied polymorphism and tell me what problem it solved?”

Problem-Solving Approach: When given a problem you have not seen before, can you think through it systematically? Interviewers at Infosys for fresher roles are not expecting you to produce optimal solutions to novel algorithmic problems instantly. They are watching whether you can break a problem down, articulate your thinking, and move toward a solution. Silence followed by a perfect answer is less impressive than a transparent, audible reasoning process.

Communication and Professionalism: Infosys operates in a client-service model. Employees interact with client teams, attend project meetings, and write technical documentation. Interviewers assess whether the candidate can communicate clearly, listen to questions properly, and engage professionally.

For lateral hires, the evaluation adds a fourth dimension: depth of experience. Interviewers for experienced roles are specifically checking whether the candidate’s described experience was genuinely hands-on or merely peripheral. Probing questions like “how many lines of code did you personally write in that module?” or “walk me through the most difficult bug you debugged in that project” are designed to distinguish genuine contribution from inflated resume claims.

Common Technical Topics

The following topics appear frequently in Infosys technical interviews for freshers:

Programming Fundamentals:

  • OOP concepts: classes, objects, inheritance, polymorphism, abstraction, encapsulation
  • Differences between procedural and object-oriented programming
  • Concepts of pointers (for C/C++ candidates)
  • Memory management basics

Data Structures:

  • Arrays, linked lists, stacks, queues
  • Binary trees and binary search trees
  • Hashing and hash tables
  • Sorting algorithms: Bubble, Selection, Insertion, Merge, Quick, and their time complexities
  • Searching: Linear search and Binary search

Database Management:

  • SQL queries: SELECT, INSERT, UPDATE, DELETE
  • Joins: INNER, LEFT, RIGHT, FULL OUTER
  • Normalization: 1NF, 2NF, 3NF
  • Primary keys, foreign keys, constraints
  • Indexing basics
  • Transactions and ACID properties

Operating Systems:

  • Processes and threads, and the difference between them
  • Deadlock: conditions, prevention, avoidance
  • Memory management: paging, segmentation, virtual memory
  • Scheduling algorithms: FCFS, Round Robin, SJF

Networking Basics:

  • OSI model and TCP/IP model
  • TCP vs UDP
  • HTTP and HTTPS
  • DNS, IP addressing, subnetting basics

Computer Networks and Security (increasingly appearing):

  • Basics of firewalls, encryption, and authentication

Beyond these core areas, interviewers will often ask about the candidate’s final year project or any personal projects, internships, or certifications. These project-related questions are where many candidates underperform because they either cannot explain their own work clearly or cannot handle technical follow-up questions about their project’s implementation.

A disciplined way to prepare for project questions is to build what practitioners sometimes call a “project story”: a structured explanation of the problem the project addressed, the technology choices made and why, the implementation approach, challenges encountered, how they were resolved, and what the outcome was. Candidates who can walk through this story coherently and answer follow-up questions with confidence make a strong impression.

The Interview Room Dynamic:

Technical interviews at Infosys are typically conducted in a panel format or a one-on-one format depending on the drive. For campus placements, the most common format is a one-on-one or two-member panel interview lasting 20 to 40 minutes. For lateral hires, panels of two or three technical interviewers are common, particularly for senior roles.

The interviewer will often start with a question meant to ease you into the conversation, such as asking you to introduce yourself or describe your project. This is not a throwaway warm-up. Interviewers pay attention to how you present yourself from the first sentence. A clear, structured introduction signals communication ability immediately.

From the introduction, the interview typically moves into a combination of concept questions, situational questions, and problem-solving questions. The ratio of these varies by interviewer and by how the conversation develops. If you demonstrate strong knowledge of a topic early, expect the interviewer to go deeper into that topic. If you show weakness in an area, some interviewers will move on while others will probe further to understand the depth of the gap.

Handling Questions You Are Not Sure About:

The response to uncertainty is one of the clearest differentiators between candidates who succeed and those who do not. The following pattern works reliably well: acknowledge what you know about the surrounding topic, reason through what the answer might be based on first principles, and be explicit that you are reasoning rather than recalling. For example:

“I am not entirely certain about the exact definition of a clustered index, but I know that indexes in databases are used to speed up lookups. If I reason from that, a clustered index might be one where the actual data rows are sorted in the same order as the index, which would mean faster range queries but slower inserts compared to a non-clustered one. Is that roughly correct?”

This kind of answer demonstrates reasoning ability and intellectual honesty, both of which are valued more than memorized definitions. It also opens a conversation with the interviewer, who may confirm, correct, or extend what you said, giving you the opportunity to learn and recover in real time.

When the Technical Round Includes a Live Coding Problem:

Some Infosys technical rounds include a live coding exercise or a whiteboard problem. In these cases, the evaluation is almost entirely about process. Before writing a single line of code:

  • Repeat the problem back to the interviewer to confirm you understood it correctly
  • Ask clarifying questions about edge cases (empty input, very large values, duplicate elements)
  • State your intended approach before implementing it, so the interviewer can intervene if you are heading in a wrong direction
  • Write clean, readable code with meaningful variable names
  • Walk through your solution with a simple example after writing it
  • Mention the time and space complexity of your solution

Even if you cannot arrive at an optimal solution, demonstrating structured thinking through all of these steps will usually produce a positive evaluation. An interviewer who watches a candidate systematically identify edge cases, propose a reasonable approach, write clean code, and self-evaluate its complexity is evaluating a candidate worth hiring, not just a correct answer.

Technical Interview for Lateral Candidates:

For experienced candidates, technical interviews go significantly deeper and operate on different dynamics than fresher interviews. The interviewer has your resume and has read it before the session. You should expect to be asked about specific projects, specific technical decisions, and specific outcomes.

Questions that consistently appear in lateral technical interviews at Infosys include:

  • “Walk me through the most complex technical problem you solved in your last role. What was your specific contribution?”
  • “What was your team structure and what was your ownership in the deliverable?”
  • “You mentioned using microservices in that project. What drove the decision to use microservices over a monolith? What challenges did you encounter?”
  • “Describe a time when a production issue occurred in a system you owned. How did you debug and resolve it?”
  • “How have you approached performance optimization in a real codebase?”

These questions reward genuine experience and penalize inflated resumes. Candidates who exaggerate their roles or claim credit for work done by others will typically be exposed within the first ten minutes of a well-conducted lateral technical interview. The most effective preparation is simply to be able to speak accurately, fluently, and in technical depth about work you actually did.

Certifications and How They Are Perceived:

Candidates increasingly come into Infosys interviews with AWS, Azure, Google Cloud, or other technical certifications. The perception of certifications in technical interviews is nuanced. A certification alone does not guarantee a strong interview performance, and interviewers know this. What certifications signal is that the candidate has invested deliberate time in a topic area, which is a positive signal. But the certificate becomes meaningful only if the candidate can engage substantively with questions about the technology it covers.

If you have a cloud certification, for example, be prepared to explain core concepts in depth, describe how you would design a simple cloud architecture, and discuss trade-offs between service options. A candidate who lists AWS Certified Solutions Architect on their resume but cannot explain the difference between an EC2 instance and a Lambda function will create a negative impression worse than not listing the certification at all.

Certifications from Infosys’s own ecosystem, such as InfyTQ certifications or Lex-based learning badges, are naturally viewed positively because they signal engagement with Infosys’s own technical standards and tools.

How to Handle Weak Technical Rounds

Not every technical round goes perfectly. Candidates make mistakes, forget things under pressure, or encounter questions that fall outside what they prepared for. The question is how to recover.

The most important thing to understand is that a single wrong answer or blank is not disqualifying. Interviewers are making a holistic assessment. A candidate who gets a question wrong but responds to being corrected by engaging intelligently with the correction and demonstrating understanding is often evaluated more positively than a candidate who consistently gives rote-correct answers with no apparent understanding.

If you do not know the answer to a question, say so directly. “I am not sure about the exact mechanism there, but based on what I know about how memory management works, my best guess would be…” is a more honest and often more impressive response than an obviously wrong confident answer.

If you realize mid-explanation that you have taken a wrong direction, do not double down. Stop, acknowledge the error, and correct course. Intellectual honesty is valued in technical environments.

After a technical round that felt weak, do not try to rationalize it in the HR round. If the HR asks how the technical round went and you felt it did not go well, it is acceptable to say you found one or two questions challenging while emphasizing what you did know and your eagerness to keep learning. Overconfidence about a round that clearly went poorly tends to reduce credibility.

The HR Interview Round

The HR interview is the final stage of the Infosys hiring process for freshers and is a standard component of lateral hiring as well. Many candidates treat this round as a formality, which is a significant mistake. The HR round serves as the primary cultural fit and intent verification stage, and candidates do fail this round.

What the HR Round Is Actually Testing

The HR interviewer is not trying to trick you. The questions may seem soft, but they are evaluated against real criteria. Specifically, the HR round at Infosys examines:

Genuine intent to join: Infosys has a significant yield problem where selected candidates do not show up on joining date or accept the offer and then decline it after receiving another offer. HR interviewers probe for commitment signals. If the interviewer senses the candidate is treating Infosys as a backup option, that affects the evaluation.

Attitude and adaptability: IT services careers require adjustment to different projects, clients, technologies, and team compositions. The HR interviewer is checking whether the candidate demonstrates flexibility, a positive attitude toward change, and the ability to manage ambiguity.

Communication and confidence: Can the candidate maintain composure, speak clearly, and present themselves professionally throughout a conversation?

Integrity: Questions about gaps in education, discrepancies between the resume and the conversation, or salary expectations are partly tests of honesty. Inconsistencies are noted.

Clarity about the role: Candidates who have no idea what Systems Engineer work at Infosys actually involves are a red flag. The HR interviewer expects that a candidate who has gone through a PPT and spent time applying has a basic understanding of what they are signing up for.

Common HR Questions and How to Answer Them

“Tell me about yourself.” This is an opener, not an invitation to recite your resume. The ideal response is 90 seconds to 2 minutes covering who you are, what you studied, what interests you about technology or your technical domain, and why you are interested in Infosys specifically. Keep it structured and confident.

“Why do you want to join Infosys?” Generic answers about Infosys being a good company or a reputed name come across as empty. Research specific aspects of Infosys that genuinely appeal to you: its global client base, training programs, specific technology practices, or the structured career ladder. Mention something specific.

“Where do you see yourself in five years?” Infosys appreciates ambition when it is framed within a realistic career trajectory. Talking about growing from a Systems Engineer to a Technology Analyst, building expertise in a specific domain, and taking on project leadership responsibilities is a well-received answer. Avoid saying you plan to start your own company in two years.

“What are your strengths and weaknesses?” For strengths, pick one or two that are genuinely relevant to the role and support them with specific examples. For weaknesses, the classic advice applies: choose a genuine weakness, but one that is not fundamentally incompatible with the job, and describe how you are actively working on it.

“Are you ready to relocate?” Answer honestly. Infosys expects employees to be mobile. If you have a genuine constraint around relocation, it is better to be transparent than to say yes and later create a joining complication.

“What is your salary expectation?” For freshers, there is typically a fixed package for the SE role, so this question is often not asked or has a standard answer. For laterals, come prepared with a market-informed range and be ready to discuss it calmly.

“Do you have any questions for me?” Always have at least one prepared question. Good questions include asking about the training program structure, typical first project experience, or what the team culture is like in the group the interviewer works with. Avoid asking about salary or benefits in the HR round unless the interviewer raises it.

Managing Anxiety in the HR Round:

Many candidates are more nervous in the HR round than in the technical round because the questions feel less predictable. Technical questions have right and wrong answers; HR questions feel like personality tests. The way to reduce anxiety in the HR round is to approach it as a conversation rather than an interrogation. The interviewer is a professional doing their job. They are not trying to catch you out or make you feel uncomfortable. Treat the conversation the way you would treat a meeting with a senior professional who is interested in knowing more about you.

Preparation helps significantly. Candidates who have written out their HR answers, practiced them aloud, and rehearsed follow-ups feel materially more confident than those who are improvising entirely. You cannot predict every question, but you can prepare for the most important ones and practice the skill of thinking clearly and speaking composedly under mild pressure.

HR Rounds for Lateral Hires:

The HR round for lateral candidates covers additional ground compared to fresher HR rounds. Compensation discussions are more detailed, including current CTC, expected CTC, and the components of the package being offered by Infosys. Notice period negotiation also happens here: Infosys will ask about your current employer’s notice period and may discuss whether they can accommodate a specific joining date.

For candidates who are currently employed, the HR interviewer will also probe on reasons for leaving the current role. The safest and most credible answers are honest and professional: seeking better growth opportunities, interest in a specific technology domain, desire to work on a different kind of client or project. Answers that are entirely critical of the current employer tend to create concern about how the candidate will talk about Infosys in the future.

Negotiation in the HR Round for Laterals:

Salary negotiation in lateral hiring at Infosys is possible but requires a realistic understanding of how the company structures compensation. Infosys generally offers laterals a 20 to 30 percent increment on current CTC for roles where the candidate is an acceptable fit, with higher increments possible for roles requiring niche skills or where the candidate brings a specific domain expertise that is in short supply.

The negotiation should be conducted professionally and with market data to back it up. Saying “I have an offer from another company for X amount” is a direct and commonly used approach, but it is most effective when true. Fabricating competing offers in the HR round is a risk that can backfire significantly if the HR interviewer asks probing questions about the other offer.

It is also worth understanding what is and is not negotiable. Base salary and variable pay percentage are the primary components that may have flexibility. Non-salary components like PF contributions, insurance, and standard allowance structures tend to be fixed by Infosys policy and are generally not subject to negotiation.

Offer Letter Timeline and What to Expect

After completing all the interview rounds, selected candidates move into the offer letter and pre-joining verification phase. The timeline from selection to receiving a formal offer letter varies significantly depending on the hiring track.

Campus Placements: For on-campus drives, the results are typically communicated on the same day or within a day of the final interview round. Selected candidates may receive a verbal confirmation on the day, followed by a formal offer letter within a few days to a few weeks. The offer letter is dispatched to the candidate’s registered email address.

Off-Campus Drives: Off-campus offer letter timelines are less predictable. After the final selection, the HR team initiates the documentation and background check process, which can take anywhere from two to six weeks. The offer letter is issued after the initial verification is complete.

Lateral Hiring: For lateral hires, the timeline is typically longer. After the final interview round, there is an internal approval process for the compensation structure, followed by background verification. Total time from final interview to offer letter can range from two weeks to two months, depending on the seniority of the role and how quickly the internal approvals move.

What the Offer Letter Contains: The Infosys offer letter specifies the role, the location, the joining date, the compensation package (typically presented as a CTC figure), and the applicable service agreement terms. Freshers joining Infosys at the SE level are required to sign a service agreement, the terms of which cover a minimum service period and a bond penalty for early exit. Candidates should read this document carefully before signing.

Background Verification: Background verification at Infosys is conducted by a third-party agency and covers educational qualifications, prior employment history (for laterals), and personal identification. Candidates should ensure that all documents submitted during the process match the information provided during application. Common issues that delay or jeopardize the joining process include discrepancies in percentage calculations (for example, a candidate who rounded up a 59.7 to 60 in the application), missing or incorrectly stated employment dates for lateral hires, and documents that are not properly attested.

Document Checklist:

To avoid joining delays, candidates should organize the following documents well before the joining date:

For freshers: All mark sheets from 10th, 12th, and each semester or year of the undergraduate program. The consolidated mark sheet or degree certificate where available. A valid government-issued photo ID (Aadhar, passport, or driver’s license). PAN card. Passport-size photographs. Address proof. If an internship was completed and listed on the application, an internship completion certificate.

For laterals: All of the above, plus experience letters or relieving letters from every previous employer listed in the resume. Last three months’ salary slips. Bank statements for salary credit (to verify the claimed current CTC). Form 16 from the previous employer where applicable. A no-objection certificate from the current employer if required under the service terms.

Communicating After Selection:

The period between selection and joining involves communication primarily through the offer acceptance portal and email. Candidates should check their registered email daily during this period. Missing a documentation request or a portal action because of email neglect is a frequent and unnecessary cause of joining complications. Ensure that your spam filter is not accidentally routing Infosys communications to the junk folder.

If you need to change your joining date or have a question about documentation, contact the onboarding team through the official portal or the contact details provided in the offer letter. Avoid reaching out through informal channels unless you have been specifically given a personal point of contact.

Infosys Onboarding Process

The onboarding process at Infosys is one of the more structured and comprehensive in the industry, particularly for freshers. Understanding what to expect removes anxiety and helps you arrive prepared.

Pre-Joining Documentation: After accepting the offer, candidates receive a pre-joining portal link where they must upload a set of documents. These typically include mark sheets from 10th, 12th, and undergraduate studies, a passport-size photograph, a government-issued ID proof, address proof, and PAN card. Some offers also require a relieving letter (for laterals) or a no-objection certificate from the current employer during the notice period.

Reporting for Joining: The offer letter specifies a joining date and location. Freshers joining Infosys typically report to the Infosys Global Education Center (GEC) in Mysore for foundation training. The duration and structure of the Mysore training program are covered in a separate guide in this series, but the key point at this stage is that joining happens at Mysore, not at the final work location.

Lateral hires typically report directly to the Infosys delivery center they have been assigned to, which could be in any of the company’s offices across cities including Bangalore, Pune, Hyderabad, Chennai, Kolkata, or other locations.

Induction and System Access: On the day of joining, employees complete a formal induction that covers company policies, IT access setup, HR systems, and basic compliance training. This is also when the service agreement is signed (for freshers). Employees receive their employee ID, email credentials, and access to the internal employee portal (InfyMe).

Fresher Foundation Training: After joining formalities, freshers at Mysore begin the foundation training program. This covers generic technical training across programming, databases, and systems concepts, as well as soft skills and domain-specific modules. Detailed guidance on this phase is available in the Mysore training guide in this series.

The First Few Weeks Post-Joining:

Whether you are joining as a fresher at Mysore or as a lateral hire at a delivery center, the first few weeks are important for establishing the right impressions and building the relationships that will support your early career at Infosys.

For freshers at Mysore, the structured training schedule leaves relatively little ambiguity about what you should be doing. Attend all sessions, engage with the material actively, and build relationships with your batch colleagues. Many of the long-term professional relationships that Infosys employees maintain across their careers were formed during the Mysore training period.

For lateral hires, the first weeks involve understanding the team, the current project context, the tools and processes in use, and the client environment. Resist the temptation to criticize how things are done compared to your previous employer. Ask good questions, offer your skills and perspectives constructively, and invest time in understanding the existing system before proposing changes.

Both fresher and lateral hires should engage with the InfyMe portal, which serves as the internal information hub for policies, benefits enrollment, payroll details, and internal opportunities. Setting up your profile, enrolling in health insurance, and understanding the leave policy early avoids administrative surprises later.

Payroll and Salary Processing:

The first salary credit at Infosys for freshers typically occurs in the second month of joining, covering the first month’s work. Laterals joining mid-month receive a proportional salary for the joining month in the following payroll cycle. If the salary credit does not appear on the expected date, the first point of contact is the HR helpdesk accessible through InfyMe, not the project manager or team lead.

The Mysore Training Assessment Cycle:

Freshers joining at Mysore should understand that the foundation training program involves continuous assessments. Performance in these assessments influences stream allocation, which determines the technology domain you are assigned to after training. This is covered in detail in the Mysore training guide, but it is worth flagging here: the training at Mysore is not a formality and the assessments matter. Candidates who approach the training period as a paid vacation tend to end up in less preferred streams with fewer technical growth opportunities.

Post-Training Project Allocation:

After completing the Mysore foundation training, freshers are allocated to delivery centers and projects. The allocation is based on a combination of stream performance, business demand, and the availability of open positions in various delivery centers. Candidates who performed well in a specific stream during training have a higher probability of being allocated to a project that uses those skills, but it is not a guarantee.

The transition from training to project can take a few days to a few weeks depending on how quickly a suitable project position is available. During this period, freshers may spend time on self-learning or additional internal courses, which is a useful opportunity to deepen expertise in the allocated stream.

New project joiners are typically assigned a buddy or a project mentor who helps with onboarding into the team and project context. Making the most of this mentoring relationship in the first 30 to 60 days significantly shortens the time it takes to start contributing meaningfully to the project.

Common Mistakes Candidates Make at Every Stage

This section consolidates the most significant and frequently observed errors across the entire Infosys hiring process.

During Registration and Application:

Submitting inaccurate academic data is the most consequential mistake at this stage. Even small discrepancies, such as a slightly incorrect aggregate percentage or an unlisted backlog, can result in offer withdrawal after months of waiting. Apply only when you meet the criteria, and always double-check what you submit.

Applying to multiple Infosys drives simultaneously without understanding that the company tracks applications is another issue. If you appear in an assessment for one drive and then show up in another within a short window, it can raise flags and lead to disqualification from both.

During the Online Assessment:

Uneven time management across sections is the primary technical failure in the assessment. Candidates who spend too long on difficult questions early on often find themselves rushing through sections they would have handled well under normal conditions.

Not reading the pseudocode questions carefully is a specific mistake in the coding section. Many candidates scan the pseudocode quickly and miss a critical line that changes the output entirely. Slow, systematic tracing is always the right approach here.

During Technical Interviews:

Claiming familiarity with technologies or concepts you cannot actually explain when probed is a serious credibility error. If your resume lists five programming languages but you can only genuinely discuss two, interviewers probing the other three will quickly establish that. It is better to list fewer genuine competencies than to invite scrutiny on inflated claims.

Failing to prepare for your own project is common. Candidates often spend weeks studying data structures and algorithms but spend no time rehearsing how to explain the work they themselves have done. This is backwards. Your project is the one area where you have unique depth, and it is almost always explored.

During the HR Round:

Giving memorized, generic answers to HR questions without personalizing them or demonstrating genuine thought. Interviewers who have conducted hundreds of HR rounds can identify a rehearsed answer immediately.

Showing reluctance about relocation or service terms without a factual basis. Some candidates raise concerns about the service agreement in the HR round in a way that suggests they are already planning to leave. This is a red flag.

After Selection:

Not maintaining contact or not tracking documentation timelines. The period between selection and joining can be several months for freshers. Candidates who do not follow up on documentation requests, do not keep their contact information updated on the portal, or miss pre-joining steps can jeopardize their joining without realizing it.

After Receiving the Offer Letter:

Accepting the offer letter and then continuing to actively attend interviews at other companies while treating the Infosys offer as a secured backup is a practically risky strategy, not just an ethical issue. Infosys conducts pre-joining verification and communication up to the joining date, and candidates who ghost or decline at the last minute create a record that may affect future applications.

If you genuinely receive a substantially better offer after accepting from Infosys and decide not to join, communicate your decision to Infosys as soon as possible rather than simply not showing up. This is more respectful of the resources Infosys has invested in your processing, and it releases your slot for another candidate who may have been on the waitlist.

During Induction and Early Days:

A subtle mistake many joiners make is treating the first few weeks as a period where they cannot be evaluated because they are new. In practice, the impressions formed during induction and early weeks have a lasting effect. Colleagues and managers form judgments about a new joiner’s attitude, work ethic, and potential very quickly. Candidates who engage actively, ask thoughtful questions, and show up prepared to every session or meeting consistently start their Infosys career on a stronger footing than those who coast through the joining period.

Oversharing in HR Rounds:

A specific mistake worth addressing is the tendency of some candidates to overshare personal details or grievances in the HR round. Questions like “do you have any concerns about joining?” are not invitations to discuss family problems, personal health issues, or grievances about how the process was conducted. Answer honestly and professionally, and keep personal context to what is strictly relevant.

Misrepresenting Notice Period Flexibility:

For lateral candidates, claiming you can join in 30 days when your actual notice period is 90 days creates a problem that surfaces immediately after offer acceptance. Be honest about your notice period from the beginning. Infosys HR teams are experienced at managing joining timelines and can often accommodate longer notice periods if communicated honestly upfront. The problem arises when the candidate misrepresents availability and then cannot fulfill the commitment, which can lead to offer withdrawal.

Stage-by-Stage Preparation Strategy

The following preparation framework is designed for fresher candidates going through the standard SE hiring process. Lateral candidates can adapt the relevant sections for their own preparation.

8 Weeks Before Assessment:

Begin with a comprehensive review of Quantitative Aptitude, dedicating an hour daily to working through practice questions across the core topics. Focus on achieving speed and accuracy together, not just knowing the method. Use timed practice sessions from the start.

Simultaneously, start a structured review of the Logical Reasoning topics. Seating arrangement, blood relations, and series problems require the most practice. Work through at least 10 problems per topic in the first two weeks.

On the programming side, ensure your core data structures knowledge is solid. This means being able to implement arrays, linked lists, stacks, and queues from scratch, and being able to trace through sorting and searching algorithms by hand.

6 Weeks Before Assessment:

Shift the aptitude and reasoning preparation to full-length timed mock tests rather than topic-by-topic practice. The goal now is to work under realistic time pressure across an entire section. Review every mistake after each mock to understand the pattern of where you are losing points.

Increase your verbal ability preparation. Read English-language publications daily. Practice reading comprehension passages with strict time limits.

Begin practicing pseudocode questions. Find past Infosys pseudocode problems and practice tracing through them with variable tracking on paper.

4 Weeks Before Assessment:

Begin practicing coding problems on an online platform, focusing on easy-to-medium difficulty string and array problems. Aim to solve at least two problems per day. The goal is to become comfortable writing complete, clean, compilable code quickly.

Begin preparing your project story. Write down a structured explanation of your academic or personal project, practice explaining it out loud, and then have a friend or mentor ask follow-up technical questions.

2 Weeks Before Assessment:

Take at least three complete mock assessments in a simulated environment: same time of day as the real test will be, no interruptions, no breaks between sections unless the format allows it. Review results carefully and focus remaining preparation time on your weakest areas.

Revise core technical interview topics: OOP, SQL, OS basics, and networking fundamentals. Use flashcard-style review for definitions and key distinctions.

Prepare your HR answers. Write them out, speak them aloud, and refine them. Anticipate follow-up questions and prepare for those as well.

In the Week Before the Assessment:

Do not attempt to learn new material. Focus on revision, keeping your sleep schedule consistent, and ensuring your equipment (for online/remote tests) is functioning correctly. Verify that your webcam, microphone, and internet connection meet the proctoring requirements for remote assessments.

Building a Coding Practice Habit:

Many candidates leave coding practice until the last two weeks and then try to cram it. This approach works poorly for programming skills, which develop through consistent repetition over weeks rather than intense short-term effort. The ideal is to start practicing coding problems from the beginning of your preparation period, even if it is just one problem per day, and to gradually increase the volume and difficulty as the assessment approaches.

When practicing coding problems, avoid looking at the solution until you have genuinely tried to solve the problem yourself. Productive struggle, where you are stuck and thinking hard, is where skill development actually happens. Reviewing a solution you have not attempted yourself produces minimal improvement.

Understanding Infosys’s Assessment Philosophy:

The Infosys assessment is designed to identify candidates who can think analytically, communicate in English, apply basic programming logic, and meet a minimum threshold of academic discipline. It is not designed to filter for brilliance or to find candidates with exceptional algorithmic knowledge. The difficulty is calibrated to identify a large pool of capable, trainable candidates rather than to select the top 1 percent of problem-solvers.

This calibration has a practical implication: you do not need to be an exceptional student to clear this assessment. You need to be a consistent, well-prepared student. Candidates who are academically average but who have invested systematic effort in preparation routinely outperform academically stronger candidates who walk in unprepared.

Interview Preparation Beyond Technical Knowledge:

Strong technical knowledge is necessary but not sufficient for interview success. Candidates should also invest time in:

Practicing speaking clearly and at a moderate pace. Many candidates who know their material stumble in interviews because they speak too fast when nervous, skipping important words or losing their train of thought. Practice delivering explanations to someone who will listen and ask follow-up questions.

Building comfort with being wrong. In mock interview sessions, practice the experience of being told your answer is incorrect and responding without embarrassment. The reaction to being wrong is itself evaluated in technical interviews, and composure under correction is a positive signal.

Developing awareness of body language and eye contact for in-person interviews. Posture, eye contact, and a confident but relaxed demeanor contribute to the overall impression. Candidates who stare at the table while answering or who adopt defensive postures (crossed arms, slumped shoulders) create a less confident impression regardless of the accuracy of their answers.

Preparation for Off-Campus Candidates:

Off-campus candidates often face an additional psychological challenge: the uncertainty of not knowing when or whether they will receive an assessment invitation. This waiting period can stretch across weeks or months, and maintaining preparation momentum during this time requires discipline.

The most effective approach is to set up a structured daily practice routine that does not depend on having a specific assessment date on the calendar. Treat each day of preparation as an investment with compounding returns. Candidates who maintain consistent preparation for three to four months build a level of fluency across all assessed areas that makes the actual assessment feel manageable rather than threatening.

Off-campus candidates should also diversify their application strategy. Apply to Infosys through multiple available channels simultaneously: the careers portal, InfyTQ, and employee referrals if accessible. Being in multiple pipelines increases the probability of receiving an assessment call during any given window.

Frequently Asked Questions

1. What is the minimum percentage required to apply to Infosys?

The standard eligibility criterion is 60 percent aggregate or 6.0 CGPA across 10th, 12th, and undergraduate degree. This applies consistently across most drives, and there is no rounding. Candidates who are even slightly below the cutoff are not eligible.

2. Can non-CS branches apply to Infosys?

Yes. Infosys does not restrict applications to CS or IT branches for the Systems Engineer role. However, the online assessment and technical interview do evaluate programming and computer science fundamentals, so non-CS candidates need to prepare these topics independently.

3. How many rounds are there in the Infosys selection process for freshers?

The standard process for the SE role consists of the online assessment, one technical interview round, and one HR round. Some drives include two technical rounds. The total number of rounds is specified in the drive communication.

4. Is there negative marking in the Infosys online assessment?

Whether negative marking applies depends on the specific drive. Some formats include negative marking for wrong answers. The instructions at the start of each section will specify this. Candidates should read the instructions carefully before attempting each section.

5. How long does the Infosys online assessment take?

The total duration varies but is typically around 95 to 120 minutes for the full assessment. Each section is individually time-limited, and unused time from one section cannot be carried to another.

6. What languages can be used in the Infosys coding section?

The platform typically supports C, C++, Java, and Python. Some platforms also support languages like JavaScript or Kotlin. The available language list is visible at the start of the coding section.

7. How long does it take to receive an offer letter after selection at campus placement?

For campus placements, the offer letter is usually issued within two to four weeks of selection, after initial document verification. Off-campus placements may take longer, sometimes six to eight weeks.

8. What is the Infosys service agreement for freshers?

Freshers joining Infosys at the SE level are required to sign a service agreement that mandates a minimum service period with the company. Leaving before completing this period involves a financial penalty as specified in the agreement. The exact terms are covered in the agreement document itself, which candidates receive before signing.

9. Can a candidate reapply to Infosys after being rejected?

Yes, candidates can reapply after a waiting period typically specified in the rejection communication. Infosys specifies a cooling-off period after rejection, which is usually six months to one year. Candidates should note this from the rejection message and track their reapplication eligibility accordingly.

10. Is it possible to negotiate salary at Infosys for a lateral hire?

Yes. Lateral hiring at Infosys does involve salary discussions, unlike fresher hiring where packages are generally fixed. The negotiation window is influenced by the candidate’s current CTC, the market rate for the specific skill set, and the seniority of the role being hired for. Candidates with niche or high-demand skills typically have more room to negotiate.

11. What happens if I fail the online assessment?

Failing the online assessment means the candidate is not shortlisted for the interview rounds. The result is communicated by email, and the cooling-off period before the next eligible application is specified in the communication. Candidates should use this period to systematically address the gaps in their preparation.

12. Does Infosys hire candidates with backlogs?

Active backlogs (courses not yet cleared) generally disqualify a candidate from applying. Cleared backlogs (courses eventually passed but not in the first attempt) may be acceptable in some drives, but must be honestly disclosed during registration. The specific policy varies by drive and is stated in the eligibility criteria for each application.

13. How important is the coding section compared to the aptitude sections?

All sections contribute to the overall assessment score, and sectional cutoffs are believed to apply in many drive formats. Strong performance in one section cannot fully compensate for poor performance in another. The coding section has become increasingly important in Infosys hiring, and strong performance there, particularly writing correct and clean code, meaningfully differentiates candidates.

14. What should I wear to an Infosys interview?

Formal business attire is the standard expectation for in-person interviews. For men, formal trousers, a formal shirt, and formal shoes are appropriate. For women, formal western or formal Indian attire is equally appropriate. Avoid casual clothing including jeans, t-shirts, or open footwear. For video interviews, dress formally from at least the waist up, and ensure the background is clean and professional.

15. How should I prepare for questions about projects I did not build from scratch?

Many academic projects involve using frameworks, libraries, or code bases that someone else created. This is normal and not a problem as long as you are honest about it. Prepare to explain clearly which parts you built, what you contributed, what you learned, and what the project was designed to accomplish. Interviewers are evaluating your understanding and contribution, not claiming you reinvented everything.

Final Thoughts: The Candidate Who Gets Hired

After thousands of Infosys drive cycles, the profile of the candidate who consistently succeeds through this process shares a few characteristics that go beyond academic scores and technical knowledge.

They are prepared, but not in a mechanical way. They understand what they have studied, not just how to recite it. When they do not know something, they engage with it honestly rather than trying to bluff. When they encounter a difficult problem, they lean into it rather than retreating.

They are professional without being stiff. They dress appropriately, arrive on time, and communicate clearly. In the HR round, they talk about themselves in a way that is honest and grounded. They have thought about why they want to join Infosys and can articulate it without sounding like they read it off a website.

They have done the work. The online assessment is not something you can wing if the competition in your batch is prepared. The coding section especially rewards genuine practice. Candidates who solved two hundred problems on a practice platform before the assessment consistently outperform those who solved twenty.

And importantly, they treat the entire process with appropriate seriousness. They show up, they follow up, they submit documents on time, and they ask questions when something is unclear rather than making assumptions. This attentiveness to process is itself a signal that the candidate is reliable and professional, exactly the qualities Infosys is trying to evaluate.

The Infosys hiring process is demanding, but it is also navigable. Every stage has a clear structure, every evaluation has a known set of criteria, and every challenge has a preparation path. Candidates who approach this process with a genuine commitment to preparation and a clear understanding of what each stage requires will find themselves with more opportunities than those who rely on hope or last-minute effort. That gap, between the prepared and the unprepared, is ultimately what the Infosys selection process is designed to measure.

The journey from application to your first working day at Infosys can take weeks or months depending on the hiring track and the time of year. Throughout that journey, patience and persistence matter as much as preparation. Stay engaged with your preparation even during quiet periods when you are waiting for communication. Use every available resource: practice platforms, study groups, college alumni networks, and the wealth of publicly available information about how Infosys operates.

Candidates who begin with a thorough understanding of the process, build their preparation systematically, and approach each stage with professionalism and genuine engagement give themselves the best possible chance not just of receiving an offer, but of starting their Infosys career well-positioned for the growth and opportunity the company genuinely offers its committed employees.