How Target Corporation India campus internship and full-time loops usually run, synthesized from public GeeksforGeeks and Bengaluru SWE reports. We reorganized OA → combined tech+HR panels versus multi-round experienced-hire paths - treat this as a prep map, not a script.
Round-wise process at a glance
Round
Typical format
What clears you
Recruiter screen
~30 min phone/Zoom
Motivation, logistics, comp band
Online assessment
HackerRank 60-90 min; 2-3 DSA + SQL on many drives
Fully passing solutions; SQL not skipped
Technical 1
40-50 min; live coding + machine coding
Clean code, tests, narrated complexity
Technical 2
~60 min; DSA + system/API design
Retail-scoped design; resume depth
HR / behavioural
20-30 min (sometimes combined with tech on campus)
Guest-centric STAR; consistent timeline
Campus intern variant
OA → ~75 min combined tech+HR Zoom
Python depth if claimed; delayed results
Full-time vs campus: Experienced-hire loops in Bengaluru often run four separate technical/managerial rounds (DSA, Spring/microservices depth, scaling, API design) before HR. Campus internship accounts frequently merge technical and HR into one long panel - see cards below.
Technical interview experience 1 - Internship, on-campus pool 2023
Technical interview experience 1
Candidate profile: CS/IS/AIML/EC eligible; Dec 2023 virtual pool drive
Round 1 - OA
Shortlist from online assessment into interviews
HR schedules Zoom slots at student convenience in that account
Tip: Keep calendar flexible - panels can span days
Round 2 - Technical + HR (~75 min)
Two interviewers (one data engineer, Python-strong)
Intro including past intern and CV projects
Preferred language Python; rate skills /10; dive into coding
DS: queues and stacks; how to check empty
OOP; DBMS; DML; SQL transactions; MySQL vs PostgreSQL if used in projects
Python multithreading? → GIL discussion; mutex and semaphores
HR scenarios: team rejects your week-long solution - how do you handle?
Family/hometown; your questions (team, culture, feedback)
Final result: Selected with 3 others after ~12 days; some peers needed another round
Tip: Ask for feedback politely if network allows
Takeaways
What decided it: Calm coding after a honest Python self-rating, then queues/stacks, OOP/SQL transactions, GIL/mutex answers, and a teamwork STAR when a solution is rejected.
Common fail: Inflating the /10 rating; shallow MySQL vs PostgreSQL reasons.
How to practise: One live Python coding sit plus GIL explanation aloud; one “team rejects your idea” STAR.
Occasional Java Streams task: sort/filter strings by leading character
Machine-coding round
Handed messy or log-corrupted code - parse, clean, extend with SOLID-ish structure
Expected: error handling, logging hooks, unit tests - not a one-liner fix
Spring Boot annotations, DI, JPA pitfalls appear in follow-ups
Tip: Practice reading unfamiliar repos on GitHub before the drive; Target scores test quality alongside the fix
Key takeaways: Retail context shows up as inventory, orders, and delivery routing - not abstract puzzle names only.
HR interview experience
HR interview experience
Candidate profile: Same combined panel
Behavioural scenarios
Team rejects your solution after a week of work - response?
Other teamwork conflict prompts
Family / hometown light chat
Questions for interviewers
Final result: Combined with technical score; delayed results possible
Key takeaways: Show humility and data-driven pushback - not ego, not instant surrender.
Sample answers for high-frequency questions
Use these as frames, not scripts.
Technical
Q. Does Python support multi-threading? A. Yes for I/O-bound concurrency, but CPython’s GIL means one thread executes Python bytecode at a time - CPU-bound parallelism often needs multiprocessing or native extensions. Know mutex/semaphore ideas for shared-state safety.
Q. Stack vs queue empty check? A. Stack: top/size == 0. Queue: front==rear or size==0 depending on implementation. State your structure explicitly.
Q. MySQL vs PostgreSQL - when you picked one? A. Tie to project needs (JSON, extensions, familiarity, hosting). Avoid religious wars - show a pragmatic reason.
HR
Q. Team rejected your solution - what do you do? A. Listen to objections → ask for criteria → compare options with data/prototype → adapt or defend with evidence → document decision. Emphasise team outcome over being right.
These links are research inputs we used to map campus and Bengaluru loops - not copied page mirrors. We reorganized reports into process tables, outcome notes, and prep takeaways for Target India.
