Wipro Interview Questions and Answers

Answer

Elite NTH is the main fresher hiring gate for graduating engineers and it operates as a funnel rather than a single test. As of 2026 candidates typically describe the online assessment as three distinct parts sitting inside one sitting: an aptitude block covering quantitative ability, logical reasoning, and English usage; a written communication test where you type a piece of prose on a given topic against a stated word count; and a coding section with a small number of problems solved in an online editor. Clearing all of it leads to a technical interview and then a business discussion that also serves as the HR round.

The exact section counts, timings, and marking rules have varied between cycles and between campus and off campus drives, so read your instruction screen rather than a coaching PDF from an earlier batch. The reason candidates who look well prepared still fail is that they prepared for one third of the assessment. Aptitude is the part everyone drills, the written communication test is the part almost nobody practises, and the coding section is where people who only ever wrote pseudocode discover they cannot handle standard input. Prepare all three or the strongest block cannot save you.

Answer

Assume sections are individually timed and that once a section closes you cannot return to it, because that is how these assessments are typically run and it dictates your whole strategy. Budget your seconds per question before a section opens and enforce it mechanically rather than deciding live. Set a hard walk away rule: if a question has taken more than about ninety seconds and you still cannot see the path, mark it and move.

The most common way a capable candidate fails is not weakness, it is spending seven minutes on one number system question and then rushing eight easy ones in the final four minutes. Work two passes: sweep the section taking everything you can solve confidently, then return with the remaining time for the heavy items. If a section closes with questions unattempted, put it down immediately, because the next block is scored independently and a demoralised candidate loses far more in the following twenty minutes than they lost in the last two.

This matters more in Elite NTH than in a pure aptitude paper, because the written communication test and the coding section both come after the aptitude block and both need a clear head. Practise on a timer for at least ten full sections, since pacing is a trained reflex rather than a decision.

Answer

Marking rules have differed across cycles and even between sections of the same assessment, so read the instruction screen on the day rather than assuming. The decision framework is identical either way. With no negative marking, never leave a question blank: keep the last thirty seconds of every section free purely to sweep and mark something on everything unattempted.

With negative marking, apply elimination discipline, guess only after ruling out at least two options because that turns a one in four gamble into a favourable bet, and skip cleanly when you can eliminate nothing. The costliest error is emotional guessing on a hard question you have already invested four minutes in, because the sunk time makes you unwilling to walk away and that one question then costs you three easy ones you never reached. Decide your rule before the test and follow it without renegotiating it under pressure.

Also worth knowing: most candidates lose more marks to misreading than to guessing, particularly on items asking for the value that is not true, or asking for the remaining quantity when you computed the used quantity. Underline what is actually being asked before you compute anything, which costs two seconds and saves whole questions.

Answer

Alongside the standard Elite entry, Wipro has in several cycles run a higher band route for freshers, marketed at times under the Turbo banner. The essential difference is that it is a separate and harder assessment aimed at candidates who want the higher package, and clearing it routes you into a different offer rather than simply giving you a better score on the same one. What candidates describe as harder is depth rather than breadth: more demanding quantitative and logical items, and a coding section that expects genuinely working solutions with attention to complexity and edge cases rather than partial attempts.

The compensation gap is the whole reason to care about it. Reported figures vary by year, batch, degree, and location, but candidates commonly describe the standard Elite offer near ₹3.5 LPA and the higher band route near ₹6.5 LPA. Treat those as reported ranges, never quote them in an interview as if they were policy, and confirm what applies to your own drive.

Strategically, if a higher track is open to you and your coding is reasonable, attempt it, because no negotiation afterwards will close a gap of that size. What you must not do is sacrifice preparation for the standard route to chase it.

Answer

The recurring set is narrow enough to drill to reflex: percentages, profit and loss, ratio and proportion, averages and mixtures, time speed and distance including boats and trains, time and work, simple and compound interest, number systems with HCF, LCM, remainders and divisibility, basic permutation and combination, probability, mensuration, and data interpretation. What is being measured is arithmetic economy under a clock rather than mathematics. Learn the conversions so you stop doing long division: 12.5 percent is one eighth, 16.67 percent is one sixth, 37.5 percent is three eighths.

Use the successive change formula rather than computing two stages separately. Treat total work as the LCM of the individual times so you work in whole units instead of fractions. Back solve from the options whenever the algebra looks longer than the arithmetic.

Memorise squares to thirty, cubes to fifteen, and reciprocals to twenty. The preparation mistake that wastes the most time is solving a thousand random questions. Solve two hundred and record, for every mistake, whether it was a concept gap, a calculation slip, or a misread. Nearly everyone finds one category dominating the log, and fixing that one category is where the marks actually sit.

TIME AND WORK, the LCM method

A finishes in 20 days, B in 30 days, together?

1. Total work = LCM(20, 30) = 60 units
2. A's rate   = 60 / 20 = 3 units per day
3. B's rate   = 60 / 30 = 2 units per day
4. Combined   = 5 units per day
5. Time       = 60 / 5 = 12 days

BOATS AND STREAMS

  downstream = boat + stream
  upstream   = boat - stream
  boat  = (downstream + upstream) / 2
  stream = (downstream - upstream) / 2

SUCCESSIVE PERCENTAGE CHANGE

  Net = a + b + (a * b / 100)
  Up 20 percent then down 25 percent:
  20 + (-25) + (20 * -25 / 100) = 20 - 25 - 5 = -10 percent

ALLIGATION, for averages and mixtures

  (cheaper quantity) : (dearer quantity)
  = (dearer price - mean) : (mean - cheaper price)

Answer

Reasoning is usually the most clearable block for a prepared candidate because the question types are finite. Expect seating arrangements both linear and circular, blood relations, coding and decoding, syllogisms, direction sense, number and alphabet series, statement and conclusion, data sufficiency, and figure or pattern based items. The gap between a fast solver and a slow one is diagramming discipline, not intelligence.

For seating arrangements, draw the frame first, fill in only definite information, and mark uncertain positions with an option list rather than committing to a guess you will later have to unwind. For blood relations, use a symbol convention you never vary, plus for male, minus for female, a horizontal line for spouse, a vertical for parent to child. For syllogisms, draw Venn diagrams and then test the conclusion in every valid arrangement rather than only the first one you drew, because testing a single arrangement is the single most common error in this section.

For alphabet series, memorise the position anchors, E is 5, J is 10, O is 15, T is 20, Y is 25, and the questions collapse into arithmetic. Nobody will ask you a syllogism in the interview, so this block is a pure marks opportunity and the cheapest section to improve in two weeks.

Answer

They test different abilities and need separate preparation, and confusing them is why candidates with good English scores still fail the writing test. The English block inside the aptitude section is recognition based: reading comprehension, sentence completion, error spotting, para jumbles, synonyms and antonyms, and article and preposition usage, all answered by choosing an option. The written communication test is production based, meaning you have to generate correct English yourself, structure it, and finish inside a word count while a timer runs.

Recognition and production are genuinely different skills, which is why option based practice alone leaves you exposed. Losses in the recognition block cluster in three predictable places. Articles and prepositions, because they are learnt by exposure rather than by rule and Indian regional English carries settled habits the test marks wrong.

Subject verb agreement across long sentences where a clause separates subject from verb. And reading comprehension, not because the passages are hard but because candidates read them fully and carefully and then run out of time; read the questions first, scan for the location, and read closely only around it. For grammar, work through error spotting sets and write down the exact rule you broke each time, because your errors repeat across only eight or ten rules.

Answer

Data interpretation is where prepared candidates lose the most minutes, and almost never because the arithmetic is hard. Time vanishes in three specific places. First, reading the chart before reading the question, which means you absorb data you will never use; read the question first, then go to the chart for exactly the two numbers you need.

Second, computing exact values when the options are far apart, where approximation would have settled it in a quarter of the time; if the options differ by more than about ten percent, round aggressively and pick. Third, missing the units and the scale line, so you compute in thousands when the chart is in lakhs, which produces a confidently wrong answer that costs you the mark and the time. Add two habits.

Percentage change questions are far faster as a ratio than as a subtraction and division, so train yourself to see 240 against 200 as 1.2 and therefore twenty percent up rather than doing the long form. And when a set has four questions attached to one chart, do them together while the chart is loaded in your head instead of returning later, because reloading the context costs almost as much as solving. If a set is a pie chart nested inside a table, consider skipping it entirely on a first pass.

Answer

The written communication test is the most distinctive part of the Elite NTH assessment and the part candidates are least ready for. It exists because a multiple choice English section only proves you can recognise correct English, while the job requires you to produce it: status updates to a client, defect descriptions, handover notes, and email that a stakeholder in another country will read without you present to explain it. So you are given a topic and asked to type a piece of prose within a stated word count while a timer runs.

What is being scored is not literary quality. Candidates consistently describe the same criteria: whether you addressed the topic given, whether the piece has visible structure, whether grammar and spelling hold up, whether sentences are clear rather than ornate, and whether you respected the word count and actually finished. Two candidates with identical ideas score differently purely on structure and spelling.

The right mental framing is that this is a business writing test wearing an essay costume, so write the way you would write to a client, plain, organised, and finished, rather than the way you wrote in a school examination. A weak submission is three long unbroken paragraphs of opinion. A strong one is short paragraphs, each doing one job.

Answer

Word counts and durations reported by candidates vary between cycles, commonly falling in the range of a couple of hundred words inside a short fixed window, so confirm the exact numbers on your instruction screen and then work to a fixed template rather than improvising. The template that survives a timer has four blocks: a two sentence opening stating your position, two body paragraphs each carrying one point plus one concrete example, and a two sentence close that restates the position and adds a forward looking line. Allocate the clock before you type, roughly the first tenth of the time planning, the next seven tenths writing without editing, and the final fifth reading back for spelling and sentence breaks.

That read back is not optional, it is where the cheapest marks in the whole assessment are, because spelling and agreement errors are counted mechanically and take seconds to fix. Write to the middle of the permitted range rather than to the ceiling, since a piece that overruns and is cut mid sentence looks unfinished and one far under looks thin. Count in blocks rather than word by word, roughly forty words per short paragraph, and keep sentences under about twenty words, because long sentences are exactly where grammar collapses under time pressure.

WORKED OUTLINE
Topic: Should companies allow employees to work from anywhere?

BLOCK 1, OPENING (about 40 words)
  Sentence 1: state the position plainly.
    "Work from anywhere suits experienced employees far better than it suits
     new joiners, and companies should set the policy by experience level."
  Sentence 2: signal the two reasons you are about to give.

BLOCK 2, BODY POINT ONE (about 60 words)
  Claim: new joiners learn by observation rather than by documentation.
  Example: a fresher who overhears a production issue being debugged learns
           more in one hour than in a week of reading a runbook.

BLOCK 3, BODY POINT TWO (about 60 words)
  Claim: distributed teams need written discipline that most teams lack.
  Example: a decision taken in a corridor is never written down, so a remote
           colleague finds out two days later and rebuilds the same thing.

BLOCK 4, CLOSE (about 40 words)
  Restate the position in different words, not the same words.
  Add one forward looking line: an office based first year, flexibility after.

TIME PLAN on a 20 minute timer
  0 to 2    type the four block stubs into the answer box
  2 to 16   expand each stub, writing straight through with no editing
  16 to 20  one read back for spelling, agreement, and paragraph breaks

Answer

Topics are typically general and opinion based rather than technical, drawn from familiar ground such as technology and society, work culture, education, the environment, social media, or a current general interest theme. You are not being tested on domain knowledge, which is precisely why an unfamiliar topic is survivable. The failure is behavioural rather than intellectual: candidates freeze, burn six of twenty minutes deciding what they think, then write in a panic and run out of time.

Have a recovery procedure ready. Take a position within thirty seconds and commit, because either side scores equally and all the marks are in the structure. If you know nothing specific, argue from principles you always have, cost, fairness, time, risk, and learning, all of which apply to nearly any topic.

Use an example from your own life instead of inventing a statistic, because a fabricated figure reads as false while a personal example never can, and a line beginning 'in my college the same problem appeared when' is permanently available to you. If the topic genuinely has two defensible sides, say so in the opening, argue the stronger one, concede a single point to the other, and close, which is a legitimate and well structured piece. Silence sinks candidates here, not ignorance.

Answer

The recurring list is short and every item on it is avoidable. Spelling errors, the cheapest marks to lose and the easiest to recover in a read back, with the worst offenders being words you use constantly, receive, definitely, separate, occurred, environment, government, and business. Subject verb agreement across long sentences.

Tense drift, starting in the present and sliding into the past halfway through. Missing paragraph breaks, which turns a well argued piece into an unreadable block and is scored as poor structure even when the content is fine. Overwriting, meaning ornate sentences and vocabulary you are not fully in control of, because a misused long word damages you more than a plain accurate one.

Not answering the actual topic, which happens when a candidate writes the piece they prepared instead of the one they were given. Running past the word limit so the text is truncated mid sentence, or stopping far short so it reads as thin. And chat register, contractions everywhere, an informal opening, or an abbreviation such as 'etc' doing the work a real example should have done. Fix the mechanical errors with a disciplined read back and you are ahead of most of the pool without writing any better than you already do.

Answer

Practise the constraints rather than the platform. Set a timer to the duration you expect, open a plain text editor with spell check switched off, take a topic from a list you did not write yourself, and type to the word count without stopping. Switching spell check off matters more than anything else you do, because assessment editors usually will not correct you and candidates who always write under a red underline safety net have no idea how many words they genuinely misspell.

Do this eight to ten times over two weeks and keep every attempt in one folder. After each one do two things: count the words to see how badly you estimate length, and mark every error in a different colour and tally the error types. Almost everyone finds three or four errors repeating, and fixing exactly those is a bigger score improvement than reading a grammar book cover to cover.

Check your typing speed too, because below roughly twenty five to thirty words per minute the timer will beat you regardless of how good your English is, and that is fixable in two weeks of daily drills. Finally, read one well written business article a day, not for the content but for sentence length, because imitating plain professional prose is the fastest route to a clean piece.

Answer

The coding section is a small number of problems solved in a browser based editor against hidden test cases, typically with a choice of languages including C, C plus plus, Java, and Python. Scoring is commonly per test case rather than all or nothing, which changes your strategy completely: a partially correct solution handling the common cases is worth far more than an empty editor, so always submit something that compiles and runs even if you know it is incomplete. The most avoidable failure in this round is not algorithmic, it is input and output handling.

Candidates lose everything because they wrote a function and never read from standard input in the exact format specified, or because they printed a friendly prompt such as 'Enter the number of elements', which the automated checker counts as wrong output. Read the sample input and output block character by character and match it exactly, including whether values are space separated or on separate lines and whether the output ends with a newline. The second most avoidable failure is skipping the trivial edge cases, empty input, a single element, all elements equal, and negative numbers.

Write your solution, then spend one minute walking those four cases mentally before you submit. If time remains, test rather than refactor.

Answer

This is a staple of Indian service company coding rounds because the naive solution is obvious and the good solution reveals whether you think about data structures. The naive approach compares every character against every other, which is O(n squared) and will time out on the large hidden test case. The expected approach is two passes with a frequency map: count every character in the first pass, then walk the string again in order and return the first character whose count is one.

That is O(n) time and O(k) space where k is the alphabet size, and stating both complexities out loud before you type is itself scored. The follow ups are predictable, so pre empt them. Does case matter, is 'A' the same character as 'a'?

What should be returned when every character repeats, a sentinel, a null, or an exception, and you should state your contract rather than let the function fall through. If the input is guaranteed lowercase English letters, can you use a fixed array of twenty six counters instead of a hash map, which removes hashing overhead entirely and is the answer the interviewer is fishing for. And the streaming variant: if characters arrive one at a time and you must answer at any moment, you need a queue plus a count map, which is the genuinely interesting version of this problem.

PYTHON, two passes with a frequency map

def first_non_repeating(s):
    counts = {}
    for ch in s:
        counts[ch] = counts.get(ch, 0) + 1
    for ch in s:
        if counts[ch] == 1:
            return ch
    return None            # state your contract explicitly

print(first_non_repeating("swiss"))     # w
print(first_non_repeating("aabbcc"))    # None

JAVA, fixed 26 slot array when input is lowercase letters only

static char firstNonRepeating(String s) {
    int[] freq = new int[26];
    for (char c : s.toCharArray()) freq[c - 'a']++;
    for (char c : s.toCharArray()) if (freq[c - 'a'] == 1) return c;
    return '\0';
}

Complexity: O(n) time in both passes, O(1) extra space for a fixed alphabet.
Naive nested loop version is O(n squared) and times out on large inputs.

Answer

Output prediction questions appear because they test whether you understand what the runtime does rather than what the syntax looks like, and this particular snippet packs two of the most asked traps into eight lines. The first is string comparison. String literals are interned into a shared pool, so two variables assigned the same literal point at the same object and reference comparison returns true, while a string created with the new keyword is a fresh object on the heap and reference comparison against the literal returns false even though the contents are identical.

The lesson the interviewer wants stated is that you compare strings with equals, never with the reference operator, and that this is one of the most common defects in production Java written by beginners. The second trap is integer caching. Boxed Integer values in a small range, conventionally minus 128 to 127, are cached and reused, so reference comparison of two boxed 127 values returns true while two boxed 128 values return false.

Both behaviours look arbitrary until you know the mechanism, which is exactly why they are asked. The follow up is almost always 'so how do you compare boxed integers correctly', and the answer is equals, or compare the unboxed primitive values. A weak answer guesses true or false without naming the pool or the cache.

public class Test {
    public static void main(String[] args) {
        String a = "wipro";
        String b = "wipro";
        String c = new String("wipro");

        System.out.println(a == b);        /* line 1 */
        System.out.println(a == c);        /* line 2 */
        System.out.println(a.equals(c));   /* line 3 */

        Integer x = 127, y = 127;
        Integer p = 128, q = 128;

        System.out.println(x == y);        /* line 4 */
        System.out.println(p == q);        /* line 5 */
    }
}

OUTPUT
  line 1  true
  line 2  false
  line 3  true
  line 4  true
  line 5  false

WHY
  1. Both literals are interned, so a and b are the same object.
  2. new String() allocates a fresh heap object, references differ.
  3. equals compares contents, so it is true.
  4. Boxed values in the small cached range reuse the same object.
  5. 128 is outside that cached range, so two distinct objects are created.

THE RULE TO STATE
  Compare object contents with equals. Reference comparison on wrappers and
  strings is a defect waiting for a value outside the cache to expose it.

Answer

These two are the most asked SQL questions in Indian service company interviews and they are usually asked together because both hinge on the same idea. For the Nth highest salary the panel is testing three layers. Whether you can write it at all.

Whether you handle ties, because if two people share the top salary, does second highest mean the second distinct value or the second row, and you should ask that before writing anything. And whether you handle the empty case, because the subquery form returns NULL cleanly while a LIMIT with OFFSET form returns no row at all, and those behave differently in application code. Give the window function version with DENSE_RANK because it generalises instantly from second to Nth, and be ready to explain RANK against DENSE_RANK against ROW_NUMBER on tied values, since that follow up is guaranteed.

For duplicate removal, the naive answer of a GROUP BY into a new table is acceptable but the interviewer wants the in place version using ROW_NUMBER partitioned by the duplicate defining columns, deleting every row where the row number is greater than one. Always ask what makes two rows duplicates, because 'all columns' and 'same email' are different problems with different queries. A weak answer memorises one query and cannot adapt when the definition changes.

/* Nth highest salary, generalises by changing the rnk value */
SELECT DISTINCT salary
FROM ( SELECT salary,
              DENSE_RANK() OVER (ORDER BY salary DESC) AS rnk
       FROM   employee ) t
WHERE rnk = 3;

/* Portable second highest, returns NULL when there is no second salary */
SELECT MAX(salary) AS second_highest
FROM   employee
WHERE  salary < (SELECT MAX(salary) FROM employee);

/* Tie behaviour on salaries 90000, 90000, 75000 */
/*   RANK()       gives 1, 1, 3                  */
/*   DENSE_RANK() gives 1, 1, 2                  */
/*   ROW_NUMBER() gives 1, 2, 3                  */

/* Delete duplicates in place, keeping the first row of each group */
WITH ranked AS (
  SELECT id,
         ROW_NUMBER() OVER (PARTITION BY email ORDER BY id) AS rn
  FROM   customer
)
DELETE FROM customer
WHERE id IN (SELECT id FROM ranked WHERE rn > 1);

/* Find the duplicates before deleting anything */
SELECT email, COUNT(*) AS occurrences
FROM   customer
GROUP BY email
HAVING COUNT(*) > 1;

Answer

Do not rewrite the algorithm. A solution passing six of ten is almost never conceptually wrong, it is failing one category of input, and the job is identifying which category rather than starting again from scratch. Work a fixed checklist in order.

Empty input and single element input. Maximum constraint size, which in C or Java usually means integer overflow and the fix is long instead of int. Negative numbers and zero.

All elements identical. Already sorted and reverse sorted input. Leading, trailing, and repeated whitespace plus case variation if it is a string problem.

Then read the verdict type, because it narrows the search before you touch a line of code: a wrong answer verdict means a logic or edge case issue, a time limit exceeded verdict means the complexity is too high and the logic may be perfectly correct, and a runtime error verdict points straight at array bounds or division by zero. Also confirm you are reading input in exactly the specified format and printing exactly the specified output with no prompt strings, because automated checkers count those as wrong output and that alone has cost candidates entire sections. This question also comes up verbally in the technical interview, because defect triage is the actual job in a delivery business. A weak answer is 'I would check my logic again', which says nothing.

Answer

You are not expected to derive recurrence relations, but you are expected to state the time and space complexity of anything you write without being asked, and to be right about it. That habit alone separates candidates, because most freshers write the code and then wait for a question. Say your complexity before you type: 'this is a single pass with a hash map, so O(n) time and O(n) space', then write it.

Know the complexities of the standard operations cold: array index O(1), array search O(n), sorted array binary search O(log n), hash map average O(1) with O(n) worst case on collisions, sorting O(n log n) for comparison based algorithms, and nested loops over the same input O(n squared). Be able to say why a hash map is average constant rather than always constant, because that is the standard follow up. Also be able to talk about the tradeoff rather than reciting the number: a hash map buys you time by spending memory, and there are contexts where the memory matters more.

And be honest about space, because candidates routinely claim O(1) space while allocating a map. If you genuinely do not know the complexity of something you wrote, say you are not certain and reason it out loud from the loop structure, which reads far better than a confident wrong figure.

Answer

Name exactly one language and commit to it. This is not a modesty question, it is the panel choosing which door to open, and a candidate who answers 'C, C plus plus, Java, Python and a bit of JavaScript' has invited questions in all five and will be examined on the weakest. Say one language, add one sentence about where you used it, then stop talking.

For example, 'Java, I have used it for two years including my final year project and my data structures coursework'. The follow up set is predictable per language and you should prepare exactly that set. Naming Java brings object oriented concepts, abstract class against interface, the collections framework, string immutability and the string pool, checked against unchecked exceptions, and threads at a surface level.

Naming Python brings list against tuple, mutable default arguments, dictionaries, comprehensions, shallow against deep copy, and generators against lists. Naming C brings pointers, memory allocation, structures, and string handling. Depth in one beats shallowness in four every time.

If you genuinely work across two, name the primary and mention the second only as an aside. A weak answer hedges. A strong one commits and then grounds the language in something you built, which quietly steers the conversation toward your project where you are strongest.

Answer

The technical round is moderate on data structures rather than competitive programming hard. Expect arrays, strings, linked lists, stacks, queues, hash tables, binary trees at a conceptual level, and sorting and searching with their complexities. You are far more likely to be asked to explain a structure and give a real use case than to implement a balanced tree.

On arrays against linked lists, the answer the panel wants goes beyond the textbook line. Arrays give O(1) indexed access and are contiguous in memory, which means they benefit from cache locality and are genuinely faster to traverse even when big O says both are O(n). Linked lists give O(1) insertion and deletion once you already hold the node, but finding that node is O(n), and every node carries pointer overhead.

So the real rule is that arrays win for read heavy and index heavy work while linked lists win when you are constantly inserting and removing in the middle and already hold a reference. The follow up worth volunteering is that in practice most production code uses dynamic arrays such as Java ArrayList or Python lists because amortised resizing is cheap and cache behaviour dominates. Naming cache locality is the detail that separates a memorised answer from an understood one, and panels react to it.

Answer

Panels have heard the car and animal examples several hundred times and both signal memorisation rather than building. Ground every pillar in your own project. Encapsulation is bundling state with the methods that act on it and controlling access, so you might say your payment class keeps card details as private fields and exposes only a process method, which means no other class can leave the object half valid.

Abstraction is exposing what an object does while hiding how, so a report generator interface with a single generate method lets the caller work without knowing whether the output is a PDF or a spreadsheet. Inheritance is reuse with specialisation, a base user class with admin and student subclasses adding their own permissions, and you should immediately add the caveat that inheritance is overused and composition is usually the better default, which signals maturity. Polymorphism is one interface with many implementations, resolved at compile time through overloading or at runtime through overriding, and you must be ready to write both on the spot because 'give me an example of runtime polymorphism from your own code' is the guaranteed follow up.

Expect the abstract class against interface question next, where the rule to state is an is a relationship with shared state against a can do capability that unrelated types can implement. A weak answer defines all four and produces no code.

Answer

Three clusters recur and each has a standard follow up that most candidates miss. Keys: a primary key uniquely identifies a row, cannot be NULL, and there is one per table although it may be composite; a unique key also enforces uniqueness but permits NULLs and you can have several; a foreign key references a key in another table and enforces referential integrity. The follow ups are how many NULLs a unique column allows, which differs by engine because NULL is not equal to NULL, and what happens on delete of a referenced parent row, where you should name RESTRICT, CASCADE, SET NULL, and NO ACTION and say that CASCADE is convenient and dangerous because one delete can silently remove thousands of child rows.

ACID: use a bank transfer so all four appear in one story, and know that isolation is a set of levels rather than a boolean, naming one anomaly per level, dirty read, non repeatable read, phantom read. Indexes: an index speeds reads and slows writes because every insert must also update the index, a clustered index determines physical row order so there is one per table while non clustered indexes are separate structures, and a composite index is usable left to right so an index on surname and first name does not help a query filtering on first name alone. That last point is the one that impresses.

Answer

Definitions alone will not clear this, because the panel usually draws two small tables and asks how many rows each join returns, which is where memorised answers collapse. INNER JOIN returns only matching pairs. LEFT JOIN returns every left row plus its matches, with NULLs where there is no match.

RIGHT JOIN is the mirror. FULL OUTER JOIN returns everything from both sides with NULLs where unmatched, and it is worth volunteering that MySQL does not support it directly so you emulate it with a UNION of the left and right joins. CROSS JOIN returns the Cartesian product.

SELF JOIN is a table joined to itself, typically for an employee and manager hierarchy, which is a common follow up in its own right. Two things catch candidates and you should raise both before being asked. Fan out: if the right table has three rows matching one left row, the join returns three rows rather than one, and that silent multiplication is what doubles totals in reports and is a genuine production defect class.

And filter placement: a condition on the right table put in WHERE rather than in ON turns a LEFT JOIN into an effective INNER JOIN because the NULL rows fail the predicate. Raising fan out unprompted answers the question after the question.

/* emp:  3 rows, dept_id values 10, 10, NULL */
/* dept: 2 rows, ids 10 and 20                */

SELECT * FROM emp e INNER JOIN dept d ON e.dept_id = d.id;   /* 2 rows */
SELECT * FROM emp e LEFT  JOIN dept d ON e.dept_id = d.id;   /* 3 rows */
SELECT * FROM emp e RIGHT JOIN dept d ON e.dept_id = d.id;   /* 3 rows */
SELECT * FROM emp e CROSS JOIN dept d;                       /* 6 rows */

/* SELF JOIN: employee to manager */
SELECT e.name AS employee, m.name AS manager
FROM   emp e
LEFT JOIN emp m ON e.manager_id = m.id;

/* The trap: this LEFT JOIN behaves like an INNER JOIN */
SELECT * FROM emp e
LEFT JOIN dept d ON e.dept_id = d.id
WHERE d.name = 'Sales';

/* The fix: move the filter into the ON clause */
SELECT * FROM emp e
LEFT JOIN dept d ON e.dept_id = d.id AND d.name = 'Sales';

Answer

This carries the highest weight in the technical round because it is the only part of the interview where you control the material, and panels use it to test whether the project is genuinely yours. Structure it in four beats and keep it under ninety seconds before pausing for questions. What problem it solved and for whom.

What you personally built, using 'I' for your parts and being honest about the team split. The stack, plus one design decision you made and the alternative you rejected and why. And one thing that went wrong and how you fixed it.

That fourth beat separates candidates, because a project with no problems in it was not built. Expect the panel to drill into every technology you name, so never list a framework you cannot survive three questions about. If you used a database, expect to be asked for your schema and to defend a table design.

If you called an API, expect questions about failure and timeout handling. If you claim machine learning, expect questions about dataset size and your evaluation metric, and be ready to say why accuracy was or was not the right choice. A weak answer is a feature tour with no decisions in it. A strong one is a decision narrative in which you can defend every choice you made and name the one you would now make differently.

Answer

This is not conversational, it is a filter, and a hesitant answer here is frequently why a candidate who cleared every technical round does not receive an offer. Delivery centres are spread across cities including Bengaluru, Hyderabad, Chennai, Pune, Kolkata, Noida, Coimbatore, and others, and allocation follows project demand rather than candidate preference, so the business cannot promise your city. The strong answer is an unqualified yes followed by one sentence of substance: yes, you are willing to relocate anywhere in India, you have thought about it practically, and you would prefer a particular location if there is a choice but it is not a condition.

Never say 'yes but not the north' or 'only if it is near home', because the panel writes that down word for word. If you have a genuine constraint, for example caring for a parent with a medical condition, state it once, calmly and factually, and immediately follow with what you can do rather than what you cannot. Do not manufacture a constraint to look serious, and do not say yes while your face says no, because these panels are specifically trained to read that gap. What they are really probing is whether you will accept an allocation without escalating three weeks after joining, which is a costly operational problem for them.

SAMPLE ANSWER

"Yes, I am completely open to relocating anywhere in India. I have already
discussed it at home and there is no constraint from my side. If there is a
choice I would find Bengaluru or Hyderabad easiest for family reasons, but
that is a preference and not a condition. Wherever I am allocated I will move
and I will be there on the joining date."

WHY THIS WORKS
- The unqualified yes comes first, before any nuance at all
- Shows the decision was actually discussed, not improvised in the room
- Names a preference without converting it into a condition
- Closes with a commitment sentence, which is the line that gets recorded

Answer

Global delivery means projects run to European or American business hours, and support and infrastructure projects run rosters that include nights and weekends. The panel needs to know now rather than after you have been staffed. Answer yes if it is true, and answer with specifics so it does not sound like a reflex: say you understand shifts may rotate, that you are comfortable with it, and that you have thought through the practical side, the commute, the transport arrangement, and sleep.

If you have a genuine constraint, be straight and offer what you can do instead, for example that evening overlap hours covering a European client work comfortably for you. Never give a false yes, because the cost of that lands on your team within weeks and damages you far more than a truthful no would have. What a strong candidate adds is the reason overlap hours exist, which is that handovers with the client team happen live rather than over email, so you are not merely accepting an inconvenience, you understand the delivery logic.

A weak answer is 'I can adjust', which is vague and reads as reluctance. Another weak move is asking about the shift allowance in the same breath as the commitment, so save every compensation question for the end of the discussion.

Answer

Ninety seconds, four beats, no life story. The panel is not collecting information, they have your resume in front of them. They are assessing spoken fluency, structure, and confidence, and deciding which thread to pull next, which makes this your one chance to choose the topic of the next five minutes.

Beat one: who you are academically in one line, degree, branch, college, graduating year. Beat two: your strongest technical grounding named specifically, one language and one area. Beat three: one project or internship with an actual result, quantified if you can, and this is the thread you want them to pull.

Beat four: why you are here, connecting what you have done to the role. The failures are consistent: starting with where you were born, listing every family member, listing every subject studied, running to four minutes, or reciting something obviously memorised in a monotone. Practise aloud until it is fluent but not word perfect, because word perfect sounds rehearsed and a panel that senses recitation will interrupt you mid sentence.

Do not say anything you cannot defend, because every noun in this answer is a potential question. End cleanly with a full stop rather than trailing off, since a confident close is disproportionately memorable in a day of forty interviews.

SAMPLE ANSWER, about 90 seconds

"I am Arjun Nair, a final year Electronics and Communication student at a
college in Coimbatore, graduating in 2026 with 7.9 CGPA.

My strongest area is Python along with SQL, which I built up across coursework
and two projects rather than through my core branch subjects.

The project I am proudest of is a college attendance analytics tool. I owned
the data layer. Our first version ran a query per student per subject and the
report took almost a minute to load for a class of sixty, so I rewrote it as a
single grouped query with an index on the attendance date, and the report came
back in about two seconds.

I am interested in Wipro because I want to work on systems real users depend
on daily, and the spread of client industries here means I would see problem
types I could not see inside a single product company."

WHY THIS WORKS
- Four clean beats, under ninety seconds, no family history
- Owns a non computer science branch without apologising for it
- The project beat has a specific problem and a measurable fix
- Closes with a reason about the work, not about the brand

Answer

The panel knows you applied broadly and is not offended, so do not pretend this is your only application. What they are testing is whether you know anything specific or are reciting a template that would fit any employer. The failure mode is generic praise, a large global company, a great brand, good learning opportunities, which is what most of the pool says and which panels have stopped hearing by the third interview of the day.

Build the answer from three specifics. One about the work: the range of client industries and delivery types, so the systems you touch vary across your career instead of being one product forever. One about your own path: what you want your first two years to look like, and why a structured training and delivery environment suits that better than a small team where you would be the only person who knows anything.

One about something you actually researched, a service line, a technology area, or the graduate programme itself. If asked directly whether you applied elsewhere, say yes and name what would make you choose this offer. Honesty scores better than a transparently false exclusivity claim, and panels spot the latter instantly because they hear it thirty times a day.

SAMPLE ANSWER

"I did apply to several companies and I will be honest about that. The reason
Wipro is where I want to start is the range of work. In one organisation there
is banking, healthcare, energy, and consumer delivery going on, so in my first
few years I would see problem types I would not see inside a single product
company.

The second reason is the structured start. I know I will not be productive on
day one. A place with a real training programme and experienced people on the
delivery floor is a better foundation for me than a small team where I would
mostly be guessing and nobody would have time to correct me."

WHY THIS WORKS
- Honest about applying elsewhere, which the panel already assumed
- Two specific reasons, neither of which is generic brand praise
- Self aware about being a fresher without being self deprecating
- Contains nothing a follow up question could catch you out on

Answer

The panel is testing whether pressure makes you organised or makes you disappear, because delivery work runs to dates that do not move. Use a real, specific, modest example rather than a dramatic one, and structure it as situation, what the pressure actually was, what you did concretely, and the outcome including what you changed afterwards. Two failure patterns dominate.

The first is a story where the pressure was entirely someone else's fault and you were the victim, which tells the panel only that you assign blame. The second is a story with no visible action in it, where the candidate says they stayed calm and worked hard, which is not an answer because it names nothing you actually did. What makes an answer strong is a specific mechanism: you listed everything outstanding and cut the list to what mattered, you asked for help early instead of at the deadline, you told the person depending on you before they had to ask, or you shipped a reduced version on time rather than a complete one late.

Those are transferable behaviours and they are what gets written down. Close with the habit you kept afterwards. If your setback is an academic one such as a failed subject or a rejected offer, that is entirely usable, and honesty about it reads better than a manufactured project crisis.

SAMPLE ANSWER

"In my final semester our project partner dropped out three weeks before the
submission and took the front end with him. My first reaction was that we
would not finish.

What I actually did was list every remaining item and split it into must have
and nice to have. The dashboard charts went into nice to have and we dropped
them. Then I told our guide the same day, before he found out from the demo,
and asked whether a reduced scope would still be accepted. He said yes.

We submitted a smaller working system on time instead of a bigger broken one
late. Since then I cut scope early and tell the person waiting on me the same
day rather than the week of the deadline."

WHY THIS WORKS
- A specific setback with a real constraint, not a dramatic invented one
- Names concrete actions, cutting scope and informing early, not just effort
- No blame assigned to the teammate who left
- Ends with a habit that transfers directly to delivery work

Answer

WILP is a work integrated route into Wipro aimed at candidates who are not coming through the standard four year engineering path, typically those joining after class 12, after a diploma, or after a science degree. The model is that you are employed by Wipro and study for a degree at the same time, with the degree awarded by a university partner under a work integrated framework rather than by Wipro itself. You work on real delivery projects while completing academic semesters alongside, which is why the programme runs over several years.

The selection process typically includes an aptitude style assessment, an English component, and an interview, and the academic eligibility for the entry level in question is stated in the specific notification. Two things change across cohorts and must be verified in your own documents rather than taken from a forum: which university partner awards the degree and which degree it is, and the exact structure of the academic calendar alongside work. What the programme genuinely offers is entering the industry earlier than your peers, earning while studying, and finishing with both a degree and several years of real delivery experience. What it costs is a service commitment and a compensation curve that starts well below a standard engineering fresher offer, which the next question covers.

Answer

This is the part candidates should read most carefully, because it is where the programme differs most from a standard fresher offer, and because the terms have changed across cohorts. Typically a work integrated programme carries a service commitment for the duration of the programme and often for a period beyond it, since the employer is funding or subsidising a degree and needs the return. Commitments in this segment are commonly reported as multi year, frequently cited around the five year mark when the academic programme is included, with a stated liability if you exit early.

Compensation typically starts well below a standard engineering fresher offer, is commonly reported in the region of ₹1.5 to ₹2.5 LPA in the early years, and steps up at defined stages of the programme, with a revised package once the degree is completed and you are absorbed into a regular role. Every one of those figures varies by cohort, so treat them as reported ranges rather than as facts about your own offer. What you must do before signing: confirm the exact commitment period and when the clock starts, the exact exit liability and whether it reduces as you serve, what happens if you fail an academic semester, whether the degree is transferable if you leave, and whether any original documents are retained. Ask in writing over email so you have the answer on record.

Answer

There is no universal answer, but there is a way to decide that is better than comparing starting salaries. Compare the two paths at the same point in time, not at the start. Take the year you would finish a regular four year degree and ask where each path leaves you then.

On the WILP path you are typically several years into employment with real project experience, a degree in progress or recently completed, an income you have had throughout, and a service commitment still running. On the regular path you have a full time degree, no professional experience, no income earned so far, possibly education loan repayment starting, and complete freedom of employer choice with a fresher offer that starts higher. The honest tradeoff is money and experience earned early against optionality lost.

WILP tends to suit candidates for whom earning early genuinely matters financially, who are confident they want an IT services career, and who are comfortable with a long commitment. The regular route tends to suit candidates who want to keep the door open to higher band product roles, higher studies, or a specialisation the work integrated curriculum will not cover. Two practical checks before you commit either way: how the degree is recognised for further study, and whether the commitment period would block a move you can already foresee wanting.

Answer

Lateral hiring is demand driven rather than pool driven, and that single difference changes everything. There is usually no aptitude test and no essay. You are interviewed against a specific open requirement on a specific account, so the technical round goes deep on the exact stack named in the job description rather than on general fundamentals, and your last two years of work matter far more than your degree or your college.

Expect a technical round, sometimes two, a discussion with the delivery manager who owns the position, and an HR round covering compensation and notice period. Preparation shifts accordingly: rehearse a five minute walkthrough of your current project, know your own architecture including why decisions were made rather than just what they were, be ready to state clearly what you personally owned as opposed to what your team delivered, and carry concrete numbers, team size, ticket volume, release cadence, or a performance improvement you contributed to. On the commercial side, notice period is a live negotiating point, so if you are on ninety days raise buyout early rather than at the offer stage, since whether it is supported varies by requirement and urgency.

Be precise and honest about your current fixed CTC because verification checks payslips. A weak lateral candidate describes their team's work in the plural throughout.

Answer

Indian IT services employers commonly attach a service agreement to fresher offers, meaning a contractual commitment to remain with the employer for a stated period after joining, usually counted either from the date of joining or from completion of the initial training programme, with a stated liability if you leave earlier. Durations and amounts vary by year, band, and role and the terms change between cycles, so never rely on what a senior told you about their batch. Read your own document.

Check these specifically before signing: the exact duration and whether the clock starts at joining or at training completion, the exact payable amount and whether it reduces on a pro rata basis as you serve, what triggers the liability, whether resignation during training is treated differently from resignation afterwards, what happens if the company terminates you rather than you resigning, whether any original certificates are to be submitted, and the notice period, which is a separate clause governing your exit once the commitment period ends. Ask the HR contact in writing over email rather than verbally so the answer is on record. If asked in an interview whether you are comfortable with a service agreement, answer yes if you are, and it is entirely professional to add that you would like to read the terms first.

Answer

Background verification is usually run through a third party agency and checks identity, address, education, prior employment, and in many cases a criminal record check. Candidates worry about the wrong things: checks almost never fail because of a modest CGPA or a gap year you declared honestly, they fail on discrepancies between what you stated and what the record says. The recurring causes are employment dates that do not match what a previous employer confirms, an inflated job title, a salary figure in the application that payslips do not support, an employment period left off the resume entirely, a degree year or percentage that does not match the university record, and an experience letter from a company that cannot be contacted or will not confirm you.

For freshers the common problem is an internship claimed as employment or a certificate from an institute that cannot verify it. Keep one folder ready containing: class 10 and class 12 mark sheets, all semester mark sheets, degree or provisional certificate, transfer or bonafide certificate, PAN and Aadhaar, address proof, passport size photographs, offer, relieving and experience letters if any, recent payslips if any, and any certification listed on your resume. Declare everything including short stints, because an omission discovered later is treated as concealment and is far more serious than the thing itself.

Answer

Fresher offers are made against a demand forecast, and actual onboarding happens when project demand and training capacity line up, which is why candidates frequently wait months between an offer letter and a joining date, sometimes considerably longer in a weak demand cycle. This is normal across Indian IT services and is not by itself a sign that your offer is at risk, but it creates real decisions for you. Practically: stay reachable, keep the email address on your offer active and check the spam folder, and respond quickly to every communication, because non response is one of the very few things that genuinely puts an offer at risk.

Complete any pre joining learning assigned to you, since completion is often tracked and in some cases affects onboarding priority. Keep preparing technically rather than going idle, because there are assessments during the training that follows. It is legitimate to keep interviewing elsewhere while you wait, since an unstarted offer is not employment, but be honest with yourself about the reputational cost of accepting and then not joining. If the wait is causing genuine financial hardship, contact the recruitment team politely and factually and ask for an indicative timeline rather than repeatedly chasing, which achieves nothing and is remembered.

Answer

New joiners typically go through a structured initial training programme covering programming fundamentals, a technology stack, database work, and professional and communication skills, delivered over several weeks with periodic assessments. This is not a formality. Performance in training commonly influences your project allocation, and repeated failure in assessments has real consequences that can include extended training, reallocation, or in serious cases termination, with the specifics varying by policy and by year.

The failure pattern is remarkably consistent: candidates who have just cleared a hard selection process relax for three weeks and then discover the assessment is genuinely demanding, and by then the gap is too large to close in a weekend. Treat training as your job rather than as an extension of college. Attend every session, complete assignments on the day they are set instead of batching them into a weekend, and use the trainers, because they are accessible in a way that senior people on a live project will never be.

If you struggle with a topic, raise it early with your trainer rather than at the assessment, since support given proactively is normal while support requested after a failure looks different on your record. Ask what the retake policy is at the start of the programme rather than after you need it.