Project, DBMS, OOP, Coding, Why-Infosys round·Engineering·Easy·20 min

Infosys Systems Engineer Technical Interview — Project, DBMS, OOP, Coding, Why-Infosys

20 min · 1 credit · scorecard at the end
Z
ZeroPitch Research Desk
Updated 2026-05-25 · Newly added · be among the first to take it
Field
Engineering
Company
Infosys
Role
Systems Engineer (Power Programmer entry tier)
Duration
20 min
Difficulty
Easy
Completions
New
Updated
2026-05-25

What this round is about

  • Topic focus. The post-aptitude Infosys Systems Engineer Technical Round, covering final-year project deep-dive with file ownership, DBMS basics (1NF and 2NF and 3NF normalization, JOIN type difference, ACID, primary versus unique versus foreign key), OOP four pillars with examples from YOUR project, one canvas coding problem (string reversal, palindrome, factorial recursion, or largest of three), and a why-Infosys probe with one specific anchor.
  • Conversation dynamic. Karthik Kumar, an 11-year Senior Technology Architect on the Infosys Mysuru GEC panel, is calm and structured. He never raises his voice. After almost every technical answer he asks why did you choose that, or can you give me an example from your own project.
  • What gets tested. Project ownership at file level, DBMS basics under live recall with one SQL written, OOP applied to your own classes, one coding problem written on the canvas and dry-run cleanly for a small input, why-Infosys articulated with one specific anchor like Mysuru GEC or InfyTQ or a named client, and clear yes on the residential training.
  • Round format. Twenty minutes, four blocks, candidate-led on the project, panel-led on DBMS and OOP. Karthik will deliberately push back on one correct answer to test conviction. The whiteboard is on for the coding problem.
  • Time budget. Roughly five minutes on the project deep-dive, six on DBMS and SQL, five on OOP plus the canvas coding problem, and the last four on Why-Infosys plus the Mysuru residential training question. The clock is visible and the panel does not extend for verbose openers.

What strong answers look like

  • Specific module ownership. Name the module YOU built with a file or class name, not what your team built collectively. Name the technology and the alternative you rejected, with a one-sentence reason. Example phrase: I owned the appointment-scheduling module, files AppointmentService.java and AppointmentRepository.java; we picked MySQL over MongoDB because the relationships were already relational.
  • Non-textbook OOP examples. Encapsulation as the private fields on YOUR Patient class, inheritance as YOUR AdminUser extending User, polymorphism as YOUR generateReport behaving differently for PDFReport and CSVReport subclasses. Two sentences per pillar is enough. Karthik will probe for a class or file name on at least two pillars.
  • SQL subquery for second highest salary. SELECT MAX(salary) FROM Employee WHERE salary less than (SELECT MAX(salary) FROM Employee). No LIMIT. Dry-run mentally on five rows where two have the same top salary to show ties are handled.
  • Canvas coding that runs on first dry-run. Reverse a string by index from length minus one down to zero, or factorial recursion with base case n equals zero returns one. Sketch the input HELLO on the canvas first, then write the loop or recursion, then walk through it character by character or call by call.
  • Why-Infosys with one specific anchor. Reference Mysuru GEC residential training, InfyTQ Advanced certification, Power Programmer track and HackWithInfy, or one specific client account like HSBC or Apple Card or Goldman Sachs. One specific reason defended with one sentence beats three generic ones.

What weak answers look like (and how to avoid them)

  • Resume inflation. Listing Spring Boot or Machine Learning without being able to explain dependency injection or model selection. Avoid by removing technologies you cannot defend in two sentences before you walk into the room.
  • Textbook OOP examples. The car-engine polymorphism example or the bank-account encapsulation example as your only example. Avoid by preparing one project-specific example per pillar with the class name before the interview.
  • SQL with LIMIT when asked without LIMIT. Reads as tutorial copy, no internalisation. Practice the subquery form before the interview and dry-run it on a tie case.
  • Frozen on the canvas coding problem. Off-by-one loops you cannot debug, or a recursion with no base case. Avoid by hand-writing reverse-a-string and factorial recursion on paper the week before, dry-running each one for two sample inputs.
  • Generic why-Infosys. Infosys is a good company is the single most cited soft-reject signal. Look up one specific Infosys anchor (Mysuru GEC, InfyTQ, Power Programmer, HackWithInfy, a named client) before the interview and reference it by name.

Pre-interview checklist (2 minutes before you start)

  • Recall your project one-liner. What the system does, who uses it, which module is YOURS by file or class name. Thirty seconds, not three minutes.
  • Pull up the four OOP pillars with project examples. One sentence per pillar, drawn from your final-year project with one class or file name on at least three of them.
  • Have the second-highest-salary SQL on your tongue. Both forms: with LIMIT and the subquery form. Be ready to use only the subquery form, and to dry-run it on rows with ties.
  • Re-read your reverse-a-string and factorial recursion code once. The two most common Infosys canvas problems. Confirm base case for recursion and loop bounds for the string.
  • Identify your one Infosys anchor. Mysuru GEC residential training, InfyTQ Advanced certification, Power Programmer track, HackWithInfy, or one named client like HSBC, Apple Card, Goldman Sachs, JP Morgan, BT, or Reliance Jio. Pick one and remember it.
  • Confirm with yourself: yes to twenty-two weeks Mysuru residential training, yes to relocation across India. No city preference, no hesitation on the residential commitment.

How the AI behaves

  • Probes every technical answer. After almost every answer Karthik asks why did you choose that, or can you give me an example from your own project. Have a one-sentence reason ready every time.
  • No mid-interview praise. He will not say great answer or exactly. He acknowledges with Okay, fine. or Understood. or Right, go on. and pushes deeper.
  • Allergic to textbook examples. If you give the car-engine polymorphism, he will visibly tire and ask for a project example. The bank-account encapsulation triggers the same response.
  • Deliberate pushback once. He will challenge one correct answer during the round, often on the SQL or the OOP, to test your conviction. Defend with reasoning. Capitulating immediately reads as low conviction.
  • Cross-questions resume claims. If you list Spring Boot or Hibernate or Machine Learning, expect a deep follow-up. False statements get exposed and become an instant reject signal.

Common traps in this type of round

  • Project answered at team level. We built a hospital management system instead of I built the appointment-scheduling module, files AppointmentService and AppointmentRepository.
  • OOP definitions without examples from your work. Reciting the textbook definition then stopping. Always pair definition with a one-sentence project example and a class name.
  • SQL with LIMIT when told without LIMIT. A common tutorial habit; practice the subquery form on tie cases.
  • 2NF and 3NF given the same example. Two NF removes partial dependency on a composite key; 3NF removes transitive dependency. Different tables, different problems.
  • Off-by-one or no base case on the canvas code. Common when nervous; dry-run mentally before saying you are done. State your loop bounds or base case aloud before writing.
  • Generic why-Infosys. The most cited soft-reject signal. Name one specific anchor by name and defend it.
  • Hesitating on Mysuru residential training. Twenty-two to twenty-four weeks at Mysuru GEC is non-negotiable for the SE track. A confident yes is expected.

Sample problems you'll face

The 2 problems below are the same ones you'll work through in the live session — no surprises. Read the constraints carefully; the AI persona will refer you to the on-canvas card by problem number.

  1. 1String Reversal Without Built-in

    Write a program to reverse a string without using any built-in reverse function. Pick any language you are comfortable with (C, C++, Java, Python). Walk Karthik through your loop bounds before writing code, then dry-run it for the input HELLO character by character.

    Example inputHELLO
    Example outputOLLEH
    • No built-in reverse function or method (no Python slicing with -1, no StringBuilder.reverse in Java, no strrev in C)
    • Correct loop bounds; Karthik will probe off-by-one cases
    • Dry-run for input HELLO verbally after writing, character by character
    • Use the canvas to sketch the input and the output before writing code; the shape of the output drives the indices
  2. 2Factorial Of N Using Recursion

    Write a function to compute the factorial of N using recursion. Pick any language (C, Java, Python). State your base case aloud before writing code. Dry-run it for N equals four call by call.

    Example inputN = 4
    Example output24
    • Recursive solution only; no for-loop
    • Explicit base case for N equals zero or N equals one
    • Dry-run for N equals four verbally after writing, call by call
    • Use the canvas to sketch the recursion tree if helpful

Interview framework

You will be scored on these 6 dimensions. The full rubric with definitions is below.

Project Ownership
How specifically you name the personal module, the file or class names, the technology chosen, and one rejected alternative when challenged. Team-level we-built answers drop this sharply.
25%
Dbms Recall
How cleanly you explain 2NF and 3NF with separate examples, name the three JOIN types on a concrete schema, define ACID, and write the second-highest-salary SQL as a subquery without LIMIT that dry-runs on ties.
25%
Oop Applied To Project
How many pillars you back with a project example and a class name. Car-engine polymorphism or bank-account encapsulation as your only example drops this sharply.
20%
Canvas Coding Hygiene
How cleanly you write the canvas problem with correct loop bounds or base case, and dry-run it character by character or call by call for a small input.
15%
Why Infosys Specificity
Whether your why-Infosys names one specific anchor (Mysuru GEC, InfyTQ, Power Programmer, HackWithInfy, a named client) and you say clear yes to residential training and relocation.
10%
Resume Defensibility
Whether every technology and project you listed on the resume holds up under two-sentence cross-questioning, with no false claims and no fall-back to I forgot it.
5%

What we evaluate

Your final scorecard breaks down across these dimensions. The full rubric and tier criteria are revealed inside the interview itself.

  • Project Ownership Specificity22%
  • DBMS Recall Under Pressure22%
  • OOP Applied To Own Work20%
  • Canvas Coding Dry Run Discipline15%
  • Why Infosys Specificity10%
  • Mysuru Training And Relocation Clarity6%
  • Resume Defensibility5%

Common questions

What does the Infosys Systems Engineer Technical Round actually test for B.Tech freshers in India?
The Infosys Systems Engineer technical round is a 20 to 30 minute conversation after the online aptitude or InfyTQ certification. It tests five things: your ability to walk through your final-year project file by file and own a specific module, DBMS basics (normalization 1NF and 2NF and 3NF with examples, JOIN type difference, ACID, primary versus unique versus foreign key), the four pillars of OOP with examples from YOUR project (not the textbook car-engine example), one coding question on the canvas (typically string reversal, palindrome, factorial recursion, or largest of three), and a why-Infosys probe. The bar is clarity on basics done correctly at hygiene level, not depth.
How should I structure my answer when the Infosys interviewer asks me to walk through my final-year project?
Open with one sentence on what the system does and who uses it. Then name the specific module YOU built personally, not what your team built collectively, with the file or class name if you remember. Then name the technology you chose for that module and give a one-sentence reason for choosing it over the alternative you considered. Be ready for the follow-up question why did you choose that, which the Infosys interviewer asks after almost every technical answer. If you used Spring Boot, Hibernate, or any Machine Learning library, expect a deep follow-up; if you cannot defend it, the resume entry is hurting you not helping you.
How do I answer the OOP four pillars question without sounding memorised?
Infosys panellists are allergic to the textbook car-engine polymorphism example and the textbook bank-account encapsulation example. Use an example from YOUR final-year project for each pillar. For example: encapsulation as the private fields and public getters on your Patient class in a hospital management project; inheritance as the Admin user inheriting from the base User class; polymorphism as a generateReport method that behaves differently for PDFReport and CSVReport subclasses; abstraction as the AppointmentService interface that hides the database calls from the controller. Two sentences per pillar is enough. Karthik will probe for a class or file name on at least two of the four.
How do I write the SQL query for the second highest salary from an Employee table without using LIMIT in the Infosys interview?
Use a correlated subquery form: SELECT MAX(salary) FROM Employee WHERE salary less than (SELECT MAX(salary) FROM Employee). This works even when there are duplicate top salaries because the inner MAX returns one value and the outer MAX picks the next distinct one. The Infosys panel specifically says without LIMIT because LIMIT is MySQL specific syntax and Infosys clients run Oracle, DB2, and SQL Server alongside MySQL. Be ready to dry-run the query mentally on a five-row sample where two rows have the same top salary, to prove the query handles ties correctly.
What coding problem is most commonly asked in the Infosys SE technical round on the canvas?
The four most common problems are: reverse a string without using built-in reverse functions, check if a number or string is a palindrome, find the factorial of N using recursion, and find the largest of three numbers. Less common but seen: Fibonacci series, prime number check, removing duplicates from an array. Karthik wants you to write the code on the canvas, then dry-run it verbally for a small input like HELLO or 5 or three sample numbers. He cares about three things: do your loops or recursion calls have correct base cases, can you dry-run the code step by step, and do you state the time complexity at hygiene level.
How do I answer the why-Infosys question convincingly in the technical round?
Avoid the generic Infosys is a good company answer; that is the single most common soft-reject signal. Strong answers name one specific Infosys anchor: the Mysuru Global Education Center residential training for 22 to 24 weeks (the world largest corporate university), the InfyTQ Advanced certification path you have already cleared, the Power Programmer track and HackWithInfy contest, or one specific Infosys client such as HSBC, Apple Card, Goldman Sachs, or JP Morgan. One specific reason defended with one sentence beats three generic reasons. If you have already cleared InfyTQ Foundation or Advanced, lead with that as your hook.
What is the Infosys Systems Engineer salary package for the 2026 batch and what does the Power Programmer track pay?
The Infosys Systems Engineer base package for the 2026 batch is approximately 3.6 LPA for the standard SE role. The Digital Specialist Engineer track is around 6.25 LPA, the Specialist Programmer L1 is 10 LPA, and the Power Programmer or Specialist Programmer L2 and L3 range from 6.5 LPA up to 21 LPA for top scorers from HackWithInfy or InfyTQ. Track allocation is decided by your InfyTQ score and the coding round outcome, not negotiation. All freshers receive 22 to 24 weeks of paid residential training at Mysuru GEC before client allocation, plus 12 months service expectation.
Will the Infosys interviewer ask about Mysuru training and relocation, and what is the right answer?
Yes, in almost every Systems Engineer interview. The right answer is a clear yes, I am comfortable with the residential training at the Mysuru Global Education Center for 22 to 24 weeks and with relocation to any Infosys delivery centre in India after training, including Bengaluru, Pune, Hyderabad, Chennai, Bhubaneswar, Chandigarh, or Mangaluru. Saying I prefer Bengaluru only or hesitating on the Mysuru residential commitment is one of the most cited soft-reject signals in Infosys SE reports. The standard service expectation and the bench-to-project allocation model are both expected to be a confident yes.
What does Infosys Mysuru Generic Foundation Training look like for new Systems Engineers?
After clearing all rounds and joining, Systems Engineers go through 22 to 24 weeks of residential Generic Foundation Training (GFT) at the Mysuru GEC on Hebbal Industrial Area Road. The training covers a Java or Python or C-sharp stream, DBMS, web development, software engineering, testing, and a small capstone project. There are weekly tests and a final assessment; confirmation as a permanent SE is linked to clearing the GFT capstone with a minimum score. Most SEs are then allocated through the Lex learning platform to a BFSI, retail, healthcare, or telecom client account across Infosys delivery centres in India.
What are the most common reasons B.Tech candidates fail the Infosys SE Technical Round?
Seven repeating failure patterns: listing Spring Boot or Machine Learning on the resume but unable to explain dependency injection or model selection; giving the textbook polymorphism definition when asked for an example from your own project; confusing 2NF and 3NF or giving the same example for both; writing the second-highest-salary SQL with LIMIT after being told without; freezing on the canvas coding or writing an off-by-one loop; saying I prefer one city only or hesitating on the Mysuru residential training; giving a generic Infosys is a good company answer. False resume claims that the panel cross-questions trigger an instant reject and a six-month profile lock.
How does this AI mock differ from a real Infosys SE Technical Round?
The AI plays Karthik Kumar, a Senior Technology Architect at Infosys Mysuru GEC panel. He never breaks character, never praises, never confirms whether your answer was right. He asks one question at a time, follows up with why did you choose that or can you give me an example from your project after almost every technical answer, and will push back once on a correct answer to test your conviction. The transcript-backed scorecard at the end names the exact moment where your project ownership, DBMS recall, OOP example, or canvas coding was weak. The canvas captures your code so the report can comment on indices and base cases, the kind of feedback no real panellist gives you in time to fix.

Sources this interview is built on

Real candidate-report URLs (Glassdoor / AmbitionBox / PrepInsta / GeeksforGeeks / Medium) reviewed when authoring the questions, persona, and rubric. Verify the realism yourself.