Pseudocode and Sectional Cutoff Pressure round·Engineering·Easy·20 min

Infosys SE Aptitude — Pseudocode and Sectional Cutoff Pressure

20 min · 1 credit · scorecard at the end

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 Infosys SE InfyTQ-style aptitude assessment for SMVEC 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. Anand Kumar, a Senior Systems Engineer at Infosys Mysore Global Education Centre and Initial Learning Programme panel mentor, runs the mock. He is calm and structured, low volume, with a slow Hyderabad-Andhra cadence. He has watched the Pseudocode failure pattern repeat year after year for Tier-2 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). Anand dictates each question line by line and waits silently for you to trace on your scratch sheet. The whiteboard stays off, this is a voice-only mock of an MCQ assessment.
India context. SMVEC Puducherry and similar Tier-2 colleges see 150 to 200 Infosys offers per cycle, second-largest after TCS. 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 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, 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. Anand explicitly logs honest gaps as positive signals.

Pre-interview checklist (2 minutes before you start)

Pull up a scratch sheet. Have an A4 sheet and a pen ready before the mock starts, you will need it 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. Anand asks for the underlying number, not the headline percentage. If you say I would clear it, he asks what is the floor on that section in a number you can defend.
No mid-interview praise. Anand will not say great answer or validate. He acknowledges the specific content of what you said in 5 to 15 words, then probes deeper.
Interrupts on scanning. Anand will pause you with let us slow down if you predict a pseudocode output without tracing on scratch. He will not nudge twice.
Corrects on C-syntax assumption. Anand says this is pseudocode notation not C kindly read the base case as written if you give the C-correct answer on a recursion. He waits silently for you to retrace.
Pushes on sectional cutoff guesses. If you guess a wrong cutoff number, Anand asks you to defend it. If you cannot, he 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.

Interview framework

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

Pseudocode Tracing Discipline

How thoroughly the candidate traces variable state line by line on scratch before predicting output. Single highest-weighted behaviour because Pseudocode decides SE versus SP track.

25%

Syllogism Venn Discipline

Whether the candidate draws a Venn diagram and writes premises in order before checking each conclusion option, rather than picking the gut answer on a four-premise chain.

18%

Sectional Cutoff Awareness

Whether the candidate can name at least two of the four section-specific cutoff thresholds (Math, Reasoning, Pseudocode, Verbal) plus the overall aggregate for the SE track without guessing.

18%

Math Easy-attack Ordering

Whether the candidate picks the easy arithmetic or percentage attack first in Math and defers permutation-combination, rather than starting with the textbook-hardest question.

15%

Verbal Error Naming And Fix

Whether the candidate names which sentence part contains the error and states the correct form, not just selecting the part number on a subject-verb or pronoun-antecedent question.

14%

Honest Gaps Over Guessed Answers

Whether the candidate says I do not know cleanly on items they have not revised, instead of guessing a wrong percentage or a wrong syllogism conclusion. Anand explicitly logs honest gaps as positive.

10%

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

What is the Infosys SE Aptitude exam pattern for the 2026 campus cycle in India?

The Infosys SE Aptitude runs 100 to 120 minutes across four sections on the InfyTQ-style platform. Mathematical Ability has 10 questions in 25 minutes covering percentages, profit-loss, time-work and geometry. Logical Reasoning has 15 questions in 25 minutes covering data interpretation, syllogisms with four-premise chains, blood relations and coding-decoding. Pseudocode has 5 to 10 questions in 10 to 15 minutes predicting the output of loops, recursion, arrays and basic OOP. Verbal Ability has 40 questions in 35 minutes covering reading comprehension, error spotting, sentence completion and para-jumbles. Sectional timing is non-transferable, no negative marking, no section switching allowed.

What is the working sectional cutoff for the Infosys SE track in 2026?

Each of the four sections is independently qualifying. Mathematical Ability sectional cutoff is 50 to 55 percent, typically 5 to 6 of 10 correct. Logical Reasoning sectional cutoff is 50 to 55 percent, typically 8 to 9 of 15 correct. Pseudocode sectional cutoff is 40 to 50 percent, typically 2 to 3 of 5 correct, the lowest threshold because of question difficulty. Verbal Ability sectional cutoff is 45 to 50 percent, typically 18 to 20 of 40 correct. Overall aggregate cutoff is 60 to 65 percent for the SE track and 68 percent for the SP track this cycle, up from 65 percent in December 2025.

Why does the Pseudocode section decide the SE versus SP track at Infosys?

The Pseudocode section is the signature Infosys differentiator versus other IT services exams and the section most-stumbled-on by Tier-2 college candidates. The 5 to 10 questions ask candidates to predict the output of pseudocode snippets covering loops with bitwise and logical operators, recursion with a base case, sorting algorithms like bubble sort and insertion sort, basic data structures, and basic OOP. Power Programmer track is reserved for the top 5 percent of candidates by aptitude score, and pseudocode performance disproportionately decides who moves up to Specialist Programmer or Power Programmer over the default Systems Engineer offer.

What pseudocode question archetypes appear most often in the Infosys SE Aptitude for 2026?

PrepInsta, GeeksforGeeks, Talent Battle and Unstop report consistent archetypes. While-loop trace where a variable starts at one value and increments by another until a condition becomes false (predict the final printed value). Recursive factorial-like or sum-like function with a base case the candidate has to unwind mentally. Sorting algorithm partial trace where bubble sort has run two passes on a five-element array and the candidate predicts the array state. Conditional with modular arithmetic where the candidate predicts which branch executes. Class inheritance with method override where the candidate predicts which method runs at the call site.

What is the difference between InfyTQ certification and the Infosys SE Aptitude assessment?

InfyTQ is a free online platform run by Infosys on infytq.com that provides structured programming and software development learning, plus acts as a direct hiring channel for the SP and DSE tracks. InfyTQ certification is a prerequisite filter for SP-track applicants. The Infosys SE Aptitude assessment is the four-section qualifying test (Math, Reasoning, Pseudocode, Verbal) that all Systems Engineer applicants take during the campus drive, regardless of whether they have InfyTQ certification. The SE Aptitude score plus the technical and HR interviews determine SE-versus-SP-versus-PP track allocation.

What programming languages should I know for the Infosys Pseudocode section in 2026?

The Pseudocode section uses Infosys pseudocode notation, not any specific language syntax. Candidates with strong C, C plus plus, Java or Python background often underperform on Pseudocode because they assume the syntax matches their language and read past the off-by-one or the base-case mis-statement. The right preparation is to practise tracing variable state line by line on scratch paper using only pseudocode notation, ideally for four weeks of dedicated practice on PrepInsta and GeeksforGeeks Pseudocode quizzes. Knowing C helps with reading but not with output prediction under timed conditions.

What are the most common reasons SMVEC and other Tier-2 college candidates fail the Infosys SE Aptitude?

The most common rejection signals are ignoring sectional cutoffs and chasing overall score (failing one section by 1 to 2 marks despite a 70-plus percent aggregate), attempting permutation-combination first in Math and running out of time on easy arithmetic, spending 14 minutes on one data interpretation set and rushing four-premise syllogisms, assuming Pseudocode is easy because the candidate knows C and missing the off-by-one in the pseudocode notation, selecting cannot-be-determined on recursion questions without fully tracing the base case, and practising only IndiaBix C-syntax problems two days before the drive instead of four weeks of dedicated pseudocode practice.

How does Infosys SE 3.6 LPA compare with TCS Ninja, Wipro Elite, Cognizant GenC and Accenture ASE for 2026 freshers?

Infosys SE sits in the middle of the Tier-1 IT services band at around 3.6 LPA. TCS Ninja is around 3.36 LPA with a 1-year service bond. Wipro Elite NTH is around 3.5 LPA with a 15-month bond. Cognizant GenC is around 4.0 LPA. Accenture ASE is around 4.5 LPA. Infosys's edge is the structured six-month Mysore Initial Learning Programme, the 30,000-plus annual fresher hiring volume, and the path from SE to SP to Power Programmer (9 to 11 LPA) for top performers via InfyTQ certification. Power Programmer is reserved for the top 5 percent of candidates by aptitude score.

Is sectional time switching allowed during the Infosys SE Aptitude in 2026?

No. Time per section is non-transferable. Once a section is submitted the candidate cannot return to it, and unused time in one section cannot be moved to another. The order of section attempt is fixed (Mathematical Ability, Logical Reasoning, Pseudocode, Verbal Ability in the 2026 cycle). There is no negative marking but sectional cutoff is applied independently to each section. Candidates who skip mock tests with strict sectional timing consistently report time-management failures on the actual test day.

What is the recommended preparation timeline for the Infosys SE Aptitude for SMVEC candidates?

Six to eight weeks of structured preparation is the consistent pattern among candidates who clear sectional cutoffs. Week 1 to 2 covers quantitative arithmetic fundamentals (percentages, profit-loss, time-work, time-speed-distance). Week 3 to 4 covers logical reasoning patterns (syllogisms, blood relations, data interpretation). Week 5 is dedicated entirely to Pseudocode, the most-stumbled-on section for Tier-2 candidates. Week 6 covers verbal reading comprehension and grammar. The final one to two weeks are full-length mock tests with strict sectional timing using PrepInsta, GeeksforGeeks and Unstop materials.

How does the Infosys SE Aptitude differ from the TCS NQT for SMVEC candidates?

Both are qualifying aptitude assessments for the Tier-1 IT services campus drive but the section mix differs. TCS NQT has 90 to 180 minutes with verbal ability, reasoning ability, numerical ability, programming logic MCQs and 2 hands-on coding problems. Infosys SE Aptitude has 100 to 120 minutes with Mathematical Ability, Logical Reasoning, Pseudocode (output prediction, not coding) and Verbal Ability. Infosys does not require candidates to write actual code in the aptitude; TCS does. The Infosys Pseudocode section is the unique differentiator and the section Tier-2 candidates most stumble on. Both have sectional cutoffs and strict timing.

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.