GeeksforGeeks Experience · Apr 2019 · San Francisco

Teradata Interview Experience | Set 7 (On-Campus)

MLE Recruiter New Grad Easy

Interview Experience

Teradata recently visited our campus and the package offered was above 8 LPA. They were recruiting for the role of C/C++ development and functional testing.Round 1(Written...

Full Details

Teradata recently visited our campus and the package offered was above 8 LPA. They were recruiting for the role of C/C++ development and functional testing. Round 1(Written - 45 minutes) The questions for this round were different for the development and testing team. Candidates selected for this round were mainly on the basis of their CGPA and the corresponding entrance exam rank. Around 50 candidates took the exam(both dev and test profiles). I was in the development profile. For me, this was the toughest round. The questions were above GATE level. A few previous years' GATE questions were also asked. The subjects were C, DS, and OS. Some of the questions were tricky. There were few tough questions from bit manipulation and pointer arithmetic. 16(8 dev+8 test) ppl qualified this round. Round 2 (Technical Interview 1 - 30 minutes) This round was pretty easy. I was asked two questions. The only language allowed was C 1. Remove trailing blank spaces from the end of a string. I quickly gave an O(n) solution, n being the length of the string. He asked to optimize it in any way I can. I used the sizeof() operator for calculating string length to avoid traversing to the end of the string. He looked satisfied. 2. Given a Single Linked List, reverse the list whenever a "1" is encountered i/p: 2->3->4->5->1->10->11->12->1->13->14 o/p: 5->4->3->2->1->12->11->10->1->13->14 Took about 10 minutes to write the full code covering all test cases. He asked me to optimize it a bit. Some discussion on projects listed in the resume and he was done. Round 3 (Technical interview 2- 50-55 minutes) I found this round to be easy too. The interviewer greeted me and told that my DS was good from the first round's feedback. He then asked me to grade myself out of 10 in DS. I played safe and said 6 or 7. He asked me to answer the following questions in C: 1. Check a string to be a palindrome 2. Place the characters of the string inside the nodes of a Singly Linked List i.e, every node has one character. Check palindrome 3. Merge two sorted strings 4. Do the same using Single Linked Lists instead of arrays. 5. Do the above question inplace 6. You're given a Single Linked List whose length is unknown and a number k. Find the kth element from the end of the Linked List 7. Do the above using a single pass of the Linked List. Some discussion about projects. I wrote code for all the questions above, as quickly and accurately as possible. He seemed impressed with that. Round 4 (ML interview- optional) Only those candidates who had previous experience with ML were invited to this interview. I had taken a course on Coursera and mentioned in the resume, hence called for this additional round. 1. Difference between unsupervised and supervised learning 2. Explain the Linear Regression model. How is data revamped onto this model? What are the APIs used by your platform by which you did this project? And some other questions related to the algorithm and quality metrics. 3. Gave some scenarios. Asked to distinguish between unsupervised and supervised learning in each of them with reasons. 4. Imagine you want to help your mess with wastage of food. How will you use ML to solve this problem? Enumerate the conditions you'd use and classify them. Round 5 (

Manager round 30 minutes) Around 2-3 developers qualified for this round. Basic questions like where do you want to see yourself in 5 years and 10 years. Some questions about the resume projects(bit technical). Why did you apply for ML profile too? Other basic HR questions. Round 6 (

HR round 30 minutes) Last round was with who seemed like a head HR. He asked about my strengths, weakness. Other HR questions like incidents where I had taken initiative and saw it through, USP, CGPA, position in the class, etc., After the final round, 1 developer and 1 tester was selected Few tips: 1. Be very strong with the basics. I was lucky to be faced with strings and Single Linked List questions. Some of my friends were asked on graphs, B-Trees, etc. 2. Understand the question completely and thoroughly 3. One thing I thought worked for me was the pace with which I answered the questions. Once the question was clear to me, I was very fast in writing code. That impressed all the interviewers. 4. Be specific while answering.

Free preview — 6 questions shown. Unlock all Teradata questions →

About This Question

This is a candidate experience report from a teradata interview for a mle role (new grad level) during the recruiter round reported in 2019.

It covers the following topics: Ml, Linked List, Trees, Strings, Bit Manipulation, Sql, Graphs, Arrays .

Difficulty rating: Easy

About Teradata Interview Reports

This question was reported by a candidate who interviewed at Teradata. 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 Teradata are the higher-signal extractions to take from this report.

For broader preparation context, the Teradata 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 Teradata reports consistently are the ones worth investing in; one-off niche problems are not.

During Your Teradata 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 Teradata 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.