Tesco Interview Experience for PWD internship (On-Campus)
Question Details
Round 1:(OA Round)The first round was an online coding Test. in 90 minutes.Question Topic:OSDBMSNetworkingOopsTwo Coding Problems (Sorting and String)Round 2:(Technical R...
Full Details
Round 1:(OA Round) The first round was an online coding Test. in 90 minutes. Question Topic: OS DBMS Networking Oops Two Coding Problems (Sorting and String) Round 2:(Technical Round) Tell me about yourself and What did you learn in your 4 years of B.Tech He asked me some OS questions. Different Scheduling Algorithms. How do you assign priority values to a process i.e. which process has higher priority and low priority? Multi-core vs multi-threading. At max how many threads can you create in a process? What is deadlock? How will you handle Banker's algorithm and resource allocation graph) Then he asked some questions on Computer Networks. What does the transport layer do? What is Congestion control and flow control? Which protocol is used for sending mail?
NOTE: Basically, the way you answer will drive the interview. Interviewer generally try pick the question from your previous answer. so what ever you are answering you must be 100% sure. Write a program to find whether a given linked list is a palindrome or not? (In one traversal only). I was asked to write the entire program (in online compiler) and the interviewer checked the code against various edge cases. Round 3:(HR Round) This was a HR round. All the 15 candidates had HR round (independent of technical round performance). Tell me about your self How will you choose your team members for a project? How will you handle if your team members are not working properly? Let’s say you need to complete your project by night. You and all your team mates are stuck up and unable to proceed further and all your friends are busy in their own works. Now how will you handle this situation? Out of 10 Students 3 were selected.
About Tes Interview Reports
This question was reported by a candidate who interviewed at Tes. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Tes are the higher-signal extractions to take from this report.
For broader preparation context, the Tes interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Tes reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Tes Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Tes reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.