Interview experience
Target Interview Questions and Answers (2026)
Overview
Section titled “Overview”Target’s India tech hiring runs through Target Corporation India at Manyata Tech Park, Bangalore - a moderate-difficulty, multi-stage engineering loop (OA, live coding, machine coding, system design, behavioural) rather than a retail-store process.
Target interview process at a glance
Section titled “Target interview process at a glance”| Round | Duration | What they test |
|---|---|---|
| Recruiter screen | 30 min | Background, interest in Target, logistics |
| Online Assessment | 60-90 min | 2-3 DSA problems (Easy-Medium) + occasional SQL |
| Technical Round 1 | 40-50 min | Live coding + machine coding (bug-fix/feature/tests) |
| Technical Round 2 | ~60 min | Problem-solving + system design |
| HR / Behavioural | 20-30 min | Teamwork, conflict handling, culture fit |
Recruiter screen
Section titled “Recruiter screen”A short 30-minute call before the technical loop starts - background, why Target, and logistics like location and compensation expectations. It’s a filter, not a technical bar.
Common questions
- Walk me through your resume and current role/projects
- Why are you interested in Target?
- Location and compensation expectations
Online Assessment
Section titled “Online Assessment”A timed HackerRank test with 2-3 DSA problems at Easy-to-Medium difficulty, sometimes including a SQL question. Correctness across test cases matters more than an elegant but incomplete solution.
Common questions
- Array/string manipulation problems at Easy-Medium difficulty
- Graph or tree traversal problems
- SQL query problems (joins, aggregation)
Technical Round 1
Section titled “Technical Round 1”A 40-50 minute round, often with two interviewers, combining live coding in a shared IDE with a machine-coding task - candidates report being handed an existing code sample and asked to fix bugs, add a feature, and write tests, rather than starting from a blank editor.
Common questions
- Fix bugs in a given code sample and extend it with a new feature
- Write test cases covering edge cases for the code you just modified
- Algorithm questions on arrays, strings, or basic graph problems
- Networking and DBMS fundamentals
Technical Round 2
Section titled “Technical Round 2”Roughly an hour of problem-solving and system design, scoped to high-level or low-level design depending on the role’s seniority. Backend-focused questions lean on Spring Boot and API design.
Common questions
- Design a REST API for a retail domain problem (e.g. inventory or order status)
- High-level or low-level design discussion depending on role seniority
- Spring Boot / API design trade-offs for backend roles
- Detailed walkthrough of your strongest project - architecture and hardest bug
Round-by-round narratives are on the Target interview experience page.
HR / Behavioural round
Section titled “HR / Behavioural round”A closing 20-30 minute conversation evaluating soft skills, teamwork, and how you handle conflict or pressure.
Common questions
- Tell me about yourself and why Target
- Tell me about a time you went out of your way to create a great experience for a guest or customer
- How would you handle an unhappy customer during a busy, high-pressure moment?
- Describe a conflict with a teammate and how you resolved it
Sample answer frameworks for each of these are on the Target HR interview questions page.
Common technical interview questions and answers
Section titled “Common technical interview questions and answers”Q: Write a SQL query listing stores whose total sales last month exceeded 100000.
SELECT s.store_id, s.name, SUM(o.amount) AS total FROM orders o JOIN stores s ON s.store_id = o.store_id WHERE o.order_date is at or after the first day of last month AND o.order_date is before the first day of this month GROUP BY s.store_id, s.name HAVING SUM(o.amount) greater than 100000 ORDER BY total DESC. The key distinction is WHERE filtering individual rows before grouping and HAVING filtering the grouped results afterwards - you cannot put the SUM condition in WHERE. Use half-open date ranges rather than BETWEEN so timestamps late on the last day are not silently dropped, and keep the raw column unwrapped so an index on order_date is still usable.
Q: When would you use BFS versus DFS on a graph?
BFS explores level by level with a queue, so on an unweighted graph the first time it reaches a node it has found the shortest path in edges - use it for shortest hop count, level-order traversal, and finding the nearest matching node. DFS uses a stack or recursion, goes deep first, and is the natural fit for cycle detection, topological sorting, connected components, and any problem where you need to explore a full branch before backtracking. Both are O(V + E) time; BFS memory scales with the widest level while DFS memory scales with the deepest path, which decides the choice on a very wide or very deep graph. On a weighted graph neither gives a shortest path, so you move to Dijkstra.
Q: How would you design a REST API for order status in a retail system?
Model resources as nouns: GET /orders/:id returns the order with its current status, and GET /orders with customerId and status query parameters lists them with cursor-based pagination. Use HTTP semantics correctly - 200 for success, 201 with a Location header on creation, 404 for an unknown order, 409 for a state-transition conflict, and 422 for a well-formed request that fails business validation. Make status changes explicit transitions such as POST /orders/:id/cancel rather than a client patching arbitrary status strings, since that lets the server enforce the state machine. Version the API in the path, require an idempotency key on any request that creates or charges, and never expose internal database ids as the sole identifier.
Q: Explain dependency injection in Spring Boot and the difference between @Component and @Bean.
Dependency injection means the framework constructs and supplies a class’s collaborators instead of the class instantiating them, so a service can be tested with a fake repository. Spring scans for @Component and its stereotypes @Service, @Repository, and @Controller, registering each annotated class as a singleton bean. @Bean is a method-level annotation used inside an @Configuration class, where you build the object yourself - the right choice for third-party classes you cannot annotate, or when construction needs conditional logic. Prefer constructor injection over field injection because it makes dependencies explicit, allows final fields, and works without a Spring context in unit tests.
Q: What happens when you type a URL into a browser and press enter?
The browser resolves the hostname through DNS, checking its own cache, the OS cache, then a recursive resolver that walks the root, TLD, and authoritative servers. It opens a TCP connection with a three-way handshake - SYN, SYN-ACK, ACK - and for HTTPS performs a TLS handshake to validate the certificate and agree a session key. It then sends an HTTP request; a load balancer routes it to an application server, which may hit a cache or database, and returns a response. The browser parses the HTML into a DOM, fetches subresources in parallel, builds the CSSOM, executes JavaScript, and paints. Mentioning the caches at each layer, and that HTTP/2 multiplexes those subresource requests over one connection, is what separates a good answer.
Q: What is the difference between a clustered and a non-clustered index?
A clustered index defines the physical order of rows on disk, so a table has at most one - in InnoDB the primary key is the clustered index and the row data lives in its leaf pages. A non-clustered or secondary index is a separate structure whose leaves store the key plus a pointer back to the clustered key, so a lookup on it costs an extra traversal unless the index is covering, meaning it already contains every column the query selects. That is why a random UUID primary key hurts write throughput - inserts land in the middle of the clustered order and cause page splits - while a monotonically increasing key appends cleanly. Composite indexes are usable left-to-right only, so an index on (a, b) helps a query filtering on a but not one filtering only on b.
Q: You are given working code and asked to add tests. What cases would you write?
Cover the happy path first, then boundaries - empty input, a single element, the maximum size, and values just inside and outside each valid range. Add invalid input: nulls, wrong types, malformed strings, and negative numbers where only positives make sense, asserting the specific exception rather than merely that something threw. Cover state-dependent behaviour such as calling the method twice, and any error path involving a dependency, using a mock to simulate a timeout or a 500. Each test should assert one behaviour with a name describing it, and shared setup belongs in a fixture - Target’s machine-coding round scores test quality as heavily as the fix itself.
Q: Given an array and a target, return the indices of two numbers that sum to the target.
Walk the array once, keeping a hash map from value to index. For each element compute the complement of target minus the element, and if that complement is already in the map you have the pair, so return the stored index and the current one. Otherwise insert the current value and index and continue. That is O(n) time and O(n) space, versus the O(n squared) nested loop. Insert after checking rather than before, otherwise an element pairs with itself when the target is exactly twice that value - that off-by-one is the case interviewers actually test.
Frequently asked questions about Target interviews
Section titled “Frequently asked questions about Target interviews”What is the Target interview process for freshers?
Target India’s Engineer process typically runs 4-5 touchpoints over 2-4 weeks: 1. Recruiter screen (30 min) - background, interest, location/compensation expectations. 2. Online Assessment - a timed HackerRank test with 2-3 DSA problems, occasionally with SQL. 3. Technical Interview 1 (40-50 min, often with two interviewers) - live coding in a shared IDE, sometimes a machine-coding task (fix bugs/add a feature to existing code plus write tests). 4. Technical Interview 2 (~60 min) - problem-solving and system design at a level scoped to the role. 5. Behavioural round on teamwork and conflict handling.
Is Target’s India hiring for retail store jobs or software roles?
This page covers Target Corporation India (formerly Target India), the technology arm based at Manyata Tech Park, Bangalore, that builds Target’s e-commerce, supply chain, and enterprise systems. It runs a DSA-plus-system-design engineering loop, distinct from Target’s US retail/store hiring, which has no technical interview component.
What questions are asked in Target interviews?
Online Assessment problems sit at LeetCode Easy-Medium difficulty and often include a SQL question alongside 2 DSA problems. Technical interviews mix live coding (arrays/strings/graphs) with a machine-coding round - candidates report being handed an existing code sample and asked to fix bugs, add a feature, and write tests. Panels also ask about networking fundamentals, DBMS, and Spring Boot/API design for backend roles, plus a deep dive into your strongest project.
How many rounds are there in the Target interview?
Typically 4-5: a recruiter screen, an Online Assessment, one or two Technical Interviews (live coding/machine coding, then problem-solving and system design), and a closing HR/behavioural round. Exact count varies by drive - some campus cycles compress the recruiter screen into the first technical round.
How should I prepare for Target interviews?
Clear the OA with clean, fully-passing solutions on 2-3 LeetCode Easy-Medium problems, and don’t skip SQL practice - it shows up in the OA itself. For technical rounds, practice reading and modifying someone else’s code, not just writing from scratch, since the machine-coding format (fix bugs, add a feature, write tests) is common. Revise core CS fundamentals (networking, DBMS, OOPs) and keep one detailed project story ready. Use STAR for the behavioural round.
Is Target’s interview process considered hard?
Candidate reports describe it as moderate - most engineers who reach the on-site/virtual loop eventually get an offer, and OA/technical questions skew Easy-to-Medium rather than Hard. That said, the Bangalore drive is selective at the recruiter-screen and OA stage, so getting through the funnel is the harder part.