What questions are asked in Target interviews?

Target interviews commonly cover DSA coding (Top-K frequent elements in order stream; Shortest path in a warehouse grid), core CS (OOPs, DBMS/SQL, OS basics where relevant), project discussion, and topics tied to the business such as retail systems, inventory, Java. Behavioural questions check ownership, teamwork, and why Target.

How many rounds are there in the Target interview?

Target typically has 4 stages: Online Assessment (90 min), Technical Round 1 (45–60 min), Technical Round 2 (45–60 min), HR (20–30 min). Some drives skip GD or merge HR with managerial. Always check the mailer for that cycle.

How should I prepare for Target interviews?

For Target, prioritise DSA practice with timed mocks, revise OOPs and SQL, prepare a crisp project narrative, and read up on retail systems and inventory. Use STAR for behavioural answers and ask one thoughtful question at the end.

Target Interview Experience 2025–2026 — Real Candidate Stories

Target interview experience

These write-ups reflect how Target fresher interviews usually go — campus and off-campus. Patterns shift by year and role, so use this as a prep map, not a script.

Target placement process includes: 1. Online Assessment (90 minutes) - Coding/aptitude questions. 2. Technical Interview Round 1 (60 minutes) - Technical concepts. 3. Technical Interview Round 2 (60 minutes) - Advanced concepts and projects. 4. HR Interview (30 minutes) - Motivation and company fit. Total duration: 2-3 weeks from application to offer.

Most drives expect a clean academic record (often around 6.0–6.5+ CGPA with no active backlogs). Candidate-reported detail: Target eligibility criteria for freshers 2025 include: Degree required: B.Tech/B.E./M.Tech/MCA in relevant fields. Batch: Final year students and recent graduates. Academic Record: Typically 7.0+ CGPA or 70%. Backlogs:…

Fresher offers (candidate-reported) often land around gust 2026): Software Engineer/Analyst: ₹15-25 LPA (CTC, including base salary, bonus, and benefits). The comp. Treat numbers as directional — confirm on your offer letter.

Round-wise process

Round	Duration	What they test
Online Assessment	90 min	2–3 coding problems
Technical Round 1	45–60 min	DSA + project discussion
Technical Round 2	45–60 min	System design (orders / logistics)
HR	20–30 min	Behavioural + culture fit

Real interview experiences

Experience 1: SDE / Software Engineer (2025)

Profile: B.Tech CSE, 7.8–8.4 CGPA, tier-2 college, 1 internship, decent DSA practice (150+ problems)

Online / written round

Focus stayed on problem-solving speed and clean code, not trick questions.
Cleared with full or near-full test cases; shortlist mail came in a few days.

Technical rounds

Coding: Top-K frequent elements in order stream — approach used: heap / bucket sort. Interviewer cared about complexity and edge cases.
Follow-up coding: Shortest path in a warehouse grid — BFS.
Domain discussion around retail systems and inventory — they wanted practical trade-offs, not buzzwords.
Project deep dive: why you chose the stack, what broke in production/testing, what you would redo.

HR / managerial

Why this product?
Example of working with ambiguous requirements
Keep answers short and specific. Name the conflict, what you did, and the result.

Result: Selected What helped: Explaining approach before coding, admitting unknowns early, and linking project work to Target’s domain (retail systems).

Experience 2: SDE / Software Engineer (2024–2025)

Profile: B.Tech IT / ECE, 7.2 CGPA, strong projects, average competitive programming

What differed

OA felt tougher on time; one medium-hard problem needed an optimised solution to clear the bar.
Second technical leaned more into Java and system design basics (APIs, DB choice, failure modes).
Coding warm-up: Merge overlapping delivery slots — interval merge.

Mistakes to avoid

Jumping into code without clarifying constraints
Treating HR as a formality — Target still filters on communication and intent
Memorising system design jargon without a simple capacity / bottleneck story

Result: Selected after a managerial / HR round Takeaway: For Target, consistent DSA plus a clear story on retail systems beats a perfect CGPA with weak explanation.

Questions that come up often

Coding / technical

Top-K frequent elements in order stream — typically expects heap / bucket sort
Shortest path in a warehouse grid — typically expects BFS
Merge overlapping delivery slots — typically expects interval merge
Discussion on retail systems and inventory — capacity, failure modes, simple APIs
Project deep dive — architecture, hardest bug, what you would change

HR / behavioural

Why this product?
Example of working with ambiguous requirements
Weekend / on-call comfort
Relocation

Practical tips for Target

Practise DSA under a timer. Clearing the OA matters more than polishing a perfect resume line.
For domain rounds, be ready to talk about retail systems in plain language — inputs, outputs, bottlenecks.
Revise OOPs and SQL; many Target panels still open with fundamentals.
Keep HR answers concrete. One story with a clear result beats five buzzwords.
If you do not know something, say so and outline how you would find out. Guesswork wastes the round.

Target HR Interview Questions — common HR questions and how to answer them
Target Preparation Guide — round-wise prep plan
Target Coding Questions — practice problems with approaches
Target Previous Year Papers — past papers and patterns
Target Placement Papers — company overview, eligibility, and process

Last updated: August 2026