<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sahil Khosla on Medium]]></title>
        <description><![CDATA[Stories by Sahil Khosla on Medium]]></description>
        <link>https://medium.com/@sahilkhoslaa?source=rss-1ee6cedf9145------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WBUCmg1MnCj34ZhyScGa_Q.jpeg</url>
            <title>Stories by Sahil Khosla on Medium</title>
            <link>https://medium.com/@sahilkhoslaa?source=rss-1ee6cedf9145------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 23:53:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sahilkhoslaa/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Evolution of my Software Engineering Resumé]]></title>
            <link>https://medium.com/@sahilkhoslaa/the-evolution-of-my-software-engineering-resum%C3%A9-31be56716d4a?source=rss-1ee6cedf9145------2</link>
            <guid isPermaLink="false">https://medium.com/p/31be56716d4a</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[algorithms]]></category>
            <category><![CDATA[data-structures]]></category>
            <category><![CDATA[resume-writing]]></category>
            <dc:creator><![CDATA[Sahil Khosla]]></dc:creator>
            <pubDate>Sat, 09 Jul 2022 13:55:51 GMT</pubDate>
            <atom:updated>2022-07-09T13:55:51.734Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey everyone, thanks for the amazing feedbacks on my previous articles. I am excited to see that my article <a href="https://medium.com/@sahilkhoslaa/targeting-dsa-the-right-way-77c5ff30e47d">Targeting DSA the right way</a> has been added by 250+ people in their list.</p><p>Here in this article I will be focussing on the insights while making a Software Engineer Resume and how my resume got evolved until now. I am sure you will be able to take some key points and will try to adapt the same.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*SY3FAKsNb0gLaM7ggLU-fw.gif" /></figure><h3>The Evolution</h3><h3>Revision 1</h3><p>Fortunately my resume could not be fit on a post it not. I decided to make my first resume back in mid 2017. To some of you this resume might look good, concise and neat but actually it has a lot of mistakes. In that time resume screening was not that rigorous for internships and companies took online screening tests to filter out the candidates. So I made it to a lot of company interviews without getting filtered on resume basis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LwfRAts4o5QaxNi6UsbTJw.png" /></figure><h4>But WHAT is wrong with this resume?</h4><p>Well a lot of things!!! Keeping in mind you are applying for internships</p><ol><li><strong>Introduction/About </strong>— No one is interested in your home address (you can just keep it till the city, country you are working in). They are eventually going to gather your personal information that includes your home address. So keep in mind to put in only relevant information and save some space to fit in all your hard work into 1 page.</li><li><strong>Academic Qualifications/Education </strong>— As for your internship or placements you should mention your college CGPA. There was no need to create table to specify separate columns for Degree or year or institution. The can be concatenated into one liner.</li><li><strong>Technical Skills</strong> — As for technical skill, label can be shortened to just skills and it is really important to showcase which languages are you proficient in. You can specify separately on which amazing libraries you worked upon.</li><li><strong>Projects</strong> — This one is important if you see closely there is no need to elaborate a project in statements instead use concise points and highlight the metrics. I will be talking about this in depth later below.</li><li><strong>Achievements/Position of Responsibility/Extra Curricular Activities </strong>— Action verbs are not used. Again there is definitely no need to write full fledged statements to describe what you held responsible for, what you actually do in extra curricular activities etc. instead you crisp short words for which <strong>the recruiter don’t have to take out their dictionary.</strong></li></ol><p>PS — Don’t judge me on my coding handles :p I improved a lot later on and changed my handles too 😏</p><p>Some things to observe in this resume although it has these mentioned mistakes but</p><p>👉 It is still using the whole page. No white spaces are left to be utilised.</p><p>👉 Bulleted points help in much easy reading.</p><p>👉 Some words are highlighted so as to make recruiter focus on the things you want them to focus upon.</p><p>I would personally rate this resume as 4/10 😔</p><p>I got a chance to interview with companies like Amazon, American Express, Microsoft , Goldman Sachs etc and a lot of startups.</p><h3>Revision 2</h3><p>Next up I tried up a lot of online resources on how to make a resume for a software engineer profile and there are really good resources present out there. I explored a lot of resume from linkedin asked professionals to share their resumes as well to compare what can i improve in my resume. I learned that for a fresher it is really important to make a resume so as it can attract the recruiter quickly so I should be creative as well. <strong>There are some repeated mistakes.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cYED0eNo6DgYSObZ9VfEIA.png" /></figure><p>There is nothing wrong in being creative. This resume is much better than the previous revision. It is much more concise. Labels are shortened. I have defined roles in every projects. Used action verbs. Education section is shortened as class 10th, 12th degrees have been removed.</p><h4>Somethings still wrong 🤔, Now what?</h4><p>❎ Projects have roles much more largely highlighted than the organisation itself. Recruiters first wants to see which organisation you are working or worked for and then what was your role in it. Keeping a readable font family and size is really important.</p><p>❎ Words are not highlighted enough to showcase what was the star of the project I worked upon.</p><p>I would rate this resume as 5/10.</p><p>I got a chance to interview with Amazon, Shell, Salesforce etc.</p><h3>Revision 3</h3><p>This is the resume is used to crack <a href="https://medium.com/u/be36e94a7e47">Google</a> 😙. This is my favourite resume up until now.</p><blockquote>I got a whole lot of opportunities and what I got most was the appreciations from the Technical Recruiters as well as from the people whom I requested to put in a referral.</blockquote><p>I used a lot of resources and handpicked some best resources which I will be sharing a bit later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XRC4v2qiwvYxPtwD50howA.png" /></figure><h4>What’s better?</h4><p>Well a lot of things segregated column for professional aspects like experience, education and projects. All secondary things are on the right hand side. Human readability is from left to right so recruiters get to see the important stuff like experience, educational qualifications and projects first and then the personal information. Points are bulleted and much more concise. <a href="https://www.airbnb.co.in/trips/v1/9b7a2d3d-075b-4873-9727-62d7b2b98d76/ro/RESERVATION_USER_CHECKIN/HM255ZFQFY"><strong>Note </strong></a><strong>— that how I have incorporated numbers into projects, people love to see metrics, improvement percentages, cost reduction, optimisation percentages etc.</strong> Bolded words are highlighting the main features, achievements in the projects as I want recruiters to give a glance on that first and stuff which was responsible in achieving that. Added logos in front of organisation which helps in relating to your organisation pictorially much faster.</p><h4>Is there still a scope for improvement?</h4><p>Definitely yes, there will be always a scope for improvement when it comes to resume. As we grow in our career I feel we as a software engineers should adapt the classic resumes and start being somewhat less creative. Although creativeness helps when you are a fresher or have 1–2 years of experience because you need to stand out by beating the ATS. But eventually we need to add more content as we grow so our resume might not get fit into a page. Adapting classic resumes is the best choice we can adapt.</p><p>I would rate this resume as 7/10 🐐. I got a chance to interview with Amazon Luxembourg, Amazon India, Microsoft SDE 2, Uber SDE 2, Goldman Sachs, Google, Amazon Berlin and many more startups etc. (I know its a lot of Amazon, it felt like I have taken their subscription on a quarterly basis :p)</p><p>I can recommend you to follow this template but I feel it is you who should first understand the bits of resume reading. You need to understand how a recruiter would interpret things so try getting into their shoes and just give your resume a read for 10–15 secs because this the time recruiters have to shortlist your resume. Let me know if you still need the template I will email you or provide the link here itself if the requests are large.</p><blockquote>I will keep on updating my resume revisions here as part of the evolution process</blockquote><p>I have created many more revisions than this but these are the revisions in which significant changes took place.</p><h3>ATS — Application Tracking System</h3><p>What is ATS? Why am I hearing this ATS a lot? Should I be worried about it? Why do I have to beat it?</p><p>To answer this ATS is an application tracking system now basically deployed by every company to filter out the resume based on the Job Description. It is developed by using Machine Learning Algorithms which makes sure that no resume gets passed through if your resume is not matching 70–80% roughly to the job description. So yes you should be worrying about ATS and you need to beat it to get your resume filtered so that recruiter can have a look. This process is important as there are huge number of applicants who are applying to same job as you. So they need to narrow down the candidates and then filter out the best 100–200 candidates for a job role manually.</p><p>The thing is now you are completely depending upon how this ATS is going to parse your resume. Could be that if your formatting is not proper it will mess up the sections and mix up the words into one another. In other words it can be a disaster if you have not properly created your resume.</p><p><strong>What should I do? </strong>Check out <a href="https://resumeworded.com/">resumeworded.com</a>. Create an account and upload your resume and job description you applied to. It is an amazing tool which mimics the behaviour of actual ATS of companies and will let you know if your resume can make an impact. It will give you a percentage of that impact. Pretty cool right!! 😍</p><p>This will also show you how ATS is parsing your resume and how your resume looks like to a machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*QAn8mbhNvUwvCFL6iEhQaw.gif" /></figure><h3>Point of View of a Technical Recruiter</h3><p>Congratulations if your resume did beat up the ATS because now it’s time to understand the POV of a Technical Recruiter. You need to understand that recruiters have a lot of work to do. They do not have much time to read a resume in depth detail for huge number of candidates. So they spend only 15–20 secs on a resume and move on. So you need to keep in mind that you need to show only the stuff which has embarked something really good. Doesn’t have to be inventing hydrogen fuel but optimisation, efficiency, invention, etc would work.</p><p>The best resource I found up until now is:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FBYUy1yvjHxE%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DBYUy1yvjHxE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FBYUy1yvjHxE%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4fd5b2fdb7ecdac82bb45cbd55d6c62f/href">https://medium.com/media/4fd5b2fdb7ecdac82bb45cbd55d6c62f/href</a></iframe><h4>The framework</h4><blockquote><strong><em>Accomplished [X] as measured by [Y] by doing [Z]. (source: Google)</em></strong></blockquote><p>I will not be going into very much in depth detail as this video covers it all. I followed it till the very end which helped me in landing many job interviews with my favourite tech companies.</p><p>Don’t forget to brag about your achievements. Show your hard work, keep all your network, coding etc profiles updated.</p><p>With this I hope you got a gist or some points maybe you were doing wrong whole this time. Also remember to not be lazy and actually create custom resume for different job applications. Create 100s of resumes with same template if you have to but make sure you are adapting the job description in your resume completely. Don’t send same resume every where and then wonder why is it not getting selected. ATS is designed to filter out resume based on job description, NOT on what you did differently.</p><h3>Lastly…</h3><p>I hope you enjoyed the article. Let me know what your resume looks like share a link I would love to see them. Comment out if learned anything different from this article. I have been getting huge great response on my instagram page <a href="https://www.instagram.com/techmunks/reels/">techmunks</a>. Do check it out. Follow me on medium for such interesting articles. Stay tuned!!</p><p><strong>Do you know if you tap and hold the clap button it does something different check it out. I also found out quite recently. 😛</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31be56716d4a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making the most out of rejections]]></title>
            <link>https://medium.com/@sahilkhoslaa/making-the-most-out-of-rejections-590bea34b847?source=rss-1ee6cedf9145------2</link>
            <guid isPermaLink="false">https://medium.com/p/590bea34b847</guid>
            <category><![CDATA[faang]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[amazon]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[interview-preparation]]></category>
            <dc:creator><![CDATA[Sahil Khosla]]></dc:creator>
            <pubDate>Thu, 09 Jun 2022 10:34:17 GMT</pubDate>
            <atom:updated>2022-06-09T13:42:15.604Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi everyone, are you struggling with never ending streaks of rejections from your favourite big tech companies? Do you wonder what went wrong even if you rocked the interview? Do you get demotivated after hearing this magical phrase “I am sorry to inform you that we won’t be proceeding further with your application”? Then my friend this article is for you. I will be sharing some deep insights and tips which you can use to make a perfect rebound for your next interview.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*55Cy4wZgLmv_YF6QsfGEjA.gif" /></figure><p>I have been rejected by a lot of companies. I am just pouring my heart out here and tell you about the stuff what I did and how it made me better after every rejections. I still remember running out of a movie theatre (watching dunkirk) before interval to my home after I heard my first rejection from Amazon from SDE Intern role. My journey has been quite amazing, would love to talk about it some other time. Hehe!!</p><h3>Grieve it out</h3><p>First and foremost thing after hearing about a rejection is to grieve it out. Take some time for yourself to feel bad. Find out a close friend/family member/relative (not really) or if you love your own company, just spend some time and tell them/yourself about what expectations you had from this job interview. Think about how your life would have been if you have gotten the role you interviewed. Build up all the scenarios you can the high ones and the low ones and live them for a while. I know you will be more upset but experience these moments. Depressed till now? Not really? Thank god!!</p><p>It is really important to realise that what your mind really wants and what did you put in to achieve that. Don’t take months you are not getting over breakups but some hours or a day is fine.</p><h3>Time to Celebrate</h3><p>I have a twin brother so I made a rule that every time I am rejected I took my brother out for a celebration for a dinner. We usually have nice conversations and he motivates me every time. So Next step is to just celebrate. Order yourself something a treat or take someone out with you and tell them you failed successfully. Tell them what you learned from this rejection and celebrate the fact that you are still so much better than the others in the queue. People are not even getting interview calls at least you did and you made it to this far. Trust me getting rejected is an achievement as you have now a lot to think about for yourself and you are going to work on that. You are going to learn a lot of things so buckle up!</p><h3>Send a Good note to Recruiter</h3><p>Don’t end things with recruiter on a blank or a bad note. Send them an email elaborating about what you enjoyed most during the process and be thankful to them for giving you a chance in the first place. Tell them this is your dream organisation if it is and one day you will be there! Tell them you need a brief feedback so that you can improve on specific things, sometimes you will get a reply back. Hope for the best! Recruiters generally keep an eye on the candidates and they keep on forwarding the rejection applications into the next application pool so as someone from the pool can start with your application again after the cool down period.</p><h3>Rejections are Redirections</h3><p>Just like you believe there is gravity, just blindly believe that rejections are actually redirections. If you are getting rejected constantly that means something big is meant for you. I used to think that people are just telling me for the sake of being motivated but it is actually true. That does not mean you will not try for the organisation again but all you need to do is to bring in a mindset that you are going to fail and you have to fail in a different way. So that nothing gets messed up when you are actually trying for your big “gig”.</p><blockquote>I have not failed 10,000 times — I’ve successfully found 10,000 ways that will not work — Thomas Edison</blockquote><h3>Habit of Analysis</h3><p>I am not a know it all person. I just knew one thing that I need to experience every redirection and analyse what new thing I learned in this one.</p><p>For a specific company and a specific role the pool of questions are generally the same like medium level difficulty for linked lists, array and strings and medium-hard level difficulty for DP, graphs etc. They usually ask easy questions to warm you up and people thinking that its of medium difficulty take a lot of time than expected — a negative perception for the interviewer.</p><p>During my initial redirections I started preparing an excel sheet in which I listed down the company I interviewed for and what questions were asked in each round. This gave me a sense that what company are asking what types of questions and what they want to assess.</p><p>I analysed each and every question, its difficulty level etc. and revised every question one day before the interview and I was lucky one time that one question got asked again by a different company. It happens! Of course the wording was different.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yRbw3luZH8-JEL58zZdZZA.png" /></figure><p>Just to give you a sneak peek this is how my sheet looked for some of the redirections (blurred due signed NDA). This developed a habit for me to analyse everything very closely based on some parameter defined by me. Initially it felt useless to be honest as I was not getting much interviews to analyse upon maybe due to less experience but eventually I started to notice a difference in my problem solving instinct as certain sense of proactiveness got developed, a sudden urge to first analyse the problem statement like setting up a time for myself to solve the problem with given difficulty, started to write down given things and thought what all approaches I know and selecting the best one to be applied in the first go. I then realised that I should be able to solve any of the above problem or similar problem at any point in time. This process is gradual. You need to have patience but it will happen! These instincts will hit automatically and you will smile inside.</p><h3>After every Interview Round</h3><p>The above process was helping me a lot so I decided to upgrade this process a bit by defining the four parameters that <a href="https://medium.com/u/be36e94a7e47">Google</a> uses in its secret formula explained earlier in <a href="https://medium.com/@sahilkhoslaa/the-secret-formula-to-crack-googles-interview-process-b5fb1da35f8">The secret Formula to crack Google’s Interview process</a>.</p><p>So just after the interview ended I opened up my notebook and gave me my own feedback according to 4 parameters and a summary. All the parameters were rated out of 5</p><p>Described the Questions asked</p><ol><li>Problem Solving — Explained the approach used and realised the difficulty level. Researched for the best possible approach from internet and learned it thoroughly. I also wrote down the intuition that what and why it came to my mind. <strong>The best part was i didn’t beat myself up If was not able to come with the optimal approach</strong>. Instead I smiled and learned the approach and started recognising the patterns whenever these types of questions are asked.</li><li>Communication — In this I wrote down how was my communication and how was the communication of the interviewer. Was I able to form a bond with the interviewer which helped me with the flow and If not what was the main issue was it me or was it the interviewer. It can happen both ways. Again no need to worry if the interviewer’s communication is not upto the mark. You can just let your recruiter know when and if they ask regarding the feedback from you in the best case else just leave it to god! Again don’t beat yourself up it is definitely not your fault.</li><li>DSA — this was simple I just recognised if I knew and applied the appropriate DSA after I decided my approach. Big Tip — <strong><em>Always choose the data structure according to the algorithm and not the algorithm according to the data structure.</em></strong></li><li>Speed — When interviewer switched to the next question I used to note the time and that’s how I knew how much time approximately I took to solve the questions. I was targeting big tech companies so I knew speed matters to them a lot. I timed myself according to the difficulty of the questions. This again brought a sense of proactiveness that I need to solve these sorts of questions in the given time frame.</li></ol><p>Summary — In the end I jotted down the overall experience I had personally with the interview and wrote down what steps I can take to improve more. I was satisfied with myself if I rated at least 4 in all the parameters. This helped me a lot in the analysis. You can also prepare graphs and pie charts if you are into visuals to track your performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Rk7Ti46ij_AEbsI1mn8pqw.png" /></figure><h3>Self Analysis of the Interview Process</h3><p>Well this is the hardest part. Assuming you did not receive any feedback you have to think of the possible reasons, you got redirected from the process. Our minds works in a strange way that it starts accepting what all you did in the interview was beyond great and the results are not fair. But deeply if we start to think from the interviewer mindset we will realise what and where did we mess up.</p><p>Try to answer these questions for every round and analyse if you lacked somewhere.</p><ol><li><strong>Was my understanding to all the problems correct?</strong> — If not, problem could be in your algorithmic knowledge as you were not able to deduce any possible test case and ask the interviewer “is this the answer he is expecting?” by using the information given in the problem. You could ask the interviewer to give you an example to clarify things. No rush. There are no negative points. Interviewers job is to make sure you understand the problem.</li><li><strong>Did I directly jump onto the solution? Did I ask clarifying questions before giving the solution? </strong>— If yes, the problem could be you having short patience. You tend to attack the problem you think is very easy for you directly. The interviewer is expecting to have a good amount of discussion about understanding the problem and wants to collect data points about you that yes you collect information first then start solving the problem.</li><li><strong>Did I miss any information?</strong> — If yes, this is a big no from the interviewers perspective because you are missing the information that is already given in the question. The interviewer don’t like you saying “Ohh! we can take negative numbers as well? I thought we were solving the problem only for positive numbers I am sorry” while it is given in the questions that it is an array if integers. So this is big turn off for the interviewer as they are expecting from you to induce new information from the given information which helps you out in making the algorithm instead you are not even using the given information.</li><li><strong>Was I able to think out of an approach? Did I mention its Time and space complexity?</strong> — If no, the problem is in your problem solving ability. You need to practise more questions than you think because you should at least be able to solve the question with brute force approach. or you might have problem in identifying the time and space complexity.</li><li><strong>Did I make the solution optimal? Took the interviewer’s consent to code the problem? </strong>— If no, again the problem is in your problem solving ability. You have not seen enough questions/algorithms yet which could be used to optimise the algorithm further. At the end of the day interviewers are looking for the programmers who can solve the problem efficiently because everyone can code but can they optimise using the standard coding practises is what they need.</li><li><strong>Did I dry run my code using edge cases? </strong>— If no, you have thought about the problem using the extremities like what happens if there are all zeroes in the array, if there are duplicates in the array like that. You should think of all possible scenarios while building up your solution.</li><li><strong>Was my code clean, readable and maintainable? Was my code scalable? Chose appropriate names?</strong> — If not, you need to practise more code writing. Check famous open source projects and see how they programmed small modules of the project you will the clarity in the code, the comments, the indentation, the naming conventions, it’s quite amazing to see the professionalism and clarity in the code. You will definitely get a lot to learn.</li><li><strong>Did I use OOPs concepts where ever required?</strong> — If not, you need to learn what all data members and functions you need to keep in private and what all you need to keep in public. You can use static variables in some places if you are using any global variable. <em>Small things like that affect in a large amount. These things often compensate even if your interview is not going in the right direction</em>. Do apply OOPs concept as it is a standard programming practise.</li><li><strong>Was I able to convey my thought process clearly? Did interviewer understood the approach?</strong> — If not, you should start narrating your thoughts even while practising. Convey your thoughts in a structured manner. Don’t worry if stammer a bit in between they do not care at all. All they want to know is about your thought process and how much you are clear with the algorithmic knowledge.</li><li><strong>Was I able to determine the difficulty of the problem? Was I able to solve it on time? </strong>— If not, the problem is in your problem solving and intuition building. From experience speed comes with the confidence. If you are clear with the approach and you have a good hold. Automatically you will start solving the questions in a quickly and timely manner. You will be able to respond to interviewers doubts confidently.</li><li><strong>Did I say anything inappropriate or unnecessary during the interview? Did you oversell or short sell yourself? </strong>— If yes, there is no point in discussing further. Never ever oversell or short sell yourself. Don’t start telling your life stories to the interviewer. They are not at all interested in that. I have seen people giving desperate reasons to the interviewer, that “I am a really hardworking person, I have done this and that and I can be of huge contribution to this organisation” Please don’t do that. Even if a round got messed up analyse it and try to improvise in the next round if that was not your last round. hehe!</li><li><strong>Did I structure my stories in STAR format? </strong>— If no, then probably you got rejected for not preparing your behavioural round questions in a STAR format or even if you did, they might have somehow identified that you are struggling to come up with a story so you are faking it. Try to prepare 2 stories for every leadership principle or situations in a proper structured STAR format (Situation Task Action Result). Be very confident and expect follow up for your stories. Give them leadership data points they are looking for and keep it concise.</li></ol><p>If your situation does not fall in any of these IFs then my friend god has planned something bigger for you. Just give a pat on your back that you fought relentlessly and be thankful to experience this. Just leave it to fate.</p><p>You can come up with your own approaches to analyse after an interview. These approaches helped me a lot and gave me a sense what I am doing wrong and how can I become a better problem solver with every interview round.</p><p>That’s it this analysis is more than sufficient to let you know on the points to work on yourself and improvise accordingly.</p><h3><strong>Ted Talk</strong></h3><p>I know it’s a dream for a lot of you to crack MAANG companies. They are mine too. But eventually in this process I realised that life is not all about getting into the MAANG companies. I tried in a lot of companies and maybe I still have to try more (of course not really if you got into MAANG like companies). But what i realised is life is all about having unique experiences.</p><p>Maybe you are not satisfied with your current job, pay or something is bothering you or you are just a college grad who has just set the goals to crack only MAANG, my only advise is to check out all the opportunities you are getting in your life and make a decision based on certain parameters of your own satisfaction. No it is not easy for me to say because I got into one but I have had my fair share of redirections and I am expecting a lot more. But one thing I did was to thoroughly enjoy this journey because I knew someday I am going to crack these companies.</p><p>Don’t let anyone especially your relatives tell you, you cannot crack these companies only gifted or talented people get into these companies. If you saw this dream that means you are going to live it too. Just have the courage to fail.</p><blockquote>You are far more better than the people who cracked these companies very quickly or in the first go. Because you have worked upon the things you never would have thought of.</blockquote><p>Just focus on becoming 0.00000001% better person than the person you were yesterday and you will do wonders. Believe yourself.</p><h3><strong>Lastly</strong></h3><p>I hope you enjoyed the article and you learned something from this. Let me know what you think about this article in the comments. Do share with someone who you think can benefit out of this. I am going to share a lot of fun content on my instagram page <a href="https://www.instagram.com/techmunks/">techmunks</a>. Do follow me on medium and instagram. Still have some doubts let’s connect. I wish you all the very best for your next interview. Let me know what you want me to cover next.</p><p>Instagram —<a href="https://www.instagram.com/techmunks/"> techmunks</a></p><p>Linkedin — <a href="https://www.linkedin.com/in/sahilkhoslaa/">Sahil Khosla</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=590bea34b847" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Targeting DSA the right way]]></title>
            <link>https://medium.com/@sahilkhoslaa/targeting-dsa-the-right-way-77c5ff30e47d?source=rss-1ee6cedf9145------2</link>
            <guid isPermaLink="false">https://medium.com/p/77c5ff30e47d</guid>
            <category><![CDATA[data-structures]]></category>
            <category><![CDATA[data-structure-algorithm]]></category>
            <category><![CDATA[interview-tips]]></category>
            <category><![CDATA[algorithms]]></category>
            <category><![CDATA[interview-preparation]]></category>
            <dc:creator><![CDATA[Sahil Khosla]]></dc:creator>
            <pubDate>Wed, 01 Jun 2022 19:19:14 GMT</pubDate>
            <atom:updated>2022-06-02T06:22:31.393Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi Everyone, after amazing feedbacks on my previous article ‘<a href="https://medium.com/@sahilkhoslaa/the-secret-formula-to-crack-googles-interview-process-b5fb1da35f8">The Secret Formula to crack Google’s Interview Process</a>’, here I am back again sharing my preparation strategy in detail.</p><p>You will be getting the insights of grokking the Data Structures and Algorithms which I feel is a great way and can be applied by anyone who is preparing for big tech companies. Grab your popcorn and enjoy!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*I6GQrwQRJCbTMW2cG2mzQQ.gif" /></figure><h3>Data Structures</h3><p>Grab a notebook not just a piece of paper and start by listing down all the data structures that has been discovered until now.</p><ol><li>Arrays [1-D, 2-D]</li><li>Linked List [Singly, Doubly, Circular]</li><li>Stacks</li><li>Queues</li><li>Trees [Binary Trees, N-ary Trees]</li><li>Priority Queues</li><li>Unions/Disjoints ADT</li><li>Graphs</li><li>Strings</li><li>Trie</li><li>Hash maps</li></ol><p>Start exploring these data structures by reading about them through a book or understanding them with the help of a mentor or from youtube. Get a basic working idea about all the data structures listed above. I know you are with me up until now.</p><h4>Commit to Memory (CTM)</h4><p>I often used this abbreviation whenever I wanted to make sure my brain has to remember something for a longer period of time. We will be using this term quite often.</p><h4>Time &amp; Space Complexity Cheat Sheet</h4><p>Prepare a table and jot down the time complexity for a best, average and worst case scenarios for every data structure. Make sure you are not cheating for the cheat sheet itself and you are preparing this on your own. For initial reference you can visit <a href="https://www.bigocheatsheet.com/">https://www.bigocheatsheet.com/</a></p><p>Needless to say CTM the cheat sheet. This is going to help you a lot whenever you are solving any question. You can prepare this sheet multiple number of times by yourself if you have a tendency to forget things quite often. Paste this nearby on your desk for quick reference.</p><h3>Identifying the Algorithms for Data Structures</h3><p>Assuming you are clear with the basic data structures. Now is the time list down all the major algorithms that comes under them. Prepare an Hierarchal tree list for all the Data Structures.</p><blockquote><strong>Note that the questions are unlimited but the algorithms are limited.</strong></blockquote><ol><li><strong>Arrays </strong><br>a. Sorting (You can sub-categorize into merge sort, quick sort etc.)<br>b. Two pointer<br>c. Sliding Window<br>d. Binary Search<br>e. Recursion<br>f. Dynamic Programming (LIS, LCS, LPS etc)<br>g. Ad Hoc<br>h. Bit Manipulation<br>i. Hashing<br>j. Insert/Update/Delete an element<br>k. Merge Intervals</li><li><strong>Linked List</strong><br>a. Sorting<br>b. Slow and Fast Pointer<br>c. Recursion<br>d. Hashing<br>e. Insert/Update/Delete an element<br>f. Josephus Problem</li><li><strong>Stacks</strong><br>a. Sorting<br>b. Recursion<br>c. Hashing<br>d. Dynamic Programming<br>e. Ad Hoc<br>f. Insert/Update/Delete an element</li><li><strong>Queues</strong><br>a. Sorting<br>b. Recursion<br>c. Hashing<br>d. Ad Hoc<br>e. Insert/Update/Delete an element</li><li><strong>Trees</strong><br>a. Recursive and Iterative traversals (You can sub-categorize into pre order, post order, level order and in order traversals)<br>b. Maximum and Minimum in a tree<br>c. Height of a tree<br>d. Swapping of nodes, sub-trees<br>e. Diameter of a tree<br>f. Binary Search Trees<br>g. Inorder predecessor in Binary Search Trees<br>h. Segment Trees/Fenwick Trees (not commonly asked but good to have knowledge about it)<br>i. Hashing<br>f. Insert/Update/Delete an element<br>g. Balanced Binary Tree/ Search Trees</li><li><strong>Priority Queues<br></strong>a. Binary heaps<br>b. Insert/Update/Delete an element<br>c. Heapify/Percolate Down<br>d. Get Minimum/Maximum in a heap<br>e. Heapsort<br>f. Median in an array<br>g. Sorting a list of large numbers/files<br>h. <strong>Updating a priority queue using hashmap</strong></li><li><strong>Unions/Disjoints ADT<br></strong>a. Quick Union<br>b. slow/quick FIND<br>c. UNION by Height (UNION by Rank)<br>d. UNION by size<br>e. Makeset<br>f. Path Compression (Not really required but good to have knowledge)</li><li><strong>Graphs </strong><br>a. Traversals (You can sub-categorize into DFS and BFS — Always use Adjacency list)<br>b. Topological Sorting (DFS and BFS)<br>c. Number of Connected Components<br>d. Find if a Path exists<br>e. Dijkstra’s Algorithm<br>f. Flood fill Algorithm</li><li><strong>Strings<br></strong>a. Sorting<br>b. Recursion<br>c. Hashing<br>d. AdHoc<br>e. Insert/Update/Delete a character<br>f. KMP Search (Not required but good to have knowledge)<br>g. Two pointer<br>h. Sliding Window<br>i. Dynamic Programming (LIS, LCS, LPS etc)</li><li><strong>Trie</strong><br>a. Insert/Update/Delete a node<br>b. Searching a node<br>c. Suffix/Prefix Trees</li><li><strong>Hash maps </strong>— Hashing is used in almost all the data structures and they don’t have generic named approaches. We can get adapted to hashing and its uses with the help of numerous ad hoc questions. Ex — Find the first non-repeating character in a string of length N.<br>Do read about difference between a hash map and a hash table and how collisions happen in them and most importantly. How do we resolve them. A bit knowledge about Linear and Quadratic probing would be great.</li></ol><p><em>Please spare me if I missed any important algorithm and do tell me in the comments I will add them into the list</em>. You can add your own named algorithms into your own list which you think are getting used more frequently. Find below the list of some advanced not asked much (or at least I consider them advanced) algorithms and read them only if you have conquered the above list and want to spoil your work life balance. Just kidding!!</p><ol><li>Prims/Kruskals Algorithm</li><li>Ternary Search Trees</li><li>Fibonacci Heaps</li><li>Advanced Game Theory</li><li>AVL Trees, Red-Black Trees</li><li>(many more…)</li></ol><h3>The Bucketing Approach</h3><p>This is my self devised approach which helped me tons for the preparation. I hope this does wonders for you as well. Take three buckets and name them <strong>easy, intermediate/medium and hard</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*mwyZ0-7oQpytaq6RnOinIA.gif" /></figure><p>Now read your detailed algorithm list from top to bottom and starting putting down the algorithms from each data structures you feel you know the best and you can crack them anytime they are asked into the easy bucket. Put down all the algorithms from each data structures into the intermediate bucket that you feel you are just okay with them and sometimes you are able to solve the problem and sometimes you have to see the discuss section of the problem to get the hint. And lastly put in all the algorithms you feel you don’t even want to touch but always wish that they will be in your easy bucket one day. Obviously you have to exhaust your whole list. Each algorithm should be present in any one bucket.</p><p>Ex — <br><strong>Easy </strong>— [Arrays → Sorting, Two pointer, Sliding Window, Adhoc, Hashing, etc],[Linked List → Sorting, Slow and Fast Pointer … ] ….</p><p><strong>Intermediate</strong> — [Arrays → Dynamic Programming, Merge Intervals and Bit Manipulation], [Linked List → Josephus Problem (of course it’s easy I am just giving an example)]…</p><p><strong>Hard </strong>— [Graphs → Dijkstra’s Algorithm] …</p><h4>The Art of Solving only Quality Questions</h4><p>Once you are ready with your buckets, You have to understand that at the end of your preparation you have to fetch the items in your intermediate bucket and pour them into easy bucket and fetch the items of your hard bucket into your intermediate bucket.</p><p>AIM — We have to make our everyday productive without losing motivation to solve the problems. CTM</p><p>Chose any coding platform you like I personally prefer Leetcode. Assuming you are at least devoting 2 hours everyday into your preparation and you have to solve easy questions in 5–7 mins and medium question in 20–25 mins and hard question in 30–35 mins. At average you can solve 10 questions in one day. How to choose these 10 questions?</p><p>Refer to your buckets and pick out any 2 algorithms from easy and 6 algorithms from intermediate and 2 algorithms from hard bucket. Yes you can choose randomly between the buckets.</p><p>After this search questions on leetcode with the help of algorithm and data structures tag and filter them with difficulty and sort them with the acceptance rate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*4lXytKnjg4l1_ShuQ_CCFA.png" /></figure><p>Difficulty of the question is inversely proportional to name of the bucket.</p><p>If you have good hang of the algorithm i.e. from easy bucket then choose questions with harder difficulty and vice-a-versa.</p><p>Pick out the questions which has an acceptance rate between 40–60% for each bucket. Solve these questions by timing yourself according to the difficulty level. Solve as if you are actually giving the interview. Narrate your approach to yourself, write down the test cases you used and also mention the time complexity. Do give a pat on your back once you solve the question completely. CTM</p><p>Increase the frequency of the solved questions in the list that you prepared above. For medium questions, take some time and understand the questions, write down in one liners what is given and try to remember what algorithmic question you are solving because only that approach is mostly going to give you the solution. Refrain yourself from opening the discuss section. But if you are not able to think of an approach in 3–5 mins. Refer to the discuss section and say ‘Ahh! this is what was needed! Shit I was so close!’ CTM</p><p>For hard questions, Follow the same approach as that of medium just that you can use about 10 mins to come up with an approach because they are usually dedicated to a specific algorithm (ex — Trie, DP) or they are made up of at most 2–3 medium algorithms. Do not have the mindset of giving up while solving the question. Use the time wisely and use the Discuss section freely but do solve it after you have understood the approach. Don’t pass the question. CTM</p><p>Hard questions are meant to give you an hint of the limit of difficulty that can be expected in worst case. Try to choose medium-hard questions at first mostly so as to build up the confidence.</p><h4>Follow OOPs</h4><p>The only con of leetcode i feel is they have a template class ready for every solution that you are going to provide. It is recommended to follow OOPs approach. Define data members in private, use good naming conventions for variables and functions. Try to keep the code clean with the help of proper structured functions. Always present your solutions in terms of classes. Create classes for LinkedListNode, GraphNode, TreeNode etc. It is really better to develop this habit from the very start as people generally tend to forget these things in the interview.</p><p>That’s it within 2 months you will be ready to outshine others who have not followed this approach.</p><h3>How will I know that I’m ready?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*0YEMpFjZWvQZzXNn332H0g.gif" /></figure><p>As easy as it sounds, It’s difficult to answer. It is completely dependent on the fact that how much honest have you been with your preparation. You should have solved at least 3–5 problems minimum for each algorithm in every data structure. Were you able to push most of your items from your Intermediate bucket to easy bucket and from hard bucket to intermediate bucket?</p><p>Best way to experiment this is to ask your friend to pick any question from leetcode from medium difficulty and check whether you were able to solve it. The old trial and error way.</p><p>The key is to devise the intuition behind the algorithm and that comes with experience and practicing. If you have seen enough of the questions, you are ready to solve them at any point in time. Because sometimes problems require only a specific algorithm to solve and we cannot solve them until we have seen the approach somewhere. This bucketing approach helped me a lot as it identified the topics I feel I am not strong at and made me work specifically on them smartly. CTM</p><p>You can refer to tons of curated SDE sheets from a lot of amazing youtubers out there in the end but let me know in the comments if you want me to share a list of questions that I feel important.</p><h3>‘Data Structures and Algorithms made Easy’</h3><p>This is a gods book. I cannot put in words how important it is to read this book. This book has the appropriate algorithms that are often asked in the interviews. It has got crystal clear explanation and it talks to you itself like a mentor. I have been following this book for the last 5 years and gave a thought of creating it as a NFT lol!! Do refer this book it’s easily available online, I usually prefer hard copies as we can make notes right onto that point.</p><p>Tip: Watch out videos on improving the problem solving and improving imagination on a daily basis.</p><h3>Last but not the least</h3><p>Let me know if you were expecting my insights on a specific topic under DSA preparation. I will add that too in this article. Suggest me some topics on which you want me to cover in my next article and do not forget to follow me on medium as well as on Instagram <a href="https://www.instagram.com/techmunks/">techmunks</a>. I will be starting to post content on this page very soon, so as to give more crisp unique tips that can help you to standout during your interviews. <strong><em>It’s always about the little steps we take in life.</em></strong></p><p>Github: <a href="https://github.com/sahilkhoslaa">https://github.com/sahilkhoslaa</a></p><p>Instagram : <a href="https://instagram.com/techmunks">https://instagram.com/techmunks</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77c5ff30e47d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The secret formula to crack Google’s Interview Process]]></title>
            <link>https://medium.com/@sahilkhoslaa/the-secret-formula-to-crack-googles-interview-process-b5fb1da35f8?source=rss-1ee6cedf9145------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5fb1da35f8</guid>
            <category><![CDATA[faang]]></category>
            <category><![CDATA[tech-interview]]></category>
            <category><![CDATA[faang-interview]]></category>
            <category><![CDATA[analysis]]></category>
            <category><![CDATA[google]]></category>
            <dc:creator><![CDATA[Sahil Khosla]]></dc:creator>
            <pubDate>Fri, 27 May 2022 11:10:51 GMT</pubDate>
            <atom:updated>2022-05-27T16:54:38.498Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi everyone, I know a lot of you are wondering where am I going wrong, am I missing something in my preparation or what do I have to do to crack Google.</p><p>Here is my take how one should prepare for Google’s process in an easy non-frustrating way. I am going to talk about things no one mentions about and these are as much as important as having the knowledge of the Software Engineer domain. I hope you find this article useful and do let me know what you think about it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*9I56ZIffOKCu0k_sbErb_w.gif" /></figure><h3>What is Google looking for?</h3><p>Needless to say google is looking for top-notch set of developers across the globe but they are also looking for an x-factor which is what separates googlers from the rest of the crowd.</p><h3>The Secret Formula</h3><p>X-Factor = Algorithmic Knowledge + Problem Solving + Communication + Speed</p><p><strong>Algorithmic Knowledge</strong> — Google expects you to have not good but great algorithmic knowledge. You should be knowing all the basic and some important advanced algorithms. If you are a person who crams a lot I would advise you to also pray a lot in the interviews. Cramming never helps! Advance algorithms are usually made up of basic algorithms itself. The only best approach to learn advance algorithms is to try to divide the algorithms into sub-algorithms and then adapt it by using them in some other problems and this comes with experience only.</p><p><strong>Problem Solving </strong>— Google is looking out for people who understands the passion behind solving problems. If you are someone who tries to understand the mechanisms/working behind everyday applications or tries to solve the problems that are not visible to the naked eye, then yes you are a really good fit. Problem Solving includes creativity and sharpness. I play a chess a lot, I mean a lot which helped me develop pattern recognition and helped me make decisions both visually and analytically. It improved my problem solving creativity a lot and no I didn’t chose my opening move as <strong>Queen’s Gambit</strong>. I used to do competitive programming (It is not a must have but it is good to have).</p><p><strong>Communication</strong> — Communication is the key. Probably one of the reason most people are suffering even though having a good talent and knowledge about the domain. It’s easy to say not to be nervous but everyone gets a bit nervous during the interviews which sometimes impact our performance. Even I was struggling with this, so two piece of advice my friend gave me which I really consider the best is first just before the interviews ask yourself in heart what is your end goal and say to yourself that yes you have done enough preparation for this and you have got what it takes! Bring it on! and second Don’t ever think of this as an interview I repeat don’t instead take this as a discussion that you do with your friend. Interviewer is not sitting to reject you instead they are there to accept you. Just like an arrange marriage, they will only reject you if you give something to reject! This helped me a lot in boosting my confidence up and I also played ‘Never say Never by Justin Bieber’ before my every interview, please don’t judge me! <strong><em>Don’t defend yourself if interviewer points something wrong in your answer instead accept it and amend it</em></strong>. So remember staying confident is the key.</p><p><strong>Speed</strong> — Again a really important factor for google. Everyone knows how to code but to solve a problem with the right speed is very very crucial. I am not building up any pressure but yes they expect to ask you at least 2 questions in the interview and things are probably (not in every case unless the question they have asked is of hard difficulty) on the negative side if you wound up only solving one problem. Time yourself out. Take around 15–20 mins for solving medium questions and be prepared for follow-ups Google loves to ask follow-ups as they want to see how much easily can you deal with modifications.</p><h3>Don’t Over prepare</h3><p>Do not over prepare. I have seen people having FOMO which leads them to solve more questions than needed thinking they need to solve every question they see in be it leetcode or geeksforgeeks.org! Even if you have this urge try to apply <strong>3 minute rule</strong> in which just give yourself just 3 minutes to think of the algorithm in your head after reading and move on. Because if you are not able to think within 3 minutes you probably won’t be able to think of the algorithms anyways in an actual interview. Fight this urge to solve amount of questions which are greater than your capacity.</p><h3>Tips during an Interview</h3><ol><li>Prepare a 30 seconds introduction of yourself. Google Interviewers are more focused to assess your Technical skills as you have been already screened based upon your introduction in your screening round.</li><li>Make sure your read/understand the question carefully. I cannot emphasis much on this that how important it is to understand the question carefully. Please I repeat Please spend ample amount of time in understanding the question. Do not think the interviewer will judge you if you are constantly asking questions. Ask meaningful and clarifying questions. I used to make multiline comments (I used C++) and I specified each and every detail interviewer is telling me. Eg- /* N ≤ 10⁶, i &lt; j, element cannot move more than 2 steps in a transaction, numbers can be negative etc */. You see this establishes whatever interviewer is saying as you have a written proof. Also it helps in a way that you can think of more clarifying questions while you are typing these comments out. Do not move forward unless each and every bit of detail is clear to you.</li><li>Take a pause now 30 seconds is fine. Think out of an algorithm does not have to optimal at first but if it is already optimal than you have owned the game my friend! Give that approach. Take an example and explain them not just verbally but also typing them out in your google doc/code editor. Explain them how it will work and how the example will also cover the edge cases. If you are not able to think of an example ask them that you need an example. Don’t be afraid.</li><li>Don’t get scared if interviewer is pointing something out I know people usually tend to loose confidence here itself that why is the interviewer is pointing this out. Ohh shit! I have made a mistake! It is never like that. The interviewer just only wants to understand what were you thinking while you established the fact you stated and accept it if you have done a minor mistake and amend it quickly.</li><li>Take at max first 5 mins to think out of an approach including the 3 minute rule and spend the next 8–9 minutes in discussing your approach and optimising it (no I am not mad, 8–9 minutes is sufficient if you are prepared enough) and spend the last 6–7 minutes in coding out the problem after you have the CONSENT of the interviewer.</li><li>Write down neat code, do add comments only the important ones. There is no need to add comments like //using for loop here or //adding the elements instead comments which explains the purpose of the whole piece of code that you have written.</li><li>The more you give something to them that they can use into your feedback the better it is. Show them that you know STL in deep, how they are implemented. Show them that you are not backing down even if you are not able to solve the problem. Show them you don’t directly jump to the problem instead you take your time and then act upon it. Just a tip: Don’t use unary if condition in interviews ( (isBooked)?return 1: return 0;)</li><li><strong>Googlyness and Leadership — </strong>Please don’t take this round casually. As I have seen many people getting rejected because google could not find googlyness in them. This being said pull out your resume and read it carefully and close your eyes and try to revisit your resume in detailed milestone and capture each and every story that you feel had made a positive impact in your software development journey. Note these stories out and prepare them in a STAR format. This round consists of two sections in which they will ask you questions about Tell me about a time when something happened and second they will put you in a situation and assess your reaction. Ex — You are a head of this product as Lead Software Engineer and two of your teammates had a conflict about certain algorithm How will you assess it?.</li><li>Lastly interviewers will give you 5 mins to ask questions to them Please don’t waste this opportunity by asking can you tell me my feedback! Dude you are anyways going to get your feedback through your recruiter (in some cases) so don’t waste it. Instead ask them some casual good questions like what problems are they working on in brief? See if you can relate with any news you heard. Ask them about the daily challenges they face and how is life at google. Ask them how the growth looks like at google. etc like this you can ask many questions.</li></ol><h3>Resources</h3><ol><li>I never followed any youtube channel for my preparation I was never fond of any bhaiyas/didis for DSA preparation. Instead I used to look out for tips and tricks for interviews preparation but I could not find much content on that so I will be starting my own channel depending upon the feedback I get on this article in which I want to give insights for the interview preparation to the deepest level so that audience can actually understand what is going wrong because I have been there and It took me a lot of time to crack what was it. Ahh! Finally!</li><li><strong>Keeping it Simple</strong> — I recommend this God’s book ‘<strong>Data Structures and Algorithms made Easy</strong>’ by Narasimha Karumanchi. This book has got crystal clear explanation of all the algorithms and all good software engineers have referred to it while preparing the coding interviews. Secondly you can also refer to ‘<strong>Cracking the coding interviews</strong>’ by Gayle Laakmann McDowell. This book is heavy so give it a read if you have time.</li><li>I highly recommend to practise consistently on <strong>Leetcode</strong>. Do not practise a lot of questions but practise quality questions. I used to list down all the data structures and algorithms topics and I used to tick mark myself that I know these topics and what I don’t know I used to touch those topics very slowly. Like you I was also scared of graphs and Dynamic programming. I started to solve graphs using my imagination like drawing circular nodes in my head and placing myself at the starting point and I have to go to the destination point. This helped me a lot. But again its about giving time to yourself and these topics. initially you will see you are not able to solve it but Don’t beat yourself up. Just don’t give up you are almost there and I am rooting for you!</li><li>I also highly recommend to try <a href="https://www.pramp.com/">pramp.com</a>. This is a platform where you can take and give mock interviews for free. The questions lined up here are pretty apt and amazing and are of the level big tech companies are asking these days. Time yourself and improve with the help of feedback.</li><li>There are a lots of resources you can follow on DSA I am not going to go specifically into that but what I can say just believe in the path you are taking and don’t randomly follow anyone. That’s why I preferred books instead of people and It helped me a lot in removing the ambiguity or conflicts I was having in concepts.</li><li>If you are getting rejected constantly and not able to figure out what is going wrong? — Prepare an excel sheet in which prepare what all companies have you interviewed for. Write down their questions. start reading those questions and ask yourself if you were to be given any of these question at any random point of time in life will you be able to solve it. If the answer is no, then probably your problem solving ability is still not upto the mark. Practise until you are able to solve every question at any point in time just like you solve 2+3 = 5 in your head. If the answer is yes, probably the lagging point could be in your speed or communication for that matter.</li></ol><h3>FAQs</h3><ol><li><strong>What should I focus on for interviews competitive programming or development? — </strong>I hate to even get into this debate. Competitive programming or development has nothing to do with your interviews competitive programming helps in building problem solving creativity and development helps in building your profile which will get you shortlisted. The only thing you should focus on getting your concepts clear for DSA.</li><li><strong>I am working in other domain than software engineering can I still crack google?</strong> — The answer is yes It just takes immense hard work and perseverance to crack google but it is not impossible. Firstly you need to develop a portfolio around software engineering with amazing projects. It will take time. Meanwhile start practicing DSA on a beginner level. Understand why is there a need to store data into these format etc. Slowly get hold on DSA. Participate in coding competitions, give mock interviews build confidence. You will definitely see some progress. This process is going to take time but you can achieve it if you are consistent.</li><li><strong>Does Google hires only experienced candidates? — </strong>No, It is definitely not like that I have seen google hiring just graduates for Software Engineer position. It’s just you need to have what google wants to see in its candidates.</li></ol><h3>What am I going to do?</h3><p>I have seen people struggling with lack of motivation as they usually know DSA but they don’t know what could be the lagging points so I am going to start an Instagram page in which I will be sharing short videos on tips and tricks or hacks while preparing for this interview named <a href="https://www.instagram.com/techmunks/">techmunks</a>. The idea is to share the deepest of the tricks in fun and interactive manner which you will be seeing me roasting my fellow <a href="https://www.instagram.com/techmunks/">techmunks</a> and providing you the necessary info.</p><p>Let me know if you have any thoughts about this idea in which we can improve.</p><p><strong>Last Insider Tip: </strong>Don’t be scared of the interviewer they are also under the same pressure like you. Their job is to make sure that you are comfortable enough so that you bring out your A game. Use this to play your cards right.</p><h3><strong>Let’s Discuss</strong></h3><p>Still have doubts. Let’s connect. You can ping me anywhere you want. Looking forward to meet you at google while I enjoy my free food. I will be actively responding to comments, please let me know what are your thoughts and <strong>share</strong> this with someone who you think needs this right now! Caio!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5fb1da35f8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>