Engineer L4 at Target
- Difficulty
- Process took
- 1-2 Weeks
- Rounds
- 3
- Format
- On site
- Applied via
- Referral
How it went
- I walked out feeling drained and disappointed. But here’s the truth you can’t control the outcome, only the preparation. Treat each interview as a story you’re telling, not a test you’re passing. You’re a professional, not a student.
What they would tell you
- I walked out feeling drained and disappointed. But here’s the truth you can’t control the outcome, only the preparation. Treat each interview as a story you’re telling, not a test you’re passing. You’re a professional, not a student.
How to prepare
- Don’t go by labels like “HM Round” or “Behavioral.” My HM round turned out to be the most technical of all code on paper, system explanation, even edge-case optimizations.
- Be mentally ready to switch gears quickly.
- They care how you approach. Think aloud. Start with brute force. Explain trade-offs. Talk about space/time. Code clarity matters more than clever tricks.
Round by round
- 1
DSA + Core Concepts60 min
This round started with a quick walkthrough of my resume and current project. Then came the coding part. First question was Product of Array Except Self, I started with brute-force and improved it step-by-step to an O(n) solution with constant space. They also asked me to think about edge cases like zeros and negative numbers, and explain where my logic might fail. After that, there was a Java Streams question, I had to separate odd and even numbers using a single stream pipeline. They were checking how comfortable I was with functional programming, and they seemed happy with how I approached it.
- 2
System Design + Deep Dive60 min
The round started on a personal note, I was asked to share two proud moments from my professional journey. Then we moved into technical questions like:
- Why use Redis instead of an in-memory Java map?
- What are the trade-offs between Kafka and traditional message queues?(The focus was more on understanding my reasoning rather than just tool knowledge.) After that, I was given a system design-style question: How would you design a system to find the nearest available driver, like Uber? We discussed things like proximity filtering, geohash/grid-based indexing, caching, and keeping driver locations updated in real-time. The round wrapped up with a few Java questions, mainly around Streams and Lambdas, and how I use them in real projects. Overall, it was a challenging round, but I felt good about how it went.
- 3
HM Round60 min
This round was tougher than expected. I was told by HR that it would focus on team fit and expectations, but it turned into an in-depth technical evaluation. After introductions, they jumped straight into my current project, I had to explain the design and then write a small module (which I built at work) on pen and paper. I struggled here. I wasn’t mentally prepped for code writing in this round, and it showed. Then came another Java Streams question. They asked me the classic: Two Sum - I explained brute force, then sorting + two - pointer, and finally the hashmap-based O(n) approach. When told that hashmap wasn't allowed due to memory concerns at scale, I argued that the sorting approach was optimal under such constraints, on which they appreciated. The last 2–3 minutes were behavioral, why I was switching, what kind of work excites me, etc. To be honest, I left the room feeling drained. After back-to-back interviews and an unexpected level of depth in the HM round, I knew I hadn’t given it my best.
What came up
A candidate-reported account, lightly edited. Interview processes change by team and date.