<?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 Jigyasa on Medium]]></title>
        <description><![CDATA[Stories by Jigyasa on Medium]]></description>
        <link>https://medium.com/@jigyasajha?source=rss-49a2e9343fd1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*25GT1DnDat5H40MC.</url>
            <title>Stories by Jigyasa on Medium</title>
            <link>https://medium.com/@jigyasajha?source=rss-49a2e9343fd1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:23:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jigyasajha/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[Placements 101: My 2 cents about the placement experience of IIT Guwahati.]]></title>
            <link>https://medium.com/@jigyasajha/placements-101-my-2-cents-about-the-placement-experience-of-iit-guwahati-f915477a50bd?source=rss-49a2e9343fd1------2</link>
            <guid isPermaLink="false">https://medium.com/p/f915477a50bd</guid>
            <category><![CDATA[preparation]]></category>
            <category><![CDATA[campus-placements]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[coding-interviews]]></category>
            <dc:creator><![CDATA[Jigyasa]]></dc:creator>
            <pubDate>Fri, 07 Aug 2020 12:27:17 GMT</pubDate>
            <atom:updated>2020-08-08T21:45:33.065Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*YpJ5fg1IdR02noREKNrVTg.gif" /><figcaption>Medium suggested me to add a feature photo, so here is a random picture of IIT Guwahati. Credits: iitg.ac.in</figcaption></figure><p>If I could go back in time and am given an option to go through placements or not, I probably would be tempted to not go through placements and have it all easy but in retrospect now that I know what an enriching experience this has been, I can definitely say that I am glad I went through the placement season and I wouldn’t want to let go of the phenomenal experience and all the things I’ve been able to learn in such a short span of time. Hence I wouldn’t have wanted to do this in any other way.</p><p>The 7th semester is the most dreaded semester for everyone in college. It is the semester that is ‘deemed’ the most important semester to prove your skills and show it to companies how you’ve made yourself worthy of being hired. But I want to correct this notion. The placements in college generally have a huge luck component attached to it. There are so many variables that are not in our control but which determine our placements. The allocation of slots to companies is based on a lot of components that even involve factors such as relations with our campus, the brand name inside our campus, hence don’t fall into the trap of treating the slots as a hierarchy. There are a lot of good companies/start-ups spread across Day 1, 2, and 3. The key point I want to highlight is that where you get placed, which slot you get placed in, is NOT a measure of your skills or your hard-work. All the companies come to our campus only to hire people, you just have to find that one for yourself. And in the worst-case scenario, you can always apply off-campus if you’re not really satisfied with campus placements.</p><p>The placement tests start in the last week of September or the first week of October generally. What follows is a grueling 2 months of having multiple tests possibly on a single day along with your academic engagements of the 7th semester, such as classes and BTP. Most of the tests of companies have 2 to 3 coding questions, a few companies even have MCQs on OOPS, OS, DBMS, or probability or aptitude questions. Shortlists start getting released only in the second half of November and you’ll know the shortlists of most companies only in the last week of November.</p><h3><strong><em>A must-do (bare minimum) preparation list for tech interviews.</em></strong></h3><p>Tech interviews here mean both quant as well as software roles. It is advisable to be aware of puzzles, probability, and coding for all ‘tech’ interviews. Quant interviews require additional knowledge of probability in-depth and hence if you’re aiming for Quant roles, make sure you’ve thoroughly studied probability and practiced more puzzles and probability questions.</p><p>For coding, doing interviewbit until you have a fair understanding of all the data structures and algorithms is highly advisable. Leetcode is a great resource for further practice. Contrary to the common notion that graphs is not asked by companies, it is an extremely important topic and hence you should be aware of all the standard graph algorithms and graph-type problems. The inter-IIT doc of the current year and the docs of previous years must be your Bible, make sure you write the code yourself of the questions of the company whose test is upcoming. You might be really surprised when the questions are repeated. It is also a great resource to practice questions of varying difficulty levels. Also, do not skip topics such as tries, ternary search trees, AVL, RB trees, B and B+ trees for the aspect of interviews.</p><p>Do all the puzzles on geeksforgeeks and interviewbit, those puzzles are very basic and you might encounter them more often than you’d expect. ‘Fifty Challenging questions on Probability’ is a must-do if you’re looking to practice questions on Probability. Also, check out the tutorial on Mathematical Expectation on CodeChef which highlights the common type of questions on expectation. Read interview experiences of companies you’re interviewing for, talk to seniors who’ve interviewed with the company, it really helps to get an idea of what a company might expect. Some companies only test you on DS&amp;A, and hence their interviews only consist of coding questions, whereas some companies also ask questions on Operating Systems, DBMS, etc. OOPS is very important for almost all companies so make sure you do this topic extensively. Since in campus placements it is safer to be prepared for a number of companies at the same time, it is helpful to have a basic understanding of the core Computer Science subjects. These topics are really vast but such thorough knowledge is usually not required for the purpose of interviews and hence I’ve tried to list out some keywords which shouldn’t be missed as these will help you cover the topics, concepts or questions most often encountered.</p><p><strong>OOPS:</strong> objects, classes, encapsulation, inheritance, abstraction, polymorphism-compile time vs run-time, virtual function, its working(vTable and vPtr), abstract class, friend class.</p><p><strong>Operating Systems:</strong> program vs process, process synchronisation, threads, linking, loading, binding, mutex, semaphores, monitors, deadlock, banker’s algorithm, philosopher’s diner’s problem, segmentation, paging, page fault, memory management-virtual and physical, thrashing.</p><p><strong>DBMS:</strong> types of keys, SQL queries, normalisations, ER model.</p><p><strong>Networks:</strong> OSI model-layers and functions, TCP/IP, UDP, CIDR, Classful, HTTP vs HTTPS. Networks is usually not required for interviews but some select few companies might require extensive knowledge and hence it is advisable you do your research for the company you’re interviewing for. Just to be on the safe side at least do the topics I’ve mentioned above as the most commonly asked questions are usually from these topics.</p><p><strong>System Design:</strong> Some select companies do take system design very seriously and that’s usually because the understanding of system design is often very crucial for a Software Developer. Interviewbit’s section on System Design summarises it nicely. For a further understanding, there is a playlist on youtube by Gaurav Sen. No need to do the whole playlist, understand the concepts and see a few examples of commonly asked questions (eg: Design Whatsapp) so that you’re comfortable answering a question if asked. A lot of detailing is mostly not required for fresh grads but do it to the extent so that you don’t lose out on a company only because it asked a design question.</p><p><strong>Object-Oriented design: </strong>This is different than system design and is often more expected in SDE interviews. In this you’re asked questions such as ‘Design a parking lot using Object Oriented principles’ in which you need to highlight the classes, objects which you’ll use and how you will use the OOPs principles. Google and read a few examples.</p><h3><em>Some pieces of advice based on my experience.</em></h3><ul><li>Do not get into coding only because of peer pressure or if you know your interests align in a totally different direction, but knowing to code is a skill required even for some non-tech positions and coding tests are often required in roles such as finance, quant, and machine learning to name a few. Knowing a little basics doesn’t do any harm and just goes to show that if needed, you can ace this part as well.</li><li>Do not rely on one company or even two companies, because so many times the shortlists might seem very random and the company’s decisions cannot be comprehended by anyone. Have a good number of ambitious and safe options in your mind.</li><li>Don’t think if you didn’t make it into a shortlist you have zero chance for interviewing for a company. Be well-prepared if you feel you are the right candidate for a particular company. All the companies have extended shortlists and waitlists which they announce when they come into the campus and even if you’re not in those lists, do not worry, anything can happen on that day, just be prepared.</li><li>To give you a background of what happens on the day of interviews, we were called on 30th November at 9 pm to Umiam and people started getting called for interviews by the PORs of the respective companies a little while after that. I remember I went to a company for my first interview at almost 3 a.m. and it looked like they had already made a choice of who they wanted to take. This is obviously not always the case, a lot of companies were actively having first rounds even when it was late but to be on a safe side, just don’t go very late for your first interview to a company of your priority.</li><li>Stay and wait for another round of interviews at a company only if it looks positive, do not waste time sitting or waiting. This is the time for you to strategically think and act.</li><li>Whenever there’s a disagreement between the interviewer and you, 95% of the time the interviewer would be correct so please do not make it look like you know better than them. That being said, the 5% is possible as well, in fact, it happened with me and I was in an extremely tough spot because the disagreement was based on the time complexity of a very famous algorithm and I was certain of my answer but I realized that the interviewer was sure of his answer being correct so after having tried to explain him a couple of times, I gauged the situation and just agreed to him. By telling you this experience of mine, I am not trying to bias you to agree to the interviewer at all the instances because there can be times when the interviewer is testing you and trying to make sure you’re confident with your answer and can explain it to him/her, but it is also possible that (s)he is mistaken. You’ve to take the call by gauging the situation at that point of time.</li><li>Be prepared for questions like ‘Tell me about yourself’, ‘Tell me something not on your resume’, ‘Strengths and weaknesses’, ‘Question about your internship experience and did you get a PPO’. One more question which I never expected was ‘What other companies are you shortlisted for?’. Please be smart with your answers.</li><li>You can always politely tell your interviewer when you’re not proficient with something and hence to test you on something else. For example, if you are from non-circuital branches and you’re asked a question on Operating Systems, you can politely tell them this is something you haven’t studied in detail because you didn’t have it in your curriculum but make sure you tell them why they should still consider you and how you’ve, for instance, went out of your curriculum to become proficient in DS&amp;A because of your interests. I know of two of my friends who were asked core CS subjects and they denied having studied these subjects in detail but they still got selected because of their overall performance in the interview. You have to sell yourself in interviews. :P</li><li>Interviews can turn out to be really unexpected. I remember being asked about a basic ML concept in one of the Software Development Engineering roles. So it is advisable to have an understanding of important concepts such as Probability, ML, or whatever you think might be relevant for the company or role.</li><li>Know your resume in and out. I cannot stress this enough.</li><li>Please sleep well before slot 1.1 of placements. There’s almost no break between 1.1 and 1.2 and the slots so on and it is absolutely necessary to be prepared for the worst. The process of giving interviews can be really taxing, it can take a toll on you, you can almost just make it, you can almost just not make it, but that is no reason to belittle yourself. Please have someone by your side and take care of yourself during the whole process of giving interviews. Do not think you don’t deserve to be in a certain company because the results were unfavorable at that point of time, it is possible that your interviewer had certain other expectations or reasons possibly which cannot be explained.</li></ul><p>Please note that the whole blog is entirely based on my experience.</p><p>Feel free to reach out to me in case of any queries or suggestions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f915477a50bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>