Infosys SE Aptitude for ACET — Pseudocode and Sectional Cutoff Pressure
- Field
- Engineering
- Company
- Infosys
- Role
- Systems Engineer (Power Programmer entry tier)
- Duration
- 20 min
- Difficulty
- Easy
- Completions
- New
- Updated
- 2026-05-27
What this round is about
- Topic focus. The Infosys SE InfyTQ-style aptitude assessment for ACET Achariya Puducherry freshers, compressed into 20 minutes of focused practice. Covers one Mathematical Ability triage item, one Logical Reasoning four-premise syllogism, two Pseudocode output-prediction traces (the signature differentiator that decides SE versus SP versus Power Programmer track), and one Verbal Ability error-spotting beat with a reflection on your sectional pacing plan.
- Conversation dynamic. Divya Karthikeyan, a Senior Systems Engineer at Infosys Mysore Global Education Centre and Initial Learning Programme panel mentor, runs the mock. She is calm and structured, low volume, with a Coastal Tamil Nadu cadence. She has watched the Pseudocode failure pattern repeat year after year for Tier-2 and Tier-3 college candidates and will push you to trace variable state on scratch before any output prediction.
- What gets tested. Reading the question fully before answering, picking the easy attack first in Math, drawing a Venn diagram before picking a syllogism conclusion, tracing pseudocode variable state line by line on scratch (NOT scanning), reading pseudocode notation as written and not as C syntax, naming at least two sectional cutoffs for the SE track, and stating both the error part and the fix on a Verbal item.
- Round format. Twenty minutes, four blocks, panel-led on all four sections in order (Math, Reasoning, Pseudocode, Verbal). Divya dictates each question line by line and waits silently for you to trace on your scratch sheet. The canvas is open for you to sketch your Venn diagram and trace pseudocode variable state line by line, you can draw, write or freehand and the AI sees your work.
- India context. ACET Puducherry and similar Tier-2 and Tier-3 colleges see significant Infosys SE intake each cycle as a top tier-1 IT services offer above their roughly 2.75 LPA campus average. The InfyTQ-style assessment runs back-to-back across four sections with non-transferable time, mirroring the real Infosys campus drive funnel that converts roughly one in three attendees to the technical interview round.
What strong answers look like
- Pseudocode tracing on scratch first. You write the variable state line by line on your scratch sheet or canvas before predicting the output, naming the value of the loop variable after each iteration and identifying the exact iteration where the condition first becomes false. You sound like you wrote it before you said it.
- Pseudocode notation read as written. You read the recursion base case in pseudocode notation, not as C syntax. You say things like the page returns 1 when n equals 1, not the C-correct version. You name one notational difference (assignment operator, base case syntax, output statement) that catches Tier-2 candidates.
- Venn drawn before syllogism conclusion picked. You draw the three-circle Venn on your sheet or canvas, label each circle, write the four premises in order, then check each conclusion option against the diagram one at a time. You name which option was the standard trap (undistributed middle term, illicit major).
- Sectional cutoffs memorised, not guessed. You name at least two of the four section thresholds for the SE track (Math 50 to 55 percent, Reasoning 50 to 55 percent, Pseudocode 40 to 50 percent, Verbal 45 to 50 percent) plus the overall 65 plus percent aggregate. You say which section you would deliberately rush to bank time for Pseudocode.
- Verbal error named with the fix. You name which sentence part contains the error AND state the correct form (the singular subject takes a singular verb, the pronoun should agree with its antecedent), not just the part number. You name the grammar rule that is broken.
What weak answers look like (and how to avoid them)
- Scanning the pseudocode and assuming the output. Tier-2 candidates lose Pseudocode by scanning the snippet, seeing a familiar shape (a for loop, a recursion), and assuming the output without tracing. Fix: pause for one beat, write variable state on scratch, name the loop variable after each iteration.
- Treating pseudocode as C syntax. Candidates who know C well often underperform because they assume the syntax matches and read past the off-by-one in the base case. Fix: read the base case as written on the screen, not as you would write it in C, and notice the deliberate off-by-one before unwinding.
- Picking the syllogism conclusion without a Venn. Picking by gut on a four-premise chain misses undistributed middle terms. Fix: draw the three-circle Venn, write the premises in order, then check each conclusion against the diagram.
- Hedging on sectional cutoffs. Saying I will figure out time management on the day means you have not memorised the thresholds. Fix: walk in knowing Math 50 to 55, Reasoning 50 to 55, Pseudocode 40 to 50, Verbal 45 to 50, Overall 65 plus, before the drive.
- Selecting a sentence part without the fix. Picking part number two without stating what the correct form should be signals memorisation, not grammar understanding. Fix: practise saying the part AND the fix in the same breath.
- Guessing a wrong sectional cutoff number. Saying I think it is 70 percent or something when you have not memorised it is worse than saying I do not know. Divya explicitly logs honest gaps as positive signals.
Pre-interview checklist (2 minutes before you start)
- Pull up a scratch sheet or open the canvas. Have an A4 sheet and a pen ready before the mock starts, or use the on-screen canvas for pseudocode traces and the syllogism Venn diagram.
- Recall the four sectional cutoffs. Math 50 to 55 percent, Reasoning 50 to 55 percent, Pseudocode 40 to 50 percent, Verbal 45 to 50 percent, Overall 65 plus for SE, 68 percent for SP this cycle.
- Identify which section worries you most. Be ready to name it in your one-minute self-introduction (Pseudocode is the typical Tier-2 answer).
- Re-read one PrepInsta pseudocode snippet. Trace one while-loop output once, and one recursion base case once, just before the mock to warm up the line-by-line muscle.
- Pull up your preferred verbal grammar source. Whether PrepInsta verbal pages or GeeksforGeeks Infosys verbal, have one tab open in case you want to revise subject-verb agreement after the mock.
- Have your time-management plan ready. Know which section you will rush (typically Math) to bank time for Pseudocode, and which topic you will defer in each section.
How the AI behaves
- Probes every claim. Divya asks for the underlying number, not the headline percentage. If you say I would clear it, she asks what is the floor on that section in a number you can defend.
- No mid-interview praise. Divya will not say great answer or validate. She acknowledges the specific content of what you said in 5 to 15 words, then probes deeper.
- Interrupts on scanning. Divya will pause you with let us slow down if you predict a pseudocode output without tracing on scratch. She will not nudge twice.
- Corrects on C-syntax assumption. Divya says this is pseudocode notation not C kindly read the base case as written if you give the C-correct answer on a recursion. She waits silently for you to retrace.
- Pushes on sectional cutoff guesses. If you guess a wrong cutoff number, Divya asks you to defend it. If you cannot, she prefers an honest I have not memorised that one over a guess.
Common traps in this type of round
- Predicting pseudocode output by pattern recognition. Scanning the snippet and assuming the output by familiar shape (a for loop, a recursion) instead of tracing variable state line by line on scratch.
- Assuming pseudocode is C. Reading the base case as you would write it in C, missing the deliberate off-by-one in the pseudocode notation, giving the C-correct answer instead of the pseudocode-correct one.
- Picking the loop boundary as a equals 7 stops the loop. Missing the next iteration where a equals 10 fails the less-than condition (the loop runs while a is less than 10, so a equals 10 is the first iteration where the condition becomes false).
- Picking the syllogism conclusion that matches the gut. Without drawing the three-circle Venn on the scratch sheet, the undistributed middle term traps you on the four-premise chain.
- Attempting permutation-combination first in Math. Running out of time on easy arithmetic that would have cleared the cutoff because the textbook-hardest question ate the budget.
- Hedging on the 1-year service bond awareness. While this is more an HR-round trap, candidates often confuse the Infosys SE 1-year bond with the TCS NQT 1-year bond, or with the Wipro Elite 15-month bond. Walk in knowing it is 1 year for Infosys SE.
- Selecting cannot-be-determined on a recursion question. Picking cannot-be-determined without fully unwinding the call stack is a Tier-2 failure pattern. Trace each call to the base case before picking.
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.
- 1While Loop Pseudocode Trace
Pseudocode: integer a = 4, integer b = 3. WHILE a < 10 DO a = a + b END. PRINT a. Predict the final value printed by trace, not by pattern recognition.
Example inputInitial a = 4, b = 3Example output10- Trace variable state line by line on the canvas before predicting.
- Name a after every iteration until the loop condition first becomes false.
- Do NOT assume C syntax, this is Infosys pseudocode notation.
- Use the canvas to trace each iteration. The AI sees your variable state trace.
- 2Recursive Function Output Trace (deliberate off-by-one)
Pseudocode: FUNCTION f(n) IF n == 1 RETURN 1 ELSE RETURN n * f(n-1) END. Called as f(5). Predict the output by reading the base case as WRITTEN, not as you would write it in C. Note the base case is n == 1, not n == 0.
Example inputf(5)Example output120- Unwind the call stack on the canvas: f(5) calls f(4) calls f(3) and so on.
- Stop at the base case as the page declares it (n == 1 returns 1).
- Do NOT substitute C factorial intuition.
- Use the canvas to draw the call stack unwinding. The AI sees your unwound stack.
Interview framework
You will be scored on these 6 dimensions. The full rubric with definitions is below.
What we evaluate
Your final scorecard breaks down across these dimensions. The full rubric and tier criteria are revealed inside the interview itself.
- Pseudocode Tracing Discipline25%
- Syllogism Venn Discipline18%
- Sectional Cutoff Awareness18%
- Math Easy-Attack Ordering15%
- Verbal Error Naming and Fix14%
- Honest Gap Signalling Over Guessed Answers10%
Common questions
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.
- Infosys Aptitude Test Pattern 2026 PrepInstaprepinsta.com
- Infosys Pseudo Code Questions and Answers 2026 PrepInstaprepinsta.com
- Infosys Syllabus 2026 Online Test Pattern PrepInstaprepinsta.com
- Infosys Pseudocode Questions Quiz GeeksforGeeksgeeksforgeeks.org
- Infosys Interview Questions 2026 InfyTQ Tech HR Decoded OphyAIophyai.com
- Infosys Recruitment 2026 Process Eligibility Rounds Salary Unstopunstop.com
- How to prepare for Infosys The Complete Guide GeeksforGeeksgeeksforgeeks.org
- ACET Placements Pageacet.edu.in