Wipro Fresher Interview Questions
A campus hire at an IT services company often starts on a team that keeps a client's existing systems running: fixing small defects, writing test cases and answering support tickets. Prepare to explain your college projects in plain words and to show how your fundamentals in databases, programming and testing apply to a system that a bank, hospital or factory depends on every day. What to show here: steady fundamentals and care with a client's running systems. Each question below has what the interviewer is checking, an answer frame and a sample spoken answer to adapt.
How Wipro hires, in its own words, and its questions for every job →
1. New joiners are often placed on a client project in a technology they never studied. Tell me about a time you had to pick up a tool or language from zero for a project that was already under way.
- Say what you had to learn and how much time you had.
- Explain how you split the learning into small parts.
- Describe the first useful thing you delivered.
- Share what you would do faster next time.
“In my final year project our guide asked us to move from a desktop program to a web application, and I had never written one. The rest of the team had already started. I gave myself a few days, picked one small screen, and built only that, looking up each thing as I needed it. I kept a page of notes on every error I hit and how I fixed it. By the end of the week I had the login screen working, and my notes helped two teammates. The result was your result. Next time I would ask a senior for a reading order first.”
Weak answers say they are a fast learner without naming what they learned, how, and what they delivered.
2. Much of the early work on a support team is routine: small defects, test cases, documents. Tell me about a time you did a plain, repeated task with real care.
- Describe the routine task and why it mattered.
- Explain how you kept your accuracy up.
- Mention anything you improved along the way.
- Share the result.
“During my internship I was asked to check a long list of test cases for a billing screen by hand, every time a new build arrived. It was dull, but I knew a missed case could reach real users. I made a simple sheet with each case, the expected result and the build it last passed on, so nothing was skipped. After a few rounds I noticed the same five cases took most of my time, so I asked my mentor to show me how to script them. That gave us your result, and I learned routine work is where mistakes hide.”
Weak answers show boredom with basic tasks or suggest such work is below them.
3. A client's billing application stores customers, invoices and the items on each invoice. How would you arrange the tables, and why not keep everything in one wide table?
- Name the tables and the key of each one.
- Show how they link with foreign keys.
- Explain what goes wrong in one wide table.
- Mention one case where you would accept some repetition.
“I would make three tables. Customers, with a customer id as the key. Invoices, with an invoice id and the customer id as a foreign key. Invoice items, with the invoice id, the product and the quantity. In one wide table, the customer's address would repeat on every row, so a change of address would need many updates and some could be missed. Deleting the last invoice could also delete the only copy of the customer. I would still store the price on the invoice item itself, because an old invoice must keep the price that was charged then.”
Weak answers recite normal forms by name and cannot say what breaks when the data is kept in one table.
4. You fixed a small defect in a client's leave approval screen. What testing do you do before you call it done, and why test parts you did not change?
- Test the fix itself with the case from the ticket.
- Test the edges around it.
- Re-run tests for the parts that share the same code or data.
- Record what you tested in the ticket.
“First I repeat the exact steps from the ticket and confirm the defect is gone. Then I try the edges, such as leave that crosses a weekend or a request with no manager assigned. After that I test parts I did not touch but that use the same code or tables, like the leave balance report, because my change could break them without any error on my own screen. That is regression testing. If the team has automated tests I run them all. Last, I write in the ticket what I tested and on which build, so the reviewer can trust it.”
Weak answers test only the one case from the ticket and assume everything else still works.
5. A client's insurance system handles motor, health and home policies. They share some rules and differ in others. How would you model that with classes?
- Put shared data and behaviour in a base type.
- Let each policy type supply its own rules.
- Show how calling code treats every policy the same way.
- Say when you would prefer composition.
“I would create a base policy type that holds what every policy has: the holder, the start and end, and the status. Each kind of policy, such as motor or health, extends it and gives its own way to calculate the premium and to check a claim. The code that renews policies then only calls the premium method and does not need to know which kind it has. That is polymorphism doing useful work. If some rules are shared by only two types, like a no-claim discount, I would keep that rule in a small separate class and plug it in.”
Weak answers list the pillars of object-oriented programming and never connect them to the policies in the question.
6. A support ticket says a report in a client's application takes minutes to open. It reads from a table with a very large number of rows. What would you check first?
- Reproduce the slowness and find the query behind the report.
- Look at how the database runs it and whether it scans the whole table.
- Check indexes on the filter and join columns.
- Propose a change and test it on a copy first.
“I would first open the report myself to confirm it is slow and note the filters used. Then I would find the query behind it and ask the database for its plan. If it reads every row to find a few, the filter column probably has no index, a bit like searching a book with no index page. I would also check if the report pulls more columns or rows than it shows. I would try the index on a test copy, compare the time, and only then raise a change request with my senior, since an index also slows down inserts a little.”
Weak answers jump to asking for a bigger server or add indexes on every column without looking at the query.
7. It is your first month on a support team. Your senior has finished their shift, and a ticket arrives about an error you do not understand. What do you do?
- Read the ticket fully and judge how urgent it is.
- Search past tickets and team notes for the same error.
- Escalate by the agreed path if it is urgent or you are stuck.
- Write down what you found for whoever picks it up.
“I would read the ticket carefully and check its priority, because that decides how long I can spend on my own. Then I would search old tickets and the team's notes for the same error message, since most errors have happened before. If I find a known fix that is safe, I apply it and note it. If the issue is urgent or I am still unsure after a short time, I follow the escalation list and call the person on duty. I would not guess on a client's live system. Either way I write what I saw and tried in the ticket.”
Weak answers either sit on the ticket until the senior returns or try risky changes on the live system to look capable.
8. Why do you want to begin your career at Wipro, working on systems that belong to client companies?
- Say what you understand about IT services work.
- Name what you hope to learn from real client systems.
- Connect it to something you did in college.
- Say how you want to grow.
“My college projects were used by a handful of people and then forgotten. I want to work on systems that real businesses depend on daily, where a defect matters to someone. Wipro delivers IT services to client companies in many industries, so as a new engineer I would see how large systems are built, tested and kept running. In my project I enjoyed the testing and fixing stage more than I expected, and support and delivery work has plenty of that. I want to build strong basics first, then grow into someone a client team trusts with a whole module.”
Weak answers talk about the brand or the training period only and show no idea that the work is done for clients.
No figures on this page: pay depends on the level, the city and the offer in front of you. When the offer comes, the free salary negotiation script helps with that part.
The questions above are the prep. On the real call, ClapAssist helps with the ones you did not practice.
ClapAssist is an AI interview assistant for Mac and Windows. It listens to the interview on your computer and shows you what to say, in short lines you can read while you talk. Your live interview audio and screen are never stored. Your resume and notes are saved to your account so the app fills them in on any computer. It is hidden from screen share on every plan, including Free; only you can see it.