How to Prepare for Company-Specific Interviews: TCS, Infosys, Accenture, Capgemini and More

By Preeti Verma

Large IT services companies hire thousands of freshers, and each one runs its own process. Candidates often prepare for "a placement test" in general and then get surprised by the format. A better approach is to prepare for the company you are actually applying to.

This guide explains how to research a company's process, what the usual stages test, and what is commonly reported about TCS, Infosys, Accenture and Capgemini. One honest warning first: hiring formats change from one drive to the next, and most public descriptions come from candidate reports and prep websites, which often disagree. So treat everything here as a map of what to expect, and confirm the current details on each company's official careers page before you plan.

The five-step method for any company

Use this for any company, not just the four below.

  1. Find the official process. Open the company's careers page for graduates or freshers. Note the roles, eligibility and stages they state. This is the only source that is always current.
  2. Match the stages to skills. Each stage tests something specific (reasoning, coding, communication, fundamentals). List them.
  3. Collect recent candidate reports. Look for reports from the last year and prefer ones that describe the same role and hiring route as yours. Ignore anything that disagrees wildly with the official page.
  4. Build a plan around the weakest stage. Most candidates fail at one stage, not all of them.
  5. Practise the format, not just the topics. Timed online tests and spoken interviews need different practice.

What the usual stages test

Across these companies the same building blocks keep appearing:

  • Aptitude and reasoning: quantitative aptitude, logical reasoning and sometimes verbal ability. Speed and accuracy matter.
  • Coding or pseudocode: reading code and predicting output, or writing a short solution. Pseudocode questions test whether you can trace logic without a specific language.
  • Communication assessment: some companies test spoken or written English with automated tools.
  • Technical interview: your fundamentals and your projects.
  • HR interview: communication, willingness to relocate or learn, and fit.

If you are weak in one of these, you know where to spend the time.

TCS

TCS recruits freshers through the TCS National Qualifier Test (NQT), which TCS iON describes as a common entry-level test. The test is reported to have a foundation part (aptitude and reasoning style skills) and an advanced part, and the interview that follows depends on the track you qualify for. Public reports disagree on timing, scoring and which part decides which track, so do not rely on any blog's exact numbers.

What to do:

  • Read the official TCS NQT and careers information for the current cycle, eligibility and application steps.
  • Practise timed aptitude and reasoning, since that is where many candidates lose marks.
  • Prepare coding basics, because the advanced section and later interviews are reported to test them.
  • For the interview, prepare your projects, one language in depth, and basic DBMS and OOP.

Infosys

Infosys describes its graduate routes on its careers site, including campus hiring, the HackWithInfy coding programme and learning programmes such as InfyTQ. For HackWithInfy, the official terms describe coding assessment rounds on the Infosys assessment platform, followed by a finale for qualifiers. The usual fresher flow reported by candidates is an online test, a technical interview and an HR round, with different roles for stronger coding performance.

What to do:

  • Check the official graduates page for which route you are eligible for and when registration opens.
  • Practise coding in the assessment style: read the problem, handle edge cases, and run all test cases.
  • If you target the higher-skill roles, practise data structures and algorithms properly, because that is where those roles are decided.
  • For the technical interview, be ready for basic coding, SQL and your project.

Accenture

Accenture's own recruitment page explains its general process and, importantly, warns candidates that official communication only comes from an accenture.com email address and that Accenture never asks for payment at any stage. Candidates commonly report a communication assessment, a cognitive and technical assessment (reasoning, quantitative ability, pseudocode and basic technical knowledge), a coding round, and then technical and HR interviews. Reports differ on which stages eliminate you.

What to do:

  • Check the Accenture India early-careers page for whether graduate applications are currently open.
  • Practise a spoken communication test: clear pronunciation, steady pace and complete sentences.
  • Practise pseudocode tracing and basic technical topics such as common applications, networking and cloud basics.
  • Prepare normal technical and HR answers for the final interviews.

Capgemini

Capgemini's India careers page lists the general process: application, screening and position mapping, interviews and onboarding, with fresher stages that can include an online aptitude test, a coding or technical assessment, a group discussion for some roles, a technical interview and an HR interview. Candidates widely report game-based aptitude and pseudocode sections in the online assessment, but the exact mix changes by drive and role.

What to do:

  • Read the official recruitment process page and the specific drive notice you are applying through.
  • Practise game-based aptitude style exercises (memory, attention and pattern tasks) and pseudocode tracing.
  • Prepare spoken English for the communication stages and the HR interview.
  • Read our Capgemini Java developer interview guide for technical topics.

Other companies: the same method works

For HCLTech, IBM, Wipro, Cognizant, Tech Mahindra and the rest, repeat the five steps. We also have company guides for HCLTech, IBM, Walmart Global Tech and JP Morgan, and the company-wise question sheets collect reported questions in one place.

A four-week plan that works for most companies

Week 1: aptitude basics (percentages, ratios, time and work, number series) and logical reasoning, 45 minutes a day.

Week 2: coding fundamentals. Arrays, strings, loops and pseudocode tracing. Use our top 50 coding questions.

Week 3: technical fundamentals. Your main language, OOP, SQL, DBMS and operating systems. Use our technical questions for freshers.

Week 4: full mock tests, spoken interview practice and resume review. Check your resume with the free ATS resume checker, and practise out loud with the GenQuest AI mock interview.

Mistakes that cost candidates offers

  • Trusting one blog's exact numbers. Pass marks, timings and cut-offs change. Use the official page.
  • Skipping the communication stage. Strong coders sometimes fail a spoken English check because they never practised speaking.
  • Ignoring pseudocode. It looks easy and many people lose marks to careless tracing.
  • Not knowing their own project. Interviews often start there.
  • Falling for fake recruiters. Genuine companies do not charge candidates fees, and official emails come from the company's own domain. If someone asks for money, it is a scam.

How to read a job description before you prepare

Two roles at the same company can test different things, so read the actual posting. Look for four things:

  1. The role name and level, because an entry-level role and a specialist role often have different stages.
  2. The required skills, which usually point at what the technical round covers.
  3. Eligibility, such as degree, graduation year and academic criteria, which you should confirm on the official page.
  4. The stated stages, if any. If the posting lists them, prepare for those first.

Copy the skills into a list and mark each one "strong," "okay" or "weak." The weak ones become your study plan. This takes ten minutes and saves weeks of studying topics the company never tests.

A one-week aptitude routine that works

Aptitude is the stage that surprises strong coders, because it is about speed. A simple week:

  • Day 1: percentages and ratios, 20 questions, timed.
  • Day 2: time and work, time, speed and distance, 20 questions, timed.
  • Day 3: number series and logical reasoning, 25 questions, timed.
  • Day 4: pseudocode tracing, 10 snippets, with a variable table for each.
  • Day 5: a full mixed mock test under real timing.
  • Day 6: review every mistake and write down the rule you missed.
  • Day 7: rest, or a light revision of your formula sheet.

Repeat it for three or four weeks, and your speed will improve noticeably.

Practising the communication stage

If a company tests spoken English with an automated tool, practise the same way it will test you:

  • Read aloud for five minutes a day, at a steady pace, and record yourself.
  • Repeat sentences you hear, to build listening and speaking together.
  • Answer open questions in 30 to 45 seconds, such as "describe your daily routine" or "explain a recent project."
  • Listen back for filler words, speed and unclear endings.

Clear, complete sentences matter more than a perfect accent.

Test-day checklist for online assessments

  • Read the instructions email twice, and note the start time and any identity requirements.
  • Test your laptop, camera, microphone, charger and internet at least a day before.
  • Prepare a quiet, well-lit room, and tell people at home not to interrupt.
  • Keep your ID ready, and close every other application.
  • Have a backup plan for internet failure, such as a mobile hotspot, if the rules allow it.
  • Follow the proctoring rules exactly. Online tests monitor behaviour, and breaking rules can end your attempt.

Keep a simple tracker for every application

When you apply to several companies, details blur together. A small spreadsheet with one row per company keeps you organised: the role, the date you applied, the stages and their dates, the test deadlines, the contact email, and what you still need to prepare. Check it every morning during a hiring season. Missing a test window because an email was buried is one of the most avoidable ways to lose a chance.

Frequently asked questions

Which company is the easiest to get into?

There is no honest answer. Each hires many freshers with different bars for different roles. Prepare for the stages the company states, and apply to several.

Do I need to know DSA for service companies?

For many fresher roles, basic coding is enough, but the higher-paying or specialist tracks usually test data structures and algorithms in more depth.

Is on-campus or off-campus easier?

On-campus drives are usually simpler to access. Off-campus drives are more competitive but give more chances. Do both if you can.

How early should I start?

Four to eight weeks before the test is realistic if you already know your fundamentals. Start earlier if aptitude or spoken English is a weak point.

Sources and further reading

These are the official pages used for this guide. Always check them for the current process.

The takeaway

Prepare for the company, not for "placements" in general. Read the official process, map each stage to a skill, find your weakest stage, and practise the format. Details change often, so the official page always wins over any blog, including this one.