Navigating the Placement Journey: Insights from a Recent Grad | FAQs

As September is here, the placement season is in full force, and the mix of tension and excitement fills the air. Whether you're a final-year student on the verge of graduation or a pre-final-year student preparing for the future, the placement process can feel overwhelming. Having been in your shoes, as a former tech CSE Head at IEEE SB JIIT during my college years and now working as an SDE-1 at MakeMyTrip, I want to offer guidance based on the most frequently asked questions I've received from students like you.

This blog is not about influencing you; it's a friendly conversation aimed at helping you navigate this critical phase efficiently. I don't want you to waste time where it's unnecessary or procrastinate your studies by reading endless blogs online. Feel free to jump to the sections that interest you or provide the most benefit. Below is a list of the questions addressed in this blog, primarily for 4th-year or 3rd-year students:

1. What was your interview experience like?
2. How do you do introductions in Interview?
3. What are the types of questions in interviews?
4. How do you study for DSA?
5. How do you study theory?
6. How do you prepare for System Design?
7. When did you get your offer? How long should I wait?
8. How should I approach coding rounds?
9. How can I enhance my resume?
10. What should I ask when the interviewer invites questions from me?
11. Should I aim for on-campus or off-campus job opportunities?
12. What's the Significance of Internships in Landing a Job?
13. How to Handle Technical Questions You Don't Know the Answer to?
14. Is GPA a Critical Factor in Tech Placements?
15. What is one mistake that I wish I had known sooner myself??

What was your interview experience like?

There are a lot of layers to it, every interview experience will always be different than any other. Still, there are a few things that can be expected to be present in most interviews. I will break this into further sub-questions. I will be uploading a detailed interview experience of mine for MakeMyTrip, really soon.

How do you do introductions in Interview?

Introducing yourself effectively in an interview is a crucial yet often underestimated aspect. Your introduction sets the tone for the entire interview and can greatly influence the direction it takes.

• Be Prepared but Appear Natural: It's essential to prepare your introduction in advance, but present it in a way that seems spontaneous and natural. This makes you appear confident and composed.
• Chronological Overview: Start your introduction with your journey from the beginning of your college experience. Begin with your first year and gradually work your way up to the present, briefly touching on key milestones.
• Highlight Your Passion: Instead of merely listing your accomplishments, emphasize your passion for the subject or field. For instance, rather than saying, "I made a project X for my class on DBMS," say, "My deep interest in DBMS led me to create Project X, which was a significant learning experience in applying DBMS concepts."
• Relevant Details: Be selective about the information you include. Your introduction should focus on what's directly relevant to the job or field you're interviewing for. Tailor your introduction to align with the specific requirements of the role.
• Subtle Indications: Strategically imply your strengths and areas of expertise without overtly listing them. For instance, if you excel in DBMS, DSA, and ML, you can frame your introduction around these subjects and projects related to them. Mention your other skills like CNS and OS indirectly, letting the interviewer infer your versatility.
• Concise and Inviting: Keep your introduction concise, leaving room for the interviewer to delve deeper into specific aspects if they wish. Your goal is to pique their interest and encourage questions.

Remember, the purpose of your introduction is to engage the interviewer, create a positive impression, and open the door for further discussion. It should reflect your enthusiasm, expertise, and alignment with the role you're interviewing for. By striking a balance between preparedness and spontaneity, you can effectively steer the interview in a direction that showcases your qualifications and strengths.?

What are the types of questions in interviews?

a. Behavioral Questions: These questions assess your past behavior to predict your future actions. They often begin with phrases like "Tell me about a time when..." or "Give me an example of..."

b. Technical Questions: These assess your expertise and knowledge in a specific field or technology. They can range from coding challenges to questions about algorithms and technical concepts.

c. Situational Questions: These pose hypothetical scenarios to evaluate how you would handle certain situations in the workplace. They aim to assess your problem-solving skills and decision-making abilities.

d. Competency-Based Questions: These questions focus on your skills, competencies, and abilities related to the job. They may ask you to describe situations where you demonstrated particular competencies.

e. Cultural Fit Questions: These assess if you'll fit into the company culture and work well with the team. They may ask about your work style, values, and how you collaborate with others.

The key to acing interviews is not just knowing the surface answers but being prepared to dive deeper when asked. This shows your depth of knowledge and genuine interest in the topic. So, for each type of question, ensure you have those extra layers of understanding ready to impress your potential employers.

For the most basic example - “What algorithm would you use to search in a sorted array?” Ans - “Binary search”

Depth 1 - “ Why Binary search/What are its pros/What were the options why did you select binary search” Ans - “Because it helps to search in O(log n) complexity with no loss from linear search.

Depth 2 - “How does it provide O(log n) complexity?” Ans - “As it eliminates half of the remaining array at each step, thus, it reduces the size of the array by 1/2 times at each step. At the nth step, it has reduced the array to 1/2^n thus, the logarithmic time complexity”

How do you study for DSA?

Obviously, there are tons of sheets out there, you can refer to any of those, you really should. But I want to point out more about the way to study it. Studying Data Structures and Algorithms (DSA) effectively is crucial for computer science students, especially those in their third year. Here are some valuable tips to guide you through your DSA studies:

• Active Problem Solving: When you encounter a problem, don't rush to check the answer or solutions immediately. Take the time to actively attempt solving it on your own. Give it your best shot, and if you get stuck, that's okay. This practice helps develop problem-solving skills.
• Patience is Key: As you mentioned, waiting for some time before looking up solutions is a great approach. Sometimes, stepping away from a problem and revisiting it later can lead to fresh insights. It's normal to struggle with certain problems; perseverance is key.
• Learn from the Best: After successfully solving a problem (or even if you didn't), reading the best solutions is a fantastic way to learn. You can gain insights into more efficient approaches, alternative solutions, or clever tricks you might not have thought of.
• Taking Effective Notes: Note-taking is a powerful learning tool. Spend time creating comprehensive notes for each problem you tackle. Your notes should include:-> Problem Summary: Write a concise description of the problem. This helps you recall the problem's context and requirements.-> Hints: Document hints or clues that helped you approach the problem. Coming up with hints without giving away the full solution can be extremely valuable for future reference and learning.-> Intuition: Explain how you thought about the problem and what led you to your solution. This helps you understand the thought process and apply it to similar problems.-> Approach Explanation: Describe the final solution in words. Ensure that you can explain your solution conceptually before diving into code.-> Pseudo-Code (Optional): If you prefer, write pseudo-code to represent your solution algorithmically. This can be particularly helpful for more complex problems.-> Additional Insights: If you discover any interesting or unique aspects of the problem during your analysis, make sure to note them down. These insights can be useful in future problem-solving.

How do you study theory?

Final Years:

For those in their final year, a strategic approach is key. Start by memorizing the top 50 questions for each topic while ensuring a deep understanding of each question. It's crucial to diversify your sources, so visit at least 4-5 different websites for these top 50 questions. Variety can provide a broader perspective.

Third Years:

In the third year, I personally found taking roadmaps present on the net and creating comprehensive, self-made notes to be highly effective. These notes should be detailed, not merely copied from existing materials. As you study, jot down the information in your own words. This not only reinforces your understanding but also promotes retention. Periodically revisit these notes, aiming to understand the content deeply. Don't hesitate to use headings, subheadings, and bullet points to organize your notes effectively. Remember, studying in isolation can be less effective, so make sure to make notes. Regular revision is also crucial for long-term retention.

How do you prepare for System Design?

Foundation in OOPS:

Before delving into System Designs, it's essential to have a strong foundation in Object-Oriented Programming (OOPS). Ensure you're comfortable with OOPS concepts and principles.

Leverage LeetCode Discussions:

For fresher-level System Design preparation, exploring LeetCode discussions can be invaluable. Reading and understanding these discussions can provide practical insights into system design problems.

Watch System Design Videos:

To gain a better grasp of System Design concepts, watch instructional videos that provide real-world examples. Visualizing design concepts can be very helpful.

Embrace the Conversational Nature:

In System Design interviews, there isn't always a single correct answer. It's more of a conversation between you and the interviewer, where you discuss various design choices and trade-offs. Be prepared for this back-and-forth exchange.

(Do also read the answer to ‘What is one mistake that you wish you knew sooner yourself?’)

When did you get your offer? How long should I wait?

I received my offer in mid-October, which did involve a considerable wait. Securing a job offer can indeed involve an element of luck, but your continuous efforts and perseverance are essential.

Regarding the waiting period, it can vary from person to person and depends on various factors, including your skills, preferences, and the job market. Waiting until the end of September to be selective about your job choice is a reasonable approach. It allows you to assess your options carefully and consider opportunities that align with your career goals.

Even if you haven't secured a job by September end, don't be overly concerned. Companies continue their hiring processes into November, although the frequency may decrease slightly after that point. Keep applying, networking, and showcasing your skills, and opportunities may still come your way. Keep giving your best and remain patient, as the right offer may come when you least expect it.

How should I approach coding rounds?

Coding rounds can be both exciting and challenging. Here's some guidance to help you navigate them:

Master DSA (Data Structures and Algorithms): The foundation of coding rounds is a strong grasp of DSA. Invest time in understanding key concepts and practicing problems related to arrays, linked lists, trees, graphs, and algorithms.

Participate in LeetCode Contests: LeetCode contests are a fantastic way to improve your problem-solving skills under time constraints. Join these contests regularly to challenge yourself and learn new techniques.

Don't Be Discouraged by Rejections: It's essential to remember that not getting selected doesn't always reflect your skills. Luck plays a part in these rounds, too. Don't be disheartened by failures; they are part of the journey.

Continuous Learning: After a coding round, analyze the questions you couldn't solve. Work on them to improve your skills. Consistent practice and learning from your mistakes will make you a better coder.

In summary, focus on building a strong foundation in DSA, participate in coding contests, and maintain a positive mindset even in the face of rejection. Your hard work will pay off over time. Keep going, and you'll see progress!

How can I enhance my resume?

Crafting an effective resume is crucial for landing the job you desire. Here are some key tips to improve your resume:

• Quantify Achievements: Instead of vague statements, use numbers to highlight your accomplishments. For example, "Improved speeds by 86.7%" is more impactful than "Improved speeds."
• Be Concise: Keep your sentences clear and to the point. Use bullet points to list your achievements and responsibilities. Avoid lengthy paragraphs.
• Organize Thoughtfully: Divide your resume into well-defined sections such as "Summary," "Work Experience," "Education," and "Skills." This makes it easy for recruiters to find information quickly.
• Formal Language: Use formal language and avoid personal pronouns like "me" or "I." Write in the past participle tense for a professional tone.

What should I ask when the interviewer invites questions from me?

When the interviewer gives you the chance to ask questions, seize this opportunity to learn more about the company and showcase your enthusiasm. Here's what you should keep in mind:

• Avoid Asking for Feedback: It's generally not appropriate to ask for feedback during the interview. This can come across as too forward. Instead, focus on questions related to the company and the role.
• Explore Growth and Learning Opportunities: Inquire about the opportunities for professional development and growth within the company. You can ask about mentorship programs, training, or any initiatives that support career advancement.
• Learn About Company Culture: Ask about the company's work culture, values, and what makes it unique. Understanding the culture can help you determine if it's a good fit for you.
• Discuss Job Responsibilities: Seek clarity on the specific tasks and responsibilities you'll have in the role. This shows your genuine interest in the position.
• Express Enthusiasm: Frame your questions in a way that demonstrates your enthusiasm for the company and the role. This can leave a positive impression on the interviewer.

Remember, asking thoughtful questions not only helps you gather valuable information but also shows your genuine interest in the position and the company. It's an opportunity to leave a lasting impression on the interviewer. Also listen to answers with enthusiasm and great attention.

Should I aim for on-campus or off-campus job opportunities?

Both on-campus and off-campus placements are both important and you should try your best for both. Here's some guidance:

• On-Campus Placements: On-campus placements are often considered the easiest path to securing a job. I myself had an on-campus placement experience, and it can indeed be a smoother process. Universities often have established connections with recruiters, making it more convenient.
• Off-Campus Opportunities: Don't hesitate to explore off-campus opportunities. To increase your chances, always consider asking for a referral politely before applying for a job. People are often motivated to provide referrals, so make a compelling case in your LinkedIn messages.Expect Rejections: Be prepared for rejections, sometimes even without clear reasons. The job market can be competitive, and setbacks are a part of the journey. Stay persistent and keep improving.Follow Influencers: Many industry influencers regularly share job openings and updates on platforms like LinkedIn. Follow these influencers to stay informed about job opportunities and gain insights into the market.

What's the Significance of Internships in Landing a Job?

Internships can play a role in your job search, but they are not the sole determinant of success.? Internships can be helpful in getting your resume noticed and shortlisted by employers. They provide practical experience and demonstrate your ability to work in a professional setting. But it's important to note that not having an internship is not a deal-breaker. Many successful professionals didn't have internships or had limited internship experience.

Emphasize Learning and Projects: Whether you have internships or not, the key is to emphasize your learning capabilities and practical skills. If you do not have an internship, focus on meaningful projects where you can showcase your problem-solving abilities, technical skills, and in-depth understanding of the work.

Learning Matters More: Employers often value your ability to learn and adapt over having a long list of internships. Highlight how you've learned and applied concepts in real-world scenarios, even if it wasn't through formal internships.

In conclusion, while internships can be beneficial, they are not the only path to landing a job. Concentrate on demonstrating your learning capabilities and problem-solving skills through meaningful projects and experiences. Employers appreciate candidates who can apply their knowledge effectively.

How to Handle Technical Questions You Don't Know the Answer to?

When faced with technical questions that you're unsure about, it's crucial to approach them honestly and strategically. Here's a thoughtful way to handle such situations:

• Honesty is Key: Be transparent about your uncertainty. It's better to admit that you don't know something than to provide incorrect or vague answers.
• Eliminate Unsuitable Approaches: Analyze the problem and verbalize your thought process. Explain why certain approaches won't work based on your understanding of the problem statement. Emphasize the "why" behind your decisions.
• Consider Multiple Perspectives: Explore various angles to tackle the problem. Discuss your thought process with the interviewer, even if it involves brainstorming suboptimal or brute-force solutions initially.
• Engage in a Dialogue: Use the interview as an opportunity to learn. Engage in a dialogue with the interviewer, asking questions for clarification and seeking guidance. They are often interested in your problem-solving approach more than just the final answer.
• Brute Force Exploration: Start with a brute-force solution if necessary. This demonstrates your willingness to find a working solution even when you don't have an optimized one immediately.
• Remember the Norm: While it's acceptable not to know everything, make sure that areas where you lack knowledge are the exception rather than the rule. Interviewers understand that candidates may have gaps in their knowledge, but a consistent lack of understanding in fundamental areas can be concerning.

In conclusion, handling technical questions you don't know the answer to should involve honest communication, a structured thought process, and a willingness to engage in problem-solving discussions. Interviewers are often interested in your approach and problem-solving skills as much as the final solution.

Is GPA a Critical Factor in Tech Placements?

In tech placements, GPA does play a role in shortlisting candidates:

• GPA >= 6.5: 50% of companies shortlist.
• >=7: 60% of companies shortlist.
• >=7.5: 75% of companies shortlist.
• >=8: 90% of companies shortlist.
• >=8.5: 95% of companies shortlist.

However, it's important to note that GPA primarily helps in getting to coding rounds and resume shortlisting. It may not have a significant impact on final interviews.

What is one mistake that I wish I had known sooner myself??

Sharing Your Thought Process in Interviews

One valuable lesson I learned through experience is the importance of sharing my thought process during technical interviews. It's not about silently arriving at the correct answer; rather, it's about thinking out loud and engaging in a collaborative problem-solving dialogue with the interviewer.

Here's what I recommend:

• Take Time to Understand: Begin by taking a few moments to fully grasp the question. Don't rush into solving it immediately.
• Clarify with the Interviewer: To ensure you're on the same page, explain your understanding of the question to the interviewer. This clarifies any potential misunderstandings.
• Think Out Loud: As you work through the problem, vocalize your thought process. Imagine you're explaining the problem to a friend and share each step of your thinking. This helps the interviewer follow your reasoning.
• Balanced Communication: Avoid excessive talking or silence. Take breaks to think, but keep the interviewer informed about your progress and thought direction.
• Collaborative Problem Solving: Understand that interviewers are often inclined to help you succeed. If they see you're on the right track but need a nudge, they may provide hints to guide you toward the correct solution.

Remember, interviews are not just about the final answer; they're a chance to showcase your problem-solving skills and your ability to work collaboratively. Sharing your thought process can significantly enhance your performance in technical interviews.

I'll try to continue to update this blog if more questions or valuable information comes up. Best of luck with your placement journey!

Image by pch.vector on Freepik