The same recycled algorithm questions, some puzzles peppered in and a disproportionate amount of emphasis on your performance in the interview.
Many argue that tech hiring is broken
But that’s not really what you're worried about right now, is it? With about 2 months before campus placements, a standardized, stale hiring process is the EASIEST TO GAME. Your questionable CGPA, your lack of internships, meagre projects — all have very little bearing on your selection. Let's get down it.Competitive coding.
This is going to play a very large factor in most product company interviews. Amazon, Microsoft, Directi, Flipkart et al are guilty of asking the same questions over and over again. Two months is just enough time to cover the important topics.
InterviewBit is your bible here. It’s split into categories and guides you on what topics to do when. The average time per question feature is a good indicator of how good you currently are. You will find more specific guidance on the InterviewBit platform directly. It’s the only coding platform I used for my entire preparation.
Assuming you are a rank novice to competitive coding, expect at least 45 of your 60 days to be fully devoted to this. Get most of these days in early as it’s harder to spend quality time on coding when you are nervous.Theory
Data structures, Algorithms, Operating Systems, Databases, Networking. Very little math related theory. Find college lecture slides and revise from there; that will be enough. You can skim through these topics at your own pace. Do not spend more than a few hours on each topic. Take about 3–4 full days in total for this.
Step 1: Skim lecture slides.Projects
Step 2: Google ‘indiabix *topic* questions’ and quickly solve some MCQs.
Step 3: Don't worry about memory-based questions. Focus on concepts.
When recruiters ask you this, they are trying to see if you really enjoy programming. Make sure your face lights up when you talk about that app you built and what you were trying to solve using it. Expect to field some questions on why you chose a particular technology stack and why you designed it in a particular way.
If you have a CS degree you would have done college assignments (PPL, Compilers, Computer Graphics) you can pass them off as projects. PS-1 projects can be added here too.
If you don't have a CS degree and have minimal projects, emphasize that you are self-driven and can learn new things on your own. That you have cleared the preliminary rounds without a teacher. A friend of mine said exactly this at a PayPal personal interview (and it worked!).
That’s a whole article in itself. For now, just keep it as something to do in the last few days. You will probably be too jumpy to spend hours on coding questions that late anyway.Last few days
Practice mock interviews with friends or in front of a mirror. Rehearse out loud your introduction, two pet projects and common questions. And always do a quick (~10 minute) review of a company before you sit for its personal interviews!Word of advice
Drop absolutely everything and work your hardest for placements. There is a lot of variance in the quality of companies. A job offer in the domain of your choice is well worth the effort put into it. You should be able to put in at least 6 hours each day.
I made the mistake of not taking placements seriously enough. When you miss being a part of a data engineering team because of a standard DP question, you're going to get pretty mad at yourself. Try not to let that happen.
Most people say they got lucky on their interview day. No matter how good you are, cracking 4–5 interviews straight is pretty damn hard. Just hang in there and don't let your confidence drop just because you messed up a few interviews.Some FAQs
There are other tools/platforms you can use to learn. I've deliberately mentioned just one for each purpose. Most people spend too much time worrying what the “best” way is. Just dive in and get started.
I am surprised by how good and popular this guide is even so many years later. Goes a long way to prove that people still struggle with the basics.Reply
Thanks Saurabh! This is awesome. I hope this work for me too.Reply
“I don’t spend my time pontificating about high-concept things; I spend my time solving engineering and manufacturing problems.”― Elon MuskIf you are in your final year or pre-final year of engineering awaiting the placement season, then you should p
1. Thinking you got this coveredCommon mistakes: Being overly confident, not preparing enough, not talking to enough people.Yes, you felt entitled when you made 95 percentile in high school; you felt entitled again when you cracked JEE to get into on
I recently answered a question on Quora by an Amazon employee. I find my current job of software developer at Amazon boring and uninteresting, should I switch to companies like Microsoft and Google or to a startup?You can reach the answer on Quora wi