Service Company Interview Patterns

This page covers what’s different about interviewing at large IT services companies versus a generic Java/Spring Boot interview - round structure, each company’s technical slant, and non-technical gotchas. It does not repeat core Java/Spring Boot content; use the Java + Spring Boot Cheat Sheet for that.

A note on sourcing: round-structure and technical-emphasis claims below are cross-referenced from multiple recent (2024-2025) interview-experience write-ups (Glassdoor, Medium, GeeksforGeeks, jointaro). The “practice questions” under each company are not verbatim leaked questions - they’re written in that company’s reported style/emphasis so you can rehearse the shape of what gets asked. The “gotchas” section at the bottom is lower-confidence (thin sourcing) - treat it as directional, not guaranteed.

The Coding Round Is Real - Don’t Skip It

TCS, Wipro, and IBM in particular gate even 8-10 YOE candidates behind a timed online assessment (HackerRank, AMCAT, or a similar platform) before any human technical round. This is not the same as a live “explain HashMap” conversation - expect:

• 1-2 DSA problems, typically easy-to-medium (string/array manipulation, basic recursion, sometimes SQL queries)
• A time limit (usually 60-90 minutes total)
• Sometimes an MCQ section on Java/OOPs/DBMS fundamentals alongside the coding problems

Practice with the Java Interview Programming Questions guide - it’s specifically curated from reported senior-level coding-round questions (string problems, number problems, array/collection problems), not generic LeetCode-style content.

Common Round Structure (applies broadly across all 8)

Online Assessment (where applicable) → 1-2 Technical Rounds → Managerial Round → HR Round. Total 3-5 rounds over 2-4 weeks. The technical rounds test Core Java/OOPs first, then Spring Boot/microservices/project-specific depth.

Per-Company Notes

TCS

• Interviewers emphasize practical scenario usage over textbook definitions - they want to see you reason through a situation, not recite a definition.
• A managerial round is a distinct, separate stage even for senior individual contributors (not folded into the technical round).

Practice-style questions:

• “Your Spring Boot REST endpoint is timing out intermittently under load - walk me through how you’d diagnose it.”
• “Design the JPA entity relationships for [a scenario relevant to your project] - explain your fetch-type choices.”
• Managerial: “How do you handle a teammate who consistently misses sprint deadlines?”

Infosys

• Notably tests Java 8-21 language features (Streams, Optional, var, records) plus Spring bean lifecycle internals (@PostConstruct/@PreDestroy ordering), AOP, and the practical difference (or lack thereof) between @Component/@Service/@Repository.
• Leans more toward “framework internals trivia” than pure DSA.

Practice-style questions:

• “Walk me through what happens, step by step, when a Spring Boot application starts up - bean creation order, @PostConstruct timing, when AOP proxies get created.”
• “Functionally, does it matter whether I annotate a class @Component or @Service? What actually changes?”
• “Write a custom AOP aspect that logs the execution time of any method annotated with a custom annotation.”

Accenture

• The interview almost always opens with a deep dive into your resume/current project - tech stack, your specific responsibilities, and a technical decision you made and why - before any generic technical question. This is the single most Accenture-specific pattern reported.
• Structure: 2 tech rounds (Core Java/OOPs → Spring Boot/microservices/project) + HR.

Practice-style questions:

• Prepare a tight 2-3 minute walkthrough of your current project’s architecture and your role in it - this functions as the real first “question.”
• “Tell me about a technical decision in your current project you’d make differently now, and why.”

Capgemini

• Distinctive structure: L1 (telephonic screen) → L2 (technical and managerial combined in one round) → HR. Other companies typically split these.
• Heavy on Java 8 features, classic design patterns (especially Singleton), and Spring bean scopes.
• Reported difficulty varies significantly by account/project team - don’t assume every panel is the same bar.

Practice-style questions:

• “Explain the Singleton pattern - and how does Spring’s default singleton bean scope differ from the classic GoF Singleton implementation?”
• “Where in a typical Spring Boot service layer would you reach for the Builder pattern?”

Wipro

• HackerRank OA is a hard gate even at 5-10 YOE.
• Design patterns (Singleton/Factory/Builder/Observer/Strategy) are frequently tied to “this is how our codebase uses it” framing rather than asked abstractly.
• HR round explicitly expects 3-4 prepared STAR-format stories tied to Wipro’s stated values (integrity, transparency, care) - this is worth preparing for specifically, not generic behavioral prep.

Practice-style questions:

• “Which design pattern would you use to support multiple interchangeable payment gateway integrations, and why?” (Strategy pattern is the expected answer shape.)
• Prepare STAR stories in advance: a time you handled a conflict with integrity, a time you were transparent about a mistake, a time you supported a struggling teammate.

HCLTech

• Rounds are reported as relatively informal/conversational rather than strict Q&A drilling.
• Notably mixes React/frontend questions into backend-titled roles more than other companies - directly relevant if you’re positioned as “full-stack.” Have the React Survival Kit genuinely ready, not just Java/Spring Boot.

Practice-style questions:

• Be ready to explain a basic React concept (hooks, component lifecycle) even if the role is titled “Backend Developer.”

IBM

• Most consistently tests DevOps/toolchain breadth - Maven, Git, Jenkins, Docker, Kubernetes - alongside Spring Boot internals, more so than the other 7 companies.
• Explicit JUnit/Mockito unit-testing questions are common.
• Manager round focuses on scenario-based questions: conflict handling, delivery pressure, “how would you handle X common project situation.”

Practice-style questions:

• “Walk me through your project’s CI/CD pipeline - what does the build/deploy flow actually look like?”
• “How do you mock a repository dependency when unit-testing a service-layer method with Mockito?”
• Managerial: “Describe a time delivery pressure conflicted with code quality - what did you do?”

Tech Mahindra

• HR round is reported to include some unusual questions: relocation/shift-work willingness, and in some accounts, family-background questions - not typical of the other 7 companies.
• Behavioral questions lean toward stress-management and analytical-thinking probes.

Practice-style questions:

• Be ready to answer relocation/shift-flexibility questions directly and confidently - hesitation here is reportedly read negatively.

Cross-Cutting Gotchas (lower confidence - thin sourcing, treat as directional)

• The resume/project walkthrough is often the real first technical gate across nearly all 8 companies, most explicit at Accenture. Always have a crisp, confident 2-3 minute project narrative ready before anything else.
• Managerial rounds commonly probe scenario judgment: handling a client escalation, onboarding a junior teammate, or responding to a production incident - not pure technical knowledge.
• HR rounds commonly ask about notice period, relocation/shift flexibility, and reason for leaving your current company - have consistent, confident answers ready; these get asked almost everywhere even though this list can’t cite hard frequency data for each company individually.

Key Takeaways

• The technical bar is real Core Java/Spring Boot/microservices depth, not simplified questions - don’t underprepare thinking service companies mean “easy.”
• Each company has one dominant differentiator worth targeting specifically: Accenture (resume deep-dive gate), Infosys (framework internals), IBM (DevOps toolchain breadth), Wipro (design patterns + values-aligned HR), Capgemini (combined tech+manager round), HCLTech (React crossover risk), Tech Mahindra (unusual HR probes).
• If there’s an OA in the pipeline (common at TCS/Wipro/IBM), it is a hard gate - practice DSA problems beforehand, don’t rely on technical-round strength alone.