
One candidate reports a three-round Tata Consultancy Services Cloud & Platform Engineer process: technical, manager and HR. Questions covered broad cloud fundamentals, DevOps tools, SQL joins and AI basics like RAG, and the candidate received an offer.
$120K
Avg. Base Comp
$140K
Avg. Total Comp
3 rounds
Typical Rounds
Not reported
Process Length
A candidate who interviewed for the Tata Consultancy Services Cloud & Platform Engineer role described three rounds: a technical round, a manager round and an HR round. They called the interviews wide but shallow: the questions were not especially hard, but they covered a lot of ground. The candidate received an offer. This is a single report, so treat it as one data point rather than a fixed format.
The first technical round stayed at a basic level, with cloud infrastructure questions and a discussion of past projects. The second round went deeper, with some coding and a longer conversation about AI topics, including what RAG is and what vector databases are. The HR round was described as friendly and conversational.
The candidate also described a separate virtual round with simple SQL join questions, followed by mostly theory on security, monitoring and Splunk. They were also asked basic questions on Python, AWS, Docker, Kubernetes and SRE tools. The candidate felt the content depended on the client and team requirement, so it makes sense to review the job description closely and prepare fundamentals across several tools rather than one deep specialty.
Scheduling was the rough part. The candidate waited in a meeting, was told the panel was delayed, and was later told they had been assigned to the wrong panel. Communication then went quiet for a while. Keep your own records of times and contacts, and follow up politely if things stall.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Tata Consultancy Services process.
The process was a little uneven, but the actual interviews were pretty straightforward. I had three rounds in total: a technical round, a manager round, and an HR round. The first technical round was easy and stayed at a basic level, mostly cloud infrastructure questions along with discussion of my past projects. The second round went a bit deeper and included some coding questions, plus a longer discussion around AI topics. I was also asked what RAG is and what vector databases are, so they clearly wanted to see whether I understood newer concepts beyond just the cloud stack. The third round was with HR and was very friendly, more of a general conversation than a formal interview.
What stood out to me was that the technical questions were not especially hard, but they were broad. Another interview I had in the process was a virtual round where they asked simple SQL join questions and then spent most of the time on theory around security, monitoring, and Splunk-related concepts. I also got basic questions on Python, AWS, Docker, Kubernetes, and SRE tools, so the role seemed to depend a lot on the client and team requirement. The only frustrating part was the scheduling itself: I was made to wait in the meeting, then told the panel was delayed, and later told I had been assigned to the wrong panel. After that, communication dropped off for a while, which was disappointing. In the end, though, I did receive an offer. My takeaway is to be ready for a wide but shallow technical screen, especially around cloud fundamentals, common DevOps tools, and a few AI basics like RAG and vector databases.
Prep tip from this candidate
Brush up on basic cloud infrastructure, Python, AWS, Docker, Kubernetes, and SRE tools, and be ready to explain RAG, vector databases, and simple SQL joins. It also helps to review security, monitoring, and Splunk concepts since those came up in the more theory-heavy round.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Tata Consultancy Services
Given an integer N, write a function that returns all of the prime numbers up to N
| Question | |
|---|---|
| Find the First Non-Repeating Character in a String | |
| Sort Strings | |
| The Brackets Problem | |
| Singly Linked List | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Processing Large CSV | |
| Find Duplicate Numbers in a List | |
| Hurdles In Data Projects | |
| Swap Variables | |
| Prime Numbers Identification | |
| Pipeline Transformation Failures | |
| Text Editor With OOP | |
| String Palindromes | |
| Why Do You Want to Work With Us | |
| Azure Kubernetes Infrastructure | |
| Impossibly Iterative Fibonacci | |
| Your Strengths and Weaknesses | |
| Merge Sorted Lists | |
| Find the Missing Number | |
| Find Bigrams | |
| Data Pipelines and Aggregation | |
| N-gram Dictionary | |
| String Shift | |
| Scrambled Tickets | |
| Get Top N Frequent Words | |
| Minimum Change | |
| Good Grades and Favorite Colors | |
| Payment Data Pipeline | |
| Mouse Search |
Synthesized from candidate reports. Individual experiences may vary.
The candidate reports a first technical round that stayed at a basic level. It centered on cloud infrastructure questions and a walk-through of past projects. Prepare to explain your hands-on cloud work clearly and cover fundamentals rather than advanced edge cases.
The candidate describes a deeper second round with some coding questions and a longer discussion of AI topics. They were asked what RAG is and what vector databases are. Being able to explain these newer concepts in plain terms may help alongside your cloud stack knowledge.
The candidate also mentions a virtual round with simple SQL join questions, then mostly theory on security, monitoring and Splunk. Basic questions on Python, AWS, Docker, Kubernetes and SRE tools came up too. The exact tools may vary with the client and team, so review the job description.
The candidate lists technical, manager and HR rounds as the three total rounds, and describes the HR conversation as very friendly and general rather than formal. They also report scheduling confusion and a gap in communication, so expect some waiting and follow up as needed. The candidate ultimately received an offer.