Coding Interview ⛥

How to tailor your resume to a Job Description (JD) ?? Step 1 — Read the JD carefully Highlight keywords like: Skills mentioned (React, Node, AWS, etc.) Years of experience required Responsibilities listed Step 2 — Match your experience to it For every point in your resume, ask: "Does this relate to what they asked?" Example: JD says: "Build scalable REST APIs" Your resume should say: "Built REST APIs using Node.js handling 10k+ requests/day" Step 3 — Rewrite your bullet points using this formula Action verb + What you did + Result/Impact ❌ Bad: "Worked on backend" ✅ Good: "Developed microservices in Spring Boot, reducing response time by 40%" Step 4 — Put JD keywords naturally in your resume Most companies use ATS (auto-screening software). If your resume doesn't have their exact keywords, it gets rejected before a human even reads it. Step 5 — Sections to focus on Skills — mirror their tech stack exactly Projects — pick projects closest to their domain Experience — rewrite bullets to match their responsibilities Quick checklist before sending: [ ] JD keywords present in resume [ ] Numbers/metrics in every bullet point [ ] Irrelevant experience removed [ ] One page (for freshers) [ ] Same tech stack names as JD (e.g. don't write "JS" if they wrote "JavaScript")

𝟯𝟬 𝗦𝗰𝗲𝗻𝗮𝗿𝗶𝗼-𝗕𝗮𝘀𝗲𝗱 𝗝𝗮𝘃𝗮 𝗕𝗮𝗰𝗸𝗲𝗻𝗱 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗤𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝗝𝗮𝘃𝗮 & 𝗖𝗼𝗻𝗰𝘂𝗿𝗿𝗲𝗻𝗰𝘆: 1. Your HashMap is being accessed by multiple threads. What problems can occur, and how would you fix them? 2. Your application has a race condition causing duplicate payments. How would you identify and solve it? 3. Your application creates thousands of threads and CPU usage spikes. What would you do? 4. A REST API is taking 30 seconds because it calls three downstream services. How would you optimize it? 5. Multiple threads are updating the same record. How would you ensure consistency? 𝗦𝗽𝗿𝗶𝗻𝗴 𝗕𝗼𝗼𝘁: 6. Your Spring Boot application startup time increased from 15 seconds to 2 minutes. How would you investigate? 7. A circular dependency error appears after deployment. How would you resolve it? 8. One API works locally but fails in production with LazyInitializationException . What could be the reason? 9. A transaction partially updates data even though you expected a rollback. Why might this happen? 10. Your application suddenly starts throwing OutOfMemoryError . How would you debug it? 𝗠𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀: 11. Service A calls Service B, which calls Service C. Service C is down. How would you prevent the failure from cascading? 12. A customer reports that the same payment was processed twice. How would you prevent duplicate processing? 13. One microservice becomes slow and starts affecting the entire system. What patterns would you implement? 14. How would you trace a request across 15 microservices? 15. One microservice must communicate with another. Would you choose REST, Kafka, or gRPC? Why? 𝗞𝗮𝗳𝗸𝗮: 16. A Kafka consumer processes the same message twice. How would you handle it? 17. One Kafka partition has much higher traffic than others. How would you fix it? 18. Consumer lag keeps increasing. How would you investigate? 19. A message fails repeatedly during processing. What should happen next? 20. How would you guarantee message ordering for a customer? 𝗗𝗮𝘁𝗮𝗯𝗮𝘀𝗲: 21. A query that used to take 50 ms now takes 10 seconds. How would you troubleshoot it? 22. Your database CPU reaches 100% during peak hours. What steps would you take? 23. Two transactions update the same row simultaneously. How would you handle concurrency? 24. A table has grown to hundreds of millions of records. How would you improve performance? 25. Would you choose optimistic locking or pessimistic locking for an inventory system? Why? 𝗦𝘆𝘀𝘁𝗲𝗺 𝗗𝗲𝘀𝗶𝗴𝗻 & 𝗔𝗪𝗦: 26. Your API receives 100,000 requests per minute. How would you scale it? 27. Users are abusing your API. How would you implement rate limiting? 28. Your Redis cache crashes unexpectedly. How should your application behave? 29. An EC2 instance needs to access S3 securely. How would you configure it without storing credentials? 30. A deployment causes increased latency. How would you identify the root cause and roll back safely?

Coding Interview ⛥ pinned «How to tailor your resume to a Job Description (JD) ?? Step 1 — Read the JD carefully Highlight keywords like: Skills mentioned (React, Node, AWS, etc.) Years of experience required Responsibilities listed Step 2 — Match your experience to it For every…»