We Are Glad To Inform That You Got The Job- Hope You Hear This Soon-SURVAYU
Home
Posts

Candidate Interview Experience for Swiggy Associate Software Development Engineer Role

 

Job Still Open - CLICK HERE for Job Details

Interview Slot Details

Candidate Name: Anonymous
Slot Time: 27 July 2025, 10:00 AM IST
Mode: Online (Zoom)
Role: Associate Software Development Engineer (aSDE)
Company: Swiggy
Interview Level: Entry (0–1 years experience)

🔥 INTERVIEW SIMULATION BEGINS

📌 TECHNICAL ROUND (Backend Dev, Java, Go, Systems)

Q1. What is the difference between multithreading and asynchronous processing in Java?

Candidate Answer:
"Multithreading involves running multiple threads in parallel on the same process. It's useful when we want to break a task into subtasks that can run concurrently. Async processing doesn’t necessarily need multiple threads — it uses callbacks, event loops, or futures to handle operations like I/O without blocking the main thread."

Feedback:
Good foundational distinction. Would’ve been stronger with code examples.

Skill Assessed: Java concurrency
Mistakes to Avoid: No real-world example shared

Q2. How would you implement a message queue using Kafka? Explain the key components.

Candidate Answer:
"Kafka works on the publish-subscribe model. I'd create a topic, and producers would push data to it. Consumers would read messages from partitions. I'd manage offset tracking manually or through Kafka’s consumer groups."

Feedback:
Solid. Could improve by explaining brokers, Zookeeper (or KRaft), and throughput concerns.

Skill Assessed: Kafka fundamentals
Mistakes to Avoid: Not discussing performance tuning

Q3. What's the difference between Elasticache and Elasticsearch?

Candidate Answer:
"Elasticache is an in-memory data store used for caching (like Redis or Memcached). Elasticsearch is a search engine designed for full-text search and log analytics."

Feedback:
Clean and accurate. Could mention use cases in Swiggy's context like order caching vs search indexing.

Skill Assessed: System understanding
Mistakes to Avoid: Missing use-case linkage

Q4. Can you explain how DynamoDB handles scaling and partitioning?

Candidate Answer:
"DynamoDB automatically partitions data based on the partition key. It scales horizontally by sharding data across nodes. You can use On-Demand or Provisioned capacity."

Feedback:
Correct. Mentioning hot partitions and access patterns would’ve made it stellar.

Skill Assessed: NoSQL scaling
Mistakes to Avoid: No talk of WCU/RCU units

Q5. In Go, how does goroutine scheduling work?

Candidate Answer:
"Goroutines are lightweight threads managed by the Go runtime. The scheduler uses an M:N model, where many goroutines are multiplexed onto a few OS threads."

Feedback:
Impressive! Bonus points for runtime internals.

Skill Assessed: Go internals
Mistakes to Avoid: None here

Q6. Write a simple REST API in Java (Spring Boot) to fetch a list of restaurants.

Candidate Answer:

java
@RestController
public class RestaurantController {
  @GetMapping("/restaurants")
  public List<Restaurant> getAllRestaurants() {
    return restaurantService.getAll();
  }
}

Feedback:
Good. Missed annotations like @Service, and exception handling.

Skill Assessed: Java + REST APIs
Mistakes to Avoid: Skipping layers or validation

Q7. What data structure would you use to implement a Swiggy-style order queue with priority?

Candidate Answer:
"A PriorityQueue would work well. I'd give higher priority to express orders and use a comparator to sort."

Feedback:
Nice. Real-time systems often need more than PriorityQueue. Talk about Redis/ZMQ if possible.

Skill Assessed: Data structures in context
Mistakes to Avoid: Thinking only in Java libs

📌 BEHAVIORAL ROUND (Team Fit, Culture, Curiosity)

Q8. Tell me about a time you worked on a collaborative coding project. How did you ensure code quality?

Candidate Answer:
"In college, we used GitHub for a team project. We did code reviews using pull requests, followed style guides, and ran linters before merge."

Feedback:
Great initiative. Would love to hear how you resolved disagreements in PR reviews.

Skill Assessed: Collaboration
Mistakes to Avoid: Leaving conflict resolution vague

Q9. Swiggy’s teams work remotely with quarterly meetups. How do you stay productive and communicative in remote settings?

Candidate Answer:
"I follow a strict daily schedule. I use Notion and Slack to stay in sync. I over-communicate deliverables and ensure async updates are documented."

Feedback:
You get remote life. A+, but could mention burnout management.

Skill Assessed: Remote collaboration
Mistakes to Avoid: Not showing discipline

Q10. What motivates you to work in backend engineering?

Candidate Answer:
"I love the logic-heavy and scalable aspects of backend. It’s like solving puzzles that directly impact performance."

Feedback:
Love the passion! Could add an example where a backend improvement mattered.

Skill Assessed: Passion & alignment
Mistakes to Avoid: No real stories

📌 SITUATIONAL ROUND (Real-World Challenges at Swiggy)

Q11. What would you do if an order delivery system suddenly starts lagging during peak hours?

Candidate Answer:
"Check service logs for bottlenecks. Look at Kafka queues, Elasticache hit ratio, and DB latency. Rollback if a recent deployment is suspect."

Feedback:
Excellent diagnosis thinking! Could improve by talking about circuit breakers or autoscaling.

Skill Assessed: Debugging in real-time systems
Mistakes to Avoid: Not prioritizing alerts/logs

Q12. You're working with Go and notice goroutines piling up. What’s your approach?

Candidate Answer:
"Check if goroutines are being blocked or leaked. Use pprof to inspect, and ensure channels and contexts are being handled properly."

Feedback:
Very strong. Nice use of pprof.

Skill Assessed: Go debugging
Mistakes to Avoid: Ignoring memory analysis

Q13. Imagine your team wants to use DynamoDB, but your data has high write volume and uneven key distribution. How would you handle it?

Candidate Answer:
"I’d use write sharding, maybe append a suffix to keys, or apply a composite key model to avoid hot partitions."

Feedback:
Smart handling. You clearly read DynamoDB docs!

Skill Assessed: Scalability
Mistakes to Avoid: Using defaults blindly

📌 HR ROUND (Culture Fit, Work Expectations)

Q14. Are you comfortable working remotely full-time with quarterly travel to Bangalore?

Candidate Answer:
"Yes, I actually prefer remote-first work. I’d be happy to meet the team quarterly to sync and build connections."

Feedback:
Perfect cultural fit. Keep that attitude.

Skill Assessed: Flexibility
Mistakes to Avoid: None

Q15. What are your expectations in terms of mentorship and growth in your first year?

Candidate Answer:
"I expect to learn by doing — with code reviews, pair programming, and exposure to production systems. I'd also appreciate guidance on setting good engineering habits."

Feedback:
Clear growth mindset. Good ask for mentorship.

Skill Assessed: Coachability
Mistakes to Avoid: Being overly passive

📋 INTERVIEWER SUMMARY

Technical Performance: 8.5 / 10
Communication Skills: 8 / 10
Confidence Level: Medium-High

What the Candidate Missed:

  • Could go deeper into real-world implementations

  • Missed some edge cases and trade-offs

  • A bit shy on personal projects or GitHub contributions

Post a Comment