Every year, tens of thousands of engineering students from Mechanical, Civil, Electrical, Electronics, Chemical, and other non-IT branches receive Infosys offer letters. Many of them feel uncertain about what they have signed up for: will their degree background hold them back, will they be given inferior projects, will they struggle through technical training designed for CS students, and does joining Infosys as a non-IT student represent a compromise or an opportunity?
The honest answers to these questions are more positive than most non-IT students expect. Infosys has hired non-IT branch students for decades, has built its training program to accommodate candidates who arrive without a CS background, and has deployed non-IT hires successfully on technology projects across every service line. The non-IT student who joins Infosys today, prepares seriously during the pre-joining period, approaches training with genuine effort, and builds domain skills alongside technical skills has a career trajectory that is not meaningfully different from a CS graduate who joins at the same time.
This guide covers everything a non-IT branch student needs to know about joining and building a career at Infosys: the eligibility criteria, how the selection process differs, what the online assessment expects from non-IT candidates, how to prepare for technical questions when your degree did not cover CS fundamentals, what happens during Mysore training, how stream allocation works for non-IT students, what project work looks like, how to leverage your engineering domain knowledge as a genuine career advantage, and the realistic career trajectory from year one to year ten.
Table of Contents
- Who Qualifies as a Non-IT Branch at Infosys
- Eligibility Criteria for Non-IT Students
- How the Selection Process Works for Non-IT Candidates
- The Online Assessment: What Non-IT Students Need to Know
- Technical Interview Preparation for Non-IT Students
- HR Interview: Addressing the Non-IT Background
- [InfyTQ](https://insightcrunch.com/2021/10/09/infytq-preparation-guide/) and Pre-Joining Preparation
- Mysore Training: The Non-IT Student Experience
- Stream Allocation for Non-IT Students
- Common Myths About Non-IT Students at Infosys
- Leveraging Your Engineering Domain in IT
- Career Trajectory: Non-IT Branch at Infosys
- Non-IT to Product Company: The Longer Route
- Branch-Specific Guidance
- Frequently Asked Questions
Who Qualifies as a Non-IT Branch at Infosys
Before preparing for Infosys, non-IT students need to confirm that their specific degree and branch is eligible under Infosys’s fresher hiring criteria. Infosys is genuinely open to a wide range of engineering branches, not just CS and IT.
Branches That Are Typically Eligible:
Infosys explicitly recruits from the following non-IT engineering branches in its standard fresher hiring drives:
Mechanical Engineering (B.E./B.Tech) Civil Engineering (B.E./B.Tech) Electrical Engineering (B.E./B.Tech) Electrical and Electronics Engineering - EEE (B.E./B.Tech) Electronics and Communication Engineering - ECE (B.E./B.Tech) Electronics and Instrumentation Engineering (B.E./B.Tech) Chemical Engineering (B.E./B.Tech) Aerospace Engineering (B.E./B.Tech) Production Engineering (B.E./B.Tech) Industrial Engineering (B.E./B.Tech) Biotechnology Engineering (B.E./B.Tech, some campus drives) Agricultural Engineering (B.E./B.Tech, selected drives)
Non-Engineering Degrees:
In addition to engineering branches, Infosys also hires from certain science and mathematics programs for specific roles:
B.Sc. (Computer Science, Mathematics, Statistics, Physics) at some campuses M.Sc. (Computer Science, Mathematics, Statistics) through specific channels MCA (Master of Computer Applications) - treated similarly to IT branches in many cases
How to Confirm Your Branch’s Eligibility:
The eligibility criteria for any specific Infosys campus drive are announced through the campus placement cell. The placement cell notification lists the eligible branches for that drive. Not every drive includes all branches: some drives target only engineering students, some target only specific branches, and some are open to all eligible engineering branches. Always verify the specific drive’s eligibility list rather than assuming general eligibility applies to every drive.
For off-campus applications through the Infosys careers portal or InfyTQ, the eligibility criteria are displayed during the application process and must be confirmed before applying.
Eligibility Criteria for Non-IT Students
The core eligibility criteria are largely identical for IT and non-IT students. Infosys does not maintain a lower standard for non-IT branches: the academic performance threshold applies equally.
Academic Percentage:
A minimum aggregate of 60 percent (or 6.0 CGPA on a 10-point scale) is required across all of the following:
10th standard (Secondary School Certificate or equivalent) 12th standard (Higher Secondary Certificate or equivalent) All semesters or years of the undergraduate engineering degree
The 60 percent threshold applies to each level independently, not just the overall average. A student with 85 percent in the degree but 58 percent in 10th standard does not meet the eligibility criteria.
Some specific campus drives may have higher eligibility thresholds (65 percent or 70 percent). The placement cell notification specifies this for each drive.
Backlog Policy:
Infosys’s standard policy is no active backlogs at the time of the assessment and no active backlogs at the time of joining. A student with one or more uncleared subjects at the time of the drive is not eligible, regardless of branch.
Cleared backlogs (subjects that were not cleared in the first attempt but were subsequently cleared) are allowed within a specified limit. The exact number of allowed cleared backlogs varies by hiring cycle and is specified in the placement notification. This policy applies identically to IT and non-IT students.
Graduation Year:
Infosys fresher hiring targets students graduating in the current or upcoming academic year. Students who graduated in a previous year but have not yet found employment may or may not be eligible depending on the specific drive and the gap period since graduation. Drives that specify “current year graduates only” exclude students who graduated in prior years.
No Simultaneous Multiple Applications:
The standard Infosys policy prohibits applying to multiple Infosys hiring channels simultaneously. If you are selected in an Infosys campus drive, do not simultaneously apply through InfyTQ or the off-campus portal. This creates duplicate records in the system and can complicate the offer process.
How the Selection Process Works for Non-IT Candidates
The Infosys selection process for non-IT students follows the same structure as for IT/CS students: online assessment, technical interview, and HR interview. The difference is not in the process structure but in what is tested in the technical interview and what the interviewer looks for.
The Online Assessment:
The online assessment is identical for all branches: Quantitative Aptitude, Logical Reasoning, Verbal Ability, and in some cycles a Pseudocode section. The aptitude and reasoning sections do not test domain knowledge: they test numerical reasoning, logical deduction, and language skills, which are equally applicable regardless of engineering branch.
Non-IT students who have prepared systematically for the aptitude section actually perform comparably to CS students because the aptitude section does not reward CS knowledge. A Mechanical Engineering student who has practiced percentage problems, logical series, and verbal comprehension is as well-prepared for the aptitude section as a CS student who practiced the same content.
The Technical Interview:
This is where the experience differs most for non-IT students. The technical interview for CS students focuses primarily on OOP, Java, DBMS, OS, and data structures. The technical interview for non-IT students typically covers:
Basic programming concepts (loops, conditionals, functions) in any language the student has studied, even if only at the introductory level.
One core CS topic at a basic level: usually either basic OOP concepts or fundamental data structures (arrays, stacks, queues). The expectation is not the same depth as for CS students but sufficient familiarity to demonstrate genuine engagement with computing.
The student’s specific engineering domain as it relates to technology: what software tools were used in their engineering program, whether they have any programming exposure from their curriculum, what specific technical projects they completed.
The final year project in detail: how it was designed, what technology it used, what specific contribution the student made, and what they learned from it.
The gap year or transition motivation if the student does not have a CS background: the interviewer wants to understand why this student, with a Mechanical or Civil degree, is pursuing an IT career, and whether that pursuit is genuine or opportunistic.
What Non-IT Students Are Expected to Know Technically:
The minimum technical knowledge expected for a non-IT student in the Infosys technical interview:
Basic programming in at least one language: this means being able to write a loop, define a function, use conditionals, and explain what these do. Python or C is acceptable. Java knowledge is a significant advantage.
Awareness of OOP concepts at the definitional level: even if the student has not programmed extensively in OOP, knowing what classes, objects, encapsulation, and inheritance mean is expected.
Basic computer science awareness: what is the difference between hardware and software, what is an operating system, what does a compiler do, what is the internet and how does a web browser retrieve a page. These are general awareness questions, not deep technical questions.
Their own engineering domain tools: a Mechanical Engineering student should be able to discuss AutoCAD, MATLAB, or simulation software they used in college. A Civil Engineering student should be able to discuss structural analysis software or AutoCAD applications. An EEE student should be able to discuss MATLAB/Simulink, PSpice, or relevant embedded systems tools.
The HR Interview:
The HR interview for non-IT students covers largely the same territory as for CS students (motivation, flexibility, career goals, company knowledge) but with specific additional questions about the non-IT background:
Why IT instead of core engineering? The answer must be genuine and specific, not just “IT pays better.” A good answer connects the student’s actual interests and experiences to technology work specifically.
Are you aware that the training and initial work will involve technology domains your degree did not cover? The expected answer is yes, combined with demonstrated preparation (InfyTQ certifications, personal programming projects, self-study).
Are you comfortable working in technology service roles that may not use your core engineering knowledge directly? The expected answer is yes.
The Online Assessment: What Non-IT Students Need to Know
The Infosys online assessment, as described in the Aptitude Questions guide in this series, is branch-agnostic. The Quantitative, Logical Reasoning, and Verbal Ability sections do not test CS or domain knowledge. However, the Pseudocode section, where it appears, does test basic programming logic.
The Pseudocode Section for Non-IT Students:
The pseudocode section tests the ability to trace through simple code logic and determine outputs. It does not require knowledge of any specific programming language but does require basic understanding of:
Variable assignment: understanding that x = 5 assigns the value 5 to the variable x.
Conditionals: understanding what IF-THEN-ELSE structures do.
Loops: understanding what FOR and WHILE loops do, including loop termination conditions.
Basic arithmetic and modulo operations: understanding MOD (remainder) and how to compute it mentally.
Non-IT students who have not been exposed to programming in their curriculum should study these basics specifically before the assessment. The pseudocode questions in the Infosys assessment are at the simplest end of what a programmer would consider basic; they are designed to test whether a candidate has any programming awareness at all, not whether they can build complex programs.
Recommended Preparation for the Pseudocode Section:
Work through the pseudocode examples in the Infosys Aptitude Questions guide in this series. Each example includes a trace-through explanation that builds the understanding needed for the actual assessment. Five to ten hours of dedicated pseudocode practice is sufficient for most non-IT students to reach a comfortable level on this section.
InfyTQ as Pre-Assessment Preparation:
The InfyTQ platform has specific courses designed as foundational programming and CS content. For non-IT students, completing the Python Fundamentals course on InfyTQ provides both the pseudocode reasoning skills needed for the assessment and the programming foundation needed for Mysore training. This is the single highest-value pre-assessment preparation activity for non-IT students who have limited programming background.
Technical Interview Preparation for Non-IT Students
Technical interview preparation for non-IT students requires a different approach from what a CS student needs. The bar is lower on CS depth but the expectation for genuine curiosity and demonstrated self-learning effort is higher.
Minimum Technical Preparation:
Before the Infosys technical interview, every non-IT student should be able to:
Write a basic program in at least one language. “Hello World” is not sufficient. Aim for being able to write a program that uses a loop, a conditional, and a function. Python is the recommended language for non-IT students given its readability and the strong support available through InfyTQ.
Explain the four OOP concepts (encapsulation, inheritance, polymorphism, abstraction) at the definitional level with a simple example each. The example does not need to come from a complex program; everyday analogies work fine if combined with a brief code explanation.
Explain what a database is and what SQL does at a conceptual level: “a database stores structured data in tables, and SQL is the language used to query and manipulate that data.” Basic SELECT, INSERT, and WHERE concepts are sufficient.
Explain what an operating system does: manages hardware resources, provides an interface between applications and hardware, handles process scheduling and memory management. Basic familiarity with the concepts of process, thread, and file system is useful.
The Project Explanation:
The project is the non-IT student’s strongest preparation area because it is their own work. For non-IT students who worked on final year projects involving technical computation, simulation, or data analysis, the project explanation should specifically highlight any software tools or programming involved.
Examples of strong non-IT project presentations for Infosys interviews:
A Mechanical Engineering student who built a finite element analysis simulation: “I built a simulation of stress distribution in a cantilever beam using ANSYS. What was technically interesting was understanding how the software discretizes the continuous material into mesh elements and applies numerical methods to compute stress at each node. This gave me an appreciation for how computational tools solve physical problems that cannot be solved analytically.”
An EEE student who built a load monitoring system: “I built a real-time power consumption monitoring system for a lab. I used an Arduino microcontroller with current sensors, programmed it in C, and displayed the readings on an LCD. I also wrote a Python script to log the data to a file over USB for post-processing analysis in Excel.”
A Civil Engineering student who used structural analysis software: “I modeled a three-story reinforced concrete building in STAAD.Pro for my design project. Working with the software taught me how structural engineers translate physical design specifications into computational models. I also used AutoCAD for the detailed drawings.”
These explanations are strong because they connect the engineering work to technical tools and computational thinking, demonstrating that the student’s engineering background involved genuine technology engagement.
Handling “Why Don’t You Know Java/OOP Deeply?”
The most common challenge in non-IT technical interviews is being asked about topics the student genuinely has not studied in depth. The correct approach:
Be honest about what you have and have not studied. “My degree curriculum did not include Java, but I have been learning it through InfyTQ since receiving the Infosys offer. I can explain the basic OOP concepts I have studied so far.”
Demonstrate genuine self-learning. Showing that you have already started learning the relevant CS topics signals initiative. Saying “I plan to learn it during training” is weaker than “I have completed the InfyTQ Python certification and I am working through the Java module.”
Connect your engineering problem-solving skills to programming. Engineering problem-solving and programming problem-solving share fundamental skills: decomposing a complex problem into manageable sub-problems, thinking systematically about constraints and edge cases, verifying solutions against expected outputs. These connections, articulated thoughtfully, demonstrate that the transition from engineering to programming is genuine rather than superficial.
HR Interview: Addressing the Non-IT Background
The HR interview for non-IT students has a specific dimension that CS students do not face: addressing why a person with a Mechanical or Civil degree is pursuing an IT career. This question deserves serious preparation.
The “Why IT?” Question:
This is the highest-stakes question for non-IT students in the HR round. The interviewer is specifically assessing whether the interest in IT is genuine or purely financial, and whether the transition is likely to be stable or likely to produce an early resignation when the student realizes the work does not match their interests.
What Makes a Weak “Why IT?” Answer:
“IT has better salary than core engineering.” This is probably true but it is the wrong reason to join an IT company. It signals that the student will leave for core engineering if core salary ever improves, or that they have not thought about what IT work actually involves.
“I could not find a core engineering job.” This signals that Infosys is a fallback, not a first choice. It raises joining probability and retention probability concerns simultaneously.
“I am good at mathematics, so I thought IT would suit me.” Mathematics ability is a prerequisite but not a distinguishing reason. Every engineering student can make this claim.
What Makes a Strong “Why IT?” Answer:
A strong answer is specific, genuine, and connected to the student’s actual experiences and interests.
Good answer framework: “My interest in IT developed specifically during [specific experience or course]. I realized that [specific aspect of technology work] aligns with [specific thing I enjoy]. I have since [specific preparation action] to build toward this transition. The work I want to do at Infosys specifically involves [specific service line or type of work] because [genuine reason].”
Example (Mechanical Engineering): “My interest in IT developed during my final year project when I used MATLAB to simulate vibration in a gear system. I spent significantly more time programming the simulation and interpreting data than I did on the mechanical design itself, and I found the computational side more engaging. I then taught myself Python to process the simulation output data, which gave me a direct experience of how programming solves engineering problems. I want to pursue this further in a professional context, and Infosys’s engineering and manufacturing service line would let me combine my mechanical engineering domain knowledge with the software skills I am developing.”
This answer is strong because it is specific (MATLAB, simulation, Python, gear system), connects the interest to real experience rather than abstract preference, demonstrates self-learning action, and articulates a specific career direction within Infosys that leverages the non-IT background.
The Flexibility Question in the Non-IT Context:
Non-IT students sometimes hope that joining an IT company will eventually lead to a role that uses their core engineering knowledge: a Civil engineer hoping to work in construction technology, a Mechanical engineer hoping to work in manufacturing automation. This hope is legitimate but should not be expressed as a conditional: “I want to join IT but I want to work in manufacturing technology projects.”
The appropriate framing is: “I am fully committed to the IT career path at Infosys. My engineering domain knowledge may be an advantage in specific project contexts, but my goal is to become a strong IT professional, not to replicate my engineering curriculum in an IT context.”
InfyTQ and Pre-Joining Preparation
For non-IT students, InfyTQ is the single most important preparation resource between receiving an offer and joining at Mysore. It is not just a certification platform; it is a structured CS curriculum designed to bring non-CS students to the baseline needed for Mysore training.
The InfyTQ Courses for Non-IT Students:
InfyTQ offers courses in Python Fundamentals, Database Management Systems (DBMS), Java Basics, and Data Structures. For non-IT students, the recommended completion sequence before joining is:
Python Fundamentals first: Python’s readable syntax and minimal boilerplate make it the most accessible first programming language for students without prior programming experience. Completing the Python module and certification provides the foundational programming concepts (variables, data types, control flow, functions, collections) in a context that is genuinely learnable in four to six weeks of daily practice.
DBMS second: the DBMS module covers relational databases, SQL, normalization, and transaction concepts. This is highly teachable through InfyTQ and directly testable in both the Infosys assessment and the Mysore training assessments.
Java Basics third: Mysore foundation training primarily uses Java. Non-IT students who arrive with Python and basic Java exposure are significantly better positioned than those who arrive with neither.
Realistic InfyTQ Goals for Non-IT Students:
For a non-IT student with zero prior programming experience, completing the Python certification and achieving passing marks on the DBMS certification in the pre-joining period is a realistic and high-value goal. The Java module is secondary if time is limited; Python fundamentals translate reasonably well to understanding Java code even before Java is formally studied.
For a non-IT student who had programming in their curriculum (many EEE, ECE, and even some Mechanical programs include C or MATLAB programming), the InfyTQ certifications should be achievable at a higher level and should be targeted proactively.
Personal Projects During Pre-Joining:
Beyond InfyTQ, non-IT students who build a small personal project during the pre-joining period arrive with a concrete demonstration of self-learning. The project does not need to be sophisticated; a simple Python script that solves a problem related to the student’s engineering domain (a beam deflection calculator, a circuit analysis tool, a statistical analysis of a data set) demonstrates both programming ability and the ability to connect domain knowledge to software.
A project of this kind, explained in the technical interview (“I built a Python calculator for beam deflection using Euler-Bernoulli beam theory during the pre-joining period”), is a genuine differentiator that most non-IT students do not arrive with.
Mysore Training: The Non-IT Student Experience
The Mysore foundation training is where most non-IT students’ biggest concerns are centered: will I keep up with CS students who have four years of programming background? The honest answer is that the training is designed for the full range of IT freshers, including non-IT students, and most non-IT students who engage seriously with the training do fine.
The Foundation Training Curriculum:
The Mysore training covers: programming fundamentals (using Java as the primary language), data structures and algorithms, database management systems, software development methodologies (Agile, Scrum), Unix/Linux fundamentals, networking concepts, software testing, and professional skills. This curriculum is designed to bring all freshers to a common baseline, including those who arrive without a CS background.
Non-IT students who completed the recommended InfyTQ preparation arrive at Mysore at a disadvantage relative to CS students on the programming-intensive modules, but at a smaller disadvantage than they would otherwise face. The key is the gap between CS students who code daily and non-IT students with zero programming exposure, not between CS students and non-IT students who prepared seriously.
Assessment Performance:
The Mysore training includes regular assessments that are graded and used for stream allocation. Non-IT students who prepare seriously using InfyTQ and arrive with a genuine motivation to learn typically perform adequately in these assessments. The assessment questions are not designed to filter out non-IT students; they test the training content, and the training content is designed to be learnable by everyone in the training batch.
The assessment areas where non-IT students most commonly struggle are: Java programming questions requiring syntax and OOP application (where CS students have a practice advantage), data structure implementation questions (similar advantage), and complex SQL queries (varies more with individual preparation). The areas where non-IT students perform comparably are: logical reasoning questions, conceptual questions about software development methodologies, Unix commands and networking concepts, and professional skills assessments.
The Learning Rate Advantage:
One genuine advantage that motivated non-IT students bring to Mysore training is that they are not overconfident. CS students who have been programming for years sometimes underestimate the Mysore training and do not engage seriously enough with the assessments. Non-IT students, knowing they have more to learn, often bring more consistent effort to the daily training, which compounds over the training period into genuinely strong assessment performance.
Seeking Support During Training:
Infosys’s Mysore campus has resources for trainees who need additional support with specific topics: faculty available for extra sessions, peer tutoring from stronger performers in the batch, and the Lex platform’s self-study materials available outside training hours. Non-IT students should use all of these resources without hesitation. The training is designed to be completed by everyone in the batch; the support resources exist specifically for students who need to spend more time on certain topics.
Stream Allocation for Non-IT Students:
Stream allocation is based on training performance (assessment scores across the training period) combined with availability of project opportunities and business demand at the time of allocation. The stream allocations available to non-IT students are identical to those available to CS students: Java development, .NET development, testing, infrastructure, data and analytics, cloud, and others.
The most common concern non-IT students have is being assigned to a non-preferred stream because of lower training performance. This concern is legitimate: lower training scores do affect stream allocation outcomes. The mitigation is straightforward: prepare seriously before training, engage fully during training, and approach the assessments with the same rigor as any important examination.
Stream Allocation for Non-IT Students
Stream allocation at Mysore is the process through which trainees are assigned to specific technology streams for their first project deployment. Understanding how this works, and what streams are particularly accessible or advantageous for non-IT students, helps in setting realistic expectations and making the most of the process.
How Stream Allocation Works:
The stream allocation process considers: overall training assessment scores, performance on stream-specific assessments, available project demand in each stream at the time of allocation, and in some cases the candidate’s expressed preference (which carries limited but non-zero weight).
Training performance is the primary driver. Consistently high scores across all assessments produce the strongest position in stream allocation. Performance in stream-specific assessments (a Java-focused module’s assessment, for example) has direct relevance to Java stream allocation.
Streams Most Accessible for Non-IT Students:
Testing and Quality Assurance: software testing is the stream where domain knowledge matters least initially and where logical thinking and systematic methodology matter most. Non-IT students with strong logical skills and attention to detail perform well in testing streams, and the work builds genuine technical skills over time.
Data and Analytics: data engineering and analytics roles often value the ability to work with numerical data, understand statistical concepts, and frame business problems clearly. Non-IT engineers who studied data-intensive topics in their program (instrumentation data, structural load data, materials testing data) have natural preparation for analytical thinking. Python-based data work aligns well with the InfyTQ Python preparation.
Infrastructure and Cloud: cloud infrastructure work involves understanding how systems are set up, maintained, and monitored. It requires systematic thinking more than deep programming, and non-IT students who engage seriously with the networking and Unix modules in training often do well in infrastructure streams.
Java and .NET Development: these are the programming-intensive streams where CS students have the strongest advantage. Non-IT students who prepare seriously and perform well in the training’s programming assessments absolutely can be allocated to development streams. The preparation requirement is simply higher.
What to Do If You Receive a Stream You Did Not Want:
The stream allocated is not the stream you will work in forever. Within Infosys, internal job posting (IJP) opportunities exist after a defined service period. Engineers who develop strong skills in their first stream, demonstrate performance in their appraisals, and proactively apply to IJP postings in their preferred stream successfully make stream transitions. The first stream is the starting point, not the permanent assignment.
Additionally, the skills built in any stream contribute to the overall technical foundation that future moves, including transitions to other companies, are built on. A year of experience in a testing stream builds software quality knowledge, automation testing skills, and familiarity with SDLC that is genuinely valuable in subsequent roles.
Common Myths About Non-IT Students at Infosys
Several persistent myths about non-IT students at Infosys create unnecessary anxiety or unrealistic expectations. Addressing them directly clears the way for accurate preparation.
Myth 1: Non-IT students are automatically assigned to inferior or support roles.
Reality: Stream allocation is based on training performance, not branch. A Mechanical Engineering student who performs in the top quartile of the training batch receives the same stream allocation options as a CS student with the same performance level. Branch is not a discriminating factor in stream allocation once the candidate is in the training batch.
Myth 2: The Infosys technical interview for non-IT students is just a formality.
Reality: The technical interview for non-IT students is a genuine evaluation, though calibrated appropriately to the expected knowledge level. Arriving without any programming preparation or without being able to explain basic computing concepts is not protected by being from a non-IT branch. Non-IT students who have genuinely prepared pass; those who have not, do not.
Myth 3: CS students at Infosys always earn more than non-IT students hired at the same time.
Reality: All SE-level hires receive the same compensation package regardless of branch. A Mechanical Engineer joining as SE earns the same 3.6 LPA as a CS student joining as SE in the same batch. Designation-level parity is complete. The DSE and PP premium tracks are available to non-IT students through the same channels (DSE through the normal SE drive with stream performance, PP through HackWithInfy which is open to all branches).
Myth 4: Non-IT students cannot participate in HackWithInfy or other premium selection routes.
Reality: HackWithInfy is explicitly branch-agnostic. The contest evaluates competitive programming skill, not degree background. Non-IT students who have developed competitive programming skills participate on equal footing. Past HackWithInfy cycles have had non-IT branch students among the top performers.
Myth 5: Infosys training is so CS-heavy that non-IT students cannot keep up.
Reality: The training is designed to bring all participants to a baseline standard, including those without CS backgrounds. The pace is challenging for everyone and genuinely harder for non-IT students who arrive without preparation, but it is not impossible with serious engagement. Thousands of non-IT students successfully complete Mysore training every cycle.
Myth 6: Working in IT as a non-IT engineer is a waste of engineering education.
Reality: IT companies serve clients in every industry. A Mechanical Engineer working at Infosys on a project for a manufacturing client brings domain knowledge that a CS graduate does not have. This domain value becomes more apparent over time as the engineer builds both technical skills and industry expertise. Some of the most valued profiles at senior Infosys levels are engineers who combine deep domain expertise in a specific industry with strong IT delivery skills.
Leveraging Your Engineering Domain in IT
The career value of a non-IT background in IT is not immediately obvious in the first year, when the focus is entirely on building the software and CS foundations. But from the second year onward, the domain knowledge that a non-IT engineer brings becomes an increasingly valuable differentiator.
Domain-Specific Industry Knowledge:
Infosys serves major clients across every industry sector: manufacturing, automotive, aerospace, energy, utilities, healthcare, construction, and consumer goods. Many of these clients are best served by engineers who understand the industry at a deeper level than a CS graduate typically does.
A Mechanical Engineer working on a project for an automotive OEM client understands what a CAD system does, what the product development lifecycle looks like, and what the pain points of a manufacturing engineer are in ways that a CS graduate working on the same project may not. This understanding produces better requirements conversations, better solution design, and better client relationships.
An EEE Engineer working on a utilities sector client understands power system operations, demand forecasting, and grid management at a conceptual level that makes the business context of the software being built more intuitive.
A Civil Engineer working on a construction management platform project understands the project scheduling challenges, the materials procurement workflow, and the contract management complexity that the software is meant to address.
This domain understanding is not just background color; it is a genuine advantage in technology consulting, solution design, and business analysis roles that non-IT engineers increasingly fill as they progress in their careers.
The Domain + Technology Sweet Spot:
The most sought-after profiles in IT consulting combine deep technical software skills with genuine industry domain expertise. These profiles are rare and highly valued. A Mechanical Engineer who also becomes a strong Java developer or a strong data engineer is more valuable to an automotive or aerospace client than either a pure CS developer or a pure domain expert alone.
Building this combination is a deliberate process: develop the software skills seriously during Mysore training and the first project years, while consciously seeking opportunities to apply these skills in projects related to your engineering domain. Over five to seven years, this combination produces a profile that commands significantly higher compensation and more interesting work than either profile alone.
Business Analysis and Consulting Roles:
Business analysis roles at Infosys involve understanding client business requirements, translating them into technical specifications, and acting as the bridge between the client’s business stakeholders and the technical delivery team. These roles value domain knowledge highly: a BA on a manufacturing analytics project who understands production scheduling, quality control frameworks, and cost accounting is significantly more effective than one who does not.
Non-IT engineers are naturally suited to BA roles in their industry domains, and the transition from technical engineering delivery to BA is one of the most natural career evolutions for non-IT engineers at Infosys.
Technical Architecture in Domain-Specific Projects:
As careers progress into the Senior Engineer and Technology Analyst levels, technical architects begin defining how systems are built, not just building them. An engineer who combines strong software architecture knowledge with deep industry domain expertise can design systems that non-domain architects miss. This positioning becomes increasingly valuable and distinctive in years four through eight.
Pursuing Domain-Relevant Projects Strategically:
The first project assignment is determined by Infosys’s deployment needs, not the engineer’s preference. However, from the second project onward, engineers can express preferences through the internal mobility system and through conversations with their manager and unit HR about career direction.
Non-IT engineers who want to build the domain-plus-technology combination profile should articulate this interest to their manager from early in the first project. “I am a Mechanical Engineer and I want to develop my career toward manufacturing technology clients. What are the available paths within our unit for this?” is a legitimate and strategic conversation that most managers will respect.
Managers who know about a career interest can flag relevant internal postings, recommend the engineer for relevant projects, and provide context about the accounts in their portfolio that would suit the domain interest. Managers who do not know about the interest cannot help with it.
Certifications That Amplify Domain Value:
For non-IT engineers who want to formalize their domain expertise in a way that is recognized by clients and internal teams, industry-specific certifications provide this formalization:
For manufacturing domain: APICS CPIM (Certified in Production and Inventory Management) or APICS CSCP (Certified Supply Chain Professional) certifications are recognized by manufacturing clients.
For construction domain: PMP (Project Management Professional) certification, Autodesk Revit certification, or LEED certification are relevant.
For energy and utilities: CBCP (Certified Business Continuity Professional) or utility-sector regulatory certifications where applicable.
For aerospace: INCOSE Systems Engineering certifications for engineers working in aerospace or defense technology services.
These certifications combined with IT delivery credentials (cloud certifications, programming certifications) create the distinctive dual-credential profile that is rare and consequently valued.
Career Trajectory: Non-IT Branch at Infosys
The career trajectory for a non-IT student who joins Infosys is not fundamentally different from that of a CS student, with the understanding that the first two years require more active effort to build the CS foundation that CS students arrived with.
Year 1: Foundation and Adaptation
The first year is almost entirely about building the technical foundation: completing Mysore training, performing in assessments, getting stream allocated, and delivering on the first project. The non-IT student’s primary focus should be on learning the technology stack of the first project as thoroughly as possible.
In year one, the non-IT background is largely invisible to the project team. The work is the same as for any new joiner: understanding the existing codebase, fixing bugs, implementing small features, writing test cases, and learning how professional software development differs from academic projects. Embracing this work with genuine curiosity, rather than treating it as beneath an engineering graduate, is the foundation of a successful first year.
The appraisal at the end of year one is the first formal evaluation of performance. The criteria are identical for all SE-track employees regardless of branch: code quality, delivery against commitments, communication with the team, and initiative in learning. Non-IT engineers who have put in serious effort during training and the first project year receive ratings that are entirely comparable to CS peers.
Year 2-3: Building Technical Depth
Years two and three are where the non-IT student begins to build genuine technical depth in the technologies used in their project stream. The distinction that was present in training (non-IT student with less prior exposure) diminishes rapidly with serious on-the-job engagement.
By the end of year three, a non-IT student who has been genuinely engaged on their project, actively learning rather than just executing tasks, should have a technical profile that is comparable to a CS student with the same experience level, with the additional advantage of domain knowledge in their engineering area.
The SSE promotion, which occurs approximately at the two-year mark for strong performers, is entirely accessible to non-IT engineers. The promotion criteria are performance-based: delivery quality, skill development evidenced by certifications and project contributions, and initiative demonstrated through the appraisal record.
During years two and three, non-IT engineers who want to maximize their career options should pursue technical certifications relevant to their project stream. AWS, Azure, or GCP certifications for infrastructure-adjacent work; Java or Python professional certifications for development work; ISTQB certifications for testing streams. These certifications build the external-facing profile alongside the internal Infosys record.
Year 4-5: Domain Value Emerges
From years four and five, the strategic value of the non-IT background begins to be felt more tangibly. Engineers who have combined technical skills with domain expertise are increasingly sought for roles involving direct client engagement, requirements analysis, and solution design in their domain. Internal job postings in business analysis, presales support, and consulting begin to be accessible.
The SSE to TA transition in years four to five is also when engineers begin to have more influence over the technical direction of their work. Non-IT engineers who have developed strong opinions about how technology can be applied in their domain bring a perspective to architecture and design discussions that is genuinely valuable.
This is also the period when lateral movements within Infosys become accessible. The IJP (Internal Job Posting) system allows employees to apply for roles in different service lines, different accounts, or different locations after completing a defined service period. Non-IT engineers who have built both technical skills and domain expertise are competitive applicants for IJP postings that seek this combination.
Years 6-10: Senior Professional Trajectory
Beyond the five-year mark, the non-IT origin increasingly fades as a relevant classification and is replaced by the engineer’s specific professional profile: their technology skills, their domain expertise, their leadership experience, and their track record on projects. The paths to Principal Architect, Domain Consultant, or Senior Manager are equally available to non-IT origin engineers as to CS origin engineers, provided the skill development over the preceding years has been serious and deliberate.
Non-IT engineers who decide in the first three years that their goal is to transition to product companies or GCCs should follow the same path described in the Product Company Transition guide in this series. The non-IT origin requires slightly more preparation time for the DSA and system design components of product company interviews, but it does not change the fundamental path.
Salary Benchmarks at Each Stage:
At the SE level (joining): 3.6 LPA (standardized, branch-agnostic). At SSE (2-3 years): 5-7 LPA depending on performance, project, and appraisal outcomes. At TA (4-6 years): 8-12 LPA. At TL (6-9 years): 13-18 LPA.
These are approximate Infosys internal ranges; the actual trajectory depends heavily on individual performance and the specific project and account. External market transitions at any of these stages typically produce 50-80% salary improvements for non-IT engineers who have built genuine technical depth alongside their domain expertise.
Non-IT to Product Company: The Longer Route
The transition from a non-IT Infosys background to a product company is achievable but typically takes longer than the equivalent transition for a CS student. Understanding why, and planning for it accordingly, is more useful than being discouraged by the additional preparation time.
Why the Route Is Longer:
CS students at Infosys typically arrive with four years of programming practice and a theoretical CS foundation. Non-IT students arrive with engineering domain knowledge and (after Infosys training) a practical software foundation, but without the depth of algorithmic thinking and CS theory that four years of CS education builds.
The additional preparation required for product company technical interviews (specifically DSA at LeetCode Medium and above) is typically two to three months longer for a non-IT Infosys engineer than for a CS Infosys engineer at the same experience level.
The Realistic Timeline:
For a non-IT Infosys engineer targeting GCCs or tier-2 product companies: expect 12 to 15 months of focused preparation from when serious preparation begins. For tier-1 product companies: expect 15 to 20 months.
These timelines are entirely manageable when preparation is started early. An engineer who begins LeetCode practice at the one-year Infosys anniversary and maintains consistent daily practice is realistically in a position to apply to tier-2 targets by the two-and-a-half to three-year mark.
Leveraging Domain Knowledge in Product Company Interviews:
One genuine advantage non-IT Infosys engineers have in product company interviews that is rarely discussed: their domain expertise. Product companies that serve specific industry verticals (fintech, healthtech, edtech, construction tech, industrial IoT) actively value candidates who combine software skills with genuine industry understanding. A Mechanical Engineer turned software developer who has worked on manufacturing analytics at Infosys has a profile that is genuinely differentiated in manufacturing technology company interviews.
Branch-Specific Guidance
Different non-IT branches have different advantages and challenges in the IT career path. Understanding the specifics for your branch helps in targeted preparation.
Mechanical Engineering:
Advantages: Strong mathematical foundation, exposure to simulation software (ANSYS, MATLAB, SolidWorks), understanding of manufacturing processes, materials, and mechanical systems. Natural fit for manufacturing, automotive, and industrial IoT domain work.
Challenges: Typically the least programming-exposed branch. Most Mechanical programs include at most one C programming course. Additional programming preparation is the highest priority.
Specific preparation advice: InfyTQ Python is the most important pre-joining investment. Focus on building a simple simulation or computation project in Python using knowledge from the engineering domain (beam analysis, thermodynamics calculations, gear ratio computations). This directly bridges the academic background to the IT interview.
Career domain fit: Manufacturing analytics, industrial IoT, automotive technology, CAD/PLM software services, engineering simulation services.
Civil Engineering:
Advantages: Strong structural analysis and project management knowledge, exposure to STAAD.Pro, AutoCAD, and Revit, understanding of construction processes and cost estimation.
Challenges: Among the least programming-exposed branches. Similar to Mechanical in requiring significant pre-joining programming preparation.
Specific preparation advice: Focus on basic Python and SQL through InfyTQ. Building a spreadsheet analysis or data visualization project using construction or project management data demonstrates the connection between the degree and data analysis work.
Career domain fit: Construction technology platforms, infrastructure management, smart city solutions, building information modeling (BIM) services, project management software.
Electrical and Electronics Engineering (EEE):
Advantages: Strong mathematical foundation (signal processing, control systems), exposure to MATLAB and Simulink, understanding of power systems and electrical equipment, typically has more programming exposure than Mechanical or Civil.
Challenges: The programming typically done in EEE programs (MATLAB scripts, some C for embedded systems) is not the same as object-oriented application development. The conceptual gap to OOP programming is manageable but requires deliberate bridging.
Specific preparation advice: Leverage the MATLAB familiarity to build confidence with scripted computation, then systematically extend to Python and Java through InfyTQ. Smart grid technology, power systems analytics, and embedded systems IoT are natural domain applications.
Career domain fit: Utilities and energy sector clients, smart grid technology, power electronics simulation, industrial automation.
Electronics and Communication Engineering (ECE):
Advantages: Among the closest to CS of all non-IT branches. Many ECE programs include C programming, data structures, and in some cases Java or Python. Understanding of communication systems, signal processing, networking hardware, and embedded systems.
Challenges: While closer to CS than other non-IT branches, OOP concepts and software engineering practices may still require bridging preparation.
Specific preparation advice: ECE students are typically the best-prepared among non-IT students for Infosys technical interviews. Leverage any networking and communication systems knowledge for infrastructure and cloud stream discussions. Embedded systems experience bridges naturally to IoT work.
Career domain fit: Telecommunications clients, embedded systems and IoT, networking infrastructure, communication technology services.
Chemical Engineering:
Advantages: Strong in process simulation (Aspen Plus, HYSYS), data-intensive laboratory and production analysis, process optimization thinking. Growing demand for chemical process digitalization.
Challenges: Among the most distant from CS conceptually. Limited programming exposure in most programs. Requires significant pre-joining preparation.
Specific preparation advice: Python data analysis (using pandas and numpy for laboratory data processing) is the most natural bridge between chemical engineering work and IT skills. Process industries analytics is a growing area where this domain combination is valuable.
Career domain fit: Pharmaceutical and life sciences clients, oil and gas process clients, specialty chemicals sector.
Aerospace Engineering:
Advantages: Very strong mathematical and simulation foundation, exposure to MATLAB, Python (increasingly common in aerospace programs), finite element analysis tools, and computational fluid dynamics software.
Challenges: Aerospace programs vary widely in programming exposure. Strong programs include significant software; weaker programs do not.
Specific preparation advice: Leverage any MATLAB or Python exposure aggressively. Aerospace engineering programs that include CFD simulation using OpenFOAM or similar tools provide genuine programming exposure that should be highlighted in interviews.
Career domain fit: Aerospace and defense clients, engineering simulation services, CAD/CAE services.
Preparing for Core Engineering vs Infosys: Making the Decision
Some non-IT students reading this guide are genuinely uncertain whether to pursue Infosys or whether to focus entirely on core engineering roles. This decision deserves honest consideration.
When to Prioritize Core Engineering:
If you have a specific technical interest in your core engineering domain that IT work would not satisfy, if you have already received or are expecting good core engineering offers, if your college has strong core engineering placement, and if you genuinely find the prospect of IT services work less interesting than the technical engineering work your degree prepared you for, then pursuing core engineering first makes sense.
Joining IT from genuine disinterest, purely for the salary or because core options did not materialize, creates a work experience that feels like compromise. This feeling compounds over time and typically produces early attrition.
When Infosys Is the Better Choice:
If your interest in technology work is genuine and sustained (not just a response to placement pressure), if core engineering job opportunities in your location and specialty are limited, if you have already been building programming and IT skills independently, if you see the domain combination as a genuine long-term career strategy rather than a temporary paycheck, then Infosys is a strong choice.
The critical test is honest self-assessment: if someone offered you an equally paying core engineering job and the Infosys SE role, which would you genuinely prefer? The answer to this question, answered honestly, should guide the decision more reliably than any external advice.
The Mixed Strategy:
Some students pursue both simultaneously, applying to Infosys and to core engineering recruiters in parallel during the placement season. This is a legitimate strategy that hedges against the uncertainty of placement outcomes. The only caution: if you receive an Infosys offer and a core engineering offer simultaneously, make a genuine decision rather than accepting both and defaulting to whichever feels easier to decline later. Infosys’s offer acceptance process creates obligations that should be taken seriously.
Frequently Asked Questions
1. I am from a non-IT branch. Will Infosys assign me to IT work that has nothing to do with my engineering degree?
Infosys deploys employees based on project availability and training performance, not branch-specific routing. Many non-IT engineers are deployed on projects in their engineering domain, but it is not guaranteed. The first project assignment depends on batch-level demand at the time of your deployment. The strategy for eventually working in your domain is to develop both technical skills and domain expertise, then pursue internal postings in domain-relevant projects over time.
2. I have no programming background at all. Can I genuinely succeed in Infosys technical work?
Yes, provided you invest seriously in pre-joining preparation through InfyTQ and engage fully during Mysore training. The Mysore training is specifically designed to build programming skills from scratch. Students who arrive with zero programming exposure and complete the training successfully include non-IT engineers every cycle. The key variable is genuine effort, not prior background.
3. Will I earn less than CS students at Infosys because of my non-IT branch?
No. The SE package is standardized across all branches at the same figure (currently 3.6 LPA for the standard SE track). Branch does not affect compensation at the joining level. Future compensation growth is based on performance appraisals and promotions, which are also branch-agnostic.
4. Is there a stigma among Infosys teams against non-IT branch employees?
At the project team level, what matters is technical capability and work quality, not educational background. A non-IT engineer who delivers excellent work on a project quickly establishes credibility that makes the branch background irrelevant. The stigma concern, to the extent it exists at all, is most relevant in the first few weeks when no one knows you yet. Performance over the first few months effectively eliminates it.
5. Can I join Infosys as a Mechanical Engineer and eventually work in a role related to manufacturing technology?
Yes, and this is actually one of the most strategic long-term career paths for non-IT engineers at Infosys. Manufacturing and industrial clients are major Infosys accounts. Engineers who combine IT delivery skills with Mechanical Engineering domain expertise are valuable profiles for these client engagements. Building both over the first three to four years positions you for exactly this kind of work.
6. Which non-IT branch has the easiest time at Infosys technically?
ECE graduates typically find the transition to IT work easiest because their curriculum has the most overlap with CS fundamentals: C programming, data structures, networking hardware, digital electronics. EEE graduates typically have the next easiest transition due to MATLAB and C exposure. Mechanical and Civil graduates face the steepest learning curve from a technical standpoint, though it is entirely manageable with preparation.
7. I failed to clear InfyTQ certifications before my joining date. Should I be concerned?
InfyTQ certifications before joining are an advantage but not a formal prerequisite for joining the SE track. The Mysore training is designed for everyone in the batch including those who did not complete InfyTQ beforehand. You will face a steeper learning curve than peers who completed InfyTQ, which makes engaging more intensively with the training content from day one particularly important.
8. Is there any way to get a higher designation like DSE as a non-IT student?
Yes. The DSE track is not exclusively for CS students. Non-IT students who clear the DSE hiring process (which involves a higher-difficulty online assessment and technical interview) are offered DSE designation. The technical bar for DSE is higher than for SE, so the programming preparation required is also higher. Non-IT students targeting DSE should complete all InfyTQ certifications and invest in dedicated programming practice beyond the InfyTQ curriculum before attempting the DSE assessment.
9. My CGPA is exactly 6.0 on a 10-point scale. Am I eligible?
Yes, if the eligibility criterion for the specific drive is a minimum of 6.0 CGPA. Many Infosys drives specify this as the minimum threshold. Verify the specific drive’s criteria carefully: some drives specify 6.5 CGPA as the minimum, which a 6.0 would not meet.
10. I graduated two years ago from a non-IT branch and have been working in a core engineering job. Can I apply to Infosys now?
The standard fresher hiring process targets current final-year students. If you graduated two or more years ago, you would need to apply through the lateral or experienced hire channel rather than the campus or fresher channel. Lateral hire eligibility typically requires one to two years of prior work experience (which you would have from your core engineering role) and the same academic percentage criteria. The lateral process has a different assessment and interview format from fresher hiring.
11. Are non-IT students allowed to participate in Infosys Hackathons and internal competitions?
Yes. Infosys’s internal platforms including hackathons, innovation contests, and coding competitions are open to all employees regardless of joining branch. Participation in these activities is actually a smart career strategy for non-IT engineers who want to build technical visibility and credibility within the organization.
12. How should I explain the decision to work in IT on my resume for future job applications?
The framing for future applications should emphasize the career direction rather than the branch of origin: “Software Engineer with background in Mechanical Engineering, with 3 years of experience in manufacturing analytics and industrial IoT at Infosys. Strong in Python, SQL, and data pipeline development, with domain expertise in production process optimization and quality control.”
This framing treats the engineering background as an asset (domain expertise) rather than a liability (non-CS degree), which is the accurate framing for anyone who has developed genuine IT skills alongside their engineering knowledge.
13. Can non-IT branch students join Infosys through InfyTQ?
Yes. The InfyTQ hiring channel is open to all eligible branches including non-IT. The InfyTQ selection process evaluates performance on the InfyTQ platform assessments and certifications, which are accessible to all students. Non-IT students who perform well on InfyTQ can receive Infosys offers through this channel.
14. What happens during the technical interview if I truly cannot answer a technical question?
The recommended approach is identical to what the technical interview guide describes: acknowledge honestly what you do not know, engage with what you do know related to the topic, and demonstrate intellectual curiosity rather than shutting down. For non-IT students, adding “I have been specifically studying this topic since receiving the offer through InfyTQ” is a genuine and positive supplement when it is true.
15. Is Infosys a good first employer for a non-IT branch student who ultimately wants to work in a product company?
Yes, for three reasons. First, Infosys provides structured training that builds the CS foundation that non-IT students need to pursue product company roles. Second, the Infosys brand is recognized and respected in the market. Third, working at Infosys provides the professional experience record that future employers’ background verification processes verify. The transition to a product company from Infosys requires additional preparation (as described in the product company transition guide), but Infosys is a legitimate and valuable starting point for that journey.
The Non-IT Student’s 90-Day Plan After Receiving the Offer
The period between receiving the Infosys offer letter and the Mysore joining date is the highest-leverage preparation window available to non-IT students. How this period is used largely determines how the Mysore training experience unfolds.
Days 1-30: Foundation Building
The first month should be dedicated entirely to programming fundamentals. For students with zero prior programming experience, the goal is to reach the point of being able to write and understand basic Python programs independently.
Daily practice structure: 90 minutes of InfyTQ Python course content, followed by 30 minutes of solving the practice problems associated with each module. Do not rush through the content: understanding the first-principles of why a loop works is more valuable than rushing to the advanced modules.
Specific targets for the end of month one:
- Understand and write programs using variables, data types, conditionals, loops, and functions
- Understand what lists, dictionaries, and tuples are and how to use them
- Write a simple program that reads input, processes it, and outputs a result
- Have started the InfyTQ Python certification practice assessments
Days 31-60: CS Fundamentals
The second month should cover the conceptual CS foundations that the Mysore training builds on: OOP concepts, database basics, and basic data structures.
For OOP: Study the four pillars (encapsulation, inheritance, polymorphism, abstraction) using both definition-level understanding and simple code examples in Python. The goal is to be able to explain each concept with a real example in 60 seconds, not to write complex OOP programs.
For databases: Complete the InfyTQ DBMS module. Focus especially on: what a relational database is, what a primary key and foreign key are, and how to write basic SELECT queries with WHERE, JOIN, and GROUP BY clauses.
For data structures: Understand what arrays, linked lists, stacks, and queues are conceptually and what operations they support. Implementation-level knowledge is a bonus but not required in this preparation window.
Personal project: Build a small project during this month that uses both Python and a simple database. A student records tracker, a basic inventory system, or a simple quiz application all qualify. The project does not need to be impressive; it needs to be genuinely built by you.
Days 61-90: Assessment and Interview Preparation
The final month before joining should shift toward practicing under test conditions and specifically preparing for the joining day technical discussion.
Complete the InfyTQ Python certification if not yet done. Attempt the practice assessment under timed conditions. Identify the areas where you are losing marks and spend one week specifically on those areas.
Practice explaining your project (the engineering final year project and the personal IT project) in two minutes each. Record yourself and review. The explanation should include: what it does, what technology was used, your specific contribution, and what you learned.
Practice answering the most common non-IT technical interview questions: why IT, what programming languages you know, explain OOP concepts, what is a database, what does your final year project do technically.
Complete the iConnect portal submission with all documents. Resolve any documentation issues early rather than in the week before joining.
Real Experiences: What Non-IT Infosys Employees Say
The following perspectives are composites drawn from the experiences of non-IT engineers who have successfully navigated the Infosys journey. They represent genuine patterns rather than polished testimonials.
“The first two months at Mysore were genuinely hard.”
Many non-IT engineers describe the first six to eight weeks of Mysore training as more challenging than they expected. The pace of the Java curriculum, combined with the unfamiliarity of OOP concepts for engineers who had never programmed in an OOP language, creates a steep initial learning curve.
The consistent theme in how this was navigated: using every available hour of study time. Where CS colleagues could revise, non-IT engineers were often learning new material for the first time in the evenings and weekends. The students who managed this accepted that their preparation time needed to be proportionally higher and did not resist this reality.
“My Mechanical Engineering background became valuable much sooner than I expected.”
Several engineers who joined Infosys from Mechanical and EEE backgrounds describe being assigned to manufacturing or utilities sector projects within the first two years. In these contexts, their ability to understand the client’s technical language, their familiarity with the processes the software was supporting, and their credibility with client engineers who shared their background created a visible impact from early in the engagement.
One common experience: being included in client calls earlier than peers from CS backgrounds because the team recognized that the engineer’s domain knowledge made them more effective in client communication. This early client engagement accelerated career development significantly compared to purely technical peers.
“I wish I had started InfyTQ earlier.”
The most consistent regret expressed by non-IT engineers looking back at their joining preparation is not starting InfyTQ early enough. Candidates who received offers months before their joining date but only started InfyTQ in the final two weeks arrived significantly underprepared compared to those who began immediately after receiving the offer.
The preparation window is as long as the time between the offer letter and the joining date. Using all of it, rather than treating it as a holiday period, is the single most impactful decision a non-IT engineer can make.
“Being from Mechanical did not limit my career.”
Engineers at the SSE and TA level who joined from non-IT backgrounds consistently report that their branch origin became completely irrelevant within two to three years of joining. What mattered was their technical capability on the current project, their appraisal ratings, and their initiative in building skills. The branch appears in their resume as a historical fact; it does not define their professional identity or their career options.
Pre-Joining Skills Checklist for Non-IT Students
Before leaving for Mysore, confirm that you can confidently do each of the following. Items you cannot do are the priority for the remaining preparation time.
Programming Basics:
- Write a Python function that takes parameters and returns a value
- Write a Python loop that processes each element of a list
- Explain what a variable, a conditional, and a loop do in plain language
- Read a simple piece of code (10-15 lines) and predict what it outputs
OOP Concepts:
- Define encapsulation with an everyday example
- Define inheritance with an everyday example
- Define polymorphism at the definitional level
- Define abstraction with an everyday example
- Explain the difference between a class and an object
Database Basics:
- Explain what a relational database is and what tables, rows, and columns represent
- Write a SELECT query with a WHERE clause
- Explain what a JOIN does at a conceptual level
- Explain what a primary key is
Computing Awareness:
- Explain what an operating system does in two sentences
- Explain what a compiler does in two sentences
- Explain the difference between RAM and storage
- Explain at a high level what the internet is and how a web browser retrieves a page
Self-Presentation:
- Explain your engineering final year project in two minutes, including the technical tools used
- Explain a personal IT project or InfyTQ certification you completed in 60 seconds
- Answer “Why IT?” with a specific, genuine, 90-second answer
- Name three specific things about Infosys that genuinely interest you
Documentation:
- All academic documents organized and photocopied
- iConnect portal completed and submitted
- Bank account details verified
- 10 recent passport photographs prepared
The Longer View: Non-IT Branch as a Career Advantage
The non-IT branch background at Infosys, viewed through a ten-year lens rather than a two-year lens, is a genuine career advantage for engineers who choose to develop it deliberately. The technology industry is increasingly defined by domain-specific applications: manufacturing technology, construction technology, agricultural technology, energy technology, healthcare technology. The engineers who understand both the technology and the domain are the ones who build the products, lead the consulting engagements, and earn the premium compensation that these senior roles command.
Pure CS graduates who have spent their careers in general-purpose software development must learn domain knowledge on the job, later in their careers, to access these senior domain-specific roles. Non-IT engineers who joined IT companies early, built strong technical skills, and maintained their domain knowledge through client engagement and deliberate learning arrive at the same senior roles with the domain knowledge already in place.
This is the strategic arc that the best non-IT Infosys engineers are building, consciously or intuitively. They are not trying to become generic software developers who happened to start from a non-CS background. They are building toward being the kind of professional who is genuinely rare: technically capable, domain knowledgeable, and able to operate credibly in both technical and business contexts simultaneously.
That profile, developed over ten years through deliberate choices at each career stage, is worth significantly more in the market than either skill alone. It is also more personally satisfying to the kind of engineer who chose their original discipline because they found it genuinely interesting, and who has been quietly finding ways to reconnect that interest to their professional trajectory ever since.
The Infosys offer letter is the beginning of that arc. What the engineer does with it determines where the arc ends.
Common Technical Interview Questions for Non-IT Students: Practice Set
The following questions are specifically calibrated to the level expected from non-IT students in the Infosys technical interview. Unlike the deeper technical questions in the Infosys Technical Interview Questions guide (Article 12 in this series), these are framed at the entry-level depth appropriate for the non-IT candidate.
Q: You are from Mechanical Engineering. What programming have you done? Strong answer template: Be specific. Name the exact language(s), the context (course vs self-study vs project), the specific things you built, and what you have done since receiving the Infosys offer. Avoid saying “basic programming” without specifics.
Q: What is object-oriented programming? Expected answer: OOP is a way of writing software by organizing code around objects that combine data (attributes) and behavior (methods). The main concepts are encapsulation (bundling data and methods, controlling access), inheritance (a child class inheriting from a parent class), polymorphism (same method name behaving differently in different classes), and abstraction (exposing only what is necessary, hiding complexity).
Q: What is a database and how is it different from a spreadsheet? Expected answer: A database stores structured data in a way that supports efficient querying, concurrent access by multiple users, data integrity enforcement (primary keys, foreign keys), and transaction management. A spreadsheet is primarily for human-readable data manipulation with no built-in concurrency, integrity enforcement, or query language. For large-scale, multi-user data management, databases are necessary.
Q: Explain what your final year project does technically. Non-negotiable: be able to explain this in two minutes. Name the software tools used, describe the technical process, and state your specific contribution. Generic answers (“I worked on a renewable energy project”) are unacceptable. Specific answers (“I built a MATLAB simulation of wind turbine output versus wind speed using the Betz limit as the theoretical maximum, and validated the simulation against published field data from three turbine sites”) demonstrate genuine engagement.
Q: Why are you interested in software development if your degree is in [branch]? This question requires a genuine answer. The answer must reference a specific experience that created the interest (not a vague preference), the specific aspect of software work that appeals, and the concrete steps taken since that experience to develop toward it.
Q: What is an algorithm? Expected answer: An algorithm is a step-by-step set of instructions for solving a problem. It takes an input, processes it through defined steps, and produces an output. An algorithm has properties: it must terminate (finish in finite time), each step must be precise and unambiguous, and it must produce the correct output for all valid inputs. Everyday examples: a recipe is an algorithm for producing a dish; the process for solving a quadratic equation is an algorithm.
Q: What is the difference between hardware and software? Expected answer: Hardware is the physical components of a computer system (processor, memory, storage, input/output devices, network interfaces). Software is the set of instructions that runs on hardware. System software (operating systems, device drivers) manages hardware resources and provides a platform for application software. Application software (web browsers, databases, word processors) provides functionality directly to users.
Q: Can you tell me what happens when you run a Python script? Expected answer: The Python interpreter reads the source code (the .py file), compiles it into bytecode (an intermediate representation), and executes that bytecode using the Python Virtual Machine (PVM). The execution proceeds line by line, evaluating expressions, calling functions, and performing operations until the script completes or an exception is raised.
This level of technical explanation for non-IT students demonstrates genuine curiosity and self-study, which is exactly what the interviewer is looking for.
Summary: The Non-IT Student’s Path to Success at Infosys
Success at Infosys for non-IT branch students comes down to three decisions made in sequence, each building on the previous.
Decision 1: Commit to the IT career genuinely. The students who thrive are those who make a genuine commitment to building an IT career, not those who join because it was the most convenient offer or because core engineering did not work out. The genuine commitment is what produces the pre-joining preparation investment, the Mysore training engagement, and the first-project learning intensity that distinguishes strong performers from mediocre ones.
Decision 2: Build the technical foundation deliberately. The CS students in the batch arrive with four years of programming background. Non-IT students who close this gap through deliberate, consistent preparation (InfyTQ, personal projects, daily coding practice) arrive at the same destination as CS peers within two to three years. Those who assume the gap will close by itself discover that it does not.
Decision 3: Position the engineering domain as an asset. At some point in the first three to four years, the non-IT engineer must make a conscious decision about what their career positioning will be. The engineer who positions themselves as a generic IT professional with a non-CS background is competing against thousands of CS graduates with more prior exposure. The engineer who positions themselves as a domain expert in manufacturing, energy, construction, or aerospace who is also a capable software professional is competing in a much smaller field with much higher demand.
Every non-IT engineer at Infosys faces these three decisions. The career outcomes across the ten-year horizon are largely determined by how they are made.
Infosys Non-IT Branch: Quick Reference Fact Sheet
The following condensed reference covers the most-asked factual questions from non-IT students considering or preparing for Infosys.
Eligibility:
- Minimum 60% or 6.0 CGPA across 10th, 12th, and all semesters of the degree
- No active backlogs at time of assessment and joining
- All engineering branches eligible: Mechanical, Civil, EEE, ECE, Chemical, Aerospace, Production, Industrial, and others
- Non-engineering science degrees (B.Sc. CS, M.Sc. Maths) eligible at selected campuses
Compensation:
- SE standard package: 3.6 LPA (identical for all branches)
- DSE package: approximately 7.5 LPA (branch-agnostic)
- PP package: approximately 9 LPA (branch-agnostic)
- No branch-based salary differentiation at hiring
Assessment:
- Quantitative Aptitude: 10Q, 35 min (branch-agnostic)
- Logical Reasoning: 15Q, 25 min (branch-agnostic)
- Verbal Ability: 20Q, 20 min (branch-agnostic)
- Pseudocode (when included): 5Q, 10 min (requires basic programming logic awareness)
Technical Interview:
- OOP concepts at definitional level with examples
- Basic programming in at least one language
- Database and SQL at conceptual level
- Engineering domain project explained technically
- Self-learning since offer (InfyTQ, personal projects)
Mysore Training:
- Duration: 3-6 months depending on stream
- Primary language: Java
- Curriculum: Programming, data structures, DBMS, networking, testing, SDLC
- Assessment-based stream allocation
- Non-IT students with InfyTQ preparation adapt successfully
InfyTQ Priority for Non-IT Students:
- Python Fundamentals + Certification (most important)
- DBMS Certification
- Java Basics
- Data Structures Awareness
Top Domain-IT Career Combinations:
- Mechanical: Manufacturing analytics, industrial IoT, automotive technology
- Civil: Construction tech, smart city solutions, BIM services
- EEE: Smart grid, utilities analytics, power systems simulation
- ECE: Telecom, embedded systems IoT, networking infrastructure
- Chemical: Pharma tech, oil and gas process, lab informatics
- Aerospace: Defense tech, simulation services, CAE
Timeline to Product Company Transition (from joining):
- GCC or tier-2 product company: 15-18 months serious preparation
- Tier-1 product company: 18-24 months serious preparation
- Both timelines assume daily LeetCode practice starting from month 6 onward
Addressing Parent and Family Concerns About Non-IT Students Joining Infosys
Many non-IT students face a specific additional challenge: family members who question why an engineering graduate from a “core” branch is joining an IT company. These concerns are worth addressing with accurate information.
“You studied Mechanical Engineering for four years. Why are you wasting it?”
The engineering foundation is not wasted. Engineering education develops analytical thinking, mathematical reasoning, systematic problem-solving, and the ability to understand complex technical systems. All of these are directly applicable in IT work and are specifically valued in the client contexts where engineering domain knowledge matters. The engineering degree is the foundation; the IT skills being built are the structure on top of it.
“IT is not real engineering.”
Modern software engineering is genuinely engineering: it involves designing systems, managing complexity, making trade-offs under constraints, and delivering functional results. The fact that the material being shaped is software rather than steel or concrete does not make the discipline less rigorous or the work less meaningful.
“You will forget your engineering if you go into IT.”
Engineering domain knowledge, particularly at the industry understanding level (how manufacturing processes work, how structural engineering calculations are made, how power systems operate), is not lost by working in IT. It is supplemented by IT skills and, in the right career context, actively applied. The domain understanding of an engineer who works on manufacturing technology software is actually reinforced by regular engagement with manufacturing clients.
“Core engineering jobs are more stable.”
Employment stability in any sector depends on the demand for specific skills and the health of the industry. IT services companies including Infosys serve clients across all industries and are not more or less stable than any specific engineering sector. The specific stability comparison depends on the local job market for the branch and the specific IT company being compared.
These conversations are part of the reality many non-IT students navigate. Approaching them with accurate information, calm confidence, and genuine respect for the family’s concern (which comes from care, not malice) produces better outcomes than defensiveness or dismissiveness.
Final Note: The Non-IT Engineer’s Unique Advantage
Every non-IT engineer who joins Infosys carries something into the organization that the majority of their batch does not: four years of understanding a physical engineering discipline. This understanding, applied deliberately over a career, is the differentiating asset.
The Indian IT industry has no shortage of CS graduates who can write Java code and implement algorithms. It does have a shortage of professionals who can sit across from a client from a manufacturing, energy, construction, or aerospace company and understand their technical problems at the depth that an engineer from that discipline does. These professionals, when they also have the software and data skills to build solutions to those problems, are genuinely rare and genuinely valuable.
Building toward that profile is not a default outcome of joining Infosys. It is a deliberate career strategy that requires: learning the IT skills seriously in the first three years, maintaining and deepening the engineering domain understanding through the clients you seek, the projects you pursue, and the reading you do outside of work, and positioning yourself explicitly as the combination rather than as a generic IT professional.
The non-IT student reading this guide today has the opportunity to build that combination. The career that results from building it successfully is not a compromise. It is among the most interesting and most rewarded professional profiles that the current Indian technology industry produces.
Frequently Asked: Salary, Growth, and Exit Options for Non-IT Hires
Does an ECE or Mechanical Engineer who joins Infosys as SE have the same promotion criteria as a CS/IT engineer?
Yes. The promotion criteria at Infosys are entirely performance-based and apply identically across all branches. The performance band, the skill certification requirements, the manager’s rating, and the normalized appraisal process do not differentiate by educational background. An ECE engineer and a CS engineer who join in the same batch, receive identical appraisal ratings over three years, and meet the same certification milestones will receive the same promotion timelines.
After five years at Infosys, can a non-IT engineer compete for roles at tier-2 product companies?
Yes. The Infosys experience record, combined with the technical skills built during that time, creates a competitive profile for tier-2 product company applications. The additional preparation needed (DSA to LeetCode Medium level, basic system design) is the same for non-IT Infosys engineers as described in the Product Company Transition guide. The non-IT engineering background is not a disadvantage in product company technical interviews; it may be an advantage in domain-specific roles.
What certifications should a non-IT Infosys engineer prioritize in the first three years?
Year 1: Complete the primary technology certifications for your allocated stream (AWS Cloud Practitioner or equivalent for infrastructure, ISTQB Foundation for testing, Java SE certification for development streams).
Year 2: Add a second-level certification in your primary stream and begin a certification in your engineering domain’s industry technology intersection (SAP for manufacturing/finance, Salesforce for CRM, or domain-specific analytics certifications).
Year 3: If targeting product companies, begin structured LeetCode practice alongside a cloud architect or data engineering certification.
This three-year certification path builds both the internal Infosys appraisal record and the external market profile simultaneously.
This guide is part of the InsightCrunch Infosys Series - the most comprehensive collection of guides for Infosys aspirants available anywhere. The full series covers the hiring process, salary structure, InfyTQ, Power Programmer, Mysore training, career growth, work culture, HackWithInfy, product company transitions, aptitude questions, technical interview, HR interview, offer letter and joining, background verification, placement papers, and this non-IT branches guide.