Target Software Engineer interview typically runs 4-6 rounds: recruiter screen, coding assessment, technical interview, hiring manager, and onsite/panel rounds. The process usually takes about 2-4 weeks and is fairly structured, with some candidates reporting extra waiting and format changes.
$100K
Avg. Base Comp
$144K
Avg. Total Comp
4-6
Typical Rounds
2-4 weeks
Process Length
We’ve seen Target evaluate software engineers less like algorithm specialists and more like builders who can explain real tradeoffs. Multiple candidates reported questions centered on past projects, architecture decisions, and how they handled issues like concurrency in Java or debugging broken code. That tells us the team is looking for practical engineering judgment: can you describe what you built, why you chose that approach, and what you’d do when the implementation gets messy?
A recurring theme is that the strongest signals come from candidates who can stay grounded in fundamentals without sounding memorized. We saw ACID, SQL joins, OOP basics, and even insertion sort show up alongside system design-style prompts and repo-based problem solving. The non-obvious part is that Target seems to care a lot about clear communication under ambiguity — one candidate noted a round that shifted from behavioral into technical, while another described a pair-programming exercise where the code didn’t even build cleanly. In other words, they’re watching how you respond when the prompt is imperfect.
We also noticed a consistent emphasis on fit and collaboration. Several candidates said the conversation leaned toward why they wanted Target, how they work with others, and how they explain challenges from prior projects. Even when the technical bar was moderate, the people who moved forward were the ones who could connect their experience to the role in a polished, concrete way. For Target, that combination of hands-on problem solving and calm, credible communication seems to matter more than flashy complexity.
Synthetized from 5 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Target process.
The process felt longer than it needed to be. I started with a recruiter call, then moved into an online coding assignment that was based on Spring Boot. After that I had a hiring manager round where they asked about my past project work and some concurrency in Java, so that part was more about explaining what I had actually built and how I handled threading issues than solving a pure algorithm problem. The next step was a pair programming round over Zoom, and that was the most frustrating part for me. They gave me code with a bug and expected me to fix it and write test cases in about 1.5 hours. Even when I found the issue, the code apparently still would not build, and the interviewer did not seem very interested in helping or adjusting the exercise. I also got a topological sorting question framed around a repo, so there was still some data structures and algorithms mixed in with the stack-specific work.
There were also a couple of face-to-face technical rounds that stayed focused on projects and general technical discussion. One round that was supposed to be behavioral ended up turning into another technical interview, which was a little off-putting because it felt like the format changed on the fly. Overall the questions themselves were not especially complex, but the process was tiring because there were so many rounds and the expectations in the pair programming session were not very clear. I ended up getting rejected with no offer and no real feedback afterward. If you’re preparing, I’d make sure you can talk through a Spring Boot project in detail, explain concurrency in Java clearly, and practice debugging broken code while writing tests under time pressure.
Prep tip from this candidate
Be ready for a Spring Boot-based coding assignment, then practice explaining a Java project with concurrency details in a hiring-manager style discussion. Also drill live debugging and test writing, since the pair programming round centered on fixing buggy code that may not even build cleanly.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Target
Write a query to identify customers who placed more than three transactions each in both 2019 and 2020
| Question | |
|---|---|
| Monthly Customer Report | |
| Over-Budget Projects | |
| Average Order Value | |
| Hurdles In Data Projects | |
| Black Friday Shopping Spree | |
| Common Prefix | |
| Sales Leaderboard | |
| Client Solution Pushback | |
| Your Strengths and Weaknesses | |
| Slow OLAP Aggregations | |
| 2nd Highest Salary | |
| Random SQL Sample | |
| Total Spent on Products | |
| Valid Anagram | |
| Cumulative Sales Since Last Restocking | |
| Max Quantity | |
| Total Transactions | |
| ATM Robbery | |
| Monthly Product Sales | |
| String Palindromes | |
| Find Mismatched Words | |
| Testing Constraints | |
| Azure Kubernetes Infrastructure | |
| Why Do You Want to Work With Us | |
| Friend Requests Down | |
| Generative AI Privacy | |
| Weighted Average Sales | |
| Employee Salaries | |
| Closest SAT Scores |
Synthesized from candidate reports. Individual experiences may vary.
The process usually begins with a recruiter phone call or chat after an application or outreach through LinkedIn or Indeed. This step covers your background, interest in Target, role fit, and a preview of the next steps.
Candidates are commonly asked to complete an online screening assessment or coding challenge. Reported formats include technical MCQs, DSA questions, and a Spring Boot-based assignment that must be submitted by a deadline.
This round focuses on practical coding and core technical fundamentals. Interviewers have asked algorithm questions like longest substring, array rotation, insertion sort, and topological sorting, along with DBMS basics such as ACID properties, SQL joins, and OOP concepts.
A later round often shifts toward project discussion and system thinking. Candidates were asked to explain past work, discuss Java concurrency and threading issues, and talk through how they would build a specific application at a high level.
The final stages can include face-to-face or virtual conversations with devs, directors, or store leadership depending on the role. These interviews tend to mix behavioral questions, project discussion, and general technical conversation, and in some cases a behavioral round may turn technical.