Target L4 Java Backend | In-person Drive | 3 Rounds | Bangalore | Awaiting Result
Background: 2 YOE, Java Backend Developer at a service-based company working with a banking client. Applied through the Target careers page, cleared the OA, and attended a one-day in-person drive in Bangalore. Once you read the interview experience, can you please share your view on getting the offer letter.
Online Assessment (28 September 2026)
1.Greedy + PriorityQueue (Variation of Task Scheduling) - Hard
2.Stack + Greedy + String - Medium Hard
3.Toplogical Sort + Mutli-BFS - Medium
Round 1 — Technical (6th October 2026)
Topics included:
- Projects and project-based scenarios
- Java
- Spring Boot
- Kafka
- Database optimization
The discussion was mostly scenario/project based rather than purely theoretical.
Result: Positive
Round 2 — Projects + Pair Programming + Design Patterns (6th October 2026)
First 30 min — Projects
Deep discussion about my current/recent projects.
Next 30 min — Pair Programming
Was given 3 bugs to identify and fix. I was able to resolve all 3.
Last 25 min — Design Patterns
Implemented:
- Strategy Pattern — for extensibility
- Factory Pattern — for object creation
Result: Positive
Round 3 — Hiring Manager (6th October 2026)
The round was scheduled for 1 hour but lasted approximately 2 hours.
The HM repeatedly asked a question I found interesting:
"What problem existed, and what problem does this solve?"
The discussion was very conversational and focused heavily on engineering reasoning and trade-offs.
Projects
Discussed a project that reduced downtime by 62% for around 10 minutes, including several follow-up questions.
Database / Scalability
Discussed a database with millions of rows:
- Indexing and write trade-offs
- Selecting only required columns
- Query optimizer hints
- Caching
- N+1 query problem
- Partitioning
Then discussed:
- Sharding — when to use it, advantages/disadvantages
- Replication — when to use it, advantages/disadvantages
The HM specifically said regarding my partitioning answer:
"Exactly, I am looking for this from you."
Security
Discussed:
- Authentication vs authorization
- JWT
- Encryption
- Security using real-world examples
This was particularly relevant because the role is a Java Backend Engineer (L4) within a Cybersecurity/IAM team, and my current project is in the banking domain where security is a major concern.
Messaging / Distributed Systems
Discussed:
- Why IBM MQ was used in my project
- Trade-offs
- Resilience patterns
- Circuit Breaker in detail, including what happens in each state
- Short discussion on Saga
- Kafka — what problem it solves and how I used it in a progress-tracking service
AI / LLM / RAG
Discussed:
- How I use AI during development
- Whether AI-generated code can go directly to production
- My code-validation process: business requirement verification → code review → dry run → sanity testing → QA/SIT → production
- How LLMs work
- RAG
- PDF upload and processing
- Chunking
- Vector database / retrieval
Behavioral / Managerial
Discussed:
- Conflict with a manager
- How I measure growth
- Why Target?
- Why am I leaving my current company?
- How I handle deadlines
- Delivering a service within 2 days
- Prioritizing my own delivery vs helping a teammate
- Supporting an upstream team with an issue
- My troubleshooting approach: logs → request level → application → DB → gateway/infrastructure
- Whether I've ever missed a deadline
- Communication feedback I've received from colleagues
I was also asked to rate myself in Java and Spring Boot. I said 8.5–8.8/10, while mentioning that there is always room for improvement.
At the end, the HM explained some of the challenges an employee might face during the first 90 days and said he would share his feedback with HR.
Questions Where I Fumbled
There were a few questions where I couldn't immediately recall the terminology:
- The name of the pub/sub model when multiple consumers consume the same event
- Defining RAG specifically from the retrieval/context perspective
- The terminology for overlapping chunk context
- Disadvantages of a very large prompt/context — I initially struggled, and the HM mentioned cost
These were mainly terminology/concept-recall gaps, rather than problems with the core backend topics discussed throughout the interview.
Overall Experience
Overall, I felt the first two rounds went well, and the HM round was a very deep and conversational discussion.
The HM spent significant time on databases, distributed systems, security, messaging, resilience, AI/RAG, projects, and behavioral scenarios.
I'm now waiting for the final result and wondering how much the few gaps in newer areas like RAG/LLMs might weigh against the overall performance.
October 8th (7.30 PM): Rejection
HR called me my profile not inclined. we are not able to move forward.in round 2 i they did not get what they want.
In 2nd round interviewer told i have very good bug fix skills.
Even if we do lot of hardwork, end of the day luck matters. Tough day for me.
#target #interview #feedback #backend engineer #L4 #rejected


