Code all day, apply all evening, mock interview on weekends. The search has eaten the rest of my life and there is no salary for the search. Trying to give myself two guilt-free evenings a week. Recommend it.
Blocking two no-apply evenings a week saved my sanity. The search is a marathon, not a sprint.
RazorpayRejected in 2023, rejected in 2024, offer in 2025. Same company, better me each time. A no is a "not yet" more often than the sting lets you believe.
Third time at the same place is such a specific kind of vindication. Congrats.
Swiggy · rejectedBuild a whole feature, tests, a writeup, "about two hours" (it was nine). Then a form rejection with zero comment on the actual submission. If you are going to make me build it, at least tell me what was wrong with it.
Unpaid nine-hour take-homes with no feedback should be illegal. Value your weekend.
You said no. Loudly. In writing. Now you are in my inbox being enthusiastic about the exact position. The role did not change. The desperation did. I have questions.
A conflict, a failure, a win. Three stories, pre-loaded, adaptable to almost any "tell me about a time". You will never be caught blank, and prepared beats spontaneous every single time in a behavioral round.
Three reusable stories is the cheat code for behavioral rounds. Simple and it works.
Goldman Sachs · rejectedHackerRank OA to start, then rounds heavy on OOP, data structures, and some domain/aptitude. Less "design a scalable system", more "do you actually know your fundamentals cold". Fumbled a concurrency question. Different flavor from the product-company loops, prepare accordingly.
You've reached the Mariana Trench. That's everything for now.