Skip to content
Interview Questions

Service vs Product Interview Prep

Campus season in India often means parallel tracks: service majors like TCS, Infosys, and Wipro alongside product targets like Google, Amazon, and Flipkart. Using one undifferentiated LeetCode binge for all of them wastes time. The skills overlap; the emphasis does not.

Key takeaways

  • Keep a shared core: communication, projects, CS fundamentals, basic DSA.
  • Add a service layer: subjects + HR logistics + OA carry-over.
  • Add a product layer: deeper DSA, behavioural ownership, format drills (Doc, timed coding).
  • Schedule by interview date, not by brand prestige alone.
  • Read each company’s experience page for format, not as a universal syllabus.

What “service” and “product” mean here

These are prep shortcuts, not moral categories.

Service-leaning campus loops often optimize for trainable fundamentals, communication, and fit for project deployment models. Assessments (NQT-style, Infosys-style, Wipro assessments) matter a lot before you ever speak to an interviewer. See TCS NQT to interview.

Product-leaning loops usually put more weight on problem-solving depth, code quality under follow-ups, and behavioural evidence that you can operate in ambiguous product teams. HR still exists, but it is not the only behavioural filter (see Googleyness vs HR and Amazon LP prep).

Indian product companies such as Flipkart sit closer to the product pattern: serious DSA, role-related depth, and structured behavioural questions, with campus logistics still in play.

Comparison table

Prep area Service-leaning (TCS / Infosys / Wipro) Product-leaning (Google / Amazon / Flipkart)
OA Often decisive; aptitude + coding variants Coding OA or phone screen; harder DSA bar
Technical interview OOP, DBMS, OS, networks, project deep-dive Multi-round DSA; design at higher levels
Behavioural HR + light managerial Dedicated LP / Googleyness-style depth
Code expectation Correctness + clarity; language basics Optimal approaches, edge cases, complexity
Differentiation Communication, consistency, trainability Signal of strong problem-solving + ownership

Shared core (do this once)

Regardless of company type:

  1. One project you can defend for 15 minutes with architecture, your module, a bug, and a metric.
  2. CS fundamentals shortlist you can explain with an example, not a definition dump.
  3. DSA baseline - arrays, strings, hashing, recursion, basic trees; enough to not embarrass yourself on either track.
  4. HR fact sheet - education timeline, location, joining, backlog, family constraints if relevant.
  5. Reading method - How to read an interview experience so you do not memorize random questions.

Service layer: extra drills

When an Infosys, TCS, or Wipro interview is within two weeks:

  • Rehearse subject Q&A out loud (especially DBMS joins, OOP pillars, OS basics).
  • Prepare “training and location” answers that are honest.
  • Refresh OA weak sections on placementpapers.app for that company.
  • Expect project questions that check whether you actually wrote the code.

Failure mode to avoid: spending all remaining days on hard graph problems while you cannot explain your own database schema.

Product layer: extra drills

When Google, Amazon, or Flipkart is close:

  • Raise DSA difficulty and timed sets; practice follow-ups (“can you do better?”).
  • Match format: Doc coding without autocomplete for Google-style screens; timed IDE for others.
  • Build behavioural depth with STAR stories that fail as a quality check.
  • For Amazon, map stories to LPs without name-dropping. For Google, prep ambiguity and collaboration stories.

Failure mode to avoid: polishing a perfect “why company” paragraph while you cannot finish a medium coding problem cleanly.

A dual-track weekly schedule

Assume you are actively applying to both types:

  • Mon / Thu: DSA block (product depth)
  • Tue: CS subjects + project (service depth)
  • Wed: Mixed mock (one coding + one subject oral)
  • Fri: Behavioural / HR (rotate Googleyness, LP, service HR)
  • Sat: Company-specific: read 2 experiences + OA set for the next drive
  • Sun: Light review + rest; fix notes, do not binge new topics

If only one interview is imminent, collapse the schedule toward that company’s layer for 5-7 days, then rebalance.

Offer strategy note (practical, not preachy)

Candidates sometimes treat service offers as “backup” and product as “real.” Interviewers can sense contempt. Prep each loop respectfully. You can still rank preferences privately after offers exist. Public disdain in an HR round (“I am only here until FAANG”) is a self-own.