Abhishek Shukla

FAANG companies are hiring again, here are 8 vetted interview resources to help you pass your interviews you can save for later: System Design Resources: 1. system-design-primer Github repo (275k stars)  - Good high-level review resource https://lnkd.in/g6yMEsGv 2. Alex Xu’s system design guides - Great end-to-end resources about the process https://lnkd.in/gNB26q5W 3. Roadmap for what topics to study - https://lnkd.in/gw__WDTD 4. Designing Data-Intensive Applications - Great book for the concepts you need to understand for system design https://lnkd.in/gMhbvW23 Algo interview resources 5. Github repo of Leetcode questions to study by company (https://lnkd.in/gYP-ND4W) 6. Navdeep's Neetcode 150 - list of good questions to work through for practice https://lnkd.in/gyyb5WWB 7. CLRS book - Great book for learning the fundamental algorithms (just first two sections are most important) https://lnkd.in/g84bh_yd Behavioral Interviews 8. Lenny's first-round interview guide https://lnkd.in/gedSsNfe This curated list will give you a strong foundation but there’s no substitute for real practice. The best you could do is get some mock interviews and feedback from people who interview for their company. Best of luck!

1,769

44 Comments

It often perplexes me that Software Development Engineers (SDE-1) on platforms like YouTube and LinkedIn are offering advice on interview preparation for Senior Software Engineer positions, particularly for system design rounds. Engineers who have just been promoted from SDE-1 to SDE-2 are also guiding how the promotion system operates and how one can achieve promotion. While it is true that they have experienced promotion firsthand, I believe a more comprehensive understanding is required. This understanding comes from going through multiple promotions, observing the process extensively, and ideally, assisting team members in their promotion journey. Being involved in decision-making, providing feedback, and advocating for promotions are crucial elements to truly comprehend how the system works and how to effectively support career advancement within a team. In an environment where views are monetized, it seems that everyone feels compelled to share their opinions, even if they lack substantial experience. This only adds to the noise, and recently, my YouTube and LinkedIn feeds have been overwhelmed with this type of content. It feels reminiscent of the group discussion rounds often conducted during campus hiring drives. Pata nai par bolna hai!

65

2 Comments

Just a couple of months ago, I interviewed at Intuit💪🏻🚀 It was an incredible interview and I want to share my experience for everyone targeting Intuit! 🌴 Technical Screening Round: In this round, I created a stopwatch using React. Additionally, I answered questions on JavaScript concepts like debouncing and throttling. 🌴 Craft Demo Round (~45 mins): I developed a UI for sports event registration, documented the project on Confluence, and even wrote unit tests with 100% coverage. 🌴 Technical Interview I (~45 mins): I solved a factorial problem using recursion and dynamic programming and explained React concepts like hoisting and virtual DOM. 🌴 Technical Interview II (~30 mins): I explained non-functional testing approaches and outlined steps to troubleshoot a non-functional widget based on customer complaints. 🌴 Hiring Manager Round (~30 mins): There was a brief project discussion along with some behavioral questions on communication, leadership, etc. Like every SDE interviewing after a gap, even I was a bit underconfident. But I didn’t want to risk this opportunity. So, I gave a few mock interviews that helped me improve my communication💯 If you’re like me, preparing for interviews after a long time, do give mock interviews to experienced SDEs. You can easily find them on Preplaced these days. Just book a FREE session and get started - https://lnkd.in/gsmRKMmS The best part is, these SDEs don’t just conduct one-off mock interviews. They will help you with your entire preparation, ensure you stay consistent, and even provide referrals🚀 #transition #interview #interviewexperience #collab #preplacedcollab #sde #tech #Intuit #IntuitIndia #intuitinterviewexperience #interviewquestions #sde2 #softwareengineer #TechCareers #JobSearch #IntuitLife #IntuitCareers

67

10 Comments

Alexa, change my title to SDE 2! Hi everyone, I have been promoted to the next level at Amazon. Amazon's evaluation process differs from what you typically write in a work document. This difference offers a unique perspective on how your work is assessed. In hindsight everything seems obvious, so I won't discuss specific successes or failures. However, I want to highlight the lessons I learned, which I'll both apply in the future. 1. Look out for impactful work. 2. My job is not just to create tools or write code but also seek feedback from users and advertise it to potential users. Here is to new learnings and responsibilities. At last but not least. It has been amazing co-workers like Krishnaprasad Krishnamoorthy , Rajkumar Pandian and many more who, I cannot mention as list will go beyond the limit who have played a key role in the whole process.

313

50 Comments

Google is currently hiring a large number of #SWE in India! Due to the high volume of inquiries I'm receiving for referrals, manually checking messages and downloading resumes is becoming challenging. To make the process smoother, please use the link below to fill out the referral form: https://lnkd.in/giF2fatt This will allow me to view everything in one place and refer you more efficiently! #softwareengineering #google #leetcode #codeforces #competitiveprogramming #coding #programming #referral #resume #faang #maang

1,159

31 Comments

Sharing the list of FREE resources I used to transition from TCS to Intuit 🚀 I have been asked many times about the resources I referred to for preparation. So, here it is.👇 𝐅𝐨𝐫 𝐃𝐒𝐀 👉 I used GeeksforGeeks to consistently solve problems everyday for 2-4 hours after work hours. 👉 Applying filters on the topic and top companies list helped. 👉 I did not have takeUforward during my time, but you have Raj Vikramaditya. So, you can refer to Striver’s SDE sheet for preparation. 𝐅𝐨𝐫 𝐒𝐲𝐬𝐭𝐞𝐦 𝐃𝐞𝐬𝐢𝐠𝐧 👉 System Design Interview book by Alex Xu 👉 Gaurav Sen’s playlist 𝐅𝐨𝐫 𝐉𝐚𝐯𝐚, 𝐒𝐩𝐫𝐢𝐧𝐠𝐁𝐨𝐨𝐭 👉 Wanna read? - javatpoint.com 👉 Binge watcher? - Navin Reddy’s Youtube channel - TELUSKO 𝐅𝐨𝐫 𝐜𝐨𝐫𝐞 𝐬𝐮𝐛𝐣𝐞𝐜𝐭𝐬 Sometimes, companies also ask questions on OOPS, SQL, OS and Networking. I had watched Ravindrababu Ravula sir’s videos during my college days and prepared notes. So, I used to revise them before every interview. And last but the most important thing - keep going. Stay consistent.. Lage raho, manzil mil hi jaegi.. 🙌 Do follow Akanksha Buchke for hirings, referrals, interview preparation content and please mention in the comments any other resource you found helpful. PS~ Join this group for all tech content (DSA, coding, System Design - interview preparation and resources) - https://lnkd.in/gUw9-G_u #interviewresources #interviewexperience #interviewpreparation #interviewtips #softwareengineer #softwaredeveloper #referral #intuit #jobswitch #networking #connections #reach #linkedin #linkedincommunity #akankshabuchke

300

47 Comments

My Google Interview Experience for SWE II role 💙 ❤️ 💛 💙 💚 ❤️ :  ⏰ The Timeline: 1️) Recruiter email on 15th April 2024 2️) Recruiter call on 18th April 2024 3️) Asked for some prep time (yes, you can do that!) 4️) Mock Interview on 10 May 2024 5️) 3 Coding rounds 6️) 1 Googleyness round 7️) 2 Team match rounds for the same team Based on my profile, the recruiter skipped the phone screen round and moved me directly to the onsite interviews. These onsite rounds are non-eliminatory, meaning I'll receive the results only after completing all of them. 💻 The Onsite Interviews: 1️⃣ Coding round 1: A topological sort problem with an alternative solution using color coding Difficulty: Medium-Hard - I let the interviewer know about both the approaches and  coded the first one but forgot to handle some edge cases. - I then resolved the problem and the interviewer appeared satisfied. - The interviewer then gave me a follow-up for the same question, to which I explained the approach and coded it as well. 2️⃣ Coding round 2: A problem involving Square Root Decomposition. Difficult: Hard -This problem was the most difficult problem among all my rounds. -I solved the problem in 30 mins; I had gotten confused with respect to the time remaining and hence coded it super-fast. -The interviewer then went on to ask me 5 follow-ups for this question. -I was able to solve 4 of them and code them as well. I got stuck in the last follow-up. I was really nervous about the result of this round but later on I got to know it had better feedback than my first round!!. 3️⃣ Coding round 3: Another Graph problem. Difficulty: Hard -This could be solved using a modification of Dijsktra’s algorithm. -The interviewer really checked my thought process and approach in this round and I had only 12 mins to code it up. Overall, it went well and the interviewer seemed very happy with the explanation and code. 4️⃣ Googleyness round: -I was asked 1 behavioural question with multiple follow up questions and different scenarios in each of the follow up. -I had prepared the top 50 questions asked in Interviews for this round. 💃 Result: -My interview feedback was very positive. I had a team match round 4 days after my Googlyness Round.  -I had a Fit Call with my to be manager and I liked the team so I conveyed the same to my recruiter. -Post that I had another fit call with another member of the same team, since this was a new team and they wanted me to meet the Team Lead as well. Once this was done I got my offer letter from Google within 5 days! 🤓 My Experience: The Google interview problems are very unique and they really force one to think out of the box. The whole process was very enriching for me and I had the best experience with the recruiters, interviewers and interview coordinators as well. They were very accommodating and always available!

3,773

118 Comments

Interesting take on her when it comes to entry-level resumes 👇 But what if the job description lists 7+ languages in the required and preferred qualifications section? Nowadays, especially in this market, just meeting the required qualifications isn't enough. You also wanna have a good number of the preferred qualifications down. And to get through ATS, the more keywords and phrases the better, which is what "tailoring" your resume is really about. So if engineers shouldn't stuff their resumes with keywords, then should job descriptions be less demanding then?

27

1 Comment

For the SDE-2 role, Low-Level Design (LLD) is one of the most critical interviews in most companies. I'm sharing some frequently asked LLD interview questions: 1. Parking Lot 2. Snake and Ladder 3. Vending/ATM Machine 4. Zomato/Swiggy 5. Appointment/Hotel Booking 6. Ticketing System (IRCTC/BookMyShow) 7. Splitwise 8. Elevator System 9. Cricbuzz 10. Inventory Management System 𝐏𝐫𝐞𝐫𝐞𝐪𝐮𝐢𝐬𝐢𝐭𝐞𝐬 𝐛𝐞𝐟𝐨𝐫𝐞 𝐭𝐚𝐜𝐤𝐥𝐢𝐧𝐠 𝐚𝐧𝐲 𝐩𝐫𝐨𝐛𝐥𝐞𝐦: 1. SOLID principles 2. Design Patterns 3. UML Diagrams 4. Understanding of any object-oriented language 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬: Concept && Coding by Shrayansh Jain Christopher Okhravi youtube channel Head First Design Patterns Book You can find me here and book a 𝐅𝐑𝐄𝐄 session to get started : https://lnkd.in/gX6nsWWN #LLD #SDE

31

I recently interviewed for the SDE-2 Backend position at CureFit, and here's a quick breakdown of my experience: Round 1: Online Assessment Platform: HackerEarth Duration: 1 hour 10 minutes Number of Questions: 2 (One Medium, One Hard) The test was focused on problem-solving skills, with questions that required a good understanding of data structures and algorithms. Round 2: DSA Round This was a coding-focused round where I was asked to solve two LeetCode Medium-Hard level questions. The interviewer was looking for optimal solutions as well as clarity in approach and code explanation. Round 3: Design Round This round had a mix of: One DSA Question: To test algorithmic thinking. One LLD Question: I was asked to design a RedBus-like application, covering key aspects of low-level design, such as class diagrams, relationships, and design patterns. Round 4: Hiring Manager Round This was more of a discussion-based round: The hiring manager explained the team structure and role expectations. Java Spring: I was asked a few conceptual and practical questions related to Java Spring. Project Discussion: I had to explain the architecture design of one of my past projects. The manager deep-dived into my project details and my approach to solving problems. Verdict I received 5-star ratings in all rounds. However, the salary offered was lower than my expectations, and I already had better offers in hand. If you're preparing for CureFit or have questions about the process, feel free to comment or DM me. 😊 #jobsearch #interviewexperience #curefit #dsa #systemdesign #techindustry #java

75

3 Comments

***Update: We will be filtering from the ones who have applied. Position can be considered as closed now**** I'm hiring for the following positions in my team. All of these are 0-1 (founding engineers) positions for a new vertical that we're building. Folks who have worked on scale are preferred. (Our current scale is around 3M rpm and expected to grow significantly over this year). 1. Full Stack engineer (Lead role) Experience: 4+ years (or should be able to justify less experience for the role) Tech stack: Reactjs, Nodejs, MySQL (but should be open to try new things) Should have worked on third-party app integration. 2. Intern Full stack (6 months): You come with the right mindset and work on full-stack (platform, front-end, backend, mobile). Build expertise while as you gain insights. You will be working with Shivam Munshi Harsh Rathi Utkarsh Arya Karan Varshney Arsh Thind Aditya Chowdhry Ankan Pal Sachin Gupta Note: If you are applying for internship, please include your highlights in the message along with resume. Please add your response here : NA #Software #Fullstack #Openings

371

98 Comments

Hi connections AngelOne is hiring for several roles . Some roles listed down. SDE-2 Backend SDE-3 Backend SDE 2 - Android SDET 1 Staff Engineer - Backend Frontend SDE2 Frontend SDE3 Data Scientist 3 SDE 3 - Android SDET 2 Frontend - Mobile & Web Please check the careers page Please contact me for a referral with your resume for an interested role. Format - Name - <Name> Role - <Role> Resume - <Tinyurl link of resume> Happy coding 🙂 Thanks #connections #coding #sde #engineering #data #frontend #backend #hiring

172

23 Comments

𝗔𝗺𝗮𝘇𝗼𝗻 𝗶𝘀 𝗛𝗶𝗿𝗶𝗻𝗴 🚀 Fill up your information below, so that I can refer to your preferred job opening at Amazon. You must not apply to this position of your own or else my referral will be invalid. Also make sure that you have not applied to any other job opening at Amazon in the last 6 months. If you have applied to any Amazon opening within last 6 months, the referral won't work. [Update] : No longer accepting responses. 𝑵𝒐𝒕𝒆.: 𝑪𝒉𝒆𝒄𝒌 𝒄𝒐𝒎𝒎𝒆𝒏𝒕 𝒇𝒐𝒓 𝒕𝒉𝒆 𝒓𝒆𝒔𝒐𝒖𝒓𝒄𝒆𝒔

106

6 Comments

Hello everyone 🙂 I have launched my page on Topmate, mainly because I love mentoring and interacting with people 😄 Right now, I am open to having 1:1 calls, having a brief chat session and taking mock interviews. This is mainly for fresher level SWE roles, and academics related discussions (Classes 9th to 12th) https://lnkd.in/gjp-74sD Do drop me a message in case you want to suggest more ways I can help or if the price seems high [though I have tried to keep it affordable]. I am open to feedback and will try to accommodate requests. Some suggestions to utilize time of both parties involved in the session: 1. For mock interviews, please have a decent level of preparation in DSA and computer fundamentals. Try preparing your introduction beforehand as well. 2. For chats, please have specific questions. I am open to giving quick review of resumes as well. 3. Over call, we can discuss specific as well as open ended questions.

40

2 Comments

Own your promo doc, part 2 out of 2 Part 2 is the story of writing my Senior Engineer to Principal Engineer promo (2013-2014). (Part 1, the story of writing my SDE-II to Senior Engineer promo, is at https://lnkd.in/gMHMzFR4) One thing I wanted to do differently was that the doc should be Forward-Looking (“here’s what I’m going to do” - proactive) rather than the standard “here’s what I did” (reactive). Amazon tends to follow a process called "Working Backwards" in a lot of docs - and I figured it would apply well to promos. I wrote the Forward Looking doc well before I thought I was ready. It didn’t just list the things I had accomplished, but the things I felt I could/should accomplish in the next 12 months. I then shared the doc with a selected group of Directors and Principals around me to seek feedback. The basic question was, “if this document was being discussed a year from now and everything in it was then true, would you be Inclined or Not Inclined? Does it ballpark describe the body of work of a Principal?” It was not a comfortable experiment: I certainly put myself out there and felt very vulnerable. The people I sought feedback from were also very direct and candid and challenged me in uncomfortable ways, but I knew they cared about my growth. Their advice helped me to be focused and deliberate on where I spent my time in the next year. When I felt the doc was good enough, I shared it with my manager. I didn’t get promoted the first time around, but I did get promoted six months after my first failed attempt. That was roughly a year after I initially wrote the doc. This is pretty standard for PE promos - if you get promoted the first time around chances are your manager waited too long! Years later, I was having coffee and catching up with the manager that promoted me to Principal. He said something curious: “You know, I was planning on promoting you, but your doc helped me do this six months earlier!” I had spent about 30 hours of my life writing, revising, incorporating feedback, and thinking about it. I don’t remember what kind of financial benefit getting promoted half a year earlier had for me specifically at the time, but let's use the following thought experiment: just using today’s public numbers from levelsfyi, Amazon L6 averages $405k, Amazon L7 averages 680k, so the difference is $275k/yr. Having L7 compensation six months earlier would mean an additional 138k. Given 30 hours of additional work, that’s an ROI of $5000/hr. I'd say that's a pretty decent ROI for that investment of time! (there were many other benefits to being promoted earlier, but that one is easy to quantify and articulate)

362

22 Comments

My UBER interview experience for SDE1 part-1: One of the coding problems I solved involved a shop scenario with manual cash registers. The cashier manually entered prices, leading to potential errors. My task was to compare the actual prices of products with the entered prices and count how many times mistakes occurred. For example-> Products: ['eggs', 'milk', 'cheese'] Correct Prices: [2.89, 3.29, 5.79] Sold Products: ['eggs', 'eggs', 'cheese', 'milk'] Entered Prices: [2.89, 2.99, 5.97, 3.29] The goal was to identify discrepancies between the entered and correct prices. part-2: logs to detect suspicious users based on their transaction activity. Each log entry recorded a money transfer between two users. The objective was to identify users involved in at least a specified number of transactions, either as a sender or recipient. For example, with logs like ["88 99 200", "88 99 300", "99 32 100", "12 12 15"] and a threshold of 2, users 88 and 99 were flagged for appearing at least twice. The output would be ['88', '99'], sorted in ascending order. part-3: (after shortlisting) Interview: You are given a grid where some cells are occupied by cars, and others are empty. Each car has a predefined path to follow, represented by a set of coordinates. Your task is to find the shortest path from a given start point to an endpoint while minimizing the number of collisions. A collision occurs when two or more cars attempt to occupy the same cell at the same time. You need to find the shortest path from the start to the end point that avoids as many collisions as possible. If multiple paths have the same length, choose the one with the least collisions. Output: Return the shortest path (as a list of coordinates) from the start to the end, while minimizing collisions. If no path exists, return an empty list. * Designing a low-level logging system for a large-scale distributed application. The system should efficiently record and manage logs generated by different components of the application. Logs can be of different levels (e.g., INFO, DEBUG, ERROR) and need to be written to different output sources (e.g., files, databases, external services). The logging system should allow flexibility when configuring log levels and destinations.

438

25 Comments

𝗙𝗿𝗼𝗺 𝗜𝗻𝗱𝗶𝗮 🇮🇳 𝘁𝗼 𝗜𝗻𝘁𝗲𝗿𝗻𝗮𝘁𝗶𝗼𝗻𝗮𝗹 🌏 : 𝗛𝗼𝘄 𝗦𝗪𝗘 𝗵𝗶𝗿𝗶𝗻𝗴 𝗽𝗿𝗼𝗰𝗲𝘀𝘀 𝗱𝗶𝗳𝗳𝗲𝗿𝘀 𝗮𝗰𝗿𝗼𝘀𝘀 𝗯𝗼𝗿𝗱𝗲𝗿𝘀 During my search for international SWE roles, I interviewed with over 15 global companies, including Amazon Luxembourg, Google Tokyo, and Hudson River Trading London. Along the way, I encountered unique challenges that highlighted key differences between the international and Indian hiring process: 𝗥𝗲𝗷𝗲𝗰𝘁𝗶𝗼𝗻 𝗥𝗮𝘁𝗲 ❌ : International roles can be tough to crack, especially due to local hiring preferences. For instance, I was in the final stages with Google Tokyo when my offer fell through because Japan closed its borders due to COVID. Visa sponsorship and relocation hurdles often lower your chances, especially for freshers. At each step, from resume screening to the team-matching phase, international candidates face stiffer odds, as companies want to avoid complexities. 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗗𝗶𝗳𝗳𝗶𝗰𝘂𝗹𝘁𝘆 👨‍💻 : There's a myth that international interviews are either much harder or easier than those in India. In my experience, the difficulty level is pretty consistent globally. For Google, the interview process is exactly the same, no matter where you apply. 𝗖𝘂𝗹𝘁𝘂𝗿𝗮𝗹 𝗙𝗶𝘁 🍣 : International roles might put a bigger emphasis on cultural fit. For example, my Amazon Luxembourg interview placed around 50% weightage on HR rounds, specifically on Amazon's leadership principles, unlike any other interview I'd gone through. While the technical skills were crucial, they were equally interested in how I aligned with their company values and if I could adapt to their work culture. 𝗖𝗼𝗺𝗽𝗲𝗻𝘀𝗮𝘁𝗶𝗼𝗻 & 𝗙𝗶𝗻𝗮𝗻𝗰𝗲𝘀 💸 : International packages often come with perks like relocation benefits, visa sponsorship, and housing allowances. For example, many companies offer services to help you find housing, which is a huge relief. While the salaries are higher than in India (you hear stories of X crore INR packages), it’s important to remember that living costs and taxes abroad are much higher too. I had to carefully evaluate my finances by considering the cost of living and taxes in the country before understanding how much I'd actually save. I’d love to hear your thoughts! Share your experiences and insights in the comments.

33

If you’re an SDE targetting Senior SDE Roles like SDE II, then prepare System Design well 🔥 Targeting such roles require you to have good hands-on experience with designing system. Save this guide and gain experience in Designing Scalable Systems 👇 Huge thanks to Bosscoder Academy for sharing this doc. Check here: https://bit.ly/4egIYHi This doc contains → 👉 HLD & LLD Conceps along with practice questions ✅ Save this doc and share it with your friends! #notes #systemdesign #collab #tech

648

45 Comments

🚀 Level Up Your Product Strategy & Dive into API Product Management! 🚀 As an SDE at Amazon, I've had the privilege of building APIs and wearing the hat of an API Product Manager blending technical expertise with strategic product management. To further enhance my skills, I've obtained the Product Strategy Micro-Certification from Product School, 🌟 huge thanks to the guidance of my amazing instructor Michelle Parsons, Chief Product Officer at Lex. This certification has equipped me with in-depth knowledge in: 👉 Crafting a Rock-Solid Product Strategy 👉 Market Analysis 👉 Customer Analytics 👉 Product Vision & Mission 👉 OKRs 👉 Roadmap 👉 Prioritization 👉 Communicating Product Strategy This comprehensive learning has equipped me with the tools to craft and execute effective product strategies that align with organizational goals and drive stakeholder alignment, I'm grateful for the opportunity to learn from the best. 📢 Although product management is widely discussed on LinkedIn, API Product Management is a niche that deserves more attention. Starting tomorrow, I’ll be sharing my learnings and insights on building APIs and managing API products. Follow the hashtag #APIPM for all the updates! P.S. Did I mention this course is currently FREE? For those interested in enhancing their product strategy skills, Enroll here and unlock your product strategy potential: https://lnkd.in/gPzUY8DF #Amazon #API #APIProductManagement #APIPM #APIStrategy #Certification #Growth #Learning #LearningJourney #PMschool #ProductDevelopment #ProductManagement #ProductSchool #ProductStrategy #ProfessionalGrowth #TechLeadership #careerdevelopment #productmanagement #productstrategy

16