Video summary

TCS Prime Interview Experience 2027 batch I How He Cracked Prime Role| TCS NQT 2026| TCS NQT 2027

Main summary

Key takeaways

Educational

Main ideas / lessons conveyed

  • Interview preparation is about focused practice + time management, especially for timed quantitative sections and pattern-based reasoning/numerical topics.
  • Math/numerical preparation should focus on high-frequency areas, such as:
    • ratios & proportion
    • trains/time & distance
    • edge/other numerical topics
    • simplification
  • Reasoning and verbal preparation should follow the syllabus format closely, for example:
    • sentence completion without options
    • passage recall with separate memorization + writing timers
    • email writing with strict keyword sequencing
  • Coding round strategy requires completing sections in order (no jumping/backtracking between Numerical → Reasoning → Coding). In coding, the input format may require writing more than just the core function logic.
  • For DSA/technical interviews, pattern learning via a structured playlist/sheet is more effective than randomly switching resources.
  • Interview success depends on confidence and “read-the-room” communication—speak simply, clearly, and confidently; show fundamentals; be responsive to what interviewers ask.
  • For AI/ML project questions, demonstrate fundamentals and correct reasoning, not just claiming AI usage (and be ready to discuss limitations like deployment knowledge).
  • Final takeaway: consistency over months (and not getting stuck on one topic like arrays) drives improvement.

A) TCS NQT / Online Assessment: Numerical preparation

Prioritize high-yield topics

  • Ratio & proportion (described as very high frequency)
  • Train & stream / distance–speed–time related problems (including trains and stations)
  • Edge-type numerical topics (example mentioned: “wide edge”)

Time management approach

  • Numerical section: ~20 questions in ~25 minutes (tight)
  • Target solving speed: roughly ~1 minute 15–20 seconds per question
  • The implied strategy: repeated practice until solutions become fast under pressure

Practice volume

  • Spend 4–5 days on numerical
  • Solve about ~60 questions per relevant topic
  • YouTube tutorials are okay, but the key is repeat practice and familiarity with question types

Difficulty note

  • Numericals were described as hard-level, but still solvable with practice

Advanced numerical tip (simplification-heavy)

  • Advanced numericals may feel easier due to simplification-type problems, such as:
    • expressions like (x + 1)²
    • square roots
    • powers like “to the 4”
  • Add quick-math practice

B) Online Assessment: Reasoning preparation

Start reasoning close to the exam

  • Preparation began the day before / around NQT timing

Use a focused long video/topic list

  • Used a 10-hour YouTube resource covering important topics only

High-frequency reasoning topics listed

  • Blood relations
  • Syllogism / related relation-pattern types
  • Alphabet patterns (examples referenced with sequences like A-B-C-X-Z style)

Expected performance

  • From ~20 questions, expected about 8–10 to be relatively easier if completed in time

C) Verbal Ability format & how to handle it

Section 1: Sentence completion (20 questions)

  • No options (open fill-in)
  • 25-second timer per question
  • If time runs out, the question is effectively lost
  • Guidance: choose a word that fits the meaning/context (exact word may differ, but context must be correct)

Section 2: Passage recall

  • Passage length: ~3–5 lines
  • ~30 seconds to remember
  • ~90 seconds to write the meaning
  • Don’t rewrite word-for-word—write the overall meaning
  • Memory trick:
    • recall in a comfortable language (example: Odia; also Hindi/any comfort language)
    • then write the meaning in English during the output timer (paraphrase allowed)

Section 3: Email writing

  • A context is given (to manager/team leader/head/juniors)
  • 3–5 keywords are provided
  • Requirements:
    • keywords must appear in the same sequence
    • do not change the tense of the provided keywords
  • Time: about 8–9 minutes (around 9 minutes)
  • Target length: about 100–120 words (the exact upper bound noted was garbled)

D) Coding round strategy (important rules)

Follow strict section order

  • No skipping
  • Fixed order: Numerical → Reasoning → Coding
  • No backtracking to previous sections

Test structure and approach

  • Easy question first, then medium
  • Easy question:
    • described as very easy
    • included mention of an erasure-related question (topic unclear)
    • key point: you must write the input portion yourself (the prompt may not provide full scaffolding)
  • Medium question:
    • array-based with logic
    • brute force might pass limited/private tests, but optimal logic is needed for larger constraints

Time note

  • They completed the easy question in about 5 minutes
  • Then waited about ~30 minutes before the medium question appeared (since they couldn’t proceed out of order)

Outcome mentioned

  • Brute force did not pass all private tests
  • They passed 4 out of 4 visible test cases, while private ones failed

E) DSA / Interview preparation plan (resource strategy)

Use one structured playlist/sheet

  • Recommended: Striver A to Z sheet (free version) or equivalent structured plan
  • Avoid randomly switching to reels/videos mid-way—consistency matters

Use one programming language

  • Practiced only in Python

DSA topics progression mentioned

  • Arrays (emphasized as fundamentals)
  • Sorting: selection sort, quick sort, merge sort (basic sorting fundamentals)
  • Pattern-based methods: two pointers, sliding window
  • Hashing
  • Recursion: basic + intermediate
  • Stacks/queues and linked lists
  • Trees / binary search related practice
  • “HIPS” mentioned (unclear, but implies extended practice)

Core principle

  • Focus on fundamentals, especially arrays, to build logic

Practice volume

  • Solved about ~300–400 LeetCode-style problems (transcript wording imperfect, but volume is clear)

F) Choosing “skill” for NQT interview (AI vs SQL example)

  • There’s a section: choose your skill for the interview
  • Many choose AIML, but the speaker chose SQL because:
    • comfort from more practice in SQL
    • AI/LMM/agents/overfitting concerns felt like they could lead to deeper questioning

G) Interview rounds & how to behave

Interview structure

  • Only two rounds:
    • Technical
    • HR

Confidence and communication rules

  • Enter with confidence (mentioned: “big smile”)
  • Treat it like a discussion, not adversarial
  • Use simple, clear English
  • Don’t rush—avoid stuttering from speed; speak comfortably
  • Show fundamentals and be responsive to interviewer questions

Technical topics mentioned

  • DSA examples:
    • reverse a string (discuss optimal approach, not just brute/trivial)
    • merge two sorted arrays (tie to merge sort intuition)
    • trapping rainwater (write intuition/thought process/pseudocode)
  • Python basics:
    • slicing and slicing syntax
    • justify why an approach is optimal (time complexity)
  • SQL basics:
    • update/alter/write queries
    • joins: left join, right join, inner join, full join
      • explain with example tables (dummy data)
    • window functions:
      • difference between rank, dense_rank, and row_number

Handling AI/ML project questions

  • If asked how much AI you know and what you did:
    • use AI tools for assistance, but emphasize fundamentals
    • acknowledge gaps (e.g., deployment knowledge)
    • explain how you used a model approach and discuss classification vs what you used

Personal fit questions

  • Questions like:
    • where you live
    • willingness to explore
    • hobbies (used to show time management and growth mindset)

Asking questions back

  • Don’t say “no questions”
  • Example suggestion: ask what the interviewer expects from the candidate if hired

H) Final preparation tips (explicit)

  • Consistency is everything: start and complete whatever you begin thoroughly.
  • Don’t get stuck on arrays:
    • If arrays take too long (e.g., 1–2 weeks), move on to the next topic
    • Revisit later (e.g., practice difficult items on weekends; revise on weekends)
  • Timeline: run this cycle for 4–5 months for a drastic improvement

Speakers / sources featured

Speakers

  • Ummiti Mittal (host/channel presenter)
  • Shakti Marana (guest; candidate who cleared TCS Prime Interview / NQT)

Sources referenced

  • YouTube (NQT numerical/reasoning and DSA playlists/videos)
  • Striver A to Z sheet (recommended DSA resource)
  • LeetCode (used for “famous questions” reference)
  • Python (primary coding/DSA language)
  • ChatGPT / similar AI tools (used for assistance and explanations, including deployment-related learning)

Rate this summary

Your feedback will help improve summaries.

Improve this summary

Reprocess with a stronger model when the summary feels incomplete or inaccurate.

Pro

Translate summary in another language

Pro

Ask questions to this video

Chat for follow-up questions, clarifications, and source-backed answers.

Coming soon

Share this summary

Original video