<?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 Kapil Shanbhag on Medium]]></title>
        <description><![CDATA[Stories by Kapil Shanbhag on Medium]]></description>
        <link>https://medium.com/@programerkapilshanbhag?source=rss-69ae160e3e98------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vAn0W8koJLolKBCu83rc3Q@2x.jpeg</url>
            <title>Stories by Kapil Shanbhag on Medium</title>
            <link>https://medium.com/@programerkapilshanbhag?source=rss-69ae160e3e98------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:28:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@programerkapilshanbhag/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[Google Interview Experience – SWE L3.]]></title>
            <link>https://medium.com/@programerkapilshanbhag/google-interview-experience-swe-l3-7d6b23a984b6?source=rss-69ae160e3e98------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d6b23a984b6</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[data-structure-algorithm]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[interview-questions]]></category>
            <dc:creator><![CDATA[Kapil Shanbhag]]></dc:creator>
            <pubDate>Sat, 29 Mar 2025 08:31:49 GMT</pubDate>
            <atom:updated>2025-03-29T08:31:49.724Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi everyone, I recently interviewed at Google for the Software Engineer (L3) role. In this blog, I will be sharing details about the interview rounds, the questions asked, my learnings, and my preparation strategy. Before you scroll to the end to find the verdict, let me tell you right here — I got <strong>rejected.</strong> 🥲. So, let’s get started with the reading journey!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sLMsW2OsTvLU2eOpTo0-Tg.png" /></figure><h4>Recruiter Reach out — 24th Dec 2024</h4><p>The recruiter viewed my LinkedIn profile and reached out to me via email regarding Software Engineering job opportunities at Google. I replied, expressing my interest in the opportunities. The recruiter then asked me to share my resume and contact number to proceed with the next steps. After that, the recruiter scheduled a meeting to discuss the upcoming interview rounds.</p><h4>Recruiter Call — 3rd Jan 2025</h4><p>This round was mainly to discuss the available roles at Google and to understand my experience. The recruiter began by asking me to introduce myself, followed by questions about my previous work experience. I was also asked if I had worked on scalable systems. The recruiter then briefed me about the various teams and tech stacks they were hiring for. Additionally, she explained the interview process and what to expect in the upcoming rounds.</p><p>For the Software Engineer (L3) role at Google, the process starts with a Phone Screen round. If you clear it, you will move on to the next four onsite rounds, which are non-eliminatory. This means that even if you don’t perform well in one onsite round, you will still get the opportunity to attempt the remaining rounds. You won’t be eliminated midway!</p><p>After the call, the recruiter emailed me a list of Data Structures &amp; Algorithms (DSA) concepts to prepare for. The recruiter also asked me to share up to five preferred time slots for my Phone Screen round.</p><h4>Phone screen Round — 6th Feb 2025 | DSA — 45 mins.</h4><p>This round was initially scheduled for January 28th but had to be rescheduled due to my unavailability. The interview began with a brief introduction — both the interviewer and I exchanged greetings and introduced ourselves for about five minutes. After that, the interviewer presented me with a coding question related to Binary Search and Strings. It was a straightforward <strong>Binary Search</strong> problem, categorized as an <strong>Easy</strong> level. I explained my approach, and the interviewer asked me about the time complexity. I explained the complexity, and once she was satisfied with my explanation, she asked me to implement the solution. I wrote the code and then walked her through a dry run of the implementation. During the dry run, the Interviewer pointed out an edge case that my solution didn’t handle and asked how I would fix it. I gave it some thought but, unfortunately, couldn’t come up with a proper solution before time ran out. At the end of the round, I was given the chance to ask questions, which I did.</p><p><strong>Verdict: Hire</strong>.</p><p>A week later, I received a call from the recruiter regarding my interview. The feedback was positive! We then discussed the details of the next round. I was quite happy at this point because I had successfully cleared one round of the Google interview process! 😅 After that, I shared my availability for the onsite rounds over email, and the recruiter proceeded to schedule them.</p><h4>On-site round 1–4th Mar 2025 | DSA — 45 mins.</h4><p>The interviewer and I began by greeting each other and spent about five minutes introducing ourselves. After that, I was given a problem to solve. The question was based on simple linear iteration over Strings. However, the problem statement was quite lengthy and included some terms that were new to me. It took me around five minutes just to fully understand the question.</p><p>Once I understood it, I explained my approach to the interviewer and also discussed possible test cases, edge cases, and input-output constraints. My approach was accepted, and I proceeded to write the code. It took me around 10 minutes to complete the implementation.</p><p>After coding, we dry-ran the solution using the test cases and discussed the time and space complexities. By then, the time was up, and the round ended with a Q&amp;A session where I got a chance to ask my questions.</p><p><strong>Verdict: Lean Hire — Hire.</strong></p><p>I felt that I was pretty slow in the interview as I took more time to understand the question and explain the solution. There was no time left for the follow up at the end, cause of which I couldn&#39;t get a Hire to Strong hire.</p><h4>On-site round 2–5th Mar 2025 | DSA — 45 mins.</h4><p>I messed up badly in this round! This time, the problem was based on the Stack data structure.</p><p>Right from the start, I struggled to figure out the correct approach. I explained a solution to the interviewer, which I later realized was incorrect. However, before diving into the approach, I made sure to discuss possible test cases and edge cases. The interviewer seemed impressed by the clarifying questions I asked during this phase.</p><p>I then explained my approach, thinking it was correct at that moment, and discussed the time and space complexities. I proceeded to write the code but couldn’t complete it within the given time. Unfortunately, I also missed the chance to do a proper dry run and ask follow-up questions due to time constraints.</p><p>The round concluded with a short Q&amp;A session during the last five minutes.</p><p><strong>Verdict: No Hire</strong></p><p>I was very upset after this round as I couldn&#39;t perform well. This was my worst interview throughout my Google Interview. Later, after thinking about this question, I figured out that this was a simple stack question. But couldn&#39;t get this during the interview.</p><h4>On-site round 3–10th Mar 2025 | DSA — 45 mins.</h4><p>This round was initially scheduled for March 6th but had to be rescheduled due to the unavailability of the interviewer. This turned out to be the best interview I had in the entire process, and interestingly, the interviewer was based in India.</p><p>The first question was an array-based scheduling/queuing problem with a <strong>Medium</strong> difficulty level. I was able to understand the problem statement quickly. I wrote my own test cases, discussed a few edge cases and constraints, and then explained my approach. The interviewer was satisfied with my explanation.</p><p>I proceeded to write and complete the code and then did a dry run to validate the solution. After that, the interviewer asked a follow-up question related to the same problem, which could be solved using Binary Search. I explained the approach, and once the interviewer was satisfied with it, I wrote the pseudocode as well.</p><p>Towards the end, I was asked a second question based on Strings. I explained my approach and successfully coded the solution. We wrapped up the round with a Q&amp;A session before the interview ended.</p><p><strong>Verdict: Hire — Strong Hire.</strong></p><p>This was my best interview, and I could answer all of that. I felt that I had a slim chance of getting selected after this round and was very happy about it.</p><h4>On-site round 4–19th Mar 2025 | Googleyness — 45 mins.</h4><p>This interview was initially scheduled for March 7th, then rescheduled to March 13th, and finally took place on March 19th. Unlike the previous rounds, this was not a coding round. It was focused on general behavioral and leadership questions, based on my previous work experience and a few hypothetical scenarios. Here are the questions.</p><p>1) If you are working in a team for the project, while presenting that one presents it. What would you do?<br>2) If I had asked your manager about me, what would be the feedback from the Manager.<br>3) Explain about any school project where you initially planned some thing and at the end you executed some different thing.<br>4) Are you comfortable or happy working on projects where the priority changes constantly?</p><p>I answered all the questions pretty well, and the Interviewer seemed satisfied with my answers.</p><p><strong>Verdict: Hire.</strong></p><h4>Final Verdict — 25th March 2025</h4><p>I received a call from the recruiting team, and they informed me that I didn’t receive strong positive feedback and would <strong>not be</strong> moving forward in the process. I was quite disappointed, as I had a small hope that I might still have a chance. But unfortunately, I couldn’t make it — I was <strong>rejected</strong> 🥲.</p><p>The recruiter also mentioned that I wouldn’t be eligible to interview for the same role again for the next <strong>12 months</strong>.</p><h4>My Mistakes.</h4><ol><li><strong>Speed</strong> is important. I think I ignored the speed aspect. The interview lasts for 45 minutes. Of which, 5 mins goes for the introduction and the last 5 mins for the Q&amp;A. You are left with 35 minutes! To get a hire or strong hire verdict, you must solve the question and also follow ups in this 35 mins.</li><li>I messed up the interview schedule! The first two of my interviews were scheduled around 3 pm in the afternoon. Usually, I won&#39;t be able to think fast during the afternoon as I feel drowsy cause of lunch. If it was in the morning, maybe I could think about it and complete the coding faster.</li></ol><h4>Tips</h4><ol><li><strong>Keep up the pace</strong>. Think fast &amp; solve fast. Understand the question in 5 minutes. Analyse the test cases, edge cases &amp; constraints, and explain the approach in the next 5 mins. Code for the next 10 mins. Dry run and complexity analysis in the next 5 minutes. Now, you are left with 10 out of 35 minutes. Solve follow-ups in these 10 minutes.</li><li><strong>Communication</strong> is important. If you are not clear with questions, ask them. Sometimes, there will be open-ended questions to test your communication skills. Always <strong>think louder</strong> so that the interviewer knows what you are thinking.</li></ol><p>Will write a <strong>separate blog</strong> on my preparation, highlighting the questions &amp; concepts I prepared for the interview.</p><p>Thanks for reading it out. I hope it helps you in one way or another. All the best to those who are interviewing.</p><h3>For anything, Connect with me: <a href="https://www.linkedin.com/in/kapil-shanbhag/">https://www.linkedin.com/in/kapil-shanbhag</a></h3><h3>Thank You!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d6b23a984b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Proxy in System Design]]></title>
            <link>https://medium.com/@programerkapilshanbhag/proxy-in-system-design-efef2ba0fb91?source=rss-69ae160e3e98------2</link>
            <guid isPermaLink="false">https://medium.com/p/efef2ba0fb91</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[system-design-concepts]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[system-design-interview]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Kapil Shanbhag]]></dc:creator>
            <pubDate>Fri, 20 Sep 2024 13:03:28 GMT</pubDate>
            <atom:updated>2024-09-20T13:03:28.191Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi everyone! In this blog, I will be discussing Proxy, which is an important component in the system design. Then, we will be discussing about 2 types of proxies in detail. We will also discuss what makes proxies different from load balancers. Let&#39;s Start!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RgV8KAgnzq1WCRGcYpVmXQ.png" /><figcaption>Thumbnail Image</figcaption></figure><h4>What is Proxy?</h4><p>A proxy is a server or component that sits between the client and the server. It is used to decouple the client from the server while adding additional functionalities such as authentication, caching, performance optimization, and security</p><p>Proxy mainly intercepts the network call &amp; redirects it. Proxy is a must required for the system we design. Most of the websites we use in today&#39;s world have proxies. Whatever request we make to the server, it&#39;s intercepted by the proxy.</p><p>There are 2 types of Proxy.<br>1) Forward Proxy.<br>2) Reverse Proxy.</p><h4>Forward Proxy</h4><p>A forward proxy is a proxy placed in front of clients. When a client makes a request to a server, the request is first routed to the forward proxy, which then forwards the request to the intended server.</p><p><strong>Why use a Forward Proxy?</strong><br>• It protects the client&#39;s data &amp; provides the anonimosity.<br>• It restricts some contents that might not be safe.<br>• It can optimize or change the request made by the client.</p><p><strong>Disadvantages</strong><br>• No privacy for the client.<br>• Can add extra latency for the client to load the data.</p><h4>Reverse Proxy</h4><p>A reverse proxy is a proxy placed in front of a server or a group of servers. It intercepts requests from clients and forwards them to the appropriate server, ensuring that the servers are not accessed directly.</p><p>Why use reverse Proxy?<br>• It ensures that our servers are secure &amp; out of threat.<br>• It also caches some mostly requested data.<br>• It also acts as a load balancer to the server.</p><p>Disadvantages<br>• It increases the complexity of the system.<br>• It can add additional latency for our request.<br>• There can be a single point of failure. If the proxy fails, the client might not be able to communicate with the server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*HztQZlu1bZ6AuZv9DMBfDw.png" /><figcaption>Figure 1</figcaption></figure><p>Now, let’s understand how both Forward Proxy and Reverse Proxy work, using the above image as a reference. When a client (on the left side) makes a request to the server, the request is first intercepted by the Forward Proxy. The Forward Proxy then initiates the request on behalf of the client to the Internet. This request is received by the Reverse Proxy, which forwards it to the appropriate server. Once the server responds, the Reverse Proxy sends the response back to the requester (in this case, the Forward Proxy). Finally, the Forward Proxy delivers the response to the client.</p><h4>Load Balancer vs Reverse Proxy</h4><p>Let&#39;s understand the difference between the load balancer &amp; reverse proxy. <strong>What&#39;s the difference</strong>? It&#39;s the <strong>intent</strong>. Load Balancer intends to distribute load among multiple servers. Whereas a proxy, along with load balancing provides additional functionalities like caching, authentication, security, etc. Load Balancer might not be useful when there is only one server node but Proxy is useful even if there is one server node</p><h4>Reference</h4><ul><li><a href="https://www.enjoyalgorithms.com/blog/proxies-in-system-design">https://www.enjoyalgorithms.com/blog/proxies-in-system-design</a></li><li><a href="https://dev.to/karanpratapsingh/system-design-proxy">https://dev.to/karanpratapsingh/system-design-proxy</a></li></ul><h3>For anything, Connect with me: <a href="https://www.linkedin.com/in/kapil-shanbhag/">https://www.linkedin.com/in/kapil-shanbhag</a></h3><h3>Thank You!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efef2ba0fb91" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tech Interview Tips for SDEs. ‍]]></title>
            <link>https://medium.com/@programerkapilshanbhag/tech-interview-tips-for-sdes-bda2d5f2b9f7?source=rss-69ae160e3e98------2</link>
            <guid isPermaLink="false">https://medium.com/p/bda2d5f2b9f7</guid>
            <category><![CDATA[interview-questions]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[interview-preparation]]></category>
            <category><![CDATA[sde-interview]]></category>
            <category><![CDATA[campus-placements]]></category>
            <dc:creator><![CDATA[Kapil Shanbhag]]></dc:creator>
            <pubDate>Wed, 28 Aug 2024 18:26:26 GMT</pubDate>
            <atom:updated>2024-08-28T18:26:26.624Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi everyone! For a while now, I’ve wanted to write a blog on this topic. I wanted to bring out some points I experienced during my interviews. Note that I won&#39;t be discussing anything about coding or technical things. Maybe I can make some more blogs for those in the future 😅. Let&#39;s Start!</p><p>But What is my Source of Reference?<br>It’s me! I have interviewed with more than 10+ companies in the last 3–4 years. It includes service-based companies like TCS, Cognizant, etc. Startups like Redbus, Rapido, Ola, Zomato, Zeta, Meesho, Licious, etc. MNCs like Grab, Western Digital, Walmart, etc. So, I will be explaining the experiences I had in these interviews here in this blog.</p><p>Here we go!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-jyxpvQkQW30a6hoLw9OJg.png" /></figure><ol><li><strong>It’s okay not to know some things.<br></strong>One of the major misconceptions we have about the interviews is that we must know everything. Well, you must indeed be great in knowledge. But you need not know 100%. You can tell the interviewer a No for the questions you don&#39;t have an answer. There were instances where I couldn&#39;t answer every question, but I was still selected for the next round.</li><li><strong>Watch your words.</strong><br>In one of my interviews, I remember that one of my sentences changed the mood of the whole interview. I said a sentence (not abusive though😂) which hurt the interviewer&#39;s ego. Thereafter, the interviews started asking me questions on some random, difficult iOS topics that I had never heard of! I suspect he might have even Googled those topics himself 😢. So, be careful of your words and sentences. Your one sentence can mess up everything.</li><li><strong>Be firm &amp; Confident.<br></strong>Always be firm and confident. Make sure you are certain about the answers you give to the interviewer. If you aren&#39;t sure about the question, ask for clarification. Even if you are not confident in your answer, state it without hesitation. Being Dicey or unsure about your answer or solution can negatively impact your interview.</li><li><strong>The interview Schedule does matter.<br></strong>Yes, the timing of your interview can impact your chances of getting selected. I have personally experienced this! I had an interview scheduled on a Friday at 5 pm. The interviewer had worked all day and all week, which made him less patient and more eager to leave the office. The result? I got rejected in the interview likely cause of his tiredness (though there were other reasons as well). So, always try to schedule your interview early in the afternoon or maybe in the morning. Never schedule an interview for Friday evening 😂.</li><li><strong>There is always a Luck factor.<br></strong>Yes, you might answer all the questions correctly but still get rejected in the interview. It could be because other candidates asked for less compensation than you, or for many other reasons. The luck factor always exists in all the interviews you give. So be prepared for it.</li></ol><p>Here are some important points below, that I felt during my <strong>Campus Placements</strong>.</p><ol><li><strong>Your Resume is your question Paper.<br></strong>During my campus placements, I would wonder what I might be asked in the technical interview. Yes, DSA would be obvious, but what else besides DSA? Concepts from DBMS, OS, CN, and OOP, of course. Again, what else? But what else? It’s simple — the skills you’ve mentioned on your resume. The interviewer will review your resume and ask questions about the skills you’ve listed. So make sure you have tailored your resume well; it&#39;s your question paper for the interview.</li><li><strong>How you answer &gt; How much you answer<br></strong>Does this mean you don’t need to answer many questions? No. You have to answer the majority of the questions. You can also politely say no to the question you don&#39;t know. But in campus interviews, the Interviewer focuses on your knowledge as well as the depth &amp; clarity of that knowledge. The interviewer always checks your confidence in the answer you are saying. He checks your way of communicating, Understanding of concepts, etc. So along with reading the concepts, always be prepared with the right approach to explain those concepts to the interviewer.</li><li><strong>Check your interviewers.<br></strong>Wait! Should I stalk my interviewers 😳? I think Yes. If you get to know who your interviewer is, it&#39;s a green flag for you! You can anticipate the kinds of questions you might be asked. But how? The answer is simple. Search for your interviewer on Linked In. Go to his profile &amp; check his skills. If his skills match those you mentioned in your resume, you will get those questions in your tech round.</li></ol><p>I think these are some of the key points I found important during my interviews. If there are any other points I have missed, will cover them in some other blogs or may be updated in the comments. Thank you for the read, Hope this will help you to ace your interview. All the best!</p><h3>For anything, Connect with me: <a href="https://www.linkedin.com/in/kapil-shanbhag/">https://www.linkedin.com/in/kapil-shanbhag</a></h3><h3>Thank You!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bda2d5f2b9f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Walmart Software Engineer III — IOS (IN3) Interview Experience]]></title>
            <link>https://medium.com/@programerkapilshanbhag/walmart-software-engineer-iii-ios-in3-interview-experience-b4bf81cdbde5?source=rss-69ae160e3e98------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4bf81cdbde5</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[data-structure-algorithm]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[interview-experience]]></category>
            <category><![CDATA[walmart]]></category>
            <dc:creator><![CDATA[Kapil Shanbhag]]></dc:creator>
            <pubDate>Sun, 19 May 2024 10:38:06 GMT</pubDate>
            <atom:updated>2024-06-09T09:29:15.023Z</atom:updated>
            <content:encoded><![CDATA[<h3>Walmart Software Engineer III — IOS (IN3) Interview Experience</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A8puDkEmcIvMq-AOaTTgNg.png" /></figure><p>Hi all, Recently I interviewed at Walmart Global Tech for the position of Software Engineer III — IOS. There were overall <strong>3</strong> rounds of interviews, all were <strong>tech interviews </strong>scheduled on the <strong>same day</strong>. Will tell you about the overall interview experience in detail.</p><h4>How did I apply?</h4><p>The recruiter contacted me on <strong>Linked In</strong> Regarding the open position in the company. I was interested in the opportunity and replied to the recruiter that I was interested in the position. Then the interview was scheduled 5 days later.</p><h3>Interview Rounds.</h3><h4>Round 1: Data Structures And Algorithms Round.</h4><p>This Round was conducted by the Software Engineer at Walmart. The interviewer first went on with his introduction and then asked me about my introduction. I introduced myself and then he directly jumped to the interview question. The first question was a leetcode easy question. I explained the approach with O(n²) time complexity. Then I explained my approach with O(n) time complexity which he was convinced and was asked to code. Later, the interviewer asked me the second question which was also a leetcode easy question. I explained the approach with O(n²) time complexity and then O(n) complexity and coded it. The recruiter was convinced by my approach as it could clear all test cases. Then the recruiter came with additional requirements for the given problem. I told the Interviewer that I would use min heap. He asked me to write a code but couldn&#39;t do it because of time constraints.</p><p>The interview lasted for <strong>60 mins</strong>. Overall the feedback was positive and I received a call from a recruiter for the second round.</p><h4>Round 2: Swift/iOS Round</h4><p>This Round was also conducted by the Software Engineer at Walmart. The interviewer first went on with his introduction and then asked me about my introduction. I introduced myself and then directly we jumped to the interview question. The questions were.</p><ol><li>Struct vs Class.</li><li>Protocol: Delegations, Skip or ignore a method from protocol.</li><li>Closures: Escaping vs non-escaping closures.</li><li>ARC: Weak, unowned, strong references.</li><li>Main thread and Background Threads.</li><li>MVVM vs MVC architecture.</li><li>Singleton Classes.</li><li>Generics in Swift.</li><li>Open vs Public access control.</li><li>Application and View lifecycle in iOS.</li></ol><p>I could answer around 95% of the questions. The interview lasted for <strong>60 minutes</strong>. Overall the feedback was positive and I got a call from the recruiter for the next round.</p><h4>Round 3: Hiring Manager Round</h4><p>This round was conducted by the Senior Engineering Manager at Walmart. He was from the Android development domain. The Interviewer introduced himself and then he asked me to introduce myself. I introduced myself and then he directly went up to questions. The questions were.</p><ol><li>My reason for switching?</li><li>How would I ensure that the iOS app is performing well?</li><li>My contribution to my previous organization.</li><li>2 bad things about my current organization.</li><li>Why Native Apps Are Better than Hybrid?</li></ol><p>Then he asked me if I had any questions. And I asked him some questions about the company culture, App architecture, etc. The interview lasted for around <strong>45 minutes</strong>.</p><p>Overall, the round went pretty well. However, I felt that I messed up some things in the interview and was not pretty sure about some of the things I was answering. I didn&#39;t hear back anything from the recruiter after this round.</p><p>So that&#39;s about my interview experience. The difficulty level I would rate as <strong>3</strong> out of 5. I am yet to receive further updates from them.</p><h3>Conclusion and Takeaways</h3><ul><li>For the iOS round, Must know everything from the Swift, and Apple documentation.</li><li>For the DSA round, Be prepared with leet code easy, medium questions.</li><li>Always be very well prepared for the Hiring Manager Round. Be ready with your convincing answers and always be confident.</li></ul><h4>For anything, Connect with me: <a href="https://www.linkedin.com/in/kapil-shanbhag/">https://www.linkedin.com/in/kapil-shanbhag</a></h4><h4>Thank You!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4bf81cdbde5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CAP Theorem]]></title>
            <link>https://medium.com/@programerkapilshanbhag/cap-theorem-be1168f02092?source=rss-69ae160e3e98------2</link>
            <guid isPermaLink="false">https://medium.com/p/be1168f02092</guid>
            <category><![CDATA[system-design-concepts]]></category>
            <category><![CDATA[cap-theorem]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[system-design-interview]]></category>
            <dc:creator><![CDATA[Kapil Shanbhag]]></dc:creator>
            <pubDate>Wed, 14 Feb 2024 13:08:03 GMT</pubDate>
            <atom:updated>2024-02-14T13:08:03.327Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, I will be explaining to you what the CAP theorem states and why we have to understand it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t6TzH2qFwY7NPJWXNKx9Lw.jpeg" /><figcaption>Figure-1</figcaption></figure><h4>What is the CAP Theorem?</h4><p>CAP theorem states that for a distributed system, you can&#39;t expect a system to have Consistency, Availability, and Partition Tolerance all the three simultaneously.</p><p>A <strong>distributed system</strong> is a collection of multiple computers or nodes that work together to form a single computer for the end users. In figure-1, A, B, C &amp; D are different computer nodes that form into a single big unit of computer.</p><p>Now let&#39;s understand What Consistency, Availability &amp; Fault Tolerance are.</p><ol><li><strong>Consistency</strong><br>Consistency defines that all nodes in our distributed system must have the same data simultaneously. Irrespective of the node selected by the user, it should always provide the same data every time. If the user performs the write operation in one of the nodes, it must be updated in every node.</li><li><strong>Availability</strong><br>Availability refers to the ability of the system to be available all the time. Even if some nodes are not operational, our system should be available. Our system must ensure that it responds to the user every time there is a request.</li><li><strong>Partition Tolerance</strong><br>Partition Tolerance refers to the ability of the system to handle the communication failure between nodes. If the nodes in our system cannot communicate with each other, then our system must be able to handle itself.</li></ol><p>I understand that you might not be able to completely understand these definitions from above. You will understand it once you read the below part!</p><h4><strong>Let&#39;s prove the CAP Theorem!</strong></h4><p>Now let&#39;s jump into the important part of proving and understanding the CAP theorem in depth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*liTdJGBdVKcIFSTCj3a03Q.jpeg" /><figcaption>Figure-2</figcaption></figure><p>Let&#39;s say that I have a bank called “Kaps” bank. I have a group of computers/servers(A and B in this case) nodes to store the balance of the users. As a user I interact with the bank system and the bank system operates based on user interaction. The server nodes are connected to each other so that the balance is updated in real time whenever the user withdraws money.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*URgOra4cX-X8-SogmrfohQ.jpeg" /><figcaption>Figure-3</figcaption></figure><p>Now assume there has been a communication failure between nodes A and B. The User has made a withdrawal request of ₹50. Node A has performed the request and the balance has been deducted from Node A. Since there is a communication failure between Node A and B, the balance is not updated in Node B. This will lead to inconsistency in the data &amp; I the owner of Kaps Bank will go bankrupt 😢.</p><p>Our system can let users withdraw money even if the communication between nodes is damaged, this aspect is called <strong>Partition Intolerance</strong> of the system. Our system is always available to users irrespective of uncertainty, this aspect is called as <strong>Availability</strong> of the system. Having the same balance in all the systems is called as <strong>Consistency</strong> of the system.</p><p>What has happened here? To maintain the Partition Tolerance and Availability we are messing up the consistency of the data. Different balances will be stored in the different machines. <strong>This is what the CAP theorem says</strong>. We will have to <strong>sacrifice one among these 3</strong> for our distributed system.</p><p><strong>What&#39;s the solution? </strong><br>I as an owner of Kaps Bank have to make sure that there is consistency in the balance stored on each server. So wherever there is communication failure, I have to let my system down and block all the withdrawal requests from the user. There might be other great solutions but this solution is in the context of the CAP Theorem.</p><h4>Why CAP Theorem?</h4><p>After understanding the CAP theorem, we know that we can&#39;t achieve all 3 factors at the same time. So we have to decide which factor out of the 3 you can let go or sacrifice. You can do it based on the data store, functionality of the system, etc. For the above example the Bank case I may let go of the Availability factor but I can&#39;t let go of the Consistency factor. In another example like a social media platform, I can let go of the consistency factor as it doesn&#39;t matter much to me, and focus on the availability of my platform.</p><h4>Reference</h4><ol><li><a href="https://www.educative.io/blog/what-is-cap-theorem">https://www.educative.io/blog/what-is-cap-theorem</a></li><li><a href="https://www.youtube.com/watch?v=BHqjEjzAicA">https://www.youtube.com/watch?v=BHqjEjzAicA</a></li></ol><h4>For anything, Connect with me: <a href="https://www.linkedin.com/in/kapil-shanbhag/">https://www.linkedin.com/in/kapil-shanbhag</a></h4><h3>Thank You!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be1168f02092" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Topological Sorting in Swift]]></title>
            <link>https://medium.com/@programerkapilshanbhag/topological-sorting-in-swift-c82d3e9c6aa2?source=rss-69ae160e3e98------2</link>
            <guid isPermaLink="false">https://medium.com/p/c82d3e9c6aa2</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[data-structures]]></category>
            <category><![CDATA[algorithms]]></category>
            <category><![CDATA[topological-sort]]></category>
            <dc:creator><![CDATA[Kapil Shanbhag]]></dc:creator>
            <pubDate>Mon, 15 Jan 2024 01:29:27 GMT</pubDate>
            <atom:updated>2024-01-15T01:29:27.346Z</atom:updated>
            <content:encoded><![CDATA[<p>Topological Sorting is the Linear ordering of every node in <strong>Directed Acyclic Graph(DAG)</strong> such that for every edge from vertex <strong>u-&gt; v</strong>,<strong> u </strong>comes <strong>before</strong> <strong>v</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OQjbhKC8QPs-Um-5rpAMAw.png" /><figcaption>Directed Cyclic Graph</figcaption></figure><p>The above graph would be the DAG we would be working for top sort.</p><p>So the top sort will be<br>[1, 2, 4, 3, 5]<br>or<br>[1, 2, 3, 5, 4]</p><p>The edges are 1-&gt;2, 1-&gt;4, 2-&gt;4, 2-&gt;5, 2-&gt;3, 3-&gt;5<br>So Let&#39;s verify in [1, 2, 3, 5, 4] and [1, 2, 3, 5, 4]<br>For 1-&gt;2, does 1 come before 2 in top sort? ✅<br>For 1-&gt;4, does 1 come before 4 in top sort? ✅<br>For 2-&gt;4, does 2 come before 4 in top sort? ✅<br>For 2-&gt;5, does 2 come before 5 in top sort? ✅<br>For 2-&gt;3, does 2 come before 3 in top sort? ✅<br>For 3-&gt;5, does 3 come before 5 in top sort? ✅<br>So, [1, 2, 3, 5, 4] and [1, 2, 3, 5, 4] can be the top sort of the above DAG.</p><p><strong>Note:</strong> [1, 2, 4, 5, 3] ❌ will not be a top sort because there is an edge from 3-&gt;5 but in our top sort 5 appears before 3.</p><h3>Why Topological Sorting?</h3><p>Top Sort can be used in multiple things like Task Scheduling, Dependency Resolution, Network Routing, etc.</p><h3><strong>Algorithm</strong></h3><p>func getDFS(node: Int) {<br> 1) If the node is visited {return} else mark node is visited.<br> 2) Call the DFS for the vertices connected to the current node.<br> 3) Push the current node in the stack at the end.<br>}</p><ol><li>For every element in the adjacency list, call DFS.<br>for i in adjList {<br> getDFS(node: i)<br>}</li><li>Pop the elements from the stack and add them to an Array or Linear Data. It will give the top sort for the DAG.</li></ol><h3><strong>Code</strong></h3><pre>class Stack {<br>    private var stack: [Int] = []<br>    private var count = 0<br><br>    func push(_ n: Int) {<br>        stack.append(n)<br>        count += 1<br>    }<br><br>    func pop() {<br>        stack.removeLast()<br>        count -= 1<br>    }<br><br>    func getTop() -&gt; Int? {<br>        if stack.isEmpty {<br>            return nil<br>        }<br>        return stack[count - 1]<br>    }<br>    func isEmpty() -&gt; Bool {count == 0 ? true : false}<br>}<br><br>class Graph {<br><br>    var adjList: [Int : [Int]] = [:]<br>    var topSort: [Int] = []<br>    var isVisited: [Int : Bool] = [:]<br>    var stack: Stack = Stack()<br><br>    func addEdge(_ u: Int, _ v: Int) {<br>        if let _ = adjList[u] {<br>            adjList[u]?.append(v)<br>        }<br>        else {<br>            adjList[u] = [v]<br>        }<br>    }<br><br>    func getTopSort() {<br>        isVisited = [:]<br>        for (i, _) in adjList {<br>            getDFS(i)  // Call DFS.<br>        }<br><br>        while !stack.isEmpty() {<br>            topSort.append(stack.getTop() ?? -1)<br>            stack.pop()<br>        }<br><br>        print(topSort) // Print the top sort.<br>    }<br>    func getDFS(_ node: Int) {<br>        if isVisited[node] == true {<br>            return  // Return if visited.<br>        }<br>        isVisited[node] = true  // Mark as Visited.<br><br>        for i in adjList[node] ?? [] {<br>            getDFS(i) // Call DFS for the vertices connected to node.<br>        }<br>        stack.push(node) // Push node in stack.<br>    }<br>}<br><br>let g = Graph()<br>g.addEdge(1,2)<br>g.addEdge(1,4)<br>g.addEdge(2,4)<br>g.addEdge(2,3)<br>g.addEdge(2,5)<br>g.addEdge(3,5)<br>g.getTopSort()</pre><h3>Reference:</h3><ol><li><a href="https://www.youtube.com/watch?v=5lZ0iJMrUMk">https://www.youtube.com/watch?v=5lZ0iJMrUMk</a></li><li><a href="https://www.geeksforgeeks.org/topological-sorting/">https://www.geeksforgeeks.org/topological-sorting/</a></li></ol><h4>For anything, Connect with me: <a href="https://www.linkedin.com/in/kapil-shanbhag/">https://www.linkedin.com/in/kapil-shanbhag</a></h4><h3>Thank You!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c82d3e9c6aa2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Content Delivery Network]]></title>
            <link>https://medium.com/@programerkapilshanbhag/content-delivery-network-317364c849a1?source=rss-69ae160e3e98------2</link>
            <guid isPermaLink="false">https://medium.com/p/317364c849a1</guid>
            <category><![CDATA[content]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[system-design-interview]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[system-design-concepts]]></category>
            <dc:creator><![CDATA[Kapil Shanbhag]]></dc:creator>
            <pubDate>Thu, 30 Nov 2023 13:26:19 GMT</pubDate>
            <atom:updated>2023-11-30T13:26:19.169Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, I will be writing about the Content Delivery Network. Assume that you are running a website called “kaps.com”. Your headquarters is in Bengaluru. And you have users worldwide. You have a worldwide user base who are situated on multiple continents. Now a user from the US will open your website and he will be served from the servers that we have located in Bengaluru i.e in our headquarters. No matter where from the world any user opens your website, the contents will be served from Bengaluru only. Now here the main issue comes! The content has to travel from Bengaluru across the land and oceans to users from other continents. This will add a delay in the loading of content for users. This issue is solved by using the Content Delivery Network (CDN).</p><h4>What is CDN?</h4><p><strong>CDN is a geographically distributed group of servers that work together to provide fast delivery of internet content. </strong>Generally, static files such as HTML/CSS/JS files, Images, and videos are served from CDN.</p><h4>How does CDN work?</h4><p>In CDN 3 servers come into the picture.<br><strong>1) Origin Server</strong>: The Origin Server is the main server which is responsible for storing the original version of the content. It serves the content to the edge servers present globally.<br><strong>2) Edge Server:</strong> An Edge server is the server with which the user interacts with. It stores the cached version of the content received from the origin server and also provides it to the client or users. Edge servers are distributed globally.<br><strong>3) DNS Server:</strong> The DNS server is responsible for giving the appropriate IP Address of the edge server to the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8-IIPjeDA9YCchojVm_ptw.jpeg" /></figure><p>Being a System Designer in kaps.com. I will set up an origin server in my headquarters i.e. Bengaluru. Then I will keep edge servers in different locations throughout the world. Whenever a user from any part of the world requests the content, he will be served from the node server present geographically near to him.<br>Here are the steps on how the content will be served.</p><ul><li>When a user requests a content. The DNS server will provide the IP Address of the corresponding edge server.</li><li>The User then makes a request to that particular edge server.</li><li>If the requested content is present in the edge server, the content will be served to the user.</li><li>Otherwise, the edge server requests the origin server for the content. The Origin server will provide the content to the edge server.</li><li>The Edge server then caches the content locally and simultaneously provides the content to the user.</li></ul><h4><strong>Types Of CDN</strong></h4><ol><li><strong>Push CDN</strong><br>In Push CDN the contents are pushed from the origin server to the edge server before the user makes the request to the edge server. Whenever there is a change in the content, it is the duty of an origin server to push it to the edge server. If it is not pushed then a user will get the stale or older version of content.</li><li><strong>Pull CDN</strong><br>In Pull CDN the contents are cached based on the request made by the user. If the content requested by the visitor is present in the edge server it will be served. Otherwise, the content is fetched from the origin server, cached locally, and then served to the client.</li></ol><h4><strong>Why use CDN?</strong></h4><ol><li><strong>Increase the content availability</strong>: Our content is available throughout the world. Even if one edge server fails it can be substituted by another edge server or origin server.</li><li><strong>Reduce the Latency and load time</strong>: Our content can be stored from the nearby edge server which reduces the traveling time of content and thus reduces the loading time for the content.</li><li><strong>Load Balancing</strong>: Edge servers takes up much load from the origin server to itself, making it easy for an origin server.</li></ol><h4>Disadvantages of CDN.</h4><ul><li><strong>Extra Charge and Memory</strong> for storing the content in each and every node server.</li><li>Every country will have a <strong>restriction on the content</strong> that we are supposed to store. So, we have to abide by the law of that country while storing the data.</li></ul><h4>References</h4><ol><li><a href="https://dev.to/karanpratapsingh/system-design-content-delivery-network-cdn-bof">https://dev.to/karanpratapsingh/system-design-content-delivery-network-cdn-bof</a></li><li><a href="https://www.akamai.com/glossary/what-is-a-cdn">https://www.akamai.com/glossary/what-is-a-cdn</a></li><li><a href="https://www.cloudflare.com/learning/cdn/what-is-a-cdn/">https://www.cloudflare.com/learning/cdn/what-is-a-cdn/</a></li></ol><h4>Thanks &amp; Regards,<br>Kapil Shanbhag.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=317364c849a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Redbus Interview Experience]]></title>
            <link>https://medium.com/@programerkapilshanbhag/my-redbus-interview-experience-a88fc0bf241d?source=rss-69ae160e3e98------2</link>
            <guid isPermaLink="false">https://medium.com/p/a88fc0bf241d</guid>
            <category><![CDATA[dsa-training]]></category>
            <category><![CDATA[interview-experience]]></category>
            <category><![CDATA[campus-placements]]></category>
            <dc:creator><![CDATA[Kapil Shanbhag]]></dc:creator>
            <pubDate>Wed, 10 May 2023 04:47:49 GMT</pubDate>
            <atom:updated>2023-05-10T04:47:49.394Z</atom:updated>
            <content:encoded><![CDATA[<p>Interview type: On-Campus.<br>Role Offered: Software Engineer.<br>CTC Offered: 10 LPA.</p><p><strong>Total Rounds — 5</strong></p><p><strong>Round 1: Aptitude and Coding Test<br></strong>The first round was conducted on the Hacker Earth platform. It had some quantitative MCQ questions, verbal ability questions and some technical aptitude questions from C/C++, Java, DBMS, OOPS, CN etc. Next, it had 3 coding questions which were like leet code easy questions. I got the result on the same day and I was said that the interview would be conducted on the next day.</p><p>On the next day, we had a talk with the CTO and the HR lead about the company and its culture. They also had a Q&amp;A session where they would answer our questions.</p><p><strong>Round 2: Technical Interview<br></strong>This interview was scheduled at 10:30 pm on Day 2. This round was conducted by the Engineer/ Manager of Redbus. The interviewer greeted me and said to introduce myself. I introduced myself and then he told me to explain my projects. Then he went on asking questions on DBMS subjects like joins, and Normalization. Then he went with the OOPS concepts like the 4 Pillars of OOPS. Then he went to DSA and asked me about linked lists, doubly linked lists, and also the application. Then he asked about stack and he asked how can I implement the browser using linked list and stack. It went well and I could answer all the questions. Then he went with a puzzle-type question. Given we have a square inside a circle if the radius is r what would be the side of the square? I could solve it and we were done with the round. The interview was around 45 mins long.</p><p><strong>Round 3: Technical Interview<br></strong>I got a call from the recruiter that I was selected for the Next Round and it was scheduled at 2:30 pm. This round had 2 interviewers both were Engineers or Managers. The interviewer greeted me and told me to introduce myself. Then she asked me to explain my projects and to show a demo of them if I have any. I showed the screen recording of my projects. Then she gave me a coding question that I had to solve. The question was that there is a list of the names in the array and I have to print it in alphabetic order. I could solve it and Interviewer was satisfied with my solution whereas the other interviewer expected optimization. Then the interviewer asked a question about the skills mentioned in the resume. She asked me about React, MongoDB, etc. Then the Second interviewer asked questions about Java and MongoDB. The interview went for 1 hr approx. This round went a bit well and I was disappointed that I could not answer some of the questions asked by them.</p><p><strong>Round 4: Direction discussion<br></strong>I cleared around 3 and got the mail about Round 4. It was scheduled for 4:30. It was conducted by the director at Redbus. The interviewer greeted me then he told me to introduce myself. I introduced myself and he told me to explain the projects. I explained the projects and then he asked if I had any demo of the projects. I showed him the GitHub repository of the project. I had embedded the link in my resume. Then the Interviewer gave me the coding question. The question was to rotate the array clockwise. I could solve it and he was satisfied with the solution. It was taken for 20 mins.</p><p><strong>Round 5: Interview with CTO<br></strong>I got selected for Round 4 and the last interview was with CTO Anoop Menon and Tech and HR lead Srijit Sarkar. I got the mail about the interview and it was scheduled for 6:30 pm. At First Anoop and Srijit greeted me and asked for my introduction and I introduced myself. Then he said to me that he would go with the general HR question. He asked me about my college, Hometown, Hobbies, etc. He asked me about the challenges I faced and also my projects. It was a normal HR interview and I was confident throughout. At the end of the interview, Anoop told me that I have been selected. And that was the moment I was on cloud nine!. This round went on for 1 hr.</p><p>Overall, this was my interview experience for redBus. Hope you would learn something insightful.</p><p>Thanks &amp; Regards,<br>Kapil Shanbhag.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a88fc0bf241d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to host websites with Github]]></title>
            <link>https://medium.com/@programerkapilshanbhag/how-to-host-websites-with-github-575b18dbd163?source=rss-69ae160e3e98------2</link>
            <guid isPermaLink="false">https://medium.com/p/575b18dbd163</guid>
            <dc:creator><![CDATA[Kapil Shanbhag]]></dc:creator>
            <pubDate>Mon, 16 Nov 2020 09:54:14 GMT</pubDate>
            <atom:updated>2020-11-16T09:54:14.367Z</atom:updated>
            <content:encoded><![CDATA[<p>Here are the steps to host your website with Github.</p><p>1)First create a GIT Hub account.</p><p>2)Then create a new repository. Select whether you want to make it a private or public. Then click commit changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*YcjxVwGpV7Q5SpTL" /></figure><p>3)Once the repository is created successfully, you will get this page</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*2YvlvUyD5ib-zpTZ" /></figure><p>4)If you want to upload a file or a blog html page to the repository click uploading an existing file.</p><p>Note:-The name of the file should be index.html which serves as an home page of your website or blog.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*VjgZulGVRGSzjheY" /></figure><p>5)After uploading the code go to the settings</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*3lZa2u3eLAIUFbLW" /></figure><p>6)Scroll down to the GITHub pages and put source as the master-branch and your website is published and you will get your published website link.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*qB-_AsSPSLCmGpy1" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*kzS2-wjQz1xBlqBa" /></figure><p>7)click on the link to view your website or blog.</p><p>Note:It may take some time to get published. In such case wait for 30 to 60 secs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*YyftWoWAkBaUW-h5" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=575b18dbd163" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>