HR interview questions
Common Target HR questions, sample answer frames, and STAR tips.
Target Interview Experiences
How Target fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat 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.
Eligibility (from student reports): 7.0+ CGPA or 70%.
Fresher package ballpark (from student reports): Analyst: ₹15-25 LPA. Confirm on your offer letter.
Round-wise process
Section titled “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
Section titled “Real interview experiences”These are rewritten from public candidate write-ups, not invented composites. Details differ by campus and year.
Experience 1: Software Engineer, on-campus
Section titled “Experience 1: Software Engineer, on-campus”Source: Target Corporation India Interview Experience (On-Campus) - GeeksforGeeks
Round 1 - Online assessment (HackerEarth)
- 11 questions: 10 predict-the-output MCQs plus one 100-point coding problem (given a list of product costs, apply a 30% discount to items above $50 - deliberately retail-flavoured).
- Roughly 80 candidates sat the drive; 16 reached the interviews.
Round 2 - Technical 1 (panel of 2)
- OOP fundamentals, and a live “sum an array in Java” style warm-up.
- Heavy SQL: SELECT, joins, primary/foreign key constraints, normalisation, ACID. The candidate was asked to draw sample tables, populate them with dummy data, and write queries against them on the spot.
- Git/GitHub usage, then the web project on the resume and how its database was designed.
Round 3 - Technical 2 (panel of 2, holding notes from round 2)
- Java access specifiers, inheritance and abstract classes.
- Why merge sort is efficient; how Google ranks search results; REST API calls via AsyncTask; synchronous vs asynchronous execution.
Outcome: 3 offers from the 16 interviewed. Notably, no separate HR round in this drive.
Experience 2: Internship, on-campus (December 2023)
Section titled “Experience 2: Internship, on-campus (December 2023)”Source: Target Corp. Interview Experience For Internship (On-Campus) 2023 - GeeksforGeeks
- Round 1 - Online assessment: MCQs across reasoning, logic, quantitative and technical, plus two coding questions (count the digits in a number; one graph problem). Open to CS, IS, AIML and EC branches; 29 shortlisted. All rounds virtual.
- Round 2 - Combined technical + HR (75 min, two interviewers on Zoom, one a Python-focused data engineer): tuples vs lists and branchless programming in Python; stacks and queues with real use cases; overloading vs overriding and the diamond problem; DBMS - DML commands, transactions, MySQL vs PostgreSQL; then multithreading, the GIL, mutexes and semaphores. Closed with scenario questions on teamwork and conflict.
- Outcome: 4 selected, with 5-6 taken into further rounds. The interviewer’s own advice in the write-up was to pause before answering and keep answers articulate.
Common thread: Target’s fresher loop is unusually fundamentals-and-SQL heavy rather than a LeetCode grind - expect database design you have to write out, OOP theory, and language-specific internals for whatever you list on your resume.
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “Coding / technical”- Top-K frequent elements. Usually expects heap / bucket sort
- Shortest path in a grid. Usually expects BFS
- Merge overlapping delivery slots. Usually expects interval merge
- Discussion on retail systems and inventory, bottlenecks, failure modes, simple APIs
- Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
Section titled “HR / behavioural”- Why this product?
- Working with unclear requirements
- On-call or weekend comfort
- Relocation
Practical tips for Target
Section titled “Practical tips for Target”- Clear the screening round first. Timed practice beats last-minute topic hopping.
- For domain questions, explain retail systems in plain language, inputs, outputs, what breaks at scale.
- OOPs and SQL still open a lot of Target panels. Do not skip fundamentals.
- HR answers should be concrete. One story with a result beats five slogans.
- If you do not know something, say so and outline how you would find out.
HR interview
Section titled “HR interview”After technical rounds, Target usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.